LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 02-10-2010, 02:12 PM   #1
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Rep: Reputation: 176Reputation: 176
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.
 
Old 02-10-2010, 02:39 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,293

Rep: Reputation: Disabled
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
 
Old 02-10-2010, 02:53 PM   #3
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Original Poster
Rep: Reputation: 176Reputation: 176
Quote:
Originally Posted by Alien Bob View Post
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.
 
Old 02-10-2010, 03:27 PM   #4
MannyNix
Member
 
Registered: Dec 2005
Location: ~
Distribution: Slackware -current, OpenBSD
Posts: 449

Rep: Reputation: 41
Quote:
Originally Posted by cwizardone View Post
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.

Last edited by MannyNix; 02-10-2010 at 03:29 PM. Reason: fix copy/paste
 
Old 02-10-2010, 04:17 PM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,293

Rep: Reputation: Disabled
Quote:
Originally Posted by cwizardone View Post
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
 
Old 02-18-2010, 11:04 AM   #6
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Original Poster
Rep: Reputation: 176Reputation: 176
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.
 
Old 02-23-2010, 06:59 PM   #7
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Original Poster
Rep: Reputation: 176Reputation: 176
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.
 
  


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] dbus problem slackware64-current gtludwig Slackware 5 01-05-2010 10:32 AM
[SOLVED] -current dbus-daemon shows Reject messages danielldaniell Slackware 4 08-03-2009 03:36 AM
kde4 + hal + dbus problems on -current (24 mar) janhe Slackware 1 03-29-2009 02:18 PM
Fedora Core 9 update dbus.exception & dbus.proxies & DBus.Error.AccessDenied errors trien27 Fedora 1 12-08-2008 11:23 PM
DBUS Problem at -Current willysr Slackware 6 03-26-2007 10:01 PM


All times are GMT -5. The time now is 07:53 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration