[07:03] <tjaalton> jcristau: prevents upgrades, says slangasek
[07:04] <tjaalton> jcristau: sorry for not mentioning that in the first place :)
[07:05] <jcristau> so what should i do to get the package manager to remove the obsolete package?
[07:09] <tjaalton> Replaces should do according to him
[07:10] <jcristau> hrm. i thought replaces was about replacing files. /me goes read policy.
[07:11] <RAOF> I've missed the first part of this, but Conflicts+Replaces sounds like what you want, I think.
[07:12] <jcristau> oh. 7.6.2.
[07:17] <jcristau> Replaces: libxcb-xlib0 is enough, or do i add the -dev?
[07:20] <tjaalton> if libxcb1-dev replaces libxcb-xlib0-dev, then perhaps
[07:21] <jcristau> installing the new libxcb1 breaks libxcb-xlib0, and thus also libxcb-xlib0-dev
[07:23] <jcristau> so i'm not sure explicitly replacing is needed. and if it is where it should be.
[07:23] <jcristau> (also fwiw 'apt-get -t experimental dist-upgrade' does remove libxcb-xlib0)
[07:24] <jcristau> gah, s/explicitly replacing/& libxcb-xlib0-dev/ above.
[07:27] <tjaalton> works here too, but I'm just the middle-man :)
[07:28] <jcristau> bad vorlon.
[07:28] <tjaalton> maybe prod him on #debian-x :)
[07:53] <jcristau> that worked :)
[07:54] <tjaalton> yeah :)
[08:26] <tjaalton> turns out to be quite hard to debug a crashing xserver on acpi resume
[08:27] <jcristau> last time that turned up, screen came to the rescue
[08:27] <tjaalton> maybe I didn't use the correct options for gdb
[08:28] <jcristau> you told it to not stop on sigusr1?
[08:29] <tjaalton> I did now, let's see
[08:31] <tjaalton> hey, I've got a backtrace
[08:31] <tjaalton> let's try with -dbg
[08:36] <tjaalton> http://bugs.freedesktop.org/attachment.cgi?id=22303
[13:34] <ogra> tjaalton, seems ouchscreens with the new evdev infrastructure dont work at all ... (just got some user feedback, didnt look myself yet)
[13:38] <tjaalton> ogra: that's unfortunate
[13:39] <tjaalton> tseliot: new nvidia*.. but you probably knew that already :)
[13:39] <ogra> yes, StevenK tested it today and he sees no motion at all tapping or touching the screen
[13:39] <tjaalton> does evdev pick the device?
[13:39] <ogra> it should at least show some miscalibrated movement 
[13:40] <tjaalton> logs etc in a bug report would be nice :)
[13:40] <jcristau> and evtest output probably
[13:40] <tjaalton> yes
[13:41] <tjaalton> tseliot: oh, they still don't support the current ABI
[13:42] <tjaalton> seems that aaron didn't get his message through
[13:42] <tjaalton> (or the got problems)
[13:42] <tjaalton> *they
[13:43] <tjaalton> hmm, legacy drivers apparently do support the new ABI
[13:48] <tseliot> tjaalton: maybe he forgot to add a note about the new ABI in the changelog
[13:48] <tseliot> I'll test them
[13:48] <tjaalton> could be
[13:49] <tjaalton> Maple v12 crashed my jaunty today.. after I resized the window. I blame nvidia :)
[13:49] <tseliot> well, running drivers with IgnoreABI is not recommended ;)
[13:50] <tjaalton> yeah..
[13:50] <tseliot> but I do it
[13:50] <tjaalton> I'd like to listen to my music though
[13:50] <tjaalton> no sound on the desktop or the laptop..
[13:50] <tseliot> don't resize the window then
[13:51] <tseliot> or is it pulseaudio?
[13:51] <tjaalton> of course it works now, can't reproduce it :)
[13:51] <tseliot> hehe
[13:51] <tjaalton> I've had issues with sound since pa 0.9.14 was uploaded
[13:51] <tjaalton> well, no sound
[13:52] <tseliot> audio is choppy here e.g. when I switch between windows
[13:53] <tjaalton> for instance the playing doesn't even start, it just hangs there
[13:53] <tjaalton> +in rhythmbox
[13:53] <tjaalton> and if I kill pa, no sound
[13:54] <tseliot> :-/
[13:54] <tseliot> did you talk to theMuso about it?
[13:55] <tjaalton> yes
[13:55] <tseliot> no solution?
[13:55] <tjaalton> he could reproduce some of the issues, but no solution
[13:55] <tseliot> ok, then
[13:55] <tjaalton> for instance alsamixer fails to start
[13:55] <tseliot> pulse_haters++
[13:55] <tseliot> but isn't that a bug in alsa?
[13:56] <tjaalton> that too
[13:57] <tjaalton> but I'm hopeful that the commits he requested for the kernel might help
[14:01] <tseliot> keep your fingers crossed then
[14:12] <tjaalton> I will..
[14:15] <ogra> tjaalton, hrm
[14:16] <ogra> so i'm trying out the samsung Q1 with the new ubuntu-netbook-remix image ... it still includes evtouch ... lshal shows me though that "synaptics" is forcefully used for the touchscreen
[14:16] <ogra> while the evtouch initscript seems to have run and all calibration data is applied
[14:16] <ogra> shouldnt it use evdev ? 
[14:17] <ogra> instead of synaptics
[14:17] <tjaalton> yes
[14:17] <tjaalton> but that depends what the new image holds
[14:17] <jcristau> sounds like it shouldn't be reported as a touchpad..
[14:17] <tjaalton> +on
[14:17] <tjaalton> right
[14:18] <ogra> well, lshal shows capabilities input and input.touchpad ... where does touchpad get set  ?
[14:18] <ogra> is there an fdi i can mangle ? 
[14:18] <jcristau> probably hal source
[14:19] <tjaalton> ogra: what version of hal?
[14:19] <jcristau> and probably based on what the kernel reports about the device
[14:19] <tjaalton> I bet it's too old
[14:19] <ogra> its todays image build 
[14:19] <ogra> so whatever is in the archive atm
[14:19] <tjaalton> ok, maybe hal is still missing something.. bug pitti :)
[14:20] <ogra> git20090120-0ubuntu1
[14:43] <tseliot> seb128, mvo: can you merge from my branch, please? https://code.launchpad.net/~albertomilone/gnome-control-center/randr-virtual
[15:02] <tseliot> seb128, mvo: this adds the DontZap checkbox to enable users to decide whether Ctrl+Alt+Backspace can restart X or not
[15:44] <superm1> tseliot, while you are getting the upload ready for the new drivers, did you have a fix queued for https://bugs.edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/309116 ?
[15:45] <tseliot> superm1: I won't upload the new drivers without fixing that first
[15:45] <tseliot> ;)
[15:45] <superm1> tseliot, okay :)
[17:29] <bryce> morning
[17:43] <bryce> I spoke with amd this morning and asked them for a date on when they expect to provide a 1.6/.28 compatible fglrx
[17:44] <bryce> they didn't have that info currently but will try to get it by the end of the week
[17:47] <tjaalton> ok
[17:47] <tjaalton> nvidia released new versions of the legacy drivers
[17:47] <bryce> sweet
[17:48] <bryce> yeah amd seemed a bit surprised that we were planning on 1.6 for 9.04.  I had to remind them I emailed them a month and a half ago that this was our plan
[17:49] <tjaalton> heh
[18:02] <superm1> bryce, any indications from them if a driver will be coming more than 1 month prior to release this time around?
[18:04] <bryce> superm1: I pressed them on giving us a date.  they said they'll get back to us after they've "scrubbed their schedule"
[18:06] <bryce> I would be feeling frustrated if the deja vu feelings weren't keeping me in such mirth
[18:13] <federico1> mister bryce
[18:13] <bryce> superm1: anyway, so I sense we're going to be in about the same situation as last time, despite our efforts.
[18:13] <federico1> I resurrected the 10-second confirmation dialog for the RANDR tools and committed it to gnome svn
[18:13] <bryce> federico1: oh interesting
[18:14] <superm1> bryce, oh that's too bad :(
[18:14] <federico1> bryce: http://bugzilla.gnome.org/show_bug.cgi?id=545115
[18:14] <superm1> bryce, well at least this time, all the packaging is ready and it's at least easy to update new drops etc
[18:15] <federico1> bryce: are you or anyone here in distributor-list?
[18:15] <federico1> I'll post an evil patch to deal with wacom tablets and RANDR
[18:15] <bryce> federico1: "distributor-list"?  first I've heard of that; what is it?
[18:16] <bryce> federico1: thanks for committing that revert dialog patch; I'd been disappointed that it hadn't been taken previously
[18:16] <tseliot> federico1: what's the plan on wacom tablets?
[18:17] <bryce> superm1: yep.  
[18:17] <federico1> bryce: distributor-list@gnome.org
[18:18] <bryce> federico1: ah, I bet seb128 is on that list, he usually handles the gnome interfacing
[18:19] <federico1> ah, ok
[18:19] <federico1> tseliot: one sec, meeting
[21:28] <kees> fun
[21:28] <kees> [ 6009.433242] mtrr: no MTRR for f0000000,100000 found
[21:28] <kees> [ 6009.604066] Xorg[12735] general protection ip:4961b6 sp:7ffff1fccde0 error:0 in Xorg[400000+1c2000]
[21:28] <kees> 64bit jaunty under kvm
[21:31] <superm1> kees, i've been seeing mtrr: no MTRR for e0000000,10000000 on real systems, is there any significance to what that's representing?
[21:41] <kees> superm1: not sure.  :(
[21:41] <superm1> kees, oh okay.  just wasn't sure what MTRR was an abbreviation for.
[21:44] <bryce> I've seen reports about that
[21:45] <bryce> btw speaking of acronyms I finally learned what fglrx stands for...  "FireGL and Radeon for X"
[21:45] <bryce> MTRR == Memory Type Range Registers maybe?
[21:45] <bryce> http://www.mjmwired.net/kernel/Documentation/mtrr.txt
[21:57] <kees> bryce: ah! I've always wondered wtf fglrx stood for.  :)
[21:58] <tormod> well we always knew it was an f-word
[22:00] <tormod> bryce: landslide in radeon git today - what are your plans for updating jaunty? There's some agp quirks etc that otherwise could be cherrypicked
[22:01] <tjaalton> bryce: got a patch from jesse for the interrupt loss when using vblank, will try it out tomorrow
[22:03] <tjaalton> against the kernel(drm) though, so a bit harder to get through if it works
[22:17] <bryce> tjaalton, ok
[22:17] <bryce> tormod: I anticipate updating -ati at least once more before we're done with jaunty
[22:18] <bryce> even if that might mean shipping a git snapshot.  A release would be nice of course, but we've shipped git snapshots before
[22:25] <tormod> bryce: good
[22:26] <bryce> tormod: at some point post-beta I also will be pulling any outstanding quirks for both -ati and -intel