[Desktop-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash
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 562f7fa9bea2 sp 7ffd0d54b720 error 4 in bluetoothd[562f7fa0+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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1948990 Title: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash Status in gnome-control-center package in Ubuntu: New Bug description: I had bluetooth crash (see logs below). After the crash, I attempted to restart bluetooth by pressing the On/Off switch in the top-right of the Bluetooth tab of gnome-control-center (it was set to off). After pressing the switch, the switch read "On", but the display of Bluetooth devices still appeared as it does when Bluetooth is off (it read "Bluetooth Turned Off\nTurn on to connect devices and receive file transfers."). I was able to remedy the situation by manually executing `sudo bluetoothd`. I did this while the above On/Off switch was "Off" and the Bluetooth device list said Bluetooth was off. After executing, the Bluetooth device list listed all my Bluetooth devices as expected. This is with bluetoothd 5.48. Bluetooth crash logs ``` 12:22:15 pulseaudio: (6856.168| 0.576) [pulseaudio] bluez5-util.c: Bluetooth daemon disappeared 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, status=11/SEGV 12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000] 10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 Uname: Linux 5.10
[Desktop-packages] [Bug 1948990] [NEW] Bluetooth does not turn on via gnome-control-center after bluetooth.service crash
Public bug reported: I had bluetooth crash (see logs below). After the crash, I attempted to restart bluetooth by pressing the On/Off switch in the top-right of the Bluetooth tab of gnome-control-center (it was set to off). After pressing the switch, the switch read "On", but the display of Bluetooth devices still appeared as it does when Bluetooth is off (it read "Bluetooth Turned Off\nTurn on to connect devices and receive file transfers."). I was able to remedy the situation by manually executing `sudo bluetoothd`. I did this while the above On/Off switch was "Off" and the Bluetooth device list said Bluetooth was off. After executing, the Bluetooth device list listed all my Bluetooth devices as expected. This is with bluetoothd 5.48. Bluetooth crash logs ``` 12:22:15 pulseaudio: (6856.168| 0.576) [pulseaudio] bluez5-util.c: Bluetooth daemon disappeared 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, status=11/SEGV 12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000] 10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 27 13:00:09 2021 InstallationDate: Installed on 2021-01-04 (295 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1948990 Title: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash Status in gnome-control-center package in Ubuntu: New Bug description: I had bluetooth crash (see logs below). After the crash, I attempted to restart bluetooth by pressing the On/Off switch in the top-right of the Bluetooth tab of gnome-control-center (it was set to off). After pressing the switch, the switch read "On", but the display of Bluetooth devices still appeared as it does when Bluetooth is off (it read "Bluetooth Turned Off\nTurn on to connect devices and receive file transfers."). I was able to remedy the situation by manually executing `sudo bluetoothd`. I did this while the above On/Off switch was "Off" and the Bluetooth device list said Bluetooth was off. After executing, the Bluetooth device list listed all my Bluetooth devices as expected. This is with bluetoothd 5.48. Bluetooth crash logs ``` 12:22:15 pulseaudio: (6856.168| 0.576) [pulseaudio] bluez5-util.c: Bluetooth daemon disappeared 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'. 12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, status=11/SEGV 12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000] 10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) 10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22) ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3
[Desktop-packages] [Bug 1946279] [NEW] GNOME session crashes on wakeup from sleep
Public bug reported: Upon waking up, my system occasionally has its GNOME session crash after logging in. This takes it back to the log-in screen, and resets the session with all previous windows lost. Here are some relevant logs. ``` 12:46:01 gnome-shell: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 330049 error_code 11 request_code 12 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 12:46:02 systemd-coredum: Process 3287 (gnome-shell) of user 1000 dumped core. Stack trace of thread 3287: #0 0x7f15c76b7817 raise (libpthread.so.0) #1 0x56092dc02a6b n/a (gnome-shell) #2 0x7f15c76b7980 __restore_rt (libpthread.so.0) #3 0x7f15c9437fc1 n/a (libglib-2.0.so.0) #4 0x7f15c943a939 g_log_writer_default (libglib-2.0.so.0) #5 0x7f15c9438bae g_log_structured_array (libglib-2.0.so.0) #6 0x7f15c94395ee g_log_structured_standard (libglib-2.0.so.0) #7 0x7f15c6bc7c41 n/a (libgdk-3.so.0) #8 0x7f15c6bd4ac3 n/a (libgdk-3.so.0) #9 0x7f15c60849ba _XError (libX11.so.6) #10 0x7f15c60818eb n/a (libX11.so.6) #11 0x7f15c6081995 n/a (libX11.so.6) #12 0x7f15c60828f0 _XReply (libX11.so.6) #13 0x7f15c6068445 XGetWindowProperty (libX11.so.6) #14 0x7f15c6be5064 n/a (libgdk-3.so.0) #15 0x7f15c6be5d55 n/a (libgdk-3.so.0) #16 0x7f15c6bceeef n/a (libgdk-3.so.0) #17 0x7f15c6bcf1f6 n/a (libgdk-3.so.0) #18 0x7f15c6b99d70 gdk_display_get_event (libgdk-3.so.0) #19 0x7f15c6bcef82 n/a (libgdk-3.so.0) #20 0x7f15c9432537 g_main_context_dispatch (libglib-2.0.so.0) #21 0x7f15c9432770 n/a (libglib-2.0.so.0) #22 0x7f15c9432a82 g_main_loop_run (libglib-2.0.so.0) #23 0x7f15c795c9ac meta_run (libmutter-2.so.0) #24 0x56092dc0248c n/a (gnome-shell) #25 0x7f15c72d5bf7 __libc_start_main (libc.so.6) #26 0x56092dc025ca n/a (gnome-shell) Stack trace of thread 3291: #0 0x7f15c73c8cb9 __GI___poll (libc.so.6) #1 0x7f15c94326e9 n/a (libglib-2.0.so.0) #2 0x7f15c9432a82 g_main_loop_run (libglib-2.0.so.0) #3 0x7f15c9a202d6 n/a (libgio-2.0.so.0) #4 0x7f15c945a2a5 n/a (libglib-2.0.so.0) #5 0x7f15c76ac6db start_thread (libpthread.so.0) #6 0x7f15c73d571f __clone (libc.so.6) Stack trace of thread 3289: #0 0x7f15c73c8cb9 __GI___poll (libc.so.6) #1 0x7f15c94326e9 n/a (libglib-2.0.so.0) #2 0x7f15c94327fc g_main_context_iteration (libglib-2.0.so.0) #3 0x7f15c9432841 n/a (libglib-2.0.so.0) #4 0x7f15c945a2a5 n/a (libglib-2.0.so.0) #5 0x7f15c76ac6db start_thread (libpthread.so.0) #6 0x7f15c73d571f __clone (libc.so.6) Stack trace of thread 3293: #0 0x7f15c76b2ad3 futex_wait_cancelable (libpthread.so.0) #1 0x7f15a9d9efdb n/a (radeonsi_dri.so) #2 0x7f15a9d9ebc7 n/a (radeonsi_dri.so) #3 0x7f15c76ac6db start_thread (libpthread.so.0) #4 0x7f15c73d571f __clone (libc.so.6) // Stack traces for threads 3300, 3303, 3309, 3295, 3336, 3301, 3294, 3338, 3306, 3334, 3297, // 3347, 3337, 3305, 3343, 3335, 3339, 3299, 3304, 3341, 3290, 3296, 3298, 3302, 3307, 3332, 3340, // 3344, and 3345 which are all similar to 3293, where there's a futex and then calls to any of // radeonsi_dri.so, libmozjs-52.so.0, libglib-2.0.so.0, or libpulse.so.0 // // Happy to give the explicit stack traces for these if needed. 12:46:03 pulseaudio: ( 0.000| 0.000) [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true 12:46:03 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry ``` Happy to provide more logs if needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 16:29:03 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-04 (275 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1946279 Title: GNOME session crashes on wakeup from sleep Status in gnome-shell package in Ubuntu: New Bug description: Upon waking up, my system occasionally has its GNOME session cr
[Desktop-packages] [Bug 1924190] [NEW] Display is wrong resolution, aspect ratio, and size
Public bug reported: So last night (April 13th), I installed an update from Canonical that popped up in a GUI, it said something about a security update (I didn't look at it too hard). Since then I've rebooted my machine and now the display is the wrong resolution (it ought to be 3840 x 2160, 597mm x 336mm, 60fps [monitor](https://www.lg.com/us/monitors/lg-27UD58-B-4k- uhd-led-monitor)). I'm presently on Ubuntu 20.04.2 LTS. ``` $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* ``` ``` $ inxi -G Graphics: Device-1: NVIDIA GM107GL [Quadro K2200] driver: N/A Display: x11 server: X.Org 1.20.9 driver: fbdev,nouveau unloaded: modesetting,vesa resolution: 1024x768~76Hz OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 ``` I've tried unplugging and replugging the monitor, rebooting several times, adding an xrandr modeline, and changing `/etc/default/grub` to have `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"` (where it was `"quiet splash"` before). None of these have led to any success. My feeling is that there's some graphics driver issue (that the renderer is llvmpipe doesn't seem right). I guess there's also a confounding factor in that I'm running the display through a [KVM switch](https://www.tripplite.com/2-port- displayport-usb-kvm-switch-4k-60-hz-hdr%7EB005DPUA4), but I really hope that's not the problem. I've been using it for a while anyway with no issue, the Windows 10 partition of this machine renders fine, and I have another machine running 18.04 that gets the resolution just fine. I tried booting into recovery mode, which was no dice (also tried cleaning up `dpkg` through the recovery interface). While I was in the GRUB menu, I noticed that it defaults to the kernel version 5.8.0-49, but that I also had 5.8.0-48 installed. Boothing into the older kernel, everything worked. Curious, I checked the logs. ``` $ cat /var/log/dpkg.log | grep linux-image 2021-04-13 23:15:01 install linux-image-5.8.0-49-generic:amd64 5.8.0-49.55~20.04.1 ``` And that lines up with when I did that update. So it seems that the new kernel version somehow made it so xrandr couldn't detect any of the modes on my monitor and just defaulted to some default. So the workaround presently is just boot with 5.8.0-48. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 17:21:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2021-02-15 (58 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=babb99d2-0867-4673-b5ec-2cce0643eaa2 ro quiet splash i915.alpha_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-
