LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-09-2011, 10:42 PM   #1
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Rep: Reputation: 105Reputation: 105
"Could not start kdeinit4. Please check installation." problem booting into KDE


So I closed out X with ctrl+alt+backspace, and when I did startx it showed the Nvidia splash screen like usual, then shows for just a second that loading splash screen that KDE does. Then a little box pops into the top left corner that says "Could not start kdeinit4. Please check installation."

I hit okay on the box, it takes me back to the terminal. I try again, same result. I reboot. Same result. So I use xwmconfig to change to enlightenment, which boots up fine. So I ctrl+alt+backspace out and retry KDE again, with the same problem.

This is the first time I've closed out KDE in over a week, so I guess its possible that anything I've done over that time may have somehow broken it. I hadn't noticed any problems til now. The only reason I did it this time was because I'd changed the KDE plasma theme and I wanted to watch the new one boot up.

I'm typing on the same computer and the same Slackware installation right now, just running E instead of KDE.

Any tips on how to fix KDE this would be greatly appreciated.
 
Old 01-09-2011, 11:39 PM   #2
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Could it be something simple like a /tmp partition at full capacity? That can cause a DE to act funny.

If that's not it, you could try renaming your .kde directory and start KDE to see if it is a problem with your config files (make sure you can get your old .kde back afterwards!)
 
Old 01-10-2011, 07:42 AM   #3
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
Quote:
Originally Posted by brixtoncalling View Post
Could it be something simple like a /tmp partition at full capacity? That can cause a DE to act funny.

If that's not it, you could try renaming your .kde directory and start KDE to see if it is a problem with your config files (make sure you can get your old .kde back afterwards!)
I deleted all the .tgz files in /tmp, that didn't help. To avoid messing anything up I moved /tmp to /home and created an empty /tmp directory and tried. After doing this I couldn't boot into any wm - it just gave an x error and took me back. So I moved the original /tmp back to where it went and started xfce to get on here.

I tried renaming .kde to .kdebackup, which had no effect other than removing my theme for the 2 nanoseconds that I see my KDE loading screen.

Same problem happening and still can't fix it. Need help please!
 
Old 01-10-2011, 07:52 AM   #4
SavoTU
Member
 
Registered: Apr 2005
Distribution: Slackware64 Current
Posts: 175

Rep: Reputation: 27
I have had similar problems they have always been caused by either no disk space or wrong permissions. Try running running df to check you have free space.
 
Old 01-10-2011, 07:54 AM   #5
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
I only have two system partitions, root and home. df shows
Code:
/dev/root             76896316  33225672  39764444  46% /
/dev/sdb3            229799920 148525824  69600868  69% /home
So I don't think its a space issue
 
Old 01-10-2011, 08:00 AM   #6
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
See if there is an .xsession-errors file in your home directory. It may give you some ideas as to what is wrong.
 
Old 01-10-2011, 08:08 AM   #7
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
found it, but its extremely long. I'll copy over the last twenty or so lines

Code:
ProcessControl: Application '/usr/bin/nepomukservicestub' stopped unexpected (Process crashed)
Application '/usr/bin/nepomukservicestub' crashed. No restart!
Application '/usr/bin/nepomukservicestub' exited normally...
[/usr/bin/nepomukservicestub] virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection 
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x1ec5900) 
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection 
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection 
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection 
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x1ec2e20) 
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection 
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x1e4c240) 
virtual Soprano::ODBC::Connection::~Connection() QThread(0x1dbe9a0) 
Shutting down virtuoso instance 3928 
Virtuoso server stopped: 0
Application '/usr/bin/nepomukservicestub' exited normally...
NepomukServer(3920)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
startkde: Running shutdown scripts...
startkde: Done.
No protocol specified
kded4: cannot connect to X server :0
kded(9239): Communication problem with  "kded" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.kded was not provided by any .service files" " 

KCrash: Application 'kded4' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
No protocol specified
drkonqi: cannot connect to X server :0.0
not sure what to be looking for. should I paste the whole thing?

Last edited by Cultist; 01-10-2011 at 08:10 AM.
 
Old 01-10-2011, 08:37 AM   #8
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
The error is there ... but I don't know exactly what it is or how to resolve it. Try creating a new user and log into KDE. That'll show us whether you can a corrupt config file somewhere.

You haven't been using KDE as root have you?
 
Old 01-10-2011, 08:50 AM   #9
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
Quote:
Originally Posted by brixtoncalling View Post
The error is there ... but I don't know exactly what it is or how to resolve it. Try creating a new user and log into KDE. That'll show us whether you can a corrupt config file somewhere.

You haven't been using KDE as root have you?
never log into KDE as root. I tried after this all started but it gave the same error.

created a new user with adduser in terminal, and when I ctrl+alt+backspace out and log in the console as the new user. after hitting startx as the new user, it kinda hangs there repeating
Code:
xauth: timeout in locking authority file //.Xauthority
then it tries to boot X, and gets as far as the original error I posted about but instead of that, the box says
Code:
Kdestartupconfig4 does not exist or fails. The error code is 3. Check
couldn't use xwmconfig to change wm either. So I logged back into my usual user name and back into xfce.
 
Old 01-10-2011, 08:55 AM   #10
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,027

Rep: Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928Reputation: 1928
Permissions

Try running chmod as root on your "/home/username?" directory recursively so that any permission changes are undone and restored to normal. You at least need to nail this down so you know and are not assuming.
 
Old 01-10-2011, 08:57 AM   #11
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
Quote:
Originally Posted by enorbet View Post
Try running chmod as root on your "/home/username?" directory recursively so that any permission changes are undone and restored to normal. You at least need to nail this down so you know and are not assuming.
Code:
 chmod -r /home/username
did nothing to help

Last edited by Cultist; 01-10-2011 at 09:18 AM.
 
Old 01-10-2011, 09:39 AM   #12
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Quote:
Originally Posted by Cultist View Post
Code:
xauth: timeout in locking authority file //.Xauthority
I wonder if that shouldn't be:
Code:
/home/USERNAME/.Xauthority
What does "echo $HOME" tell you?
 
Old 01-10-2011, 09:47 AM   #13
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
it gives my home directory.

I don't think its a problem with my user account, because I'm logged in it right now under xfce. The error only comes up when I try to log into KDE (which I much prefer to xfce)

That xauth problem only happened when I tried to log in under that new user acct I made.

echo #HOME under the console logged in as that account just says / instead of /home/username. But still, that was just a test account I was making.

Last edited by Cultist; 01-10-2011 at 09:48 AM.
 
Old 01-10-2011, 10:06 AM   #14
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,052

Rep: Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773Reputation: 1773
Stale lock file? Try removing /tmp/kde-<username>/.
 
Old 01-10-2011, 10:14 AM   #15
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Quote:
Originally Posted by allend View Post
Stale lock file? Try removing /tmp/kde-<username>/.
He tried a blank /tmp above without success. However, the fact that no WM started when he did that suggests something might have been wrong with that /tmp, so it may well be that allend...

Cultist, this is perhaps off topic, but how did you create a new user and not have $HOME set correctly? "adduser" should take care of all that. I suggest creating a new user again with that command and see if a new user can start KDE.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Could not start kdeinit4. Check your installation. BobNutfield Slackware 1 09-10-2010 10:04 AM
running KDE4 apps using sudo: "Could not start ksmserver. Check your installation." ta0kira Slackware 2 12-28-2009 06:49 PM
error message "Could not start kdeinit . Check your installation" suse2166 SUSE / openSUSE 5 06-10-2007 08:55 AM
could not start kstartupconfig, check your installation "when connecting through NIS" damo051078 Linux - Software 0 02-10-2006 04:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration