[06:08] <TheMuso> c
[06:18] <BigWhale> Good Morning everyone.
[06:19] <mlankhorst> morning!
[06:34] <pitti> Good morning
[06:38] <BigWhale> Who do I vent to if I want to vent about Nautilus? :/
[07:47] <jibel> good morning
[07:48] <didrocks> salut jibel
[07:48] <jibel> bonjour didrocks
[07:49]  * didrocks grrr at magners
[08:02] <jpds> Anyone else have problems on raring where a full-screen application, isn't really full-screen?
[08:03] <didrocks> jpds: yeah, known issue, fixed in trunk, waiting for mterry to publish unity
[08:37] <tjaalton> didrocks: hey, who was it again that was supposed to look into the issue where some unity/compiz settings get reset on upgrade?
[08:38] <didrocks> tjaalton: I think smspillaz had an idea on what is causing it
[08:38] <tjaalton> ah
[08:39] <tjaalton> ok I'll ping him later
[08:40] <didrocks> :)
[08:55] <pitti> RAOF: are you aware of the colord autopkgtest failure? looks like colord has FTBFSed for a while
[08:55] <RAOF> pitti: No, I'm not; also, I see the most recent colord in my archives?
[08:55] <pitti> some CDSensor.../ cd_sensor_* unknown symbols
[08:56] <pitti> https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-colord/11/ARCH=i386,label=adt/artifact/results/log
[08:59] <RAOF> Looks like it's pretending to be on kFreeBSD?
[08:59] <seb128> hey desktopers
[08:59] <pitti> bonjour seb128
[08:59] <RAOF> pitti: Why hasn't that stopped propagation from raring-proposed to raring?
[08:59] <pitti> RAOF: britney doesnt' look at autopkgtest yet
[09:00] <seb128> salut pitti
[09:00] <RAOF> Aha, that would be why.
[09:00] <seb128> hey RAOF
[09:00] <RAOF> Ok, I'll look at colord tomorrow. I've been meaning to make that autopkgtest a bit more awesome anyway.
[09:01] <RAOF> pitti: Thanks!
[09:01] <pitti> ah, thanks!
[09:03] <Laney> hallo!
[09:04] <pitti> hey Laney
[09:06] <seb128> hey Laney
[09:06] <Laney> hey pitti, seb128
[09:06] <Laney> did you have good weekends?
[09:06] <pitti> quite fine indeed, thanks! and you?
[09:06] <seb128> w.e was quite ok here, weather was grey and rainy though
[09:07] <Laney> not so bad, managed to get out on the bike in the gaps in the rain
[09:07] <pitti> it was actually quite sunny here (but cold)
[09:07] <pitti> sunny enough for ice cream, anyway (inside)
[09:08] <pitti> but it's swowing again now, yay
[09:08] <pitti> snowing, too
[09:09] <Laney> spring starts on Wednesday, no fear ;-)
[09:10] <mlankhorst> :D
[09:10]  * mlankhorst sends waves of snow Laney's way
[09:11] <Laney> :<
[09:14] <mlankhorst> spring soon!
[09:14] <mlankhorst> lets wrap up this winter
[09:49] <czajkowski> morning folks
[09:50] <czajkowski> would anyone be able to share any light on why I do an update on Raring, it's breaking my virtual Box so I have to kick it each time via http://pastebin.ubuntu.com/5624797/
[09:51] <ogra_> czajkowski, #ubuntu-kernel perhaps ?
[09:51] <czajkowski> ok cheers ogra_
[09:51] <ogra_> looks like a module issue
[09:52] <mitya57> let's have virtualbox broken in every release!
[09:52]  * mitya57 wonders when will someone sponsor lp:~mitya57/ubuntu/precise/virtualbox/4.1.12-dfsg-2ubuntu0.3 for him
[10:14] <jibel> didrocks, I filed bug 1156540 for the issue we had this morning
[10:14] <ubot2> Launchpad bug 1156540 in cowdancer (Ubuntu) "cowdancer deletes bind-mounted directories" [Critical,New] https://launchpad.net/bugs/1156540
[10:15] <didrocks> jibel: merci!
[10:18] <czajkowski> didrocks: any idea where to send mitya57 to so they can get their branch sponsored
[10:19] <didrocks> czajkowski: sorry, do you have some context? :-) which projects?
[10:19] <czajkowski> 09:52 < mitya57> let's have virtualbox broken in every release!
[10:19] <czajkowski> 09:52  * mitya57 wonders when will someone sponsor lp:~mitya57/ubuntu/precise/virtualbox/4.1.12-dfsg-2ubuntu0.3 for him
[10:19] <Laney> it's already in the sponsor queue
[10:19] <didrocks> czajkowski: they should just follow the sponsorship process :)
[10:19] <didrocks> ah, so it's already in the queue :)
[10:20] <czajkowski> Laney: didrocks cheers I didn't know :)
[10:20] <Laney> someone will get to it soon; four days isn't overly long to wait (unfortunately?)
[10:20] <didrocks> :)
[10:26] <mitya57> that's not urgent for me (at all), but the large sponsoring queue %Bis%B a problem
[10:27] <mitya57> oops, that was *is* :)
[10:27] <seb128> mitya57, the sponsoring queue is sort of under control
[10:27] <seb128> it was close from 40 items on friday
[10:28] <mlankhorst> \o/
[10:28] <seb128> with a stack of "needs packaging" bugs
[10:29] <pitti> robru, didrocks: oh, friends is apparently part of the daily autolanding -- how does one fix the broken autopkgtests?
[10:29] <pitti> I guess I shouldn't just manually upload?
[10:29] <didrocks> pitti: just propose a branch upstream :)
[10:29] <didrocks> and it will be in tomorrow daily release, published if ken acks it
[10:29] <pitti> didrocks: oh, is the packaging part of the upstream branch?
[10:29] <didrocks> pitti: right
[10:29] <pitti> urgh
[10:30] <pitti> didrocks: d'accord, merci !
[10:30] <didrocks> pitti: de rien :)
[10:30] <didrocks> pitti: make dist doesn't dist the pakcaging
[10:30] <didrocks> but I don't have the time to give the full rationale again :)
[10:30] <pitti> no worries
[10:37] <didrocks> pitti: python3-dbusmock is in universe, do you think it can go to main?
[10:37] <pitti> didrocks: bug 1154126
[10:37] <ubot2> Launchpad bug 1154126 in python-dbusmock (Ubuntu) "[MIR] python-dbusmock" [Undecided,Fix committed] https://launchpad.net/bugs/1154126
[10:38] <pitti> it was approved, so feel free to promote
[10:38] <didrocks> excellent! :)
[10:38] <didrocks> thanks pitti. Will promote once indicator-messages published
[10:38] <didrocks> pitti: because it already happened more than once that prepromotion was demoted…
[10:57] <pitti> robru, kenvandine: https://code.launchpad.net/~pitti/friends/fix-autopkgtest/+merge/153749, s'il vous plaît
[11:49] <lool> tjaalton: Hey, since recent updates xrandr detects a VGA display attached on my laptop, but nothing is connected; how could I check whether this is kernel or xorg related?
[11:50] <lool> I've read dmesg, but I wasn't able to spot informtion from the i915 logs
[11:50] <tjaalton> lool: it's a kernel regression, 20afbda209d708 is needed from linus
[11:50] <tjaalton> boot -12, it should work
[11:50] <lool> tjaalton: ok, so known/reported and being fixed already, thanks
[11:50] <tjaalton> known, not fixed yet
[11:51] <lool> tjaalton: is this something we could auto-test for?  I guess it's super hardware specific
[11:51] <tjaalton> lool: aiui it's oly on gen4 hw, what do you have?
[11:52] <tjaalton> *only
[11:52] <tjaalton> yeah dunno how to autotest hw specific stuff, other than having each gen represented in some lab
[11:53] <lool> tjaalton: I have super old intel
[11:53] <lool> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
[11:53] <lool> not sure how to find a more useful name for it
[11:54] <tjaalton> yeah it's fourth generation
[11:55] <lool> Intel Graphics Media Accelerator 4500MHD
[11:55] <tjaalton> the kernel stable series picked up an incomplete set of patches to fix some bug, missing this commit
[11:56] <lool> tjaalton: just curious, are we testing new kernel / xorg stacks against all hardware revisions in our cert lab?
[11:57] <tjaalton> don't think so
[11:57] <tjaalton> probably should know though :)
[11:57] <lool> sounds bad not to leverage this to try to catch bugs
[11:58] <lool> (even if this particular bug might not be covered because we might not have this particular class of hardware)
[12:06] <didrocks> xnox: hey, do you know when steve or anyone on your team will look at the ubuntu-platform source?
[12:06] <didrocks> xnox: as it's the first one, maybe would be better to get this one in first :)
[12:06] <xnox> didrocks: ack. I think it will end up being me doing all the vorlon's tasks on that blueprint.
[12:07] <didrocks> xnox: well, at least, you will bring consistency between MP :)
[12:07] <xnox> didrocks: I did this one as "simple" trial run. Will look at others in a moment ;-)
[12:07] <didrocks> xnox: I don't really have time to review them right now properly (but feel free to continue, first look, it sounds fine)
[12:07] <didrocks> thanks xnox :)
[12:07] <didrocks> xnox: oh, i'm a little bit pendantic about on dep per line though
[12:08] <didrocks> xnox: and trailing , so that next diff doesn't have 2 lines when adding something
[12:08] <xnox> didrocks: ack. ack. Not sure who is doing MIR to land it into raring though. I believe vorlon volunteered, and not sure if that got delegated yet or not.
[12:08] <didrocks> also, you miss the info on debian/control
[12:08] <xnox> didrocks: patches to wrap and sort are welcome!
[12:08]  * xnox did run it... unless you want further tweaks to it.
[12:08] <xnox> wrap-and-sort --didrocks-mode
[12:09] <xnox> aliased to --pedantic
[12:09] <didrocks> xnox: well, the rest sounds fine, I would appreciate if you have the time to finish this :-)
[12:09] <didrocks> xnox: can wrote the comment on the MP, one sec
[12:13] <didrocks> xnox: commented :)
[12:14] <xnox> didrocks: thanks a lot ! will fix up.
[12:14] <didrocks> xnox: thanks to you :-)
[12:29] <seb128> mitya57, it's fine to use the serie name without -proposed for SRUs nowadays
[12:29] <seb128> just for info
[12:30] <mitya57> seb128: thanks, I forgot about that
[13:03] <kenvandine> pitti, thanks!
[13:03] <pitti> hey kenvandine, how are you?
[13:03] <kenvandine> great
[13:03] <kenvandine> and you?
[13:05] <pitti> I'm getting a cold (argh), but otherwise quite well
[13:05] <seb128> kenvandine, hey, had a good w.e?
[13:05] <kenvandine> i did
[13:06] <pitti> kenvandine: does the CI test run again automatically? I added a commit message back then and clicked on that jenkins link, but I didn't see another test run
[13:06] <kenvandine> no, but the ci test did show success.  so i marked it as approved
[13:06] <kenvandine> so the merger will run
[13:07] <kenvandine> didrocks, do you know if we'll see an update of ubuntu-ui-toolkit for raring?
[13:38] <didrocks> kenvandine: not sure, quite busy with other stuffs, why?
[13:38] <didrocks> kenvandine: something to ask to cyphermox who is in charge of his stack
[13:44] <kenvandine> didrocks, it includes styling changes to PageStack that i need for gwibber
[13:44] <kenvandine> and i am going to file an MIR for that today :)
[13:44] <kenvandine> although i haven't really looked at the packaging yet...
[13:45] <kenvandine> cyphermox, ^^
[13:45] <didrocks> kenvandine: btw webapps… still in manual publishing mode for days and days :/
[13:45] <didrocks> despite the pings
[13:45] <didrocks> (not really happy)
[13:46] <kenvandine> didrocks, you mean the package split?
[13:46] <didrocks> kenvandine: no, the daily release job
[13:46] <kenvandine> i'm looking, i thought i manually published that already
[13:47] <didrocks> thanks kenvandine
[13:47] <didrocks> kenvandine: it looks wrong to me looking at it btw
[13:47] <didrocks> kenvandine: the change in symbols was done manually, not automatically
[13:47] <didrocks> and list a version > of the changelog one
[13:47] <didrocks> it should have been 0replaceme
[13:47] <didrocks> so that the daily release change for the right version
[14:10] <seb128> mterry, hey, had a good w.e?
[14:11] <mterry> seb128, sort of.  I was a bit sick and still am, but hopefully can work fine
[14:11] <seb128> mterry, I looked at the unity/autopilot issues this morning, found out the buggy commit and Trevinho fixed the issue (it's r2222) ... can you kick a retry or unity build/daily landing?
[14:11] <seb128> mterry, oh ok, get better!
[14:11] <seb128> retry of*
[14:15] <mterry> seb128, yup
[14:54] <xnox> didrocks: default priority should be Optional, instead of extra?! Agree, disagree, keep as it is?
[14:54] <didrocks> xnox: completely agree :-)
[14:54]  * didrocks is always nagging seb128 about it :p
[14:56]  * seb128 couldn't care less :p
[14:57] <ogra_> Extoptional
[14:57] <ogra_> ^^^ compromise
[14:59] <seb128> time for some exercice, be back in ~1h
[15:01] <xnox> didrocks: why are we purging debian/source/format ? to mix-and-match how it's build? (native and non-native)
[15:01] <didrocks> xnox: hum, you don't really need, you can put it to 1.0
[15:02] <didrocks> xnox: I don't really care as long as it's not 3.0 ;)
[15:21] <xnox> didrocks: how / when are we going to land libhybris? as these packages depend on it....
[15:22] <didrocks> xnox: ogra_ was telling it's not needed. ogra_ ?
[15:22] <ogra_> huh ?
[15:22]  * ogra_ cant remeber saying such a thing ... 
[15:22] <didrocks> ogra_: libhybris is a runtime dep, right?
[15:22] <didrocks> not build time?
[15:22] <xnox> ogra_: platform-api & qtubuntu-sensors at the moment build-dep on libhybris. And both of them are compat/wrapper/provider libs around libhybris by the looks of things.
[15:22] <ogra_> we need the ubuntu side of libhybris  pakckaged
[15:22] <didrocks> and so if we have the ubuntu-platform api built
[15:23] <xnox> (as well as other)
[15:23] <ogra_> not the android side though
[15:23] <ogra_> (sine thats armel and built at android image buildtime)
[15:23] <ogra_> i'm not sure if rsalverti probably has plans to do it differently though
[15:23] <didrocks> ogra_: the ubuntu-side is arch:any?
[15:23]  * xnox is confused why those packages build-dep on libhybris though.....
[15:23] <ogra_> didrocks, good question
[15:23] <xnox> libhybris looks arch:any as well to me (looking at the upstream code)
[15:24] <ogra_> root@localhost:/# dpkg -l|grep hybris
[15:24] <ogra_> ii  libhybris                                    0.61-0phablet1                                          armhf        Allows to run bionic-based HW adaptations in glibc systems - libs
[15:24] <ogra_> ii  libhybris-test                               0.61-0phablet1                                          armhf        Allows to run bionic-based HW adaptations in glibc systems - tests
[15:24] <xnox> afterall android does run on i386 atoms (?!)
[15:24] <ogra_> thats what i get on my phone
[15:24] <xnox> from a ppa, not from raring archive though.
[15:25] <ogra_> root@localhost:/# apt-cache showsrc libhybris|grep ^Arch
[15:25] <ogra_> Architecture: any
[15:25] <ogra_> yeah, its any atm
[15:25] <ogra_> and we will roll x86 userspace if we actually make a qemu image work ...
[15:25] <xnox> didrocks: are we landing _that_ daily though?
[15:25] <ogra_> so it needs to be any
[15:26] <xnox> (or daily landing, but actually manually merging when we want updates?!)
[15:26] <didrocks> xnox: we will do as if. But I guess we'll land that daily in a ppa for raring
[15:26] <didrocks> xnox: ah, you meant libhybris?
[15:26] <ogra_> i'm not really sure how safe it is to land it inependently from the adnroid side
[15:26] <xnox> didrocks: yeah, libhybris.
[15:26] <didrocks> ogra_: would be good if one of you can dig into that
[15:26] <didrocks> xnox: so, we have two choices, for things we are not upstream for:
[15:26] <xnox> ogra_: you get the work-item =)
[15:27] <didrocks> - either do the manual upload way
[15:27] <ogra_> well, it woyld help if we discussed that in a channel where any of the devs are :P
[15:27] <didrocks> - on demand release, with a merge in a branch that is our "ubuntu trunk"
[15:27]  * didrocks is on 100 scopes, not really on that as a matter of urgency TBH
[15:58] <mlankhorst> Laney: then suddenly it was 10°c here o.O
[17:24] <jbicha> seb128: I guess bug 1153567 is approved then? I have the .plka we need for setting the hostname in gnome-control-center
[17:25] <ubot2> Launchpad bug 1153567 in ubuntu-system-service (Ubuntu) "[FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code" [Low,Triaged] https://launchpad.net/bugs/1153567
[17:25] <seb128> jbicha, it's approved yes ...profiles should be in the desktop-privelege package, not in the sources
[17:26] <jbicha> seb128: but this .plka is just a rewrite of the one included in gnome-control-center since we're not using the new policykit for raring
[17:26] <seb128> 3.6 depends on the new polkit?
[17:26] <seb128> that doesn't make sense
[17:26] <seb128> the new polkit was out yet at the time?
[17:27] <jbicha> yes and of course GNOME uses the latest stuff they can...
[17:28] <jbicha> on the other hand I hit bug 1156074 which should block the systemd-services transition
[17:28] <ubot2> Launchpad bug 1156074 in xserver-xorg-video-intel (Ubuntu) "[raring] after updates, i965 driver won't load" [Undecided,Incomplete] https://launchpad.net/bugs/1156074
[17:29] <seb128> jbicha, that's a kernel bug afaik
[17:29] <seb128> nothing to do with systemd-services
[17:33] <Laney> pitti: still here perchance?
[17:34] <Laney> I notice that you never get PrepareForSuspend(false) signalled from logind after resuming and I'm wondering if that's because of the fallback pm-utils stuff
[17:34]  * Laney does a little hax
[17:36] <jbicha> seb128: well the problem that I saw was that I had systemd-services installed without libpam-systemd
[17:38] <seb128> jbicha, would need to check with pitti, there is a second FFE about logind
[17:38] <Laney> that will get seeded
[17:38] <seb128> see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1153224
[17:38] <ubot2> Launchpad bug 1153224 in systemd "[FFE] Move to logind for session tracking" [Wishlist,New]
[17:39] <seb128> we will either to transition to logind
[17:39] <seb128> or drop it from syste
[17:39] <seb128> or drop it from systemd-services
[17:40] <jbicha> ok I'll just wait then unless you had somewhere you wanted me to put my g-c-c patch
[17:42] <seb128> jbicha, no I didn't, thanks
[17:54] <chrisccoulson> jibel, did you say that the autopkgtests are done with 1GB or 2GB of RAM?
[17:54] <jibel> chrisccoulson, 2
[17:55] <chrisccoulson> jibel, and there's no swap either?
[17:55] <jibel> chrisccoulson, no swap
[17:56] <chrisccoulson> jibel, i wonder whether the tests do hi OOM. i'm trying to figure out random failures like https://jenkins.qa.ubuntu.com/job/raring-ppa-adt-ubuntu_mozilla_daily_ppa-firefox-trunk/ARCH=i386,label=adt/lastCompletedBuild/testReport/dom.media.tests/mochitest/test_peerConnection_bug840344_html/, but they don't happen when i run locally with 4GB
[17:56] <chrisccoulson> and that test failure was followed shortly afterwards by a crash
[17:56] <chrisccoulson> which is suspicious...
[17:57] <chrisccoulson> jibel, in fact, at the bottom of the log:
[17:57] <chrisccoulson> out of memory: 0x0000000000070800 bytes requested
[17:57] <chrisccoulson> i didn't notice that before ;)
[17:58] <jibel> chrisccoulson, that's what I suspect too but didn't do much investigation. I'll increase the amount of memory for firefox tests
[17:59] <chrisccoulson> jibel, thanks
[18:08]  * didrocks waves good evening
[18:11] <jbicha> seb128: gnome-calculator 3.7.92 is out with the renamed .desktop, do you need to fix the Unity test again before I upload?
[18:11] <seb128> likely yes
[18:11] <seb128> mterry, cyphermox: ^
[18:12] <seb128> some test is using gnome-calculator.desktop, we will need them back on gcalctool.desktop
[18:14] <Laney> pitti: Hmm, so you only get the False ones in response to an org.freedesktop.systemd1.Manager JobRemoved signal but we'll never have that
[18:29] <cyphermox> seb128: ok
[18:41] <mterry> seb128, guh
[18:41] <seb128> mterry, don't give me that guh look!
[18:41] <seb128> ;-)
[18:42] <mterry> cyphermox, are you doing that or shall I?
[18:49] <cyphermox> mterry: I can
[19:10] <cyphermox> seb128: where do these tests live? unity?
[19:11] <jbicha> cyphermox: https://code.launchpad.net/~sil2100/unity/autopilot_gcalctool_rename/+merge/151063
[19:13] <cyphermox> ok, just reverting that?
[19:13] <jbicha> yes please
[19:17] <cyphermox> jbicha: is there a bug open for that?
[19:27] <seb128> cyphermox, what was just said ;-)
[19:28] <cyphermox> I suck?
[19:31] <cyphermox> seb128: sorry, I don't follow what you mean by that
[19:34] <chrisccoulson> hi jibel, any idea why the links to the 2 test failures on https://jenkins.qa.ubuntu.com/job/raring-ppa-adt-mozillateam_firefox_next-firefox/4/ARCH=i386,label=adt/ give a 404?
[19:49] <seb128> cyphermox, sorry, walked by between dinner and dessert ;-)
[19:49] <cyphermox> yeah, is fine
[19:49] <seb128> cyphermox, I was just acking the "just need to revert that commit once gnome-calcultator is updated"
[19:49] <cyphermox> so you mean you mentioned the bug aleady? I can't see it
[19:49] <cyphermox> ok
[19:49] <cyphermox> when is that going to be done?
[19:49] <seb128> whenever you wants
[19:49]  * cyphermox doesn't especially like that kind of X depends on Y
[19:50] <cyphermox> it gets more painful with daily release
[19:50] <seb128> that's a trivial .90 -> .92 GNOME update
[19:50] <cyphermox> ok
[19:50] <cyphermox> but we're fixing a bug; this is after feature freeze
[19:50] <cyphermox> I'd just want it to be tracked for the commit too
[19:50] <seb128> cyphermox, if you are ready to get the unity test updated just tell jbicha that it's ok to upload gnome-calculator
[19:51] <seb128> cyphermox, it's a bit unfortunate that there was this renaming and renaming back on the .desktop unity picked for its tests
[19:51] <cyphermox> is that only going to be run for unity or are other things using unity's autopilot tests, beside indicators?
[19:51] <seb128> just reverting the commit mentioned before
[19:51] <seb128> that was the only one
[19:53] <cyphermox> ok
[19:54] <jibel> chrisccoulson, there is a delay between the notification (sent by the internal server) and the results on the public instance
[19:55] <chrisccoulson> jibel, ah, thanks
[20:08] <jbicha> cyphermox: no we hadn't a filed a bug on the Ubuntu side for the issue
[20:19] <cyphermox> jbicha: that's fine, I did
[20:36] <cyphermox> mterry: wanna review? https://code.launchpad.net/~mathieu-tl/unity/revert-gcalctool/+merge/153923
[20:36] <mterry> cyphermox, sue
[20:36] <mterry> sure
[20:37] <cyphermox> thanks
[22:06] <marga> desrt, you around?  It's me with weird issues again :)
[22:06] <marga> Two users are telling me their screensavers left the bus during the weekend.  I got one apport report from one of them, and apparently it's dconf related: http://paste.ubuntu.com/5626553/
[22:07] <marga> With "left the bus" I mean this syslog error message: gnome-session[4387]: WARNING: Detected that screensaver has left the bus
[22:07] <desrt> 'left the bus' :)
[22:07] <desrt> hmm.
[22:07] <desrt> i'm not sure that's a serious problem?
[22:08] <marga> yeah, that's a very weird message.  It's associated with signal 7 (Bus Error)
[22:08] <desrt> are you using NFS?
[22:08] <desrt> or ecryptfs...
[22:09] <marga> maybe :)
[22:09] <desrt> sigbus in dconf code is almost always (maybe _always_) caused by the user not having a fully-functional XDG_RUNTIME_DIR
[22:09] <marga> it's possible that the kerberos credentials timed out or something similar.
[22:09] <desrt> since you're on precise i assume that XDG_RUNTIME_DIR is not setup properly
[22:09] <marga> let me check taht.
[22:09] <desrt> so that means that the user's homedir is used as a fallback
[22:09] <desrt> if ~ is NFS or ecryptfs you will get bus errors from time to time
[22:10] <marga> yes, at least in one case ~ is NFS
[22:10] <desrt> dconf grew improved NFS support this cycle
[22:10] <marga> confirmed for the other user as well.
[22:10] <desrt> but only if XDG_RUNTIME_DIR is supported :(
[22:11] <desrt> and i guess it doesn't help you anyway if you're stuck on precise
[22:11] <marga> But we have like half our users on NFS, and we don't have all the screensavers leaving the bus
[22:12] <desrt> i think 'left the bus' is my new favourite euphemism for 'failed horribly'
[22:12] <marga> :)
[22:13] <desrt> this issue has been known to periodically occur with NFS or ecryptfs for a while
[22:13] <desrt> basically it happens when a file on the NFS server gets replaced and the clients are left looking at a stale copy
[22:13] <desrt> with read() or write() you would get ESTALE
[22:13] <marga> you mean the .dconf copy?
[22:13] <desrt> but with mmap() you get SIGBUS
[22:14] <desrt> i mean the dconf database file
[22:14] <marga> ok
[22:14] <desrt> are you sort of going through old dconf bugs lately and you found these?
[22:14] <desrt> or did both of them just happen all of the sudden?
[22:15] <marga> This happened this weekend.
[22:15] <desrt> huh
[22:15] <marga> 2 users in the same weekend.
[22:15] <desrt> and you never saw it before?
[22:15]  * desrt wonders what changed....
[22:15] <marga> So for this to happen, they would need to have accessed their dconf settings from some other machine, right?
[22:15] <desrt> maybe.  i'm not entirely clear on what happens here.
[22:15] <marga> It might be that they haven't been running precise for long.  We just finished the migration.
[22:16] <marga> Let me check that
[22:16] <desrt> when a client has open file handles and it deletes or replaces the open file, it's supposed to do this weird renaming trick
[22:16] <desrt> so that fixes the problem if you make the change from the same machine
[22:16] <desrt> it's indeed possible that multiple logins could be the cause of this
[22:17] <marga> So, one of them is a very recent precise user, the other one has been using precise for more than 6 months.
[22:17] <desrt> heh
[22:19] <desrt> anyway... i'm just about to head out for the night
[22:19] <desrt> but we've known about this issue for a very long time
[22:19] <desrt> getting an SRU to fix precise might be difficult but we could discuss what to do
[22:19] <marga> Ok, I'll keep digging into this, thanks for the imput.
[22:19] <marga> input
[22:19] <desrt> find out about the XDG_RUNTIME_DIR variable being set (or not) on precise
[22:19] <desrt> and file a bug with all the infos
[22:19] <desrt> ciao
[23:57] <cyphermox> jbicha: still around?
[23:59] <jbicha> cyphermox: yes
[23:59] <cyphermox> jbicha: did you upload gnome-calculator? I'd be approving the merge for unity tests, so that would land soonish