Here's a more complete set of logs around the bluetooth crash
``` 12:22:15 gnome-shell: JS ERROR: TypeError: monitor is null _reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/layout.js:210:17 12:22:15 pulseaudio: (6856.168| 0.000) [pulseaudio] flist.c: pulsecore/hashmap.c: entries flist is full (don't worry) 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 kernel: Code: c0 c3 66 0f 1f 44 00 00 31 c0 48 85 ff 74 59 53 48 8b 4f 08 48 89 fb 48 85 c9 74 43 48 3b 31 48 8b 79 08 74 4b 48 85 ff 74 5e <48> 39 37 48 8b 47 08 74 0d 48 89 f9 48 89 c7 eb ea 0f 1f 44 00 00 12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 0000562f7fa9bea2 sp 00007ffd0d54b720 error 4 in bluetoothd[562f7fa00000+f3000] 12:22:15 kernel: show_signal_msg: 5 callbacks suppressed 12:22:15 upowerd: unhandled action 'unbind' on /sys/devices/virtual/misc/uhid/0005:046D:B019.0007 12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:87 12:22:15 gnome-shell: g_array_unref: assertion 'array' failed 12:22:15 gdm-x-session: (II) event23 - MX Master 2S Mouse: device removed 12:22:15 gdm-x-session: (II) event23 - MX Master 2S Mouse: device removed 12:22:15 gdm-x-session: (**) Option "fd" "72" 12:22:15 gdm-x-session: (II) config/udev: removing device MX Master 2S Mouse 12:22:15 gnome-shell: g_array_unref: assertion 'array' failed 12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:86 12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:86 12:22:15 gdm-x-session: (II) UnloadModule: "libinput" 12:22:15 gdm-x-session: (II) event22 - MX Master 2S Keyboard: device removed 12:22:15 gdm-x-session: (**) Option "fd" "60" 12:22:15 gdm-x-session: (II) config/udev: removing device MX Master 2S Keyboard 12:22:15 acpid: input device has been disconnected, fd 22 12:22:14 gnome-shell: JS ERROR: TypeError: monitor is null _reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/layout.js:210:17 12:22:14 pulseaudio: (6855.591| 86.788) [pulseaudio] bluez5-util.c: Properties changed in device /org/bluez/hci0/dev_E8_F7_90_05_99_E4 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948990 Title: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948990/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
