/srv/irclogs.ubuntu.com/2016/09/21/#ubuntu-unity.txt

=== peaches is now known as Guest15157
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 black10:11
SaviqEdwardMorbius, can you clear ~/.cache/upstart/* and /var/crash/* and /var/log/lightdm/* - try again and look in those folders for anything interesting10:24
SaviqEdwardMorbius, also, because of bug #1525285, you might need to start an X11 session first10:24
ubot5`bug 1525285 in clutter-gst-3.0 (Ubuntu) "inspecting clutter plugin hangs outside X11" [High,Triaged] https://launchpad.net/bugs/152528510:24
=== Guest15157 is now known as badpeaches
=== badpeaches is now known as peaches
EdwardMorbiusSaviq thanks I will check that out11:05
mterryTrevinho: 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:48
Trevinhomterry: mhmh, let me see... I think there was some sort of hack anyway12:49
Trevinhomterry: anyway, this refactor is somewhat temporary in terms of design, since I'm now updating it to match new designs12:50
mterryTrevinho: sure, I'm just trying to avoid regressions, no matter how temporary  :)12:51
Trevinhomterry: mhmh, yeah... Actually the old menu-item had no opacity set when an item was disabled12:53
Trevinhomterry: however I think this is not wrong, and also in designs so they look... But...12:53
Trevinhomterry: I mean, it was like that only in eventMenu12:54
mterryTrevinho: ah right, I was looking at EventMenu and didn't notice the filename12:54
mterryTrevinho: 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
mterrySeems like a not-uncommon desire, and one that doesn't necessarily imply a visual change12:55
Trevinhomterry: 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 override12:57
mterryTrevinho: 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
mterryMaybe we need another key like interactive=false or something13:00
Trevinhoyeah, I agree.. Since both cases could be valid13:00
Trevinhomterry: anyway, I guess it's better to revert the change for now, right?13:01
mterryTrevinho: yeah maybe just put it in EventMenu like before.  :-/13:01
Trevinhook13:02
Trevinhomterry: fine, pushed13:06
mterryTrevinho: nice thanks, approved13:08
Trevinhothanks13:08
sil2100Saviq, 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.gz13:55
sil2100Saviq, dandrader, faenil: it's from a test-run of the KPI-sync script with the instrument-enable patch13:55
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:56
dandradersil2100, is that lp:qtmir or some silo?13:57
sil2100sil2100: it's the latest released qtmir + http://pastebin.ubuntu.com/23146289/13:57
sil2100(from the overlay)13:57
dandradersil2100, hmm, I recall a branch from faenil fixing a similar issue which happens when you enable some compiler flag...13:58
* faenil reads13:58
dandradersil2100, https://code.launchpad.net/~faenil/qtmir/add_missing_default_return_value/+merge/304945 fixes it I think13:58
sil2100Oh, ok, thanks ;)13:59
faenilyeah13:59
faenilso no new qtmir release since that MR?13:59
dandraderfaenil, no. see if it's in silo 7813:59
Saviq'fraid not14:00
Saviqhopefully that silo will land today and we can prepare the next one14:00
sil2100Ok, no worries, if that's scheduled somewhere then that's good14:01
faenilyeah, doesn't seem to be in 78, at a quick glance14:01
faenilsil2100: but thanks for spending time on the kpi stuff! )14:11
faenil:)14:11
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== dandrader is now known as dandrader|afk
sil2100faenil: no problem ;) Ok, scripts set-up now, let me send you an e-mail about all the details16:18
faenilsil2100: coool16:18
=== dandrader|afk is now known as dandrader
taiebotHey 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.18:01
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!