[Desktop-packages] [Bug 1915681] Re: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384
Hi, (a) The version is correct: nemanja@thinkpad:~$ gnome-shell --version GNOME Shell 3.38.2 nemanja@thinkpad:~$ dpkg -l | grep gnome-shell ii gnome-shell 3.38.2-1ubuntu1~20.10.1 amd64 graphical shell for the GNOME desktop (b) I'm not sure what do you mean? Could the faulty GPU memory be also responsible for such behavior? Randomly, I'm experiencing random graphics crashes (also on previous Ubuntu 19.04) and I plan to do a GPU memory test. Also, maybe related: Enabled Gnome extensions: - Dash to Panel (https://extensions.gnome.org/extension/1160/dash-to-panel/) - Desktop icons (system extension) -- 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/1915681 Title: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Feb 12 09:10:29 thinkpad gnome-shell[85476]: Error in freeze/thaw accounting Feb 12 09:10:29 thinkpad gnome-shell[85476]: GNOME Shell crashed with signal 5 Feb 12 09:10:29 thinkpad gnome-shell[85476]: == Stack trace for context 0x561dd4480270 == Feb 12 09:10:29 thinkpad gnome-shell[85476]: #0 561dd96ccf18 i resource:///org/gnome/shell/ui/windowManager.js:1384 (1c61e18d03d0 @ 589) Feb 12 09:10:29 thinkpad gnome-shell[85476]: #1 7ffc72c53090 b self-hosted:850 (22fd89d4e5b0 @ 454) Taken from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1897765/comments/38 This crash will also show up in the existing error buckets from bug 1897765: https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") - JS ERROR: TypeError: actor.__animationInfo is undefined
Thank you. Cheers -- 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/1897765 Title: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") - JS ERROR: TypeError: actor.__animationInfo is undefined Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell package in Debian: Unknown Bug description: [ Impact ] Launching terminator crashes gnome-shell [ Test case ] - Launch terminator - GNOME Shell should not crash In any case these errors should not be reported anymore with gnome-shell 3.38.2-1ubuntu1~20.10.1: - https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd - https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605 [ Regression potential ] A window could not be animated on size change. --- Launching terminator crashes gnome-shell, happens on two separate machines. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 18:05:57 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1600706451 InstallationDate: Installed on 2019-10-14 (350 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/tjaalton ProcEnviron: LANG=fi_FI.UTF-8 PATH=(custom, user) SHELL=/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 5SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
Recently I'm also experiencing this on: Ubuntu 20.20 (Linux 5.8.0-41-generic) AMD® A10-5750m apu with radeon(tm) hd graphics × 4 This is an older system indeed, but still... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel- ppa but that made no difference. It appears to be a bug in radeon. Nothing specific makes this happen, just regular usage with a compositing window manager. I'm not playing games or particularly exercising the GPU. The last two times I was just reading in web browser. It's also happened in the middle of the night while I was asleep. Sometimes I have a few days uptime, sometimes it happens in less than 24 hours from boot. This never happened before the radeon update mentioned on the first line. I'll attach two files of dmesg output. As per https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and started apport for next time it happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
I'm sorry, I saw the "don't post errors for gnome-shell 3.38.2-1ubuntu1~20.10.1" message after I have already submitted my comment. -- 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/1897765 Title: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell package in Debian: Unknown Bug description: [ Impact ] Launching terminator crashes gnome-shell [ Test case ] - Launch terminator - GNOME Shell should not crash In any case these errors should not be reported anymore with gnome-shell 3.38.2-1ubuntu1~20.10.1: - https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd - https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605 [ Regression potential ] A window could not be animated on size change. --- Launching terminator crashes gnome-shell, happens on two separate machines. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 18:05:57 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1600706451 InstallationDate: Installed on 2019-10-14 (350 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/tjaalton ProcEnviron: LANG=fi_FI.UTF-8 PATH=(custom, user) SHELL=/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 5SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
I'm experiencing this issue on gnome-shell 3.38.2-1ubuntu1~20.10.1. Gnome crashes randomly, this time it happened while MS Teams video call was running, and I tried to switch to Nautilus (file browser). Extract from the syslog is attached. ** Attachment added: "Syslog extract" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897765/+attachment/5463197/+files/gnome-crash.txt -- 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/1897765 Title: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell package in Debian: Unknown Bug description: [ Impact ] Launching terminator crashes gnome-shell [ Test case ] - Launch terminator - GNOME Shell should not crash In any case these errors should not be reported anymore with gnome-shell 3.38.2-1ubuntu1~20.10.1: - https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd - https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605 [ Regression potential ] A window could not be animated on size change. --- Launching terminator crashes gnome-shell, happens on two separate machines. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 18:05:57 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1600706451 InstallationDate: Installed on 2019-10-14 (350 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/tjaalton ProcEnviron: LANG=fi_FI.UTF-8 PATH=(custom, user) SHELL=/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 5SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
On Ubuntu 19.10 I'm experiencing the same thing as the comment above: ### Jan B (hey-e) wrote on 2015-04-08: #143 I have a laptop and a monitor as secondary display ... Every time I switch back from only using the monitor (laptop display disabled) to using the laptop display as a second screen – I need to rearrange the displays. By default they are side-by-side but I always want the monitor above the laptop display. ### I don't have Ubuntu 20.x installed at the moment to confirm whether it happens there, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Mutter: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp