blueman-applet crashed with gi.repository.GLib.GError in __init__(): g-io-error-quark: Timeout was reached (24)

[Brian Bogdan]

https://errors.ubuntu.com/problem/32abdcb54be5cbce03513de83428152ffe5decce

---

was after update. Not sure what actually happened

```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/blueman/plugins/applet/TransferService.py", line 235, in _on_dbus_name_appeared
    self._manager = Manager()
                    ^^^^^^^^^
  File "/usr/lib/python3/dist-packages/blueman/gobject.py", line 11, in __call__
    cls._instance = super().__call__(*args, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/blueman/bluez/obex/Manager.py", line 29, in __init__
    self._object_manager = Gio.DBusObjectManagerClient.new_for_bus_sync(
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)
```

ProblemType: Crash
DistroRelease: Ubuntu 24.10
Package: blueman 2.4.1-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: MATE
Date: Sat May 18 15:17:03 2024
ExecutablePath: /usr/bin/blueman-applet
InstallationDate: Installed on 2024-05-11 (7 days ago)
InstallationMedia: Ubuntu-MATE 24.10 "Oracular Oriole" - Daily amd64 (20240510)
InterpreterPath: /usr/bin/python3.12
JournalErrors: -- No entries --
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-applet
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1
PythonArgs: ['/usr/bin/blueman-applet']
PythonDetails: N/A
SourcePackage: blueman
Title: blueman-applet crashed with gi.repository.GLib.GError in __init__(): g-io-error-quark: Timeout was reached (24)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users

[Launchpad Janitor (janitor)]

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

[Benjamin Drung (bdrung)]

I ran into the same crash when I upgraded noble to oracular.

[Jason Harvey (jason-alioth)]

Seeing the same crash, also on Oracular.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2066094

[Sebastien Bacher (seb128)]

Could someone having the issue attach the corresponding journalctl session log? Is the problem that bluez fails to start for some reason?

The problem doesn't seem new, https://errors.ubuntu.com/problem/32abdcb54be5cbce03513de83428152ffe5decce shows that reports started in focal

[Alexandre ARNOUD (aarno)]

please find attached full journalctl session log

[Stephematician (stephematishun)]

I believe I got the same error (when clicking the applet). I believe this is resolved upstream, and I haven't seen this error since v2.4.3 built from https://salsa.debian.org/debian/blueman

[Daniel van Vugt (vanvugt)]

Bumped to high because this is the #1 crash in all of Ubuntu 25.04.

[Christian Ehrhardt (paelzer)]

FYI, hit the same on my test of the cinnamon desktop for plucky

[Sebastien Bacher (seb128)]

> I believe this is resolved upstream, and I haven't seen this error since v2.4.3 built from https://salsa.debian.org/debian/blueman

Plucky has 2.4.4 so and the comment from Christian suggests then it's not fixed by the newer version

@Christian: did you have a chance to check if the bluez service was active/working?

[Daniel van Vugt (vanvugt)]

This is now the #1 crash in all of 25.10 too.

[Daniel van Vugt (vanvugt)]

Reported upstream: https://github.com/blueman-project/blueman/issues/2930

[Guybrush88 (guybrush)]

I just got this issue in Lubuntu 26.04