LinuxQuestions.org - KDE logout issue

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - KDE logout issue (https://www.linuxquestions.org/questions/slackware-14/kde-logout-issue-211941/)

KDE logout issue

Whenever I logout from KDE, it leaves me with a blank screen and I'm forced to reboot. I'm using Slackware 10. Any solutions?

hi :) this is a very very common problem usually caused by a corruption/incorrect data in your /home/xx/.kde directory. this directory contains all your basic KDE settings, such as taskbar location, colour scheme and wallpaper, so be careful before erasing the whole thing. i would recommend renaming the .kde directory u hav to .kde.old or something, forcing kde to recreate it. you can then easily restore your old setup.

however, if all other user accounts have the same problem it might be something different.

Yeah, all my accounts act the same way when they log out and the renaming didn't work, any other ideas?

When you log-out, are you in the shell, or is the screen totally blank. Does the monitor respond that there isn't any signal?

In the file /etc/inittab, what default level are you using.

If you are using init level 5 as the default, which session manager are you using?

When I logout, the screen goes completely blank, or 'black' as it were. No indications, nothing, just blank(black). I think my default is level 3 but I wasn't sure so here's the file:

Code:

#

# inittab        This file describes how the INIT process should set up

#                the system in a certain run-level.

#

# Version:        @(#)inittab                2.04        17/05/93        MvS

#                                      2.10    02/10/95        PV

#                                      3.00    02/06/1999      PV

#                                      4.00    04/10/2002      PV

#

# Author:        Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>

# Modified by:        Patrick J. Volkerding, <volkerdi@slackware.com>

#



# These are the default runlevels in Slackware:

#  0 = halt

#  1 = single user mode

#  2 = unused (but configured the same as runlevel 3)

#  3 = multiuser mode (default Slackware runlevel)

#  4 = X11 with KDM/GDM/XDM (session managers)

#  5 = unused (but configured the same as runlevel 3)

#  6 = reboot



# Default runlevel. (Do not set to 0 or 6)

id:3:initdefault:



# System initialization (runs when system boots).

si:S:sysinit:/etc/rc.d/rc.S



# Script to run when going single user (runlevel 1).

su:1S:wait:/etc/rc.d/rc.K



# Script to run when going multi user.

rc:2345:wait:/etc/rc.d/rc.M



# What to do at the "Three Finger Salute".

ca::ctrlaltdel:/sbin/shutdown -t5 -r now



# Runlevel 0 halts the system.

l0:0:wait:/etc/rc.d/rc.0



# Runlevel 6 reboots the system.

l6:6:wait:/etc/rc.d/rc.6



# What to do when power fails.

pf::powerfail:/sbin/genpowerfail start



# If power is back, cancel the running shutdown.

pg::powerokwait:/sbin/genpowerfail stop



# These are the standard console login getties in multiuser mode:

c1:1235:respawn:/sbin/agetty 38400 tty1 linux

c2:1235:respawn:/sbin/agetty 38400 tty2 linux

c3:1235:respawn:/sbin/agetty 38400 tty3 linux

c4:1235:respawn:/sbin/agetty 38400 tty4 linux

c5:1235:respawn:/sbin/agetty 38400 tty5 linux

c6:12345:respawn:/sbin/agetty 38400 tty6 linux



# Local serial lines:

#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100

#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100



# Dialup lines:

#d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100

#d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100



# Runlevel 4 used to be for an X window only system, until we discovered

# that it throws init into a loop that keeps your load avg at least 1 all 

# the time. Thus, there is now one getty opened on tty6. Hopefully no one

# will notice. ;^)

# It might not be bad to have one text console anyway, in case something 

# happens to X.

x1:4:wait:/etc/rc.d/rc.4



# End of /etc/inittab

I'm using KDE and probably the default session manager. If there is a way I can check, if you could specifiy? Thanks.

That is level 3.

1. Did you always have this problem? Did it start after you (upgraded X\some libraries\enabled accelleration?)
2. After you log out of KDE and get to blank screen, what happens if you press:
a. CTRL+ALT+F1
b. CTRL+ALT+BackSpace
3. What command do you use to start windowing environment?
4. Give your system specs. (Vid card, Version of X, if you use special 3rd party drivers, kernel, if you enabled DRI, FB, if you use custom AGPGart module, etc.)

Please also try pressing CTRL-ALT-F2 while still running X, to see if you have a virtual terminal show up while running X. I am wondering if it is the 3-D graphics driver installation. I've had in the past the virtual terminals blank out on a 2nd monitor when starting X.

When you exit out of X, if you blindly type in 'startx' and return, does x-windows come back.

Alright here goes. I've never had this problem before, only on this installation. It started the first time I logged out of KDE. When I logout of KDE and press alt+F1 or alt+Backspace or alt+F2 or type in startx blindly, the screen flickers to a different shade of black and the returns to the normal shade of black. When I start slackware, I use startx to startup KDE. My video card is an Intel Extreme Graphics 845G chipset. Version of X is the version that comes with Slackware 10. I'm using the vmlinuz kernel, everything is default. (I didn't setup anything specifically) Hope this helps somewhat.

Quote:

Originally posted by a_priebe47
Alright here goes. I've never had this problem before, only on this installation. It started the first time I logged out of KDE. When I logout of KDE and press alt+F1 or alt+Backspace or alt+F2 or type in startx blindly, the screen flickers to a different shade of black and the returns to the normal shade of black. When I start slackware, I use startx to startup KDE. My video card is an Intel Extreme Graphics 845G chipset. Version of X is the version that comes with Slackware 10. I'm using the vmlinuz kernel, everything is default. (I didn't setup anything specifically) Hope this helps somewhat.

Thx for a complete reply.

1. "I've never had this problem before, only on this installation." means:
a. "I enstalled slack 10 on this same computer before and it was OK" or
b. "I enstalled other recent linux distros on this same computer before and it was OK"
c...
2. Please, post the following:
a. "Monitor section" of /etc/X11/xorg.conf file
b. "Graphics device section" of /etc/X11/xorg.conf file
c. results of "lsmod" command done in terminal window in X.

I am inclined to say it's an issue related to the way X uses the VidCard. I would suspect either an issue with fb (frame buffer interface) in the kernel, or a faulty DRI (Direct Rendering Interface)/Acceleration usage under X.

Next step I would do is upgrade to 2.6.x kernel. It is on CD2 of your Slackware 10 CD set.
2 new things come with it: alternative fb, and new AGPGart module. I would see if that makes a difference. Good luck.

Yeah, I just upgraded to 2.6.7 and it seemed to be working fine, I was able to login to KDE and then logout and appear back at the text terminal, except I can't start KDE back up after I've logged out of it. If I do startx, it just gives me the black screen again, except this time I can ctrl+alt+backspace to return to the text terminal. To answer your previous question, I had FreeBSD installed and KDE had no issues on it. I've never had Slackware before.

Monitor Section

Code:

# **********************************************************************

# Monitor section

# **********************************************************************



# Any number of monitor sections may be present



Section "Monitor"



    Identifier  "My Monitor"



# HorizSync is in kHz unless units are specified.

# HorizSync may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S

# USER MANUAL FOR THE CORRECT NUMBERS.



    HorizSync  31.5 - 50.0



#    HorizSync        30-64        # multisync

#    HorizSync        31.5, 35.2    # multiple fixed sync frequencies

#    HorizSync        15-25, 30-50  # multiple ranges of sync frequencies



# VertRefresh is in Hz unless units are specified.

# VertRefresh may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S

# USER MANUAL FOR THE CORRECT NUMBERS.



    VertRefresh 40-90



EndSection

Graphics Device Section

Code:

# **********************************************************************

# Graphics device section

# **********************************************************************



# Any number of graphics device sections may be present



Section "Device"

    Identifier  "VESA Framebuffer"

    Driver      "vesa"

    #VideoRam    4096

    # Insert Clocks lines here if appropriate

EndSection

Here are some of the error names it gave me when I ctrl+alt+backspaced out of the black screen when kde wouldn't start backup after logout:

kdeinit
ebkded
rksplash
knotify
ksmserver

There were more detailed error messages and if you want those I can copy them out, but this may just have been a result of me killing the process. Thanks.

Oh, and the results of lsmod:

Code:

Module                  Size  Used by    Not tainted

snd-pcm-oss            37736  0  (unused)

snd-mixer-oss          12504  0  [snd-pcm-oss]

usb-storage            66176  0  (unused)

printer                7744  0

intelfb                31004  63

uhci                  24444  0  (unused)

ehci-hcd              17580  0  (unused)

usbcore                59308  1  [usb-storage printer uhci ehci-hcd]

snd-intel8x0          18924  1

snd-ac97-codec        49500  0  [snd-intel8x0]

gameport                1420  0  [snd-intel8x0]

snd-pcm                56072  1  [snd-pcm-oss snd-intel8x0]

snd-timer              13604  0  [snd-pcm]

snd-page-alloc          6328  0  [snd-intel8x0 snd-pcm]

snd-mpu401-uart        3200  0  [snd-intel8x0]

snd-rawmidi            12740  0  [snd-mpu401-uart]

snd-seq-device          3888  0  [snd-rawmidi]

snd                    30852  0  [snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-ac97-codec snd-pcm snd-timer snd-mpu401-uart snd-rawmidi snd-seq-device]

soundcore              3396  4  [snd]

8139too                14376  1

mii                    2272  0  [8139too]

crc32                  2880  0  [8139too]

pcmcia_core            39972  0

ide-scsi                9328  0

agpgart                43940  0  (unused)

And while we're here, is there a list of sound cards and corresponding drivers anywhere? I had GNOME up for abit and the sound worked there but right now on KDE it's not. When I had FreeBSD with KDE, I had to preload all the snd drivers and my sound worked fine, maybe I have to do the same thing here?

Good news! There's just a little left to go. I see the problem. (At least I perceive it as your problem)

1. What is it? As I expected, your X doesn't know better and falls back onto VESA driver. (Which is not 1/2 that bad) What VESA does, is rely on FB (framebuffer) in the kernel to do DRI-like functions. (Which IS, in my experience, bad, or relatively unstable)
Look at your lsmod:
- intelfb 31004 63 //Used by Vesa X driver.
- agpgart 43940 0 (unused)

2. How do I avoid\fix this situation?
Go here - Xorg specialised drivers page - and choose i810 (for all Intel 8x0 chipsets). Follow directions. When you are done, I hope you see the AGPGart module used and intelfb left alone.

THE SOUND: your modules are loaded OK. Just adjust do alsaconfig\alsamix portion of install FAQ from ASLA's website. Better... read the demn millon threads about ALSA\Sound setup already posted in this forum :)

Thanks suslik, that fixed it nicely, although it doesn't show intelfb as 'unused' agpgart is now not unused and it works. Thanks.

sorry for the bump...

i have been having issues with slackware 12 of the same sort.

here are the important parts of my xorg.conf:

Code:

Section "Monitor"



    Identifier  "My Monitor"



# HorizSync is in kHz unless units are specified.

# HorizSync may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S

# USER MANUAL FOR THE CORRECT NUMBERS.



    HorizSync  31.5 - 50.0



#    HorizSync  30-64        # multisync

#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies

#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies



# VertRefresh is in Hz unless units are specified.

# VertRefresh may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S

# USER MANUAL FOR THE CORRECT NUMBERS.



    VertRefresh 40-90



EndSection





# Any number of graphics device sections may be present



Section "Device"

    Identifier  "VESA Framebuffer"

    Driver      "vesa"

    #VideoRam    4096

    # Insert Clocks lines here if appropriate

EndSection

and the results of lsmod:

Code:

Module                  Size  Used by

snd_seq_dummy          6788  0

snd_seq_oss            32896  0

snd_seq_midi_event    10112  1 snd_seq_oss

snd_seq                50640  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event

snd_pcm_oss            42784  0

snd_mixer_oss          18048  1 snd_pcm_oss

nfsd                  209904  13

exportfs                8576  1 nfsd

ipv6                  254496  147

capability              7304  0

commoncap              9344  1 capability

lp                    13736  0

parport_pc            27812  1

parport                34760  2 lp,parport_pc

pcspkr                  6528  0

psmouse                39048  0

serio_raw              9220  0

i2c_prosavage          7552  0

snd_via82xx            26520  2

gameport              15112  1 snd_via82xx

snd_ac97_codec        98980  1 snd_via82xx

ac97_bus                6016  1 snd_ac97_codec

pata_via              12164  0

snd_pcm                72068  3 snd_pcm_oss,snd_via82xx,snd_ac97_codec

snd_timer              22532  2 snd_seq,snd_pcm

snd_page_alloc        11528  2 snd_via82xx,snd_pcm

snd_mpu401_uart        10496  1 snd_via82xx

snd_rawmidi            22560  1 snd_mpu401_uart

snd_seq_device        10508  4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi

snd                    47204  15 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device

ata_generic            9220  0

soundcore              9824  1 snd

shpchp                33172  0

via_agp                12160  1

agpgart                31432  1 via_agp

evdev                  11904  1

8139too                25472  0

mii                    8576  1 8139too

i2c_viapro            11668  0

also, from my lspci command, this looks like my video card:

01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]

i have added 'TerminateServer=true' to the kdmrc file, it didnt help; just to elaborate on the problem, i am running at init level 4, so kdm starts up normally. anytime I logout/shutdown/restart/switch virtual terminals, the screen goes black/blank and i cannot do anything but a hard shutdown.

Having the same issue. I think it is connected with HAL.

well I find that in your /home/youruser/.kde hidden file. could be screwed up easy fix. delete it then log out then log back in it will create a new one. also ccheck in you tmp ksocket that it is accseible to you. this happened when I added a new user that had the same name as an old one. the problem it it is looking to put your cashe in the file and is stopped. After you log in you will reconfigure your kde desk top.Oh yes this happen when I put the new QT 3.8 i think I did'nt realise it changed all the ksocket permissions info. Why it was for a the newer kde in slackware you need to use the qt for the same kde if you want to keep from having problems like this. do you use the kdm display manager or are you doing a startx. hope this helps.