[10:11] <EdwardMorbius>  hello, how can I debug Unity 8 not starting on 16.10 on Nouveau driver? Installed 16.10 on a spare partition to test Unity 8 but it doesnt start, after I enter my password in Unity 7 greeter it throws out some message and then screen turns black
[10:24] <Saviq> EdwardMorbius, can you clear ~/.cache/upstart/* and /var/crash/* and /var/log/lightdm/* - try again and look in those folders for anything interesting
[10:24] <Saviq> EdwardMorbius, also, because of bug #1525285, you might need to start an X11 session first
[10:24] <ubot5`> bug 1525285 in clutter-gst-3.0 (Ubuntu) "inspecting clutter plugin hangs outside X11" [High,Triaged] https://launchpad.net/bugs/1525285
[11:05] <EdwardMorbius> Saviq thanks I will check that out
[12:48] <mterry> Trevinho: so I see what you're saying about the opacity 0.5 / enabled status...  But the old code looked full opacity to the user without changes in u8 -- what are we now doing differently?
[12:49] <Trevinho> mterry: mhmh, let me see... I think there was some sort of hack anyway
[12:50] <Trevinho> mterry: anyway, this refactor is somewhat temporary in terms of design, since I'm now updating it to match new designs
[12:51] <mterry> Trevinho: sure, I'm just trying to avoid regressions, no matter how temporary  :)
[12:53] <Trevinho> mterry: mhmh, yeah... Actually the old menu-item had no opacity set when an item was disabled
[12:53] <Trevinho> mterry: however I think this is not wrong, and also in designs so they look... But...
[12:54] <Trevinho> mterry: I mean, it was like that only in eventMenu
[12:54] <mterry> Trevinho: ah right, I was looking at EventMenu and didn't notice the filename
[12:55] <mterry> Trevinho: so you're saying that changing opacity is fixing us to be closer to design?  (if the menu item wants to be non-interactive, is there something they can do besides enabled=false to get that across?)
[12:55] <mterry> Seems like a not-uncommon desire, and one that doesn't necessarily imply a visual change
[12:57] <Trevinho> mterry: let me check, but that seems closer... However I can also put that back and enable only for EventMenu,  but in geeneral I think we should indicate about disabled and enabled menus... If it's not the case, then we can override
[13:00] <mterry> Trevinho: well sort of.  Being enabled means you are clickable, right? and some menu items just want to be a label (like the charge level menu item).  They set enabled=false currently to do that, but don't want to look like they're disabled...
[13:00] <mterry> Maybe we need another key like interactive=false or something
[13:00] <Trevinho> yeah, I agree.. Since both cases could be valid
[13:01] <Trevinho> mterry: anyway, I guess it's better to revert the change for now, right?
[13:01] <mterry> Trevinho: yeah maybe just put it in EventMenu like before.  :-/
[13:02] <Trevinho> ok
[13:06] <Trevinho> mterry: fine, pushed
[13:08] <mterry> Trevinho: nice thanks, approved
[13:08] <Trevinho> thanks
[13:55] <sil2100> Saviq, dandrader, faenil: hey! Does anyone of you guys know any possible reason for such a qtmir FTBFS? https://launchpadlibrarian.net/285791636/buildlog_ubuntu-vivid-amd64.qtmir_0.4.8+15.04.20160906-0ubuntu1kpi1~test2_BUILDING.txt.gz
[13:55] <sil2100> Saviq, dandrader, faenil: it's from a test-run of the KPI-sync script with the instrument-enable patch
[13:56] <dandrader>  /«BUILDDIR»/qtmir-0.4.8+15.04.20160906/src/platforms/mirserver/screen.cpp:97:1: error: control reaches end of non-void function [-Werror=return-type]
[13:57] <dandrader> sil2100, is that lp:qtmir or some silo?
[13:57] <sil2100> sil2100: it's the latest released qtmir + http://pastebin.ubuntu.com/23146289/
[13:57] <sil2100> (from the overlay)
[13:58] <dandrader> sil2100, hmm, I recall a branch from faenil fixing a similar issue which happens when you enable some compiler flag...
[13:58]  * faenil reads
[13:58] <dandrader> sil2100, https://code.launchpad.net/~faenil/qtmir/add_missing_default_return_value/+merge/304945 fixes it I think
[13:59] <sil2100> Oh, ok, thanks ;)
[13:59] <faenil> yeah
[13:59] <faenil> so no new qtmir release since that MR?
[13:59] <dandrader> faenil, no. see if it's in silo 78
[14:00] <Saviq> 'fraid not
[14:00] <Saviq> hopefully that silo will land today and we can prepare the next one
[14:01] <sil2100> Ok, no worries, if that's scheduled somewhere then that's good
[14:01] <faenil> yeah, doesn't seem to be in 78, at a quick glance
[14:11] <faenil> sil2100: but thanks for spending time on the kpi stuff! )
[14:11] <faenil> :)
[16:18] <sil2100> faenil: no problem ;) Ok, scripts set-up now, let me send you an e-mail about all the details
[16:18] <faenil> sil2100: coool
[18:01] <taiebot> Hey could i give design feedback on the "unified stage" spread. I know it is very early  but i have installed silo 75 to have a look. I really feel the windows in the spread are two small and they all look like squashed.  There is like 30% of the screen not used above them. Would it not be better to have bigger windows there. my 2 cents. Unity8 looks much more responsive.