[RS482] x server crash

[Charles Dumont]

Hello, using Jaunty

I don't know precisely what paquage is in fault, but I figure it comes from compiz-fusion. often when I use the plug-ins "sélecteur en anneau" or "sélecteur en cascade", the x server just crashes and I go back to the gdm.

I use the free x.org driver for my ATI XPress 200M. this pug-ins worked very well under Intrepid with the proprietary driver (it worked no at all with the free one)

[Philip Muškovac (yofel)]

Thank you for taking your time to report this bug and help make ubuntu better. Can you please attach your Xorg.0.log from /var/log/ after the crash occurs and also your dmesg output (type 'dmesg > ~/Desktop/dmesg.log' in a terminal and attach the dmesg.log file form your Desktop), Thanks.

[Martin Olsson (mnemo)]

Hi Charles, if you have access to two computers can you please install ssh on the machine affected by the bug. Then, whenever the bug happens again you immediately login (without touched in the box with the crashed xorg) using ssh and run this command:
apport-collect 360417

This will give us detailed information about your hardware and software and it might also give us information about the crash (the xorg.log you provided before unfortunately did not have any specific crash information in it).

[Charles Dumont (unomadh)]

i have no access to two machines just now but i will do it soon

i just wanted to add a precision before: there seems to be a crash, i had seen that just using this plugins, when X is very sought. for example, if i hold <super><tab> pushed, or if i use the first plugin i spoke about then the second just after, very quickly.

I hope you'll understand in the way i don't speak english very well :D...
I'll try the ssh as soon...

[Charles Dumont (unomadh)]

I tried the ssh manipulation

the commandline apport-collect 360417 does not work, its execution seems to "freeze" (not the terminal).
can I try to get Xorg.0.log from /var/log/ and the dmesg sort manually from ssh ?

[Bryce Harrington (bryce)]

Are you able to reproduce this issue on the Jaunty release? If so, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

[Charles Dumont (unomadh)]

sorry, I had some problems with my internet connexion then I couldn't answer...
yes, this issue is still in the release. more, I installed the jaunty release on a friend's laptop, with the same graphic card than me, an XPress 200M: he has exactly the same problems. this tends to prove it comes from the driver I think...

I'll do the backtrace getting manipulation as soon as I can with the ssh

[Joshua Morris (joshua-a-morris)]

Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: xserver-xorg-video-ati 1:6.12.1-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Bryce Harrington (bryce)]

We still need a backtrace for this issue

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new version of the -ati driver is now available in Karmic.

This is a significant update to -ati which brings in kernel mode-setting
(currently disabled) and scores of fixes for DRI2, EXA, etc.

I've posted the new version of this driver to the following PPA,
would you mind testing it and seeing if it resolves the bug you
reported?

  https://edge.launchpad.net/~bryceharrington/+archive/ppa/+sourcepub/709908/+listing-archive-extra

If you're not running this release of Ubuntu, you can try booting the Karmic
LiveCD and loading the PPA onto it, and then log out/in to restart X.
ISOs are available at http://cdimages.ubuntu.com/releases/

After testing Karmic, report back here whether it's still an issue or not,
and if it is please post a fresh Xorg.0.log and 'dmesg' output.

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug xorg'.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.