[11:52] <miculou> hi all, how do you run apps on mir from the CLI?
[11:53] <miculou> on unity8/desktop
[11:55] <anpok> depending on the toolkit you have to set specific flags.. since they might find a DISPLAY env var.. so GDK_BACKEND=mir QT_QPA_PLATFORM=ubuntumirclient SDL_VIDEODRIVER=mir MIR_SOCKET=/run/user/YOU_USER_ID/mir_socket
[11:55] <anpok> unset DISAPLAY..
[11:56] <anpok> then depending on the applictation unsetting  QT_QPA_PLATFORMTHEME is also necessary
[11:57] <anpok> oh and for unity8 to accept the connection of a starting application it needs to find a desktop file
[11:58] <miculou> anpok: i'm trying to run supertux2 (sdl2 i think)
[11:58] <ogra_> just look up ubuntu-app-launch ;)
[11:58] <anpok> it gets either via ubuntu-app-launch or by looking at the command like parameter
[11:59] <miculou> i tried both ubuntu-app-launch and -- --dektop_file_hint etc
[12:00] <miculou> with ubuntu-app-launch i can see a windows + the loading spinner but then it closes
[12:00] <miculou> and with -- it complains that the args are wrong wich they are
[12:04] <miculou> i'm not even sure if the sdl2 in ubuntu has mir enabled, that's an option on compile.. i think? don't know very noob lol
[12:04] <ogra_> it does
[12:06] <miculou> DL_VIDEODRIVER=mir MIR_SOCKET=/run/mir_socket supertux2
[12:06] <miculou> [FATAL] /build/supertux-7_Bg7b/supertux-0.4.0/src/supertux/main.cpp:444 Unexpected exception: Couldn't set video mode 1280x800: Failed to created a mir surface: Error processing request: An output ID must be specified
[12:06] <miculou> Internal error details: /build/mir-NNwsqv/mir-0.23.2+16.10.20160624/sr
[12:06] <miculou> i don't even know what i'm doing! :))
[12:16] <anpok> you try to connect to a system compositor
[12:16] <anpok> the system compositor only allows full screen clients (aka greeters/session shells)
[12:16] <anpok> so try the mir_socket of the unity8 session instead..
[12:16] <anpok> (/run/mir_socket is opened by unity-system-compositor)
[12:18] <miculou> oh, i see, so this bit MIR_SOCKET=/run/user/YOU_USER_ID/mir_socket
[12:18] <miculou> ?
[12:18] <miculou> let's see
[12:18] <anpok> yes .. should be 1000 in most desktop installations
[12:19] <anpok> and if you launch it from a unity8 terminal .. you would not have to care about that part..
[12:22] <miculou> DL_VIDEODRIVER=mir MIR_SOCKET=/run/user/1000/mir_socket supertux2
[12:22] <miculou> [2016-07-04 15:21:24.099366] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/mir-NNwsqv/mir-0.23.2+16.10.20160624/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
[12:22] <miculou> Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >
[12:22] <miculou> std::exception::what: Failed to send message to server: Broken pipe
[12:23] <miculou> 32, "Broken pipe"
[12:23] <miculou> [FATAL] /build/supertux-7_Bg7b/supertux-0.4.0/src/supertux/main.cpp:444 Unexpected exception: Couldn't initialize SDL: Failed to connect to the Mir Server
[12:24]  * ogra_ assumes the missing S in SDL_VIDEODRIVER is just a copy/paste error ?
[12:24] <miculou> yep
[15:38] <attente> is there a way to change the output scale factor on the mir demo server?
[16:44] <anpok> attente: hm not yet..
[16:46] <anpok> i mean we could add an example server that does that.. or a client that reconfigures the desired content scaling
[16:50] <attente> anpok: how did you test your MirSurfaceOutputEvent patch? did you use a hi-dpi monitor?
[16:53] <anpok> attente: printf... only..
[16:54] <attente> anpok: but is there some way to trigger a MirSurfaceOutputEvent?
[16:59] <anpok> on recent mir servers you should get one after creating the surface
[16:59] <anpok> and then when you move the surface over to a different output
[17:00] <anpok> hmm I am afk for 2.5 hours.. I think I can come up with some test client to play with the scale value