FS#70117 - [gjs] 2:1.68.0-1 causes GNOME session to crash when Element and gajim are started together
Attached to Project:
Arch Linux
Opened by Pascal Ernster (hardfalcon) - Sunday, 21 March 2021, 20:13 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 07 May 2021, 16:52 GMT
Opened by Pascal Ernster (hardfalcon) - Sunday, 21 March 2021, 20:13 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 07 May 2021, 16:52 GMT
|
Details
gjs 2:1.68.0-1 causes the whole GNOME session to crash when
Element and gajim are started together. The order in which
both programs are started doesn't seem to matter, but a few
seconds after the second of both (whichever it is) has been
launched, the whole GNOME session crashes and I'm back at
the login screen.
I'm not sure what exactly is causing this, but downgrading to gjs 2:1.66.2-1 from extra made the issue go away. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Friday, 07 May 2021, 16:52 GMT
Reason for closing: Fixed
Additional comments about closing: gjs 2:1.68.1-1
Friday, 07 May 2021, 16:52 GMT
Reason for closing: Fixed
Additional comments about closing: gjs 2:1.68.1-1
Having to remove this extension is not really an option for me. Anyway if this application is related to the crash, well, I will deactivate it.
gnome-shell-extension-appindicator 35-1
Also, as mentioned in the original post, downgrading gjs to 1.66.2-1 works around the issue.
Is this something the appindicator needs to fix?
Because here GNOME still crashes.
When I just disable all GNOME user extensions GNOME session doesn't crash anymore.
`gsettings set org.gnome.shell disable-user-extensions true`
always-indicator@martin.zurowietz.de
appindicatorsupport@rgcjonas.gmail.com
dash-to-dock@micxgx.gmail.com
keypadTiling@abakkk.framagit.org
workspace-indicator@gnome-shell-extensions.gcampax.github.com
https://extensions.gnome.org/extension/258/notifications-alert-on-user-menu/
https://extensions.gnome.org/extension/600/launch-new-instance/
https://extensions.gnome.org/extension/352/middle-click-to-close-in-overview/
https://extensions.gnome.org/extension/1720/weeks-start-on-monday-again/
Thanks for diving into this hardfalcon.
PS: I don't know, but without appindicator, no single app which uses such an icon is shown. Personally I cannot deal with that, especially apps which act like a background service need this, e.g. Nextcloud, Syncthing. Still don't know why GNOME devs are strictly against it. So for me I'll for now ignore the gjs update. :/
NetworkSpeed@m0hithreddy
volume_scroll@qord.si
runcat@kolesnikov.se
middleclickclose@paolo.tranquilli.gmail.com
vpn-snx-indicator@als.kz
executor@raujonas.github.io
lockkeys@vaina.lt
NordVPN_Connect@poilrouge.fr
sound-output-device-chooser@kgshank.net
remove-rounded-corners@markbokil.com
impatience@gfxmonk.net
caffeine@patapon.info
shutdown-timer-gnome-shell-extension
remove-dropdown-arrows@mpdeimos.com
autohide-battery@sitnik.ru
suspend-to-topbar@zeplia.com
Vitals@CoreCoding.com
status-area-horizontal-spacing@mathematical.coffee.gmail.com
trayIconsReloaded@selfmade.pl
tray-icons@zhangkaizhao.com
user-theme@gnome-shell-extensions.gcampax.github.com
arch-update@RaphaelRochet
appindicatorsupport@rgcjonas.gmail.com
apps-menu@gnome-shell-extensions.gcampax.github.com
arch-update@RaphaelRochet
dash-to-dock@micxgx.gmail.com
disable-force-quit@kingodz.gmail.com
shell-volume-mixer@derhofbauer.at
user-theme@gnome-shell-extensions.gcampax.github.com
So i needed to revert back to 1.66.2-1 for gjs and 40.0+39 for gnome-shell.
I have also tried to turn of all extensions but one or two and keep testing.
Sometimes it works for a few moments and after a while it somehow breaks. I haven't tried removing the extensions as a whole, because maybe there are some checks done by these extensions which causes an issue in the background.
So i still downgraded it, which seems to work for me right now, though i which to upgrade of course.
I was afflicted by 'toggling down object GSettings that's already queued to toggle up' gnome-shell crash bug.
I've recompliled gjs package to 43aa4ac32a6f76d4abc592956e55a396cf6bf0b3 (last one just in case...) commit and all is working here.