Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#57222 - [gjs] 1:1.50.3-1 is causing serious issues with GNOME's lock screen

Attached to Project: Arch Linux
Opened by Kyle Matheson (kmat) - Thursday, 25 January 2018, 05:11 GMT
Last edited by Jan de Groot (JGC) - Monday, 16 April 2018, 11:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No



Clicking the lock screen background/wallpaper (before it slides up) with the mouse causes gnome-shell to crash. Additionally, this can be considered a security concern as it briefly exposes the users desktop and running applications. Downgrading to gjs 1:1.50.2-1 resolves the issue.

Additional info:
* package version: gjs 1:1.50.3-1

Steps to reproduce:
1. Lock screen (Super+L)
2. Use the mouse to click the lock screen background/wallpaper
3. Watch it crash
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 16 April 2018, 11:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  gjs 1.52.0 does not crash but prints infinite amounts of backtraces everytime gnome-shell does something wrong.
Comment by debek (debek) - Monday, 29 January 2018, 07:16 GMT
The same problem
Comment by Jan de Groot (JGC) - Monday, 29 January 2018, 10:31 GMT
Is this still an issue with gjs 1.50.4-1?
Comment by Inixi Noisse (Inixi) - Monday, 29 January 2018, 10:48 GMT
The mouse click is not related to the crash. Gnome Shell can crash also during:
- computer sleep
- computer wake
- attempting to login to already started session

Example stack trace of that event:

Jan 26 10:20:18 workstation systemd-coredump[24353]: Process 22829 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 22829:
#0 0x00007f649d3f0422 g_type_check_instance_cast (
#1 0x00007f649b136960 st_label_set_text (
#2 0x00007f64978471c8 ffi_call_unix64 (
#3 0x00007f6497846c2a ffi_call (
#4 0x00007f649c0a1cab n/a (
#5 0x00007f649c0a3607 n/a (
#6 0x00000ffeff80b810 n/a (n/a)
#7 0x0000560e7622c650 n/a (n/a)
#8 0x00000ffeffcb8b73 n/a (n/a)
Comment by Léo (Leeo97one) - Monday, 29 January 2018, 11:33 GMT
Comment by Vlad (vlad3ciobanu) - Tuesday, 30 January 2018, 17:33 GMT
With gnome-shell 3.26.2 (gjs 1.50.4-1) I have experienced freezes when opening Firefox tabs or some GTK apps like gEdit.
It seemed Javascript related so I googled and found a recomandation to downgrade gjs. I installed 1.50.3-1 and now the problems are less frequent, but my system still freezes.

Additional info:
* package version: gjs 1:1.50.4-1 but also with 1:1.50.3-1

Steps to reproduce:
It happenes at irregular intervals - when loading a site in Firefox or when pressing Super or starting a GTK app.

Maybe this journalctl snippet helps:

gnome-shell[2194]: Received error from DBus search provider org.gnome.Epiphany.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Servi
dbus-daemon[2161]: [session uid=1000 pid=2161] Successfully activated service 'org.gnome.Documents'
dbus-daemon[2161]: [session uid=1000 pid=2161] Successfully activated service 'org.gnome.bijiben.SearchProvider'
bijiben-shell-s[28096]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
bijiben-shell-s[28096]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-documents[28081]: JS LOG: Can't find a valid getting started PDF document
gnome-shell[2194]: Invalid result meta returned from search provider org.gnome.Nautilus.desktop

dbus-daemon[2161]: [session uid=1000 pid=2161] Activating service name='org.gnome.gedit' requested by ':1.10' (uid=1000 pid=2194)
dbus-daemon[2161]: [session uid=1000 pid=2161] Successfully activated service 'org.gnome.gedit'

gnome-shell[2194]: Object Clutter.Clone (0x55c845c587a0), has been already finalized. Impossible to get any property from it.

org.gnome.Shell.desktop[2194]: == Stack trace for context 0x55c83e298000 ==
org.gnome.Shell.desktop[2194]: #0 0x7ffd617de340 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7fc8240ddef0 @ 9)
org.gnome.Shell.desktop[2194]: #1 0x7ffd617de3e0 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7fc8240df230 @ 36)
org.gnome.Shell.desktop[2194]: #2 0x7ffd617de480 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7fc8240df098 @ 52)
org.gnome.Shell.desktop[2194]: #3 0x7ffd617df020 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7fc8240e9cd0 @ 54)
org.gnome.Shell.desktop[2194]: #4 0x7ffd617df170 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7fc8240e9d58 @ 1626)
org.gnome.Shell.desktop[2194]: #5 0x7ffd617df220 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7fc8240e9de0 @ 100)
org.gnome.Shell.desktop[2194]: #6 0x7ffd617df2b0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7fc8240e9e68 @ 10)
org.gnome.Shell.desktop[2194]: #7 0x7ffd617df330 I resource:///org/gnome/gjs/modules/signals.js:126 (0x7fc8240e2b38 @ 386)
org.gnome.Shell.desktop[2194]: #8 0x7ffd617df3e0 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7fc8240df808 @ 159)
org.gnome.Shell.desktop[2194]: #9 0x7ffd617df440 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8240c2bc0 @ 71)
org.gnome.Shell.desktop[2194]: #10 0x7ffd617df440 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7fc8240df780 @ 20)
org.gnome.Shell.desktop[2194]: #11 0x7ffd617df4d0 I self-hosted:917 (0x7fc8240ee5e8 @ 394)
Comment by Vlad (vlad3ciobanu) - Friday, 02 February 2018, 23:31 GMT
This is just getting worse... getting freezes every minute and ocasionally core dumps - tried both linux and lts kernels (the non-lts seems worse). I've pasted a new log of errors. I really don't know where to get help.
Comment by Adam (ZeroAdam) - Sunday, 04 February 2018, 13:05 GMT
This has been affecting my system for several days as well.
Comment by Vlad (vlad3ciobanu) - Sunday, 04 February 2018, 14:30 GMT
It may be unrelated - but maybe this info helps. I'm starting to think there's a problem problem with the open source AMD driver... I use amdgpu and have radeon blacklisted in modprobe.conf. I don't manually load any modules in mkinitcpio.conf. Actually, if I remember correctly, the problems started after I fixed this bug: (updated mesa from 17.2.6-1 to 17.3.0-2 and the firefox upon starting was unresponsive)

From lspci -k:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition]
Subsystem: Gigabyte Technology Co., Ltd Pitcairn XT [Radeon HD 7870 GHz Edition]
Kernel driver in use: amdgpu

From uname -r:

systemd-coredum: Process 1107 (Xwayland) of user 1000 dumped core.

Stack trace of thread 1107:
#0 0x00007fc96f3ee860 raise (
#1 0x00007fc96f3efec9 abort (
#2 0x0000562dfbe08c6a OsAbort (Xwayland)
#3 0x0000562dfbe0e783 n/a (Xwayland)
#4 0x0000562dfbe0f5a5 FatalError (Xwayland)
#5 0x0000562dfbc9abdf n/a (Xwayland)
#6 0x0000562dfbe067e1 n/a (Xwayland)
#7 0x0000562dfbdff68b WaitForSomething (Xwayland)
#8 0x0000562dfbdcb493 n/a (Xwayland)
#9 0x0000562dfbdcf730 n/a (Xwayland)
#10 0x00007fc96f3daf4a __libc_start_main (
#11 0x0000562dfbc9a23a _start (Xwayland)

Stack trace of thread 1108:
#0 0x00007fc96f77e3bd pthread_cond_wait@@GLIBC_2.3.2 (
#1 0x00007fc96b2e5fec n/a (
#2 0x00007fc96b2e5ef8 n/a (
#3 0x00007fc96f77808c start_thread (
#4 0x00007fc96f4afe7f __clone (
Comment by Vlad (vlad3ciobanu) - Sunday, 04 February 2018, 14:44 GMT
Related to the gjs bug:

From Gnome Bugzilla:
"The fixes have been merged to gnome-shell 3.26 git branch and will land in the next release, 3.26.3."

I will stop posting here and try to find another solution for my amdgpu / radeon problem. Thank you for your patience!
Comment by Anel (anelge) - Tuesday, 20 February 2018, 16:32 GMT