Package: libdbus-1-3 Version: 1.1.1-3 Severity: normal
When I upgrade libdbus-1-3 from the etch version to the lenny version, I start getting the following message when I start bluetooth-applet from the command-line: libnotify-Message: Unable to get session bus: dbus-launch failed to autolaunch D-Bus session: Option `--close-stderr' is unknown. I'm not clear on how much of a problem this is for the effective operation of bluetooth-applet, or whether it affects other programs. It occurs when I have the following set of programs installed: ii bluez-gnome 0.6-1 Bluetooth utilities for GNOME ii dbus 1.0.2-1 simple interprocess messaging system ii libdbus-1-3 1.1.1-3 simple interprocess messaging system but not when I have the following: ii bluez-gnome 0.6-1 Bluetooth utilities for GNOME ii dbus 1.0.2-1 simple interprocess messaging system ii libdbus-1-3 1.0.2-1 simple interprocess messaging system My research shows that the --close-stderr option was introduced in the 1.1 branch of dbus, prior to the release of the 1.1.0 tarball. -- System Information: Debian Release: 3.1 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-5-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libdbus-1-3 depends on: ii libc6 2.7-4 GNU C Library: Shared libraries Versions of packages libdbus-1-3 recommends: ii dbus 1.0.2-1 simple interprocess messaging syst -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
