LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
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-10-2011, 09:24 AM   #16
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107

Quote:
Originally Posted by brixtoncalling View Post
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.
First time I created the user, it was just in konsole under xfce. Did it in the actual console this time and it did the complete process, creating home directory and so forth.

But logging into KDE with this user does exactly the same thing that it does when I try to start KDE with my regular user account. Could not start kdeint4....

this is getting frustrating.
 
Old 01-10-2011, 09:28 AM   #17
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,810

Rep: Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446
Yikes!

Quote:
Originally Posted by Cultist View Post
Code:
 chmod -r /home/username
did nothing to help
I really must apologize. I assumed you were familiar with chmod options and I was less than clear, leaving it for you to interpret for your own situation. What I was trying to do was to fix a problem (or rule it out) that can occur a number of ways. One way this can occur doesn't affect most Slackware users because we don't use "sudo". In other distros if you issue a command like "sudo dolphin" to launch a KDE-specific graphic application there are libraries that don't load by default with just sudo and some permissions in your home directory specific to KDE will be changed to root. Other things can cause such problems but however it occurs it needs to be ruled out, I think, largely depending on what caused the problem initially.

The easiest way to do this is thusly

Code:
 chown -R yourusername:yourusername /home/yourusername/.kde
that should do it but you could get fancy with

Code:
 chown $(id -un):$(id -gn) -R $(kde4-config --localprefix)

Again, sorry for being oblique earlier.
 
Old 01-10-2011, 09:39 AM   #18
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Quote:
Originally Posted by Cultist View Post
First time I created the user, it was just in konsole under xfce. Did it in the actual console this time and it did the complete process, creating home directory and so forth.

But logging into KDE with this user does exactly the same thing that it does when I try to start KDE with my regular user account. Could not start kdeint4....

this is getting frustrating.
OK, this means that it has nothing to do with your user account and something to do with your install. Have you touched anything in /etc recently? And what are the permissions on your /tmp directory?
 
Old 01-10-2011, 09:45 AM   #19
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by enorbet View Post
I really must apologize. I assumed you were familiar with chmod options and I was less than clear, leaving it for you to interpret for your own situation. What I was trying to do was to fix a problem (or rule it out) that can occur a number of ways. One way this can occur doesn't affect most Slackware users because we don't use "sudo". In other distros if you issue a command like "sudo dolphin" to launch a KDE-specific graphic application there are libraries that don't load by default with just sudo and some permissions in your home directory specific to KDE will be changed to root. Other things can cause such problems but however it occurs it needs to be ruled out, I think, largely depending on what caused the problem initially.

The easiest way to do this is thusly

Code:
 chown -R yourusername:yourusername /home/yourusername/.kde
that should do it but you could get fancy with

Code:
 chown $(id -un):$(id -gn) -R $(kde4-config --localprefix)

Again, sorry for being oblique earlier.
chmod isn't something I've had to learn before, and I usually wait to learn commands til they're actually needed :P

But, I tried
Code:
 chown -R yourusername:yourusername /home/yourusername/.kde
logged in under my username, it did nothing to help. switched to root and did the same command then changed back to my user and tried to log in, again nothing.

is there any more info I can provide? I wasn't sure what all would be applicable to this.

It has to be a KDE problem because I can log into my other window managers just fine
 
Old 01-10-2011, 09:47 AM   #20
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by brixtoncalling View Post
OK, this means that it has nothing to do with your user account and something to do with your install. Have you touched anything in /etc recently? And what are the permissions on your /tmp directory?
I edit my fstab pretty much daily trying to get it to do what I need it to do, but thats it in /etc.

I haven't changed my /tmp permissions since I installed slackware - still read/write for all users

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

Rep: Reputation: 67
Quote:
Originally Posted by Cultist View Post
I edit my fstab pretty much daily trying to get it to do what I need it to do, but thats it in /etc.

I haven't changed my /tmp permissions since I installed slackware - still read-only for non-root users.
/tmp must be read and write for all users.
 
Old 01-10-2011, 09:51 AM   #22
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by brixtoncalling View Post
/tmp must be read and write for all users.
mistyped, it is rw for all users
 
Old 01-10-2011, 10:40 AM   #23
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Cultist, I'm heading out and I'm out of ideas in any case. Good luck!
 
Old 01-10-2011, 10:43 AM   #24
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
can kde be reinstalled without totally screwing up my system? I'll redo my widgets and theme customization if I have to.
 
Old 01-10-2011, 10:44 AM   #25
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,810

Rep: Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446
Timing

Quote:
Originally Posted by Cultist View Post
It has to be a KDE problem because I can log into my other window managers just fine
Yeah I saw that after I posted. There is something fuXored in KDE. What version were you running? If you hadn't upgraded to v.4.5.9 yet that would kill two birds with one stone. Alien Bob makes it easy with his Ktown area if you're using current.
http://alien.slackbook.org/ktown/

If you're using 13.1 you either have to narrow down with logs to find out specifically what is bad or shotgun it by reinstalling KDE.

Last edited by enorbet; 01-10-2011 at 10:46 AM.
 
Old 01-10-2011, 10:46 AM   #26
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by enorbet View Post
Yeah I saw that after I posted. There is something fuXored in KDE. What version were you running? If you hadn't upgraded to v.4.5.9 yet that would kill two birds with one stone. Alien Bob makes it easy with his Ktown area.
http://alien.slackbook.org/ktown/
If I could log into kde I'd tell you :P but its whatever version comes stock on slackware 13.1. I haven't updated from that

edit: If I upgrade to 4.5.9, will it break the stuff I already have installed?

Last edited by Cultist; 01-10-2011 at 10:57 AM.
 
Old 01-10-2011, 10:58 AM   #27
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,810

Rep: Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446Reputation: 4446
Backup and Reinstall

Quote:
Originally Posted by Cultist View Post
If I could log into kde I'd tell you :P but its whatever version comes stock on slackware 13.1. I haven't updated from that
It's a good idea anyway to take snapshots of your home directory so I would back it up somewhere and reinstall off your DVD. If OTOH this isn't a critical system I'd do the whole upgrade to current. I'm not all the way up to HAL-less KDE 4.6 yet but even 4.5.4 was a substantial improvement over previous versions both in a few features and especially resource management - it's footprint is considerably smaller. There's lots of help here and elsewhere for getting a good clean upgrade. If your system is new enough representing a fairly small investment I'd get the iso and do a fresh install of current.

Regarding current, I do get the kernel bug thing with it where about every 8th or 10th boot panics out but it is so early in the boot process that no file systems have been mounted in read-write mode so there is no consequence to a reset, at least not in my experience over 6 weeks now. I like current rather a lot and I did hesitate for awhile.
 
Old 01-10-2011, 11:01 AM   #28
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
I'll try installing 4.5.9 and see where that takes me. Worst case scenario is I'm back where I am now with a newer KDE
 
Old 01-10-2011, 11:09 AM   #29
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by Cultist View Post
I'll try installing 4.5.9 and see where that takes me. Worst case scenario is I'm back where I am now with a newer KDE
Or was going to. It says 'Assuming you downloaded the complete directory tree "4.5.95" with everything
below'. How exactly do I download the entire tree? file by file?
 
Old 01-10-2011, 11:40 AM   #30
natex
LQ Newbie
 
Registered: Dec 2009
Location: Central/Northern New York, USA
Distribution: slackware-current
Posts: 15

Rep: Reputation: 2
I would advise to NOT update to -current. First figure out what the problem is. (In the long run, this is going to help you out, and adding another variable is going to add to your confusion and frustration.)

1. check and post the /var/log/Xorg.0.log after the error.
2. make sure you can log into another DE (twm).
3. make sure you have kept up to date with the slackware changelog for your version
4. make sure you have_all_ the KDE dependencies installed.
5. see if KDE will start from runlevel 4 (#telinit 4).
6. think back to what you have changed while you were using KDE (new graphics drivers?, KDE update?)

natex
 
  


Reply



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 09:04 AM
running KDE4 apps using sudo: "Could not start ksmserver. Check your installation." ta0kira Slackware 2 12-28-2009 05:49 PM
error message "Could not start kdeinit . Check your installation" suse2166 SUSE / openSUSE 5 06-10-2007 07:55 AM
could not start kstartupconfig, check your installation "when connecting through NIS" damo051078 Linux - Software 0 02-10-2006 03:32 AM

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

All times are GMT -5. The time now is 11:09 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
Open Source Consulting | Domain Registration