Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62036 - [gnome-shell] coredump at startup in 3.32.0+15+gb7d79a5f0-1
Attached to Project:
Arch Linux
Opened by Konstantin Gizdov (kgizdov) - Sunday, 17 March 2019, 01:57 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 19:51 GMT
Opened by Konstantin Gizdov (kgizdov) - Sunday, 17 March 2019, 01:57 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 19:51 GMT
|
DetailsDescription:
GNOME Shell cannot start and dump core immediately at startup. Downgrading to 3.32.0 solves the issue. Lots of references to libmozjs: could this be due to the removed `sed` in recent commit? Additional info: * package version(s) - gnome-shell-3.32.0+15+gb7d79a5f0-1 * config and/or log files etc. - attached * link to upstream bug report, if any - n/a Steps to reproduce: 1. Upgrade to gnome-shell-3.32.0+15+gb7d79a5f0-1 2. Reboot 3. Try to login |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 19:51 GMT
Reason for closing: Fixed
Additional comments about closing: fixed upstream
Tuesday, 10 December 2019, 19:51 GMT
Reason for closing: Fixed
Additional comments about closing: fixed upstream
I have attached a couple of seconds worth of journalctl logs containing the core dump.
This is still happening with gnome-shell-3.32.0+16.
I found that disabling extensions was necessary.
`gsettings set org.gnome.shell disable-user-extensions false`
So far I haven‘t found a fix or workaround