Package: blueman Version: 1.22~bzr707-1+b1 Severity: normal With recent update to blueman, blueman-manager started quitting when removing bluetooth adapter. It asks, should it quit or enable bluetooth (how's that possible?), leaving blueman-applet running but not blueman-manager.
-- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blueman depends on: ii bluez 4.96-3 ii dbus 1.4.16-1 ii hicolor-icon-theme 0.10-2 ii libatk1.0-0 2.2.0-2 ii libbluetooth3 4.94-3 ii libc6 2.13-7 ii libcairo2 1.10.2-2 ii libfontconfig1 2.8.0-2.1 ii libfreetype6 2.4.2-2.1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-0 2.28.8-1 ii libgtk2.0-0 2.24.4-3 ii libpango1.0-0 1.28.3-6 ii libpython2.7 2.7.2-6 ii librsvg2-common 2.32.1-1 ii libstartup-notification0 0.10-1 ii notification-daemon 0.4.0-1 ii obex-data-server 0.4.4-2 ii python 2.7.2-9 ii python-central 0.6.14+nmu2 ii python-dbus 0.84.0-2 ii python-gobject 2.28.6-5 ii python-gtk2 2.24.0-2 ii python-notify 0.1.1-3 Versions of packages blueman recommends: ii libpulse-mainloop-glib0 0.9.21-3 ii policykit-1 <none> ii python-gconf 2.28.1-3 blueman suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
