[05:35] <pitti> Good morning
[07:37] <seb128> good morning desktopers
[08:01] <Laney> hey hey!
[08:01] <Laney> 25/06 00:13:10 -queuebot:#ubuntu-release- New binary: chocolate-doom [amd64] (wily-proposed/multiverse) [2.2.0-1] (no packageset)
[08:01]  * Laney wonders what that could be
[08:02] <seb128> hey Laney
[08:08] <Laney> hey seb128!
[08:08] <Laney> how's it going?
[08:08] <seb128> good!
[08:08] <seb128> you?
[08:08] <seb128> had a drive longer that expected yesterday though
[08:09] <seb128> they are redoing some highway and changed the road to be 1 line in one way and 2 in the other
[08:09] <Laney> yeah good, did some planting out in the garden last night
[08:09] <seb128> I was on the 1 line direction, and apparently a truck had issues and got stucked
[08:09] <Laney> one day i'll get some food out of this thing
[08:09] <seb128> blocking everything for 1.5 hours...
[08:10] <Laney> had like 3 potatoes so far
[08:10] <Laney> oh man, that sounds dire
[08:10] <seb128> hehe
[08:10] <seb128> well, I had my laptop, so I just debugged a bit that snappy image offline while stucked :p
[08:10] <seb128> but it sucked being stopped in the middle of the road in the sun
[08:11] <seb128> what did you plant in the garden?
[08:14] <Laney> some tomatoes and rocket
[08:14] <Laney> and some other things got upgraded to bigger pots
[08:16] <seb128> watch out for the slugs ;-)
[08:17] <Laney> grr!
[08:17] <Laney> i hope that letting things get quite big in the pots first should help
[08:17] <Laney> then putting them in the ground after
[08:17] <seb128> I guess it should help
[08:17] <seb128> still they might eat your food :p
[08:17] <seb128> bah
[08:18] <seb128> is one supposed to be able to "upstart --user" from a vt or ssh?
[08:18] <Laney> I took a picture the other day...
[08:18] <seb128> xnox, ^
[08:18] <seb128> Laney, to prove you had vegetables because having nothing left? ;-)
[08:18] <xnox> seb128: eh.... no.
[08:18] <seb128> talk with pitti about beer traps :p
[08:18] <xnox> seb128: you can "join" existing graphical session though.
[08:19] <Laney> https://goo.gl/photos/877B43UqAHsaM4Dq7
[08:19] <Laney> AAAAAAHHHHHHHH
[08:19] <seb128> oh, snails, nice ;-)
[08:19] <xnox> seb128: export `cat /run/user/upstart/*.session` or some such, and then initctl --user should do the right stuff.
[08:20] <xnox> seb128: in theory launching `upstart --user` from vt/ssh should do the right thing, in practice it tries & fails to launch gui things.
[08:21] <seb128> xnox, thanks, in fact that's on a snappy image and upstart-event-bridge seems to not like it according to .xsession-errors so I was trying to start it by hand to get debug info
[08:21] <seb128> the log only says it exit 1 and is retried and fail the same way
[08:23] <Laney> seb128: you want to try to get wps & friends migrated?
[08:23] <seb128> Laney, sure, but you need to tell me what to do because I didn't follow the details ;-)
[08:24] <seb128> xnox, hum, with the export, it's better, it complains about not being about the connect to system Upstart, which is normal, that's a systemd system ... why is it trying to use the event bridge?
[08:24] <Laney> seb128: I think demote-to-proposed zygrib (FTBFS with new gda) and remove mapnik from wily-proposed should do it
[08:25] <seb128> oh, in fact .xsession-errors has the same issue on my normal laptop
[08:25] <Laney> that's what you need to do, then I should be able to copy back the old version
[08:25] <seb128> so I guess that's a redherring
[08:25] <seb128> Laney, ok
[08:26] <Laney> maybe sync blacklist mapnik?
[08:26] <xnox> seb128: yes, i have a patch to do event-bridge under systemd, but i don't think it landed last cycle (cause phone was not a priority)
[08:26] <xnox> imho i could land a few more things and then slowly start kicking upstart from the user session out.
[08:26] <xnox> patriciadavila: ipv6 - respect!
[08:27] <Laney> I wonder why I'm not on via v6
[08:28] <seb128> xnox, that would be nice ;-)
[08:28] <seb128> though user session might be way out
[08:29] <Laney> 25/06 09:28:49 [Freenode] -!-  hostname : 2001:ba8:1f1:f1ab:216:3eff:fe14:af00 2001:ba8:1f1:f1ab:216:3eff:fe14:af00
[08:29] <xnox> seb128: heh. well, between james and I, i'm sure we can cook something up =)
[08:29] <xnox> Laney: you have ipv6 too, or what's going on?
[08:29] <seb128> Laney, ok, done the demoting&deleting from proposed, unsure about the sync blocking ... what is going to happen if it's synced back to proposed after the migration?
[08:30] <Laney> xnox: yeah but I was connected over v4, guess that is preferred still
[08:30] <Laney> seb128: I'm worried the broken transition will start again if they do another upload before it is ready
[08:31] <seb128> Laney, let's see, worth thing we remove it again?
[08:31] <Laney> I guess we could deal in the same way if necessary
[09:47] <Laney> it's going in \o/
[09:47] <seb128> \o/
[09:48] <seb128> k, so recovery mode works on a normal install in wily
[09:48] <seb128> seems like another snappy image specific issue :-/
[09:49] <Laney> does this stuff work (exist?) on snappy core?
[09:49] <seb128> "stuff"?
[09:49] <seb128> I've no idea how recovery works, it's that by having "friendly-recovery" installed?
[09:49] <Laney> recovery, other problems that you have, do you compare?
[09:49] <seb128> the boot entry has "recovery"
[09:49] <seb128> compare what with what?
[09:50] <Laney> snappy core
[09:51] <seb128> oh, core, sorry I misread before
[09:51] <pitti> seb128: friendly-recovery, yes
[09:51] <seb128> I did compare some stuff, not for that one
[09:51] <pitti> but I don't think that makes much sense on snappy
[09:51] <pitti> if you ever land in it, you'll do more harm than good
[09:51] <pitti> and with the A/B partitions this Should Not Happen™
[09:52] <seb128> well my first motivation was that sudo was screwed and I needed a way to get a root prompt
[09:52] <seb128> and if it's not useful it should not be listed in grub
[09:53] <seb128> hum, friendly recovery is installed
[09:53] <seb128> k need to go for lunch but I'm going to look more after that
[11:19] <Sweet5hark> dpm: fyi, libreoffice is already way ahead on the size issue: https://twitter.com/samtuke/status/614021556675682308
[11:20] <dpm> Sweet5hark, I might need some more context though: he's throwing a bunch of figures, but I'm not sure exactly what they mean
[11:21] <dpm> oh, msoffice
[11:21] <dpm> ok, you were comparing sizes
[11:22] <Sweet5hark> dpm: right -- MS will have lots of fun cutting that monster back down.
[12:02] <mitya57> Who is responsible for compiz packaging these days?
[12:03]  * mitya57 wants a review on his https://code.launchpad.net/~mitya57/compiz/switcher-plugins-in-default/+merge/262518
[12:10] <seb128> mitya57, bregma&co
[12:11] <mitya57> thanks!
[12:11] <seb128> yw
[12:11] <mitya57> bregma, ↑ — can you please review that?
[12:36] <Sweet5hark> lol@ https://bugzilla.redhat.com/show_bug.cgi?id=1141137
[12:37] <Sweet5hark> ah, pitti is even in on the party ...
[12:38] <pitti> Sweet5hark: we got that patch reverted in Debian and Ubuntu, does it affect us still?
[12:41] <Sweet5hark> pitti: no, just saw it fly by on social media (someone requesting a systemd project maintainer attitude readjustment tool)
[15:01] <seb128> bregma, hey, I saw you discussing with brandon about u-s-c, are you guys debugging issues with it?
[15:02] <seb128> bregma, I'm having problems with unity8 on the snappy personal image
[15:02] <bregma> seb128, well, our problems is we're trying to use it in a way it was sort of designed to prevent :)
[15:03] <bregma> seb128, the log you posed looked like it had a bad library and that's what was preventing Unity8 from running
[15:07] <seb128> bregma, the symbol error?
[15:08] <bregma> seb128, yeah
[15:08] <bregma> looks suspcious to me
[15:08] <bregma> seb128, was that log from Unity8 or from USC?
[15:09] <seb128> bregma,  that's bug #1458689
[15:09] <seb128> but removing the .so doesn't change anything
[15:10] <seb128> bregma, http://paste.ubuntu.com/11773781/ is usc
[15:10] <seb128> bregma, http://paste.ubuntu.com/11773784/ unity8.log
[15:11] <bregma> seb128, the USC log looks normal:  it's just sitting there waiting for U8 to ack its start, which never happens
[15:12] <bregma> seb128, it looks like the nested Mir server in qtmir is not starting for whatever reason
[15:12] <bregma> at this point I usually resort ot using gdb in batch mode
[15:13] <seb128> on what process?
[15:14] <bregma> copy /usr/share/upstart/session/unity8.conf into ~/.config/upstart and replace the exec line with a gdb command to run unity8
[15:15] <seb128> there is no way to get debug info in a log on why the nested mir server doesn't start?
[15:16] <bregma> seb128, you might be able to turn on the LTTNG loggin from Mir
[15:16] <seb128> you would think some people did that before and it's documented ;-)
[15:16] <bregma> Mir?  documented?
[15:16] <seb128> lol, one can dream, no? ;-)
[15:17] <seb128> bregma, when you gdb, do you usually b/stop on something?
[15:18] <bregma> seb128, I spent a lot of time using "catch throw" to stop when exceptions are thrown and get a backtrace
[15:18] <bregma> may not help in your case
[15:22] <bregma> seb128, looking at the qtmir code involved, it's all wrapped in threads and ends up just calling into the Mir libraries, I thing using LTTNG might be your most productive approach
[15:25] <seb128> bregma, how do you do that?
[15:28] <bregma> seb128, you might want to ask the Mir devs, but you could start at http://lttng.org/docs/#doc-tracing-your-own-user-application and add commands to ~/.config/upstart/unity8.conf
[15:28] <bregma> I have a vague recollection of doing just that
[15:30] <seb128> bregma, thanks
[15:30] <seb128> that's less trivial that what I was hopping for there
[15:51]  * mitya57 wonders why bregma ignores him
[15:52] <bregma> mitya57, I'm not ignoring you, I'm working through plenty of backlogs
[15:52] <bregma> always backlogs
[15:55] <bregma> mitya57, I'm not sure if we want to move that plugin into the core plugins or just have compiz-gnome depend on compiz-plugins instead
[15:56] <bregma> I need to discuss it with other devs
[15:57] <mitya57> bregma: The latter won't much help because the session has TryExec=compiz, and thus it will show every time when compiz is installed.
[15:58] <mitya57> If moving switcher plugin to -main is not an option, then I'll have to split compiz session to a separate package (which I don't want to do).
[15:59] <mitya57> bregma: So please discuss it and let me know the result :)
[16:00] <bregma> mitya57, we'll comment on the MP when we have a conclusion
[16:00] <mitya57> Thank you!
[16:00] <chrisccoulson> when starting unity 8 desktop, is anything meant to set QT_QPA_PLATFORM, and if so, what sets it?
[16:04] <bregma> chrisccoulson, /usr/bin/lightdm-unity8-session sets it in the unity8-desktop-session-mir package
[16:05] <chrisccoulson> bregma, unity8 desktop doesn't run on my system, and never has done. I get this crash on startup: https://errors.ubuntu.com/oops/a111aea4-1b52-11e5-af4a-fa163e5bb1a2
[16:05] <chrisccoulson> which looks like QT_QPA_PLATFORM isn't set
[16:06] <bregma> chrisccoulson, yeah, you should never see references to xcb
[16:06] <bregma> chrisccoulson, the alternative is you need to install the desktop graphics stack because Mir no longer pulls it in as a dependency
[16:07] <chrisccoulson> bregma, what exactly do I need to install?
[16:07] <bregma> it gets seeded in the desktop-next ISO but it was only recently added as a dependency to the unity8-desktop-session-mir package
[16:08] <bregma> chrisccoulson, try manually adding the mir-graphics-drivers-desktop package and see if it helps
[16:09] <chrisccoulson> bregma, it looks like I've already got that installed
[16:09] <bregma> :(
[16:15] <bregma> chrisccoulson, are you running on Intel hardware?
[16:15] <chrisccoulson> bregma, I am
[16:15] <bregma> hmm
[16:15] <bregma> wily or vivid?
[16:16] <chrisccoulson> bregma, vivid
[16:18] <bregma> very odd
[16:18] <bregma> chrisccoulson, does it happen with unity8 or just unity8-dash?
[16:19] <chrisccoulson> bregma, I have a crash report from unity8 at the same time - https://errors.ubuntu.com/oops/94721788-1b52-11e5-b837-fa163e75317b
[16:19] <chrisccoulson> although, it doesn't look like there's a stack trace there
[17:34] <chrisccoulson> bregma, how is the session meant to be started? In my lightdm.log, I see "Running command /usr/sbin/lightdm-session lightdm-unity8-session"
[17:36] <bregma> chrisccoulson, unity8-desktop-session-mir provides the file /usr/share/lightdm/lightdm.conf.d/55-unity8.conf that tells LightDM what to do, which is basically run /usr/bin/lightdm-unity8-session
[17:36] <bregma> that script just sets some environment variables and runs upstart
[17:37] <chrisccoulson> bregma, oh, I bet this is because lightdm hasn't been restarted since that file was installed
[17:37] <chrisccoulson> brb
[17:44] <chrisccoulson> bregma, so, I can log in to it now. Only, I can't get past the first run bit because I can't pull the launcher out
[17:46] <chrisccoulson> Ok, I can do it with the mouse. Just not my touchpad
[17:57] <bregma> chrisccoulson, yes, that's a tragic limitation to the new Unity design
[17:57]  * bregma expects it to be fixed by the time it ships officially
[17:57] <chrisccoulson> heh, I hope so
[17:58] <bregma> all my laptops have touchscreens
[18:02] <chrisccoulson> bregma, yeah, I don't have a touchscreen on my laptop
[18:03] <chrisccoulson> It's sort-of ok with the mouse, but unusable with the touchpad. The cursor actually wanders across the screen when I put my finger on the touchpad
[19:43] <chrisccoulson> right, so, webbrowser-app works on desktop-next again :)
[19:45] <chrisccoulson> well, locally anyway