/srv/irclogs.ubuntu.com/2015/02/20/#ubuntu-desktop.txt

pittiGood morning05:55
ochosimorning everyone06:51
ochosilarsu: since you said i should ping you if i don't get a response within a few days, here it comes! PING :D https://bugzilla.gnome.org/show_bug.cgi?id=74460106:52
ubot5Gnome bug 744601 in general "Titlebar is hidden when window is maximized" [Normal,Unconfirmed]06:52
darkxstochosi, won't that conflict with unity where they do hide titlebars for maximised apps?06:57
ochosidarkxst: i'm not really an expert on unity over here, but since larsu approved it, i presume it's ok for them06:58
darkxstseb128, does unity rely on set_hide_titlebar_when_maximized, or do the global menu bar hacks override that?06:59
seb128hum, to hide what?07:00
seb128titlebars are handled by the wm and always removed afaik07:00
seb128if it was relying on a flag it would work on every application07:01
ochosiyeah, i think this line in evince is just a relic07:01
pittibonjour seb12807:02
seb128pitti, salut, ça va ?07:02
pittiseb128: ça va bien, mieux que systemd :)07:03
pittiseb128, Laney: I filed bug 142381107:03
ubot5bug 1423811 in systemd (Ubuntu) "219-1ubuntu1 regression: boot hangs, logind fails" [Critical,In progress] https://launchpad.net/bugs/142381107:03
seb128pitti, are Laney and I the only ones to see the issue?07:03
pittiI now get this as well07:03
seb128oh07:03
seb128great!07:03
pittisome dist-upgrade or change or whatever triggered it07:03
pittiso I'm debugging it now07:03
seb128going to be easier for you to debug07:04
seb128let me know how you debug07:04
pittiI added the minimal set of packages to downgrade there07:04
seb128can be useful for next time :-)07:04
pittiseb128, Laney: would be nice if you could confirm that you have exactly the same, i. e. downgrading these four packages and doing no other modifications makes things work again? (with and without splash)07:04
seb128can do that in a bit07:04
seb128but I need to do some catchup on email and stuff first07:05
pittiseb128: no worries07:05
pittiseb128: I'm fairly sure it's the same issue, it woudl be too much of a coincidence07:05
pittiLaney, seb128: or, eaiser: just wait until I have a fix, and if things still go haywire for you, you file another bug (but chances are low)07:05
seb128right, I was going to say07:06
seb128still please keep us updated on what you do and what you found07:06
pittiseb128: I got a debug journal and did the usual package bisecting first, so pretty much what you did yesterday07:08
pittiseb128: I now build a package with a sysv-generator fix, to ensure that it's not that (or maybe it actually is)07:08
pittiseb128: and then I'll start bisecting individual /lib/systemd/systemd-* binaries07:08
pittiand also have a good deep look at the debug log07:08
pitti(wrt. "what do I do now"); but I keep track of stuff in the bug report too07:09
seb128k07:09
darkxstseb128, well the hints come from gtk, but we have mostly been on CSD's for a while now, so....07:10
didrocksgood morning07:22
didrocksseb128: pitti: I got the boot issue once this morning07:22
seb128lut didrocks07:23
didrocksspent 30 minutes rebooting/trying multiple things…07:23
seb128didrocks, pitti gets it as well07:23
didrocksdidn't retrigger it07:23
seb128he's debugging07:23
didrocksah07:23
seb128you guys and you "no, works fine here" :-)07:23
didrocksseb128: well, I did boot twice with the new systemd without any issue07:23
seb128didrocks, happy friday btw!07:23
didrocksand this morning, got it once on 10 boots!07:23
didrocksso clearly annoying issue :/07:24
didrockshappy friday seb128 :)07:24
pittibonjour didrocks07:24
pittiyeah, until yesterday 219-1ubuntu1 was humming away fine for me, too..07:25
didrockspitti: I don't want to say, but seb128 saw it first07:25
pittididrocks: hereux vendredi !07:25
didrocksI will definitively put the blame on him :)07:25
didrocksand happily :p07:25
* didrocks hugs seb12807:25
didrockspitti: joyeux vendredi aussi!07:25
* seb128 hugs didrocks back07:25
pittididrocks: keeping track in bug 142381107:25
ubot5bug 1423811 in systemd (Ubuntu) "219-1ubuntu1 regression: boot hangs, logind fails" [Critical,In progress] https://launchpad.net/bugs/142381107:25
* didrocks opens07:25
didrocksoh, you were able to use list-jobs07:26
pittisudo works, yes07:26
didrocksmy vt1 login was totally screwed for me07:27
pittiwithout sudo it wants polkit which doesn't work07:27
didrocksno sudo, no dbus…07:27
didrocksthe machine was really in a weird state07:27
didrocksall commands hanging basically07:27
pittiI get something funny in qemu as well: I see the plymouth dots on top of my X session07:28
didrocksso "sudo plymouth quit" didn't work07:29
didrocks(and we ignore the return value for this job)07:29
pittithat's unexpectedc -- my locally built .debs with merging a few trivial fixes from debian work07:32
* pitti rebuilds our exact vivid package locally to verify07:32
pittibut that may explain why it worked for me until yesterday, when I got my self-built debs replaced with the archive's07:33
didrockspitti: well, I always used the archive version, and so, on 12 boots since I upgraded, I only got the issue once07:33
pittididrocks: obviously a race; it also works fine with teh archive debs in a VM07:34
* pitti tries some other things, bbl07:35
didrocksgood luck!07:35
pittiWTF, I managed to kill the dpkg database07:42
pitti/var/lib/dpkg/status is mostly empty07:42
pittiseb128, didrocks, Laney: it works again here without persistant journal07:46
pittibut I rm'ed mine; could you perhaps mv /var/log/journal{,.old} to keep it for reproducing, and check if that helps?07:47
didrockspitti: I disabled persistent journal last week07:47
didrockspitti: and so, got the issue this morning07:47
pittiack, noting that down07:48
didrocks$ ls /var/log/journal07:48
didrocksls: impossible d'accéder à /var/log/journal: Aucun fichier ou dossier de ce type07:48
pittiso now I hope I can get the issue again somehow07:48
didrocksyeah, definitively can't here :/07:48
pittididrocks: *phew*, I got it in a VM! https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/308:19
ubot5Launchpad bug 1423811 in systemd (Ubuntu) "219-1ubuntu1 regression: boot hangs, logind fails" [Critical,In progress]08:19
pittithat makes things a ton easier08:20
didrockspitti: interesting, not sure how this is related as I didn't touch the journal for quite a while, but if this can trigger the race reliably, that's nice!08:21
pittididrocks: well, reliable enough at least, for me08:21
pittiin qemu it only seems to hang once after that, but good enough I guess08:23
didrocksinteresting…08:25
* pitti runs off to get a haircut, bbl08:25
didrockssee you pitti :)08:25
seb128pitti, have fun!08:25
willcookemorning08:46
* willcooke <-- no here08:46
willcooke*not08:47
didrockshey willcooke-london :)08:47
willcookeSo much for my day off08:48
tsdgeoshmmm08:48
tsdgeosguys i have no indicators at atll running08:48
tsdgeosis it something i did?08:49
tsdgeosor did some update land yesterday?08:49
seb128hey willcooke08:49
didrockstsdgeos: do you have unity-panel-service running?08:49
seb128tsdgeos, desktop, phone, Ubuntu version, desktop env?08:49
tsdgeosdidrocks: yes08:49
tsdgeosseb128: desktop08:49
seb128vivid?08:50
tsdgeosotherwise i'd be in #ubuntu-touch :D08:50
tsdgeosseb128: yes08:50
seb128https://launchpad.net/ubuntu/+source/unity/7.3.1+15.04.20150219.2-0ubuntu1 landed08:50
seb128do you have anything in your .cache/upstart/unity7.log08:50
seb128or unity-panel-service.log08:51
tsdgeosuntiy7 is not interesting08:51
tsdgeosthis is unity panel service http://paste.ubuntu.com/10321094/08:52
tsdgeosnot sure if interesting or not08:52
seb128Trevinho, ^ can you help there?08:54
tsdgeosactually it's weird08:57
tsdgeossince indicator time is running for example08:57
tsdgeosbut i can't see it08:57
seb128do you have any indicator showing or menus?08:57
tsdgeosthe title of the app08:58
tsdgeosand the [x] to close08:58
tsdgeosno idea about appmenu08:58
tsdgeossince it's kind of broken in qt5 apps08:58
tsdgeosbut probably not since firefox does not show me the menus either08:59
tsdgeoslet me reboot08:59
tsdgeosand see if it fixes anything08:59
larsuochosi, darkxst: what seb128 says. Unity always removes title bars for maximized windows, whereas gnome shell only does it when the application requests it (basically if it has window controls inside of its main toolbar)09:00
larsubut this has gone out of style anyway for csd09:00
larsuochosi: pinging upstream about it09:03
Laneymorning!09:04
larsumorning Laney!09:04
Laneyah pitti, you managed to get the bug?09:05
pittiLaney: yeah, I keep notes in the LP bug report09:06
Laneydo you remember what I said yesterday too?09:06
didrockshey Laney09:06
Laney19/02 18:15:00 <Laney> I removed BusName from polkitd.service and SystemdService from  /u/s/dbus-1/system-services/org.freedesktop.PolicyKit1.service and now I have lightdm again09:07
pittiLaney: it's a bit finicky to reproduce, but I now found a recipe that at least works on my laptop and in qemu09:07
pittiLaney: not everything, sorry; I got sidetracked by some other pings09:07
Laneyhopefully that wasn't a coincidence09:07
Laneyoh, maybe it was, now I have low graphics ^o)09:08
pittiLaney: do you use persistant journal?09:08
Laneyyep09:08
Laneywait09:09
pittiI have a hunch that this is related to the new ACL tmpfiles.d feature09:09
LaneyI'm getting confused between systems09:09
pittibut I'm currently bisecting the changes09:09
LaneyI need to check09:09
pittiI have four debs to test, then a couple of binaries, etc.09:09
LaneyI enabled it on this laptop, but that system → I just installed systemd-sysv and rebooted09:09
Laney(the one with the bug)09:09
Laneyno, no persistent journal there09:10
pittididrocks got it without persistant journal once, too, but it also applies ACLs to /run/systemd/journal/09:10
pittiso having a persistant journal is not "the" trigger, but it helps on my systems at least09:10
didrocksyeah, the ACL one is a good lead I guess09:10
didrockspitti: tell us if you need help, I'm almost done with my backlog09:10
tsdgeosseb128: a reboot "fixed" it btw09:12
tsdgeosi'll see if it happens again09:13
seb128tsdgeos, weird :-/09:13
seb128tsdgeos, k, let we know09:13
pittididrocks: can you reproduce it in a VM?09:13
* pitti getting diverted by another high urgency issue again, argh09:13
didrockspitti: I can give it a try, let me upgrade the VM to a more recent version09:15
pittididrocks: btw, I edited /etc/default/grub to drop splash quiet and added systemd.debug-shell09:18
pittithen sudo update-grub09:18
didrockspitti: ok, doing with that + persistent journal (but downloading a new iso for now)09:19
pittimeh, and now it stopped reproducing in vm09:20
pittihah, and it starts again when I do an sbuild in the background on my host, to slow it down again09:23
pittiah no, boot is just slower09:25
pittibummer09:25
mlankhorstargh, using /bin/bash ../configure gives different results than ../configure09:25
mlankhorstgiving the useless ../libtool: preserve_args+= --tag CC: not found09:26
larsuochosi: pushed to master. Thanks!09:31
=== hikiko-lpt is now known as hikiko
didrockspitti: tried multiple reboots without quiet splash, creating persistent logs and nothing…09:48
larsulet me know if you guys need help debugging09:49
didrockspitti: oh, however, my keyboard is now in qwerty, despite the indicator09:49
didrocksso, something fishy…09:49
didrocksLANG is right…09:50
didrocksand no LC_*09:50
didrocksloadkeys didn't work, and now, reboot and azerty…09:52
didrocksah, got it this time09:55
Laneydidrocks: did you get the bug?10:03
davmor2Hey guys on vivid desktop I can't update via software updater because of the extras repo is there any chance we can get them disabled if they are broken?10:04
LaneyI turned of systemd dbus activation for logind too and it's booted a few times okay now ...10:04
Laneyhi davmor2, do you mean upgrading from utopic?10:05
didrocksLaney: on qemu, once, on my system one as well (as said this morning ;))10:05
davmor2Laney: no fresh install10:05
Laneywhen did you install?10:05
willcookechange of plans, I will be here today10:06
davmor2Laney weekend10:06
Laneydidrocks: lot of backlog, didn't read it all ........10:06
didrockswillcooke: sorry man :/10:06
davmor2Laney: last Saturday infact10:06
Laneyit's supposed to not be enabled any more10:07
Laneyhttps://launchpad.net/ubuntu/+source/apt-setup/1:0.80ubuntu710:07
Laneytry a new daily to double check?10:07
willcookedidrocks, thanks :)  It's not so bad.  I figure I wont need to work over the weekend, which is probably the better idea10:08
davmor2Laney: hmmmm should that not of got installed via update too though or will it not over write the existing list?10:08
didrockswillcooke: heh, not untrue10:09
didrocksgrrrr, can't stop on shell-debug :/10:09
Laneydavmor2: what existing list?10:09
Laneythat's why I asked you if it was an upgrade10:09
davmor2Laney: only update from the fresh install on saturday10:09
LaneyI don't think anything will fix it within vivid10:10
Laneyonly for new installs and upgrades after the fixes went in10:10
didrockspitti: wait! I tried multiple reboots with upstart, and got one hang10:10
didrocksseb128: Laney ^10:10
pittididrocks: with upstart?10:11
Laneywith upstart?10:11
didrocksyeah10:11
Laneyumm10:11
davmor2Laney: right.  I'll do a fresh install later then and see if it is fixed in that install10:11
didrocksinit=/sbin/upstart10:11
Laneywhat are you suspecting?10:11
seb128different pb?10:11
didrocksdon't know, but we got also newer kernels and such10:11
didrockscan maybe be unrelated to systemd10:11
pittididrocks: where does it hang? I occasionally get graphics lockups when I boot without "quiet splash", but that's something else10:11
Laneyit worked when I downgraded systemd though10:11
seb128it works with upstart for me10:11
seb128hangs every time with systemd10:12
didrocksseb128: Laney: well, it works 12 times in a raw here10:12
didrockswith latest systemd10:12
didrocksso seems $random, maybe systemd trigger it more…10:12
didrockslet me retry other reboots with upstart10:12
Laneywell10:12
didrocksbut I got the exact same behavior10:13
seb128we need to get at the bottom of it on a system having the issye10:13
Laneyit's related to dbus service activation10:13
didrockshanging, then xfailsafe…10:13
Laneyfor me10:13
seb128trying to do random config boots and draw conclusions is not leading anywhere10:13
seb128it's not consistant enough to do that10:13
didrocksconfirming, hanging again, with upstart10:14
didrocks[   OK   ] on Started D-bus…10:14
Laneygo to a vt10:14
Laneysee if logind is running10:14
didrocksLaney: well, I'm unsure why my qemu doesn't enable me doing that10:14
didrocksI'm going to the qemu console10:14
didrocksuse sendkey…10:14
pittiI haven't yet managed to get a reliable reproducer either; when I want to test with a different deb, I never get it any more, and then I also don't get it any more with the vivid deb10:15
pittididrocks: alt+f9 works fine here in qemu (you need to grab the keyboard first)10:15
didrocksargh, it stopped being stalled after 60s and booted this time10:15
didrockspitti: alt+f9 doesn't work here (after grabbing the keyboard)10:17
didrocksok, hanging again10:17
Laneydo it in virt-manager, then you get a nice menu to send those keys10:17
didrocksStarted D-Bus system message bus10:18
didrocksand now unstall (I wasn't doing anything on my system)10:18
didrocksso maybe not the same thing, just a way slower boot10:18
seb128could be10:19
seb128if that was impacting upstart I'm surprised nobody else reported it10:19
seb128it's like 3 systemd users reported it10:19
seb128and 0 upstart users10:19
didrocksseb128: well, it boots in the end10:19
seb128and we probably have a lot more people on upstart than systemd10:19
didrocksjust hanging for a while10:19
seb128systemd doesn't boot at the end10:19
seb128plytmouth go away that's all10:19
seb128then you can get to a vt10:19
didrocksyeah, but the root cause might be the same?10:19
seb128but you never get lightdm10:19
seb128could be I guess10:20
seb128systemd just not recovering from it?10:20
Laneywell yes10:20
Laneybecause on systemd it breaks bus activation via systemd10:20
Laneyon upstart that probably doesn't happen10:20
pittiyeah, and if downgrading to 218-10ubuntu2 also helps (just the 4 systemd binaries), that's another strong indication that it's systemd specific10:20
Laneyah bah, I think I've heisenbugged it10:20
pittiin the debug log I see lots of "[system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out"10:20
seb128same here10:20
pittiyeah, same here (heisenbug)10:21
LaneyI just reverted the disable-systemd-bus-activation changes I did10:21
Laneyand it still boots10:21
Laneyhm, not the polkit one actually, lemme try that10:21
Laneykernel takes ages to init one of the drives :(10:23
Laneynah, it works now10:23
Laneyafter I've reverted all of the changes I made10:24
Laney:(10:24
didrocksLaney: told you, it's not 100%, maybe try multiple reboots as well?10:24
Laneyit was 100% before10:24
Laneythen it worked once and since then seems consistent10:24
Laneyoh hang on, I forgot one more service ;-)10:25
pittiLaney: I had a certain success with https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/310:27
ubot5Launchpad bug 1423811 in systemd (Ubuntu) "219-1ubuntu1 regression: boot hangs, logind fails" [Critical,In progress]10:27
pittis/certain/some/ I mean10:27
Laneypitti: I never had persistent journal, but can try enabling that10:27
pittijust to slow things down a bit; plus booting without quiet/splash and with debug10:27
didrocksrebooting in loop, nothing :/10:28
didrocksok, I can get sometimes this ~30s hang with systemd as well on the system dbus thingy10:30
didrocksbut then, get to lightdm10:30
didrocksand systemctl status shows all services succeeding…10:30
didrocksmaybe time for bootchart to see where it's waiting?10:31
Laneytrying with debug/no quiet/no splash10:35
Laneyno good10:36
Laney(in a world where 'good' is no good :P)10:36
didrockshum, init=/lib/systemd/systemd-bootchart triggers a kernel panic here10:37
didrockschecked twice, no typo…10:37
pittiattempted to kill init?10:38
didrocksyeah10:40
* pitti wonders how unhealthy http://paste.ubuntu.com/10322345/ is (polkit errors)10:42
pittididrocks: do you have busybox-static installed? if not, install it (could be bug 1421117)10:43
ubot5bug 1421117 in initramfs-tools (Ubuntu) "fails to boot with "Attempted to kill init" in VMWare, absolute /sbin/init symlink does not work" [Medium,In progress] https://launchpad.net/bugs/142111710:43
didrockspitti: ah thanks for the reference, doing10:43
didrockspitti: was already installed10:45
pittiok, need the error message then10:45
didrockspitti: the issue is that it can't open /run/log for writing10:48
didrocksopening output file "/run/log/bootchart-<timestamp>" : No such file or directory10:48
didrockslike https://bbs.archlinux.org/viewtopic.php?id=16601310:49
didrocksI doubt -i /lib/systemd/systemd would work, but let's see…10:50
didrockswaow it does10:51
pittididrocks: systemd-bootchart does have that option, you might need some quoting, i. e. init="... -i ..." ?10:51
didrockspitti: yeah, this works10:51
pittididrocks: ok, bug report SVP; I'll write an autopkgtest for bootchart10:51
willcookeseb128, do you know:  I want to have a new category in the u8 dash, where you can drop down for "All, Communicaton, Games" etc10:51
didrocksok, something else to consider, not sure why the default isn't taken10:51
didrockspitti: doing10:51
willcookeseb128, I want to create one called Productivity - is it easy?10:51
didrocksLaney: didn't you try to get a bootchart yesterday?10:52
pittididrocks: how can I disable failsafe-x? it messes up qemu10:53
pittiI added an ExecStartPre=/bin/sleep 1 to /lib/systemd/system/polkitd.service which seems to help10:53
pittididrocks: masking failsafe-x.service, I figure?10:55
didrockspitti: that or disabling the fallback, one sec10:55
didrockspitti: disable the target rather10:56
didrocksfailsafe-graphical.target10:56
didrocks(the target is what is isolated, so remove other services)10:57
didrockspitti: if that's not enough, maybe overriding graphical.target: /lib/systemd/system/graphical.target.d/xdiagnose.conf (this is where there is the OnFailure=failsafe-graphical.target)10:58
didrockspitti: btw: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/142386710:59
ubot5Launchpad bug 1423867 in systemd (Ubuntu) "init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on kvm" [Undecided,New]10:59
pittididrocks: confirmed, will look after that boot failure11:01
didrockspitti: grrrr, I can't get to any vt, I'm having the issue now :/11:01
pittidebug-shell11:01
didrocksah, send-key works now11:01
didrocksok, need to disable failsafe as well11:02
pittididrocks: masking failsafe-x WFM11:11
ochosilarsu: thanks a lot!11:11
ochosilarsu: btw, andrzejr (developer of xfce4-indicator-plugin) had some questions wrt libido and libindicator releases, because there haven't been any for a while11:12
didrockspitti: I guess the target is failing and so isolation on the target isn't called11:15
larsuochosi: we don't do traditional releases for those anymore, but import them to ubuntu directly11:19
ochosilarsu: yeah, i guess he noticed, the question was, are they intended for use within ubuntu only?11:20
ochosi(personally i get his request, because i think the indicators are great and shouldn't be limited to ubuntu. they work really well with other DEs like xfce too)11:21
larsuochosi: I consider them to be ubuntu-only, because I don't like giving any stability guarantees for them. Other people think otherwise though :)11:24
larsuochosi: in any case, tedg is the right guy to ask for releases11:25
ochosiah ok :)11:25
didrockspitti: ok, so during the hangs (that sometimes prevents to boot to graphical, sometimes don't), I can see: "systemd[1]: Failed to get initial list of names: Connection timed out"11:25
* ochosi will annoy tedg in that case11:25
larsu:)11:26
pittididrocks: hm, I don't see that in two failed cases11:26
darkxstochosi, nothing is ubuntu only, but the flavours have to put in some leg work in that case11:26
ochosilarsu: are there concrete plans for unity8 yet – i mean: will indicators break for other DEs with unity8?11:26
pittididrocks: just always the timeouts with activating the dbus services11:26
didrockspitti: I have 16 jobs starting… and stuck at that number (which I guess is due to the dbus activation)11:27
darkxstpitti, systemd exploded now?11:27
pittididrocks: I dropped the --no-debug from  polkitd.service11:27
pittidarkxst: yeah, it's a helluva bug :/11:27
pittididrocks: in succeeding cases polkitd starts up and mumbles some stuff, but in the timeout cases it appears to not even start11:27
pittididrocks: maybe the added sleep 1 helped a bit, but I get it more regularly now in VM11:28
didrocksurgh :/11:28
darkxstpitti, figured as much from the back log11:29
didrockspitti: journactl "systemd[1]: Looping too fast. Throttling execution a little/"11:29
larsuochosi: they work as they are with unity8 and I'm not aware of any concrete plans11:29
larsuochosi: I wouldn't bet on the design staying the same though11:30
larsuochosi: and I do have some non-concrete plans myself (which would totally change them), but I don't think I'll work on that11:30
darkxstlarsu, but teams can share, I think Ubuntu GNOME has proven that ;)11:31
larsudarkxst: ah, I thought he meant non-ubuntu-flavors as well11:31
larsudarkxst: share what?11:31
darkxstlarsu, ochosi is xubuntu?11:31
ochosiyup11:31
Trevinhotsdgeos: have you foxed your issues? Changes happened yesterday to indicators, so you need to make sure you reloaded everything properly11:31
darkxstlarsu, packages,11:31
tsdgeosTrevinho: i rebotted and it worked11:31
ochosidarkxst: only the project lead, not xubuntu as a whole though ;)11:32
darkxstlarsu, we have a huge overlap with -desktop11:32
larsudarkxst: I know, I thought this was about upstream, because why else would he care about releases?11:32
tsdgeosTrevinho: but when i found the issue i just had rebooted too11:32
tsdgeosTrevinho: so it's stading at 50% success/error at the moment since yesterday :D11:32
Trevinhotsdgeos: I see11:32
larsudarkxst: I know and I didn't say that was a bad thing!?11:32
darkxstlarsu, maybe I came into the convo late!11:32
larsudarkxst: haha okay :)11:32
ochosilarsu: i think the idea was to get indicators playing nicely on other distros and getting them packaged11:33
ochosilarsu: without releases that's rather hard11:33
larsuochosi: right. Talk to tedg about that. I would not recommmend it, but that's only me11:33
ochosiok, either way, good to know11:34
ochosithanks for the heads up11:34
larsuprobably it will be fine11:34
ochosilarsu: one more thing, will the evince patch find its way to ubuntu naturally or should/can i do anything about this?11:46
larsuochosi: will find its way naturally if you're fine with waiting until we get 3.16. Otherwise let's backport it11:49
ochosiright, would be good to have it in 15.04 for us11:51
ochosiit's a rather annoying bug in xubuntu, losing your window borders on a maximized window isn't very intuitive :)11:51
ochosican i do anything to help backporting?11:51
larsuright, if you want to help, make an MR with the patch for our evince package11:52
larsuand assign me or Laney as reviewer11:52
ochosiok, i'll try that11:52
didrockspitti: bah, going for a run, can't get any useful logs and as it's not reliably reproduceable…11:52
didrockspitti: I'm in a broken state in qemu right now, kept it like that11:52
ochosilarsu: i'm not that good at the patch/packaging stuff, but i'll do my best. to the worst you'll have to educate me and i'll learn something...11:52
pittididrocks: ack, enjoy! continuing to bisect here11:52
larsuochosi: a launchpad bug with one of us as assignee will work as well ;)11:52
ochosiheh, bugreport already exists11:53
larsuochosi: ha, I don't know much either. Laney is the pro11:53
ochosihttps://bugs.launchpad.net/ubuntu/+source/evince/+bug/142235411:53
ubot5Launchpad bug 1422354 in Evince "Show traditional titlebar when maximized with no GtkHeaderBar present" [Medium,New]11:53
didrockspitti: keep me posted once I'll be of any help. I'm going to run, let's see how my knees will handle :)11:53
larsuochosi: ah cool11:53
pittididrocks: you're starting with a short round, I hop?11:53
ochosilarsu: upstream bug already added to watch ofc11:53
Laneypitti: are you reliably reproducing it now?11:53
larsuochosi: cool. Do you want to try adding the patch? Otherwise I'll do it11:54
didrockspitti: it's the 3rd time, my physiologist told me to try 8kms + some cycling11:54
ochosilarsu: i can give it a shot11:54
didrockspitti: I'm sure I will run slowly though :/11:54
larsuochosi: cool! let me know if you run into trouble11:55
Laneyochosi: no chance to get it via evince 3.14?11:55
Laneyif not, yeah, we can totally backport it11:55
pittiLaney: no, not reliably, it's a lot of retries once I get to the broken state again11:55
ochosiLaney: it was applied in the 3.15 branch11:55
Laneyindeed, sometimes fixes are put into the stable branch too11:56
ochosioh, i wouldn't know. larsu?11:56
larsuLaney, ochosi: I hesitated to put onto stable for everyone because it _is_ a UI change11:59
larsuprobably one that everyone wants, but still11:59
larsuplease let's backport11:59
ochosibut it would only affect the !CSD folks, no?11:59
ochosieither way, i'm fine with whatever you guys say/prefer12:00
larsuochosi: right, it's a ui change for those folks12:00
larsucould be more trouble than it's worth, and it's an insanely small patch for us to carry12:00
ochosiagreed12:02
willcookeQuesiton for gtk people...  Inside XMir gtk applications (well xhchat)  have MASSIVE fonts.  I wonder, perhaps it's picking up funny settings from gsd running on the device?12:08
willcookecan I over ride them some how?12:08
larsuwillcooke: you can, but let's check whether that's the issue first. Do you have libgtk-3-dev installed?12:13
larsuwillcooke: open the inspector with Ctrl+D and select "GtkSettings" on the left side, and check what the value of "gtk-font-name" is12:13
larsusorry, Ctrl+Shift+D12:14
=== MacSlow is now known as MacSlow|lunch
willcookelarsu, bear in mind this is on a tablet, inside Xmir - will installing that break much?12:14
willcookelet me backup my stuff quickly...12:14
larsuwillcooke: oh. Shouldn't break anything, but I don't know if/how opening new windows works12:14
willcookeoki, installing12:15
willcookelarsu, ok, installed, ctrl-d doesnt do anything12:16
willcookectrl shift d doesnt either12:17
larsuwillcooke: Ctrl+Shift+D, sorry12:17
larsuoh. Weird.12:17
larsuseb128: does opening the inspector not work on xmir?12:17
willcookelarsu, I'm seeing this in the logs...12:18
willcookeIceWM: Warning: Could not load font "DejaVu Sans".12:18
willcookeIceWM: Warning: Could not load font "sans-serif:size=11".12:18
willcookeIceWM: xft: fallback from 'DejaVu Sans,sans-serif:size=11'12:18
willcookeIceWM: Warning: Could not load font "DejaVu Sans".12:18
willcookeIceWM: Warning: Could not load font "sans-serif:size=10:bold".12:18
willcookeIceWM: xft: fallback from 'DejaVu Sans,sans-serif:size=10:bold'12:18
willcookeSo I think it's trying to use ~ 11 point font12:18
willcookebut each letter is about an inch high12:18
willcookeI tried to create a .Xresources file with a lower dpi12:18
willcookedidnt help12:18
larsushouldn't it try the ubuntu font?12:19
larsumaybe g-s-d isn't set up correctly?12:19
* larsu doesn't know about the xmir setup, sorry12:19
larsuwillcooke: in any case, you can override xsettings in g-s-d by settings the org.gnome.settings-daemon.plugins.xsettings key12:20
larsugsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/font-name': <'ubuntu 10'> }"12:21
willcookelarsu, No such schema 'org.gnome.settings-daemon.plugins.xsettings'12:23
larsuwillcooke: so g-s-d is not installed...12:24
willcookeso that's why I'm getting these massive fonts?12:24
larsuor the xsettings plugin12:24
* willcooke install gsd12:24
willcookelarsu, do I need to tell it to start inside the Xmir session?12:25
larsuya12:27
willcookehahahaahahahah!!!!12:28
willcookeyaya12:28
willcookethanks larsu12:28
larsuwillcooke: I should probably look into our xmir setup a bit more to give better advice. Glad it works12:28
willcookelarsu, yah, we'll have to look in to this soon, but soon, not now :)12:29
ochosilarsu: wat, the ubuntu packaging docs told me to add the .pc folder and now the diff is totally screwed up :'( https://code.launchpad.net/~ochosi/evince/show_titlebar/+merge/25043612:31
Laneyflexiondotorg: hi, did you have an LP bug to close with the new gtk?12:31
flexiondotorgLaney, Sure. One sec.12:31
flexiondotorghttps://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/135189012:31
ubot5Launchpad bug 1351890 in ubuntu-mate "Changing external screen resolution with dual monitors" [Medium,Triaged]12:31
willcooke_phablehello desktoppes from Xchat running on the phablet12:32
popeyhello willcooke_phable12:32
willcooke_phablenow with normal sized fonts12:32
Laneyty12:32
flexiondotorgLaney, So 15.04 is using the new release of GTK2 or patching an old releasE?12:32
Laneyflexiondotorg: new one soon12:32
willcookehello willcooke_phable would you like some lunch now12:32
willcooke_phablewillcooke, yes, yes I would12:32
flexiondotorgLaney, Great.12:32
larsuwillcooke_phable: haha12:32
ochosiwillcooke_phable: hehe, your nick gave away the surprise ;)12:32
willcookeochosi, :D12:33
larsuochosi: I don't even know what that .pc directory does...12:33
larsuochosi: clearly the diff is wrong ;)12:33
ochosilarsu: yeah, sorry about that. blaim http://packaging.ubuntu.com12:34
ochosialso blame12:34
larsuochosi: never read that *cough*12:34
Laneyum yeah, don't add that12:34
ochosii would hope that the patch otherwise is ok, i even added the frickin DEP-3 header12:35
Laneyah right, we usually use lp:~ubuntu-desktop/evince/ubuntu not lp:ubuntu/evince12:35
LaneyI can sort that out. :)12:35
larsuLaney: thanks12:35
* larsu <-- clueless12:35
ochosiLaney: thanks a bunch12:35
ochosi<-- more clueless12:35
larsu*cluelesser?12:36
Laneythere's some kind of fail going on with this workflow12:36
ochosiLaney: ok, so just that i learn something here: 1) don't add the .pc folder 2) correct MR-destination 3) ..?12:36
Laneyif you bzr branch lp:~ubuntu-desktop/evince/ubuntu you get something which looks a bit different12:37
ochosiright, i guess i should've done that then, i branched lp:ubuntu/evince12:38
Laneyi.e. we only store the changes in debian/ and not the full source12:38
Laneyso .pc is not relevant for us12:38
willcooke_phablegood bye12:40
willcookewell, it was nice of him to drop in12:41
willcookewhat a great guy12:41
seb128willcooke, sorry, too much backlog, do you still need something?12:42
seb128IRC is crazy today12:42
willcookeseb128, erm....12:42
willcookeseb128, oh - maybe - I want to create a new category in the drop down from the apps scope "Productivity"12:42
willcookeseb128, I think I asked you this before, and it's non-trivial12:42
willcookeif so, care=zero12:43
seb128willcooke, oh, categories, I don't know exactly how that works, but part comes from the server since that's what provides the translations iirc12:45
willcookeseb128, kk - nw.  I wont worry about it then12:46
=== alan_g is now known as alan_g|lunch
=== MacSlow|lunch is now known as MacSlow
didrockspitti: any lead?13:50
pittididrocks: ça va ! comment était le cours ?13:50
pittididrocks: bisecting individual binaries now13:50
didrockspitti: la course était difficile, je cours lentement maintenant :p Sinon, quelques douleurs, mais globalement, ça allait13:51
didrockspitti: do you need any help? (Not sure how many reboots you are doing to qualify the bisection :))13:51
pittididrocks: I verified that current vivid and systemd+systemd-logind from 218 are FAIL13:52
pittididrocks: i. e. the regression is not in systemd or systemd-logind13:52
pittiI never got a failure with those two plus journald from 21813:53
pittiso I'm currently trying to get a failure with vivid and just journald from 21813:53
pittididrocks: and I keep leaving an sbuild -j4 on my host, to slow down things13:53
didrocksargh :/13:54
cyphermoxdidrocks: fwiw I didn't really get an issue that I noticed13:54
didrockspitti: so, you would need the contrary, systemd 218 + journald alone from 219?13:54
pittididrocks: to cross-check, yeah13:54
didrockscyphermox: yeah, it's pretty random, seems to happen more on heavy load13:54
didrockspitti: doing that13:54
cyphermoxthat would explain it, maybe13:54
* didrocks downloads the binary13:54
pittididrocks: do you now have a way to reproduce?13:54
=== alan_g|lunch is now known as alan_g
pittididrocks: I'm still doing the "reset /v/l/j, reinstall, swap binary, reboot a few times" approach13:55
didrockspitti: rebooting like crazy, sometimes I have a hang which unblocked after ~30s, sometimes it will hang as we discussed13:55
didrocksI don't do the reset /v/l/j13:55
pittididrocks: oh, and I think I still have the ExecStartPre=/bin/sleep 1 in polkitd.service13:55
didrocksthat helped triggering it for you, right?13:55
didrocks(the sleep)13:55
pittididrocks: a bit; hard to say13:56
didrockshappy to see we are all so clear about the issue :p13:56
pittididrocks: I didn't yet try to downgrade systemd-tmpfiles, btw (that's still on my "to check" list)13:57
didrocksoh right13:57
pittiat least if we cannot confirm journald to be the culprit13:57
didrockswell, let's me downgrade everything and upgrade13:57
didrocksyeah13:57
pittididrocks: I'm now running one VM with 219 and journald 218, and another VM with 218 and journald 219; no hangs on either so far..14:07
didrockspitti: \o/14:14
didrockspitti: when I was going to call bankrupcy on the journal after 30 successful boot, I just got a hang!14:15
didrocksso all systemd/udev and such on 218, but systemd-journald on 221914:15
didrocks219*14:15
pittididrocks: oh!14:15
* pitti feeds the hamsters harder then14:15
didrocksahah :)14:16
didrockstook 30 boots here14:16
pittididrocks: did you wait long enough to make sure it's really the same issue? i. e. you get into the loop of "restart services"?14:16
pittididrocks: yay, got it too now!14:17
didrockspitti: yeah, same states, with queued jobs14:17
didrocksnice to know at least which component is guilty :p14:17
pittiok, so it's not the tmpfile ACL either, good!14:17
* pitti records that in the bug14:17
didrocksnice that you confirmed with 218 + journald from 21914:18
pittididrocks: hm, I had bet on logind, but I disproved this already14:20
pittilogind hanging/crashing polkit, everything else needing logind or polkit, would have made sense14:21
pittididrocks: but journald makes it more plausible why I can trigger it with various-sized persistant journals :)14:21
pittididrocks: do you have time for another test?14:22
didrockspitti: sure14:22
pittididrocks: I wonder if ForwardToSyslog=no makes a difference14:22
pittialthough, hold that thought14:22
* didrocks was looking at "git log v218..v219 src/journal" just in case14:22
pittiyeah, that would have been my next thingy14:23
didrocksah14:23
pittididrocks: so we should be able to use journalctl from upstream trunk with explicitly setting ForwardToSyslog=yes in journald.conf14:23
didrockslet me try to disable syslog forwarding then14:23
didrocksyeah14:23
pittididrocks: wait, that might not be the cheapest next step14:23
didrockshum?14:23
pittididrocks: might be better to split the bisecting into two halves?14:24
didrocksnot sure to follow you, you want to bisect the whole repo between the 2 tags?14:24
pittididrocks: for src/journal14:25
pittididrocks: well, first read all changes to see which could be plausible candidates14:25
didrocksyeah14:25
pittididrocks: ok, let's do that then, and maybe split the candidates between us?14:25
didrockswell, if the change is in src/journal14:25
didrocksnot in the share/static libs14:25
didrockssounds good to me :)14:25
pittiah yeah :/14:26
didrockspitti: we did include the acl capabilities before 219, right?14:31
didrocks(as the acl support is unconditional now)14:31
didrockswell, there is the large commit on restarting the journal without loosing stream connexions, but I doubt the journal is restarting in this boot or shouldn't…14:35
didrocks(13790add4bf648fed816361794d8277a75253410)14:35
pittididrocks: yes; just that 218 didn't have the tmpfiles.d ACL support, and /{run,var}/log/journal didn't get ACLs for group adm assigned14:37
didrocksok14:37
willcookeSweet5hark, when I open Writer in one DISPLAY and I try to open Calc in a different one, LO actually converts the Writer instance in to a calc instance.  Can I tell LO not to do that - to start a whole new process instead?14:38
pittididrocks: I sent a message to the upstream ML as a heads-up14:38
didrocksgood idea14:39
didrockspitti: saw Michael's answer?14:42
didrocksah, you are speaking on #debian-systemd :)14:42
* Laney goes to lurk in there15:05
=== ubuntu is now known as Guest76382
pittididrocks: back from meeting16:50
* pitti feels burned out, needs to go buy some groceries, and it's been too long a week anyway, so I guess I'll resume the systemd madness on Monday16:50
* Laney hugs pitti 16:51
didrockspitti: yeah, I doubt we'll dig deeper now16:51
Laneygood investigating16:51
didrockspitti: c'est l'heure de la glace :)16:51
didrockset du week-end!16:51
pittididrocks: did you try reverting/bisecting anything else? (just for keeping notes)16:54
didrockspitti: no, I did backlog on what I planned for Ubuntu Make, started to be burnt out as well with this number of testing/reboots. So I guess we'll have to bisect the whole tree on Monday16:56
pittiack16:56
* didrocks waves good evening and good week-end to everyone :)17:02
seb128didrocks, bye17:02
didrockssee you seb128!17:02
desrtattente_: did you know that '(int) item' works on GVariant?18:10
desrtevil, but true18:10
attente_no18:11
desrtthanks for that vala bug, btw.  very well-explained.18:11
attente_oh18:11
phablet_demowillcooke, uiuouoiu18:23
Laneyhappy weekend!18:25
Laneyhello phablet!18:25
phablet_democya Laney18:29
qenghoLater, L.18:29
qenghokenvandine: are you on vivid on that high-dpi laptop?18:30
kenvandineqengho, yeah, vivid18:31
qenghokenvandine: there's a chromium landing in the PPA I mentioned that I would like you to try over the weekend. It's not downloadable yet, but I don't want you to disappear before I tell you.18:32
qenghokenvandine: Should be ready in the next 30 minutes.18:32
kenvandineqengho, sweet... can do!18:33
NoskcajLaney, Should we be updating glibmm to match the glib2.0 updates?22:06
andrzejrochosi, larsu, xfce4-indicator-plugin is using private (unreleased) API of libindicator - I have no problem with that as this plugin is only intended for xubuntu only. Especially users that install xubuntu-desktop on top of Ubuntu and want to use familiar indicators.22:27
ochositedg: ^22:27
tedgWhich symbol is private that's being used?22:29
* tedg might be missing some context here22:30
andrzejrtedg, sorry, I meant the API used by the plugin is not in a released version of libindicator. Mostly because the method of starting indicators has been changed ~2 years ago.22:31
tedgandrzejr, I'm still confused, which version is it in?22:33
tedglibindicator doesn't deal with starting indicators22:33
tedgIt's just the plugin ABI really.22:33
andrzejrtedg, libindicator/indicator-ng.h is not yet released22:34
tedgandrzejr, By "released" do you mean "in a tarball" ? We're not really building tarballs anymore.22:35
andrzejrI noticed that. This is why I'm here to find out if that is simply an omission or if these libraries are intended for Ubuntu only22:37
tedgandrzejr, I wouldn't describe them as "Ubuntu only" but I'm not sure anyone else has them.22:38
tedgThey're free software, anyone can download and build it.22:38
andrzejrAs I mentioned, this is not a problem for xfce4-indicator-plugin (written deliberately for xubuntu). But it means I cannot depend on other libraries (like IDO) for distro-independent code (like xfce4-pulseaudio-plugin).22:40
andrzejrthank you for clarification, btw22:40
tedgandrzejr, Sure, on the other side you might just want to cut-and-paste from IDO. Realistically GTK+ isn't our focus right now, I doubt it'll change much.22:41
andrzejrtedg, that is something I was considering as a fallback. I agree that this may be a good solution.22:44

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