Dear Maintainer,

after upgrading from Debian 10 to 11.2, I can no longer seamlessly switch
to different VTYs/Window Managers and then back to Enlightenment.

F'rex, switching to VTY1 (text console) works as expected, but after
switching back to Enlightenment on VTY7 E crashes.
Same after switching back to VTY7 from VTY8 (where a different user runs
XFCE4).

_Most_ of the time I get a black screen with red writing, citing "Guru
meditation #02248813.00000011", and can recover my Enlightenment session
(and open programs) via pressing F1. At other times I get a non-responsive
screen where I can see the title bars of all windows but clicking anywhere
with the mouse is non-responsive - this I can usually recover via
restarting Enlightenment (which I've bound to ctrl-alt-x for this purpose),
but sometines all I can do is kill all Enlightenment processes from, say,
VTY1 and logging in again from lightdm.

Backtrace log / ~/.e-crashdump.txt from when I get the back screen/red
writing situation:
---------------------------
Thread 1 (Thread 0x7f287f74e740 (LWP 5319)):
#0  0x00007f287d1c6b8d in pause () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1  <signal handler called>
No locals.
#2  0x00007f286afbed2b in ?? ()
   from /usr/lib/enlightenment/modules/comp/linux-gnu-x86_64-0.17.3/module.so
No symbol table info available.
#3  0x00007f286afbef4b in ?? ()
   from /usr/lib/enlightenment/modules/comp/linux-gnu-x86_64-0.17.3/module.so
No symbol table info available.
#4  0x00007f287f031657 in ?? () from /usr/lib/x86_64-linux-gnu/libecore.so.1
No symbol table info available.
#5  0x00007f287f0359d9 in ?? () from /usr/lib/x86_64-linux-gnu/libecore.so.1
No symbol table info available.
#6  0x00007f287f035f17 in ecore_main_loop_begin ()
   from /usr/lib/x86_64-linux-gnu/libecore.so.1
No symbol table info available.
#7  0x0000000000434ac0 in main ()
No symbol table info available.
Detaching from program: /usr/bin/enlightenment, process 5319
---------------------------

VTY-switching in this manner has worked well for me for over a decade
now, and I'm a bit stumped on as to how to debug this.

Thanks for any pointers.

Kind regards,
Robert

Switching to a different vty and back works fine for me, but I don't have
another desktop session running anywhere.  Does the issue still happen if you
only have one session running?

It looks like you're missing the debug symbols.  Please follow the instructions
at https://wiki.debian.org/HowToGetABacktrace and try again.

Ross

On Thu, 06 Jan 2022 22:26:53 -0800, Ross Vandegrift writes:


I've installed enlightenment-dbgsym, but can't get Enlightenment
started via gdb:
----------------------
$ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex 'threa
d apply all bt full' --args /usr/bin/startx /usr/bin/enlightenment_start

"0x7ffc0cb4c140s": not in executable format: file format not recognized
No executable file specified.
Use the "file" or "exec-file" command.
No stack.
No stack.
----------------------

~/.e-crashdump.txt (attached) looks filled with a bit more info, though.

I've then started E normally via lightdm, and attached to the (or
 rather "a", there's a couple) running
 /usr/bin/enlightenment process with gdb as per
https://wiki.debian.org/XStrikeForce/XserverDebugging  and did a
 backtrace there, gdb.txt is also attached.

Hope that helps.

Thanks for taking an interest!

Kind regards,
Robert