[05:22] Hi [05:22] Hi hi. [05:54] morning all [05:59] hiya, ra [06:24] Morning to Europe and visitors to Europe [06:25] And Africa [06:27] It's official I have too many test peripherals on this desk [06:40] Hmm, Unity7 login failure fixed on yakkety but still waiting for a fix in the live images... http://cdimage.ubuntu.com/daily-live/current/ [06:40] So live Ubuntu doesn't work today [06:41] I guess a new image is only hours away [06:43] cimi: Out of curiosity what hardware are you using to test Unity8? [06:49] yo [06:52] 'sup [06:53] west side [06:53] tedg: find ... | xargs sed -i '/^ExecStart/ s/$/\nRestart=on-failure/' [06:57] hey desktopers [07:11] hi seb128 and qengho and robert_ancell_ and duflu and Laney and pitti (end of scroll up :p) [07:12] o/ [07:12] \o [07:12] -o- [07:12] mOm [07:12] m m [07:19] ^_^ [07:51] Anyone know what changed with dbus/dbus menus in yakkety? [07:51] https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1604704 [07:51] Launchpad bug 1604704 in gtk+3.0 (Ubuntu) "[regression] GTK apps hang for a very long time on start-up under Xmir and Mir failing to find dbus" [Undecided,New] [08:07] morning all [08:10] morning willcooke [08:17] tedg: https://www.freedesktop.org/wiki/Software/systemd/dbus/ [08:33] morning follks [08:33] howdy Trevinho [08:34] hi willcooke et Trevinho [08:34] salut you meant [08:34] coucou [08:34] :D [08:36] hey Trevinho willcooke hikiko [08:36] did you guys see the question from duflu earlier, about this: [08:36] https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1604704 [08:36] Launchpad bug 1604704 in gtk+3.0 (Ubuntu) "[regression] GTK apps hang for a very long time on start-up under Xmir and Mir failing to find dbus" [Undecided,New] [08:36] I saw the bug [08:37] gtk or dbus didn't change in yakkety afaik [08:37] also mir/xmir I've no clue how to even test that [08:38] I should add some test cases... [08:40] that would be useful [08:41] gtk didn't change [08:41] did mir change? [08:41] when did that delay thing start? [08:42] mir always changes :-) [08:43] Yes, but hopefully Mir and Xmir never touch dbus yet.... [08:46] tedg: busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager ListUnitFiles [08:47] Something is wired into GTK to go searching for a dbus when it shouldn't. Is that menus? [08:49] could be [08:49] but why shouldn't be using dbus? [08:50] what is concerning is that it tries to contact another bus that the actual one [08:50] seb128: because the same bug applies to native Mir shells (which have no busses) [08:50] what is the value of DBUS_SESSION_BUS_ADDRESS ? [08:50] seb128: I think it's confused by DISPLAY=:1 (Xmir) but the session bus was create by and for Unity8 [08:51] tedg: gdbus call --session -d org.freedesktop.systemd1 -o /org/freedesktop/systemd1 -m org.freedesktop.systemd1.Manager.ListUnitFiles [08:51] seb128: There is no DBUS_* environment. I'm logged in to ssh [08:51] But might try [08:54] that might be the issue [08:56] seb128: Yep setting that fixes the problem in Unity8. In Mir demo shells however there is no bus so no correct address to set [08:57] I guess $things could handle better no dbus [08:57] but having no session bus is not a normal env nowadays [08:58] seb128: Sure, but it used to work :) [08:58] can you get a bt of the hang? [08:58] it might tell us what code is doing a sync call [08:58] It's only when dbus finds $DISPLAY that it hangs. But I need to focus on other things right now [08:58] k [08:59] but yeah, it behaves differently [09:01] seb128: Not assuming $DISPLAY uniquely identifies the login or session bus any more would solve it sufficiently [09:01] Although you then have to assume $USER has a single login instead [09:02] it's something somebody should look at I guess [09:02] but everybody is busy so I don't think that happening any time soon === robert_ancell_ is now known as robert_ancell [09:25] pitti: http://people.canonical.com/~laney/patch-dump/0001-Die-if-the-XDG-session-we-were-started-under-goes-aw.patch [09:39] good morning [09:40] hey andyrock [10:38] pitti, https://bugzilla.redhat.com/show_bug.cgi?id=1303300 [10:38] bugzilla.redhat.com bug 1303300 in samba "gvfsd-smb-browse causes 100% CPU usage" [Unspecified,New] [10:39] pitti, https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032 [10:39] Launchpad bug 1409032 in samba (Ubuntu) "gvfsd-smb: very high CPU utilisation" [High,Confirmed] [11:11] Seem to be hit by this today: http://www.bbc.co.uk/news/technology-36844712 [11:18] oh, a tornado warning for my city for tomorrow! [11:19] nice === hikiko is now known as hikiko|ln === hikiko|ln is now known as hikiko [15:47] * Laney has made it to le airport [15:51] happy trails Laney [15:51] the flight takes 15 minutes [15:52] ohhohoh [15:52] Laney: it's spelled "Luchthaven" [17:22] seems like I didn't restart IRC after reboot! [17:33] night all, see you next week [17:43] mitya57, question for you, do you know how qt4 decide what theming to use? we are looking at using systemd for user session in yakkety and with it and dbus-user-session enabled qt code looks like win95 [17:43] qt5 looks fine [17:43] I don't see anything in the env that looks like it could be it [17:43] so wondering if it's poking on dbus or something [17:45] seb128, I think it checks for $DESKTOP_SESSION=gnome or non-empty $GNOME_SESSION_DESKTOP_ID [17:45] http://sources.debian.net/src/qt4-x11/4:4.8.7%2Bdfsg-8/src/gui/kernel/qapplication_x11.cpp/#L2346 [17:47] mitya57, thanks, DESKTOP_SESSION=gnome makes it work but that's not it because from my "env" call in each it was not defined under upstart either [17:47] or rather it was DESKTOP_SESSION=ubuntu [17:47] for both [17:47] they also have GNOME_DESKTOP_SESSION_ID=this-is-deprecated [17:47] This one should work, the check is only for non-emptinness [17:48] Btw, yay for systemd sessions ;) [17:48] I must have done my "env" wrong before [17:48] it' s unset now [17:48] thanks!