Some apps must be run with dbus-launch

Bug #694627 reported by Jody McIntyre
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: dbus

I've logged in to my system using the "Ubuntu Desktop Edition" session and run a shell.

When running some applications, I get dbus errors unless I run the app with 'dbus-launch'. dbus and gconf are running.

Examples:

$ evince

(evince:16835): EggSMClient-WARNING **: Failed to connect to the session manager: Could not open network socket

Failed to get bus connection: Error connecting: Connection refused
**
GLib-GIO:ERROR:/build/buildd/glib2.0-2.26.0/gio/gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)

** (evince:16835): WARNING **: Couldn't run bug-buddy

$ ubuntu-bug evince
warning, in file '/var/lib/dpkg/status' near line 24975 package 'jre':
 error in Version string '1.6.0_05-1': invalid character in version number
warning, in file '/var/lib/dpkg/available' near line 26517 package 'jre':
 error in Version string '1.6.0_05-1': invalid character in version number
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused)
Error showing url: Operation not supported
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused)
Error showing url: Operation not supported

(The projects.gnome.org URL is a general overview of gconf, not D-Bus troubleshooting information as expected.)

dbus and gconf are running:

$ ps aux |grep dbus |grep -v grep
103 1060 0.0 0.2 8240 6344 ? Ss Dec22 1:47 dbus-daemon --system --fork
gdm 8459 0.0 0.0 3456 568 ? S 16:37 0:00 /usr/bin/dbus-launch --exit-with-session
scjody 8565 0.0 0.0 3348 204 ? Ss 16:37 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session gnome-session
scjody 8568 0.0 0.0 3456 564 ? S 16:37 0:00 /usr/bin/dbus-launch --exit-with-session gnome-session
scjody 8569 0.0 0.0 4568 1976 ? Ss 16:37 0:05 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

$ ps aux |grep gconf |grep -v grep
scjody 8574 0.0 0.1 9616 4520 ? S 16:37 0:00 /usr/lib/libgconf2-4/gconfd-2

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dbus 1.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
Date: Sun Dec 26 18:19:08 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: dbus

Revision history for this message
Jody McIntyre (scjody) wrote :
Revision history for this message
Alemann Massho (armistice-con-deactivatedaccount) wrote :

Can you still reproduce this bug on an up-to-date installation? If you can, could you please provide us with some system logs?

Changed in dbus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for dbus (Ubuntu) because there has been no activity for 60 days.]

Changed in dbus (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Lennart Karssen (l.c.karssen) wrote :

Bug #694627 links to this report. It seems that the two are related.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.