Jump to content

Now I've gone and done it...


digby
 Share

Recommended Posts

Well, I broke something and I'm not sure what or why. I've been using Gnome since I started mandrake a week and a half ago. I'm trying to learn everything I can, so I thought I'd start up KDE and see what it had to offer. (I installed both from the CD during the initial install) so I logged in and ran "startkdm" Some text went by and then the system locked up. After getting no response from any keyboard key combos, I did a hard restart. Having decided that my 1st experience with KDE was a ilttle disapointing, I ran startx to load up Gnome. Well, the scren went black and I had another lockup. I rebooted once more, and logged in as a different user (my roommate's hitherto unused account). When I ran startx, it took me to the desktop selection wizard and asked me if I wanted to use KDE, Gnome, Icewin, etc. So I have a usable login, but what did I do wrong, and how do I fix it?

Link to comment
Share on other sites

Logged in as the user that works in X, check /var/log/messages /var/log/syslog and /var/log/XFree86.0.log to see if you can find any specific error for your user that doesn't work during the time frame you attempted to to start kde or gnome. Or better yet, see if it is at all possible to see what the last few messages that fly by say.

Link to comment
Share on other sites

well, I don't see anything in any of those files that looks like a real error... granted, I can't make heads or tails of what most of it is saying... I'm going to logout and I'll try to catch the messages that go by. I was thinking, I didn't give it any particular command to tell the system to go back to gnome after I ran startkdm. I did try startgdm and gdm, but neither seemed to be valid commands. Is there anoyher one I need to try?

 

-edit-

After logging out and back in as my main user, startx worked perfectly. It was also much faster than normal. Do I need to run something like init3 to kill X? Am I completely off my rocker?

Edited by digby
Link to comment
Share on other sites

Ok, it gets better. Now when I run startkde, it gives me what I believe is the same error as before, but now it quits nicely to a bash prompt. Here is the text:

$ startkde
xset:  unable to open display ""
xsetroot:  unable to open display ' '
xmodmap:  unable to open display ' '
xmodmap:  unable to open display ' '
startkde: Starting up...
ksplash: cannot connect to X server
kdeinit: Aborting. $DISPLAY is not set.
Warning: connect () failed: : No such file or directory
ksmserver: cannot connect to X server
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contace kdeinit!
startkde: Running shutdown scripts...
startkde: Done.
$

 

I also how have an icon on my desktop that launched konqueror's file manager to my home dir

Edited by digby
Link to comment
Share on other sites

you could just not use a dm or use Xtart, a console dm.

urpmi Xtart (to install)

Xtart (to run from init 3)

service dm stop (stops the dm)

service dm start (starts the dm)

chkconfig dm off (turns the dm off at boot)

chkconfig dm on (turns the dm on at boot)

 

you can also do it in mcc>System>Services

 

from init 3 you can

 

echo > .xinitrc \ exec /usr/bin/startkde

and hit Enter, then startx will start whatever is in ~/.xinitrc

 

for gnome

exec /usr/bin/startgnome

 

You can have multiple entries and just comment out whichever you don't want to use.

 

this is an old one of mine

#!/bin/bash

#======MISC=======#
(sleep 10; gkrellm) &
#(sleep 5; artsplay /home/soundz/Save.wav & exit) &
#(sleep 4; Eterm --trans -g 80x77+0+0) &
#(sleep 8; krusader) &
(sleep 12; kate) &
(sleep 7; gnome-settings-daemon) &
#(sleep 2; gnome-theme-properties) &
#####/usr/bin/kicker &
#######/usr/bin/kdeinit &
#####/usr/bin/dcopserver && kded &
#~/setbkgrd.sh
#(sleep 12; idesk) &
#enable_X11_numlock &
#(sleep 1; xset s off s noblank dpms 0 0 0) &

#=======WAIMEA=======#
#export LD_LIBRARY_PATH=$QTDIR/usr/lib/qt3/lib/
#export OPERA_FORCE_JAVA_ENABLED=1
#####export LC=C 
#####export LC_ALL=C 
#export QT_XFT=true
#export GDK_USE_XFT=1
#(sleep 4; Eterm --trans -g 80x77+0+0) &
#/usr/bin/wampager &
#exec /usr/X11R6/bin/waimea --menufile /home/bvc/waimea/menu


#=========GNOME2========#
#export LD_LIBRARY_PATH=$QTDIR/usr/lib/qt3/lib/
#export OPERA_FORCE_JAVA_ENABLED=1
#export LC=C 
#export LC_ALL=C 
#export QT_XFT=true
#export GDK_USE_XFT=1
###(sleep 5; /usr/bin/esd -terminate -nobeeps -as 2 -spawnfd 15) &
#(sleep 3; play /home/soundz/maxmsn.wav) &
#Esetroot -s ~/wallpapers/scales/Clean_Gnome.png
#Esetroot -s ~/wallpapers/scales/GNOME-simple_1600x1200.png
#exec /usr/bin/startgnome

#========KDE3-1=======#
export LD_LIBRARY_PATH=$QTDIR/usr/lib/qt3/lib/
export OPERA_FORCE_JAVA_ENABLED=1
##export LC=C 
##export LC_ALL=C 
export QT_XFT=true
export GDK_USE_XFT=1
exec /usr/bin/startkde

#=======AfterStep=======#
#(sleep 6; aterm -T Aterm -tr +sb -bg black -fg yellow -bw 0) &
#exec /usr/X11R6/bin/afterstep

 

by using startx from init 3 you'll be able to see the errors better than w/ a dm.

 

You didn't by chance upgrade X did ya?

 

Have you mv'd your user .kde dir?

mv ~/.kde ~/kdeold

Edited by bvc
Link to comment
Share on other sites

root has always been able to use kde. I should have mentioned that before. When I run startx as root, kde has always run. I've only had 1 occasion to run a GUI as root, so I hadn't played with it that way.

 

I haven't upgraded X. I only have the faintest idea how I might go about it even. Haven't moved the .kde dir either.

Link to comment
Share on other sites

ahh... that makes sense... (I haven't given away the fact that I'm a complete newb, have I?)

 

I'll try it realy quick and let you know what happens

 

-edit-

ok that works... I was actually wondering how to bring up that graphical login screen... I hadn't seen it since shortly after the install. I did get one error while kde was coming up, though:

 

Sound server informational message:

Error while initializing the sound driver:

device /dev/dsp can't be opened (Permission denied)

The sound server will continue, using the null output device.

Edited by digby
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...