=== tmpRAOF is now known as RAOF [06:08] good morning [06:18] bonjour didrocks [06:20] hey pitti [06:21] * pitti pulls his hair out on the racy systemddm tests [06:22] pitti: do you have the journalctl order? [06:22] would be interesting to see the boot ordering, at least, if it's been run [06:23] I wonder why it became racy suddenly… [06:23] I mean I get the self.assertTrue(self.is_active_unit('systemddm')) failure pretty much always in jenkins, but almost no time when I run it manually [06:23] I'll try to get a journal the next time it happens [06:24] but it's just a matter of waiting a bit longer AFAICS [06:24] with the "wait for job-list to be empty", right? [06:25] yes [06:26] and no "activating" jobs any more [06:26] crazyness… [06:26] hey didrocks pitti desktopers [06:26] hey seb128 [06:27] bonjour seb128, ça va ? [06:27] pitti, oui, très bien, et toi ? [06:28] je vais bien aussi, merci ! [06:30] Apr 08 06:29:25 autopkgtest systemd[1]: start request repeated too quickly for systemddm.service [06:30] didrocks: ^ could it be that? [06:31] pitti: oh, that shouldn't happen, interesting… [06:31] let me look at systemddm [06:31] morning! [06:32] pitti: so, it can be the qemu issue [06:32] pitti: see create_systemd_dm_unit(), I'm copying the lightdm.service [06:32] removing the Bus= line (as it won't match) [06:32] pitti: but that's what is used in all tests [06:34] didrocks: no, I mean could this be triggered simply by the fact that the tests start/stop systemddm very often? [06:34] pitti: oh, you removed the 2s… [06:34] didrocks: before it says "systemddm.service holdoff time over, scheduling restart." [06:34] so yeah, we maybe burst the limit [06:34] ah, then I'll put that back [06:35] pitti: good catch! [06:35] that or removing the limit in the .service file [06:35] didrocks: right, I get that by manual systemctl stop/start too [06:36] pitti: so StartLimitBurst=42? [06:38] didrocks: I'll try setting DefaultStartLimit* in /run/systemd/system.conf.d/autopkgtest.conf [06:40] pitti: hum, impacting all tests? Do you think it's not a trap for future-tests? [06:41] didrocks: ah, you mean only add that to systemddm.service? [06:41] pitti: yeah, seems safer to me? [06:42] in the create_systemd_dm_unit() method [06:42] didrocks: I was concerned it would also affect lightdm.service, but it actually hasn't so far [06:42] pitti: actually, systemddm.service is the service that is the most activated in the tests [06:42] that's why others are not impacted I guess [06:43] didrocks: hm, can I append something with that fileinput iterator? [06:43] ah, I'll append it after [Service] [06:44] pitti: I was going to propose that [06:44] if (line == "[Service]"): [06:44] print(line) [06:44] print("StartBurst…") [06:46] didrocks: right, I tried that, with burst=1 and limit=30, but that still doesn't reproduce it [06:47] didrocks: might actually be easier to call systemctl reset-failed during the "reload stuff" [06:48] pitti: makes sense, and even better [06:52] didrocks: hm, that line mangling doesn't work for me, but anyway, I'll try the reset-failed [06:54] * pitti -> errand, bbl [07:43] morning all [07:44] morning willcooke [07:45] hey happyaron - how's it going? [07:45] great, releasing new version of sogoupinyin atm [07:46] awesome! [07:47] hey willcooke happyaron [07:48] good morning willcooke, happyaron [07:48] hey seb128 [07:48] didrocks: morning :) [07:48] willcooke, I read the meeting log yesterday, you didn't get my email with my weekly summary? :-/ [07:48] I sent it in the morning in case I was not around [07:48] in reply to the weekly email reminder [07:54] hey seb128, erm, yeah - I'd marked it as read and then it vanished off my radar. Sorry about that [07:55] willcooke, no worry [08:03] yo [08:03] howdy Laney! [08:06] hey Laney! [08:06] hello my pals from across a bit of water [08:06] how is it going? [08:08] Laney, you're talking about Grafham Water right? In which case, I'm fine! [08:09] that place will forever be about school trips to me [08:09] :D [08:09] Very boring bike rides for me [08:10] I remember being shown around a sewage treatment plant there one time [08:10] it was a good life [08:10] When I used to do IT support for Anglian Water I went to *that* sewage works. For reals, no foolin [08:11] That's the kind of crash you don't want to have ... [08:11] :D [09:00] larsu, did you open a bug about the greeter/hidpi/bg flicker issue? [09:01] Laney, not sure if you saw me mentioning the new cairo the other day, unsure if that's an update worth getting in vivid still? maybe you want to have a look to it? ;-) [09:01] Yeah I have it on a list [09:02] great, thanks [09:03] seb128: I did not, because there are already some that go in that direction. I did however forget to ping robert_ancell. Thanks for reminding me [09:03] larsu, yw [09:03] larsu, I think I'm just going to disable the scaling on the greeter for vivid [09:03] there is still the menus issue also which is unfixed [09:03] darkxst, Laney, https://launchpadlibrarian.net/201946184/adwaita-icon-theme_3.14.0-2ubuntu7co1.diff might be for you (it's in the sponsoring queue) [09:03] seb128: ok. I won't bother robert then until the sprint [09:04] needs some discussion anyway [09:04] larsu, k, makes sense [09:06] seb128: ya, I have cairo written down [09:06] & will look at that other one, thx [09:07] Laney, you already replied 5 minutes ago, but thanks :-) [09:07] did I? [09:07] Yeah I have it on a list [09:07] must have been dreaming [09:07] I was about to say... [09:07] at least I said the same thing both times [09:07] but then didn't in case I misread something again [09:07] lol [09:07] Laney: getting old? [09:07] irc, bug report, two man pages, staring out of the window at the sunny day [09:08] too many inputs [09:08] those damn windows [09:08] wonder if we get some of those in the sprint hotel this time [09:08] we can go work in hyde park if not [09:09] under the rain? [09:09] how's the weather in england? [09:09] I vote for a boat on the lake in Hyde Park [09:09] they have roofs on their boats right? [09:09] larsu, right now - it's bloomi' lovely [09:09] or you just end up being between 2 layers of water? [09:09] * seb128 stops mocking the british weather [09:09] You can only get so wet, right? [09:10] so can my laptop [09:21] Laney: so vila also has a machine with a missing /etc/rcS.d/*networking link; I'm beginning to suspect some ancient upgrade bug here [09:21] Laney: I asked other reporters in bug 1430675 to check for this [09:21] bug 1430675 in systemd (Ubuntu) "fails to set up a bridged network interface" [High,Incomplete] https://launchpad.net/bugs/1430675 [09:21] Laney: but I think it might not hurt to upload an ifupdown which re-creates the symlink if it's entirely missing [09:22] Laney: update-rc.d disable will create a K??networking symlink instead, so we can tell apart that case and not break that [09:29] pitti: You mean if there's no /etc/rcS.d/K??networking then re-enable the service? [09:29] seb128, I still need to apply for -desktop, for these things I guess [09:30] Laney: yes; i. e. if there is no rcS.d/*networking at all [09:31] Laney: at least for vila it happend around the upgrade to trusty, but apparently was hidden by the /etc/init/networking.conf upstart job [09:31] or we add a proper networking systemd unit [09:32] pitti: haaaa, that's what made it work with upstart, thanks, was wondering... [09:33] I guess applying a hammer would be reasonable [09:33] seb128, that said the diff makes sense, since probably files moved from gnome-themes into adwaita-icon-theme [09:36] darkxst, right [09:40] seb128, so +1 from me, just can't actually sponsor it [09:40] darkxst, noted, thanks, I think Laney was looking at uploading it [09:40] ya [10:10] Laney: uploaded ifupdown with that hack now, FYI [10:19] pitti: thanks, hopefully someone didn't fix it manually & can verify [10:20] Laney: I removed the symlink here and tested the upgrade in both cases [10:42] Confirmation that there is a "do" on in the office on release day evening. [10:42] popey, are you in the office on release day? Perhaps we could arrange a meet up at a pub with community guys? (There's probably already something planned?) [10:42] I am [10:42] woot [10:42] There always was in the past a release party [10:42] but interest wained [10:43] and people wanted different things [10:43] I say a pub and a few jars [10:43] office people wanted a typical noisy london bar to unwind in, whereas community people actually wanted to chat to people [10:43] let's arrange something [10:43] willcooke: speak to msm and cvd [10:44] cvd has a thing on that week which finishes on thurs, she talked to me yesterday about beer and pizza for her dept in the office [10:44] just spoke to cvd, hence confirmation of an office event - but I'm thinking of some beers outside the office for an all inclusive thing [10:44] I'd be up for us nominating a pu to be in [10:44] +1 [10:44] *Pub [10:45] popey, I'll start a thread on the UK mailing list [10:45] nice one. [10:45] pick a nice real ale pub pleases [10:46] :-) [10:46] * willcooke googles [10:46] * Laney goes to get the tome [10:46] GBG 2015 [10:46] \o/ [10:46] There's a Brewdog place which is supposed to be good - but might be a bit hoppy for "brown beer" fans# [10:50] +1 to fartybeer [10:53] sheaf or old king's head [10:53] Laney, you're on the Ubuntu UK mailing list right? [10:53] in the vicinity of london bridge anyhow [10:53] ya [10:54] oki, just sending an email to that list, if you'd like to pitch in there? [10:55] 'kay [10:55] thx === benonsoftware is now known as clockwork === clockwork is now known as benonsoftware === tmpRAOF is now known as RAOF === MacSlow is now known as MacSlow|lunch === alan_g is now known as alan_g|lunch === alan_g|lunch is now known as alan_g [13:20] good morning, desktopanoj [13:20] hey desrt [13:20] hihi [13:21] seb128: did you try testing that patch on the bug? [13:21] desrt, no, since teuf commented saying it doesn't work for him [13:22] * desrt has one negative feedback so far but suspects that maybe it was tested wrong [13:22] I can if you want though [13:22] let me ping teuf first and see what his exact case is [13:22] maybe there's something i missed [13:22] is it still possible to uninstall systemd on vivid and have a working system? [13:22] or have we passed the point of no return? [13:22] popey, yes, you can keep using upstart, that's what ubuntu touch is doing [13:23] ok, thanks [13:24] removing systemd complains... policykit-1 : Depends: libpam-systemd but it is not going to be installed [13:24] didrocks or pitti might know about that [13:24] I have a bug and the current suspect is systemd, wanted to remove it as a quick test to confirm that [13:25] * ogra_ isnt so sure about bein able to remove it on desktop ... [13:25] well, at least you can use a different init system [13:25] not sure about uninstalling either [13:25] we draw a trick on touch to keep it out of the image ... removing it on desktop would remove ubuntu-standard at least [13:26] popey: no, you can boot with upstart a single time or permanently (upstart-sysv), that's going to be supported until 16.04 at least [13:26] and has propbably dependency issues in packages the phone doesnt ship [13:26] popey: you can't remove systemd; you can remove systemd-sysv and replace it with upstart-sysv [13:26] popey: but we need logind and other bits from that package [13:27] great, thanks === MacSlow|lunch is now known as MacSlow [13:50] Laney, larsu, does https://code.launchpad.net/~seb128/unity-settings-daemon/dont-scale-greeter/+merge/255512 looks fine to you? [13:51] seb128: there's XDG_SESSION_CLASS? [13:51] it's not set on my desktop — but I guess it is on the greeter? [13:51] larsu, I did start a greeter and string /proc/pidof greeter/environ [13:51] wait, two lines up, we don't scale on unity either? [13:52] larsu, if you find a better variable let me know [13:52] not sure [13:52] larsu, right, unity7 handle the scaling factor itself in unity [13:52] ah, right [13:52] we use that fallback for the installer [13:52] looks good to me if that env var exists [13:52] it does for me [13:52] I might ask you to test on your laptop once it's a silo ppa [13:52] ok, please let me know [13:53] thanks [13:57] seb128: testing appreciated [13:57] looks like teuf's setup was indeed a bit messed up [13:57] desrt, k [13:58] the patch may not be perfect yet, but it will probably work in most cases that we care about [13:59] in fact, i just reproduced his problem -- but it's oddly specific, and perhaps completely unrelated [13:59] oh. you're in #gtk+. i'll stop the play-by-play :p [14:05] Noskcaj, Laney: am I ok to upload gnome-keyring 3.15.92 for a fix blocking logout? [14:07] Riddell: If you upload 3.16.0, yes. :) [14:07] Riddell, bonus point if you upload the new stable 3.16 or find somebody wanting to do that [14:09] oh 3.15 is unstable? [14:09] yes [14:09] odd/even version scheme [14:10] so how come it isn't uploaded already? don't you have an automated/scripted way to update them all? [14:13] well, it's semi automatic, but you want an human verification, especially after beta [14:13] you guys just get script throwing updates in the archive? [14:14] alas not quite yet but we have it all buliding continuously and we have weekly isos from that to test http://kci.pangea.pub/ [14:15] but still needs to get that connected with the "make tars" step and the "package tars" step [14:22] cyphermox, hey, do you think you could maybe review https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1248720? [14:22] Ubuntu bug 1248720 in gnome-control-center (Ubuntu) "Bluetooth ON/OFF button switches OFF automatically" [Medium,Confirmed] [14:22] ok [14:23] cyphermox, thanks :-) [14:50] seb128: is it a know issue that sometimes notify-osd won't disappear? [14:50] cyphermox, do you have your cursor over it? [14:50] no [14:50] just get a second mouse and keep one over it :P [14:51] sounds like a less optimal plan than killall notify-osd ;) [14:51] * ogra_ is full of helpful tips today :D [14:51] cyphermox, not know then [14:51] ok [14:51] I'll report it with a video of the screen as soon as I get it again [14:51] it seems to happen often when I get pinged [14:52] cyphermox, are you sure you client is not buggy and keep refreshing the notification or something? [14:52] well, it's a possibility but it usually does work properly [14:52] cyphermox, check the dbus activity to make sure [14:52] cool, will do [15:07] larsu, can you try the debs from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+build/7308452 and see if your desktop is still scaled but the greeter not/if that resolve the flickering issue at login [15:09] seb128: on the phone, will try ion a bit [15:09] larsu, no hurry, thanks [15:22] qengho, https://plus.google.com/+FrancoisBeaufort/posts/gymYoHEeQUN [15:22] \o/ [15:22] (via didrocks, thanks) [15:23] Yep, we don't have to wait 12 weeks. Already backported to stable. [15:23] nice! [15:24] woo! rock on [15:24] qengho, that means it's going to be in vivid? [15:25] Yes. [15:25] desrt, that patch fixes the apport issue [15:25] desrt, it's used instead of gedit [15:26] desrt, commented on the bug to say so [15:30] cool [15:30] am still looking into the teuf problem [15:30] (in fairness, this fixes his issue too -- but he has another issue that he accidentally uncovered) [15:30] btw: that patch has a leak in it, so don't distro-patch it or anything :) [15:38] yeah, I read that [15:39] Riddell, thanks for the gnome-keyring update :-) [15:42] seb128: well we'll just see if the tests pass! === hikiko__ is now known as hikiko [16:10] Trevinho: hey, my apps lens isn't working in unity7, does it have a log file I could look into? Or where could I start to learn why? [16:10] greyback: it generally happens when the lens crashes [16:11] greyback: killing unity-scope-home and loader generally fixes it... [16:11] as for the log.... [16:11] Trevinho: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope [16:11] /usr/bin/unity-scope-loader: error while loading shared libraries: libunity.so.9: cannot open shared object file: No such file or directory [16:11] doesn't look right to me... [16:11] not much, as these are loaded by unity via dbus calls, but... [16:12] oh, right [16:13] Trevinho: should that work? I have libunity9 installed [16:13] greyback: make sure it's all installed and in right paths... [16:13] ldd /usr/bin/unity-scope-loader will fail, I guess [16:14] Trevinho: indeed, libunity.so.9 not found. but it in /usr/lib/x86_64-linux-gnu [16:15] oh, other libs are picked from that path I guess... === pat__ is now known as pmcgowan [16:15] so, mhmh, maybe it's a broken link? [16:16] lrwxrwxrwx 1 root root 17 Aug 8 2014 /usr/lib/x86_64-linux-gnu/libunity.so -> libunity.so.9.0.2 [16:16] lrwxrwxrwx 1 root root 17 Oct 29 20:49 /usr/lib/x86_64-linux-gnu/libunity.so.9 -> libunity.so.9.0.2 [16:16] -rw-r--r-- 1 root root 670296 Aug 8 2014 /usr/lib/x86_64-linux-gnu/libunity.so.9.0.2 [16:16] nothing looks wrong, /me scratches head [16:16] try to ldd on the binary? [16:17] I just reinstalled libunity9, now it works [16:17] the classic way :D [16:18] only change I see is date: 17 Oct 29 20:49 -> Aug 8 2014 [16:18] md5sum also, I guess... [16:19] too late [16:19] * greyback hopes his ssd is ok [16:23] seb128: ok it passed tests, now you can thank me :) [16:25] Riddell, thanks! :-) [16:25] seb128: I can't install that ("installing unity-settings-daemon would break unity") [16:25] deconfiguration is not permitted (--auto-deconfigure might help) [16:25] larsu, ?! [16:25] larsu, can you pastebin the full log? [16:26] seb128: hm, I made a typo passing auto-deconfigure before. Seems to have worked now [16:27] larsu, why did you need to use that option at all?! [16:27] I don't know :) [16:27] do you still have the log? [16:28] just rebooted [16:28] but this was the only message [16:28] k, weird [16:28] when installing unity-settings-daemon woth dpkg -i [16:28] maybe your previous dist-upgrade had issues or something [16:28] ok. set scale factor in displays or somewhere else? [16:28] no [16:28] things should just work normally [16:28] no? [16:28] e.g boot should give you a non-scaled greeter [16:28] I'm not running scaled right now [16:29] you shouldn't have flickering on login [16:29] then desktop should be hidpi scaled [16:29] but I need to set that [16:29] because I usually don't [16:29] I though your laptop was hidpi? [16:29] I run it natively :) [16:29] well, I was more interested if it fixes your greeter/login flicker issue [16:29] that was scaled before that update right? [16:29] yes, greeter is native and no flickering [16:29] k [16:30] maybe try a guest session and see if that's scaled? [16:30] but that scaling factor is set by unity so it should work [16:30] guest session is not scaled [16:31] but setting scale factor for my session works [16:31] hum :-/ [16:31] k, I guess it's another issue/not new [16:31] larsu, thanks [16:31] might be just under the treshold at 2880? [16:31] right [16:32] anyway seems to work. thanks seb128! [16:32] larsu, thanks for testing! [16:42] * willcooke -> EODish. Will probably be back later [16:43] willcooke, have fun! === alan_g is now known as alan_g|EOD [18:36] cyphermox: have you got a moment to help me debug something that I think is nm related? [18:42] cyphermox: it's a trap run you fool ;) [18:43] I'm already debugging NM, what's one more data point :) [18:48] cyphermox: bug 1441053 [18:48] bug 1441053 in network-manager (Ubuntu) "Two network adapters on same LAN causes 30s drop-outs" [Undecided,New] https://launchpad.net/bugs/1441053 [18:49] basically my network drops for ~20-30s every minute while I have wired and wifi connected. Disconnect wifi, and use wired only, it's fine. [18:49] popey: reminds me of 1436330 [18:49] ooh [18:49] it could be that [18:50] its driving me potty [18:51] cyphermox: yeah I think the nm in vivid has some issues, the kind that would get a man put in a padded cell with a jacket that fastens at the back ;) [18:56] ooh, there's a patch there [18:59] 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 [18:59] 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 [18:59] looks plausible. same metric for both interfaces [19:07] that one is on my list too, but is very not easy to fix [20:06] cyphermox: my pet bug is bug #1422096 if that's not on your list (or is maybe a dupe) :-) [20:06] bug 1422096 in network-manager (Ubuntu) "Occasionally no network on resume" [Undecided,New] https://launchpad.net/bugs/1422096 [20:06] I only know how to restart n-m to fix it which is scary because about 10% of the time that locks up my machine [20:06] russian roulette [20:06] :) [20:06] * cyphermox weeps [20:07] heh, the fact that it sees there is a lxc bridge and whatnot shouldn't be affecting attempts to connect to wifi [20:09] could file it upstream and/or try a snapshot if you want [20:12] yeah maybe file it upstream [20:12] I also see something suspicious here, but I'm busy with other bugs [20:12] also I'm not on 10.1 yet [20:13] & ubuntu2 has a fix to hide these devices [20:13] lemme dist-upgrade and see what happens [20:13] although that's applet so I don't know how much will ... [20:17] could this wifi BE any slower?