According to Josselin Mouette <[EMAIL PROTECTED]>: > Le lundi 04 septembre 2006 à 12:12 +0300, Heikki Kantola a écrit : > > Package: gnome-session > > Version: 2.14.3-1 > > Severity: important > > > > There is something weird happening when I attempt to start GNOME with > > my session settings (included below), namely the startup begins > > normally and then kaboom the session ends prematurely and I am > > returned to the login manager (or shell where startx was invoked). > > My prime suspect for this behaviour is the fact that I am using > > two display setup without Xinerama and therefor there has to be two > > instances of my favourite window manager FVWM (currently from Debian > > package fvwm-gnome 2.5.17-1) and given that there has already been > > reports on that gnome-session fails to launch multiple instances of > > xterm, my problems may be related to that. I've tried with another > > user account, where the window manager is sawfish and there seems to > > be no problem. Also on a laptop I manage to run the very same GNOME > > and FVWM versions fine, but there I have just one screen, so the > > problem most likely has something to do with my desktop dualhead X > > configuration. > > It looks like "just another libxklavier crash"... > > Question 1: after that happens, is there a trace of a crash > in /var/log/Xorg.0.log.old ?
I checked and yes, there is a trace of crash. Relevant parts of that log seem to be: SetKbdSettings - type: -1 rate: 30 delay: 500 snumlk: 0 *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x89) [0x80b67d9] 1: [0xffffe420] 2: /usr/lib/xorg/modules/libfb.so(fbCompositeCopyAreammx+0x60) [0xa77d1560] 3: /usr/lib/xorg/modules/libfb.so(fbComposite+0x527) [0xa77c2087] 4: /usr/lib/xorg/modules/libxaa.so(XAAComposite+0x1ee) [0xa777b41e] 5: /usr/bin/X11/X [0x81503e6] 6: /usr/bin/X11/X(CompositePicture+0xeb) [0x813e08b] 7: /usr/bin/X11/X [0x8144280] 8: /usr/bin/X11/X [0x8141115] 9: /usr/bin/X11/X(Dispatch+0x19b) [0x8086b3b] 10: /usr/bin/X11/X(main+0x48e) [0x806e5de] 11: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xa7cffea8] 12: /usr/bin/X11/X(FontFileCompleteXLFD+0xad) [0x806d911] Fatal server error: Caught signal 11. Server aborting > Question 2: what if you run: > gconftool-2 -- recursive-unset > /desktop/gnome/peripherals/keyboard/bell_custom_file Did so, quit the on-going session and logged in again and the session startup still fails the same way as earlier. :( -- Heikki "Hezu" Kantola, <[EMAIL PROTECTED]> Lähettämällä mainoksia tai muuta asiatonta sähköpostia yllä olevaan osoitteeseen sitoudut maksamaan oikolukupalvelusta EUR100 alkavalta tunnilta.