[06:20] <DanaG> Hmm, anyone here familiar with the Bamboo Touch device?
[06:20] <DanaG> https://lists.launchpad.net/multi-touch-dev/msg00314.html
[06:20] <DanaG> I just got a new Wacom Bamboo Touch (no pen) as a gift. I want to know how much gesture support there is in Linux, before opening it.
[06:51] <DanaG> I'm back.  Anyway, so I'll idle here in case anyone later answers about bamboo touch.
[08:54] <xelister> hello
[08:54] <xelister> guys how to try 10.11 catalyst driver best on ubuntu
[09:29] <Yefloa__> hi, problem installing propertiary driver (ati... . run) driver 10.11, into Ubuntu maverick (10.10) amd64.  aticonfig --initial -f    says no adapters detected.  I run the .run --buildpkg and then dpkg -i *dpkg and rebooted. How to fix?
[10:09] <Yefloa__> im getting:    failed to load: libfglrxdrm.so   any idea why?  or how to debug    Trying to install binary 10.11 catalyst
[10:09] <Yefloa__> libatiuki.so no such file
[10:13] <Yefloa__> the file is present in /usr/lib/fglrx/
[10:14] <Yefloa__> overall X has trouble finding so files.  The files are there, but they are named .so.1  instead .so (ln -s fixes)   or some other .so file can not find other .so file ... what the fuck is going on here
[10:16] <Yefloa__> ATI support is shitty.
[10:29] <vish_> how do i debug a freeze?
[10:29] <vish_> X has just frozen and when i'm sshing into the client, i'm not even able to Ctrl-C 
[10:30] <vish_> X is just frozen, and the only way seems to be for me to Alt+Sys+k.. , it there anyway for me to get some backtrace from this freeze? 
[10:31] <vish_> Xor.log doesnt show anything special , so i'm not even sure what break points to set ..
[10:31] <vish_> Xorg.0.log
[10:52] <Duke`> hi
[10:52] <Duke`> latest xorg-video-intel is broken on my i945/maverick (black screen after splash screen)
[11:02] <Yefloa__> ok never mind... the problem was old nvidia modules/shit that was not uninstalled
[16:11] <Sarvatt_> Duke`: copy-fb broken again, fixed one is uploaded now
[16:14] <Duke`> okay
[16:15] <Duke`> on maverick too?
[16:16] <Sarvatt_> yeah
[16:16] <Sarvatt_> hmm failed to build on maverick http://launchpadlibrarian.net/60147488/buildlog_ubuntu-maverick-i386.xserver-xorg-video-intel_2%3A2.13.901%2Bgit20101205.c2fac6ca-0ubuntu0sarvatt2~maverick_FAILEDTOBUILD.txt.gz
[16:25] <Sarvatt_> savage failed the same way, i think the maverick buildds are screwed up. will keep retrying it
[17:04] <greg-g> hey all, any suggestions on how to triage/debug this issue? https://bugs.launchpad.net/bugs/682864 (I'm the reporter)
[17:04] <ubot4`> Launchpad bug 682864 in xserver-xorg-video-intel (Ubuntu) "[GMA 4500MHD] Display freeze after VGA cable disconnected (affects: 1) (heat: 6)" [Undecided,New]
[17:30] <Sarvatt_> Duke`: looks like the linux-libc-dev in 2.6.37-8 is screwed and it didn't hit natty yet because it's still waiting in NEW, rebuilding now
[17:32] <Sarvatt_> greg-g: I'm 99% sure your problem is https://bugs.launchpad.net/ubuntu/natty/+source/xserver-xorg-video-intel/+bug/626967
[17:32] <ubot4`> Launchpad bug 626967 in xserver-xorg-video-intel (Ubuntu Natty) (and 2 other projects) "MASTER: Hang in MI_WAIT_FOR_EVENT on framebuffer switch. (affects: 29) (dups: 41) (heat: 314)" [Medium,Fix released]
[17:33] <Sarvatt_> greg-g: hopefully should have that fixed in -proposed/-updates soon, if you need it fixed now you can enable this PPA https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
[17:33] <greg-g> Sarvatt_: I can test that PPA, sure. Thanks!
[17:33] <greg-g> I'll leave my bug open for now but subscribe to that one.
[17:35] <vish> Sarvatt_: hey, how do i debug a freeze? i'm trying to follow the wiki, but i have no clue as to what the function name can be.. for (gdb) break <function-name>
[17:35] <vish> is there any list of function names?
[17:35] <vish> the X freeze happens at random when scrolling
[17:37] <Sarvatt_> vish: gdb break make_me_freeze? :) it could be anything, if you aren't getting a crash gdb aint gonna help that much, you want to find a way to avoid the freeze to narrow down the suspects probably
[17:37] <Sarvatt_> like, does it happen without compiz?
[17:38] <vish> hmm, i havent tried without compiz..
[17:38] <Sarvatt_> what gpu is it?
[17:38] <vish> RV515
[17:38] <Sarvatt_> what kernel?
[17:39] <vish> .35
[17:39] <vish> and it doesnt crash, i'v ssh'd into the session, it just freezes and doesnt mention any crashes
[17:39] <Sarvatt_> nothing in dmesg?
[17:39]  * vish checks..
[17:41] <vish> nope, no mention of 'errors' in dmesg
[17:41] <vish> error too
[17:42] <vish> when it freezes i'm only able to move the pointer and nothing reacts..
[17:43] <vish> random freezes are a bother :/ , it freezes very randomly when i'm scrolling something, its like living with a constant fear of being frozen ;p
[17:43] <Sarvatt_> gpu hang and nothing in dmesg or the xorg.0.log? thats odd
[17:44] <Sarvatt_> how about /var/log/gdm/:0.log?
[17:45] <Sarvatt_> would be at the very bottom if there's anything there
[17:47] <Sarvatt_> vish: sorry to run but the wife wants to go christmas shopping and i've been stalling for 2 hours now as it is, gotta run
[17:47] <vish> Sarvatt_: sure, no hurry,  thanks.. :)
[17:49] <Sarvatt_> vish:  you could try just attaching to the X process and getting a bt to see what its stuck doing maybe
[17:49] <Azelphur> Sarvatt_: still getting that issue with the X crashes, got another backtrace on the way :D
[17:49] <Azelphur> It's at 82,000 entries and counting, it's still printing it all out rofl
[17:49] <vish> Sarvatt_: yeah, i tried attaching, but it just hangs with nothing else..
[17:50] <vish> it just stays "Continuing." even when it is frozen
[17:51] <Sarvatt_> if you attach with -p and the X process id it'll wait for you to cont manually, and you can just bt from there instead of cont
[17:52] <vish> ah ha!
[17:52] <vish> Sarvatt_: so i should attach *when* it is frozen?
[17:52] <vish> i hadnt tried that, thanks :)
[17:52] <jcristau> or attach before, and then ^c when it's frozen
[17:53] <vish> jcristau: i tried Ctrl-C , and Ctrl-\ but they dont seem /visually/ to cause it to break, i might have to type commands blindly the next time i guess
[17:54] <vish> once i ^C , it just stays that way, and i dont get back to the (gdb) prompt'
[17:54] <Sarvatt_> you need to start X with another command for ^c to work in gdb dont you? seem to remember having that problem before
[17:54] <vish> the last time i had to blindly type "quit" and "y" to detach..
[17:55] <Sarvatt_> blindly? are you using gdb on the same machine? ya want to do it over ssh
[17:55] <vish> ssh
[17:56] <Sarvatt_> like -keeptty or something, argh can't remember
[17:57] <Sarvatt_> Azelphur: dont keep trying to get the backtrace, it's going to just recurse forever and isn't useful for your crash, sucks that upgrade didn't fix it :(
[17:57]  * Sarvatt_ disappears for real
[17:59] <vish> this i what i see in the terminal (when i'v ssh'd) :
[17:59] <vish> (gdb) cont 
[17:59] <vish> Continuing. 
[17:59] <vish> ^\^C^\^\^C^C^C^C^Cquit
[17:59] <vish> y 
[17:59] <vish> Quit
[18:00] <vish> i'm just expecting the gdb prompt to be there and quitting
[18:00] <vish> while the gdb record has only :
[18:00] <vish> (gdb) cont
[18:00] <vish> Continuing.
[18:02] <Azelphur> haha
[18:02] <Azelphur> yea it's mostly the same thing
[18:03] <vish> heh, but i found it interesting that the X keeps getting a lot of SIBPIPE and broken calls … ;p
[18:03] <vish> broken pipe rather..
[18:03] <Azelphur> bryceh / bryceh_ you wanted a backtrace from the crashes I was having yesterday on my 9500GT in arecord, http://pastebin.com/uZ8RnB57
[18:04] <Azelphur> that's a small part of it, but it just keeps printing the same thing, I'm curious to see how deep it is, as you can see I'm already at 120k recursions :D
[18:05] <Azelphur> ah it finished, 127,060 :D
[18:08] <Azelphur> http://dl.dropbox.com/u/3832397/misc/gdb-Xorg.txt.tar.gz here's the full backtrace
[18:08] <Azelphur> probably wanna think about what text editor you open that in though, it's 358k lines
[22:12] <RAOF> Wow.  Busy weekend.
[22:23] <tuga3d> hi all, anyone using xorg-edgers ppa?
[22:26] <RAOF> A fair number of people do, yes.
[22:26] <Sarvatt_> tuga3d: if you're using intel on maverck it should be fixed now if you update
[22:26] <RAOF> Sarvatt_: Good $TIME_OF_DAY :)
[22:27] <Sarvatt_> heya RAOF :)
[22:27] <Sarvatt_> copyfb broken again post 2.13.901 :(
[22:27] <tuga3d> Sarvatt_: i'm using nvidia with nouveau drivers and i get this error trying to start blender
[22:27] <tuga3d> blender: nvfx_state_fb.c:36: nvfx_surface_get_render_target: Assertion `target->pitch' failed.
[22:28] <tuga3d> since the update i made today :(
[22:28] <tuga3d> Sarvatt_: on maverick
[22:28] <Sarvatt_> what mesa version?
[22:28] <Sarvatt_> ah
[22:28] <RAOF> Sarvatt_: copyfb should get pushed upstream with 1.10, now that the server-side bits have actually happened :)
[22:29] <tuga3d> Sarvatt_: 7.10
[22:30] <Sarvatt_> tuga3d: fixed upstream, i'll package a new one up now
[22:30] <Sarvatt_> http://cgit.freedesktop.org/mesa/mesa/commit/?id=af5345d9371e927019d51ce3ad198958f8cd42a9
[22:30] <tuga3d> :) cool
[22:30] <tuga3d> Sarvatt_: thanks!!!
[22:31] <Sarvatt_> no worries, will take about 30 minutes to show up, thanks for the heads up :)
[22:31] <tuga3d> Sarvatt_: wow! thank you
[23:28] <tuga3d> Sarvatt_: working great, thanks again