[00:04] <shiznix> hi all, so trying to build some stuff using 16.04 LTS and oxide-qt QML is causing qmlplugindump to break again (see LP# 1332996)
[00:05] <shiznix> "This is because qmlplugindump selects the minimal Qt platform, which doesn't implement QPlatformNativeInterface, which we depend on for getting the native display handle"
[00:06] <shiznix> in my instance, having webbrowser-app installed causes content-hub build failure as it calls qmlplugindump
[00:07] <shiznix> qmlplugindump causes webbrowser-app qml files to call on oxide-qt qml and explodes in the same way as LP# 1332996 :(
[00:07] <shiznix> so, wondering if you guys are working around this problem in some way, or perhaps need to re-open the bug?
[00:08] <shiznix> i guess i could ensure webbrowser-app (and any other app depending on oxide-qt QML) is always uninstalled whenever something calls qmlplugindump, but really just wondering if there's a better way?
[00:09] <shiznix> thanks :)
[07:47] <andyrock> morning all
[08:08] <desrt> word up
[08:42] <seb128> good morning desktopers
[09:09] <TheMuso> Hey folks, sounds like everybody got back safely.
[09:10] <andyrock> morning seb128
[09:12] <seb128> hey TheMuso andyrock, had good flights back?
[09:13] <andyrock> yeah short and safe
[09:27] <Sweet5hark> heya desktoppers!
[09:28] <seb128> hey Sweet5hark! had a good trip back?
[09:30] <Sweet5hark> trip was nice and quick. On the next day I attended "Tanz in den Mai" at the "Muenchner Hofbraeuhaus" -- all you can eat and lots of bavarian beer for everyone ...
[09:31] <Sweet5hark> ... but me -- because I decided to stay away from alcohol after Prague.
[09:31] <seb128> too much drinking in Prague? ;-)
[09:32] <seb128> but yeah, good to have some rest after a team week!
[09:38] <Sweet5hark> well, we didnt overdo it in Prague, I think. But I wanted to take it slower after that.
[09:38] <TheMuso> seb128: Uneventful, so thats good. :)
[09:39] <Sweet5hark> OTOH staying sober there while everyone else around me was getting drunk in dirndl and lederhosen wasnt making things easier either ;) ...
[09:57] <Trevinho> Mh, well... I tried to avoid beer in these days... But in order to go back to normality I still need some small daily amount :-D :-D
[10:04] <seb128> hey Trevinho
[10:04] <Trevinho> hey seb128!
[10:04] <seb128> had a good trip back?
[10:05] <seb128> I miss you guys today ;-)
[10:05] <Trevinho> seb128: yeah... Some hacking included. You? :)
[10:05] <seb128> need to be reused to work without the team!
[10:05] <seb128> it was early on satuday so I was tired didn't get much done
[10:05] <seb128> but it was an ok flgiht
[10:05] <Trevinho> seb128: me too... Unfortunately we had not a table big enough to fit all us, but welll ... yeah, I miss the "office" atmosphere too :)
[10:06] <seb128> yeah :-/
[10:06] <Trevinho> seb128: ... and since I was playing with u-s-d, I noticed that tere are some branches that didn't land. Nothing important, but I didn't see they were approved
[10:08] <seb128> the hotel was alright, but I like being at the office in London better, it has a big table, more nice chairs/other places to set, ac is less agressive, and we don't have people who keep trying to grab your non empty coffee cups or glaces
[10:08] <seb128> oh, I should have a look to that, thanks for pointing it out
[10:08] <seb128> I think one of those was a segfault fix from chrisccoulson, would be good to land
[10:08] <Trevinho> seb128: eheh, yeah.. however "coffee" break here were awesome.
[10:08] <Trevinho> yeah
[10:09] <Trevinho> seb128: together with some mine wich I'll post soon
[10:09] <seb128> k
[10:10] <Trevinho> seb128: speaking of which.... I was looking at it for two reasons: 1) kbd backlight (for normal case could be an easy fix, while for my laptop it seems that there's some missing kernel events to upower)... 2) org.freedesktop.screensaver. It's not implemented and we really need to redirect it to gnome screensaver api, or thuings like chrome (i.e. netflix)
[10:10] <Trevinho> won't be able to disable the screensaver.
[10:11] <Trevinho> as for 2) however I don't know if you prefer to implement it there (I'd say so), or doing it in unity... But I think it's better to use it as a proxy, so that it will work with both unity or gnome screensaver running (which might be still the case when a11y is enabled)
[10:12] <seb128> the proxy seems fine to me
[10:12] <seb128> backlight should work iirc
[10:15] <Trevinho> seb128: the proxy has some unimplemented methods
[10:15] <Trevinho> seb128: it's there, but it doesn't redirect
[10:16] <seb128> oh ok, let's fix it then :-)
[10:16] <Trevinho> seb128: http://pastebin.ubuntu.com/16187264/
[10:16] <Trevinho> seb128: yeah, quite asy to do
[10:17] <Trevinho> seb128: keyboard backlight thing... it works, but... usd doesn't monitor the changes, so it doesn't reset it to the value it was set before (after screensaver, suspend... Othe than after a fresh boot. But this would require a setting that it's probably better to avoid for now)
[10:18] <Trevinho> seb128: in my case however there could need some upower changes, as I don't get any hw event when it's changed from the keyboard
[10:18] <Trevinho> a small thing, but still somewhat annoying :)
[10:21] <seb128> yeah
[10:22] <seb128> we should maybe try to rebase the power plugin on the current GNOME version...
[10:22] <seb128> it has fixes/improvement, it's just quite some changes and there didn't seem to be much buggy behaviour it would fix, most code cleanups/refactoring they did
[10:25] <Trevinho> seb128: i was doing that some time ago...
[10:25] <Trevinho> seb128: and I've a branch, but... There was some u-c-c changes involved too, IIRC so it's not so straight forward
[10:25] <Trevinho> we could try to reduce those, btw
[10:26] <Trevinho> I could check it again, as I don't remember at which point I was :-D. BUt the code is there
[10:27] <seb128> yeah, I started doing that a few times as well
[10:27] <seb128> then decided that it was more work that it was worth
[10:27] <seb128> I don't remember the specifics now though
[10:27] <seb128> it might have been that it needed too much control center changes to go with it
[11:01] <Trevinho> oh, it seems my BAMF change fixed the menu thing...
[11:01]  * Trevinho fingers crossed
[11:02] <pitti> Good morning
[11:02] <desrt> good afternoon, pitti
[11:03] <pitti> hey desrt, how are you?
[11:04]  * pitti waves from Austin
[11:04] <desrt> i'm good.  what's going on in austin?
[11:04]  * desrt waves from köln
[11:06] <pitti> desrt: cloud sprint
[11:06] <pitti> desrt: oh, so we swapped Atlantic shores :)
[11:06] <pitti> desrt: at larsu again?
[11:06] <desrt> larsu lives in berlin :)
[11:06]  * desrt is with mascha
[11:08] <Trevinho> seb128: do you have any clue why the changes you need in order to get different apport infos for the unity package doesn't seem to apply?
[11:09] <Trevinho> seb128: i.e. see https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1532318 the attached files doesn't include the gsettings or the upstart logs
[11:09] <pitti> Trevinho: sorry, which changes?
[11:09] <Trevinho> pitti: hey
[11:09] <Trevinho> pitti: well, we changed the unity (and compiz, iirc) apport file in order to get proper logs
[11:10] <pitti> Trevinho: the hook might crash in the middle, so it might only have the fields up to that certain point
[11:11] <Trevinho> pitti: well, it might... But I see some files that shouldn't be there, like the compiz gconf one
[11:11] <Trevinho> pitti: this was the change, btw: https://code.launchpad.net/~seb128/unity/update-apport-hook/+merge/278774
[11:12] <pitti>     report.add_hooks_info(ui, srcpackage='compiz')
[11:12] <pitti> Trevinho: the compiz info does get added in current source_unity.py ^
[11:13] <Trevinho> pitti: I'm not much familiar with such things, but compiz side was in https://code.launchpad.net/~seb128/compiz/update-apport-hook/+merge/278835
[11:19] <seb128> hey desrt pitti, did you have good flights?
[11:19] <Trevinho> mh, that might be an old report maybe? as new bugs shows more data... mhmh
[11:19] <desrt> seb128: short and sweet.  yours?
[11:19] <seb128> had to wake up a bit early but otherwise trip was without issue
[11:19] <pitti> seb128: yes, went well; terribly tight connection in Chicago (1:15 h only, with immigration and a ~ 25 min security check), but I made it :)
[11:20] <seb128> great
[11:20] <pitti> seb128: home sweet home after two weeks? :-)
[11:22]  * desrt ponders currywurst for lunch
[11:22] <desrt> (first day in germany, would you honestly expect any other possibility?)
[11:24] <pitti> desrt: Bratwurst with Sauerkraut or Eisbein? :-)
[11:24] <desrt> peh
[11:24]  * desrt is an avowed cabbage-hater
[11:33] <seb128> pitti, yeah, in fact in France for some days, then no traveling planned for a while :-)
[11:42] <seb128> Trevinho, unsure, they are there in e.g https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1576310
[11:43] <seb128> the apport hook should have been good in that version
[11:44] <seb128> there was maybe an issue which made the hook stop in the middle as p_itti said
[11:45] <Trevinho> maybe
[11:45] <seb128> that bug ^ is the same one and has the info
[11:47] <seb128> Trevinho, oh, and good work on fixing the menu issue ... it was a bug in bamf then?
[11:47] <Trevinho> seb128: it seems so
[11:47] <Trevinho> seb128: looks like it's a race
[11:50] <seb128> Trevinho, does it had to do with the warnings in e.g https://launchpadlibrarian.net/256917412/upstart.unity-panel-service.log.txt?
[11:50] <seb128> well I guess not
[11:50] <Trevinho> seb128:
[11:50] <seb128> because I've seen such warnings regularly but menus are not missing here
[11:50] <Trevinho> (unity-panel-service:7533): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
[11:50] <Trevinho> ** (unity-panel-service:7533): WARNING **: Failed to get active window:
[11:50] <Trevinho> these seems to be related
[11:51] <Trevinho> however, if they now fails is fine... as once the proxy gives the result out, we still notify with signals
[11:51] <Trevinho> before I think it was failing the initialization and thus not setting the proxy at all
[11:51] <seb128> k
[11:51] <seb128> in fact I don't see those warnings you copied
[11:51] <seb128> but i've some of those "window_menu_model_new: assertion 'BAMF_IS_APPLICATION(app)' failed"
[12:24] <Trevinho> seb128: yeah, that's another thing that I notice as well.... But not really a problem
[12:24] <Trevinho> in fact I could have just removed the g_return_if_fail
[16:41] <dpm> cyphermox, hey - quick question: we had to move some UOS sessions because of Mark's Q&A. We put yours 1h later - does the new time work for you? -> http://summit.ubuntu.com/uos-1605/2016-05-04/display
[18:54] <cyphermox> dpm: it's totally fine
[19:05] <seb128> pitti, why did you had a wily target to bug #1559284? g-s didn't even exist in wily
[19:05] <pitti> seb128: I didn't (or at least not deliberately), I just was asked to add xenial tasks to the two bugs
[19:05] <seb128> pitti, https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1559284/+activity states that you did ;-)
[19:06] <seb128> k
[19:06] <seb128> on thursday
[19:06] <pitti> seb128: ok, sorry then; deleted
[19:06] <seb128> no worry, it just confused me
[19:06] <seb128> was the xenial line for SRU purpose?
[19:07] <seb128> I guess so
[19:07] <seb128> pitti, thanks!
[19:09] <pitti> seb128: yes, mwhudson asked for an SRU
[19:09] <seb128> pitti, well, the SRU is in since thursday
[19:10] <seb128> but I guess it makes sense to target the serie which is SRUed
[19:10] <seb128> though it was already verification-done so in practice it doesn't make much difference
[19:31] <xnox> pitti, http://paste.ubuntu.com/16195208/
[19:33] <xnox> pitti, https://github.com/systemd/systemd/issues/102
[19:34] <pitti> xnox: bug
[19:34] <pitti> xnox: bug 1387908
[19:36] <xnox> pitti, /lib/udev/rules.d/70-u2f.rules is shipped by libu2f-host0
[19:36] <xnox> and it probably shoult "trump"
[19:37] <xnox> the builtin
[19:37] <xnox> cause libu2f-host0 probably will get ids before we patch them into systemd
[19:37] <xnox> pitti, ^
[20:32] <pitti> xnox: https://developer.github.com/v3/activity/events/types/#pullrequestevent
[21:11] <pitti> seb128: FYI, bug 1576656 needs a yakkety upload
[21:35] <seb128> pitti, yeah, I plan to, just didn't have any y-system ready to test it while traveling
[21:35] <seb128> pitti, thanks for reviewing!