Bug#1050547: GNOME crashes with white screen after boot up
Hor Jiun Shyong
jiunshyong at gmail.com
Sun Sep 24 04:22:36 BST 2023
Hi,
After updating the below packages yesterday, the GDM3 white screen issue
returns. I have tried with reinstalling gnome-shell but it error still
persists. I have performed a backtrace with debugging symbols. Results are
as below. Thanks.
Start-Date: 2023-09-23 17:10:36
Commandline: apt-get dist-upgrade -V
Upgrade: gnome-text-editor:amd64 (45~beta-2, 45.0-1), libcups2:amd64
(2.4.2-5, 2.4.2-6), tecla:amd64 (45~rc-1, 45.0-1), gnome-user-docs:amd64
(44.3-2, 45.0-1), liferea:amd64 (1.15.2-1,
1.15.3-1),mutter-common-bin:amd64 (44.4-2, 44.5-1), eog:amd64 (45~rc-1,
45.0-1), libglib2.0-bin:amd64 (2.78.0-1, 2.78.0-2), cups-common:amd64
(2.4.2-5, 2.4.2-6), liferea-data:amd64 (1.15.2-1, 1.15.3-1), libgdm1:amd64
(45~beta-1, 45.0.1-1), libmutter-12-0:amd64 (44.4-2, 44.5-1),
cups-client:amd64 (2.4.2-5, 2.4.2-6), cups-ppdc:amd64 (2.4.2-5, 2.4.2-6),
cups-daemon:amd64 (2.4.2-5, 2.4.2-6), libshumate-common:amd64 (1.1~rc-1,
1.1.0-1), mutter-common:amd64 (44.4-2, 44.5-1), libglib2.0-data:amd64
(2.78.0-1, 2.78.0-2), gnome-calendar:amd64 (45~rc-1, 45.0-1),
libshumate-1.0-1:amd64 (1.1~rc-1, 1.1.0-1), cups-ipp-utils:amd64 (2.4.2-5,
2.4.2-6), gdm3:amd64 (45~beta-1, 45.0.1-1), gir1.2-mutter-12:amd64
(44.4-2, 44.5-1), gir1.2-shumate-1.0:amd64 (1.1~rc-1, 1.1.0-1),
gnome-music:amd64 (44.0-2, 45.0-1), gir1.2-gdm-1.0:amd64 (45~beta-1,
45.0.1-1), bash-completion:amd64 (1:2.11-7, 1:2.11-8), libglib2.0-0:amd64
(2.78.0-1, 2.78.0-2), cups-core-drivers:amd64 (2.4.2-5, 2.4.2-6),
gnome-characters:amd64 (45~alpha-2, 45.0-1), cups:amd64 (2.4.2-5, 2.4.2-6),
sysvinit-utils:amd64 (3.07-1, 3.08-1), libqt5designer5:amd64 (5.15.10-3,
5.15.10-5), cups-server-common:amd64 (2.4.2-5, 2.4.2-6), gnome-clocks:amd64
(44.0-2, 45.0-1), libqt5help5:amd64 (5.15.10-3, 5.15.10-5)
End-Date: 2023-09-23 17:11:29
*Backtrace*
Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2513
Download failed: Invalid argument. Continuing without source file
./obj-x86_64-linux-gnu/../src/core/display.c.
2513 ../src/core/display.c: No such file or directory.
[Current thread is 1 (Thread 0x7fb206184e00 (LWP 1761))]
(gdb) bt
#0 meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2513
#1 0x00007fb20aaf9b3b in meta_cursor_sprite_xfixes_initable_init
(initable=0x55724b0cd7c0, cancellable=<optimized out>, error=0x7ffc13ebd0b0)
at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:134
#2 0x00007fb20b26d3d3 in g_initable_new_valist (object_type=<optimized
out>, first_property_name=0x7fb20abafb8e "display",
var_args=var_args at entry=0x7ffc13ebcfa0,
cancellable=cancellable at entry=0x0, error=error at entry=0x7ffc13ebd0b0) at
../../../gio/ginitable.c:250
#3 0x00007fb20b26d4bd in g_initable_new (object_type=<optimized out>,
cancellable=cancellable at entry=0x0, error=error at entry=0x7ffc13ebd0b0,
first_property_name=first_property_name at entry=0x7fb20abafb8e "display")
at ../../../gio/ginitable.c:164
#4 0x00007fb20aaf9eda in meta_cursor_sprite_xfixes_new (display=0x0,
cursor_tracker=cursor_tracker at entry=0x557249ae82c0, error=error at entry
=0x7ffc13ebd0b0)
at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:110
#5 0x00007fb20aafd6ee in ensure_xfixes_cursor
(tracker_x11=tracker_x11 at entry=0x557249ae82c0) at
../src/backends/x11/meta-cursor-tracker-x11.c:94
#6 0x00007fb20aafd74d in meta_cursor_tracker_x11_get_sprite
(tracker=0x557249ae82c0) at
../src/backends/x11/meta-cursor-tracker-x11.c:162
#7 0x00007fb20aa8b05e in meta_cursor_tracker_get_sprite
(tracker=<optimized out>) at ../src/backends/meta-cursor-tracker.c:365
#8 0x00007fb20a0bbf7a in ffi_call_unix64 () at ../src/x86/unix64.S:104
#9 0x00007fb20a0bb40e in ffi_call_int (cif=cif at entry=0x55724ad81410,
fn=fn at entry=0x7fb20aa8b050 <meta_cursor_tracker_get_sprite>,
rvalue=<optimized out>,
rvalue at entry=0x7ffc13ebd2e8, avalue=<optimized out>,
closure=closure at entry=0x0) at ../src/x86/ffi64.c:673
#10 0x00007fb20a0bbb0d in ffi_call (cif=0x55724ad81410, fn=0x7fb20aa8b050
<meta_cursor_tracker_get_sprite>, rvalue=0x7ffc13ebd2e8, avalue=<optimized
out>)
at ../src/x86/ffi64.c:710
#11 0x00007fb20af01fa7 in Gjs::Function::invoke (this=<optimized out>,
context=0x55724a2f63e0, args=..., this_obj=..., r_value=<optimized out>)
at ./obj-x86_64-linux-gnu/../gi/function.cpp:1048
#12 0x00007fb20af02698 in Gjs::Function::call (context=0x55724a2f63e0,
js_argc=<optimized out>, vp=<optimized out>) at
./obj-x86_64-linux-gnu/../gi/function.cpp:1228
#13 0x00007fb208196650 in CallJSNative (args=...,
reason=js::CallReason::Call, native=0x7fb20af025b0
<Gjs::Function::call(JSContext*, unsigned int, JS::Value*)>,
cx=0x55724a2f63e0) at ./js/src/vm/Interpreter.cpp:420
#14 js::InternalCallOrConstruct (cx=0x55724a2f63e0, args=...,
construct=<optimized out>, reason=js::CallReason::Call) at
./js/src/vm/Interpreter.cpp:493
#15 0x00007fb208189d97 in InternalCall (reason=<optimized out>, args=...,
cx=<optimized out>) at ./js/src/vm/Interpreter.cpp:574
#16 js::CallFromStack (args=..., cx=<optimized out>) at
./js/src/vm/Interpreter.cpp:578
#17 Interpret (cx=0x55724a2f63e0, state=...) at
./js/src/vm/Interpreter.cpp:3314
#18 0x00007fb208195d6d in js::RunScript (cx=cx at entry=0x55724a2f63e0,
state=...) at ./js/src/vm/Interpreter.cpp:389
#19 0x00007fb2081981e9 in js::ExecuteKernel (result=..., evalInFrame=...,
envChainArg=..., script=..., cx=0x55724a2f63e0) at
./js/src/vm/Interpreter.cpp:781
#20 js::Execute (cx=0x55724a2f63e0, script=script at entry=...,
envChain=envChain at entry=..., rval=...) at ./js/src/vm/Interpreter.cpp:813
#21 0x00007fb2081f2148 in js::ModuleObject::execute (cx=<optimized out>,
self=self at entry=..., rval=...) at ./js/src/builtin/ModuleObject.cpp:1249
#22 0x00007fb2083631e4 in intrinsic_ExecuteModule (cx=<optimized out>,
argc=<optimized out>, vp=<optimized out>) at
./js/src/vm/SelfHosting.cpp:1891
#23 0x00002b78f24f94e0 in ?? ()
#24 0x00002b78f24f55e8 in ?? ()
#25 0x00007ffc13ebdbd0 in ?? ()
#26 0x0000000000000000 in ?? ()
Regards,
Hor Jiun Shyong 何俊雄
Hor Jiun Shyong <jiunshyong at gmail.com> 于2023年9月11日周一 08:22写道：
> Hi,
>
> >>DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb
> Partial output as below and full output as per link. Thanks.
>
>
> https://drive.google.com/file/d/19pahjyQSf_PRw-zQDwtC9FWRPcGQvUfo/view?usp=sharing
>
>
> # DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb
> PID: 1720 (gnome-shell)
> UID: 117 (Debian-gdm)
> GID: 122 (Debian-gdm)
> Signal: 11 (SEGV)
> Timestamp: Sat 2023-09-09 19:13:27 +08 (1 day 12h ago)
> Command Line: /usr/bin/gnome-shell
> Executable: /usr/bin/gnome-shell
> Control Group: /user.slice/user-117.slice/session-c1.scope
> Unit: session-c1.scope
> Slice: user-117.slice
> Session: c1
> Owner UID: 117 (Debian-gdm)
> Boot ID: db5045b3be454eabaf40ab7634cdd15f
> Machine ID: e2ff68e6a046472b82838d16f35a6e1f
> Hostname: meixian
> Storage:
> /var/lib/systemd/coredump/core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst
> (present)
> Size on Disk: 6.4M
> Message: Process 1720 (gnome-shell) of user 117 dumped core.
>
> Module libudev.so.1 from deb systemd-254.1-2.amd64
> Module libsystemd.so.0 from deb systemd-254.1-2.amd64
> Stack trace of thread 1720:
> #0 0x00007f9e956ced54 meta_display_get_x11_display
> (libmutter-12.so.0 + 0xced54)
> #1 0x00007f9e956f9a3b n/a (libmutter-12.so.0 + 0xf9a3b)
> #2 0x00007f9e95e95f8f g_initable_new_valist
> (libgio-2.0.so.0 + 0x7df8f)
> #3 0x00007f9e95e96069 g_initable_new (libgio-2.0.so.0 +
> 0x7e069)
> #4 0x00007f9e956f9dda n/a (libmutter-12.so.0 + 0xf9dda)
> #5 0x00007f9e956fd5ce n/a (libmutter-12.so.0 + 0xfd5ce)
> #6 0x00007f9e956fd62d n/a (libmutter-12.so.0 + 0xfd62d)
> #7 0x00007f9e9568b04e meta_cursor_tracker_get_sprite
> (libmutter-12.so.0 + 0x8b04e)
> #8 0x00007f9e94d4cf7a n/a (libffi.so.8 + 0x6f7a)
> #9 0x00007f9e94d4c40e n/a (libffi.so.8 + 0x640e)
> #10 0x00007f9e94d4cb0d ffi_call (libffi.so.8 + 0x6b0d)
>
>
> Regards,
> Hor Jiun Shyong 何俊雄
>
>
>
> Simon McVittie <smcv at debian.org> 于2023年9月11日周一 01:40写道：
>
>> On Sat, 09 Sep 2023 at 12:40:53 +0800, Hor Jiun Shyong wrote:
>> > coredumpctl_gdb.txt.gz
>>
>> The relevant part is:
>>
>> #0 0x00007f9e956ced54 in meta_display_get_x11_display () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #1 0x00007f9e956f9a3b in ?? () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #2 0x00007f9e95e95f8f in g_initable_new_valist () from
>> /lib/x86_64-linux-gnu/libgio-2.0.so.0
>> #3 0x00007f9e95e96069 in g_initable_new () from
>> /lib/x86_64-linux-gnu/libgio-2.0.so.0
>> #4 0x00007f9e956f9dda in ?? () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #5 0x00007f9e956fd5ce in ?? () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #6 0x00007f9e956fd62d in ?? () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #7 0x00007f9e9568b04e in meta_cursor_tracker_get_sprite () from
>> /lib/x86_64-linux-gnu/libmutter-12.so.0
>> #8 0x00007f9e94d4cf7a in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
>>
>> but this is of limited usefulness since you don't have debug symbols for
>> mutter available.
>>
>> The easiest way to get the debug symbols is to use:
>>
>> DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb
>>
>> and type "bt" at the (gdb) prompt when the symbols have finished
>> downloading.
>>
>> Or you could enable the debug symbols apt repository (see
>>
>> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
>> )
>> and install the libmutter-12-0-dbgsym package. We don't need any other
>> packages for this particular crash.
>>
>> >
>> core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst.gz
>>
>> In general we can't get a useful backtrace from the actual compressed
>> core dump: that's something that the bug reporter needs to do. I tried to
>> get a useful backtrace from this with debug symbols, but it doesn't match
>> the result you sent and I'm not sure whether it really makes sense.
>>
>> Sharing these core dumps is also a privacy risk because they can contain
>> private information, although in this case the crash was from the gdm
>> login screen before you had a chance to enter any passwords, so it's
>> probably harmless.
>>
>> smcv
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20230924/fd26d926/attachment-0001.htm>
More information about the pkg-gnome-maintainers
mailing list