FS#13560 - Certain actions in GTK2 apps crash X when started in a certain way

Attached to Project: Arch Linux
Opened by quantax (quantax) - Thursday, 26 February 2009, 16:27 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 31 May 2009, 14:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I usually like to start X form the console in the background an then logout. I do it like this:
- Using zsh's builtins: startx &!; exit
- Or using another shell and detach [1]: detach startx; exit

Then the following actions will crash the whole X server:
- Save and overwrite an already existing file with Firefox
- Execute "Verify versions and deprecations" in Glade's preference dialog
- Authenticate a buddy in Pidgin with the OTR plugin

The following workaround makes the programs behave normal:
- In zsh: startx &! 2> /dev/null; exit
- With detach: detach startx 2> /dev/null; exit

I have no idea what's going on. Maybe that's just a stupid way to start X. Since serveral applications are affected this could also be a GTK2 bug.

Some package versions:
detach 0.2.0-1
firefox 3.0.6-1
glade 3.5.4-1
gtk2 2.14.7-1
pidgin 2.5.4-1
pidgin-otr 3.2.0-1
zsh 4.3.9-1

[1] http://aur.archlinux.org/packages.php?ID=24245
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 31 May 2009, 14:08 GMT
Reason for closing:  Upstream
Additional comments about closing:  thanks for reporting the bug upstream
Comment by quantax (quantax) - Thursday, 26 February 2009, 16:50 GMT
I played around some more and it seems the Pidgin authentication no longer crashes X.
Futhermore I found out that another workaround is appending the "2> /dev/null" to my "exec xmonad" line in my ~/.xinitrc.
So it is probably an XMonad issue. So I'll post to their bugtracker.
Comment by Jan de Groot (JGC) - Thursday, 26 February 2009, 18:21 GMT
Is it X crashing itself, or is it just a normal shutdown because XMonad doesn't like to run anymore?
Comment by quantax (quantax) - Thursday, 26 February 2009, 18:55 GMT
You are right. It is XMonad crashing. The X server just shuts down nicely afterwards.
I filed a report upstream: http://code.google.com/p/xmonad/issues/detail?id=279

Loading...