LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Upgraded to 'current' and Now Have Dbus Problems, Among Others. (https://www.linuxquestions.org/questions/slackware-14/upgraded-to-current-and-now-have-dbus-problems-among-others-788296/)

cwizardone 02-10-2010 02:12 PM

Upgraded to 'current' and Now Have Dbus Problems, Among Others.
 
Upgraded to 'current' and now have a series of problems.
First, when trying to 'startx' to fire up KDE I get the following error message,

"Could not start d-bus. Can you call qdbus?"


If I try Xfce it gives this similar message,

"Failed to execute dbus-launch to autolaunch d-bus sessions.


When logging in, but before entering the password this error message pops up:

'Dialups-check-enab'
'nologin-str'
'Configuration error - unknown item. (notify administrator)'


Any suggestion on how to fix all the above would be greatly appreciated.
Thanks.
:hattip:

Alien Bob 02-10-2010 02:39 PM

Did you make sure you dealt with all the .new files that were left on your computer? Specifically, the .new files in /etc/rc.d ?

Thinking of /etc/rc.d/rc/udev.new , /etc/login.defs.new , ...

Eric

cwizardone 02-10-2010 02:53 PM

Quote:

Originally Posted by Alien Bob (Post 3859489)
Did you make sure you dealt with all the .new files that were left on your computer? Specifically, the .new files in /etc/rc.d ?

Thinking of /etc/rc.d/rc/udev.new , /etc/login.defs.new , ...

Eric

Thank you for taking time to reply.
What do you mean by '...dealt with...'?
Thanks, again.
:hattip:

MannyNix 02-10-2010 03:27 PM

Quote:

Originally Posted by cwizardone (Post 3859510)
What do you mean by '...dealt with...'?

I guess Eric means (taken from man slackpkg):
Code:

new-config
            This  action  searches for .new configuration files and ask
the user what to do with those files.
new-config is very useful when you perform an upgrade and leave the configuration files to  be reviewed later. Instead of a manual search, diff, and replace; you can use the new-config action.


Alien Bob 02-10-2010 04:17 PM

Quote:

Originally Posted by cwizardone (Post 3859510)
Thank you for taking time to reply.
What do you mean by '...dealt with...'?
Thanks, again.

I mean, upgrading Slackware packages often leaves files in your filesystem with the extension ".new". If you do not do anything with these .new files, there will be a fair chance that your Slackware system will not function properly. These files have the extension .new so that the package upgrade will not overwrite the original (which you may have edited yourself).
Most of these .new files will be configuration files, but some are startup scripts (those in /etc/rc.d/). You should always check the changes in the .new files compared to the original ones, and in many cases, copying the .new file over the original one (i.e. overwriting the old with the new) is the proper procedure. Especially the new rc-scripts will be often required for proper functioning of your computer.

Eric

cwizardone 02-18-2010 11:04 AM

Many Thanks for taking the time to reply.
I've done as you have suggested, i.e., I'v searched for *new files and reviewed and copied over what I found, but the problem remains.
From searching on the 'Net this appears to be something to do with
gcc, but I haven't found anything that looks like the answer.

cwizardone 02-23-2010 06:59 PM

OK. I did a text search and found the two lines,

'Dialups-check-enab'
'nologin-str'

in the same file, /etc/login.defs.

After going in and commenting out the lines the problem was solved.
Just FYI.
:hattip:


All times are GMT -5. The time now is 01:38 PM.