blueman-tray crashed with gi.repository.GLib.GError in __call__(): g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetStatusIconImplementations” (19)

Bug #1990317 reported by Sebastian Kowalski
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

something went wrong during update

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: blueman 2.3.2-1
ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
Uname: Linux 5.19.0-1001-raspi aarch64
ApportVersion: 2.23.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Tue Sep 20 22:57:10 2022
ExecutablePath: /usr/bin/blueman-tray
ImageMediaBuild: 20211105
InterpreterPath: /usr/bin/python3.10
JournalErrors:
 wrz 20 22:57:06 username-desktop systemd[54585]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
 wrz 20 22:57:07 username-desktop bluetoothd[54585]: Failed to set privacy: Rejected (0x0b)
 wrz 20 22:57:07 username-desktop bluetoothd[54585]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-tray
ProcEnviron:
 LANGUAGE=pl_PL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonArgs: ['/usr/bin/blueman-tray']
PythonDetails: N/A
SourcePackage: blueman
Title: blueman-tray crashed with gi.repository.GLib.GError in __call__(): g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetStatusIconImplementations” (19)
UpgradeStatus: Upgraded to kinetic on 2022-09-20 (0 days ago)
UserGroups: adm cdrom dip gpio i2c input lpadmin lxd plugdev sambashare spi sudo video

Revision history for this message
Sebastian Kowalski (kowalski.sebastian) wrote :
tags: removed: need-duplicate-check
Changed in blueman (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Alex Murray (alexmurray) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
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.