[02:31] <attente> robru, thanks for the postcard :)
[03:43] <robru> attente, wow, did you just get it now? i sent that weeks ago! ;-)
[03:44] <attente> robru, i was in china and only arrived back yesterday :)
[03:45] <robru> attente, ahhhhh, that makes sense. welcome back!
[03:46] <attente> are the red hat offices the tallest buildings in brno?
[03:47] <robru> attente, almost, but not really. there's some churchy-fortressy-towery things that aren't really visible in that shot.
[03:47] <robru> attente, it's a really small town, same population as victoria (300k)
[03:48] <attente> robru, ah, ok
[04:29] <Mirv> hmm, I wonder why jenkins complains autopilot machines would be offline while I can reach them via the jenkins machine
[04:54] <Mirv> poof, solved
[04:58] <Mirv> and now someone rebooted nvidia machine and it wasn't me :P
[07:15] <sil2100> Mirv: morning! I see qtubuntu FTBFS in platform
[07:16] <Mirv> sil2100: morning! so do I.
[07:18] <Mirv> sil2100: but the worse thing is those 'lxc cannot start' things that seem to happen in check phases. I've been waiting now for this newest tick after fixing the autopilot machines, if anything changes regarding those.
[07:28] <Mirv> sil2100: have you seen the sort of http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1624/label=autopilot-intel/console before?
[07:28] <Mirv> I don't know what caused the autopilot problem I fixed, and I don't know what's causing this one
[07:38] <sil2100> Mirv: hm, maybe these are my delusions, but I think I saw that before - jibel fixed that last time IIRC
[07:40] <Mirv> sil2100: ok, that's a good hint at least.. I think he should be soon up so we can ping him
[08:03] <Laney> morning!
[08:05] <highvoltage> morning Laney
[08:07] <seb128> good morning desktopers
[08:08]  * Laney gets zapped by highvoltage 
[08:08] <seb128> hey Laney highvoltage
[08:08] <Laney> hi seb128
[08:08] <Laney> good weekends?
[08:08] <seb128> yes, mostly avoided the rain during the day (it rained quite a lot during nights though)
[08:08] <seb128> you?
[08:08] <Laney> yep, climbing shopping beer
[08:09]  * highvoltage is strongly considering taking a beer brewing class next weekend
[08:09] <Laney> mmm, I did some kits last year
[08:09] <Laney> need to buy some more equipment
[08:09] <seb128> did you get anything drinkable? ;-)
[08:10] <Laney> kirkland's posts make me jealous
[08:10] <Laney> well... you could drink it and it tasted like beer
[08:10] <Laney> but possibly the most boring beer ever
[08:10] <seb128> haha
[08:10] <highvoltage> heh
[08:12]  * Laney stabs the pandaboard
[08:14]  * highvoltage is tempted to get this: https://twitter.com/linuxfoundation/status/374955050642067456/photo/1
[08:14] <highvoltage> (but I'm slightly scared that it will pile up with all my other toy electronics that I never get a chance to play with)
[08:15] <Laney> nice
[08:57] <seb128> shrug
[08:57] <seb128> sil2100, Mirv: how come we didn't get any setting landing for 5 days? :-(
[08:58] <seb128> indicators as well?
[08:58] <Mirv> seb128: we're in manual publishing mode as ordered by asac, until unity8/mir lands today
[08:59] <mlankhorst> morning
[08:59] <seb128> asac, do we really need to block settings from landing? we have quite some changes/work that's blocked for almost a week there :/
[08:59] <mlankhorst> Laney: I've had a biker tailing ME last week :L
[08:59] <Laney> \o/
[08:59] <Laney> were you going fast?
[08:59] <mlankhorst> faster than him, i tried to stay behind him at first and wasn't patient enough
[09:00] <seb128> sil2100, Mirv: quite some red also in the stack, 8 red ones (and 3 yellow)
[09:00] <seb128> sil2100, Mirv: didrocks is back today right? I guess he's going to get unhappy :/
[09:01] <Mirv> seb128: on Saturday autopilot machines jenkins connection had broken down. I managed to fix it this morning. now lxc containers refuse to start up for the check phases, sil2100 suspected jibel could be able to fix those.
[09:03] <seb128> Mirv, shrug, QA team is having a week in Lexington so I guess he's not going to be around before a while ... are we stucked until he's there?
[09:04] <seb128> is sil2100 around today?
[09:05] <Mirv> seb128: we're stuck unless someone can decipher and fix this http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1624/label=autopilot-intel/console . sil2100 was around two hours ago
[09:05] <Mirv> 1.5h, to be more exact
[09:09] <seb128> k
[09:09] <seb128> it's going to be one of those days...
[09:10] <seb128> Mirv, thanks for the email, can you maybe follow up on the list as well to let people know landings are blocked?
[09:11] <Mirv> seb128: ok, which list specifically?
[09:12] <asac> seb128: Mirv: hi
[09:12] <seb128> Mirv, I though the previous outrages were mentioned on some lists, but I can't find it now... ignore that I guess
[09:13] <seb128> asac, hey! good morning? are you in Lexington? (if so it's quite early!)
[09:13] <Laney> They were mentioned internally IIRC
[09:13] <Mirv> seb128: yeah ue-leads etc, I just think since everything is blocked _anyhow_ because of the unity8/mir landing, it's not yet that urgent
[09:13] <Laney> Don't see why it couldn't be done on ubuntu-devel however
[09:13] <asac> seb128: whats the risk of settings landing? seems that folks worked all weekend to get us to a green dashboard :)
[09:13] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/4094/
[09:13] <Mirv> builds are building, they are just not getting released
[09:13] <asac> seb128: yeah i am in lexington :)
[09:13] <asac> early bird
[09:13] <Laney> the power of jetlag
[09:15] <marga> Hey, there's a tzdata issue that is screwing up all machines in Israel right now
[09:15] <marga> https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1222345
[09:15] <ubot2`> Launchpad bug 1222345 in tzdata (Ubuntu) "Wrong DST dates in Israel" [Undecided,Confirmed]
[09:15] <seb128> asac, so, I've been told it's due to you that we didn't get any settings update on the touch image for 6 days ... is there anything we can do to get our code to land again? we can't skip weeks like that :/
[09:15] <marga> The 2013d version (currently in saucy) of tzdata needs to be backported into previous ubuntu versions.
[09:15] <Laney> mmm, tzdata
[09:16] <marga> I'm wondering what the version number should be, and if there's going to be someone taking care of this, or if I should.
[09:16] <marga> Saucy version is 2013d-1ubunut1
[09:16] <marga> ubuntu, obviously :)
[09:16] <seb128> marga, hey, thanks for pointing it out
[09:16] <asac> seb128: i dont think its because of us... we looked at the staged changes last friday
[09:17] <asac> and pushed stuff in that didnt look to dangerous (like SDK we kept out)
[09:17] <asac> and unless i am mistaken there was no settings in daily-release staged
[09:17] <Laney> marga: 2013d-0ubuntu0.XX.YY would work if you want to work on that
[09:17] <seb128> asac, the way stacks are done I think settings needs SDK to be published :/
[09:18] <sil2100> seb128: yes, I am
[09:18] <seb128> sil2100, hey
[09:18] <seb128> sil2100, is there any way we can get settings published?
[09:18] <asac> seb128: ok... so let us have a look at the daily-release ppa today in lex
[09:18] <marga> Laney, -0ubuntu? even if the saucy one is -1ubuntu?
[09:18] <seb128> asac, thanks
[09:18] <marga> I'm always surprised by this numbers
[09:18] <asac> seb128: i believe for SDK we do a special manual test run
[09:18] <sil2100> seb128: we're not landing things because asac wanted to have manual publishing set and go through him with everything that we land - it was Mirv's tick right now, but I'll see settings state right now
[09:19] <asac> and if that isn't busted like th elast two times we will punch it in :)
[09:19] <Laney> marga: Oh I was thinking you'd apply the new upstream on top of what was already in precise
[09:19] <sil2100> asac: btw. as I already asked pstolowski in -touch... where can I find the logs from the camera-app automation crash?
[09:19] <Laney> marga: that'd be usual for the SRU (minimal changes)
[09:19] <marga> Laney, yeah, but I don't know if this makes sense for tzdata
[09:19] <marga> I think tzdata is normally pushed as a whole (at least in Debian)
[09:20] <seb128> Laney, marga: https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
[09:20] <Laney> i.e. we'd usually leave the packaging changes
[09:20] <asac> pstolowski: sil2100: the test is not failing anymore - luckily ... however, there are mediascanner crashes still
[09:20] <asac> pstolowski: sil2100: http://reports.qa.ubuntu.com/smokeng/saucy/image/4094/camera-app-autopilot/
[09:20] <Laney> yeah
[09:20] <Laney> like that
[09:20] <asac> and we have click scope crashes ALL THE TIME :)
[09:20] <asac> like see all the "1" crashes http://reports.qa.ubuntu.com/smokeng/saucy/image/4094/
[09:20] <sil2100> pstolowski: ^
[09:20] <Laney> seb128: thanks for pointing, didn't know that existed
[09:21] <seb128> Laney, yw ;-)
[09:21] <seb128> marga, do you plan to work on the update? I can do sponsoring
[09:21] <sil2100> asac: ok, good to know about the automation failure, since I checked both mediascanner and autopilot changes and tests and didn't see any of those cause a crash in camera
[09:21] <marga> seb128, well, if it makes sense.  I have done tzdata updates for Debian, but not for Ubuntu.
[09:22] <seb128> marga, cf the wiki link I just copied, we have a standing exception to update it, we just didn't keep up with doing that
[09:22] <marga> right.  So, what should the version be?
[09:22] <asac> seb128: right. still mediascanner reliably crashes ONLY during the camera-app run
[09:22] <asac> err
[09:22] <asac> sil2100: ^
[09:22] <asac> so i am not really buying the story of mediascanner not being related
[09:23] <asac> so my story now is:
[09:23] <asac> 1. camera saves images
[09:23] <asac> 2. mediascanner crashes and produces super slowdown due to crash file IO
[09:23] <seb128> marga, 2013d-0ubuntu0.<release> it seems
[09:23] <asac> 3. test gets flaki and fails due to timing issues
[09:23] <seb128> marga, e.g 2013d-0ubuntu0.12.04
[09:23] <seb128> marga, 2013d-0ubuntu0.13.04
[09:24] <sil2100> asac: well, that might make sense, it was hard seeing a relation without seeing any test logs ;) Since it's not really reproducible here on my system
[09:24] <sil2100> pstolowski: ^ can you take a look?
[09:24] <marga> seb128, ok.
[09:24] <seb128> marga, thanks
[09:24] <asac> sil2100: you dont get a crash?
[09:24] <asac> it happens close to 100% in automation during the camera-app autopilot
[09:25] <sil2100> So that is indeed something strange
[09:25] <sil2100> pstolowski: if you're busy, I'll just revert that change and release it without it until it's fixed, ok?
[09:25] <sil2100> asac: I guess the first thing to do is filling out a bug, did you manage to do that already?
[09:27] <asac> i dont think filing a bug will help :)
[09:27] <pstolowski> sil2100: can I get the core file from https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-camera-app-autopilot/57/artifact/clientlogs/_usr_bin_mediascanner-service.32011.crash/*view*/ ?
[09:27] <asac> so i leave it to the owners
[09:27] <asac> pstolowski: http://reports.qa.ubuntu.com/smokeng/saucy/image/4094/camera-app-autopilot/ ther eis a .crash file
[09:27] <asac> that has a Core included usually
[09:27] <asac> ah you pointed to that
[09:27] <asac> sorry
[09:28] <asac> the CoreDump: area
[09:28] <asac> is the bas64 encoded core
[09:28] <asac> but afaik there is a tool to untangle it
[09:28] <asac> lool: ?
[09:28] <pstolowski> asac: yeah, seen it, but was actually wondering if it's readily available in a more friendly format
[09:29] <sil2100> apport-unpack
[09:29] <asac> sil2100: i think more important - now that i look at it - is to figure what happened wth click scope
[09:29] <asac> that one seems to break
[09:29] <pstolowski> alecu: ^
[09:29] <asac> and crash all the time since a few days
[09:29] <sil2100> pstolowski: try downloading http://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-camera-app-autopilot/57/artifact/clientlogs/_usr_bin_mediascanner-service.32011.crash/*view*/ and then using apport-unpack on it
[09:30] <pstolowski> sil2100: yep, it worked, thanks
[09:31] <sil2100> asac: btw. filling bugs will help ;) Since otherwise upstreams at least know there is a problem
[09:31] <sil2100> asac: and they have a base point where they can start off from, write progress, discuss
[09:32] <asac> sil2100: oh ... well, i send them a ping and they should file their own bug io
[09:32] <sil2100> asac: it's a bit more efficient when we have a distributed environment - Florian and some other guys highly recommend filling out bugs whenever there is a problem instead of just directly pinging, as while some people are off some others might see it and pick it up
[09:32] <asac> imo
[09:32] <asac> but yeah i am not saying we shouldnt do bugs at all
[09:33] <asac> sil2100: yeah let me think about that point
[09:33] <asac> the bad about bugs itsw not an interactive thing
[09:34] <seb128> happyaron, hey, do you have an opinion on https://bugs.launchpad.net/ubuntu/+source/libchewing/+bug/1220224 ?
[09:34] <ubot2`> Launchpad bug 1220224 in libchewing (Ubuntu) "Sync libchewing 0.3.5-2 (main) from Debian unstable (main)" [Undecided,Incomplete]
[09:36] <marga> seb128, would this have the 7 day wait?
[09:36] <seb128> Laney, if you want some change from system settings, there is a new glib tarball available out there
[09:37] <seb128> marga, no, if we find testers we can probably wave it in today
[09:37] <Laney> seb128: oh cool, that was last week even
[09:37] <seb128> Laney, there is also a new gtk tarball, I'm going to do that one
[09:38] <Laney> the "display languages" ui in u-s-s isn't very friendly
[09:38]  * sil2100 sighs
[09:38] <seb128> Laney, I'm going to test g-s-d today as well
[09:38] <sil2100> Things are all red today...
[09:38] <seb128> Laney, yeah :/
[09:38] <seb128> sil2100, indeed, going to make didrocks happy :p
[09:38] <Laney> gsd> cool
[09:38] <seb128> sil2100, shame, it has been going good and smoothly while he was not there, and the day he's back everything turns ted
[09:38] <seb128> red
[09:39]  * Laney sniggers at everything turning ted
[09:39] <sil2100> seb128: we need jibel, since we won't release anything without working lxc containers in the test machines
[09:39] <sil2100> Mirv: you said you tried rebooting them, yes?
[09:40] <seb128> asac, ^ can you go and wake up jibel :p
[09:41] <sil2100> seb128: ;D It seems Didier is the CAUSE OF ALL EVIL!
[09:42] <asac> hehe
[09:42] <asac> seb128: you can just call the hotel and have your call put through
[09:42] <asac> saying its an emergency
[09:43] <asac> they have single rooms, so you will precisely wake up who you want :)
[09:43] <seb128> haha
[09:44] <seb128> asac, joke aside, it sucks to always being stucked on people on american tz to be up to unscrew CI
[09:44] <seb128> asac, we need better world coverage
[09:45] <asac> yeah
[09:45] <asac> its an understood issue
[09:45] <asac> and one of the main points
[09:46] <asac> "How can we provide 24h lab operations with 8h business hours?"
[09:47] <pstolowski> asac, sil2100 : I've just checked the core, it seems to be race somewhere when files get removed while still being scanned. I really don't see any relation to the fix I recently did in mediascanner, but also can't offer any quickfix right now (chasing bugs in mediascanner is rather time consuming)
[09:48] <marga> seb128, I'm preparing the packages, but I'm not sure how I would give them to you for sponsoring
[09:48] <seb128> marga, scp somewhere I can dget it?
[09:48] <marga> ah, heh, sure :)
[09:48] <seb128> marga, please list the bug number you pointed earlier in the changelog
[09:49] <marga> of course
[09:49] <seb128> thanks ;-)
[09:49] <asac> pstolowski: since the test doesnt fail anymore the priority is a bit lower than "super escalation", but... the crash surely is high priority
[09:49] <Laney> marga: attaching diff.gz and a link to the orig to the bug is usual
[09:49] <pstolowski> asac: understood. and this isn't the only crash we observed with mediascanner...
[09:50] <marga> Laney, right, but this one has a new orig
[09:50] <asac> pstolowski: maybe the race is a systematic thing?
[09:50] <asac> files get removed while being scanned ... hmm
[09:50] <Laney> marga: indeed, hence linking to it
[09:50] <asac> maybe its also when files still grow while you scan?
[09:51] <pstolowski> asac: I haven't seen this particular crash before. the other crash we have is because it or grillo plugins leak filedescriptors
[09:51] <Laney> rather than you uploading it and then the sponsor having to verify you didn't tamper. :-)
[09:54] <asac> pstolowski: anyone else works on mediascanner or is that just you?
[09:55] <pstolowski> asac: my team "inherited" it; I started looking at it last week
[09:55] <pstolowski> asac: reported it https://bugs.launchpad.net/mediascanner/+bug/1222731
[09:55] <ubot2`> Launchpad bug 1222731 in mediascanner "Mediascanner crashes" [Critical,Confirmed]
[09:58] <asac> thanks
[10:00] <marga> seb128, what should be the distro name <distro>-updates?
[10:00] <Laney> just <series> is fine
[10:02] <Mirv> sil2100: yes
[10:02] <seb128> marga, what Laney said
[10:03] <seb128> Laney, e.g "raring" "precise" works nowadays
[10:13] <sil2100> Mirv, seb128: the otto test machines seem to be somehow broken, it's indeed impossible to start any of the containers, with errors like:
[10:14] <sil2100> chroot: failed to run command ‘useradd’: No such file or directory
[10:17] <Mirv> sil2100: right.. I just wonder if the lxc problems are anyhow related to the autopilot host problem I fixed.
[10:19] <sil2100> Mirv: not sure, it was also a mystery to me that it wasn't installed if it was required - maybe it wasn't really necessary or something, but well, I think we need to poke jibel so that he gives us a walkthrough through the otto machines configuration
[10:21] <sil2100> asac: anyway, sad thing... on Friday we specifically selected the click stack and mediascanner to publish because it seemed safe
[10:21] <sil2100> asac: even if mediascanner changes are not causing trouble, but the click ones you say started crashing
[10:22] <sil2100> So much for 'safe bets'
[10:27] <marga> seb128, packages finished.  They should be available to dget from http://www.marga.com.ar/ubuntu/tzdata/.  Do you want me to give you the 3 dsc urls?
[10:28] <seb128> marga, thanks, and no need for the 3 urls, the one you gave me is easy enough to browse ;-)
[10:32] <seb128> marga, did you decide to not use the same version scheme for raring for a reason?
[10:32] <marga> seb128, no, probably mistake.  Will fix.
[10:32] <seb128> marga, thanks
[10:33] <marga> it's hard not to make mistakes when doing almost the same thing three times.  Sorry, rebuilding now.
[10:35] <darkxst> seb128, hi
[10:35] <seb128> darkxst, hey
[10:35] <darkxst> have you had a chance to look at the g-s-d update?
[10:36] <seb128> darkxst, no yet, but that comment about dropping keys makes me uneasy, it's going to make ubuntu-system-settings abort when opening the battery preferences ... are we sure nothing else in the archive or out there use those keys?
[10:36] <Laney> I searched for it
[10:37] <seb128> Laney, you searched in Ubuntu or just in Debian?
[10:38] <Laney> in Ubuntu using my codesearch instance
[10:38]  * Laney updates its index
[10:38] <seb128> oh, I see
[10:38] <Laney> you have to ignore the branding
[10:38] <Laney> I didn't fix that yet ;-)
[10:38] <seb128> yeah, that confused me
[10:38] <seb128> I though it was the debian tool
[10:39] <seb128> ok, session restart with today updates
[10:39] <seb128> then I do the tzdata sponsoring
[10:39] <seb128> then I test g-s-d
[10:40] <darkxst> Laney, where is your codesearch at?
[10:40] <marga> ouch
[10:40] <Laney> http://162.213.35.4/
[10:40] <Laney> the index is a couple of weeks old
[10:40] <marga> So, I fixed the versions for the raring packages, but seb left.  I'm off to lunch
[10:42] <darkxst> Laney, right, still nice :)
[10:42] <Laney> ya
[10:42] <seb128> hum
[10:42] <seb128> why is my mouse pointer wrong?
[10:42] <seb128> is anyone seeing that as well today?
[10:43] <Laney> describe wrong, but no
[10:43] <seb128> I get a small dark arrow
[10:43] <seb128> rather than my usual white one
[10:43]  * Laney restarts session
[10:44] <Laney> oh yeah!
[10:45] <seb128> Laney, confirming?
[10:45] <Laney> yep
[10:45] <Laney> what controls that?
[10:45] <seb128> gnome-settings-daemon I would say
[10:45] <Laney> did you get the new one?
[10:45] <seb128> I think it's a gtk xsetting
[10:45] <seb128> no
[10:45] <Laney> well I do
[10:46] <seb128> shrug, I had a lot of updates today
[10:46] <seb128> going to be fun to find which one it could be :/
[10:47] <darkxst> pointers are fine here, but I am running a hybrid mix of gnome 3.9 on this machine
[10:49] <Laney> I got a new hicolor-icon-theme
[10:49] <Laney> does that do cursors?
[10:49] <Laney> wait, wtf, no I didn't
[10:49] <seb128> Laney, what is weird is that I get the correct pointer in tb
[10:50] <Laney> yeah firefox goes to the right one too
[10:50] <seb128> or firefox
[10:50] <seb128> did we get a gtk3 update?
[10:50] <Laney> ah new gnome-themes-standard
[10:50] <seb128> ah
[10:51] <seb128> no cursor changes in there though it seems
[10:52] <seb128> oh, in that one
[10:52] <seb128> http://launchpadlibrarian.net/140848282/gnome-themes-standard_3.6.5-0ubuntu1_3.8.1-2ubuntu1.diff.gz
[10:52] <seb128> +  [ Josselin Mouette ]
[10:52] <seb128> +  * Install a cursor.theme to configure the default X cursor.
[10:52] <seb128> +  * Set up the x-cursor-theme alternative.
[10:57] <Laney> is dmz-theme what we use?
[10:58] <Laney> yep
[10:58] <Laney> so I guess we should add a higher alternate for that one
[11:03] <Laney> oh, well, I had manually installed g-themes-standard
[11:03] <Laney> so arguably it's ok
[11:03] <asac> sil2100: yeah. sad
[11:04] <asac> sil2100: did we land the click scope ?
[11:04] <asac> ralsina: check with sil2100 to narrow down the regression window
[11:04]  * asac bbi2h
[11:09] <Mirv> sil2100: on Friday yes https://lists.ubuntu.com/archives/saucy-changes/2013-September/009662.html
[11:11] <seb128> Laney, what do you mean "manually installed so it's ok"? it's still a config change on upgrade
[11:12] <sil2100> ;)
[11:15] <marga> seb128, I see that you uploaded the packages, do you need me to do anything?
[11:16] <seb128> marga, if you can help verifying the updates/getting people to help testing those, once they are accepted, it would be good
[11:16] <seb128> marga, otherwise no
[11:16] <Laney> hmm
[11:16] <seb128> marga, thanks for the updates! ;-)
[11:16] <Laney> darkxst: do you intentionally seed the dmz-cursor-theme?
[11:17] <marga> no prob. Thanks for the quick response.
[11:18] <larsu> how did the scroll direction work on i-sound? I assume scrolling up meant volume up?
[11:18] <Laney> presumably
[11:19] <larsu> well that's how it's going to be then :) Thanks!
[11:19] <seb128> marga, just to make sure, is the current tzdata already leading to wrong time or is that going to happen in the futur?
[11:19] <marga> seb128, it's already happening.
[11:19] <seb128> larsu, correct
[11:19] <seb128> larsu, that's good common sense no? :p
[11:19] <seb128> marga, ok, thanks
[11:20] <darkxst> Laney, we use the Adwaita cursor them
[11:20] <darkxst> theme
[11:20] <Laney> darkxst: I guess you want to unseed it yet
[11:20] <Laney> s/yet/then/
[11:20] <larsu> seb128: yep, just wanted to make sure :)
[11:20] <Laney> I think we'll have to make dmz-cursor-theme have a higher priority
[11:20]  * larsu never uses that feature, has hardware buttons for volume
[11:21] <marga> For precise/quantal it started yesterday.  For raring it's still ok, it will be wrong in 3 weeks.
[11:21]  * seb128 has on y laptop, but not on his desk keyboard
[11:21] <seb128> marga, ok, the bug description was not really clear about that, thanks for confirming
[11:22] <seb128> marga, I pinged directly on #ubuntu-release, let's see how that works
[11:26] <darkxst> Laney, ok will do
[11:26] <Laney> cool
[11:27] <seb128> marga, want to do the lucid SRU as well? ;-)
[11:27] <marga> seb128, suuuure.
[11:27] <seb128> marga, thanks!
[11:44] <lool> pstolowski: I see you found my original report
[11:44] <pstolowski> lool: yes, thanks for that
[11:44] <lool> pstolowski: you can extract coredump from .crash with apport-unpack
[11:45] <lool> pstolowski: and you can even sometimes jump straight to gdb with apport-retrace -g
[11:45] <pstolowski> lool: yep, figured that, thanks
[11:46] <lool> pstolowski: I tried to debug it a bit; it seems related to the cancellation, like the gst_listener being NULL-ed and then used again
[11:46] <lool> but I couldn't figure it out this week-end and thought that people who worked on the code would have a better chance of finding this quickly
[11:47] <lool> pstolowski: looks like an old bug that is just popping now because we're using it on the device
[11:47] <lool> pstolowski: BTW what are we going to do with the mediascanner?  search for medias in scopes?
[11:48] <pstolowski> lool: yes, it's just coincidence it showed up after my other bugfix
[11:49] <pstolowski> lool: mediascanner keeps track of all media files on the device, and exposes them to scopes
[11:57] <marga> seb128, http://www.marga.com.ar/ubuntu/tzdata/lucid/tzdata_2013d-0ubuntu0.10.04.dsc
[11:57] <seb128> marga, thanks!
[12:11] <pitti> Good morning
[12:12] <Laney> I was about to say something and then I realised where pitti is :P
[12:13] <pitti> Laney: well, I did get up at 5 am as usual, just in a wrong TZ :)
[12:13] <pitti> just didn't check IRC this morning yet
[12:13] <pitti> my first time in the Lexington office
[12:15] <seb128> pitti, hey, how are you? had a good flight? how is Lexington?
[12:16] <pitti> seb128: yes, it was quite fine; everything worked, did some hacking, reading, and watched Oblivion
[12:16] <pitti> seb128: and I trained myself into the TZ before, I went to bed very late on Fri/Sat :)
[12:16] <seb128> pitti, I liked that movie, but mostly for the amazing images ... I guess you didn't get that effect in a plane :p
[12:16] <pitti> seb128: Lexington seems to be in the middle of a forest, but surrounded by ridiculous traffic jam at the same time
[12:17] <pitti> seb128: otherwise, quite similar to the London office, just much smaller
[12:17] <seb128> k
[12:17] <sil2100> Mirv: I guess you can also take a look here in the meantime: https://code.launchpad.net/~sil2100/cupstream2distro-config/diverge_autopilot/+merge/184551
[12:17] <sil2100> ;)
[12:17] <sil2100> fginther: hi!
[12:17] <sil2100> fginther: do you know if jibel is somewhere nearby?
[12:17] <pitti> seb128: heh, no; usual crappy screen, but it was an okay story
[12:17] <seb128> yeah, I really enjoyed the first half
[12:17] <sil2100> fginther: since I guess we would really need his help with the otto autopilot machines and containers, as everything is badly broken
[12:18] <sil2100> fginther: and seb128 (as probably everyone else) would really like to get some things released finally ;)
[12:18] <seb128> pitti, the end is a bit disappointing/no real surprise ... but I mostly liked the movie as well ;-)
[12:19] <seb128> pitti, if you see a jibel, please poke him, lxc containers are screwed and we can't do landing
[12:20] <fginther> sil2100, He's not here at the moment
[12:20] <pitti> seb128: I saw him at breakfast this morning, but he'll take the second bus; so he should arrive in 15 mins or so
[12:20] <seb128> pitti, ok
[12:20] <sil2100> ;_;
[12:20] <pitti> seb128: but I finally watched "Fight club" Saturday night; that was surprisingly good
[12:21] <pitti> (gotta keep yourself awake with something -- so it was that movie and playing Descent until 2:30 :) )
[12:21] <seb128> ;-)
[12:21] <seb128> I didn't that one either
[12:21] <sil2100> Oh, Fight Club, that was a fun movie to watch, I would watch it once again since it's been a while
[12:21] <seb128> but it reminds me I saw it in the tv grid for the week, I wonder if I missed it again
[12:21] <pitti> My sister saw it in, what, 1999?, and didn't like it
[12:22] <seb128> lot of people talked about it by then, seems still worth watching
[12:22] <pitti> yes, absolutely
[12:23] <pitti> it was funny to see people using public phones and no mobiles, etc.
[12:25] <seb128> hehe
[12:26] <Mirv> sil2100: so is the idea to temporarily have 'head' actually AP 1.3 while trunk can be developed at will, until at some point 1.3 would be moved to saucy release cu2d proper an head would again have trunk?
[12:30] <sil2100> Mirv: yes, that's the idea - since we're not moving all cupstream2distro-config things from Head to Saucy yet
[12:30] <sil2100> Mirv: while we want to still enable the AP guys to work on python 3 porting etc. without any problems on trunk
[13:10] <seb128> marga, ok, SRUs approved, they need verification next
[13:11] <marga> seb128, good
[13:11] <seb128> Laney, darkxst, jbicha: ok, just built the new g-s-d from the current vcs/installed that, keyboard panel in g-c-c abort on missing gsettings key
[13:11] <seb128> Settings schema 'org.gnome.settings-daemon.plugins.media-keys' does not contain a key named 'switch-input-source'
[13:11] <seb128> not a great start...
[13:13] <seb128> same for the region&language panel
[13:16] <jbicha> seb128: yes you need gnome-control-center too from https://launchpad.net/~darkxst/+archive/gsd38/+packages
[13:17] <seb128> jbicha, shrug
[13:18] <seb128> those key changes make me quite unhappy
[13:18] <seb128> hum
[13:18] <seb128> did gnome-keyring stop working for anyone else?
[13:18] <seb128> well, the ssh agent at least
[13:19] <seb128> jbicha, is there a vcs with that version?
[13:22] <jbicha> no, not yet
[13:23] <seb128> hum, k
[13:31] <Laney> jbicha: probably needs a breaks for older g-c-cs
[13:36] <jibel> seb128, I replied to Mirv , daily-release jobs can not run because the kernel fails to load the module aufs.
[13:37] <seb128> jibel, hey, did you have a good flight?
[13:37] <seb128> jibel, ok, is that a kernel bug or...?
[13:37] <jibel> Mirv, can you please file a bug against the kernel and ping them on #ubuntu-kernel?
[13:37] <jibel> seb128, flight was uneventful, so good thanks.
[13:38] <jibel> seb128, yes I think it is a kernel bug it started with 3.11.0-5.11-generic
[13:39] <jibel> seb128, aufs fails to load with "ERROR: could not insert 'aufs': Function not implemented" with this kernel
[13:42] <seb128> jibel, ok
[13:48] <jbicha> Laney: I don't think your dmz cursor theme change is useful
[13:53] <Laney> why
[13:53] <alex_abreu> sil2100, ping
[13:56] <jbicha> because Ubuntu doesn't install gnome-themes-standard by default; I think we can assume that people that have Adwaita installed don't mind the Adwaita mouse cursor or can use gnome-tweak-tool to pick something different
[13:57] <seb128> jbicha, Laney: btw I uninstalled gnome-themes-standard and my cursor is still wrong
[13:57] <seb128> restarted the session as well
[13:58] <jbicha> ISTR there's a second place where the cursor theme is set
[13:58] <Laney> I discussed the intended semantics of the alternatives in #-gnome and this is right
[13:59] <Laney> Tim is going to unseed dmz from ubuntu GNOME
[13:59] <seb128> k
[13:59] <seb128> what do you I need to do to get back my nice cursor? :p
[13:59] <rsalveti> Laney: hey, do you plan to integrate the gst 1.1.4 packages soon?
[13:59] <seb128> (ideally I should have to do nothing, things should just go back to what they were)
[14:00] <rsalveti> I saw you updated the ppa already
[14:00] <Laney> rsalveti: I have an FFe
[14:00] <Laney> so, whenever that is approved
[14:00] <rsalveti> Laney: right, have the bug around?
[14:00] <Laney> bug #1220588
[14:00] <ubot2`> Launchpad bug 1220588 in gstreamer1.0 (Ubuntu) "[FFe] Update GStreamer stack to 1.1.4" [Undecided,New] https://launchpad.net/bugs/1220588
[14:02] <rsalveti> thanks
[14:15] <seb128> jbicha, darkxst, Laney: I'm happy enough with the new g-s-d (out of a screen locking bug that I mentioned on launchpad)
[14:15] <Laney> cool
[14:15] <desrt> new ALL the things!
[14:15] <Laney> 3.10 time?
[14:16] <seb128> lol
[14:17] <seb128> desrt, did you make uncompatible glib changes again? I just uploaded the fix for https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1222538 ... but I don't like much the "glib changed making app to be patched to work again"
[14:17] <ubot2`> Launchpad bug 1222538 in seahorse-nautilus (Ubuntu) "Unable to encrypt & or sign files with current glib" [Low,Fix committed]
[14:17] <desrt> seb128: not afaik?
[14:17] <jbicha> seb128: https://bugzilla.gnome.org/707769
[14:17] <ubot2`> Gnome bug 707769 in power "Lid close doesn't lock screen if lid-close-action not set to suspend" [Normal,Unconfirmed]
[14:17] <desrt> seb128: this is colin's bug
[14:18] <desrt> seb128: and i think we already fixed it
[14:18] <seb128> desrt, k, maybe that's part of the glib update we didn't get yet
[14:18] <seb128> jbicha, thanks
[14:19] <desrt> seb128: https://bugzilla.gnome.org/show_bug.cgi?id=698081
[14:19] <ubot2`> Gnome bug 698081 in mainloop "Pidgin hangs in g_spawn_command_line_sync" [Normal,Resolved: fixed]
[14:19] <seb128> desrt, that one is quite old, I remember we discussed pidgin around raring release time
[14:19] <seb128> desrt, seahorse-nautilus was still not working in saucy with glib 2.37.5 though
[14:19] <desrt> seb128: this error was introduced in the same monster of a commit that caused the pidgin problems :/
[14:20] <desrt> sigh...
[14:20] <desrt> and here i was, hoping to do something productive today
[14:20] <seb128> desrt, anyway I uploaded https://git.gnome.org/browse/seahorse-nautilus/commit/?id=c41f07cf5785b2d755b85f20bf0546c6ce2ebb02 which fixes it, I hope we don't have other similar bugs
[14:20] <seb128> desrt, don't worry about it, maybe it's all good, I'm going to keep an eye for bugs that might be similar, but it's likely we are going to have none
[14:20] <desrt> oh
[14:21] <desrt> erm.  this is just a warning according to stef's commit
[14:21] <seb128> desrt, well, for some reason seahorse-nautilus stopped working ...
[14:21] <desrt> i wonder if it had fatal warnings or something
[14:22] <seb128> desrt, https://bugzilla.redhat.com/show_bug.cgi?id=981580#c12
[14:22] <ubot2`> bugzilla.redhat.com bug 981580 in glib2 "Glib regression related to SIGCHLD warnings" [Unspecified,New]
[14:24] <seb128> marga, tzdata updates released to -updates for precise-quantal-raring (lucid still to be done and then we are all good)
[14:24] <desrt> marga: hey.  any progress on that binary nfs-safe dconf backend? :)
[14:25] <marga> desrt, :-/  I have it in my queue, but it lost priority over here.
[14:25] <marga> seb128, yes, I saw, my machine already picked up the precise change, thanks.
[14:26] <desrt> marga: know how that feels...
[14:26] <seb128> marga, excellent! yw ;-)
[14:27] <desrt> seb128: so i understand the problem now.... and it's a bit of a mixed bag
[14:27] <desrt> the bad behaviour was in seahorse, for sure
[14:27] <desrt> and maybe other apps out there
[14:28] <desrt> when they do things in the way that they were before, they install a child watch into glib that never ever gets satisfied
[14:28] <desrt> and may inadvertantly reap the wrong child at some future point if PIDs get recycled
[14:28] <desrt> the difference is that we changed the behaviour that we have in this case from leaking forever to immediately reporting the child as exited, with a warning
[14:28] <desrt> and this behaviour change is what caused the issue
[14:29] <desrt> from the standpoint of "this will allow us to find broken applications easier" i sort of like colin's change
[14:29] <seb128> ok, so seahorse was basically working by luck, relying on a buggy code which happened to work
[14:29] <desrt> well.... it was installing a watch that would never be satisfied
[14:30] <desrt> and glib was trying over and over again to satisfy the faulty watch
[14:30] <desrt> and each time it did this, it would add another one to the list
[14:30] <desrt> so now it's just removed from the list immediately, a warning is printed and (the imcompatible change) it's immediately dispatched
[14:30] <desrt> *incompatible
[14:30] <seb128> I see
[14:31] <seb128> I guess that's ok, it's not like it was making "good code" not work anymore
[14:31] <seb128> it's making buggy code more visibly buggy :p
[14:31] <desrt> this was a somewhat arbitrary decision on colin's part.   he could have just as well removed it from the list, given the warning, then dropped it on the floor, which would have been closer to the old behaviour
[14:31] <desrt> but ya... dispatching the handler immediately does make the bug more obvious
[14:31] <desrt> which is nice
[14:32] <desrt> anyway... case closed as far as i'm concerned... if you get more bugs like this, tell upstream to talk to me about why the problem is their fault :p
[14:33] <seb128> desrt, wfm, thanks for the explanations ;-)
[14:44] <desrt> seb128: your measure disk usage API just landed
[14:45] <seb128> desrt, \o/
[14:45] <seb128> desrt, thanks ;-)
[14:55] <mdeslaur> seb128: is there a new bug for gnome-settings-daemon not locking the screen when the lid is closed?
[14:56] <seb128> mdeslaur, https://bugzilla.gnome.org/707769
[14:56] <ubot2`> Gnome bug 707769 in power "Lid close doesn't lock screen if lid-close-action not set to suspend" [Normal,Unconfirmed]
[14:56] <mdeslaur> seb128: no ubuntu bug yet?
[14:56] <seb128> mdeslaur, but that's not in Ubuntu yet, it's part of the 3.8 update that is FFe discussed
[14:56] <seb128> mdeslaur, I mentioned it on https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1219486
[14:56] <ubot2`> Launchpad bug 1219486 in gnome-settings-daemon (Ubuntu) "FFe: Update gnome-settings-daemon to 3.8.4" [Wishlist,New]
[14:57] <mdeslaur> seb128: oh, I thought I saw 3.8.5 go by on the saucy-changes list
[14:58] <seb128> mdeslaur, shrug, jbicha just jumped on it and uploaded it seems
[14:58] <seb128> jbicha, was the FFe even officially approved?
[14:59] <seb128> mdeslaur, seems like jbicha didn't consider the bug important enough to get it fixed before upload, I'm not sure I'm happy about that
[14:59] <seb128> mdeslaur, but it's uploaded now...
[14:59] <mdeslaur> hrm
[15:03] <happyaron> seb128: I've commented on that bug, it seems the crash fixes are really helpful, but breaking scim-chewing isn't something we want
[15:07] <jbicha> seb128: I thought you said you were happy enough with the update and Laney approved the FFe conditional on you being happy
[15:07] <seb128> jbicha, out of the locking issue yes :p
[15:07] <Laney> They promised to fix any regressions ...
[15:08] <seb128> jbicha, oh, well, I just hope somebody is going to make sure it's fixed before release
[15:08] <Laney> so I expect this to be resolved quite soon
[15:08] <seb128> wfm
[15:09] <Laney> bah
[15:09] <seb128> jbicha, did you look at updating gtk to 3.8.4 (I'm about to do it but don't want to dup work)
[15:09] <Laney> qml is giving me a hard time today
[15:10] <seb128> Laney, what are you fighting with? (I doubt I can help much but who knows)
[15:10] <Laney> the change password dialog
[15:10] <Laney> I had a bug where it was saying a value was undefined until I printed it with console.log then it worked ...
[15:11] <seb128> Laney, btw please review https://code.launchpad.net/~seb128/ubuntu-system-settings/battery-new-idle-key/+merge/184588 ... jbicha uploading g-s-d means ubuntu-system-settings' battery panel is going to abort() on missing gsettings key until that lands
[15:11] <larsu> what's handling the hardware volume keys on the phone? Is it also gnome-settings-daemon?
[15:11] <Laney> oh yeah, k
[15:11]  * seb128 shakes fist in direction of desrt for the abort() on missing keys
[15:11] <Laney> not that u-s-s is landing ...
[15:11] <seb128> yeah, that's the next issue then :/
[15:11] <desrt> seb128: hi.  thanks for thinking of me.
[15:11] <jbicha> seb128: no, I'm not working on the gtk3 update
[15:11] <seb128> larsu, no, no gnome-settings-daemon on the phone (that depends on gtk and has quite some x11 code)
[15:12] <seb128> jbicha, ok, I'm start it on it then, thanks
[15:12] <seb128> larsu, powerd does I think
[15:12]  * desrt notes that gnome 3.10 has an experimental wayland version this cycle
[15:12] <desrt> i wonder what they're doing for g-s-d....
[15:12] <larsu> seb128: interesting. Thanks :)
[15:12] <seb128> desrt, https://live.gnome.org/Wayland/gnome-settings-daemon
[15:13] <seb128> desrt, quite some TBD still, I guess they turn off a part of the plugins
[15:13] <desrt> ya.  i guess so too.
[15:13] <desrt> this page reads like
[15:13] <desrt> plugin a: this plugin communicates with X to take care of setting up A
[15:13] <desrt> plugin b: this plugin communicates with X to take care of setting up B
[15:13] <desrt> ...
[15:13] <seb128> though the page is quite outdated
[15:14] <sil2100> alex_abreu: hi!
[15:14] <seb128> desrt, https://mail.gnome.org/archives/gnomecc-list/2013-July/msg00000.html has a more recent status
[15:15] <desrt> pah
[15:15] <sil2100> alex_abreu: good thing you pinged me, damn, I almost forgot about the issue
[15:15] <sil2100> jibel: hi!
[15:16] <sil2100> jibel: did the guys already inform you about the autopilot otto machine problems we're having?
[15:16] <larsu> seb128: hm, doesn't look like it's in powerd. Do you have any idea who I could ask?
[15:16] <seb128> larsu, #ubuntu-touch
[15:17] <larsu> ah, right :)
[15:17] <desrt> i'd guess it's handled in the compositor....
[15:17] <desrt> the hardware buttons probably get translated to input subsystem events... which get slurped up by the compositor... we have no mechanism for global key grabs afaik, so they'd have to be handled there.
[15:20] <larsu> desrt: that makes sense, but I'm looking to find the code that responds to those events and changes the volume
[15:20] <larsu> as that seems to be buggy :)
[15:25] <alex_abreu> sil2100, :)
[15:25] <alex_abreu> sil2100, have you had time to think about it?
[15:31] <jibel> sil2100, yes. It's a kernel issue, apw is working on it.
[15:31] <apw> jibel, which one is that
[15:32] <jibel> apw, aufs failing to load
[15:32] <apw> jibel, ahh yes
[15:33] <apw> jibel, yeah we know what that is and have a fix, it will be in teh next upload
[15:33] <jibel> apw, thanks
[15:36] <sil2100> \o/
[15:36] <sil2100> alex_abreu: sitting down to that now
[15:49] <sil2100> alex_abreu: another problem with the libunity-webapps webbrowser-app dependency and powerpc problem is that well, essentially there is no FFe for webapps
[15:49] <alex_abreu> sil2100, yeah there is https://bugs.launchpad.net/unity-webapps-qml/+bug/1207515
[15:49] <ubot2`> Launchpad bug 1207515 in webbrowser-app "[FFE] Webapps container for Desktop" [Undecided,New]
[15:50] <sil2100> alex_abreu: oh, did it get reviewed and approved?
[15:51] <alex_abreu> sil2100, I think so ... didrocks +1'nd it I think, not sure if something else is needed
[15:54] <sil2100> alex_abreu: ok, since the thing is, this change would fire up a really big chain of powerpc-support drops, since without libunity-webapps for powerpc, we won't have bamfdaemon for powerpc, so there won't be no unity as well
[15:54] <sil2100> So I guess I need to think of a different solution
[15:55]  * sil2100 wonders why someone released webapps before the weekend
[15:55] <alex_abreu> sil2100, I don't think I see the connection there, why no bamf if no libunity-webapps ?
[15:55] <sil2100> alex_abreu: because bamfdaemon depends on libunity-webapps0, so it won't be installable if we drop libunity-webapps0 for powerpc
[15:56] <alex_abreu> argh right forgot about it
[15:57] <alex_abreu> sil2100, can we have conditional depends? based on arch
[15:57] <sil2100> alex_abreu: we could, but the code would have to be written so that it would still work without webbrowser-app installed
[15:57] <sil2100> Would that be possible?
[15:58] <sil2100> To have a 'powerpc fallback' code path
[15:59] <alex_abreu> sil2100, yes, that's why I am asking
[16:02] <sil2100> alex_abreu: we can either do a conditional dependency (which I guess would be fine, as it's better than not having unity for powerpc) or maybe try something with Suggests/Recommends
[16:03] <sil2100> seb128: what happens if a package Recommends: some other package that is not available? Is it like with a dependency, or is it 'more ok' in that case?
[16:06] <seb128> sil2100, we shouldn't do that, but we mostly get away with it
[16:06] <seb128> they still show on e.g component mismatch
[16:10] <sil2100> seb128: so in this case a conditional platform-wise dependency would be ok, what do you think?
[16:11] <sil2100> From the distro point-of-view
[16:17] <alex_abreu> sil2100, we could add an arch dependant dep and I could adjust the code ... or we could go the dirty recommends route
[16:17] <sil2100> didrocks: hello! How were your holidays? :)
[16:18] <sil2100> alex_abreu: for now, let's just adjust the code anyway, since I guess that in both cases I would like that rule to be around
[16:18] <alex_abreu> sil2100, +1
[16:18] <sil2100> alex_abreu: thanks!
[16:18] <didrocks> hey sil2100, the holidays were excellent, thanks!
[16:18] <alex_abreu> sil2100, I'll MR you the changes
[16:19] <sil2100> didrocks: all rested and refreshed I hope ;)!
[16:19] <sil2100> alex_abreu: excellent, will be waiting :)
[16:20] <didrocks> sil2100: and jetlagged :p
[16:21] <sil2100> didrocks: after the 'sudden' flight to the US I guess that's normal ;) Should I already prepare the Saucy series in cu2d-config? ;)
[16:22] <didrocks> sil2100: please do, think about fghinter to change the process about it please :)
[16:22] <sil2100> didrocks: at least with the QA stack for now (and slowly migrating other projects one by one)
[16:22] <sil2100> Aye!
[16:23] <seb128> didrocks, hey, welcome back!
[16:23] <didrocks> hey seb128! ça va?
[16:23] <seb128> didrocks, très bien, et toi ?
[16:23] <didrocks> read that you loved the g-c-c changes :p
[16:23] <didrocks> ça va, mais déjà dans le bain rapidement!
[16:24] <seb128> didrocks, on t'as pas vu de la journée, dans le bain des vacances ? :p (c'est bien Lexington ?-)
[16:24] <seb128> ;-)
[16:24] <seb128> didrocks, yeah, I always love late changes in a cycle, you know me ;-)
[16:25] <didrocks> seb128: dans des meetings (il est 12h20 ici) but I woke up at 2h30 :/
[16:25] <seb128> :-(
[16:25] <didrocks> just didn't connect to IRC, only reading emails
[16:25] <seb128> seems like the time I go to bed atm :p
[16:29] <didrocks> argh…
[16:29]  * didrocks hugs seb128
[16:30]  * didrocks away for a while
[16:32]  * seb128 hugs didrocks
[16:55] <mdeslaur> argh
[16:55]  * mdeslaur shakes fist at whoever killed the session saver plugin from gedit
[18:04] <sil2100> didrocks, fginther: https://code.launchpad.net/~canonical-desktop-team/cupstream2distro-config/new_saucy_series/+merge/184641 <-
[18:09] <didrocks> sil2100: I think fginther's won't understand the to_transition or will it?
[18:10] <fginther> didrocks, sil2100, upstream merger will skip projects under to_transition (which I believe is the right action)
[18:12] <didrocks> so we are good for stuff diverged I guess :)
[18:13] <fginther> sil2100, I have an question for thomi regarding the autopilot ppas
[18:13] <czajkowski> anyone else having this bug issue? https://bugs.launchpad.net/bugs/1107926
[18:13] <ubot2`> Launchpad bug 1107926 in bamf (Ubuntu) "bamfdaemon crashed with signal 5 in _XReply()" [Medium,Confirmed]
[18:13] <czajkowski> I've done daily updates today and still running into it
[18:14] <didrocks> sil2100: you will need to ask as well jibel I guess to create the views
[18:28] <seb128> czajkowski, try pinging Trevinho