You are not logged in.
Pages: 1
I installed my arch linux 2 days from now, i'm using gnome in my samsung expert x30. When i'm using my laptop sometimes i get a black screen from nowhere, somenthing is written(like when i turn on my arch) but i can't read because it's too fast, after this the gnome login screen appears but i can't login, the only way i can do it is rebooting. I can't see the pattern envolving this black screen, i can use my laptop for hours and this comes from nowhere, no pattern.
Offline
Look in your journal for clues.
Offline
I don't now how i see
Edit:
I learned how to see it and i think is something related to crash dumped in things realated to gnome.
Last edited by mperusso (2017-05-29 15:05:49)
Offline
The idea is that you specify to us what is "crash dumped in things realated to gnome" and yes, it's very most likely a segfault of gnome-shell why you'll next learn about "cordumpctl" and share the coredump of such crash
If it's in libgjs and your mozjs38 version is up-to-date, it's most likely a problem with some (non-stock?) extension, there're quite some recent threads on the matter.
Offline
The 7609 process is the on that crashed, and yes, libmozjs-38 is there
Stack trace of thread 7609:
#0 0x00007fb14498d8ec n/a (libmozjs-38.so)
#1 0x00007fb14496d147 n/a (libmozjs-38.so)
#2 0x00007fb14492abcc n/a (libmozjs-38.so)
#3 0x00007fb144c4930f n/a (libmozjs-38.so)
#4 0x00007fb1449516ca n/a (libmozjs-38.so)
#5 0x00007fb14495a932 n/a (libmozjs-38.so)
#6 0x00007fb14495ac24 n/a (libmozjs-38.so)
#7 0x00007fb144c63777 n/a (libmozjs-38.so)
#8 0x00007fb14495acd8 n/a (libmozjs-38.so)
#9 0x00007fb14495082f n/a (libmozjs-38.so)
#10 0x00007fb14495a932 n/a (libmozjs-38.so)
#11 0x00007fb14495ac24 n/a (libmozjs-38.so)
#12 0x00007fb144c63777 n/a (libmozjs-38.so)
#13 0x00007fb14495acd8 n/a (libmozjs-38.so)
#14 0x00007fb14495082f n/a (libmozjs-38.so)
#15 0x00007fb14495a932 n/a (libmozjs-38.so)
#16 0x00007fb14495ac24 n/a (libmozjs-38.so)
#17 0x00007fb144c63777 n/a (libmozjs-38.so)
#18 0x00007fb14495acd8 n/a (libmozjs-38.so)
#19 0x00007fb14495082f n/a (libmozjs-38.so)
#20 0x00007fb14495a932 n/a (libmozjs-38.so)
#21 0x00007fb14495ac24 n/a (libmozjs-38.so)
#22 0x00007fb144c5f8eb n/a (libmozjs-38.so)
#23 0x00007fb14495acd8 n/a (libmozjs-38.so)
#24 0x00007fb14495b845 n/a (libmozjs-38.so)
#25 0x00007fb144c27ee7 _Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1
#26 0x00007fb147040426 n/a (libgjs.so.0)
#27 0x00007fb145050fbf ffi_closure_unix64_inner (libffi.so.6)
#28 0x00007fb145051330 ffi_closure_unix64 (libffi.so.6)
#29 0x00007fb146d04643 n/a (libgio-2.0.so.0)
#30 0x00007fb146d04679 n/a (libgio-2.0.so.0)
#31 0x00007fb14675e66a g_main_context_dispatch (libglib-2.0.so.0)
#32 0x00007fb14675ea20 n/a (libglib-2.0.so.0)
#33 0x00007fb14675eacc g_main_context_iteration (libglib-2.0.so.0)
#34 0x00007fb146d19f9d g_application_run (libgio-2.0.so.0)
#35 0x00007fb1450511c8 ffi_call_unix64 (libffi.so.6)
#36 0x00007fb145050c2a ffi_call (libffi.so.6)#37 0x00007fb14703e82f n/a (libgjs.so.0)
#38 0x00007fb14703fee4 n/a (libgjs.so.0)
#39 0x00007fb14495acd8 n/a (libmozjs-38.so)
#40 0x00007fb14495082f n/a (libmozjs-38.so)
#41 0x00007fb14495a932 n/a (libmozjs-38.so)
#42 0x00007fb144968ec1 n/a (libmozjs-38.so)
#43 0x00007fb144969253 n/a (libmozjs-38.so)
#44 0x00007fb144c27728 n/a (libmozjs-38.so)
#45 0x00007fb144c27864 _ZN2JS8EvaluateEP9JSContextNS_6HandleIP8JSObjectEERKNS_22ReadOnlyCompileOptionsEPK
#46 0x00007fb14705f191 gjs_eval_with_scope (libgjs.so.0)
#47 0x00007fb147055616 gjs_context_eval (libgjs.so.0)
#48 0x0000000000401888 main (gjs-console)
#49 0x00007fb146008511 __libc_start_main (libc.so.6)
#50 0x0000000000401a9a _start (gjs-console)
Offline
You can either build the js38 package with debug en- and stripping disabled to gain more information on why it crashes, or try to identify the triggering extension by removing/disabling them all, see whether gnome-shell still crashes and (if not) enable them one-by-one until the crash re-occurs.
Offline
i have no idea how to debug the package. I'm going to try disable the extensions, but keeping in mind that the crash occurs maybe one/two times a day, this will require a lot of time.
Offline
Pages: 1