Bug 49900 - X crashes (SEGFAULT) when a graphical application is started.
Summary: X crashes (SEGFAULT) when a graphical application is started.
Status: RESOLVED DUPLICATE of bug 49182
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-14 04:25 UTC by Alexander Brock
Modified: 2012-05-14 07:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
output of lspci -vv, output from gdb, xorg.conf (9.20 KB, application/octet-stream)
2012-05-14 04:25 UTC, Alexander Brock
no flags Details

Description Alexander Brock 2012-05-14 04:25:51 UTC
Created attachment 61604 [details]
output of lspci -vv, output from gdb, xorg.conf

Whenever I start a graphical application like iceweasel, icedove, gajim etc. X crashes. I use i3 as a window manager and dmenu to start programs. If I replace the radeon driver by the vesa driver X doesn't crash.

I use debian testing and installed the following packages:

xserver-xorg-video-radeon
xserver-xorg-video-radeon-dbg
xserver-xorg-core
xserver-xorg-core-dbg

but the output from gdb is full of "file xy not found" messages.
Comment 1 Michel Dänzer 2012-05-14 06:06:48 UTC
Already fixed in Git. BTW, you wouldn't have hit this bug with KMS, any particular reason why you've disabled that?

*** This bug has been marked as a duplicate of bug 49182 ***
Comment 2 Alexander Brock 2012-05-14 07:14:35 UTC
I didn't disable KMS on purpose, I just didn't enable it because I didn't know about it.

Now I enabled KMS by changing the first line in /etc/modprobe.d/radeon-kms.conf from "options radeon modeset=0" to "options radeon modeset=1", running "update-initramfs -k `uname -r` -u" and rebooting and now it works :-)

Thank you for your help.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.