Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51602 - kdm crashes and kills XFree when "end session only" selected
Summary: kdm crashes and kills XFree when "end session only" selected
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-20 17:23 UTC by Jerry Kiely
Modified: 2004-06-08 08:28 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry Kiely 2004-05-20 17:23:13 UTC
When ending a KDE session, instead of returning to a kdm login / welcome screen, you end up at a terminal login (where you were at bootup before kdm started). trying to restart kdm by entering "/etc/init.d/xdm start" tells you it (kdm) is still running.



Reproducible: Always
Steps to Reproduce:
1.Log in to KDE as user / root
2.Logout choosing "end session only"
3.

Actual Results:  
kdm / X crashes back to terminal login

Expected Results:  
You should have been brought back to a kdm login screen.

Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.10
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium4 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium4 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://212.219.247.17/sites/www.ibiblio.org/gentoo/
http://212.219.247.19/sites/www.ibiblio.org/gentoo/
http://212.219.247.20/sites/www.ibiblio.org/gentoo/
http://212.219.247.16/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib acpi alsa apm arts avi berkdb crypt cups dvd encode esd foomaticdb
gdbm gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad
maildir mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png
python qt quicktime readline sdl slang spell ssl svga tcltk tcpd truetype
wxwindows x86 xml xml2 xmms xv zlib"
Comment 1 Jerry Kiely 2004-05-20 17:52:20 UTC
I should have said, this only became a problem since emerging kde 3.2.2 a few days ago.

J.K.
Comment 2 Jerry Kiely 2004-05-24 13:22:35 UTC
In fact, after reverting to 3.2.1, I am still experiencing the same problem.

May downgrade to 3.2.0 to chech it out.

J.K.
Comment 3 Caleb Tennis (RETIRED) gentoo-dev 2004-05-27 16:02:31 UTC
did you check your kdmrc file to make sure something didnt' change?
Comment 4 Jerry Kiely 2004-05-27 17:11:01 UTC
One of the many things I did was comparing the contents of the kdmrc generated by the kde control center with the one generated by 'genkdmconf --no-old'. No significant difference.

I compared '/etc/X11/xdm/Xservers' with '/usr/kde/3.2/share/config/kdm/Xservers'. I replaced;

:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp :0 vt7

with

:0 local /usr/X11R6/bin/X

and it seems to be working ok. But I'd like to more fully understand the syntax and meaning of the contents of the kdm Xsessions file, but cannot find relevant documentation. Any help here would be appreciated.

Nothing of note in the ~/.xsession-errrors file, but some interesting entries in the /var/log/messages file;

May 28 00:21:56 pantagruel kde(pam_unix)[6764]: session closed for user jkiely
May 28 00:21:56 pantagruel kdm[6595]: X server for display :0 terminated unexpectedly
May 28 00:21:56 pantagruel [6764]: pam_setcred(DELETE_CRED) for jkiely failed: System error

...

May 28 00:29:49 pantagruel kdm[6595]: X server for display :0 terminated unexpectedly
May 28 00:29:49 pantagruel kdm[6595]: Unable to fire up local display :0; disabling.

...


May 21 21:01:02 pantagruel kde(pam_unix)[21848]: session closed for user root
May 21 21:01:02 pantagruel kdm: :0[21986]: IO Error in XOpenDisplay
May 21 21:01:02 pantagruel kdm[6476]: Display :0 cannot be opened
May 21 21:01:02 pantagruel kdm[6476]: Unable to fire up local display :0; disabling.

Hope this helps.

J.K.
Comment 5 Jerry Kiely 2004-05-27 17:32:12 UTC
I forgot to mention that the following was what I found in the file  '/usr/kde/3.2/share/config/kdm/Xservers';

:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7

so I changed it to;

:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp :0 vt7

and it seemed to work much better. I wonder if the missing :0 is important. Although it performs better with the added :0, the xdm version still performs much better.

KDM seems quite buggy to me on this laptop, but is rock solid on the 2 other boxes I have gentoo installed on. 

Plus, I'm not 100% sure of the relevance of all of the 'messages' I included in the previous post. I think the last one (for user 'root') is probably the most relevant of the three. It was the one most frequently seen after the problem.

I'd love to get this most annoying of issues sorted out before I do a complete reinstall. I don't want to have to do it again, but I'm just so frustrated by this issue.

Thanks in advance,

J.K.
Comment 6 Jerry Kiely 2004-06-03 11:45:20 UTC
So I disabled synaptics in xorg.conf and the problem is gone! So if I don't want X to die at logout I cannot use synaptics any longer.

J.K.
Comment 7 Jerry Kiely 2004-06-08 08:28:26 UTC
After some more fiddling, it does appear that the Synaptics driver is causing X to segfault (signal 11) on logout. I'm going to do some more investigation when I get home from work tonight. It may simply be an issue of a mis-configured xorg.conf.

I'm closing this bug as INVALID as it's not kdm related after all.

Sorry for the trouble,

J.K.