*** This bug is a duplicate of bug 2137758 ***
https://bugs.launchpad.net/bugs/2137758
The issue is that that crash was relatively old (2 Jan) considering that
I've been experiencing the "Bluetooth toggle not responding" scenario
each time I reboot the device or exit a Suspend state.
I don't see a "crash" popup with a corresponding ".crash" file for every
time I log back into a desktop session, meaning that the crash dump
above could be correlated to my Bluetooth issue, but possibly not the
whole story.
I think the behaviour I'm seeing is AT LEAST a combination of both #bug
2137691 and #bug 2137758 .
I propose the scenario in which I'm not seeing proper "segfault" crashes
anymore because I disabled Autosuspend for the Bluetooth controller. I
don't know if it makes sense.
Anyway, the controller MT7925 looks like is creating issues on multiple
distros (I've seen some reports of problems on Arch, Fedora, not only
Debian-based distros).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2137719
Title:
bluetoothd 5.83 segfault during GDM to Desktop session handoff on
Ubuntu 25.10 (MediaTek MT7925 / GNOME 49)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2137719/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
