Gnome 2.28 occasionally crashes back to gdm login screen!

eggplantbren · 2009-11-12 19:46:37

Glad it helped, o1911, but my problem reappeared today. *sigh*

eggplantbren · 2009-11-12 20:53:15

I now have a hypothesis that the problem reappeared since I locked the screen overnight. Once I have a single crash after unlocking the screen, everything is fine until I lock it again.

insanemal · 2009-11-13 09:25:06

eggplantbren: Have you checked for the errors I was talking about?
X spawing on TTY7 or the other errors in your logs?

Gather · 2009-11-13 11:25:40

@o1911 - form me it helped !

o1911 · 2009-11-14 22:15:41

Alas, it's still not working, and reverting back to manually starting gnome via startx means I'm again "not authorised" to mount stuff. However, just downloaded new gdm, see how this goes...

insanemal · 2009-11-16 11:31:01

o1911 wrote:

Alas, it's still not working, and reverting back to manually starting gnome via startx means I'm again "not authorised" to mount stuff. However, just downloaded new gdm, see how this goes...

Have you tried removing the TTY2 entry in your inittab?

Or

Using Run level 5 configured to auto spawn GDM ?

If you need to PM or email me.. feel free...

Last edited by insanemal (2009-11-16 11:32:11)

o1911 · 2009-11-17 01:29:55

I'm really restricted on time at the moment, last two university exams before the weeks end.... I'll play around with arch later.

uwinkelvos · 2009-11-18 20:50:12

I have been using gnome/gdm 2.28 for a while now (before it hit extra) and knew about this bug, but i did never affect me. Yesterday i unplugged my keyboard and plugged it in again, while logged in and: Instant crash to login window.
Today i tested this again: unplugged keyboard -> replugged keyboard -> nothing seems to happen -> start firefox -> HARD LOCKUP (reset is your friend...)
next Test: open firefox -> unplugged keyboard -> replugged keyboard -> instant crash to login window

this is some realy weired stuff!

Edward.H · 2009-11-20 03:27:08

I got same problem! new GDM is sucks

insanemal · 2009-11-20 13:29:38

Edward.H and uwinkelvos
All I can say is read the earlier parts of this thread.. and start testing..

The newest thing to try first is to make sure GDM is the LAST LAST!!! thing in your DAEMONS section in your rc.conf
After that.. try some of the other suggestions...
ALL OF THEM... not at once... dont just discount any of them.. for any reason other than having tested it.. AGAIN.

falconindy · 2009-11-20 20:04:31

I had no problems with GDM until I decided to pick up the recent update in the Extra repo. Today, I was trying to use GIMP and quite often, any operation involving the clipboard would crash me out to the login. Had to revert back to GDM 2.20 to get my work done.

DAEMONS=(syslog-ng hal network rpcbind nfs-common nfs-server @alsa @cups @samba @dnsmasq @crond @sshd @fam @mpd @postfix @gdm)

edit for more: I only run 2 tty's. GDM always respawns on the third.

Last edited by falconindy (2009-11-20 20:06:57)

eggplantbren · 2009-11-20 20:41:01

Still no luck for me on this issue. I've tried the various fixes suggested in this thread (except for rolling back gdm, I don't have the old package anyway)
And my gdm is always on tty7.
So now my morning routine is to unlock the screen, and run gv to crash, after which it doesn't happen until I lock the screen again.

jarav · 2009-11-21 20:32:03

after the gdm update the inittab method of starting gdm seems to work.

eggplantbren · 2009-11-23 21:02:48

The update to xorg-server 1.7.1.902-1 appears to have fixed this issue for me.

Pizon · 2009-11-27 17:23:42

I've recently encountered this same behavior but I was not able to resolve it through any of the suggestions posted previously. I found the following error in ~/.xession-errors that helped me determine the nature of the problem:

/home/gbur/.profile: line 1: set: multiline: invalid option name

The fix was to remove the following from ~/.profile:

set -o multiline

I had been tinkering with korn shell the day before and had created a .profile to hold a few customization. I'm curious as to why gdm would interpret this as a fatal error and drop back to the login window.

fabertawe · 2009-11-30 12:15:03

I'm having the same reset with the latest and previous versions of GDM and after having tried all the suggestions here. I have no testing repos activated.

eggplantbren wrote:

The update to xorg-server 1.7.1.902-1 appears to have fixed this issue for me.

Is the only way to get this via xorg-server-git on AUR?

My first post btw Hi to everyone, enjoying Arch

eggplantbren · 2009-11-30 21:48:23

fabertawe wrote:

eggplantbren wrote:
The update to xorg-server 1.7.1.902-1 appears to have fixed this issue for me.
Is the only way to get this via xorg-server-git on AUR?
My first post btw Hi to everyone, enjoying Arch

Hmm, no, it was just a regular update in extra. I see there's been another one yesterday as well, xorg-server 1.7.2-1. Still no crashes for me.

simon04 · 2009-11-30 22:52:38

## I experienced the same problem after the xorg-server update to 1.7.2. Running `mv .gconf* /tmp/` (i.e. temporary deleting the folders) helped.

## Thank you!

2009-12-01: GDM/Gnome crashed again today. So the mentioned solution didn't work after all. I downgraded to nautilus-2.28.1-2, xorg-server-1.7.1.902-1, gvfs-1.4.1-2.

Cheers

Last edited by simon04 (2009-12-01 15:22:35)

pal · 2009-12-01 04:42:34

I think I may be experiencing the same problem and I can reliably
reproduce it, like this: (1) reboot the machine (2) log in (3) type
the string "example(integr" (in urxvt, which is started from
.xsession). When I press the last character, "r", the ScrollLock
keyboard indicator is turned on. If I now press Enter, X11 crashes and
I'm back to the graphical login screen. It makes no difference if I
use backspace to erase some characters before pressing Enter. It makes
no difference if I type some other characters before I type the string
"example(integr". I don't know what modification of this string will
still produce the behavior, but I know that other strings of
characters of the same length do not activate the bug.

If instead of typing the string in urxvt immediately after logging in,
I open emacs first and type the string there, the bug is activated
in exactly the same manner.

If I log in for the second time after rebooting, the bug is not
activated (I have to reboot the system to reproduce it again).

I have the following setup:

Core2Duo, integrated Intel graphics (G45)
xf86-video-intel 2.9.1-1
xorg-server 1.7.1.902-1
xorg-xdm 1.1.8-1
xf86-input-evdev 2.3.1-1
xmonad 0.9-2

I don't have gnome installed.

If I use slim instead of xdm, the bug is not activated. However, if I
use wdm, it is. Yet, XDMCP does not seem to be relevant, since turning
it off in xdm (DisplayManager.requestPort: 0) does not help.

If I start X11 with startx, the bug is not activated.

After the crash, .xsession-errors contains the following:

urxvt: X connection to ':0.0' broken, unable to recover, exiting.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 286 requests (286 known processed) with 0 events remaining.
fetchmail: background fetchmail at 3627 killed.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 1372 requests (1371 known processed) with 0 events remaining.

The end of /var/log/xdm-errors.log
=======================

[config/dbus] couldn't register object path
Cannot open config file. Using builtin defaults
Dropping master
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 1849 requests (1849 known processed) with 0 events remaining.

/var/log/Xorg.0.log.old
=======================

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x45b808]
1: /usr/bin/Xorg (0x400000+0x62939) [0x462939]
2: /lib/libpthread.so.0 (0x7f02118f4000+0xee80) [0x7f0211902e80]
3: /lib/libc.so.6 (__select+0x13) [0x7f0210c4a133]
4: /usr/bin/Xorg (WaitForSomething+0x1ba) [0x45907a]
5: /usr/bin/Xorg (0x400000+0x463a2) [0x4463a2]
6: /usr/bin/Xorg (0x400000+0x2205c) [0x42205c]
7: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f0210ba0b6d]
8: /usr/bin/Xorg (0x400000+0x21c09) [0x421c09]

Fatal server error:
Caught signal 3 (Quit). Server aborting

Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Logitech Optical USB Mouse: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) AIGLX: Suspending AIGLX clients for VT switch

fabertawe · 2009-12-01 11:41:46

eggplantbren wrote:

fabertawe wrote:
eggplantbren wrote:
The update to xorg-server 1.7.1.902-1 appears to have fixed this issue for me.
Is the only way to get this via xorg-server-git on AUR?
Hmm, no, it was just a regular update in extra. I see there's been another one yesterday as well, xorg-server 1.7.2-1. Still no crashes for me.

Seems my mirrorlist needed changing... I had all the UK mirrors uncommented but had to comment out the first two to get refreshed?! Now on xorg-server 1.7.2-2, fingers crossed.

Update: One reset with the new xorg-server so far.

Last edited by fabertawe (2009-12-01 17:33:54)

uwinkelvos · 2009-12-08 01:14:00

xorg-server 1.7.3 is in testing and does solve my gdm crash problems. 1.7.2 did not!

graysky · 2009-12-08 01:21:04

uwinkelvos wrote:

xorg-server 1.7.3 is in testing and does solve my gdm crash problems. 1.7.2 did not!

Can anyone else confirm what uwinkelvos reported?

fabertawe · 2009-12-08 14:31:14

graysky wrote:

uwinkelvos wrote:
xorg-server 1.7.3 is in testing and does solve my gdm crash problems. 1.7.2 did not!
Can anyone else confirm what uwinkelvos reported?

I picked up 1.7.3-1 from extra today and it's fine so far.

graysky · 2010-01-10 21:58:08

Been a while and I'm using xorg-server 1.7.3.902 now so I upgraded to the current gdm (2.28.2) and will report back in the thread whether or not this problem is still present.

graysky · 2010-01-10 23:39:15

Wow, crashed in less than 2 h of use. Downgraded back to 2.20

Arch Linux

#126 2009-11-12 19:46:37

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#127 2009-11-12 20:53:15

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#128 2009-11-13 09:25:06

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#129 2009-11-13 11:25:40

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#130 2009-11-14 22:15:41

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#131 2009-11-16 11:31:01

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#132 2009-11-17 01:29:55

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#133 2009-11-18 20:50:12

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#134 2009-11-20 03:27:08

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#135 2009-11-20 13:29:38

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#136 2009-11-20 20:04:31

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#137 2009-11-20 20:41:01

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#138 2009-11-21 20:32:03

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#139 2009-11-23 21:02:48

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#140 2009-11-27 17:23:42

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#141 2009-11-30 12:15:03

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#142 2009-11-30 21:48:23

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#143 2009-11-30 22:52:38

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#144 2009-12-01 04:42:34

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#145 2009-12-01 11:41:46

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#146 2009-12-08 01:14:00

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#147 2009-12-08 01:21:04

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#148 2009-12-08 14:31:14

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#149 2010-01-10 21:58:08

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

#150 2010-01-10 23:39:15

Re: Gnome 2.28 occasionally crashes back to gdm login screen!

Board footer