angelic venus
January 17th, 2007, 03:50 PM
Hello,
I have a peculiar problem with Edgy AMD64. After 10 minutes or so of usage, programs stop loading complaining that there is no X display, after loading perfectly for a while.
Then, on log-out (actually I have been restarting the X server as the logout/power off panel no longer loads), the default gnome login screen shows (not the ubuntu one) and I cannot start a new session till I reboot (when it happens again)
I don't really know what is being effected, the X server? Gnome? It is essentially Gnome that ceases to function, X keeps going.
This is a fresh copy of Edgy AMD64, running on an AMD Sempron 3000+, Asus K8U-X motherboard and GeForce FX550 graphics board.
edit I forgot to mention, I cannot actually get back into Gnome once the destruction occurs leaving me in the strange generic login screen, it comes back with an error saying that the last Gnome session was destroyed in less than 10 seconds and that an error report has been dumped to ~/.xsession-error [see pastebin: http://pastebin.com/861509 (the first 5 lines of which seem most pertinent to my problem)]
Any ideas?
Adam.
I have a peculiar problem with Edgy AMD64. After 10 minutes or so of usage, programs stop loading complaining that there is no X display, after loading perfectly for a while.
Then, on log-out (actually I have been restarting the X server as the logout/power off panel no longer loads), the default gnome login screen shows (not the ubuntu one) and I cannot start a new session till I reboot (when it happens again)
I don't really know what is being effected, the X server? Gnome? It is essentially Gnome that ceases to function, X keeps going.
This is a fresh copy of Edgy AMD64, running on an AMD Sempron 3000+, Asus K8U-X motherboard and GeForce FX550 graphics board.
edit I forgot to mention, I cannot actually get back into Gnome once the destruction occurs leaving me in the strange generic login screen, it comes back with an error saying that the last Gnome session was destroyed in less than 10 seconds and that an error report has been dumped to ~/.xsession-error [see pastebin: http://pastebin.com/861509 (the first 5 lines of which seem most pertinent to my problem)]
Any ideas?
Adam.