I found the crash file (_usr_libexec_bluetooth_bluetoothd.0.crash) dated Jan 2. Due to strict security/privacy requirements, I cannot run 'ubuntu-bug' to upload the full dump.
However, with the help of Gemini 3 Pro I manually unpacked the crash report. Here is the 'StacktraceTop': ------------------------------------------------ ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ------------------------------------------------ While the trace lacks debug symbols, I think the crash in 'g_main_loop_run' aligns with the "device lost" scenario. Please confirm if this text-based stack trace is sufficient for your debugging needs or let me know if you need additional sanitized data. -- 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
