[Desktop-packages] [Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
When I first started getting these crashes, they were triggered by attaching an external monitor, but that problem seems to have been fixed. Now, I am getting crashes when I put my laptop to sleep and then wake it up. It also destroys screen and tmux sessions somehow, so these crashes have about the same effect on the user as a kernel panic. Yet another way that systemd is broken, I guess? There was a [similar bug](https://bbs.archlinux.org/viewtopic.php?id=224570) reported on Arch Linux, where the redshift extension was blamed as the culprit (though no explanation was given about his this was determined or what the mechanism might be. I'm going to try disabling Night Mode. -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+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 1799789] Re: gnome-shell segfaults when external monitor attached or detached
Following step 3, I was able to file a crash report as bug 1800027. -- 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/1799789 Title: gnome-shell segfaults when external monitor attached or detached Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently updated to Ubuntu 18.10, and I seem to have hit a new bug with gnome-shell/wayland. When an external monitor is attached or detached, gnome-shell crashes with a segmentation fault and falls back to a gdm session. This appears in dmesg : [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d I've also attached the syslog file, starting from where the monitor was plugged in. Here are some of the highlights. First, the monitor is attached, and gnome-shell reaches for St.Bin and finds it already deallocated : Oct 24 12:37:00 evenedric kernel: [97488.486851] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: == Stack trace for context 0x5619aee531c0 == Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #0 5619b71b1ff0 i resource:///org/gnome/shell/ui/userWidget.js:56 (7fdd27a55a60 @ 155) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #1 7ffd8cf7d990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fdd27cb0b80 @ 71) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #2 7ffd8cf7e5c0 b self-hosted:979 (7fdd27cf01f0 @ 440) This repeats several times with a few variations as the js interpreter in gnome-shell falls apart. Then the gnome-shell process is killed : Oct 24 12:37:01 evenedric kernel: [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d This is then followed by the teardown for the whole session, eventually culminating in bringing up a new gdm login session. If you read through the attached syslog file, you can see the whole mess unfold. At about 12:37:05, I plug in an external mouse. Then colord makes a ton of noise for some reason, possibly related to the external monitor. Then I fire up my Bluetooth keyboard and log into a new session. This appears to be a regression. I've used this exact configuration (gdm3 and gnome-shell running in Wayland, with an external monitor that I use while I'm at work) for several Ubuntu, Gnome and Wayland releases. This appears to be a new issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799789/+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 1799789] Re: gnome-shell segfaults when external monitor attached or detached
Oops. Browser gremlins autofilled the wrong package name while I was filing the bug. ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) ** Description changed: + I recently updated to Ubuntu 18.10, and I seem to have hit a new bug + with gnome-shell/wayland. + When an external monitor is attached or detached, gnome-shell crashes with a segmentation fault and falls back to a gdm session. This appears in dmesg : [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] - [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d + [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d I've also attached the syslog file, starting from where the monitor was plugged in. Here are some of the highlights. First, the monitor is attached, and gnome-shell reaches for St.Bin and finds it already deallocated : Oct 24 12:37:00 evenedric kernel: [97488.486851] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: == Stack trace for context 0x5619aee531c0 == Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #0 5619b71b1ff0 i resource:///org/gnome/shell/ui/userWidget.js:56 (7fdd27a55a60 @ 155) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #1 7ffd8cf7d990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fdd27cb0b80 @ 71) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #2 7ffd8cf7e5c0 b self-hosted:979 (7fdd27cf01f0 @ 440) - - This repeats several times with a few variations as the js interpreter in gnome-shell falls apart. Then the gnome-shell process is killed : + This repeats several times with a few variations as the js interpreter + in gnome-shell falls apart. Then the gnome-shell process is killed : Oct 24 12:37:01 evenedric kernel: [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] - Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d + Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d This is then followed by the teardown for the whole session, eventually culminating in bringing up a new gdm login session. If you read through the attached syslog file, you can see the whole mess unfold. At about 12:37:05, I plug in an external mouse. Then colord makes a ton of noise for some reason, possibly related to the external monitor. Then I fire up my Bluetooth keyboard and log into a new session. This appears to be a regression. I've used this exact configuration (gdm3 and gnome-shell running in Wayland, with an external monitor that I use while I'm at work) for several Ubuntu, Gnome and Wayland releases. This appears to be a new issue. -- 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/1799789 Title: gnome-shell segfaults when external monitor attached or detached Status in gnome-shell package in Ubuntu: New Bug description: I recently updated to Ubuntu 18.10, and I seem to have hit a new bug with gnome-shell/wayland. When an external monitor is attached or detached, gnome-shell crashes with a segmentation fault and falls back to a gdm session. This appears in dmesg : [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000]
[Desktop-packages] [Bug 1076802] [NEW] Widget rendering broken after quantal upgrade
Public bug reported: After upgrading from the LTS release to quantal, something seems to have gone very wrong with evolution. It is extremely slow; opening a new message window takes fifteen to thirty seconds, although there is little or no CPU, memory, network or disk activity. Also, it seems to draw widgets incorrectly. See attached screenshot. Evolution package version : 3.6.0-0ubunt amd64 Ubuntu release : 12.10 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Attachment added: Evolution widget rendering bug https://bugs.launchpad.net/bugs/1076802/+attachment/3428284/+files/evolution_widget_bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1076802 Title: Widget rendering broken after quantal upgrade Status in “evolution” package in Ubuntu: New Bug description: After upgrading from the LTS release to quantal, something seems to have gone very wrong with evolution. It is extremely slow; opening a new message window takes fifteen to thirty seconds, although there is little or no CPU, memory, network or disk activity. Also, it seems to draw widgets incorrectly. See attached screenshot. Evolution package version : 3.6.0-0ubunt amd64 Ubuntu release : 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1076802/+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 1076802] Re: Widget rendering broken after quantal upgrade
Hmm. Perhaps this bug is a problem with the Adwaita theme, although Evolution is the only package that seems to be affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1076802 Title: Widget rendering broken after quantal upgrade Status in “evolution” package in Ubuntu: New Bug description: After upgrading from the LTS release to quantal, something seems to have gone very wrong with evolution. It is extremely slow; opening a new message window takes fifteen to thirty seconds, although there is little or no CPU, memory, network or disk activity. Also, it seems to draw widgets incorrectly. See attached screenshot. Evolution package version : 3.6.0-0ubunt amd64 Ubuntu release : 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1076802/+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 787465] Re: View-Show MenuBar isn't working in 11.04 and later in gnome-terminal
Ugh. I loathe global menus, but I don't want a menubar on my terminal. Could we maybe just have a dialog box pop up when you uncheck show menu bar explaining that if you remove the menu, you'll have to get it back by alt-clicking, or running something in the command line, or whatever? I think it's safe to assume that if a user wants a terminal and doesn't want a menu bar, that we can probably relax the usability requirements a little. This might not be the best approach for, say, Evolution, but this is the terminal. If you want to muck around in the terminal, you'd better know what you're doing anyway. Russell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/787465 Title: View-Show MenuBar isn't working in 11.04 and later in gnome-terminal Status in “appmenu-gtk” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-terminal If you click on the global menus the View-Show MenuBar and (un)check it, it won't work, the menu will stay at the 'global menus panel' or whatever it is. In my opinion this option shouldn't exist now, considering that global menus are the future, and also considering that a global menu has the advantage not to keep its own space on the screen :) WORKAROUND: 1. sudo apt-get purge appmenu-gtk appmenu-gtk3 2. Logout 3. Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/787465/+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
