Closed ilmarn closed 3 years ago
Can confirm.
The wayland session will crash to gdm, which will then try to fall back to the x session. This then crashes with an "oh no. something went wrong" message on the white screen.
The Metacity Fallback session works. But if I try to start GDM by itself, GDM will also give me the "oh no" message.
Tried downgrading to 33720 with --force --picky
, but the whole thing is still borked. The gnome sessions do the exact same thing. Strangely though, GDM now works to allow me to get into the Fallback session without having to drop to an alternative tty.
Update 33740 failed to boot.
Downgrading to 33720 did work for me luckily.
Downgrading to 33720 did work for me luckily.
33720 did not work for me, but 33710 did. Go figure.
In either case, this is a pretty serious issue.
Same issue here. Haven't tried dowgrading yet.
looks like the core issue here is the gnome upgrade. switching to console and startx
gives me gnome 3.38 without any of my theming. May be some incompatible shell extensions and theming
sudo swupd autoupdate --disable sudo swupd repair -m 33710
shoulld work no?
sudo swupd autoupdate --enable after this is fixed.
also startx from commandline works.
gnome-tweaks # or any shell extension
WARNING : Shell not installed or running
WARNING : Error detecting shell
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/gtweak/tweaks/tweak_group_shell_extensions.py", line 217, in __init__
raise Exception("Shell not running or DBus service not available")
Exception: Shell not running or DBus service not available
WARNING : Shell not running
NoneType: None
sudo swupd repair -m 33710
sudo swupd repair -m 33710 --force
and probably also a good idea to have --picky
as well.
Would recommend first running
sudo swupd diagnose -m 33710
To see what changes will be made example output (abbreviated):
-> Missing file: /usr/lib/modules/5.8.9-986.native/kernel/sound/pci/echoaudio/snd-indigoiox.ko
...
...
-> Hash mismatch for file: /usr/share/yelp-xsl/xslt/mallard/html/mal2html-page.xsl
[100%]
Inspected 495040 files
5371 files were missing
8316 files did not match
Use "swupd repair" to correct the problems in the system
Diagnose successful
Picky downgrade to 33720 worked for me.
sudo swupd autoupdate --disable
sudo swupd repair -m 33720 --picky
gjs dumped core with 33740
Comment/Close this issue when they push a working update. Thanks in advance.
@ahkok has anyone looked at this yet?
I got the crash screen from GDM, looks like the same issue?
I can see in the logs a segfault for Gnome Shell
[ 4.320669] gnome-shell[695]: segfault at 29a6000029ce ip 00007f5e4f386e98 sp 00007ffcf93fc4c0 error 6 cpu 3 in libgjs.so.0.0.0[7f5e4f353000+8e000] [ 6.042665] gnome-shell[948]: segfault at 3e ip 00007f45fa353e98 sp 00007fff3b717fa0 error 6 cpu 15 in libgjs.so.0.0.0[7f45fa320000+8e000]
GNOME 3.38 was integrated in release 33740, and this crash is certainly related to that update.
After initial investigation, I suspect that gjs 1.66.0 is not compatible with glib 2.66.0; some of its unit tests fail when built with glib 2.66.0 (but not with glib 2.64.5), and some of the test error messages are identical to the ones we are seeing at bootup beginning with release 33740. If I rebuild gjs with glib 2.64.5 as a build dependency, those errors disappear, and all unit tests pass. Similar unit test result improvements appear for gnome-shell when it is built with the rebuilt gjs in the environment.
I will do some testing on a live Clear Linux system tomorrow, and if my suspicion is correct, we will downgrade glib to 2.64.5 (and do any rebuilds, likely for gjs followed by gnome-shell at a minimum).
Testing should be done before any release on at least 20+ different hardware systems. We had several of these no-boot issues now with CL over the past months, you need to implement a proper release test plan to prevent such avoidable situations in the future ..
I tried the repair command but it also breaks other stuffs like: module for RTL8822BE USB wireless adapter can't be loaded, fonts rendering broke, USB DAC doesn't work. The good thing is this isn't a work machine.
I tried the repair command but it also breaks other stuffs like: module for RTL8822BE USB wireless adapter can't be loaded, fonts rendering broke, USB DAC doesn't work. The good thing is this isn't a work machine.
try swupd repair --picky
try swupd repair --picky
I tried the same commands in https://github.com/clearlinux/distribution/issues/2133#issuecomment-697991500
Yep. Same on two machines with wildly different setups (one Intel-only hw, one with Intel+NVIDIA) both borked, both work machines. This is a pretty critical issue.
Aren't the failing tests supposed to be a red flag for pushing this kind of stuff?
I tried the repair command but it also breaks other stuffs like: module for RTL8822BE USB wireless adapter can't be loaded, fonts rendering broke, USB DAC doesn't work. The good thing is this isn't a work machine.
@namm2 please check that you are still running the correct kernel uname -a
.
one of my systems switched to the lts kernel and had no networking either
@amonforstmann I'm using lts2019 kernel version 5.4.65
I checked the logs and it
I tried the repair command but it also breaks other stuffs like: module for RTL8822BE USB wireless adapter can't be loaded, fonts rendering broke, USB DAC doesn't work. The good thing is this isn't a work machine.
On the fonts issue, I checked the command's output and it looks like it removed a lot of files in /usr/lib
, /usr/lib64
, /usr/share
and more. But can't explain some kernel modules broke.
I am facing the exactly same issue and I can see that it has generated core dumps for 3 binaries. /usr/bin/Xwayland /user/bin/gnome-shell /usr/bin/gjs-console
also hit this. downgrade fixed it
33760 is working
swupd repair -V 33760 --picky
33760 still not booting on USB drive with Luks. I noticed when pressing e during boot, that the kernel version still is listed as 5.8.9-* and not 5.8.11-?? for 33760, so something is still broken ..
33760 is working
swupd repair -V 33760 --picky
sudo swupd check-update Password: Current OS version: 33760 Latest server version: 33740 Thanks nodanero.
33760 does indeed boot and load a desktop.
gnome-terminal (ctrl+alt+t) is still not working properly though... <-- gtk theme error
gnome-photos still dumps core
Sep 25 14:36:30 workstation-essen systemd-coredump[8899]: Process 8800 (gnome-photos) of user 1000 dumped core.
Stack trace of thread 8800:
#0 0x00007f8a25bc3fae n/a (libglib-2.0.so.0 + 0x86fae)
#1 0x00007f8a25bc40dc g_log_default_handler (libglib-2.0.so.0 + 0x870dc)
#2 0x00007f8a25bc9d28 g_logv (libglib-2.0.so.0 + 0x8cd28)
#3 0x00007f8a25bc9fd9 g_log (libglib-2.0.so.0 + 0x8cfd9)
#4 0x00007f8a25802beb n/a (libgio-2.0.so.0 + 0x14dbeb)
#5 0x00007f8a25cf5fdc n/a (libgobject-2.0.so.0 + 0x29fdc)
#6 0x00007f8a25cf71b4 g_object_new_valist (libgobject-2.0.so.0 + 0x2b1b4)
#7 0x00007f8a25cf7c1e g_object_new (libgobject-2.0.so.0 + 0x2bc1e)
#8 0x000056463bafdcac n/a (gnome-photos + 0xcbcac)
#9 0x000056463ba93a66 photos_base_manager_get_all_filter (gnome-photos + 0x61a66)
#10 0x000056463bae91da n/a (gnome-photos + 0xb71da)
#11 0x000056463bae9cb5 photos_query_builder_global_query (gnome-photos + 0xb7cb5)
#12 0x000056463bab7ed7 photos_fetch_ids_job_run (gnome-photos + 0x85ed7)
#13 0x000056463bae8438 n/a (gnome-photos + 0xb6438)
#14 0x00007f8a24370652 ffi_call_unix64 (libffi.so.6 + 0x7652)
#15 0x00007f8a2436fdf3 ffi_call (libffi.so.6 + 0x6df3)
#16 0x00007f8a25cea642 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x1e642)
#17 0x00007f8a25ce4a8c g_closure_invoke (libgobject-2.0.so.0 + 0x18a8c)
#18 0x00007f8a25d290b9 n/a (libgobject-2.0.so.0 + 0x5d0b9)
#19 0x000056463ba81938 n/a (gnome-photos + 0x4f938)
#20 0x00007f8a25846ad2 n/a (libgio-2.0.so.0 + 0x191ad2)
#21 0x00007f8a25821b26 n/a (libgio-2.0.so.0 + 0x16cb26)
#22 0x00007f8a25bbb63c g_main_context_dispatch (libglib-2.0.so.0 + 0x7e63c)
#23 0x00007f8a25c4574f n/a (libglib-2.0.so.0 + 0x10874f)
#24 0x00007f8a25bb9aba g_main_context_iteration (libglib-2.0.so.0 + 0x7caba)
#25 0x00007f8a257eca5d g_application_run (libgio-2.0.so.0 + 0x137a5d)
#26 0x000056463ba6deee main (gnome-photos + 0x3beee)
#27 0x00007f8a244ce51d __libc_start_main (libc.so.6 + 0x2a51d)
#28 0x000056463ba6e03e _start (gnome-photos + 0x3c03e)
Stack trace of thread 8870:
#0 0x00007f8a245c8b20 syscall (libc.so.6 + 0x124b20)
#1 0x00007f8a25c3e8c6 g_cond_wait (libglib-2.0.so.0 + 0x1018c6)
#2 0x00007f8a25a683eb n/a (libgegl-0.4.so.0 + 0x2a3eb)
#3 0x00007f8a25bf5d0e n/a (libglib-2.0.so.0 + 0xb8d0e)
#4 0x00007f8a2438081f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007f8a245ce963 __clone (libc.so.6 + 0x12a963)
33760 does indeed boot and load a desktop. gnome-terminal (ctrl+alt+t) is still not working properly though...
No problem here, starting gnome-terminal with ctrl+alt+t works properly.
No problem here, starting gnome-terminal with ctrl+alt+t works properly.
Indeed, switching to a different gtk style/theme resolved this.
Can confirm that the update to 33760 mostly fixes the shell. But I am also having some glitches with my non-standard theme: in my case, Arc.
Can confirm that the update to 33760 mostly fixes the shell. But I am also having some glitches with my non-standard theme: in my case, Arc.
@jumpinggoofballs Also check update for your theme.
Working now as of latest update.
Can confirm that the update to 33760 mostly fixes the shell. But I am also having some glitches with my non-standard theme: in my case, Arc.
@jumpinggoofballs Also check update for your theme.
The theme files are copied over from a flatpak installation of the theme (not available in the repo), and I think it hasn't been updated in any case since 3.22
But I don't see why a theme should give visual artefacting. I understand styling classes going awry and such, but the kind of artefacting that you get from buggy graphics drivers? Why would that have anything to do with a particular css theme?
@jumpinggoofballs
If you manually run flatpak update
in shell, it will report some runtime it installed as end-of-life or deprecated. For the new gnome, for example, the old icon theme for example is deprecated.
Also, gnome would disable extensions if it's not declared as compatible. For example, the popular dash-to-panel.
im closing it as its resolved in 33760 terminal issue can be resolved by swithing to adwaita theme or manually updating your current theme
im closing it as its resolved in 33760 terminal issue can be resolved by swithing to adwaita theme or manually updating your current theme
Is it safe to enable auto update after 33760?
im closing it as its resolved in 33760 terminal issue can be resolved by swithing to adwaita theme or manually updating your current theme
Is it safe to enable auto update after 33760?
only CL team knows :) personally i prefer to update manually after a day or two after release and checking issues on github
I am a little disappointed CL team not checking out updates more carefully this last 33740 update for me required a reinstall of Clear Linux with a disable of auto update I guess gnome desktop is not top priority for CL team. I think for me on my PC a usb bluetooth dongle I use was not handled properly by 33730 and then 33740 broke everything.
On Sat, Sep 26, 2020 at 11:07 AM ilmarn notifications@github.com wrote:
im closing it as its resolved in 33760 terminal issue can be resolved by swithing to adwaita theme or manually updating your current theme
Is it safe to enable auto update after 33760?
only CL team knows :) personally i prefer to update manually after a day or two after release and checking issues on github
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2133#issuecomment-699507557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJFGJRVX2TFEGZXKP4HRQILSHX7UJANCNFSM4RXKI4NA .
33760 did not fix my broken installation, followed all instructions given here. Result: another dead server which has to be reinstalled .. impressive !
33760 did not fix my broken installation, followed all instructions given here. Result: another dead server which has to be reinstalled .. impressive !
33760 worked perfectly on my PC??
update to 33760, problem persists, gnome-shell still crashes for me. Going back to 33710...
Sep 28 00:27:14 glorfindel systemd-coredump[1288]: Process 1269 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 1269:
#0 0x00007f6347756459 __GI_raise (libc.so.6 + 0x44459)
#1 0x0000557c12c53f21 dump_gjs_stack_on_signal_handler (gnome-shell + 0x2f21)
#2 0x00007f63477564f0 __restore_rt (libc.so.6 + 0x444f0)
#3 0x00007f6348644fae g_log_structured_array.part.0 (libglib-2.0.so.0 + 0x86fae)
#4 0x00007f63486450dc g_log_default_handler (libglib-2.0.so.0 + 0x870dc)
#5 0x0000557c12c53cbb default_log_handler (gnome-shell + 0x2cbb)
#6 0x00007f634864ad28 g_logv (libglib-2.0.so.0 + 0x8cd28)
#7 0x00007f634864afd9 g_log (libglib-2.0.so.0 + 0x8cfd9)
#8 0x00007f6347971374 meta_cursor_sprite_xcursor_realize_texture (libmutter-7.so.0 + 0x5f374)
#9 0x00007f634798f223 meta_cursor_renderer_x11_update_cursor (libmutter-7.so.0 + 0x7d223)
#10 0x00007f6347974c8c meta_cursor_renderer_update_cursor (libmutter-7.so.0 + 0x62c8c)
#11 0x00007f6347974e0f sync_cursor.lto_priv.0 (libmutter-7.so.0 + 0x62e0f)
#12 0x00007f6347974e63 meta_cursor_tracker_set_pointer_visible (libmutter-7.so.0 + 0x62e63)
#13 0x00007f6346c02652 ffi_call_unix64 (libffi.so.6 + 0x7652)
#14 0x00007f6346c01df3 ffi_call (libffi.so.6 + 0x6df3)
#15 0x00007f6347c07162 gjs_invoke_c_function (libgjs.so.0 + 0x3b162)
#16 0x00007f6347c07b91 function_call (libgjs.so.0 + 0x3bb91)
#17 0x00007f63447e9f83 _Z12CallJSNativeP9JSContextPFbS0_jPN2JS5ValueEEN2js10CallReasonERKNS1_8CallArgsE (libmozjs-78.so.0 + 0x17bf83)
#18 0x00007f63447da237 _ZN2js13CallFromStackEP9JSContextRKN2JS8CallArgsE (libmozjs-78.so.0 + 0x16c237)
#19 0x00007f63447e96de _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-78.so.0 + 0x17b6de)
#20 0x00007f63447ebe2b _ZN2js13ExecuteKernelEP9JSContextN2JS6HandleIP8JSScriptEENS3_IP8JSObjectEENS3_INS2_5ValueEEENS_16AbstractFramePtrENS2_13MutableHandleISA_EE (libmozjs-78.so.0 + 0x17de2b)
#21 0x00007f634493d7cf EvaluateSourceBuffer<char16_t> (libmozjs-78.so.0 + 0x2cf7cf)
#22 0x00007f634493d98f _ZN2JS8EvaluateEP9JSContextNS_6HandleINS_13StackGCVectorIP8JSObjectN2js15TempAllocPolicyEEEEERKNS_22ReadOnlyCompileOptionsERNS_10SourceTextIDsEENS_13MutableHandleINS_5ValueEEE (libmozjs-78.so.0 + 0x2cf98f)
#23 0x00007f6347c3ad21 _ZN17GjsContextPrivate15eval_with_scopeEN2JS6HandleIP8JSObjectEEPKclS6_NS0_13MutableHandleINS0_5ValueEEE (libgjs.so.0 + 0x6ed21)
#24 0x00007f6347c3ee73 gjs_context_eval (libgjs.so.0 + 0x72e73)
#25 0x00007f6348a6efb7 gnome_shell_plugin_start (libgnome-shell.so + 0x24fb7)
#26 0x00007f634799c674 meta_compositor_do_manage (libmutter-7.so.0 + 0x8a674)
#27 0x00007f63479bae58 meta_start (libmutter-7.so.0 + 0xa8e58)
#28 0x00007f63479bb094 meta_run (libmutter-7.so.0 + 0xa9094)
#29 0x0000557c12c538ae main (gnome-shell + 0x28ae)
#30 0x00007f634773c51d __libc_start_main (libc.so.6 + 0x2a51d)
#31 0x0000557c12c53ace _start (gnome-shell + 0x2ace)
Stack trace of thread 1272:
#0 0x00007f6329751c72 jsimd_idct_islow_avx2.columnDCT (libjpeg.so.62 + 0x85c72)
#1 0x00007f6329710fdb decompress_onepass (libjpeg.so.62 + 0x44fdb)
#2 0x00007f632970e741 process_data_simple_main (libjpeg.so.62 + 0x42741)
#3 0x00007f63296fdf5b jpeg_read_scanlines (libjpeg.so.62 + 0x31f5b)
#4 0x00007f6329922f73 gdk_pixbuf__jpeg_image_load_lines (libpixbufloader-jpeg.so + 0x2f73)
#5 0x00007f6329924c53 gdk_pixbuf__jpeg_image_load_increment (libpixbufloader-jpeg.so + 0x4c53)
#6 0x00007f63473a0975 load_from_stream (libgdk_pixbuf-2.0.so.0 + 0x14975)
#7 0x00007f63473a0d11 gdk_pixbuf_new_from_stream (libgdk_pixbuf-2.0.so.0 + 0x14d11)
#8 0x00007f6347996c75 load_file (libmutter-7.so.0 + 0x84c75)
#9 0x00007f63488b6711 g_task_thread_pool_thread (libgio-2.0.so.0 + 0xef711)
#10 0x00007f63486883ab g_thread_pool_thread_proxy (libglib-2.0.so.0 + 0xca3ab)
#11 0x00007f6348676d0e g_thread_proxy (libglib-2.0.so.0 + 0xb8d0e)
#12 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#13 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1275:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1274:
#0 0x00007f6347830742 __GI___poll (libc.so.6 + 0x11e742)
#1 0x00007f63486c66d8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x1086d8)
#2 0x00007f634863aaba g_main_context_iteration (libglib-2.0.so.0 + 0x7caba)
#3 0x00007f63411f453b dconf_gdbus_worker_thread (libdconfsettings.so + 0x653b)
#4 0x00007f6348676d0e g_thread_proxy (libglib-2.0.so.0 + 0xb8d0e)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1271:
#0 0x00007f6347830742 __GI___poll (libc.so.6 + 0x11e742)
#1 0x00007f63486c66d8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x1086d8)
#2 0x00007f634863b2bb glib_worker_main (libglib-2.0.so.0 + 0x7d2bb)
#3 0x00007f6348676d0e g_thread_proxy (libglib-2.0.so.0 + 0xb8d0e)
#4 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1276:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1273:
#0 0x00007f6347830742 __GI___poll (libc.so.6 + 0x11e742)
#1 0x00007f63486c66d8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x1086d8)
#2 0x00007f634863cec3 g_main_loop_run (libglib-2.0.so.0 + 0x7eec3)
#3 0x00007f63489442fe gdbus_shared_thread_func (libgio-2.0.so.0 + 0x17d2fe)
#4 0x00007f6348676d0e g_thread_proxy (libglib-2.0.so.0 + 0xb8d0e)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1278:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1281:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1279:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1277:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1282:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Stack trace of thread 1280:
#0 0x00007f6346c17c04 futex_wait_cancelable (libpthread.so.0 + 0x10c04)
#1 0x00007f634520acb0 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-78.so.0 + 0xb9ccb0)
#2 0x00007f6344951a64 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-78.so.0 + 0x2e3a64)
#3 0x00007f6344951b14 _ZN2js12HelperThread10ThreadMainEPv (libmozjs-78.so.0 + 0x2e3b14)
#4 0x00007f6344947791 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-78.so.0 + 0x2d9791)
#5 0x00007f6346c1081f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007f634783c963 __clone (libc.so.6 + 0x12a963)
Sep 28 00:27:14 glorfindel systemd[1]: systemd-coredump@2-1285-0.service: Succeeded.
journalctl attached journalctl.log