GalaxorI get a black screen when trying to play video using Xv.  I can switch it to native X11 video just fine, and that's how I've been playing videos.  I've got enough cpu that it hasn't yet been an issue.  Still...00:00
GalaxorOh, that was weird.  It was just that my contrast was set to -1000 in nvidia-settings.  I wonder how it got like that.  Oh well, that's fixed.00:02
GalaxorAnd that concludes the bugs.  My new computer now works perfectly.00:02
RAOFSarvatt|gone: That's a fine idea, too.01:02
brycehheya RAOF02:38
RAOFbryceh: Howdie02:44
artfwoHello! I've stumbled upon a bug (actually 2 bugs), introduced by xserver-xorg-input-evdev 1:2.3.2-6ubuntu1. Could anyone experienced take a look?05:03
artfwoBugs in question are bug 41301 and bug 58331205:03
ubot4Launchpad bug 41301 in xserver-xorg-input-evdev (Ubuntu) (and 2 other projects) "Mouse clicks stop working sporadically (affects: 41) (dups: 5) (heat: 270)" [Undecided,New] https://launchpad.net/bugs/4130105:03
ubot4Launchpad bug 583312 in xserver-xorg-input-evdev (Ubuntu) "Left mouse clicks not being processed (affects: 2) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/58331205:03
artfwoDowngrading to xserver-xorg-input-evdev 1:2.3.2-6build1 solves the problem for me05:03
RAOFHm, interesting.05:06
artfwoI'm almost certain, that the bug is introduced in debian/100-fix-touchup-problem-on-touchpads.patch05:11
artfwobecause it does something with switching absolute/relative axes, and my mouse works with absolute axes, judging by Xorg.0.log05:12
artfwobut axes have nothing to do with buttons on the other hand, weird05:12
RAOFIndeed :)05:12
artfwowhile I was experiencing the bug, switching mice actually helped05:14
artfwohere's what happens, when I plug in the "buggy" mouse http://pastebin.ubuntu.com/487615/05:14
artfwoand this is Xorg.0.log for "working" mouse http://pastebin.ubuntu.com/487616/05:15
artfwoanyway, A4tech mouse worked okay without the latest patch05:16
artfwoI'm thinking of perhaps opening a new bug report for the Maverick behaviour, is it reasonable?05:24
RAOFYes, I think so.05:25
RAOF20 mouse buttons!!!05:26
artfwothere are actually only 6 + the wheel :)05:27
RAOFI wonder if that's actually a kernel problem, then.05:28
RAOFI guess it shouldn't be, if switching evdev versions fixes it.05:29
artfwowell, the ubuntu patch could introduce a dependency on "kernel stuff done right"05:31
artfwoand in turn, triggered a bug, because of a kernel problem05:32
RAOFYour A4tech thing is a mouse, not a touchpad, isn't it.05:46
RAOFAnd you've only got one of them, right?05:46
artfwobut the laptop has built-in touchpad05:47
RAOFIt looks like X thinks both /dev/input/event12 and /dev/input/event13 are the A4Tech thingy.05:51
artfwoalso /dev/input/js1 and dev/input/mouse305:54
artfwojs* are the joysticks06:06
RAOFAh, right.06:06
RAOFAnd you've got one of those plugged in, I presume.06:07
artfwowith all the USB stuff unplugged, I still get [ 15360.722] (II) config/udev: Adding input device A4Tech USB Full Speed (/dev/input/js0)06:11
artfwolooks like the mouse is detected as mouse, keyboard and joystick simultaneously06:11
RAOFAnd with 37 axes, and 20 buttons.06:12
artfwobut that seems unrelated, because my external USB keyboard also produces lines like [ 15468.588] (II) config/udev: Adding input device Logitech Logitech USB Keyboard (/dev/input/js1)06:12
artfwowhen plugged in06:12
artfwoand... [ 15468.581] (II) Logitech Logitech USB Keyboard: Found 20 mouse buttons06:13
RAOFWhat does “udevadm info --query=all --name=/dev/input/js1” say?06:13
artfwoRAOF, http://pastebin.ubuntu.com/487633/06:14
RAOFYour keyboard doesn't happen to have a joystick-like thing on it?06:15
artfwoonly a scrollwheel06:15
artfwobut the bug above happens without the keyboard, that's for sure06:16
artfwo*with or without06:16
RAOFThings just appear weird.06:18
RAOFDo you have the a4tech device plugged in now?06:18
artfwoyes, with evdev downgraded06:18
RAOFWhat event node is it?06:19
RAOFAnd can you grab the udevadm info for it?06:19
artfwoI can, but for which device - js0?06:20
artfwohere it is http://pastebin.ubuntu.com/487635/06:20
RAOFAnd, just for the record, this is a pure mouse, right?06:21
RAOFThe fact that it's got ID_INPUT_KEYBOARD=1 set is a total lie?06:21
artfwoI guess so06:21
artfwothe mouse hasn't any builtin keyboard06:21
artfwoif I query /dev/input/mouse0 this string goes away06:22
RAOFAnd I'd wager that one of the (many!) /dev/input nodes has ID_INPUT_TOUCHPAD=1 set.06:24
artfwo/dev/input/mouse2 has it06:24
RAOFAnd is the A4tech mouse?06:25
artfwoI think it's the builtin touchpad06:25
RAOFIt's your honest-to-goodness touchpad?06:25
RAOFNone of the patches in evdev look particularly suspicious.06:30
RAOFThis only starts happening after some period of time, yes?06:31
RAOFNot straight after startup?06:32
artfwoyes, in an absolutely random, but rather short period06:32
artfwoI think it's most often triggered by chromium and empathy windows, but also happens in nautilus and gimp06:33
artfwothe system is absolutely unusable afterwards. it behaves like the left mouse button is down all the time06:36
artfwokeeps selecting bunches of text, or dragging the windows06:36
artfworight & middle continue to work, as well as the wheel06:36
artfwoI can alt+tab between windows, catch events in xev, etc.06:37
artfwounplugging the mouse and clicking left button on the touchpad returns everything to normal06:37
RAOFartfwo: What architecture are you on?  I'd like to prepare a couple of packages to see which patch is breaking for you.06:59
artfwoRAOF, x8607:59
* RAOF updates his i386 chroot08:00
RAOFartfwo: http://cooperteam.net/Packages/xserver-xorg-input-evdev_2.3.2-6ubuntu2~notouchupfix_i386.deb is a first hack at it.08:12
artfwoRAOF, installing right now08:12
artfwoRAOF, your package made the bug reappear almost immediately08:15
RAOFOk; second one without gesture support.08:16
RAOFartfwo: http://cooperteam.net/Packages/xserver-xorg-input-evdev_2.3.2-6ubuntu2~nogestures_i386.deb08:24
artfwookay, let me restart X...08:25
artfwoRAOF, it looks like everything's okay now08:27
ScottKNow I understand why my mini 10v looks like crap on Kubuntu Maverick: http://blog.martin-graesslin.com/blog/2010/09/driver-dilemma-in-kde-workspaces-4-5/13:41
ScottKAny suggestions on how to usefully file bugs/troubleshoot compositing problems for this?13:42
jcristauget the kde people to talk to mesa driver devs?13:43
ScottKUnlikely to provide much relief on the maverick timeline.13:45
tseliotScottK: I think you can switch to Xrender instead of OpenGL for compositing (as a temporary workaround)13:54
ScottKtseliot: Thanks.  I'll try that.13:55
=== Sarvatt|gone is now known as Sarvatt
Sarvattevery time I read this guys blog I get the impression he thinks everyone not using nvidia proprietary drivers is doing it wrong :)14:07
Sarvattand that its just a matter of getting drivers ready to do opengl 2.0 and not a hardware limitation of hardware thats still shipping today14:09
jcristauSarvatt: and that driver bugs get fixed out of thin air, without anybody reporting issues to the devs14:11
Sarvattyeah especially that14:11
ScottKtseliot: Much better.  Thanks.14:13
tseliotScottK: np14:14
SarvattScottK: can ya describe "looks like crap"?14:14
tseliotno desktop effects14:14
tseliotand KDE doesn't look extremely good without them14:14
Sarvattoh they were just disabled completely? they added all that fallback infrastructure and only made it do GL->off instead of falling back to xrender?14:15
ScottKSarvatt: Yes and then when I enable them manually the screen suffers from flashes and incomplete rendering.14:15
SarvattScottK: it would be interesting if you could try this with gl composting - https://edge.launchpad.net/~sarvatt/+archive/mesa14:16
ScottKIs there anything we can do about getting it to fall back to xrender?  Compositing is pretty essential for the Plasma Netbook interface.14:16
ScottKSarvatt: Sure.  That machine is expendable.14:16
ScottKSarvatt: That machine had an X crash on logout too (945gme).  Could that be affected by the same issue we tested on 865 yesterday?14:26
SarvattScottK: yup14:26
SarvattI've been struggling with fixing that patch but haven't had any luck yet, planning on spending all day today on it14:28
Sarvattoh joy, the blacklists for broken features in KDE specifically don't include -devel in the mesa version string so that mesa might not work right even if it will once its released. if only we could get an RC here soon :(14:35
Sarvattit looks like the only things that work right basically are proprietary drivers, nouveau, i965+ intel if you specifically blacklist blur, r300-r500 ati using gallium only and r600+ ati from mesa git14:38
ScottKInteresting experience.14:40
ScottKIt seems like things are slower, but much smoother than the current mesa.14:40
SarvattKDE 4.6 is going to be even worse no doubt since it's going opengl 3 that no free drivers implement and backwards compatability isn't planned until 4.7? wow14:40
Sarvattinteresting. I thought opengl compositing didn't work at all in 7.8.2?14:42
ScottKIt was slow enough that I had to disable functionality checks to keep it from disabling effects for being too slow.14:43
ScottKNo flickering though14:43
ScottKActually after rebooting, its14:43
Sarvattthat was with mesa 7.9 that you had to do that?14:43
ScottKmuch better.14:43
ScottKWhatever was in your ppa14:44
ScottKActually after rebooting instead of logging out, crashing X, and restarting it's quite snappy14:45
ScottKLarge blurs will still cause it to suspend effects, but other than that, works reasonably well.14:46
Sarvattwhat I have in that PPA is what we have in git and are going to try to file a FFe to get into maverick, it fixes quite a lot of bugs. it's due out in final release form by the end of september (and I'm very confident it will hit release on time) but there isn't a release candidate yet :(14:47
SarvattScottK: that should be fixed once there is a release candidate of it so the version string doesn't say -devel, it's not applying the blacklist to fix blur because of that from what I'm reading14:47
ScottKOK.  That's cool.14:48
ScottKFeel free to mention Bug #628930 in your FFe request.14:48
ubot4Launchpad bug 628930 in kdebase-workspace (Ubuntu Maverick) (and 1 other project) "Desktop effects not active by default (affects: 1) (heat: 6)" [High,New] https://launchpad.net/bugs/62893014:48
SarvattScottK: thanks, I was just going to ask if you knew of any bugs14:49
SarvattRAOF: ^14:49
ScottKSarvatt: With just blur disabled and your new mesa the system works well again.  I think on the Kubuntu end of things we will pursue disabling just blur by default on netbooks (netbooks will ~all be affected by this).  That and your planned mesa update should get us into a releasable state.15:13
SarvattScottK: thats a good idea in general, the blur only works properly on proprietary drivers apparently and that guy didn't want to disable that feature globally because he thinks the majority of people use those where it works :)15:16
ScottKThere was about a week where it worked on intel.15:17
Sarvatt965+ or your 945?15:18
ScottKHe changed something between KDE 4.5 RC and final that killed it.15:18
ScottKI marked that bug to also affect mesa, FYI, so you have something to fix too.15:19
Sarvattit's glsl only so I can't see how it ever worked on 945, hmm15:19
ScottKDunno.  I sometimes have low standards for 'worked' when running the development release.15:20
Sarvattwow, there are an amazing amount of INTEL_DEBUG env variables in mesa15:26
SarvattRAOF: oh sheesh, it's X: ../../dix/pixmap.c:118: AllocatePixmap: Assertion `pScreen->totalPixmapSize > 0' failed. breaking sandybridge, didn't we have this problem before?16:47
Sarvattoh hmm, i'm on the 31st iteration of screwing with 101_copy-fb.patch, best check with stock before I say that :)16:48
ScottKSarvatt: mgraesslin says opengl 3 in KDE 4.7 and they aren't dropping any backward compatibility stuff in 4.6.17:18
seb128bryceh, hi there17:32
seb128bryceh, http://www2.bryceharrington.org:8080/X/PkgList/versions_current.html17:32
seb128do you have an updated version of that?17:32
Sarvattseb128: http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/versions-current.html17:35
brycehyeah sorry, I need to get rid of that old link17:35
brycehSarvatt, sorry I've not yet fixed up that graph...  totally forgot, been mesmerized by launchpad->bugzilla work17:36
Sarvattbryceh: no worries at all man! it's not important or anything17:37
ScottKSarvatt: Would you please have a look at http://blog.martin-graesslin.com/blog/2010/07/blacklisting-drivers-for-some-kwin-effects/ and give me a hand figuring out how to describe i945gme to blacklist the blur effect?17:48
bjsniderSarvatt, will there be nouveau gallium3d in maverick?17:59
SarvattScottK: can you blacklist wildcards? :) I bet he doesn't want that17:59
Sarvattbjsnider: it is already, libgl1-mesa-dri-experimental17:59
ScottKSarvatt: No idea.  I'd like to at least get mini 10v blacklisted properly.18:00
Sarvattugh, really stinks that its so strict, you can break it just using driconf that way :(18:02
SarvattScottK: you get it from the OpenGL renderer: line of the glxinfo output18:03
Sarvatti dont have 7.8.2 installed at the moment to give you an exact one18:05
ScottKOf course I don't either ....18:05
* ScottK will revert first.18:05
Sarvattoh there's a comment in the blog - grep KWin::CompositingPrefs::detectDriverAndVersion ~/.xsession-errors18:06
Sarvattthe GL renderer and GL version strings18:06
Sarvattsudo ppa-purge -p mesa sarvatt will do it18:07
Sarvattdont have to reboot to get the info18:07
ScottKOK.  Back in a few.  Now distracted by another task.18:10
apparleare video memory and gart size or different?18:10
SarvattIntel=Mesa DRI Intel(R) 945GME GEM 20100328 2010Q1:-:1.4 Mesa 7.8.218:10
SarvattIntel=Mesa DRI Intel(R) 945GME GEM 20100328 2010Q1:-:1.4 Mesa 7.8.218:10
apparlehow to check what is my current video memory size (on board GPU)?18:11
SarvattScottK: this is absolutely frigging ridiculous but here you go - http://sarvatt.com/downloads/kdeblacklist.txt18:55
Sarvattthats *just* intel and *just* mesa 7.8.218:55
ScottKSarvatt: Thanks.18:55
SarvattGM45 is a weird one and affected by locale..18:56
SarvattIntel=Mesa DRI Mobile Intel® GM45 Express Chipset GEM 20100328 2010Q1 x86/MMX/SSE2:-:2.1 Mesa 7.8.2 is what it should look like18:56
Sarvattplus you have to duplicate every renderer string for every arch18:56
Sarvattsince it doesnt show x86/MMX/SSE2 on x6418:56
SarvattI dont think it'd be wrong at all to just disable it globally and let people enable it themselves if they want it even if upstream doesn't want that, just my opinion though18:58
ScottKI was about to ask about that.18:58
Sarvattthat way is so fragile, i can get 3 different opengl versions reported on 945GME by changing driconf values19:01
=== yofel_ is now known as yofel
ScottKNext time I see him online, I'll ask him about it.19:05
ScottKSarvatt: What's the correct ppa-purge incantation for your mesa ppa?19:51
* ScottK has never used it before19:51
Sarvattsudo ppa-purge -p mesa sarvatt19:51
Sarvattor sudo ppa-purge ppa:sarvatt/mesa19:52
Sarvatttormod added the ppa: handling, I forget its there19:52
SarvattRAOF: I really am drawing blanks here about this 101_copy-fb.patch. What do you think about just disabling it in the interim until we can get it fixed up? ScottK has confirmed it's screwing up server regeneration on other chipsets as well as it is now. (bug #628077)20:02
ubot4Launchpad bug 628077 in xserver-xorg-video-intel (Ubuntu) "[i865] Crash on logout with KDM (affects: 1) (heat: 8)" [High,Confirmed] https://launchpad.net/bugs/62807720:02
ScottKSarvatt: I asked mgraesslin to join us to discuss the blacklist.20:04
ScottKHello mgraesslin.20:05
ScottKSarvatt is the one that proposed that blacklist based on our testing and your blog post.20:05
ScottKSarvatt: mgraesslin says he doesnt think it needs to be so extensive.20:05
SarvattHeyo! I'm really not the right person to discuss it with, the people in#dri-devel would be much more knowledgeable about it :)20:05
mgraesslinyeah the blog post is unfortunately incomplete20:06
mgraessline.g. Intel=20100328 2010Q1:-:7.8.2 will work, too20:06
SarvattScottK: I just added every intel string from mesa to the list for future reference, wasn't suggesting using all of that20:06
ScottKSarvatt: OK.20:06
mgraesslinand there is only one line per driver - the different versions are comma separated20:06
mgraesslinnow that I have such a list I can prepare an inclusion upstream20:07
ScottKSarvatt: I'm stuck needing to produce a patch and not knowing enough.  Upstreams sort it out eventually doesn't work on the release timeline.20:07
* Sarvatt nods20:07
ScottKWhich is why I invited mgraesslin here so you two can tell me what I need to get done.20:08
mgraesslinbtw: there are Intel drivers which work, so blacklisting just all, is wrong as well as it gives no possibility to the user to disable it20:08
Sarvattsomeone would need to go through all the KDE bugs and find out what's broken and pick and choose from there, but there's only 3 or 4 generations out of all of those so if someone is broken on one it's safe to assume the others of that generation are broken too20:09
ScottKmgraesslin: Part of the problem I have is that plasma-netbook makes large assumptions that compositing will be available, so if it's not, the user experience is really unfortunate.  So I need to be rather conservative in where the more aggressive options are enabled.20:10
Sarvattaka if 945GME is broken like ScottK says it is all of the opengl 1.4 ones should need blacklisting20:10
Sarvattwell maybe not the 8xx series ones but those are broken in everything else anyway :)20:10
mgraesslinopengl 1.4 does not need blacklisting as the effects require GLSL - that is 2.020:10
mgraesslinScottK: at least in 4.5.0 we had a problem that kwin's selfcheck failed on intel hardware20:11
mgraesslinit might be resolved in 4.5.1 but I am not sure20:11
ScottKOK.  I just updated my netbook to 4.5.1.  I'll check it.20:11
mgraesslinso you might want to disable kwin's functionality checks by default20:11
ScottKWe'll ship with 4.5.1 +patches this cycle so maybe it's OK.20:12
mgraesslinproblem is, that I have access to one Intel based device and there all issues are not reproducable20:13
mgraesslinselfcheck works, kwin does not freeze on settings change and blur is fast20:14
ScottKMy results seem to be inconsistent.20:19
ScottKWhat does the device you have access to have?20:20
ScottKmgraesslin: ^^20:20
mgraesslinerm no idea to be honest20:21
bjsniderSarvatt, any ideas on this: http://pastebin.ca/193199422:17
Sarvatthe booted an old kernel22:18
bjsniderno, he proved that's not so22:18
Sarvattoh 256.53? he hasn't rebooted since updating then22:19
bjsnideri think this may be a flea power issue, where it's just stuck in memory22:19
bjsniderhe did reboot22:19
Sarvattdon't know what to tell ya, 256.53 isn't installed for the kernel he's on obviously22:19
Sarvattdid he update to 2.6.35-20 in the same update?22:20
bjsniderno, -1922:20
Sarvattwhat's his dkms status say?22:21
bjsniderit works now after another reboot22:23
bjsniderso it was a module staying in the ram even through a reboot or two22:23
Sarvatt - Next week create a 7.9 release branch.22:35
achiangdoes anyone know what happened to xserver-xorg-input-keyboard / kbd in lucid? did the package just go away?22:55
jcristaulooks that way.22:57
achiangwhat happened to the code it used to contain? :)22:58
achiangperhaps now in xserver-xorg-input-evdev?22:58
jcristauthe code is still in xf86-input-kbd, it's just not useful on linux because evdev replaces it22:58
achiangah, ok, thanks22:59
vishhow do i identify the chipset of an intel card?23:03
jcristaulspci -s 0:2.023:03
vishso from http://launchpadlibrarian.net/54896374/Lspci.txt , it would be 945GME  ?23:05
kklimondahow does 10.04 cope with computers with 2 graphic cards?23:06
vishyup, [i945gme] seems it , found another bug about AAO with same title.. 23:09
Sarvattthats the same machine i've used primarily for 2 years now :)23:14
vishSarvatt: oh! the one i pasted above?23:15
Sarvattvish: do you have one? the bios is extremely hackable to enable stuff like ahci, nx, more backlight levels, etc23:15
vishhmm, havent hacked around the bios yet..23:16
Sarvattit could be a different one, mine's an old AOA15023:16
vishSarvatt: thats the one you've got unity running?23:16
Sarvatti don't use that but it does work with CLUTTER_VBLANK=none23:17
vishah , but unity works normally, only crashes X at times ;) 23:17
vishBug 62981423:17
ubot4Launchpad bug 629814 in xserver-xorg-video-intel (Ubuntu) "[i945gme] Moving pointer over Unity's launcher crashes X and causes Unity to reload (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/62981423:17
* vish tries with vblank..23:18
Sarvattvish: different problem23:18
vishk.. :)23:19
Sarvattvish: try this for me? https://launchpad.net/~sarvatt/+archive/sarvatt-graphics23:19
vishSarvatt: for the intel  AAO , or   ATI ? 23:20
Sarvattit's just xserver-xorg-video-intel in there23:20
vishsure.. 23:20
vishyeah , just now saw the link! :D23:20
Sarvatti think i'm going to hit the liquor store if that works. that patch makes me want some booze.23:26
Sarvattwell, it's the backtrace in your gdmlog2 that I'm thinking it'll fix, I didn't read the description :D23:30
Sarvattdid you log out when those server crashes happened?23:31
vishonly once, since my network manager crashed..23:31
Sarvattis the xorglogold from a shutdown?23:32
vishhmm , might be.. i'm running unity from persistant usb stick on that one..23:32
vishoh, ho , somethign is eating my / !  running out of space on my laptop! , so if i crash out. :/23:33
Sarvattvish: how many backlight levels do you have?23:35
Sarvatton the AOA15023:36
Sarvattif its not 9 check this out - http://macles.blogspot.com/2009/03/brightness-table.html23:36
Sarvatt(ignore the comments cus I fixed that in udev a long time ago)23:37
vishjust a sec.. my backup , created its own folder in /media and started filling up my / :(23:37
SarvattI get an extra hour battery life with that new bios, there are 9 cell batteries you can pick up on ebay that last about 11 hours too :)23:38
Sarvattfor $30 or so23:38
vishwow! 11hrs of battery life! :)23:41
vishhmm , looks like i have 9 steps :s23:42
Sarvattah, not surprised, only the early AOA150's had the problem that made them not allow the lower levels23:42
vishhmm , well , the ppa works.. but doesnt solve the bug i mentioned above :)23:44
Sarvattthose things are about 10-11 hours, they make 12 cells too23:44
Sarvattyeah, sorry about that, your logs exposed another bug that you probably dont notice cus it happens when you reboot :)23:44
vishnp.. :)23:45
Sarvattgrep -r FreeClientResources /var/log/Xorg.* shouldn't return anything new anymore with that though 23:46
Sarvattare you running a unity session or just running unity?23:46
vishunity regular! :D23:47
Sarvattfrom what you said in the bug though X isn't crashing just unity?23:47
Sarvattthose X crashes are another bug?23:48
vishyeah , i dont get logged out of the session.. but only Unity is reloaded.. so might be two happening at the same time?23:48
Sarvattyeah you'd know it if those X crashes in your log were related to unity reloading, the whole session would go down23:49
vishgrep -r FreeClientResources /var/log/Xorg.*  gives an output only in the 0.log.old..23:49
Sarvattvish: next reboot it shouldn't be in .old either23:49
Sarvattany chance you could confirm that so I can chalk it up as another bug caused by 101_copy-fb.patch in xserver-xorg-video-intel? :)23:50
vishyup , rebooting it :)23:51
vishSarvatt: poof! gone :) , nil output for $ grep -r FreeClientResources /var/log/Xorg.* 23:54
Sarvattthanks vish23:54
Sarvattyours is identical to ScottK's then, ugh23:54
Sarvattpretty safe to say all intel bugs on maverick with this backtrace are the same23:55
Sarvatt0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e83bb]23:55
Sarvatt1: /usr/bin/X (0x8048000+0x5da8d) [0x80a5a8d]23:55
Sarvatt2: (vdso) (__kernel_rt_sigreturn+0x0) [0xa9640c]23:55
Sarvatt3: /usr/bin/X (FreeClientResources+0xed) [0x808f04d]23:55
Sarvatt4: /usr/bin/X (FreeAllResources+0x60) [0x808f120]23:55
Sarvatt5: /usr/bin/X (0x8048000+0x1a5e6) [0x80625e6]23:55
Sarvatt6: /lib/libc.so.6 (__libc_start_main+0xe7) [0x2a5ce7]23:55
Sarvatt7: /usr/bin/X (0x8048000+0x1a191) [0x8062191]23:55
SarvattSegmentation fault at address 0x423:55
SarvattI really think it would be a good idea to disable 101_copy-fb.patch until it can get worked out23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!