FS#18598 - [xorg-server] 1.7.5.901-1 (fluxbox issues)
Attached to Project:
Arch Linux
Opened by harryNID (harryNID) - Sunday, 07 March 2010, 21:07 GMT
Last edited by Paul Mattal (paul) - Monday, 15 March 2010, 03:13 GMT
Opened by harryNID (harryNID) - Sunday, 07 March 2010, 21:07 GMT
Last edited by Paul Mattal (paul) - Monday, 15 March 2010, 03:13 GMT
|
Details
Description:
New version of Xorg-Server causes Fluxbox (and apparently pekwm) to lock-up hard. More about this issue can be read here: http://bbs.archlinux.org/viewtopic.php?id=92679 Additional info: * package version(s) xorg-server 1.7.5.901-1 fluxbox-git 20100307-1 fluxbox 1.1.1-1 pekwm 0.1.11-2 (unconfirmed) No apparent events are logged. Steps to reproduce: Login press any button. All graphical elements lock up immediately. CTRL+ALT+F1 works to escape to a terminal. Since the new version re-enabled --enable-record I tried recompiling disabling that option. No change! |
This task depends upon
Closed by Paul Mattal (paul)
Monday, 15 March 2010, 03:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed upstream in 1.7.5.902-2. If you still have trouble with this bug first time launching X after rebooting, try a full-power-plug reboot before reopening this bug!
Monday, 15 March 2010, 03:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed upstream in 1.7.5.902-2. If you still have trouble with this bug first time launching X after rebooting, try a full-power-plug reboot before reopening this bug!
http://cgit.freedesktop.org/xorg/xserver/patch/?id=351d11fd466fae731df860a6ff4cf50ad565f43f
http://bugs.freedesktop.org/show_bug.cgi?id=25400
I don't know about this, maybe is a bug in fluxbox, or maybe something is wrong with this change. Open a ticket in http://bugs.freedesktop.org
Searching in ML, some time ago a guy reported the issue:
xorg-devel@lists.x.org/msg05737.html"> http://www.mail-archive.com/xorg-devel@lists.x.org/msg05737.html
BUT: It appears I still get this bad behavior the very first time I launch X after rebooting each time, even with 1.7.5.901-2.
Can anyone else confirm this behavior, or is it just me?
It would appear something had been set in an odd default state in the hardware. I now work correctly on first boot.
I hate hardware bugs, but probably not as much as Jan, so I'll just close this bug now. I think it really is dead.