[00:58] <smspillaz> morning all
[00:59] <smspillaz> any emergencies ?
[01:14] <jasoncwarner_> smspillaz: I saw some compiz crashers over the weekend...not sure of the bug #s. let me see if I can find them.
[01:14] <jasoncwarner_> smspillaz: not sure if compiz or nux
[01:15] <smspillaz> I fixed most of the ones I could find, so we should have distro patches ready to do for that
[01:16] <jasoncwarner_> smspillaz: hmm...seems mine didn't get filed...I'm going to pastbin my crash file to see if you knew about it
[01:16] <smspillaz> kk
[01:16] <jasoncwarner_> smspillaz: also still getting a ccsm crash every time I open that app..
[01:16] <smspillaz> I wonder if we've got the latest compizconfig-python
[01:17] <jasoncwarner_> smspillaz: ccsm crasher http://paste.ubuntu.com/701343/
[01:17] <jasoncwarner_> smspillaz: compiz is takign some time to pastebin...big crash file ;)
[01:18] <smspillaz> heh
[01:18] <smspillaz> yeah, so I've fixed that upstream
[01:18] <smspillaz> http://git.compiz.org/compiz/compizconfig/compizconfig-python/commit/?id=7c28ad895a34744d3c238b9931027f6ff2510b11
[01:18] <smspillaz> I wonder if it ever got merged downstream
[01:19] <jasoncwarner_> smspillaz: compiz crasher http://paste.ubuntu.com/701345/
[01:19] <smspillaz> jasoncwarner_: did you paste the .crash ?
[01:20] <jasoncwarner_> smspillaz: I did, the last link...
[01:20] <smspillaz> ah
[01:20] <jasoncwarner_> smspillaz: not coming up?
[01:20] <smspillaz> you'll probably just want to find the backtrace section
[01:20] <smspillaz> and paste that in future ;-)
[01:20] <smspillaz> yeah, that's nux
[01:21] <jasoncwarner_> smspillaz: is it known already? and fixed/fixable?  :)
[01:21] <jasoncwarner_> smspillaz: are there other crashers out there that you are aware of?
[01:21] <smspillaz> seen that a few times myself though I'm in lapcooke^Wnouveau, so I thought that maybe it was the driver being stupid (since fglrx was crashing in the same function due to advertising wrong opengl support)
[01:21] <smspillaz> but I'll pass that on to jay
[01:22] <smspillaz> jasoncwarner_: not that I'm aware of
[01:22] <jasoncwarner_> smspillaz: ok
[01:22] <jasoncwarner_> smspillaz: I noticed something
[01:22] <jasoncwarner_> CTRL+ALT+SHIFT and arrow to move a window to another workspace?
[01:22] <jasoncwarner_> you know of which I speak?
[01:24] <jasoncwarner_> in one of the latest updates of compiz this went from being a "smooth" process, to the window you are moving jerking around...feels a bit woobly or herky-jerky
[01:25] <jasoncwarner_> smspillaz: ^^
[01:28] <smspillaz> yeah, it's not fixable unfortunately
[01:29] <smspillaz> I basically had to make it that way in order to fix a stacking bug
[01:29] <smspillaz> next cycle it will be, but I need to break some APIs
[01:30] <smspillaz> basically, that happens if the window tries to resize itself while it is changing viewports, in that case we force asynchronous movement, which is dependent on how fast your server is
[01:30] <jasoncwarner_> smspillaz: is there a bug you are tracking for that already?
[01:30] <smspillaz> probably not, but it's one of the first things I'm going to get on to wwhen I can start breaking the API again
[01:31] <smspillaz> oddly enough, it's quite smooth here, so maybe you're missing something that I have
[01:31] <smspillaz> *shrug*
[01:33] <smspillaz> (using synchronous movement while a winow is being resized server side is dangerous and can cause undefined behaviour / window stacking problems
[05:51] <rickspencer3> pitti, jasoncwarner_, what's the word on the street?
[05:51] <rickspencer3> release looking good?
[05:52] <jasoncwarner_> rickspencer3: pitti likely won't be online today. German something or other. Unification day, maybe?
[05:52] <rickspencer3> jasoncwarner_, sounds nice :)
[05:52] <jasoncwarner_> rickspencer3: I've been testing it all weekend and feeling pretty solid to me. reported a nux / compiz crasher to smspillaz (who is working with jay to fix it).
[05:53] <rickspencer3> I wonder if it's a French holiday?
[05:53] <jasoncwarner_> but that was the only thing for me.
[05:53] <rickspencer3> jasoncwarner_, yeah, I hit that crasher yesterday
[05:53] <rickspencer3> jasoncwarner_, an Gwibber is not working well for me
[05:53] <jasoncwarner_> rickspencer3: oh? what is going on with gwibber?
[05:53] <rickspencer3> jasoncwarner_, let me find my bug
[05:54] <rickspencer3> bug #864727
[05:54] <ubot2> Launchpad bug 864727 in gwibber "Gwibber failing to start, or starting very very slowly" [Undecided,New] https://launchpad.net/bugs/864727
[05:55] <RAOF> There's also bug #863303 which I've hit a couple of times today, but that's apparently fixed in trunk.
[05:55] <ubot2> Launchpad bug 863303 in nux "compiz assert failure: *** glibc detected *** compiz: free(): corrupted unsorted chunks: 0x0000000004a1d390 ***" [High,Confirmed] https://launchpad.net/bugs/863303
[05:55] <jasoncwarner_> yuck, neither of those look like fun.
[05:56] <rickspencer3> RAOF, that was the bug I was getting
[05:56] <RAOF> And when didrocks gets in, I'll ping him about it; the unity/compiz release process is full of special-cases only he knows about.
[05:56] <rickspencer3> is there *another* compiz/nux crasher?
[05:57] <RAOF> rickspencer3: Not that I've hit recently.
[05:57] <jasoncwarner_> rickspencer3: that is the one I was getting as well.
[05:57] <rickspencer3> phew
[05:57] <rickspencer3> the Gwibber one is a bit more minor, I think
[05:57] <rickspencer3> jasoncwarner_,  the other one is that one where certain windows don't get decorated
[05:58] <rickspencer3> bug #861143
[05:58] <ubot2> Launchpad bug 861143 in unity "unity 3d firefox window borders disappear" [Critical,In progress] https://launchpad.net/bugs/861143
[06:00] <jasoncwarner_> rickspencer3: that is still happening for you? can you get it pretty consistently?
[06:00] <rickspencer3> jasoncwarner_, nah, it never really happened to me
[06:00] <rickspencer3> maybe just with gwibber last night
[06:03] <smspillaz> jasoncwarner_ i have fixed that
[06:04] <jasoncwarner_> smspillaz: the nux crasher?
[06:04] <smspillaz> no. the firefox issue
[06:12] <jbicha> smspillaz: should maximized windows show a title bar when viewed in spread mode (or whatever you call it)?
[06:13] <jbicha> like when I have 2 terminals open, one maximized and one windowed and I click the terminal icon in the launcher
[06:21] <didrocks> good morning
[06:22] <jasoncwarner_> hey didrocks
[06:22] <didrocks> hey jasoncwarner_, how was your week-end?
[06:22] <jasoncwarner_> didrocks: pretty good, thanks! you?
[06:23] <didrocks> jasoncwarner_: was nice, thanks :)
[06:23] <jasoncwarner_> how was your system? stable all weekedend ?  ;)
[06:23] <didrocks> well, I have check_gl_texture_size crashing, but apart from that, it's ok. you?
[06:24]  * didrocks makes dist-upgrades of the week-end there
[06:24] <jasoncwarner_> didrocks: oh? RAOF , see what didrocks just said?
[06:24] <RAOF> didrocks: Oh, hey?  What's happening there?
[06:24] <jasoncwarner_> didrocks: some of us got a nux crasher as well. https://launchpad.net/bugs/863303
[06:24] <ubot2> Launchpad bug 863303 in nux "compiz assert failure: *** glibc detected *** compiz: free(): corrupted unsorted chunks: 0x0000000004a1d390 ***" [High,Confirmed]
[06:25] <didrocks> RAOF: not sure, the crash is pretty random. I'm upgrading to let apport report a crash if I still get it
[06:25] <didrocks> jasoncwarner_: having a look
[06:25] <RAOF> didrocks: And is it affecting your session noticabley?
[06:26] <didrocks> RAOF: yeah, it can prevent compiz starting
[06:26] <RAOF> I don't know how that could happen :)
[06:27] <didrocks> jasoncwarner_: ok, it's fixed in trunk apparently, will look to backport some commit today for tomorrow
[06:27] <didrocks> RAOF: well, maybe just a coincidence :)
[06:28] <RAOF> You're now the second person to complain of this; the other is https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/824099/comments/19
[06:28] <ubot2> Launchpad bug 824099 in gnome-desktop3 "Max GL texture size can break multi-head" [Undecided,Confirmed]
[06:29] <didrocks> RAOF: the description is totally what I experience
[06:29] <RAOF> Although *they* seem to have fixed things with a package upgrade; anything which kills GL can cause check_gl_texture_size to crash, and will likely also take down other GL clients, like Compiz.
[06:30] <jasoncwarner_> didrocks: could you get the problem on a consistent basis? after you upgrade, would you notice if the problem goes away?
[06:31] <didrocks> jasoncwarner_: it happened 3 times on 10 reboots, so yeah, will try that once the upgrade is over there
[06:34] <jasoncwarner_> didrocks: ok...
[06:34]  * jasoncwarner_ waits to see!
[06:37]  * RAOF also waits.
[06:38] <didrocks> RAOF: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/859632/comments/4 FYI
[06:38] <ubot2> Launchpad bug 859632 in compiz-plugins-main "package compiz-plugins-main-default 1:0.9.5.94 bzr20110919-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/compiz/grid.xml', which is also in package compiz-plugins 1:0.9.4 bzr20110606-0ubuntu1~natty2" [High,Fix released]
[06:38] <didrocks> (still upgrading)
[06:40] <RAOF> didrocks: Ta.
[06:41] <RAOF> Oh, hah!  Upgrades from natty-proposed.
[06:41] <RAOF> Slash natty-updates.
[06:44] <didrocks> RAOF: got the same issue with compiz :p
[06:47] <jibel> didrocks, salut. I get bug 863717 on 2 different systems. is it a known issue ?
[06:47] <ubot2> Launchpad bug 863717 in oneconf "oneconf-service crashed with HTTPError in __negotiatehttp(): (403, 'Forbidden')" [Undecided,New] https://launchpad.net/bugs/863717
[06:51] <didrocks> jibel: salut, oh no, let me have a look
[06:52] <didrocks> jibel: do you have a proxy?
[06:52] <jibel> didrocks, yes
[06:52] <didrocks> and is it the same when you try to make a review
[06:52] <didrocks> jibel: it's piston, mvo did some changes last week for proxy support
[06:52] <jibel> didrocks, a review ? I get it when I update the package cache.
[06:52] <didrocks> jibel: I bet you have the same crash when you do a review in software-center
[06:53] <didrocks> (the same piston component is used)
[06:54] <jibel> didrocks, I can't try, s-c crashed on launch :(
[06:54] <didrocks> jibel: argh, anyway, thanks! I'll let mvo knows about piston
[06:55] <jibel> didrocks, mvo bug 865076
[06:55] <ubot2> Launchpad bug 865076 in software-center "software-center crashed with TypeError: Couldn't find conversion for foreign struct 'cairo.Context'" [Undecided,New] https://launchpad.net/bugs/865076
[07:01] <didrocks> jibel: I'll let him know
[07:01]  * didrocks reboots now with the upgrade
[07:07] <smspillaz> hi @ all
[07:12] <didrocks> RAOF: jasoncwarner_: after 7 log off and reboot, I can't reproduce it anymore, so seems good
[07:12] <didrocks> jasoncwarner_: for the other crash, I'll try to gather something to upload for tomorrow morning. We can't just take trunk, there are already stuff that we can't ship in oneiric (design changes…)
[07:24] <jasoncwarner_> didrocks: ok, the nux crasher is the other one. Hope that gets fixed right quick!
[07:25] <didrocks> jasoncwarner_: the one you pointed me this morning, isn't it? if it's the case, I found the commit in trunk, but I want to see with njpatel to make a big upload with only crasher fixes
[07:50] <czajkowski> aloha
[07:59] <seb128> hey
[08:01] <didrocks> salut seb128
[08:01] <seb128> lut didrocks, ca va ? passé un bon w.e?
[08:01] <didrocks> seb128: ça va, et toi?
[08:02] <seb128> ça va bien! ;-)
[08:06] <czajkowski> didrocks: cant find that bug I logged the other day but still happening the alt tabbing switcher display freezes. Also any idea why the default to alt tabbing is SOOO_SLOW!
[08:06] <didrocks> czajkowski: nvidia card?
[08:06] <czajkowski> nope
[08:06] <didrocks> a lot of windows opened?
[08:07] <czajkowski> nope and in 2D as it is painful in 3d
[08:07] <didrocks> just slow or the whole display freezes?
[08:07] <didrocks> oh
[08:07] <czajkowski> slow as feck
[08:07] <rodrigo_> morning
[08:07] <didrocks> 2d has no change for alt + tab
[08:07] <didrocks> it's still the metacity one, without any preview
[08:07] <czajkowski> didrocks: ah ok
[08:08] <didrocks> so, I would tell something else is bad on your setup then
[08:08] <czajkowski> didrocks: grand, there just seems to be too slow a delay between alt to the next applciation
[08:08] <didrocks> czajkowski: hum? please define "slow" then :)
[08:08] <czajkowski> didrocks: 5 seconds before I can get to another aplication
[08:09] <didrocks> czajkowski: yeah, something bad is happening then
[08:09] <didrocks> czajkowski: and same thing in -2d?
[08:09] <czajkowski> yes
[08:10] <didrocks> no clue at all then, it's neither compiz/metacity, maybe just a slow display in general,
[08:10] <didrocks> ?
[08:11] <czajkowski> wasn't before in natty.
[08:11] <czajkowski> shall go fiddle around with settings and see if it helps
[08:11] <didrocks> czajkowski: hum, as you can get that across compiz and metacity, I really have no idea, nothing else is slow in your display?
[08:11] <czajkowski> nope nothing
[08:12] <didrocks> waow, weird, RAOF any idea? ^
[08:13] <czajkowski> didrocks: aye indeed, not as weird as updating on friday, finding my desktop image gone, and my default settings for watching movies gone from vlc. I think my laptop likes to drive me bonkers
[08:13] <didrocks> yeah :-) after today's update, is it better for those issues?
[08:13] <seb128> hey rodrigo_
[08:14] <rodrigo_> hi seb128
[08:14] <seb128> rodrigo_, how are you?
[08:14] <rodrigo_> seb128, fine and you?
[08:14] <didrocks> hey rodrigo_
[08:14] <rodrigo_> hi didrocks
[08:14] <seb128> rodrigo_, I'm good thanks ;-)
[08:14] <seb128> rodrigo_, you didn't upload g-s-d on friday? :-(
[08:14] <rodrigo_> seb128, no, dont have the fix for bug 863038 yet
[08:14] <ubot2> Launchpad bug 863038 in gnome-settings-daemon "If turnoff the screen setting set to 'never' screen turns off instantly" [Undecided,In progress] https://launchpad.net/bugs/863038
[08:15] <rodrigo_> I've been having a look this weekend also, so hopefully will have it fixed today
[08:15] <seb128> rodrigo_, we should have done an upload for the "suspend on idle default value"
[08:15] <rodrigo_> seb128, oh
[08:15] <seb128> rodrigo_, we got some rc bugs on the w.e and people really freak out about it
[08:15] <rodrigo_> should I do an upload now?
[08:16] <seb128> rodrigo_, it also seems that setting the key is not enough, some boxes still suspend but that's hard to say without landing the default value change and see if issues remain
[08:16] <Laney> is that bug 864479 ?
[08:16] <ubot2> Launchpad bug 864479 in gnome-control-center "System goes to hibernate or suspend even when set to "Don't suspend"" [Critical,Confirmed] https://launchpad.net/bugs/864479
[08:16] <seb128> rodrigo_, yes please, we already lost 2 days of testing
[08:16] <rodrigo_> ok
[08:16] <seb128> Laney, that bug is a duplicate of bug #860485 but yes
[08:16] <ubot2> Launchpad bug 860485 in gnome-settings-daemon "bad default setting: suspend after 30min when plugged in" [Critical,Fix committed] https://launchpad.net/bugs/860485
[08:17] <Laney> hm? that bug seems to be about the default
[08:17] <Laney> but the one I linked is about not respecting the setting even when manually set
[08:17] <seb128> Laney, well it started about the default and then we noticed that it was still buggy even with the correct value
[08:18] <seb128> Laney, so the bug evolved a bit, we should update the title ... or use the other one
[08:18] <seb128> either way, it doesn't matter much which one of the 2 we use, "known issue"
[08:18] <Laney> right
[08:18] <seb128> Laney, did you set the setting with the ui or with gsettings,dconf-editor?
[08:18] <Laney> dup and fix the title then
[08:18] <Laney> ui
[08:19] <seb128> Laney, can you check the value of your keys?
[08:19] <Laney> sorry I can't, I'm away from the laptop
[08:19] <Laney> cjwatson was having the issue though: ^^^
[08:19] <seb128> bah unity focus...
[08:19] <seb128> Laney, gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout
[08:20] <rickspencer3> anybody know what this is referring to? http://www.thisisthecountdown.com/
[08:20] <seb128> rickspencer3, Oneiric? ;-)
[08:20] <didrocks> that was my guess as well…
[08:20] <rickspencer3> but, er, it's set for Tuesday next week?
[08:21] <seb128> seems wrong indeed
[08:22] <Laney> how about this one? http://thisisntthecountdown.com/
[08:23] <rickspencer3> dang
[08:24] <jbicha> Laney: my instinct on the second one was that it was a test site for the other one, & I'm guessing marketers can't count
[08:24] <Laney> haha
[08:24] <Laney> I thought it was some kind of troll / game
[08:24] <Laney> every time you refresh it you get a different time
[08:25] <Laney> eet eez a mystery
[08:26] <jbicha> nah, the mystery I'm beginning to worry about is what happened to the P announcement
[08:27] <Laney> maybe we're going to get a jobsian launch announcement
[08:29] <jbicha> hmm the countdown is now set to 0
[08:33] <jbicha> giggles at http://thisisthefinalcountdown.com/
[08:36] <didrocks> seb128: alt + key for gtk3 app is not fixed yet, isn't it?
[08:36] <seb128> didrocks, no, ted hinted that it was not an easy issue and that he might need to take Cody out for lunch to discuss it ;-)
[08:37] <didrocks> urgh ok :/
[08:37] <seb128> didrocks, in fact he has been looking for it without much luck before this cycle
[08:37] <seb128> we need a gtk guy...
[08:37] <seb128> he thinks it's an issue in gtk or gtk which changed how it works
[08:39] <didrocks> ok
[08:50] <jibel> I have 2 systems where Unity sometimes fails to start with "Compiz (opengl) - Fatal: GLX_EXT_texture_from_pixmap is missing" after a fresh installation. Is it known ?
[08:52] <didrocks> jibel: there is a bug about it, I pinged smspillaz on Friday
[08:54] <jibel> didrocks, do you have a bug number ?
[08:54] <jibel> I can't find it
[08:54] <didrocks> jibel: it was a local crash and I just pastebin a partial stack (was with a not packaged version, so couldn't get apport)
[08:54] <didrocks> jibel: please report the crash I'll add it to the milestone
[08:55] <jibel> didrocks, bug 851345
[08:55] <ubot2> Launchpad bug 851345 in compiz "compiz crashes on i915 graphic module with GLX_EXT_texture_from_pixmap is missing" [Critical,Confirmed] https://launchpad.net/bugs/851345
[08:55] <didrocks> jibel: thanks
[08:56] <didrocks> jibel: do you get that at every boot?
[08:56] <jibel> didrocks, no
[08:56] <didrocks> ok thanks
[08:56] <jibel> maybe once every 4 or 5 boots
[08:56] <seb128> I wonder if that couldn't be a lightdm issue
[08:57] <seb128> jibel, could you check with other things than compiz
[08:57] <seb128> or glxinfo?
[08:57] <seb128> just to see if xorg has a correct init
[08:57] <seb128> i.e if the issue is lightdm,xorg or compiz
[08:59] <RAOF> When I've asked people for details, I seem to recall that being due to not having permissions to access /dev/dri, so GL fails.
[08:59] <tjaalton> is there a key to press that prevents the sidebar from appearing? it's annoying when you need to work close to the border..
[09:00] <RAOF> ?LIBGL_DEBUG=verbose glxinfo? is the magical incantation (once in the session) to work that out.
[09:01] <tjaalton> ah, best to have the launcher on all the time
[09:01] <RAOF> That's what I do on my big monitor.
[09:03] <jibel> argh, I just lost the mouse, it becomes challenging to gather more information.
[09:04] <tjaalton> RAOF: yeah, this is "only" 24" but wide enough to have it always there
[09:06] <RAOF> That's the size of my monitor; it's pretty much big enough.
[09:06] <RAOF> :)
[09:07] <tjaalton> big enough for my table anyway :)
[09:14] <jibel> here is the problem I think: libGL error: failed to open drm device: Permission denied
[09:14] <RAOF> Yup, there it is.
[09:15] <RAOF> jibel: Is that while in your session?
[09:15] <jibel> RAOF, yes
[09:15] <RAOF> Can you pastebin the output of ?ck-list-sessions??
[09:15] <seb128> RAOF, hey
[09:16] <RAOF> seb128: Ho!
[09:16] <seb128> RAOF, can you check bug #859836 and tell me from the xrandr log if that's an xorg, driver, etc issue?
[09:16] <ubot2> Launchpad bug 859836 in gnome-control-center "Monitors are not identified in Oneiric with radeon driver" [Low,Incomplete] https://launchpad.net/bugs/859836
[09:16] <RAOF> seb128: A fix for bug #865083 would be appropriate for upload now, right?  Either that or a 0-day SRU, but we can't pre-test them, right?
[09:16] <ubot2> Launchpad bug 865083 in xdiagnose "Breaks upgrades when natty-updates is enabled" [High,Confirmed] https://launchpad.net/bugs/865083
[09:18] <RAOF> seb128: They've got a broken install; they have neither ati nor fglrx loaded, so they're using fbdev which has no resolution-changing capabilities at all.
[09:18] <RAOF> seb128: I'll follow up on that bug.
[09:18] <seb128> RAOF, upload now I would said, if r-t disagree they will not let it in and ask you to sru
[09:18] <seb128> RAOF, but piti said bug fixes are fine until tomorrow
[09:18] <seb128> RAOF, thanks
[09:19] <RAOF> Np
[09:20] <jibel> RAOF, http://paste.ubuntu.com/701543/
[09:20] <RAOF> jibel: Just as I suspected, 	active = FALSE
[09:20] <jibel> I noticed that /home/ubuntu/.xsession-errors is owned by root.
[09:21] <RAOF> jibel: Something's not setting up the ConsoleKit session properly; you're not marked as active, so you don't have permissions to the DRI device.
[09:22] <RAOF> Ok, dinner time.
[09:22] <seb128> jibel, bug #863054
[09:22] <ubot2> Launchpad bug 863054 in lightdm "random login without common admin user permissions" [Undecided,New] https://launchpad.net/bugs/863054
[09:23] <seb128> jibel, I think it's a lightdm issue
[09:23] <seb128> bug #863119
[09:23] <ubot2> Launchpad bug 863119 in lightdm "~/xsession-errors is owned by root" [Undecided,New] https://launchpad.net/bugs/863119
[09:24] <seb128> jibel, could you add your infos to #863119?
[09:24] <jibel> seb128,  thanks, will do. it is annoying as it is a fresh installation.
[09:25] <jibel> seb128, #851345 is a duplicate ?
[09:25] <jibel> bug 851345
[09:25] <ubot2> Launchpad bug 851345 in compiz "compiz crashes on i915 graphic module with GLX_EXT_texture_from_pixmap is missing" [Critical,Confirmed] https://launchpad.net/bugs/851345
[09:25] <seb128> jibel, well I'm not 100% sure but I would guess that lightdm is not setting up the session properly
[09:25] <seb128> RAOF, ^ can you make sure that robert_ancell is aware of that bug tomorrow?
[09:26] <seb128> RAOF, I've difficulties catching him up online, his IRC hours are not very european friendly
[09:26] <seb128> RAOF, enjoy your dinner ;-)
[09:26] <seb128> jibel, can you add comments in each bug to cross references them maybe and robert_ancell can decide on what to do tomorrow
[09:30] <seb128> RAOF, I would appreciate if you can look to bug #864505 as well
[09:30] <ubot2> Launchpad bug 864505 in gnome-control-center "[Oneiric] Cannot setup dual monitor with AMD 5870" [Undecided,New] https://launchpad.net/bugs/864505
[09:30] <seb128> "The selected configuration for displays could not be applied"
[09:30] <seb128> "requested position/size for CRTC 148 is outside the allowed limit: position=(1680, 0), size=(1680, 1050), maximum=(1920, 1920)"
[09:31] <seb128> we got several bugs like that
[09:31] <seb128> those are driver limitations right?
[09:34] <seb128> rodrigo_, btw maybe you could check the upstream patch for bug #841280 then go back to the other things you are debugging?
[09:34] <ubot2> Launchpad bug 841280 in gnome-control-center "gnome-control-center crashed with SIGSEGV in count_languages_and_territories()" [Critical,Confirmed] https://launchpad.net/bugs/841280
[09:35] <seb128> rodrigo_, it seems that it should be easy to review that one and maybe get it in if it makes sense
[09:35] <seb128> then go back to the non trivial bugs ;-)
[09:40] <rodrigo_> seb128, yes
[09:41] <seb128> rodrigo_, thanks!
[09:41] <Laney> i think i have a lead on that tomboy blocking shutdown bug btw
[09:43] <RAOF> Laney: Is D-Bus# not delivering signals?
[09:45] <RAOF> seb128: That guy has just broken his install in so many ways :)
[09:45] <seb128> RAOF, ;-)
[09:46] <seb128> RAOF, bug #856312 is similar, also a driver thing?
[09:46] <ubot2> Launchpad bug 856312 in xorg-server "Cant set resolution with two monitors" [Undecided,Confirmed] https://launchpad.net/bugs/856312
[09:47] <seb128> RAOF, i.e https://launchpadlibrarian.net/81553241/Screenshot%20at%202011-09-22%2008%3A19%3A19.png
[09:47] <seb128> RAOF, not sure how the capplet could handle those better
[09:47] <RAOF> It could say "Stop using nomodeset, you moron"
[09:48] <Laney> that's what it might be, yes. I'm going to instrument it to see.
[09:48] <RAOF> I mean, that wouldn't be *helpful*, but it would point sufficiently technical users in the right direction :)
[09:49] <seb128> RAOF, ;-)
[09:50] <RAOF> Oh, no?  They're using fglrx?  I thought that worked reasonably :)
[09:51] <RAOF> Laney: Because at one point I was diving into why Do's Banshee plugin was blocking on load, and it looked like it was because Banshee.CollectionIndexer was never getting the "done" signal.  But I ran out of gumption at that point.
[09:52] <Laney> I'll let you know what I find out.
[10:04] <RAOF> Oh, speak of the devil!  Good morning tseliot :)
[10:04] <tseliot> RAOF: good morning to you. What's up?
[10:05] <RAOF> tseliot: I'm confused by bug #856312.  I didn't think fglrx had that sort of framebuffer restriction.
[10:05] <ubot2> Launchpad bug 856312 in xorg-server "Cant set resolution with two monitors" [Undecided,Confirmed] https://launchpad.net/bugs/856312
[10:06] <RAOF> tseliot: Specifically - it seems to be capping the Virtual size to a square based on the initial monitor configuration.  Which is what the UMS radeon drivers did, but the Xorg.0.log shows fglrx apparently loading happily.
[10:06] <tseliot> RAOF: it doesn't, as long as you use AMD's control panel ;)
[10:06] <RAOF> tseliot: With the corollory that it *does* if you don't use AMD's control panel?!
[10:07] <tseliot> RAOF: yes, I guess so
[10:07] <RAOF> ?
[10:08] <RAOF> Ok.  I'll close out that bug then, I guess.
[10:08] <tseliot> RAOF: I suspect it's a bug in their RandR implementation
[10:08] <RAOF> That would seem likely, yes.
[10:08] <tseliot> but you're really supposed to use their control panel, as with Nvidia
[10:09] <RAOF> ? Is it wicked when you smile / even though you feel like crying ?
[10:10] <tseliot> :)
[10:11] <seb128> tseliot, if they are supposed to do that maybe our control center should list the ati tool and not the GNOME one
[10:12] <tseliot> seb128: I think we used to have a patch for the display app to tell users to launch either nvidia-settings or the AMD panel instead, when it detected one of these drivers
[10:13] <RAOF> That might be something worth resurrecting.
[10:13] <seb128> well I think we dropped it because those drivers were supposed to understand xrandr nowadays
[10:13] <RAOF> nvidia doesn't.
[10:13] <seb128> :-(
[10:13] <seb128> suckers!
[10:13] <tseliot> seb128: Nvidia still doesn't and AMD's implementation has some limitations
[10:13] <tseliot> :)
[10:14] <RAOF> Although we could *technically* write a gnome-desktop backend which would talk NV-GLX; the code's already there in nvidia-settings.
[10:14] <tseliot> RAOF: true, and I could also bug AMD about that bug
[10:15] <RAOF> Yes, please!
[10:15] <tseliot> ok, I will
[10:16] <RAOF> I'll assign that bug to you so it shows up on your radar.
[10:16] <tseliot> thanks
[10:17] <seb128> tseliot, RAOF: thanks
[10:17] <tseliot> thanks for bringing this up
[10:48] <seb128> RAOF, tseliot: on bug #856312 the reported said he couldn't use the ati tools because it segfault on start iirc
[10:48] <ubot2> Launchpad bug 856312 in fglrx-installer "Cant set resolution with two monitors" [Medium,Confirmed] https://launchpad.net/bugs/856312
[10:49] <seb128> bug #647802 he pointed
[10:49] <seb128> he opened bug #862885 which got dupped
[10:49] <tseliot> seb128: that would be a bug in the AMD control panel, which I can report too
[10:50] <seb128> tseliot, that bug collects duplicates it seems
[10:50] <seb128> tseliot, so yeah, would be nice to report it if you can ;-) thanks
[10:51] <tseliot> seb128: a duplicate of a private bug??
[10:51] <seb128> tseliot, the retracer dupped it
[10:51] <seb128> tseliot, do you have access to #647802 or should I subscribe you?
[10:53] <tseliot> seb128: please subscribe me
[10:56] <seb128> tseliot, done
[10:56] <seb128> lunch, bbl
[10:57] <tseliot> seb128: thanks
[12:23]  * rodrigo_ lunch
[12:30] <seb128> hey mterry, wb
[12:30] <seb128> mterry, back to work today?
[12:30] <mterry> seb128, yup!  Which so far means reading emails
[12:31] <seb128> mterry, how was your week off?
[12:32] <mterry> seb128, good!  Relaxing, just sat around in the sun and drank
[12:32] <seb128> mterry, sounds like my w.e ;-)
[12:32] <seb128> we have very nice autumn weather this year
[12:32] <seb128> it's rather summer weather in fact
[12:33] <mterry> seb128, nice, grab it while you can
[12:34] <seb128> indeed ;-)
[12:34] <seb128> pedro_, hola!
[12:35] <seb128> pedro_, how do I open a bug about your qa bugs pages? "Updated on: 2011-10-03 12:03:03.357854 ", I think the time is not exact enough
[12:35] <seb128> pedro_, we need better precision than the 1uS there
[12:35] <seb128> ;-)
[12:38] <seb128> mterry, if you get bored after catching up and want some bugs ping me ;-) or just grab those in the oneiric list, I'm adding an oneiric component to some I think are worth fixing still or sruing
[12:38] <mterry> seb128, ok, in pedro's list or the release team one?
[12:39] <seb128> mterry, is there a release team list? our bug tracking is confusing :-(
[12:39] <seb128> mterry, they should show up on pedro's oneiric section
[12:39] <seb128> not sure about r-t
[12:39] <mterry> seb128, not sure what it's called: http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-o-tracking-bugs.html
[12:39] <seb128> I'm just doing "target to serie: oneiric"
[12:39] <seb128> oh, those are manually tagged by r-t yes
[12:40] <seb128> that's a good list to pick in as well ;-)
[12:45] <pedro_> seb128, hey! , on which report page is that?
[12:46] <pedro_> seb128, each report has a cronjob that might be why you're seeing different times there, some take more to run
[12:46] <pedro_> like the assigned bugs one it takes almost 1 hour :-/
[12:46] <seb128> pedro_, http://reports.qa.ubuntu.com/reports/ubuntu-desktop/oneiric.html
[12:46] <seb128> pedro_, I was rather joking about the "03.357854" seconds
[12:46] <pedro_> haha
[12:47] <seb128> pedro_, we need to improve the accuracy ;-)
[12:47] <pedro_> sorry i spend too much time with the French mafia, they like to be really 'on time' ;-)
[12:47] <seb128> hum, why is chrisccoulson online?
[12:47] <seb128> pedro_, lol
[12:47] <seb128> pedro_, it's sure it's not the spanish mafia that would be on time!
[12:48] <chrisccoulson> clicked on the wrong button ;)
[12:48] <pedro_> seb128, amen to that, like always its rodrigo_'s fault
[12:48] <seb128> chrisccoulson, you said you wouldn't have internet access this week!
[12:48] <seb128> chrisccoulson, how are you? ;-)
[12:48] <chrisccoulson> seb128, i do. i didn't realize that our cottage would have free wifi
[12:48] <seb128> lol
[12:49] <seb128> chrisccoulson, you are screwed!
[12:49] <chrisccoulson> yeah, i'm good thanks. just waiting for my daughter to wake up from her afternoon nap
[12:49] <seb128> ;-)
[12:49] <chrisccoulson> lol
[12:52] <seb128> chrisccoulson, seems you are not the only one to be bad at not connection during days off
[12:52] <seb128> pitti is triaging some team assigned and rc bugs
[12:52] <seb128> while he's supposed to be off today :p
[12:53] <chrisccoulson> heh :)
[12:53] <seb128> chrisccoulson, how are your holidays otherwise? nice weather?
[12:53] <chrisccoulson> seb128, yeah, the weather is unseasonably nice
[12:54] <chrisccoulson> i've got the wrong clothes with me. it's meant to be autumn weather ;)
[12:57] <seb128> chrisccoulson, it's summer weather here as well
[12:58] <seb128> well that's changing on wednesday apparently
[12:58] <seb128> chrisccoulson, next cycle look to the forecast before going somewhere ;-)
[12:58] <chrisccoulson> yeah, we were expecting a couple of hot days then for it to change, but it's still quite hot today
[13:05] <dobey> rodrigo_: ping
[13:34] <didrocks> jibel: the crash is in piston, not oneconf, as told this morning. Today is off for german people, but I'll ping mvo tomorrow morning about it
[13:38] <jibel> didrocks, I moved it there.
[13:38] <didrocks> jibel: thanks
[13:45] <seb128> jjardon, hey
[13:46] <seb128> jjardon, is indicator-power dislaying a "non present" battery over a working one a bug in indicator-power?
[13:47] <seb128> jjardon, there is a kernel bug which makes a "ghost" battery to be listed on some dell laptop after suspend,resume, the issue is a kernel one but still that's the ghost one which is listed in the panel indicator
[13:47] <jjardon> seb128: hello
[13:47] <seb128> jjardon, shouldn't it be the real working on that should be preferred instead?
[13:47] <seb128> on->one
[13:48] <jjardon> seb128: Do you meen this? https://bugs.launchpad.net/indicator-power/+bug/863518
[13:48] <ubot2> Launchpad bug 863518 in indicator-power "Power indicator shows battery not present and the actually used battery at the same time" [Undecided,Fix committed]
[13:49] <seb128> jjardon, sort of, I would assume that having both listed is not really a bug in the indicator, it just lists what upower gives
[13:49] <seb128> jjardon, my concern was that it picks the non present one as the primary one
[13:49] <dobey> seb128: hi there :)
[13:49] <seb128> dobey, hey
[13:49] <jjardon> seb128: yeah, the bug is not in the indicator, but I commited a workaround anyway to try to fix this
[13:50] <seb128> jjardon, isn't there still a "ranking" bug in the indicator?
[13:50] <dobey> seb128: so i have this: https://code.launchpad.net/~dobey/ubuntu/oneiric/glib2.0/fix-804946/+merge/77939
[13:50] <seb128> jjardon, how do you determine which one is the one to list in the panel from the batteries available?
[13:51] <jjardon> in a normal case, depends of the charge level
[13:51] <seb128> dobey, check with desrt but I'm pretty sure he will not like it and tell you that it's an error in the "client" and not gsettings
[13:51] <jjardon> as the ghost battery has charge = 0 (first to be discharged), Its the battery to show
[13:52] <seb128> jjardon, hum, but shouldn't "not present" is not likely something discharching ;-)
[13:53] <dobey> hrmm, actually, now that i think about it a little more; i don't like that patch
[13:53] <jjardon> seb128: oh, you are rigth
[13:54] <seb128> dobey, what I think those bugs are is that there is a timeframe during the upgrade where the gsettings mmap is cleaned and the update not run, so you have no gsettings database
[13:54] <seb128> dobey, chrisccoulson suggested that we stop cleaning the cache on upgrade iirc
[13:54] <seb128> dunno what happened to that idea
[13:55] <seb128> jjardon, do you want a new bug "non-present batteries should not be preferred over present ones"?
[13:55] <jjardon> seb128: no, I'll fix it rigth now
[13:55] <seb128> jjardon, thanks ;-)
[13:56] <dobey> seb128: no, there are also cases where people don't provide schemas
[13:56] <jjardon> seb128: Do you think that we should show the ghost battery in the menu?
[13:56] <dobey> because it's a dumb hassle to do so in a lot of cases
[13:57] <seb128> dobey, you can't not provide a schemas with gsetting
[13:57] <seb128> jjardon, check with mpt maybe but my gut feeling would be "no"
[13:58] <seb128> jjardon, if the battery is not present it seems pointless to list it
[13:59] <dobey> seb128: well obviously it just crashes if you do
[14:01] <jjardon> seb128: yeah, I think the same. So with the current code the issue is fixed. Do you want to me to roll a new tarball?
[14:02] <dobey> seb128: anyway, i just made a MUCH simpler patch to fix the crashing.
[14:02] <seb128> jjardon, no that's fine thanks, we can backport the commit
[14:02] <seb128> dobey, can you still ping desrt on #gtk+ or #gnome-hackers for review? ;-)
[14:03] <jjardon> seb128: FYI http://bazaar.launchpad.net/~jjardon/indicator-power/master/revision/115
[14:03] <seb128> kenvandine, ^ can you maybe backport that?
[14:03] <kenvandine> hey
[14:03]  * kenvandine looks
[14:03] <seb128> kenvandine, it fixes bug #863518
[14:03] <ubot2> Launchpad bug 863518 in indicator-power "Power indicator shows battery not present and the actually used battery at the same time" [Undecided,Fix committed] https://launchpad.net/bugs/863518
[14:03] <dobey> seb128: yeah, i'm surprised he's not in here
[14:04] <kenvandine> seb128, jjardon: sure!
[14:04] <seb128> kenvandine, thanks
[14:04] <kenvandine> np
[14:06] <chrisccoulson> seb128, jjardon - isn't bug 863518 really a kernel bug? (ie, bug 852406)
[14:06] <ubot2> Launchpad bug 863518 in indicator-power "Power indicator shows battery not present and the actually used battery at the same time" [Undecided,Fix committed] https://launchpad.net/bugs/863518
[14:06] <ubot2> Launchpad bug 852406 in linux "Phantom battery appears after resume from suspend" [Undecided,Confirmed] https://launchpad.net/bugs/852406
[14:06] <dobey> hrmm, the new simpler patch, actually fixes more bugs. yay me :)
[14:07] <chrisccoulson> in any case, the fix for bug 863518 doesn't fix the issue of my laptop being immediately shut down on resume from suspend, due to gsd thinking my battery is critically low ;)
[14:08] <seb128> chrisccoulson, when did that start? I've read a bug about that this morning
[14:09] <chrisccoulson> seb128, not sure. it's been the case since i got my new laptop, which does apparently have a second battery slot
[14:09] <seb128> chrisccoulson, well it's a kernel bug but since the kernel will likely not be fixed for Oneiric we can still make the ui handle the bug better at least ;-)
[14:09] <jjardon> kenvandine: Could you wait a minute? I want to commit a little fix first
[14:09] <seb128> chrisccoulson, well I get the ghost battery here but not the hibernate on resume
[14:09] <chrisccoulson> but the kernel exposes a battery via sysfs after suspending, which is definitely a kernel bug
[14:09] <kenvandine> jjardon, sure, i am working on something else now
[14:09] <kenvandine> jjardon, just ping me
[14:09] <chrisccoulson> seb128, yeah, the shutdown on resume is fairly random here - it only happens ~50% of the time
[14:09] <jjardon> kenvandine: seb128: ok, seem that we want to show non present batteries
[14:09] <chrisccoulson> "only" ;)
[14:09] <jjardon> but only in the menu
[14:10] <seb128> jjardon, why?
[14:10] <seb128> jjardon, well that works for me, as long as my real battery is what is in the panel ;-)
[14:10] <jjardon> seb128: https://wiki.ubuntu.com/Power#Battery_menu
[14:11] <seb128> jjardon, ok
[14:14] <jjardon> kenvandine: ping ;) https://code.launchpad.net/~jjardon/indicator-power/master rev 115 and 116
[14:21] <kenvandine> jjardon, thx
[14:27] <seb128> jdstrand, do we still default to imap and not imap+?
[14:28] <seb128> jdstrand, we should really recommend imap+, it's way better and there for some cycles
[14:34] <kenvandine> jjardon, so your last commit just reverted half of the previous commit right?
[14:34] <jjardon> yep
[14:34] <jjardon> kenvandine: yes
[14:34] <kenvandine> ok, just checking
[14:35] <kenvandine> so this makes it more likely to display the icon for the real battery in the panel
[14:35] <kenvandine> and the others in the menu
[14:35] <jjardon> kenvandine: yes
[14:44] <kenvandine> seb128, jjardon: uploaded
[14:44] <kenvandine> seb128, i also upload the i-s fix
[14:44] <kenvandine> s/upload/uploaded/
[14:46] <rodrigo__> seb128, I've got a fix for the undesired suspend, can you please install the package and see if it suspends when you go out for sport? :)
[14:49] <seb128> rodrigo_, sure can do!
[14:49] <seb128> rodrigo_, commit to the vcs and I will build it
[14:50] <rodrigo_> seb128, ok, pushing in a minute
[14:51] <rodrigo_> seb128, at least from my tests it doesn't set up the timeout for suspending, so I think it should be ok
[14:51] <rodrigo_> seb128, pushed
[14:53] <seb128> rodrigo_, thanks
[14:53] <rodrigo_> now back to digging the screen turning off bug, it's driving me crazy
[14:53] <rodrigo_> after 20/30 different changes in the code, still always turns it off
[15:08] <dobey> seb128: care to sponsor/upload https://code.launchpad.net/~dobey/ubuntu/oneiric/glib2.0/fix-804946/+merge/77939 now? :)
[15:09] <seb128> dobey, will do in a bit, I want to have a look to the mmap being cleared on upgrade before uploading
[15:09] <seb128> dobey, i.e I will do an upload with both once I figure the packaging issue
[15:09] <dobey> seb128: ok, thanks
[15:10] <seb128> dobey, yw, thanks for the work on glib ;-)
[15:11] <dobey> seb128: no problem, i am still triaging the massive list of bugs for this too :)
[15:11] <dobey> i wonder if fedora has lots of bugs reported with this as well
[15:31] <seb128> rodrigo_, I don't understand your 11_avoid_undesired_sleeps.patch
[15:31] <rodrigo_> seb128, it's taking into account the boolean keys
[15:31] <seb128> rodrigo_, didn't you say that the booleans were deprecated?
[15:31] <rodrigo_> seb128, in master
[15:32] <seb128> hum
[15:32] <seb128> $ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac
[15:32] <seb128> false
[15:32] <seb128> $ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout
[15:32] <seb128> 0
[15:32] <seb128>  
[15:32] <seb128> rodrigo_, that's my config
[15:32] <seb128> I don't see how your fix will make it work differently?
[15:33] <rodrigo_> I've seen on the bug reports people had it set to false, but the timeout was 1800
[15:33] <seb128> right
[15:34] <seb128> which was what we had before your g-s-d upload today when the gsettings default was wrong
[15:34] <rodrigo_> then, it might be the same as the display-sleep thing
[15:34] <seb128> but we have people who say still having their computer wrongly suspending after setting the key manually to 0
[15:35] <seb128> rodrigo_, well I can test your patch but I guess it will not make a difference for me since I've false and 0 as values
[15:35] <rodrigo_> yeah
[15:38] <jdstrand> seb128: re imap vs imap+> well, there isn't a default, you just choose one from a list. the list doesn't give a lot of info, just IMAP, IMAP+, POP, etc
[15:38] <jdstrand> seb128: plus, I upgraded for several releases, so I surely had whatever I set up initially
[15:39] <seb128> jdstrand, ok, we should probably look at hiding imap from the list next cycle
[15:39] <jdstrand> seb128: perhaps the correct course is to update the list, so IMAP+ is listed first and IMAP is listed like 'IMAP (old non-IDLE support servers)' or something
[15:40] <jdstrand> seb128: well, the server must support IDLE
[15:40] <seb128> jdstrand, IMAP+ doesn't enforce IDLE use
[15:40] <jdstrand> oh, I thought it did
[15:40] <seb128> jdstrand, no, it's a checkbox in the preferences
[15:40] <seb128> jdstrand, "use IDLE if it's handled by the server"
[15:40] <jdstrand> seb128: is that the 'Quick Resync' thingie?
[15:41] <seb128> no, the one just bellow
[15:41] <jdstrand> ah, yes
[15:42] <jdstrand> seb128: it might also be interesting to transition people from IMAP to IMAP+ on upgrades, but this might not work too well, especially if people specifically wanted the old IMAP support
[15:42] <seb128> right
[15:42] <seb128> that could be worth putting in the upgrade notes
[15:51] <didrocks> RAOF: you were asking me for the crash, I can still get it, see bug #865358
[15:52] <didrocks> RAOF: seems there are a lot of similar crashes as well
[15:52] <didrocks> race in getting a window?
[15:59] <seb128> ok, time for some sport; back in an jour
[15:59] <seb128> hour
[16:57] <dobey> BigWhale: did you ever get your boot issue fixed?
[17:08] <dobey> hrmm, i wish the unlock screen looked like the login screen on oneiric
[17:09] <BigWhale> dobey, hey
[17:09] <BigWhale> dobey, yeah... I got rid of LVM :/
[17:10] <dobey> BigWhale: oh, that is a completely different issue than i'm having then :(
[17:11] <dobey> BigWhale: i upgraded and now my laptop won't boot, it just sits "waiting for network..."
[17:12] <BigWhale> I think that the lvm and udev get into some sort of race condition.
[17:13] <BigWhale> dobey, try blacklisting your network drivers so that they won't load.
[17:13] <dobey> BigWhale: how can i do that?
[17:14] <BigWhale> dobey, did you try booting with a live CD?
[17:15] <dobey> BigWhale: no, just old kernels so far. and i'm not entirely sure where my usb drive is to make a live boot thing with
[17:16] <BigWhale> if booting into recovery doesn't work then you'll have to go with the liveCD/USB
[17:16] <BigWhale> and I feel your pain.. I had to rip the memory card from my camera so I was able to make the usb thingy :>
[17:18] <dobey> well i got recovery mode to come up with the old kernel
[17:18] <dobey> but once i do that i still have no idea how to "blacklist my drivers"
[17:19] <dobey> and how do i install an update that fixes the problem if my network drivers are blacklisted and i have no network? :(
[17:19]  * dobey feels like he's on windows 95
[17:21] <hyperair> seb128: regarding bug #840292, could you sponsor it please?
[17:21] <ubot2> Launchpad bug 840292 in nautilus-share "uses synaptic to install samba which is not on the CD" [High,Confirmed] https://launchpad.net/bugs/840292
[17:22] <hyperair> while i'd love to upload nautilus-share being the debian maintainer, i don't haev upload rights to main or nautilus-share
[17:22]  * hyperair needs to hurry up and apply for nautilus-share PPU-ship
[17:22] <seb128> hyperair, can do, thanks for working on it!
[17:23] <seb128> hyperair, could you comment on the bug saying what is to sponsor?
[17:23] <hyperair> hmm
[17:23] <seb128> comment #13 makes it a bit confusing
[17:23] <seb128> seems several people have several work in progress there?
[17:23] <hyperair> no, it loosk more like the same person made two branches
[17:24] <seb128> ok
[17:24] <hyperair> the apturl approach seems a bit awkward, but i haven't managed to test the packagekit solution.
[17:24] <hyperair> maybe i should give it a go.
[17:25] <seb128> I will check with pitti tomorrow, that seems a non trivial diff to upload during hard freeze
[17:25] <seb128> rodrigo_, still there?
[17:25] <hyperair> yeah.
[17:26] <hyperair> seb128: the apturl diff looks more promising considering the freeze.
[17:26] <seb128> rodrigo_, should we get gnome-desktop,g-s-d uploaded for the dpms issue and then gnome-screensaver will need to be fixed?
[17:26] <seb128> hyperair, right
[17:35] <BigWhale> dobey, are you using wireless network?
[17:35] <dobey> BigWhale: yes
[17:35] <dobey> it's the only kind i can use on this machine
[17:36] <dobey> oh lovely
[17:36] <dobey> my other laptop boots, but networking is disabled now :(
[17:41] <dupondje> somebody knows if there are plans for a new telepathy-mission-control-5 version upload?
[17:41] <dupondje> cause we really need some upstream fixes
[17:42] <kenvandine> dupondje, no plans atm... any particular bug fix you want uploaded?
[17:42] <dupondje> https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/726301
[17:42] <ubot2> Launchpad bug 726301 in telepathy-mission-control-5 "mission-control-5 crashed with SIGSEGV in g_str_hash()" [Medium,Confirmed]
[17:42] <kenvandine> we are in hard freeze right now, so we want to limit the change as much as possible
[17:43] <dupondje> true
[17:43] <dupondje> but guess we better fix i :D
[17:43] <dupondje> it*
[17:44] <kenvandine> i can look at back porting that specific fix
[17:44] <dupondje> would be nice
[17:46] <dupondje> guess its http://cgit.freedesktop.org/telepathy/telepathy-mission-control/commit/?id=0bae7095a9e1a10e531d311e993fc1c67438cfd2
[17:46] <BigWhale> kenvandine! Where have you been hiding? :>
[17:46] <kenvandine> BigWhale, right here, in plain sight :)
[17:48] <dupondje> kenvandine: while your on it
[17:48] <dupondje> http://cgit.collabora.com/git/user/wjt/telepathy-mission-control-wjt.git/commit/?h=39767-client-unique_name-NULL&id=5e65e972fdcbfd4dd8a2b6b6396e3ea3e91baa41
[17:48] <dupondje> fixes https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/816808
[17:48] <ubot2> Launchpad bug 816808 in mission-control-5 "mission-control-5 crashed with SIGABRT in raise()" [Critical,Confirmed]
[17:51] <BigWhale> dobey, try disabling network manager
[17:53] <dupondje> what about https://bugs.launchpad.net/gnome-control-center/+bug/819994 ?
[17:53] <ubot2> Launchpad bug 819994 in gnome-control-center "String length of items seems limited" [Low,Triaged]
[17:53] <dupondje> don't we think this would be nice to have fixed ? :D
[17:56] <dobey> BigWhale: i don't see how that would help me?
[17:57] <BigWhale> perhaps you won't get stuck at 'waiting for network' and then you can try and start network manager manually and actually see what's going on
[17:59] <dobey> BigWhale: well my other laptop boots fine, but just has no network now
[17:59] <dobey> there were still some held back updates though when i rebooted it
[18:01] <dobey> and something in X froze on logout :(
[18:07] <jbicha> are we going to disable the login sound for Oneiric?
[18:14] <cyphermox> dobey: anything in /etc/network/interfaces?
[18:14] <dobey> cyphermox: not that i would have put in there, no
[18:25] <dobey> well now, my duo seems to not even boot up the recovery mode :(
[18:27] <seb128> jbicha, no
[18:28] <seb128> jbicha, turning it off was acked but it slipped and didn't get done, I mentioned it to pitti some days ago and we agreed that it was late and we have freeze exceptions over what we should have already so delayed to next cycle
[18:29] <charlie-tca> Login sound helps with a11y. Those who can not see the screen can at least hear it
[18:29] <jbicha> seb128: ok, can I revert the nodisplay patch so that it shows up in Startup Applications ?
[18:30] <seb128> jbicha, no?
[18:31] <seb128> jbicha, why should it be listed there?
[18:31] <jbicha> seb128: the startup sound is very disruptive, it should be easy to disable for those that don't want it
[18:31] <jbicha> and if we do disable it for P, it should be easy to re-enable it
[18:31] <seb128> jbicha, can't the user just mute the sound effects in the sound capplet?
[18:33] <seb128> jbicha, I really don't understand the sound effect tab of the sound capplet ;-) it should have the list of events and associated sounds ;-)
[18:33] <jbicha> what if I want sound effects but not the outdated login sound?
[18:34] <seb128> jbicha, yeah, I agree that what we have now sucks, I though we had something in the sound capplet to turn login sound off :-(
[18:35] <jbicha> http://maketecheasier.com/disable-login-sound-in-ubuntu-oneiric-quick-tips/2011/09/15
[18:35] <seb128> jbicha, seems like showing the startup desktop is the eaasier workaround since we are late in the cycle, I don't really like having an empty list with only startup shound in that dialog though
[18:35] <seb128> that will looks quite weird :-(
[18:36] <seb128> jbicha, let me talk to pitti tomorrow, I think I would prefer to push for turning it off rather than adding an entry there
[18:37] <seb128> jbicha, do you know what's the proper way to turn it off?
[18:38] <jbicha> well if we disable it, we have to let people turn it back on for the few who want it I think
[18:40] <seb128> jbicha, well, that would be a less pressing use and a "would be nice" on the same level than "let users have a screensaver" ;-)
[18:40] <seb128> dobey, grrrrrr
[18:41] <seb128> dobey, I think you just screwed nautilus
[18:41] <seb128> dobey, bug #865567
[18:41] <ubot2> Launchpad bug 865567 in nautilus "nautilus crash Segmentation fault (core dumped) " [Undecided,Confirmed] https://launchpad.net/bugs/865567
[18:41] <seb128> "(nautilus:2710): GLib-GIO-CRITICAL **: Settings schema
[18:41] <seb128> 'org.gnome.nautilus.extensions.ubuntuone' is not installed"
[18:41] <jbicha> seb128: http://bazaar.launchpad.net/~ubuntu-desktop/libcanberra/ubuntu/revision/132
[18:42] <seb128> jbicha, oh, disabling the autostart
[18:43] <seb128> I was rather looking for a gsettings key or unsetting the sound to use
[18:43] <seb128> jbicha, good idea! ;-)
[18:44] <jbicha> seb128: well I disabled the nodisplay and then looked to see what unchecking the box in Startup Apps would do
[18:47] <jbicha> seb128: did you see I had a few things that need sponsoring on the pad?
[18:48] <seb128> jbicha, no I didn't look at the pad today since we are mostly in bug fix mode now, looking now ;-)
[18:48] <kenvandine> seb128, how do you feel about doing a minor version bump on mission-control-5?  fixes a handful of bugs, at least a couple of which have quite a few dupes
[18:49] <seb128> kenvandine, works for me but I'm not the one doing approvals in the queue ;-)
[18:49] <seb128> kenvandine, it's worth trying, worth case they tell you to go for a sru
[18:49] <kenvandine> yeah
[18:49] <kenvandine> ok
[18:50] <kenvandine> will do... seems better than back porting the fixes
[18:52] <seb128> ok
[18:53] <seb128> dobey, hum, doesn't seem to be an issue there, less grrrr ;-) still weird bug and we got a few recent nautilus doesn't start bugs which I wonder have to do with it
[18:54] <dobey> seb128: ?
[18:54] <seb128> dobey, the ubuntuone-client-gnome update is broken
[18:54] <seb128> dobey, it makes nautilus segfault, it misses its schemas
[18:55] <dobey> seb128: right, that's why i went through all that stuff for the patch this morning.
[18:56] <dobey> and if it's segfaulting why is there not backtrace?
[18:56] <seb128> dobey, because the user didn't use apport to open it
[18:56] <dobey> seb128: then why does it have all the apporty stuff in the description?
[18:57] <seb128> dobey, because he did 'ubuntu-bug nautilus"
[18:57] <seb128> dobey, and not "ubuntu-bug nautilus.crash"
[18:57] <seb128> well it's trivial to segfault
[18:57] <dobey> not for me
[18:57] <seb128> run nautilus; file -> ubuntuone -> hide ribbon
[18:57] <dobey> i can't even boot
[18:57] <seb128> that segfaults it there
[18:58] <dobey> seb128: even with my glib2.0 fix?
[18:58] <seb128> kenvandine, ^ does it work for you?
[18:58] <seb128> dobey, no
[18:58] <seb128> dobey, I didn't try your glib "fix" yet ;-) but why isn't ubuntuone-client-gnome having a schemas?
[18:58]  * kenvandine tries
[18:59] <dobey> because i didn't realize that gsettings was fascist
[18:59] <dobey> as i'm sure lots of people haven't, given the number of places this is a problem
[18:59] <seb128> well just browsing a synced directory makes nautilus segfault
[18:59] <kenvandine> interesting, nautilus crashed when i opened a folder synced on u1... but not apport
[18:59] <kenvandine> this worked last week
[18:59] <seb128> kenvandine, ubuntuone-client-gnome port to gsettings landed today...
[19:00] <kenvandine> or late the week before... not certain
[19:00] <kenvandine> ah
[19:00] <kenvandine> sigh
[19:00] <seb128> kenvandine, the new version was ftbfing before
[19:00] <dobey> well not today; thursday
[19:00] <seb128> dobey, I think you are the only one to not have a schemas
[19:00] <seb128> dobey, it got newed this morning at 6am
[19:00] <dobey> ah
[19:00] <seb128> well newed -> acked from unapproved
[19:01] <dobey> weird
[19:01] <seb128> dobey, ok, can we get a schemas?
[19:01] <dobey> well it would be nice if i coudl boot
[19:01] <dobey> could boot
[19:01] <seb128> what issue do you get?
[19:01] <dobey> it sits waiting for network, and with recovery mode i just get a blank screen now it seems
[19:04] <seb128> dobey, I'm undupping it
[19:05] <dobey> why?
[19:05] <seb128> dobey, the glib "don't segfault on unrefing a null g_value" workaround is not a fix, you need a schemas
[19:05] <seb128> because you will get an undefined behaviour without a schemas
[19:05] <dobey> well it stops the crashing
[19:05] <seb128> even if it doesn't segfault
[19:05] <dobey> us needing a schema is a separate issue
[19:05] <seb128> right
[19:05] <seb128> which is why I'm undupping :p
[19:05] <dobey> file a new bug
[19:05] <seb128> I use the new bug as "you need a schemas"
[19:05] <dobey> crash is a dup :)
[19:05] <seb128> that's what the new bug is
[19:05] <seb128> I'm renaming it
[19:05] <seb128> "(nautilus:2710): GLib-GIO-CRITICAL **: Settings schema 'org.gnome.nautilus.extensions.ubuntuone' is not installed"
[19:05] <seb128> is the description
[19:06] <dobey> btw
[19:06] <dobey> i hate gsettings.
[19:06] <seb128> why?
[19:06] <dobey> because it has caused nothing but problems
[19:07] <seb128> it works fine
[19:07] <dobey> and it doesn't actually fix any of the real issues from gconf
[19:07] <seb128> dobey, btw I'm not sure I agree with your fix being a fix rather than a workaround
[19:07] <seb128> dobey, oh it does
[19:07] <seb128> it's not slowing down login as gconf was doing ;-)
[19:08] <seb128> it's not parsing xmls over the disk
[19:08] <dobey> it's a fix. it adds a line of code that was missing from upstream, that should be there :)
[19:08] <seb128> it's just mmaping a binary
[19:08] <seb128> dobey, that will not make your software work correctly though
[19:08] <dobey> so it fixes the performance issue maybe; but that's just an implementation detail problem
[19:09] <dobey> i should just make the nautilus extension use a ini file
[19:09] <seb128> works for me but please let's be constructive there and just add the schemas for oneiric ;-)
[19:09] <kenvandine> dobey, that wouldn't fix anything
[19:10] <kenvandine> dobey, nothing wrong with conforming to how the desktop works :-p
[19:10] <dobey> kenvandine: i wouldn't need a stupid schema for it
[19:10] <dobey> kenvandine: and it would be faster
[19:10] <dobey> kenvandine: and it would be less code
[19:10] <dobey> seems like win to me :)
[19:10] <seb128> it wouldn't be faster
[19:11] <kenvandine> and there would be no mechanism for overrides, etc
[19:11] <seb128> and it would handle vendor defaults, locking, etc
[19:11] <seb128> wouldn't
[19:11] <dobey> we don't need all that
[19:11] <kenvandine> it's not like it is hard to add the default schema
[19:11] <kenvandine> i agree it shouldn't crash if there isn't one... but that is a different issue
[19:12] <dobey> not hard. it's just a complete waste of time
[19:12] <dobey> and totally pointless
[19:12] <dobey> because the main issue with every config system on the planet, is not solved by gsettings
[19:13] <dobey> and that is, people need something to save state, but there is no state saving api, so everyone uses settings
[19:13] <kenvandine> your case is for a setting though, not a state
[19:13] <kenvandine> so it is the correct use
[19:13] <dobey> no it isn't
[19:14] <kenvandine> ?
[19:14] <dobey> it is state
[19:14] <kenvandine> then i am a little closer to agreeing with you
[19:14]  * kenvandine hates agreeing with dobey
[19:14] <dobey> agreeing with me is inevitible
[19:15] <kenvandine> but regardless, it isn't worth arguing about...
[19:15] <kenvandine> it is the state of the world right now
[19:15] <kenvandine> :)
[19:16] <dobey> hrmm
[19:16] <dobey> i would like a day where i don't have to fix 10 bugs RIGHT NOW
[19:16] <dobey> :-/
[19:23] <broder> gah. why does compiz build-dep on libdecoration0-dev? is it actually using the one in the build dep instead of the one in its source tree?
[19:24] <seb128> broder, debian,ubuntu don't like using inline lib copies
[19:24] <seb128> broder, I don't know about this particular case
[19:24] <broder> seb128: ...but the lib comes from the compiz source package
[19:25] <seb128> broder, that seems buggy indeed ;-)
[19:25] <broder> alright, i'll go file a bug
[19:26] <seb128> broder, the changelog mention that it was added as a workaround in natty and dropped in the next upload
[19:27] <seb128> so seems something didn't go right and it landed back there
[19:27] <dobey> sigh
[19:27] <broder> seb128: it was added back in 1:0.9.5.0-0ubuntu1 without much of an explanation
[19:28] <seb128> broder, seems like an error
[19:28] <broder> i'll double check that it builds without the b-d and file a bug
[19:28] <seb128> broder, well open a bug in any case
[19:29] <broder> sure
[19:29] <seb128> broder, the reply might be "compiz doesn't pick the inline version as it should so we workaround it" but it's still a bug ;-)
[19:29] <broder> every once and a while i like to hack on build systems to satisfy my inner masochist, so if it doesn't just work i'll see if i can wrangle a patch together :-P
[19:31] <seb128> broder, thanks ;-)
[19:32] <dobey> it really is a pain in the ass trying to fix bugs in oneiric, when i can't even boot it :(
[19:32] <dobey> or can't use network on it
[19:33] <seb128> dobey, did you try booting the previous kernel?
[19:33] <dobey> yes of course
[19:35] <seb128> did that start today?
[19:35] <seb128> we didn't have lot of recent updates that could break that, weird
[19:36] <dobey> no; i upgraded last night when BigWhale said he was having issues with the new kernel, and then it broke
[19:38] <seb128> dobey, did you try failsafe?
[19:38] <dobey> yes
[19:39] <dobey> i just get a blank screen
[19:39] <dobey> hdd light flashes but no idea what it's doing
[19:39] <seb128> is that a laptop? is it docked?
[19:39] <dobey> dell duo, not docked, but ac is plugged in
[19:40] <seb128> dobey, can you try to press shift on boot to get the grub menu, e, edit the gfxpayload=$linux... and change to =text?
[19:40] <dobey> my other laptop boots, but won't let me configure the network, and there's no grub menu for me to choose the older kernel it seems on it :(
[19:41] <seb128> dobey, did you try pressing shift from the system start on?
[19:42] <dobey> no, but held arrow key down
[19:43] <seb128> what arrow?
[19:43] <dobey> down arrow
[19:43] <seb128> try shift
[19:44] <seb128> dobey, try also the gfxpayload thing in case, that fixes a blank screen issue on my dell when docked
[19:44] <dobey> i either didn't do it right or it didn't work
[19:45] <dobey> and that option doesn't exist for the recovery mode it seems
[19:45] <seb128> ok, it was worth trying
[19:45] <seb128> try dropping the "splash" from the kernel line? though I guess that's not used in failsafe either
[19:46] <dobey> oh right, i didn't even upgrade the kernel on the laptop that boots but just has no network any more
[19:46] <dobey> so booting the "older" kernel won't really help
[19:47] <dobey> and something causes logout to freeze on that machine
[19:48] <dobey> i had failsafe work once, and it hasn't worked since :(
[19:50] <dobey> and blank screen using 3.0.0-8 kernel
[19:50] <dobey> it did the right thing when i hit the power key though
[19:52] <dobey> surely i am not the only person having these issues?
[19:52] <seb128> try asking on #ubuntu-devel
[19:53] <seb128> well, as said my laptop has issues for some weeks due to the gtkpayload=$linux.. option which result to no screen content to be display
[19:53] <seb128> i.e the kernel or something doesn't like the mode switch
[19:53] <seb128> but it doesn't do it when I edit to boot with =text
[19:54] <seb128> i.e "e" in grub, edit, ctrl-x to boot
[19:54] <seb128> other issue I could think off is plymouth, so dropping the "splash" from the kernel line
[19:55] <dobey> right, but neither of those are used in failsafe, where i see this issue
[19:55] <seb128> try asking on #ubuntu-devel
[19:55] <dobey> in normal boot the splash works fine, it just says "Waiting for network..."
[19:55] <dobey> and then later says "Waiting 60 more seconds for network..."
[19:55] <dobey> and just never finishes waiting for network
[19:56] <seb128> it seems a bit over desktop knowledge of the base systems ;-)
[19:56] <cyphermox> doesn't sound like NM anyway
[19:57] <broder> sounds like some of the workaround stuff SpamapS was doing
[19:57] <cyphermox> aye
[19:57] <broder> i forget the exact issue, though
[19:57] <cyphermox> well, mostly related to bringing up network devices in general
[19:58] <seb128> dobey, do you boot plugged, unplugged? does it make a difference?
[19:59] <seb128> dobey, try asking SpamapS on #ubuntu-devel maybe?
[20:00] <dobey> booting not on ac doesn't doesn't help with the network issue no
[20:01] <seb128> dobey, well I was rather think eth cable ;-)
[20:01] <seb128> if you have one
[20:01] <dobey> this machine doesn't have ethernet, only wireless
[20:31] <mterry> seb128, hah, I try to slink away from a gvfs bug and you assign it right back.  ;)
[20:32] <seb128> mterry, lol, sorry it's my automatching, I read deja and I though "mterry", I kept reading and it was "dup" then I assigned :p
[20:33] <seb128> mterry, well it was more a "I will let him know about it and decide if that's an important issue for deja-dup or not", feel free to unassign yourself, I should have subscribed ;-)
[20:33]  * mterry adds an email filter to auto-retitle deja-dup bugs to "oneconf: " so seb128 will assign to didrocks
[20:34] <seb128> ;-)
[20:40] <dobey> seb128: btw, we also have bug #865593 to deal with :(
[20:40] <ubot2> Launchpad bug 865593 in ubuntuone-client-gnome "Ubuntu One launcher disappears on upgrade to Oneiric" [Critical,In progress] https://launchpad.net/bugs/865593
[20:41] <seb128> dobey, hum, why?
[20:41] <seb128> dobey, users upgrading who have ubuntuone-control-panel should still have it installed after upgrade no?
[20:42] <dobey> seb128: the .desktop file is no longer there though; it was removed and ubuntuone-installer.desktop is used now
[20:42] <seb128> dobey, why would that package get removed on upgrade?
[20:42] <seb128> oh, urg
[20:42] <dobey> yeah, remember that whole plan? ;)
[20:43] <dobey> the best part is i can't actually test them :(
[20:43] <seb128> dobey, well I though we rolled back on that plan
[20:43] <dobey> i am pretty certain my fixes are correct though; i'm only really worried about freeing a char* inside a char**
[20:44] <seb128> dobey, I will talk to didrocks tomorrow
[20:44] <dobey> seb128: by installing everything by default, not by getting rid of the installer
[20:44] <seb128> dobey, they have a migration script in unity, I think it would rather make sense to put the migration there rather than inventing a new migration codepath
[20:44] <seb128> dobey, well I didn't realize that the ubuntuone-control-panel.desktop got dropped
[20:44] <seb128> why?
[20:45] <dobey> ie, roll back in a way that would not totally break the goal of going down that route for the next cycle
[20:45] <dobey> seb128: because having 2 launchers everywhere that appare to do the exact same thing, is broken?
[20:46] <seb128> dobey, ok, I didn't try the installer, I though it was different from the control panel
[20:46] <seb128> well anyway thanks for pointing it
[20:46] <seb128> I will check if didrocks if he wants to do it in the unity migration script
[20:46] <mterry> seb128, (installer will launch control panel if u1 is installed already)
[20:46] <seb128> that seems it would be better
[20:46] <dobey> seb128: it is, but after the control panel is installed, it just runs the control panel
[20:46] <dobey> seb128: to be there by default, and keep a smooth workflow without having to mess with the user's settings to remove and add things to the launcher
[20:47] <dobey> brilliant that we have to do that anyway now, eh
[20:47] <seb128> dobey, mterry: that seems a bit buggy, it means if I've the ubuntuone-control-panel and not the installer I can't find ubuntuone in the dash?
[20:47] <jbicha> seb128: is "Suspend when inactive on battery" supposed to be "don't suspend" now?
[20:47] <dobey> but then there's still the gnome-control-center and dash issues with 2 launchers
[20:47] <seb128> jbicha, yes
[20:47] <dobey> seb128: you can't have the control panel, and not the installer
[20:48] <dobey> seb128: apt-cache depends ubuntuone-control-panel-gtk :)
[20:48] <seb128> ok, I see ;-)
[20:48] <seb128> why do we start seing all those issue the week of hard freeze :-(
[20:48] <seb128> it's crazy
[20:48] <jbicha> seb128: does setting it to 30 minutes or something break it for AC then?
[20:49] <dobey> because nobody uses the alphas/betas?
[20:49] <seb128> we do
[20:49] <seb128> well not a discussion for today
[20:50] <seb128> but I would assume u1 to test their work at each beta
[20:50] <seb128> though you got busy and lot of change of plans this cycle
[20:50] <seb128> jbicha, I'm not sure to understand the question
[20:50] <dobey> well i added the installer to my launcher before it got switched in the default list, so i could test stuff
[20:50] <dobey> and so of course i didn't see the thing not being there, since it was there
[20:50] <seb128> not blaming you
[20:51] <dobey> but that's no excuse for everyone else
[20:51] <seb128> but we need better qa testing for upgrades ;-)
[20:51] <dobey> s/for upgrades//
[20:51] <jbicha> seb128: -0ubuntu4 changed the default, Ubuntu used to autosuspend when idle on battery for X minutes, did we change that because it's broken?
[20:51] <dobey> why is my network/lightdm/bluetooth/etc not working? :)
[20:52] <seb128> jbicha, sorry, I get you now ;-)
[20:52] <seb128> jbicha, no, we though that it used to no suspend on idle and that it's a safer default
[20:53] <seb128> jbicha, see septembre 28's log on this channel
[20:54] <seb128> sept. 28 14:07:34 <pitti>       seb128: I have no strong opinion on that one, but I'd opt for consistency with previous releases here; I think we disabled autosuspend on battery
[20:54] <seb128> sept. 28 14:07:41 <pitti>       seb128: but I'm happy to boot natty and triple-check
[20:54] <seb128> sept. 28 14:08:29 <pitti>       seb128: if "not suspend" is consistent with both natty and AC, I think that'd be best
[20:54] <seb128> sept. 28 14:08:35 <pitti>       principle of least surprise
[20:54] <seb128>  
[20:54] <seb128> jbicha, ^
[20:55] <seb128> sept. 28 14:11:40 <pitti>         sleep_computer_ac = 0
[20:55] <seb128> sept. 28 14:11:48 <pitti>          sleep_comptuer_battery = 1800
[20:55] <seb128> sept. 28 14:11:59 <pitti>       so it seems we did default to 30 seconds in natty when on battery
[20:55] <seb128>  
[20:55] <seb128> hum
[20:55] <seb128> jbicha, so yeah, it seems we said we would do "30min idle suspend on battery" and "never on ac"
[20:55] <seb128> upstream commit changes both to never though
[20:56] <seb128> jbicha, well I've no strong opinion but if you have one feel free to reupload with the battery change reverted
[20:56] <seb128> jbicha, sorry that this cycle is crazy will late ui and behaviour changes
[20:58] <jbicha> seb128: ok, I should probably thoroughly test it though since power was pretty broken the last several days
[20:58] <seb128> jbicha, yeah, I'm still unsure if the "suspend on idle on ac" issue is fixed
[20:58] <seb128> i.e if that was only the default being wrong or if we have a code bug as well
[20:59] <RAOF> Mornin' all.
[20:59] <seb128> jbicha, well there is no reason the suspend on igle should be different from suspend manually, either suspend works or not
[20:59] <dobey> i guess i shouldn't have switched it to gsettings
[20:59] <seb128> if we used to default to 30min on battery we should still do it
[20:59] <seb128> dobey, stop complaining about gsettings ;-)
[20:59] <seb128> RAOF, hey
[21:00] <dobey> i'm not complaining about gsettings; i'm complaining about me having to do more work
[21:01] <dobey> if i had only done the gschema for the gsd plug-in to load, i wouldn't have also had to fix glib. could have just remained ignorant :)
[21:02] <seb128> RAOF, do you know around what time robert_ancell is on IRC usually? was he online yesterday?
[21:02] <RAOF> seb128: I didn't talk to him yesterday, and I didn't see him online.  Usually he'd be on in about an hour or so.
[21:03] <seb128> RAOF, I tend to overlap with you in the morning, can you check if you see him today what's the status on lightdm 1.0.1? we need it uploaded today if we want it in Oneiric
[21:04] <RAOF> seb128: Will do.
[21:04] <seb128> RAOF, we should at least fix the gtk greeter translation init (he fixed that in trunk) and that would be nice if he could look at the locale issue assigned to him and the ck session one you helped on a bit yesterday night
[21:04] <seb128> the ck one that prevents compiz to start seems a stopper
[21:04] <seb128> RAOF, thanks
[21:05] <RAOF> No problem :)
[21:06] <mdeslaur> seb128: ARGH...you know I can't resist fixing the screen locking bugs, right? :)
[21:06] <seb128> mdeslaur, I do know ;-)
[21:06] <seb128> hehe
[21:06] <mdeslaur> seb128: testing patch now :P
[21:06] <seb128> mdeslaur, \o/
[21:06] <seb128> (my plan worked! ;-)
[21:08] <mdeslaur> seb128: all this desktop stuff will cost you UDS beer you know :)
[21:08] <seb128> mdeslaur, isn't paying back the beers due what UDS is about? ;-)
[21:08] <seb128> but yeah, don't worry, there will be beers ;-)
[21:10] <mdeslaur> seb128: hehe :)
[22:17] <RAOF> robert_ancell: Good morning!
[22:17] <robert_ancell> RAOF, hello
[22:17]  * bryceh waves
[22:17] <cyphermox> hey RAOF, robert_ancell
[22:17] <RAOF> Hey bryceh :)
[22:17] <robert_ancell> oh dear, 3 people.  Is something broken?
[22:18] <bryceh> hey RAOF
[22:18] <RAOF> robert_ancell: I'll be your surrogate seb128 asking you what the status of lightdm 1.0.1 is, since it needs to be uploaded today to make it. ?
[22:19] <robert_ancell> RAOF, I was planning on SRUing it, unless there was a particular bug someone was intersted in (and then possibly just patching it)
[22:21] <RAOF> Seb was after a fix for the gtk greeter translation init, possibly the locale issue assigned to you, and the ck session craziness that seems to be breaking Unity for some people.
[22:22] <robert_ancell> RAOF, what's the ck session craziness?
[22:22] <RAOF> bug #863119 is the reference.
[22:22] <ubot2> Launchpad bug 863119 in lightdm "~/xsession-errors is owned by root, incorrect consolekit session breaking DRI" [High,Confirmed] https://launchpad.net/bugs/863119
[22:23] <RAOF> It seems some people are logging in but their CK session isn't being marked as active, so (among other things) they don't have access to /dev/dri, breaking 3D and hence Unity.
[22:26] <RAOF> Of course, like all good bugs, it doesn't affect any of *my* systems :)
[22:27] <robert_ancell> RAOF, yeah, me neither...
[22:27] <robert_ancell> ah well, I guess 1.0.1 today then?
[22:28] <jasoncwarner_> kenvandine: around?
[22:29] <RAOF> robert_ancell: Or some distro-patches, I guess :).  Give me a hoy if I can be of assistance with that CK madness.
[22:30] <robert_ancell> RAOF, I think it only happens when you don't have a ~/.xsession-errors.  Should be an easy fix, it's probably just writing it before the setuid
[22:31] <RAOF> Oh, freaky.
[22:32] <Amaranth> robert_ancell: wouldn't that mean every new install would reliably reproduce this issue?
[22:35] <robert_ancell> Amaranth, I would expect, but I haven't investigated the issue, just my gut feel
[22:42] <Sarvatt> RAOF: oh so that's what is breaking boot 1/30 boots or so for me?
[22:43] <RAOF> Sarvatt: No, your boots fail earlier, and X is run as root, so it always has /dev/dri permissions.
[22:45] <Sarvatt> ah ok, yeah i get http://paste.ubuntu.com/693223/ sporadically when X starts extra early and have to start lightdm again from a VT
[22:46] <jasoncwarner_> rodrigo_: hey, do you have updated status on https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/864479 ?
[22:46] <ubot2> Launchpad bug 864479 in gnome-control-center "System goes to hibernate or suspend even when set to "Don't suspend"" [Critical,Confirmed]
[22:47] <jasoncwarner_> morning everyone...how is everyone feeling today ? :)
[22:47] <jbicha> jasoncwarner_: was that fixed in g-s-d ubuntu4?
[22:48] <jasoncwarner_> jbicha: I'm not sure, which is kind of why I'm asking ;) I saw it was still open and it was on several release checklists
[22:48] <TheMuso> jasoncwarner_: Morning, refreshed after a longer than normal weekend. :)
[22:48] <jasoncwarner_> TheMuso: awesome. glad the weekend did the job!
[22:49] <jasoncwarner_> jbicha: do you think that bug is a dupe of one that is fixed released?
[22:53] <jbicha> jasoncwarner_: comment #7 and #11 indicate that it is, I don't know for sure but I _think_ it's fixed