RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2170067 - [gnome-shell-extensions] Gnome-shell crash
Summary: [gnome-shell-extensions] Gnome-shell crash
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-shell-extensions
Version: 9.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Michael Boisvert
URL:
Whiteboard:
Depends On: 2170044
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-15 15:01 UTC by Tomas Popela
Modified: 2023-05-09 09:02 UTC (History)
7 users (show)

Fixed In Version: gnome-shell-extensions-40.7-7.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2170044
Environment:
Last Closed: 2023-05-09 07:46:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-148746 0 None None None 2023-02-15 15:02:51 UTC
Red Hat Product Errata RHBA-2023:2328 0 None None None 2023-05-09 07:46:38 UTC

Description Tomas Popela 2023-02-15 15:01:27 UTC 
+++ This bug was initially created as a clone of Bug #2170044 +++

User has this backtrace:

#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007fc2ac21e5b3 in __pthread_kill_internal (signo=11, threadid=<optimized out>) at pthread_kill.c:78
#2  0x00007fc2ac1d1ce6 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x0000560d8b49a242 in dump_gjs_stack_on_signal_handler (signo=11) at ../src/main.c:357
#4  <signal handler called>
#5  std::__uniq_ptr_impl<JS::PersistentRooted<JSFunction*>, std::default_delete<JS::PersistentRooted<JSFunction*> > >::_M_ptr (this=0x18)
    at /usr/include/c++/11/bits/unique_ptr.h:173
#6  std::unique_ptr<JS::PersistentRooted<JSFunction*>, std::default_delete<JS::PersistentRooted<JSFunction*> > >::get (this=0x18)
    at /usr/include/c++/11/bits/unique_ptr.h:422
#7  std::unique_ptr<JS::PersistentRooted<JSFunction*>, std::default_delete<JS::PersistentRooted<JSFunction*> > >::operator bool (this=0x18)
    at /usr/include/c++/11/bits/unique_ptr.h:436
#8  GjsMaybeOwned<JSFunction*>::get (this=0x10) at ../gjs/jsapi-util-root.h:181
#9  GjsMaybeOwned<JSObject*>::operator JSObject* const (this=0x10) at ../gjs/jsapi-util-root.h:183
#10 ObjectInstance::wrapper (this=0x0) at ../gi/object.h:337
#11 gjs_object_set_gproperty (object=<optimized out>, property_id=<optimized out>, value=0x7ffff3322620, pspec=0x560d8f04d650) at ../gi/gobject.cpp:176
#12 0x00007fc2ad1ba936 in object_set_property (object=object@entry=0x560d8f25a440, pspec=0x560d8f04d650, value=value@entry=0x7ffff33226f0, 
    nqueue=nqueue@entry=0x560d8ddf6650) at ../gobject/gobject.c:1565

The problem is in frame 11:

(gdb) f 11
#11 gjs_object_set_gproperty (object=<optimized out>, property_id=<optimized out>, value=0x7ffff3322620, pspec=0x560d8f04d650) at ../gi/gobject.cpp:176
176         JS::RootedObject js_obj(cx, priv->wrapper());
(gdb) p priv
$6 = (ObjectInstance *) 0x0

  Checking for user environment and possible reproducer, this reproducer was found:

1. Login as any user choosing GNOME Classic in gdm prompt
2. As root run 'authselect apply-changes'

  User was told to use 'GNOME Standard', but almost certain will loose features as
user is also using gnome-shell-extension-desktop-icons

--- Additional comment from Florian Müllner on 2023-02-15 14:55:07 UTC ---

This looks like https://gitlab.gnome.org/GNOME/gjs/-/issues/510 (avoid crashing under these circumstances) and https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/416 (window-list extension handling all settings changing all at once (due to `dconf update`).

It probably makes sense to include both fixes, but as they happened in different components, I reckon we'll need to separate bugs.

--- Additional comment from Tomas Popela on 2023-02-15 15:00:07 UTC ---

(In reply to Florian Müllner from comment #1)
> It probably makes sense to include both fixes, but as they happened in
> different components, I reckon we'll need to separate bugs.

Let me change the component for this bug to gjs and copy the bug for gnome-shell-extensions.
Comment 1 Michael Boisvert 2023-02-16 16:50:23 UTC 
Using gnome-shell-extensions-40.7-7.el9, there is no longer a crash and the following message is displayed: Changes were successfully applied.
Comment 7 errata-xmlrpc 2023-05-09 07:46:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnome-shell-extensions bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2328
Note You need to log in before you can comment on or make changes to this bug.