You are not logged in.
Since the last Xorg-Server update my fluxbox sessions sometimes just crash for no trackable reason. Already on 3 computer I found that problem.
Another issue is hat since some time fluxbox freezes when used via FreeNX remote access. Fluxbox takes 100% cpu in that case and terminating the NX session won't help. The process must be finished with -sigkill signal.
Last edited by jcci (2009-08-18 10:29:59)
Offline
can you look at the tty where you launched the session and see if errors are printed there? also look through x error files and see if there is something there.
as a last resort, you could downgrade your xorg-server package.
Desktop/Laptop - DWM :: VM - screen
Registered Linux User Number 483137 :: Victory! :: GitHub
Offline
This could match. It is from errors.log
gdm-binary[2283]: pam_unix(gdm:auth): conversation failed
agetty[2334]: tty2: read: Inappropriate ioctl for device
In the Xorg logs I couldn't find anything suspicous.
But I can tell that it is not just about Fluxbox. First the X restart happened on 2 Fluxbox computer, but then also it happened on one Gnome session. The video cards are mixed. 2 use Nvidia, another has a VIA chipset using the Openchrome driver.
Maybe related: The crashes are triggered by a key. In most cases it was ENTER. But this effect is not so easy reproducable.
Last edited by jcci (2009-08-14 10:47:12)
Offline
Hello jcci!
Try to downgrade it, can it work so without random failure ? Isn't there anything in xorglog/syslog ?
Offline
Actually I'm just testing the upgrading a today new versions of GDM and Xorg arrived.
Since I do have 3 computer with the same problem it should be not so hard to tell whether or not the issue got fixed.
Anyway thanks and greetings to Budapest - it is said to be a beautiful place!
Offline
This issue seems to be fine since Xorg-Server 1.6.3-3 upgrade.
Thanks!
Offline