After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791056 - crash (SIGSEGV) when unlocking screen
crash (SIGSEGV) when unlocking screen
Status: RESOLVED DUPLICATE of bug 788931
Product: gnome-shell
Classification: Core
Component: general
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
Depends on:
Reported: 2017-12-01 04:46 UTC by Paul Wise
Modified: 2017-12-01 18:43 UTC
See Also:
GNOME target: ---
GNOME version: 3.25/3.26

gdb backtrace of the crash (55.02 KB, text/plain)
2017-12-01 04:46 UTC, Paul Wise

Description Paul Wise 2017-12-01 04:46:44 UTC
Created attachment 364714 [details]
gdb backtrace of the crash

I get a crash (SIGSEGV) in gnome-shell whenever I unlock the screen. I am using gnome-shell 3.26.2-1, Xorg 2:1.19.5-1 and GNOME 3.26 on Debian buster. If the below gdb backtrace and the attached full gdb backtrace isn't useful, please close this bug.

Core was generated by `gnome-shell --replace'.
Program terminated with signal SIGSEGV, Segmentation fault.
  • #0 g_type_check_instance_cast
    at ../../../../gobject/gtype.c line 4057
  • #0 g_type_check_instance_cast
    at ../../../../gobject/gtype.c line 4057
  • #1 st_label_set_text
    at ../src/st/st-label.c line 331
  • #2 object_set_property
    at ../../../../gobject/gobject.c line 1439
  • #3 g_object_setv
    at ../../../../gobject/gobject.c line 2245
  • #4 g_object_set_property
    at ../../../../gobject/gobject.c line 2529
  • #5 set_g_param_from_prop
    at gi/object.cpp line 446
  • #6 object_instance_set_prop(JSContext*, JS::HandleObject, JS::HandleId, JS::MutableHandleValue, JS::ObjectOpResult&)
    at gi/object.cpp line 521
  • #7 js::CallJSSetterOp(JSContext*, bool (*)(JSContext*, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::MutableHandle<JS::Value>, JS::ObjectOpResult&), JS::Handle<JSObject*>, JS::Handle<jsid>, JS::MutableHandle<JS::Value>, JS::ObjectOpResult&)
    at ./js/src/jscntxtinlines.h line 323
  • #8 NativeSetExistingDataProperty(JSContext*, js::HandleNativeObject, js::HandleShape, JS::HandleValue, JS::ObjectOpResult&)
    at ./js/src/vm/NativeObject.cpp line 2198
  • #9 SetExistingProperty
    at ./js/src/vm/NativeObject.cpp line 2406
  • #10 js::NativeSetProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::QualifiedBool, JS::ObjectOpResult&)
    at ./js/src/vm/NativeObject.cpp line 2469
  • #11 js::SetProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::ObjectOpResult&)
    at ./js/src/vm/NativeObject.h line 1540
  • #12 js::jit::DoSetPropFallback(JSContext*, js::jit::BaselineFrame*, js::jit::ICSetProp_Fallback*, JS::HandleValue, JS::HandleValue, JS::MutableHandleValue)
    at ./js/src/jit/BaselineIC.cpp line 4584
  • #13 0x00001eabec296c06 in
  • #14 0x0000000000000000 in

Comment 1 Paul Wise 2017-12-01 05:34:13 UTC
A workaround for this crash appears to be to run `loginctl unlock-session` from a virtual console instead of unlocking the screen.
Comment 2 Florian Müllner 2017-12-01 18:43:54 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 788931 ***