LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-22-2012, 02:41 PM   #1
minty33
Member
 
Registered: Aug 2012
Location: earth
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Posts: 136

Rep: Reputation: 1
D-BUS problem


my mint has been sooo buggy i don't know why i didn't upgrade i fresh installed maya. i should start another thread but you seem to always answer tobi so i'll just post this here if thats ok.

while i was editing fstab before i used nano i tried to gksu caja to do it in the gui for some reason and got the following error.
keep in mind this persisted through a reboot and also never did this before because i always ued gksu caja to get write permissions on my external hd w/ no issue. i see no d-bus daemon running why and how do i restart it. unrelated i was getting dbus issues connecting wireless w/ wicd on a diff OS the other day. is my hardware failing or is this all coincidence.

****note****
i can launch using "dbus-launch gksu caja" but why do i need to do it that way. just "gksu caja" gives following>>
------------

(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

(caja:3765): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf warning: failure listing pairs in `/apps/caja/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
linuxubuntu minty33 is online now Report This Post

Last edited by minty33; 08-22-2012 at 03:03 PM. Reason: appended info
 
Old 08-23-2012, 04:52 PM   #2
abrinister
Member
 
Registered: Dec 2010
Location: /home
Distribution: RL: Arch x64 VM: Debian
Posts: 460

Rep: Reputation: 38
Why don't you just start the d-bus daemon?

Code:
/etc/rc.d/rc.dbus start
Alex Brinister
 
Old 08-26-2012, 06:16 PM   #3
minty33
Member
 
Registered: Aug 2012
Location: earth
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Posts: 136

Original Poster
Rep: Reputation: 1
no directory

when i type "/etc/rc.d/rc.dbus start"
iget no such file or directory. this is on my Mint13 box. is file called something different because of upstart or something or is missing this file the source of my original error.
 
Old 08-26-2012, 07:23 PM   #4
abrinister
Member
 
Registered: Dec 2010
Location: /home
Distribution: RL: Arch x64 VM: Debian
Posts: 460

Rep: Reputation: 38
Oh sorry, wrong distro. It should be

Code:
service dbus start
Alex Brinister
 
  


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
Dbus System bus and Session bus mainloops deimus Linux - Distributions 0 08-20-2010 07:49 AM
Ata bus error problem with raid 5 alex6666 Linux - Hardware 0 11-16-2006 04:04 AM
/proc/bus/usb problem arunka Linux - Hardware 0 11-07-2005 07:54 AM
Firefox 1.0.7 bus problem on Fedora 3 gdpine Linux - Software 4 10-12-2005 08:09 PM
USB bus 1 deregistered problem xgreen Slackware 0 09-18-2005 09:30 AM


All times are GMT -5. The time now is 10:09 PM.

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