Cannot Connect To The Session Bus Org.freedesktop.dbus.error.noserver
2011-04-05 22:47:25 DarkSniper Member Registered: 2011-04-05 Posts: 74 [Solved] Running Thunar with sudo/su Causes GVFS Errors? Hi, I switched from Xubuntu to Arch a few days ago, and am loving it so far, but I'm running into an issue when running Thunar with sudo or su. As a result, trash as root doesn't work. I'm not sure if this is related to GVFS, but drives also do not appear when running Thunar as root. Not too major, since it's just a slight inconvenience, and I only need root privileges with Thunar occasionally. Though it'd be awesome if someone knows how to fix this, since my searching has come up with nothing for a problem like this. When logging in as root itself, the problem doesn't occur, it only happens when running it as my regular account through the sudo or su command. Here's the terminal output with the errors: [dark@YiffingInHell ~]$ suPassword: [root@YiffingInHell dark]# thunar(thunar:29855): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.(thunar:29855): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.(thunar:29855): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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. Last edited by DarkSniper (2011-04-06 02:43:46) Failure is not an option... It comes bundled with Windows. Offline #2 2011-04-05 22:54:27 ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 13,462 Re: [Solved] Running Thunar with sudo/su Causes GVFS Errors? Use gksu or kdesu instead of sudogksu is available available via pacmankdesu is part of kdebase-runtime (it brings in a lot of baggage if you don't already have KDE)edit: Thank you to SS4 and his post here Last edited by ewaller (2011-04-05 22:56:25) Nothing is too wonderful to be true, if it be consistent
Support Search GitHub This repository Watch 10 Star 48 Fork 28 gtimelog/gtimelog Code Issues 8 Pull requests 4 Projects 0 Pulse Graphs New issue dbus not found since upgrade to xubuntu 14.10 #27 Closed sam-github opened this Issue Nov 13, 2014 · 4 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants sam-github commented Nov 13, 2014 I can't run gtimelog since upgrading xubuntu from https://bbs.archlinux.org/viewtopic.php?id=116323 14.04 to 14.10. I'm not using the gtk-based ubuntu, but xubuntu, so I suspect that the packager missed some mandatory dependencies. I'm not sure what the dependency is, or what it needs to be running, any ideas? I suspect there is some gtk appindicator library that is needed, as well as something (no idea what) that https://github.com/gtimelog/gtimelog/issues/27 will start a dbus session. I can run using gtimelog --ignore-dbus, but then I don't get gtimelog in the indicator menu, and worse, when I close the window, gtimelog stays running, so I have to ctrl-c it from the terminal. Here is a normal run: % /usr/bin/gtimelog ** (gtimelog:2648): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-qofJCBylav: Connection refused gtimelog: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-uSTaNe6RdN: Connection refused % ls -l /tmp/dbus* ls: cannot access /tmp/dbus*: No such file or directory Here is with --ignore-dbus: % /usr/bin/gtimelog --ignore-dbus ** (gtimelog:2812): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-qofJCBylav: Connection refused (gtimelog:2812): libappindicator-WARNING **: Unable to get the session bus: Could not connect: Connection refused (gtimelog:2812): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Could not connect: Connection refused GTimeLog developers member mgedmin commented Nov 14, 2014 when I close the window, gtimelog stays running, so I have to ctrl-c it from the terminal. Is
Rachid Achellal on 2011-07-16 This bug report is a duplicate of: Bug #858122: incomplete migration to /run (shutdown script order has been demolished). https://bugs.launchpad.net/bugs/811441 Edit Remove 636 This bug affects 133 people Affects Status Importance https://bugzilla.redhat.com/show_bug.cgi?id=575191 Assigned to Milestone dbus (Ubuntu) Edit Confirmed Medium Unassigned Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description The dbus service doesn't start correctly. This happens since version dbus_1.4.12-4ubuntu2_amd64. Jul 16 11:15:41 desktop kernel: [ 855.230791] init: dbus main cannot connect process (2079) terminated with status 1 Jul 16 11:15:41 desktop kernel: [ 855.230812] init: dbus main process ended, respawning Jul 16 11:15:41 desktop kernel: [ 855.234366] init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Jul 16 11:15:41 desktop kernel: [ 855.234404] init: plymouth-upstart-bridge main process (2081) cannot connect to terminated with status 1 Jul 16 11:34:35 desktop kernel: [ 1988.064675] init: dbus main process (2452) terminated with status 1 Jul 16 11:34:35 desktop kernel: [ 1988.064706] init: dbus main process ended, respawning Jul 16 11:34:35 desktop kernel: [ 1988.069952] init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Jul 16 11:34:35 desktop kernel: [ 1988.069994] init: plymouth-upstart-bridge main process (2454) terminated with status 1 Tags: dbus natty oneiric raring Edit Tag help Rachid Achellal (rachid-s) wrote on 2011-07-16: #1 It seems that the init script is not removing the follow files: root@desktop:/var/run/dbus# ls pid system_bus_socket After I remove this and reboot the pc then it works. Also the Xorg is starting normally Rachid Achellal (rachid-s) on 2011-07-16 tags: added: oneiric pacrook (paul-crook) wrote on 2011-07-16: #2 I can confirm I'm experiencing the same problem with dbus service failing to start. Log reports "dbus main process ... terminated with signal 1". Desktops
Forgot Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug575191 - system-config-firewall-1.2.23-1.fc13.noarch error messages at attempted startup Summary: system-config-firewall-1.2.23-1.fc13.noarch error messages at attempted startup Status: CLOSED WONTFIX Aliases: None Product: Fedora Classification: Fedora Component: system-config-firewall (Show other bugs) Sub Component: --- Version: 14 Hardware: All Linux Priority low Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Thomas Woerner QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2010-03-19 13:23 EDT by Jim Haynes Modified: 2012-08-16 17:15 EDT (History) CC List: 5 users (show) jonas jurek.bajor ram srushfeldt twoerner See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2012-08-16 17:15:49 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) some lines from /var/log/messages that may be relevant (3.29 KB, text/plain) 2010-03-22 16:27 EDT, Jim Haynes no flags Details sessseion-errors.old (6.25 KB, text/plain) 2010-03-22 16:28 EDT, Jim Haynes no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Jim Haynes 2010-03-19 13:23:21 EDT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100216 Fedora/3.5.8-1.fc12 Firefox/3.5.8 When I try to run it from system->administration->firewall I get the error org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth I have selinux disabled When I run it from the command line I get (system-config-firewall:2609): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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 expi