Bug 1786323
| Summary: | starting chrome crash gnome-shell | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ope @Linux <ope-linux> |
| Component: | gnome-shell | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | fmuellner, gnome-sig, jadahl, jlmagee, otaylor, philip.wyett |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 16:23:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 1647500 [details]
journalctl --since "2019-12-24 12:00:00" > crash.journalctr.txt
I have the same or a similar issue. If extensions are enabled in the tweak-tool, starting chrome, even following a clean shutdown of chrome, crashes gnome and a reboot, via power button or Ctrl-Alt-F3 and root login, is required and the some careful cleanup of chrome. Disabling extensions and removing the Singleton symlinks in /home/<username>/.config/google-chrome/ will ease the cleanup of remaining windows. rpm -qa | grep gnome-shell gnome-shell-extension-activities-configurator-78-1.fc31.noarch gnome-shell-extension-window-list-3.34.2-1.fc31.noarch gnome-shell-extension-topicons-plus-22-6.fc31.20191031.0a35713.noarch gnome-shell-extension-media-player-indicator-0-0.25.20190419git65867e7.fc31.noarch gnome-shell-extension-remove-bluetooth-icon-0.5.1-11.fc31.noarch gnome-shell-extension-screenshot-window-sizer-3.34.2-1.fc31.noarch gnome-shell-extension-calc-0-0.14.gite4f4ac5.fc29.noarch gnome-shell-extension-launch-new-instance-3.34.2-1.fc31.noarch gnome-shell-extension-openweather-1-0.38.20181119git7ea4ce7.fc31.noarch gnome-shell-extension-do-not-disturb-button-34-1.fc31.noarch gnome-shell-extension-pomodoro-debugsource-0.13.3-1.fc27.x86_64 gnome-shell-extension-user-theme-3.34.2-1.fc31.noarch gnome-shell-extension-panel-osd-1-0.26.20180616giteb0d3c2.fc29.noarch gnome-shell-extension-drive-menu-3.34.2-1.fc31.noarch gnome-shell-extension-no-topleft-hot-corner-19.0-2.fc31.noarch gnome-shell-extension-ibus-font-0.20170217-6.fc31.noarch gnome-shell-extension-remove-volume-icon-0.5.1-11.fc31.noarch gnome-shell-extension-freon-39-2.fc31.noarch gnome-shell-extension-workspace-indicator-3.34.2-1.fc31.noarch gnome-shell-extension-horizontal-workspaces-3.34.2-1.fc31.noarch gnome-shell-3.34.2-1.fc31.x86_64 gnome-shell-extension-pidgin-1.0.3-5.fc31.noarch gnome-shell-extension-auto-move-windows-3.34.2-1.fc31.noarch gnome-shell-extension-places-menu-3.34.2-1.fc31.noarch gnome-shell-extension-pomodoro-0.15.2-0.1.gitcb1ad32.fc31.x86_64 chrome-gnome-shell-10.1-5.fc31.x86_64 gnome-shell-extension-simple-dock-0.1-0.20150505git25c94bc.fc29.6.noarch gnome-shell-extension-system-monitor-applet-38-4.20191019gitf00e248.fc31.noarch gnome-shell-extension-windowoverlay-icons-34-2.fc31.noarch gnome-shell-extension-common-3.34.2-1.fc31.noarch gnome-shell-extension-iok-0.20161021-7.fc31.noarch gnome-shell-extension-windowsNavigator-3.34.2-1.fc31.noarch gnome-shell-extension-native-window-placement-3.34.2-1.fc31.noarch gnome-shell-extension-historymanager-prefix-search-12-2.fc31.noarch gnome-shell-extension-background-logo-3.34.0-1.fc31.noarch gnome-shell-theme-selene-3.4.0-17.fc31.noarch gnome-shell-extension-apps-menu-3.34.2-1.fc31.noarch gnome-tweaks-3.34.0-1.fc31.noarch Linux <host>.<domain>.net 5.4.7-200.fc31.x86_64 #1 SMP Tue Dec 31 22:25:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux FWIW, the system got to Fedora 31 from Fedora 29 using the DNF system update process. gnome-shell 3.34.3 seems to have resolved the issue I spoke too soon. Seems better but it still occurs. I'm attaching a journal log snippet and an abrt directory Created attachment 1651701 [details]
journal log
Created attachment 1651702 [details]
abrt directory
Created attachment 1653249 [details]
$ journalctl --since "2020-01-18 08:58:00" --until "2020-01-18 09:05:00" >journal.txt
It's now even worser. Upload of SIGABRT fails again for unknown reasons :( Description of problem: After fresh boot, starting google-chrome, I faced a crashing of gnome-shell. Version-Release number of selected component (if applicable): $ rpm -qa | grep gnome-shell gnome-shell-extension-places-menu-3.34.2-1.fc31.noarch gnome-shell-extension-horizontal-workspaces-3.34.2-1.fc31.noarch gnome-shell-extension-common-3.34.2-1.fc31.noarch gnome-shell-extension-apps-menu-3.34.2-1.fc31.noarch gnome-shell-extension-pidgin-1.0.3-5.fc31.noarch gnome-shell-extension-user-theme-3.34.2-1.fc31.noarch chrome-gnome-shell-10.1-5.fc31.x86_64 gnome-shell-extension-background-logo-3.34.0-1.fc31.noarch gnome-shell-extension-window-list-3.34.2-1.fc31.noarch gnome-shell-3.34.3-1.fc31.x86_64 gnome-shell-extension-launch-new-instance-3.34.2-1.fc31.noarch $ rpm -qa | grep google-chrome google-chrome-stable-79.0.3945.130-1.x86_64 How reproducible: each time Steps to Reproduce: 1. boot 2. login 3. call gnome-tweaks and re-enable Extensions/AddOns again if disabled again for some unknown reasons 4. Simple start chrome :) Actual results: crash of chrome Expected results: still working gnome desktop and chrome Additional info: SIGABRT isn't very useful in my case ... So I did: $ journalctl --since "2020-01-18 08:58:00" --until "2020-01-18 09:05:00" >journal.txt in hope that's may be useful. Also, that the attachment is correctly assign to this answer. Why does it affect my setup? What does trigger the crash? Even "$ google-chrome --disable-extensions" doesn't has any changes here? just checked, enabling/disabling gnome extensions via tweaks doesn't effects the crash result :( Given the backtrace in the journal I'd say it looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1773882. strange, there seems to be some updates applied, I can use chrome again for now. For my point of view the case/bug can be closed. Hopefully never rise again ... Damn, the problem rises again .... What has been changed behind? $ rpm -qa | grep gnome-shell gnome-shell-extension-places-menu-3.34.2-1.fc31.noarch gnome-shell-extension-horizontal-workspaces-3.34.2-1.fc31.noarch gnome-shell-extension-common-3.34.2-1.fc31.noarch gnome-shell-extension-apps-menu-3.34.2-1.fc31.noarch gnome-shell-extension-pidgin-1.0.3-5.fc31.noarch gnome-shell-extension-user-theme-3.34.2-1.fc31.noarch chrome-gnome-shell-10.1-5.fc31.x86_64 gnome-shell-extension-background-logo-3.34.0-1.fc31.noarch gnome-shell-extension-window-list-3.34.2-1.fc31.noarch gnome-shell-3.34.3-1.fc31.x86_64 gnome-shell-extension-launch-new-instance-3.34.2-1.fc31.noarch $ rpm -qa | grep google-chrome google-chrome-stable-79.0.3945.130-1.x86_64 This issue is caused by https://gitlab.gnome.org/GNOME/mutter/issues/944 whic no one on the Gnome team seems interested in fixing. I've switched to Xfce, perhaps permanently. This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1647496 [details] retrace failed ... Description of problem: After fresh boot, starting google-chrome, I faced a crashing of gnome-shell. Version-Release number of selected component (if applicable): olaf@tux64 ~]$ rpm -qa | grep gnome-shell gnome-shell-extension-places-menu-3.34.2-1.fc31.noarch gnome-shell-extension-horizontal-workspaces-3.34.2-1.fc31.noarch gnome-shell-extension-common-3.34.2-1.fc31.noarch gnome-shell-extension-apps-menu-3.34.2-1.fc31.noarch gnome-shell-extension-pidgin-1.0.3-5.fc31.noarch gnome-shell-extension-user-theme-3.34.2-1.fc31.noarch chrome-gnome-shell-10.1-5.fc31.x86_64 gnome-shell-extension-background-logo-3.34.0-1.fc31.noarch gnome-shell-extension-window-list-3.34.2-1.fc31.noarch gnome-shell-3.34.2-1.fc31.x86_64 gnome-shell-extension-launch-new-instance-3.34.2-1.fc31.noarch [olaf@tux64 ~]$ rpm -qa | grep google-chrome google-chrome-stable-79.0.3945.88-1.x86_64 How reproducible: each time Steps to Reproduce: 1. boot 2. login 3. Simple start chrome :) Actual results: crash of chrome Expected results: still working gnome desktop and chrome Additional info: