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 2130131 - GUI session going blank/black and coming up, blackout time random - gnome-shell crashing at issue timestamp
Summary: GUI session going blank/black and coming up, blackout time random - gnome-she...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell
Version: 8.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Michael Boisvert
URL:
Whiteboard: OtherQA
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-27 09:53 UTC by Vishal Pakolu
Modified: 2023-09-19 04:27 UTC (History)
6 users (show)

Fixed In Version: gnome-shell-3.32.2-49.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:37:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:
vrajput: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-134990 0 None None None 2022-09-27 10:02:00 UTC
Red Hat Product Errata RHBA-2023:2841 0 None None None 2023-05-16 08:37:50 UTC

Description Vishal Pakolu 2022-09-27 09:53:54 UTC 
Description of problem:

Randomly observing screen going blank and coming up, the time for blackout is also random.

gnome-shell crash observed at issue time-stamps :

~~~
Sep  7 11:35:30 localhost systemd-coredump[7840]: Resource limits disable core dumping for process 6849 (gnome-shell).
Sep  7 11:35:30 localhost systemd-coredump[7840]: Process 6849 (gnome-shell) of user 0 dumped core.
Sep  7 11:35:30 localhost systemd[1]: systemd-coredump: Succeeded.
Sep  7 11:35:30 localhost gnome-session[2067]: gnome-session-binary[2067]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep  7 11:35:30 localhost gnome-session-binary[2067]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep  7 11:35:30 localhost /usr/libexec/gdm-x-session[1778]: (II) modeset(0): EDID vendor "NXP", prod id 13408
~~~

~~~
$ file 0030-core.gnome-shell.0.3bb3ab507cf64d66980fe10e639be602.2161.1662702623000000 
0030-core.gnome-shell.0.3bb3ab507cf64d66980fe10e639be602.2161.1662702623000000: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/gnome-shell', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/bin/gnome-shell', platform: 'x86_64'
~~~

Following backtrace generated from gnome-shell crash :

~~~
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50        return ret;
[Current thread is 1 (Thread 0x7fc04c0c2500 (LWP 2161))]
(gdb) bt
#0  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x000056493de04c43 in dump_gjs_stack_on_signal_handler (signo=6) at ../src/main.c:347
#2  <signal handler called>
#3  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#4  0x00007fc0491f8db5 in __GI_abort () at abort.c:79
#5  0x00007fc04b18d123 in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7fc048dbaf88 <__func__.70354> "st_bin_destroy", message=<optimized out>)
    at gtestutils.c:2533
#6  0x00007fc04b1e620e in g_assertion_message_expr (domain=domain@entry=0x7fc048dbab34 "St", file=file@entry=0x7fc048dbadfb "../src/st/st-bin.c", line=line@entry=186, 
    func=func@entry=0x7fc048dbaf88 <__func__.70354> "st_bin_destroy", expr=expr@entry=0x7fc048dbade7 "priv->child == NULL") at gtestutils.c:2556
#7  0x00007fc048d90b30 in st_bin_destroy (actor=0x56494067d680) at ../src/st/st-bin.c:186
#8  st_bin_destroy (actor=0x56494067d680) at ../src/st/st-bin.c:180
#9  0x00007fc04b49a3bd in g_closure_invoke (closure=0x56493e459140, return_value=0x0, n_param_values=1, param_values=0x7ffd4cc86920, invocation_hint=0x7ffd4cc868a0) at gclosure.c:804
#10 0x00007fc04b4adc56 in signal_emit_unlocked_R (node=node@entry=0x56493e46f2e0, detail=detail@entry=0, instance=instance@entry=0x56494067d680, emission_return=emission_return@entry=0x0, 
    instance_and_params=instance_and_params@entry=0x7ffd4cc86920) at gsignal.c:3550
#11 0x00007fc04b4b6a56 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffd4cc86ae0) at gsignal.c:3392
#12 0x00007fc04b4b7093 in g_signal_emit (instance=instance@entry=0x56494067d680, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3448
#13 0x00007fc049de894a in clutter_actor_dispose (object=0x56494067d680) at ../clutter/clutter/clutter-actor.c:6065
#14 0x00007fc048db587c in st_widget_dispose (gobject=0x56494067d680) at ../src/st/st-widget.c:328
#15 0x00007fc04b49f828 in g_object_unref (_object=<optimized out>) at gobject.c:3303
#16 g_object_unref (_object=0x56494067d680) at gobject.c:3232
#17 0x00007fc04a15b180 in ObjectInstance::release_native_object (this=this@entry=0x564941f2c5e0) at gi/object.cpp:1247
#18 0x00007fc04a15d8dd in ObjectInstance::disassociate_js_gobject (this=0x564941f2c5e0) at gi/object.cpp:1426
#19 ObjectInstance::disassociate_js_gobject (this=0x564941f2c5e0) at gi/object.cpp:1405
#20 0x00007fc04a15bcfc in std::function<void (ObjectInstance*)>::operator()(ObjectInstance*) const (__args#0=<optimized out>, this=0x7ffd4cc86d20) at /usr/include/c++/8/bits/std_function.h:682
#21 ObjectInstance::remove_wrapped_gobjects_if(std::function<bool (ObjectInstance*)>, std::function<void (ObjectInstance*)>) (predicate=..., action=...) at gi/object.cpp:1061
#22 0x00007fc04a15bdd8 in update_heap_wrapper_weak_pointers (cx=<optimized out>, compartment=<optimized out>, data=<optimized out>) at /usr/include/c++/8/new:169
#23 0x00007fc04185a99a in js::gc::GCRuntime::callWeakPointerCompartmentCallbacks (comp=0x56493e573050, this=0x56493e560708) at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/dist/include/mozilla/ThreadLocal.h:199
#24 js::gc::GCRuntime::beginSweepingSweepGroup (this=0x56493e560708, fop=<optimized out>, budget=...) at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/gc/GC.cpp:5054
#25 0x00007fc041833224 in sweepaction::SweepActionSequence<js::gc::GCRuntime*, js::FreeOp*, js::SliceBudget&>::run (this=0x56493e4f57f0, args#0=0x56493e560708, args#1=0x7ffd4cc87090, args#2=...)
    at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/dist/include/mozilla/UniquePtr.h:307
#26 0x00007fc04183e5da in sweepaction::SweepActionRepeatFor<js::gc::SweepGroupsIter, JSRuntime*, js::gc::GCRuntime*, js::FreeOp*, js::SliceBudget&>::run (this=0x56493e4f6ba0, args#0=0x56493e560708, 
    args#1=0x7ffd4cc87090, args#2=...) at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/dist/include/mozilla/UniquePtr.h:307
#27 0x00007fc04183f109 in js::gc::GCRuntime::performSweepActions (this=this@entry=0x56493e560708, budget=...) at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/dist/include/mozilla/UniquePtr.h:307
#28 0x00007fc041862523 in js::gc::GCRuntime::incrementalCollectSlice (this=this@entry=0x56493e560708, budget=..., reason=reason@entry=JS::gcreason::API, session=...)
    at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/gc/GC.cpp:6378
#29 0x00007fc0418634cc in js::gc::GCRuntime::gcCycle (this=this@entry=0x56493e560708, nonincrementalByAPI=nonincrementalByAPI@entry=true, budget=..., reason=reason@entry=JS::gcreason::API)
    at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/gc/GC.cpp:6685
#30 0x00007fc0418639a8 in js::gc::GCRuntime::collect (this=this@entry=0x56493e560708, nonincrementalByAPI=nonincrementalByAPI@entry=true, budget=..., reason=reason@entry=JS::gcreason::API)
    at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/gc/GC.cpp:6808
#31 0x00007fc041863b2f in js::gc::GCRuntime::gc (this=0x56493e560708, gckind=gckind@entry=GC_NORMAL, reason=reason@entry=JS::gcreason::API)
    at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/dist/include/js/SliceBudget.h:58
#32 0x00007fc04154d272 in JS_GC (cx=<optimized out>) at /usr/src/debug/mozjs60-60.9.0-4.el8.x86_64/vm/JSContext.h:293
#33 0x00007fc04a174be1 in GjsContextPrivate::trigger_gc_if_needed (data=data@entry=0x56493e55e100) at gjs/context.cpp:579
#34 0x00007fc04b1bf411 in g_timeout_dispatch (source=0x564941ed0a00, callback=0x7fc04a174bc0 <GjsContextPrivate::trigger_gc_if_needed(void*)>, user_data=0x56493e55e100) at gmain.c:4694
#35 0x00007fc04b1be95d in g_main_dispatch (context=0x56493e1f6530) at gmain.c:3193
#36 g_main_context_dispatch (context=context@entry=0x56493e1f6530) at gmain.c:3873
#37 0x00007fc04b1bed18 in g_main_context_iterate (context=0x56493e1f6530, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3946
#38 0x00007fc04b1bf042 in g_main_loop_run (loop=0x56493e4c3340) at gmain.c:4142
#39 0x00007fc049651ac0 in meta_run () at ../src/core/main.c:685
#40 0x000056493de0456f in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:503
~~~

Issue does not persist over wayland session, just Xsession affected. 

Version-Release number of selected component (if applicable):
gnome-shell-3.32.2-44.el8.x86_64
redhat-release-8.6-0.1.el8.x86_64


How reproducible:
 Issue not reproducible on demand, happens randomly

Actual results:
Screen blinking / blacking out randomly and coming back. 

Expected results:

Screen should not black out. 

Additional info:

Following bugs are probably relevant :
https://www.mail-archive.com/desktop-bugs@lists.ubuntu.com/msg768819.html
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867763
Comment 1 Tomas Popela 2022-09-27 10:43:57 UTC 
Are there any GNOME Shell extensions enabled? If so, can the customer disable them and try again? If it will help, then can they selectively enable the extensions one by one and identify the one that is causing the crashes?
Comment 2 Vishal Pakolu 2022-09-30 07:21:14 UTC 
Hello Tomas,

Checking this with customer, they have few extensions enabled like 'No hot corner', 'Screen shield disable', 'Onscreen keyboard'. They will need some time to test this, will get back as soon as we have updates. 

--
Regards,
Vishal Pakolu
Comment 3 Florian Müllner 2022-10-19 13:38:48 UTC 
(In reply to Vishal Pakolu from comment #0)
> #4  0x00007fc0491f8db5 in __GI_abort () at abort.c:79
> #5  0x00007fc04b18d123 in g_assertion_message (domain=<optimized out>,
> file=<optimized out>, line=<optimized out>, func=0x7fc048dbaf88
> <__func__.70354> "st_bin_destroy", message=<optimized out>)
>     at gtestutils.c:2533
> #6  0x00007fc04b1e620e in g_assertion_message_expr
> (domain=domain@entry=0x7fc048dbab34 "St", file=file@entry=0x7fc048dbadfb
> "../src/st/st-bin.c", line=line@entry=186, 
>     func=func@entry=0x7fc048dbaf88 <__func__.70354> "st_bin_destroy",
> expr=expr@entry=0x7fc048dbade7 "priv->child == NULL") at gtestutils.c:2556
> #7  0x00007fc048d90b30 in st_bin_destroy (actor=0x56494067d680) at
> ../src/st/st-bin.c:186

That should be https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1507.
Comment 4 Vishal Pakolu 2022-10-27 04:05:03 UTC 
Hello,

We yet await response from customer on 'GNOME Shell extensions' test stated in comment #1. 
For now we know that they have few extensions enabled like 'No hot corner', 'Screen shield disable', 'Onscreen keyboard' and they will try and identify the one that is causing the crash.
I am following-up again, will update here as soon as we have further leads. 

--
Regards,
Vishal Pakolu
Comment 6 VIRENDRASINGH RAJPUT 2022-11-11 01:00:29 UTC 
Dear Team,

The customer has done testing, please see below response from the customer:

They are using the following extensions:

  1.  Onscreen keyboard
  2.  Screenshield disable extension
  3.  No hotcorner extension
  4.  Onscreen keyboard button extension.

They have disabled each extension one by one and tested the device. After disabling screenshield extension, it is always asking for a password even after the screen is locked. So not sure if this is working fine or not.

After disabling other extensions, there is no change in the behavior. The device still blinks.
Comment 9 Michael Boisvert 2022-11-29 15:37:44 UTC 
Could you please have the customer test the issue with the new gnome-shell located: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2270998
Comment 18 errata-xmlrpc 2023-05-16 08:37:43 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 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:2841
Comment 19 Red Hat Bugzilla 2023-09-19 04:27:07 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.