You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the error and part of the BT it seems the segafult is caused when trying to use a pointer which was already removed:
Thread 1 "wf-dock" received signal SIGSEGV, Segmentation fault.
WfToplevel::handle_output_leave (this=0x5555557a0910, output=<error reading variable: Cannot access memory at address 0x8>) at ../wf-shell-0.9.0/src/dock/toplevel.cpp:99
99 pimpl->handle_output_leave(output);
ESC[?2004hESC[?2004l^MESC[?2004h(gdb) bt
ESC[?2004l^M#0 WfToplevel::handle_output_leave (this=0x5555557a0910, output=Python Exception <class 'gdb.MemoryError'>: Cannot access memory at address 0x8
#1 WfDockApp::handle_output_removed (this=0x555555598fb0, output=0x0) at ../wf-shell-0.9.0/src/dock/dock-app.cpp:89
No idea why that might be and that originates from:
#59 0x000055555556228b in WfDockApp::create (argc=1, argv=0x7fffffffdf18) at ../wf-shell-0.9.0/src/dock/dock-app.cpp:137
#60 main (argc=1, argv=0x7fffffffdf18) at ../wf-shell-0.9.0/src/dock/dock-app.cpp:147
Greetings !
The text was updated successfully, but these errors were encountered:
Using plain wayfire with plugins-extra and wf-shell with wf-panel and wf-dock. Versions:
Installed from AUR and running on artix gnu+linux. The full gdb log with backtrace at the end:
wf-dock_log.txt
From the error and part of the BT it seems the segafult is caused when trying to use a pointer which was already removed:
No idea why that might be and that originates from:
Greetings !
The text was updated successfully, but these errors were encountered: