KDE refusing to open
grady
Status: New User - Welcome
Joined: 10 Jul 2009
Posts: 3
Reply Quote
Friends:
Three weeks ago, my main rig was running fine using sidux 2009-02.
Following a sidux d-u, KDE refuses to open. Log-in as user works, following which the KDE desktop screen remains, and nothing else happens.
Dropping back to console (Ctrl-Alt-F2)- as root or as user, I get same response to either
:: Code ::
startx
or
:: Code ::
xinit
:
:: Quote ::
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.XO-lock and start again

I fail to find that file on my system, and don't know what to try next.

Several more sidux d-us have failed to fix the problem.
Nor did an SMXI d-u (no errors noted) yesterday.

I will, of course, be very grateful for suggestions. Providing logs will be a challenge (I'm seriously IT-challenged). I can't pull files from my main rig to this one. And while elinks is working on my main rig, I'm again challenged using it.

grady
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
when you run smxi, you will note that there is an information section when you start.

This section includes very important information about your disk space:

for root / and for /home especially.

Best practice has / and /home on separate partitions, sidux default deviates from best practice.

If either / or /home are close to 100% full, kde cannot start.

Usual cause is failing to clear apt archives: apt-get clean

If you see the kde desktop but it doesn't load that means you probably reinstalled your graphics driver if you use non free, so that shouldn't be the problem.

df -h
shows disk partition usage as well.
Back to top
grady
Status: New User - Welcome
Joined: 10 Jul 2009
Posts: 3
Reply Quote
@x2:

Thank you very much for your prompt response.

In that space in my partitions is ample, and my simple video adapter has never had issues, I thought it better to reply with "problem solved". Which took some time. Finally, a pal (brighter than I), found and fixed the problem.

I quote from his notes.

1. Removed & reinstalled kdm ...(didn't solve).
2. Deleted unnecessary dot files (didn't solve)
3. Examined kdm requirements (apt-cache search kdm) : three packages not installed were installed:
LDM-server,
sdm-terminal,
sidux-art-kde-moros

That fixed the problem; he thought the "sidux-art" was the necessary missing piece.

Thank you again for your kind response.

grady
Back to top
Display posts from previous:   

All times are GMT - 8 Hours