D
Deleted member 9563
Guest
My windows manager(s) won't start. I'm not sure where the problem lies because I have mixed information. The title of this thread is probably the best hint since it is KDM that I need to work in the end, but I will list information and errors below.
- This hardware (minus a new SSD for / ) ran 10.0-RELEASE for several years.
- The video driver is loaded.
- I added an SSD for / and kept the old drive. The new drive got 11.0-RELEASE installed.
- There are no old xorg.conf files anywhere.
- The /home/ole directory is symlinked to the old drive and files all looks fine there.
I am guessing that last point is where the KDM manager is balking. However:
- I added users "video" and "kdm" to group "wheel" which resulted in
opening the three window simple X display and that didn't happen before.
- I installed fluxbox as a test, and the error is:
The original and continuing errors shown at boot time on tty right after the initializing of the video driver are:
Apologies for my usual vagueness, but I'm not sure what to focus on here. Perhaps there are configuration files on the old /home directory. However, I'm being careful there because I am hoping that KDE will come back with my original configuration. Other programs, not yet installed, also have configurations which I would like to keep if possible.
Edit: perhaps it is useful to show the tail end of these files as well:
-
- This hardware (minus a new SSD for / ) ran 10.0-RELEASE for several years.
- The video driver is loaded.
- I added an SSD for / and kept the old drive. The new drive got 11.0-RELEASE installed.
- There are no old xorg.conf files anywhere.
- The /home/ole directory is symlinked to the old drive and files all looks fine there.
I am guessing that last point is where the KDM manager is balking. However:
- I added users "video" and "kdm" to group "wheel" which resulted in
startx
opening the three window simple X display and that didn't happen before.
- I installed fluxbox as a test, and the error is:
Code:
Couldn't connect to X server
The original and continuing errors shown at boot time on tty right after the initializing of the video driver are:
Code:
kdm_greet[881]: Cannot create $HOME
kdm: :0[880: Received unknown or unexpected command -2 from greeter
kdm: :0[880: Abnormal termination of greeter for display :0, code1, signal0
Apologies for my usual vagueness, but I'm not sure what to focus on here. Perhaps there are configuration files on the old /home directory. However, I'm being careful there because I am hoping that KDE will come back with my original configuration. Other programs, not yet installed, also have configurations which I would like to keep if possible.
Edit: perhaps it is useful to show the tail end of these files as well:
Code:
dmesg
info: [drm] size 8294400
info: [drm] fb depth is 24
info: [drm] pitch is 7680
fbd0 on drmn0
VT: Replacing driver "vga" with new "fb".
info: [drm] Initialized radeon 2.29.0 20080528 for drmn0 on minor 0
Code:
.xsession-errors
krunner: Fatal IO error: client killed
kded4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kactivitymanagerd: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
polkit-kde-authentication-agent-1: Fatal IO error: client killed
klauncher: Exiting on signal 1
kwin: Fatal IO error: client killed
kwin: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
QProcess: Destroyed while process is still running.
ksmserver: Fatal IO error: client killed
claws-mail: Fatal IO error 2 (No such file or directory) on X server :0.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
Code:
/var/log/Xorg.0.log
[ 307.819] (II) sysmouse: SetupAuto: protocol is SysMouse
[ 307.819] (II) config/devd: device /dev/ums0 already opened
[ 320.973] (II) config/devd: terminating backend...
[ 320.973] (II) UnloadModule: "mouse"
[ 320.973] (II) UnloadModule: "kbd"
[ 320.978] (II) Server terminated successfully (0). Closing log file.
-