You are not logged in.
Just for the record. It's not GDM, GNOME issue. Why? Because, I get same thing with KDE 4.3.2 (clean install BTW). I just crashed in KDM, with no apparent reason. I was browsing on net, and voila, I got kicked to KDM.:mad:
Maybe its true what insanemal said. Maybe is nVIDIA, Intel fault or else...
Last edited by archiebald (2009-11-02 22:09:26)
Offline
For me too, a lot of X segfaults since today, when launching an application (rhythmbox, vlc...)
Slim + Gnome ; nvidia
Offline
For me too, a lot of X segfaults since today, when launching an application (rhythmbox, vlc...)
Slim + Gnome ; nvidia
I got ocasionaly segfaults with Dolphin, KDE 4.3.0 was rock solid compared to this minor KDE 4.3.2 update.
But to keep things straight, something went terribly wrong, when I got kicked to KDM or GDM for no apparent reason.
Last edited by archiebald (2009-11-02 21:35:25)
Offline
The KDE and slim crashes may be related to the xorg updates, there are plenty of threads about that one.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
loafer is right, there are new crashes which have nothing to do with the bug in this thread. I downgraded gdm and everything worked, but since the last update it does not anymore. Please look in the other threads for that new xorg bug.
- blog (about arch and other stuff): http://thoughtyblog.wordpress.com/
- x86_64 user
Offline
Hello, here's something that might help you....
1st. DON'T USE GDM!... Remove it from DAEMONS in your /etc/rc.conf
2nd. # echo "exec gnome-session" > ~/.xinitrc
3rd. Add startx to /etc/rc.local
4th. Reboot or just run startx (after reboot Xorg should start automaticaly)
ps: It's what I did... and worked for me!
Last edited by n0kS (2009-11-03 15:37:44)
Offline
After remming out this line in /etc/inittab :
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
I've had no crashes since then.
Last edited by vinoman2 (2009-11-03 15:38:55)
Offline
Before I was using the deamon method
(http://wiki.archlinux.org/index.php/Add … on_startup)
to load gdm. The result was that for the last 6 months I've had this bug appear twice after upgrades (each time giving me headache for more than a week). Several days ago I switched to the Inittab Method on the wiki (without commenting out the agetty line), and it works flawlessly: gdm starts at tty7, and is perfectly stable.
Hope this helps.
Offline
i have this bug on a dell studio 1555 which has the ati card
Offline
i have the same problem, but it is qutIM fault: every time i send message fast, gnome crashes and i again at gdm screen.
does anyone have the same problem?
Offline
I recently started having a problem like this; when I started either gv or gimp I was returned to the gdm screen. I have no idea why these two programs did this. Reinstalling with pacman -S gv gimp worked. I have an nvidia card and use the proprietary driver.
Offline
http://bugs.archlinux.org/task/17013?string=xorg-server
This patch fix Xorg crash for me
Offline
Hey all,
Yeah the KDM crash is unrelated to the GDM crash.
Please read the whole thread before asking questions or jumping to conclusions.
There are very specific signs that you have this GDM bug.
The one thing you will have without fail, is Xorg on a TTY that isn't 7
The other thing you HAVE to get is the error in your logs ... It's in one of my posts a few pages back..
n0kS...
That is one way.. but using GDM in your rc.local has fixed it for some people.
And its probably more secure.
gnumdk: Awesome.. thats a totaly unrelated issue
Offline
The one thing you will have without fail, is Xorg on a TTY that isn't 7
The other thing you HAVE to get is the error in your logs ... It's in one of my posts a few pages back..
Not true... before I downgraded back to the older gdm package, gdm v2.28 would crash like this: it was as if I did a ctrl+alt+backspace - everything in the session is closed instantly and I get presented with the gdm login screen still on TTY7.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
http://bugs.archlinux.org/task/17013?string=xorg-server
This patch fix Xorg crash for me
It fixes my crashes too, thx Jan.
Last edited by jesusjimenez (2009-11-05 22:23:34)
Offline
insanemal wrote:The one thing you will have without fail, is Xorg on a TTY that isn't 7
The other thing you HAVE to get is the error in your logs ... It's in one of my posts a few pages back..Not true... before I downgraded back to the older gdm package, gdm v2.28 would crash like this: it was as if I did a ctrl+alt+backspace - everything in the session is closed instantly and I get presented with the gdm login screen still on TTY7.
Umm.. was it originally on 7? or when it came back was it on 7.
Im talking it about starting on a TTY that isnt 7... when it restarts it will always come back on 7
Offline
Just to add my comments:
I had issues with my system after a recent upgrade. Many things were seg-faulting (including X and sudo/su, and lots of other apps), and I just decided to reinstall Arch. After doing so, the computer would boot normally and start GDM. After entering my credentials the first time, GDM restarted, but the second time it logged me in fine. I also had problems occasionally with unlocking the computer after the screensaver activated. I took the suggestions posted here by insanemal and the wiki and took GDM out of the daemons list and instead started it with rc.local. GDM still starts on TTY2 (for some unknown reason) but it finally got rid of the random crashes.
Offline
i've come across a work around although i don't know how much it will apply to others.
i've noticed that preceding a crash, the scroll-lock light comes on(without pressing the scroll-lock key). if i press enter(or ignore it) then it will crash. if i turn it off (by cycling one of the 'lock' keys, caps scroll or num). then everything is fine.
Offline
Im talking it about starting on a TTY that isnt 7... when it restarts it will always come back on 7
Mine starts on 7 and respawn on 7 after a crash. I understand what you're saying now... just curiously, why would you want it to intentionally start on a tty that isn't 7?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
If you dont use Text consoles.. why have it on 7?
its only on 7 because we have 6 TTY's running.
I use like 3-4 at most..
but some people and not to generalize, but average ubuntu users only use X... if they do use a console it's inside X.
And 1 TTY is fine for "emergency" fixing
So Why bother "wasting" all that extra cpu/ram having 6 consoles... (not that it really does but meh)
Offline
Okay, I previously thought I'd solved this, but no longer.
For me, I usually crash back to GDM when I run gv (although sometimes it doesn't crash, particularly recently after a crash). Sometimes it happens when I run evince or gimp on a postscript file.
When GDM returns it's on tty2. Not sure what it was on when I first start up the computer (I'm running some long-term jobs and don't want to kill them).
I've tried the fixes suggested in the first page of this thread (put gdm in rc.local, comment out a line of inittab) and they didn't work.
I'm using arch x86-64
Here's some package versions that may be relevant.
gdm 2.28.1-1
xorg-server 1.7.1.901-2
nvidia 190.42-1
gv 3.6.7-1
evince 2.28.1-1
ghostscript 8.70-2
Any new ideas?
Last edited by eggplantbren (2009-11-10 19:49:51)
Offline
@eggplantbren, Your problems are just as likely (if not more likely) to be caused by the newer versions of xorg and/or the nvidia drivers as discussed in a various other threads. There are threads with titles like "xorg random crashes" or with references to xorg and nvidia problems etc. I would advise you to take a look at those.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Thanks loafer.
I ran gv >& outfile
and managed to capture an error message that looks relevant.
XIO: fatal IO error 4 (Interrupted system call) on X server ":0.0"
after 1724 requests (1630 known processed) with 32 events remaining.
Also, everything works fine if I use icewm instead of gnome.
Last edited by eggplantbren (2009-11-10 22:32:37)
Offline
Okay, deleting my .gconf and .gconfd directories seems to have fixed the problem. Might be a good idea to do that between GNOME upgrades. Will let y'all know if it's a premature declaration of victory.
Offline
Okay, deleting my .gconf and .gconfd directories seems to have fixed the problem. Might be a good idea to do that between GNOME upgrades. Will let y'all know if it's a premature declaration of victory.
I deleted my .gconf and .gconfd and haven't noticed any problems so far... the automounting is working again too! Many thanks for this tip, hope this fixes everything. Makes a lot of sense to remove config files between releases.
Arch x86_64
Offline