Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17077 - [xorg] 7.5 always crashes with xfce 4.6.1 when software is started

Attached to Project: Arch Linux
Opened by Heiko Baums (cyberpatrol) - Monday, 09 November 2009, 15:55 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 30 September 2010, 16:36 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the last system update today which included some xorg related updates, it's impossible to start any software in xfce anymore. As soon as a program is started X either kills the session or crashes completely.

This happens with these versions:
mesa 7.6-2
libgl 7.6-2
ati-dri 7.6-2
xf86-video-ati 6.12.99.git20091014-1 (Btw., what the hell has an unstable git version lost in a stable repo (extra)?)
xf86-video-radeonhd 1.3.0-1
xf86-video-vesa 2.2.1-1
xf86-input-evdev 2.3.0-1
xorg-server 1.7.1.901-2

After downgrading to these versions it's working correctly again:
mesa 7.5.1-2
libgl 7.5.1-2
ati-dri 7.5.1-2
xf86-video-ati 6.12.4-1
xf86-video-radeonhd 1.2.5-1
xf86-video-vesa 2.2.0-1
xf86-input-evdev 2.2.5-1
xorg-server 1.6.3.901-1

It's not related to xf86-video-ati and xf86-video-radeonhd.

I've attached slim.log, which seems to contain the relevant logs after firefox was started. Such errors occur with every software.
   slim.log (13.6 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 30 September 2010, 16:36 GMT
Reason for closing:  Works for me
Additional comments about closing:  only one user seems affected. ask to reopen when you have news about it.
Comment by Andreas Radke (AndyRTR) - Monday, 09 November 2009, 18:19 GMT
the git version is in extra for good reasons. you don't tell us the driver you use or any helpful log from dmesg and Xorg. the slim log doesn't help much. looks like your xorg.conf is borked. you will get better support in our forums or irc channels. closing this. xfce works for me.
Comment by Heiko Baums (cyberpatrol) - Monday, 09 November 2009, 20:16 GMT
  • Field changed: Percent Complete (100% → 0%)
Are xf86-video-ati and xf86-video-radeonhd not drivers?

I don't think, that my xorg.conf is borked, because it worked perfectly with every previous xorg version. If you are missing log files you can just ask. Btw., slim.log is the only log file I found which contains error messages which are caused by this bug.

Just closing this bug as "Works for me" is not a solution. If something is working for you that doesn't mean, that it works for everyone else and that there is no bug. If it's not possible to start any programs and if xorg always crashes, then this is not a matter for the forums but a serious bug.
Comment by Andreas Radke (AndyRTR) - Monday, 09 November 2009, 20:17 GMT
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

your 2nd chance.
Comment by Heiko Baums (cyberpatrol) - Monday, 09 November 2009, 21:05 GMT
I know the guidelines. ;-)

Tell me, what exactly you need to know.
Here are my xorg.conf and Xorg.0.log.
Xorg's console output is in slim.log.
   xorg.conf (1.6 KiB)
   Xorg.0.log (48.2 KiB)
Comment by Heiko Baums (cyberpatrol) - Monday, 09 November 2009, 21:12 GMT
Still forgot dmesg.log.
   dmesg.log (32.5 KiB)
Comment by Andreas Radke (AndyRTR) - Monday, 09 November 2009, 21:29 GMT
there's nothing special in your logs. maybe a certain option in your xorg.conf breaks something. please use kms and try without any xorg.conf. check the Arch wiki page for radeon/ati setup.
Comment by Heiko Baums (cyberpatrol) - Monday, 09 November 2009, 21:31 GMT
KMS doesn't work yet with my graphics card (Radeon HD 3450). It's planned for kernel 2.6.32 as far as I know.
I already read the wiki page.
Comment by Andreas Radke (AndyRTR) - Tuesday, 10 November 2009, 07:17 GMT
Disable KMS and try without any xorg.conf. Then discribe when it crashes and send a log of the crash. I don't have any further report about unstable 2d desktops.
Comment by Heiko Baums (cyberpatrol) - Tuesday, 10 November 2009, 11:57 GMT
KMS was already disabled by the kernel parameter radeon.modeset=0. Even if dmesg said that this parameter is unknown it worked because the system didn't boot (I think it was a kernel panic) without this parameter. Now I tried the kernel parameter nomodeset and have the same issue.

I already tried all of the suggestions you made here and in your e-mails before reporting this bug except of removing xorg.conf. But removing xorg.conf now indeed seems to work but doesn't fix this bug. I told you more than once that this is not a configuration issue but a bug. This bug also occurs when starting X from console with startx. The console output with the relevant error messages (a lot of GTK errors) is still in slim.log. You really should have a look at this file.

Slim first writes some own logs in this file and then it adds the complete console output of xorg in it. If you would read this file you could probably see or at least guess where the bug is.
Comment by Andreas Radke (AndyRTR) - Tuesday, 10 November 2009, 13:33 GMT
http://bugs.archlinux.org/task/17081 looks similar.

please clear your pacman pkg cache, use a different mirror then reinstall new Xorg/gtk2 and try with a clean ld conf cache. Xorg at all isn't broken. Or it would fail for everybody. So I expect the issue in the way you are doing the update if non of your settings breaks it.
Comment by Heiko Baums (cyberpatrol) - Tuesday, 10 November 2009, 17:50 GMT
Now I know this is definitively a bug but indeed not an Arch Linux bug.

After creating a new user, removing ~/.config in my other user's home directory and putting back every directory and file one by one I found out that the crashes are caused by my Xfce theme "Elegant Brit".

After changing the line
<property name="theme" type="string" value="Elegant Brit"/>
to
<property name="theme" type="string" value="Default"/>
in the file ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml the bug is fixed.

I've posted a short comment for this theme:
http://www.xfce-look.org/content/show.php/Elegant+Brit?content=76017

So I think, this bug can this time be closed as "Upstream".
Comment by Heiko Baums (cyberpatrol) - Tuesday, 10 November 2009, 18:25 GMT
Also filed a bug report to Xfce upstream: http://bugzilla.xfce.org/show_bug.cgi?id=5966
Comment by Heiko Baums (cyberpatrol) - Tuesday, 10 November 2009, 18:57 GMT
At the end it turned out that this is indeed an xorg bug.
Here's the upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=24703
Comment by Jan de Groot (JGC) - Monday, 30 November 2009, 11:08 GMT
Is this still an issue with xorg-server 1.7.2-2?
Comment by Heiko Baums (cyberpatrol) - Monday, 30 November 2009, 15:19 GMT
Yes, it is.
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 28 February 2010, 00:06 GMT
status of this with latest xorg?
Comment by Heiko Baums (cyberpatrol) - Sunday, 28 February 2010, 01:02 GMT
The bug still exists.
Comment by Heiko Baums (cyberpatrol) - Tuesday, 08 June 2010, 10:47 GMT
I found out that this problem only occurs with the drivers xf86-video-ati (radeon) and xf86-video-radeonhd (radeonhd). With catalyst (fglrx) it's working fine.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 13 August 2010, 03:43 GMT
Lots of things are changed since this report. Is fixed now with latest kernel 2.6.35.1 and Xorg 1.8?
Comment by Heiko Baums (cyberpatrol) - Friday, 17 September 2010, 00:24 GMT
The bug is not yet fixed.
Comment by Andreas Radke (AndyRTR) - Friday, 17 September 2010, 15:03 GMT
You've been ask in the Xorg bug to provide a backtrace. We can't do this for you.
Comment by Heiko Baums (cyberpatrol) - Friday, 17 September 2010, 19:57 GMT
And I currently can't do it, too, like I've written in the Xorg bug, because I've got only one Computer. So I have to wait until I can lend a notebook from someone and until I have time to install Linux onto a USB stick and occupy myself with gdb. This can take a while.

Loading...