=== ripps_ is now known as ripps
[03:22] <BoNiTo> hi
[03:22] <BoNiTo> I need some help :)
[03:23] <BoNiTo> I installed ubuntu-x-swat repository trying to fix the flickering or my video card
[03:23] <BoNiTo> now it just dump me to the text login screen
[03:24] <BoNiTo> some1 know if I can ppa-purge this repository?
=== Amaranth_ is now known as Amaranth
[12:36] <apw> tseliot, i seem to be having trouble with the dell 10v dead area stuff
[12:36] <apw> its doesn't seem to be taking my area thingy, has anything changed there?
[12:37] <apw> yeah feels like its not longer a feature
[12:37] <apw> could we have lost the patch?
[12:43] <apw> tseliot, user error ... that 8 is an input channel and mine have randomly moved about today
[13:16] <tseliot> apw: the patch should be there. Did you execute the xinput command in a script (pointing to device 8)?
[13:17] <apw> yeah i used 8, which its not now, its 6, but that command takes the name as text, much better
[13:24] <tseliot> right
=== marjomercado is now known as marjo
[14:01] <apw> tseliot, bryce, either of you got any bluetooth keyboards/mice ?  considering some fixes for them as they apparently appear but never dissappear and fill the X device slots ...
[14:01] <apw> so wondering if either of you have stuff you could test the proposed fixes with?
[14:02] <tseliot> apw: sorry, I don't have any
[14:02] <apw> damn i was hoping you of all people might have
[14:07] <tseliot> let's wait for bryce
[14:07] <tseliot> tjaalton: do you have one? ^^
[14:08] <tjaalton> tseliot: nope..
[14:09] <tseliot> ok, thanks anyway
[14:10] <tjaalton> should get one for my ps3 though
[15:06] <Ng> so if you'd been dragging a window around with alt-button1 and X got a bit confused and kept that pointer and wouldn't let you click on anything, what would you do? :)
[15:06] <Ng> your available tools are a terminal and/or a console :)
[15:09] <Ng> it appears to persist across suspending
[15:22] <apw> try hitting all the meta keys, crtl, alt etc to make sure they are all released
[15:23] <Ng> no joy :/
[15:23] <jcristau> sounds like the window manager getting confused and not releasing a grab
[15:30] <Ng> jcristau: another interesting idea. bouncing compiz in the face didn't help (although maybe it wouldn't)
[17:19] <bryce> no bluetooth gear myself
[17:51] <bryce> jbarnes, mind taking a look at https://bugs.freedesktop.org/show_bug.cgi?id=24383 ?   It's our one last release-important X bug on -intel
[17:51] <ubottu> Freedesktop bug 24383 in Driver/intel "[KMS] Black screen when xserver is reset (KDE logout)" [Normal,New]
[17:51] <bryce> there's a patch for it, however I don't want to include it without upstream's review
[17:54] <jbarnes> sounds like the regen bug?
[17:54] <jbarnes> oh hm yeah the patch makes some sense
[17:55] <jbarnes> bryce: I'll push that patch upstream
[17:55] <jbarnes> feel free to include it
[17:56] <bryce> jbarnes, excellent thanks
[19:00] <jcristau> jbarnes: maybe cherry-pick to 2.9 as well?
[19:00] <jbarnes> jcristau: sure I guess that makes sense
[19:13] <rickspencer3> bryce, hi, have all three of those radeon bugs been resolved now?
[19:14] <bryce> rickspencer3, 2 of them have.  Need to check in on the 3rd
[19:14] <rickspencer3> is the third one for that ancient chip?
[19:14] <bryce> rickspencer3, aforementioned discussion is regarding the KDE/X bug listed on your karmic status page; fix was taken upstream so I'm uploading it presently.  :-)
[19:14] <bryce> rickspencer3, that's right
[19:15] <rickspencer3> so is the last bug a ship stopper?
[19:15] <bryce> rickspencer3, also I took a look at his configuration closer and it's a bit non-standard so I'm having him create a cleaner test environment to re-verify.  I'll follow up.
[19:15] <rickspencer3> ok
[19:15] <rickspencer3> so, seems that there are no further issues?
[19:15] <bryce> not in my opinion
[19:16] <rickspencer3> and xorg stack is more or less in the can, modulo this upload that you would be dong if I weren't pestering you for status?
[19:16] <bryce> there are still some bugs that people are passionate about, but to be honest I think people have some widely varying ideas of what constitutes "show stopper" 
[19:16] <rickspencer3> hmm
[19:16] <rickspencer3> are these bugs new due to the mesa update, or unrelated?
[19:16] <bryce> oh completely unrelated
[19:17] <rickspencer3> well then
[19:17] <rickspencer3> that's just normal "fix bugs in priority order" work
[19:17] <bryce> most of these that I'm looking at right now are long-standing issues that have had patches posted to them in recent months, that I just hadn't had time to review before now
[19:17] <bryce> right
[19:17] <rickspencer3> alrighty, talk to you later
[19:17] <bryce> I'm just harvesting targets of opportunity that look safe
[19:17] <rickspencer3> righto
[19:17] <bryce> rickspencer3, great, cya
[19:17] <rickspencer3> sounds great
[20:23] <ilmari> huh, X eats 100% CPU and can't switch VTs when started before acpid
[20:23] <jcristau> it has nothing to do with acpid.
[20:23] <ilmari> restarting X after acpid has started or adding "and started acpid" to the gdm upstart job fixes it
[20:24] <jcristau> it still has nothing to do with acpid.
[20:24] <ilmari> might be something else that it needs to wait for
[20:25] <jcristau> that's bug 439138
[20:25] <ubottu> Launchpad bug 439138 in cryptsetup "[karmic] Xorg 100% CPU utilization -- only after first login" [Undecided,Confirmed] https://launchpad.net/bugs/439138
[20:26] <ilmari> cryptsetup?
[20:28] <ilmari> ah
[20:30] <ilmari> okay, but X still complains about not being able to open acpid.socket
[20:30] <ilmari> (if gdm is started before acpid, that is)
[20:31] <ilmari> what does X not being able to open ACPI affect?
[20:31] <jcristau> nothing
[20:32] <jcristau> well it generates wrong impressions like yours that it matters
[20:34] <ilmari> why does it try to open acpi or apm then?
[21:03] <Afzal> hi! need help for nouveau-kernel-source & xserver-xorg-video-nouveau in my newly upgraded ubuntu9.10
[21:03] <Afzal> any suggestion  is appreciated