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