Jump to content

5 big debian problems


Recommended Posts

1) KDE don't work. Same as GNOME, except no WM at all.

2) GNOME dont work. Starts up with the startup screen and none of the little icons appear. it sits for ages and eventually starts sawfish, that's all.

3) Mozilla & Firebird freeze up. No reason at all. I can't work it out. Sometimes Mozilla works

4) GTK 1 apps fonts look like $#!T.

5) Somehow my / partition filled FULLY. I did a apt-get clean, that regained 500mb of space but that isn't enough. I think it has to do with XMMS. When I run it and i haven't loaded the sound driver it writes to the drive twice a second, maybe to a logfile. Where would this file be? My /home partition is unaffected

 

I'm going to try some stuff and if you have any suggestions please let me know. I know that isn't much information but KDE,GNOME,Mozilla,Firebird don't sppit any error messages out at all. The firebird run's fine in mandy.

 

James

Link to comment
Share on other sites

apt-get install rcconf

 

Use rcconf to turn off all the unecessary junk and

apt-get remove pkg_name

to remove them. I've always seen post about kde and kde apps taking a long time to start in mandrake, and I now know why. I'm new to networking. There are many things that cause this in kde, dm, and X, the worst is dhcp. Basically a badly misconfigured network will slow them down to a crawl. I ended up removing dhcp and using static IP's :roll: . A misconfigured net will also stop the Moz-family and Konq completely.

I do use fluxbox, but i know i can change the WM in kde
Edit /usr/bin/startkde (mandrake)

# finally, give the session control to the session manager

# if the KDEWM environment variable has been set, then it will be used as KDE's

# window manager instead of kwin.

# if KDEWM is not set, ksmserver will ensure kwin is started.

# kwrapper is used to reduce startup time and memory usage

# kwrapper does not return usefull error codes such as the exit code of ksmserver.

# We only check for 255 which means that the ksmserver process could not be 

# started, any problems thereafter, e.g. ksmserver failing to initialize, 

# will remain undetected.

test -n "$KDEWM" && KDEWM="--windowmanager $KDEWM"

kwrapper ksmserver $KDEWM

if test $? -eq 255; then

 # Startup error

 echo 'startkde: Could not start ksmserver. Check your installation.'  1>&2

 xmessage -geometry 500x100 "Could not start ksmserver. Check your installation."

fi

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...