You are not logged in.

#1 2020-10-19 19:30:03

ed15v
Member
Registered: 2020-09-23
Posts: 4

Anki not starting

Hey there,

suddenly anki doesn't work on my arch installation anymore.
When I executed it on the terminal it told me segmentation fault.
I used dgb to debug it:

mpv not found, reverting to mplayer
[New Thread 0x7fff8f363640 (LWP 60538)]
[Detaching after fork from child process 60539]
[Detaching after fork from child process 60540]
[New Thread 0x7fff8eb62640 (LWP 60543)]
[New Thread 0x7fff8e361640 (LWP 60544)]
[New Thread 0x7fff8db60640 (LWP 60545)]
[New Thread 0x7fff8d35f640 (LWP 60546)]
[New Thread 0x7fff8cb5e640 (LWP 60547)]
[New Thread 0x7fff77fff640 (LWP 60548)]
[New Thread 0x7fff777fe640 (LWP 60549)]
[New Thread 0x7fff76ffd640 (LWP 60550)]
[New Thread 0x7fff767fc640 (LWP 60551)]
[New Thread 0x7fff75ffb640 (LWP 60552)]
[New Thread 0x7fff757fa640 (LWP 60553)]
[New Thread 0x7fff74ff9640 (LWP 60554)]
[New Thread 0x7fff57fff640 (LWP 60555)]
[New Thread 0x7fff577fe640 (LWP 60556)]
[New Thread 0x7fff56ffd640 (LWP 60557)]
[Detaching after fork from child process 60558]
[New Thread 0x7fff567fc640 (LWP 60560)]
[Thread 0x7fff567fc640 (LWP 60560) exited]
[New Thread 0x7fff567fc640 (LWP 60565)]
[New Thread 0x7fff55ffb640 (LWP 60579)]
[New Thread 0x7fff745f8640 (LWP 60580)]
[New Thread 0x7fff743f7640 (LWP 60581)]
[Detaching after fork from child process 60582]
[Detaching after fork from child process 60583]
[Thread 0x7fff743f7640 (LWP 60581) exited]
[Thread 0x7fff55ffb640 (LWP 60579) exited]
[New Thread 0x7fff743f7640 (LWP 60590)]
[New Thread 0x7fff55ffb640 (LWP 60613)]
Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x00007fffd9ec7d60 in ?? () from /usr/lib/dri/swrast_dri.so
(gdb) bt
#0  0x00007fffd9ec7d60 in  () at /usr/lib/dri/swrast_dri.so
#1  0x00007fffd9a83d48 in  () at /usr/lib/dri/swrast_dri.so
#2  0x00007fffd9a92bc3 in  () at /usr/lib/dri/swrast_dri.so
#3  0x00007fffd9a92d2f in  () at /usr/lib/dri/swrast_dri.so
#4  0x00007fffd9a9b146 in  () at /usr/lib/dri/swrast_dri.so
#5  0x00007fffd9a9b5fa in  () at /usr/lib/dri/swrast_dri.so
#6  0x00007fffda775cc4 in  () at /usr/lib/dri/swrast_dri.so
#7  0x00007ffff1cda6a3 in  () at /usr/lib/libQt5Gui.so.5
#8  0x00007ffff1c5ae95 in  () at /usr/lib/libQt5Gui.so.5
#9  0x00007ffff1c5b916 in QPlatformBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, bool) ()
    at /usr/lib/libQt5Gui.so.5
#10 0x00007fffe0aa6ca9 in  () at /usr/lib/libQt5XcbQpa.so.5
#11 0x00007ffff07ee6a4 in  () at /usr/lib/libQt5Widgets.so.5
#12 0x00007ffff07f07a3 in  () at /usr/lib/libQt5Widgets.so.5
#13 0x00007ffff07f2331 in  () at /usr/lib/libQt5Widgets.so.5
#14 0x00007ffff07f2b8e in  () at /usr/lib/libQt5Widgets.so.5
#15 0x00007ffff083e8e9 in  () at /usr/lib/libQt5Widgets.so.5
#16 0x00007ffff07e1752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#17 0x00007ffff109880f in  () at /usr/lib/python3.8/site-packages/PyQt5/QtWidgets.abi3.so
#18 0x00007ffff4e7ccda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#19 0x00007ffff19198a0 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5
#20 0x00007ffff18edbac in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#21 0x00007fffe0aaff9c in  () at /usr/lib/libQt5XcbQpa.so.5
#22 0x00007ffff43da924 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#23 0x00007ffff442e621 in  () at /usr/lib/libglib-2.0.so.0
#24 0x00007ffff43d9131 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#25 0x00007ffff4ed5941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#26 0x00007ffff4e7b65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#27 0x00007ffff4e83af4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#28 0x00007ffff10978ef in  () at /usr/lib/python3.8/site-packages/PyQt5/QtWidgets.abi3.so
#29 0x00007ffff7d4c8fa in PyCFunction_Call () at /usr/lib/libpython3.8.so.1.0
#30 0x00007ffff7d3f4d4 in _PyObject_MakeTpCall () at /usr/lib/libpython3.8.so.1.0
#31 0x00007ffff7d3ada8 in _PyEval_EvalFrameDefault () at /usr/lib/libpython3.8.so.1.0
#32 0x00007ffff7de5d2d in  () at /usr/lib/libpython3.8.so.1.0
#33 0x00007ffff7d3605b in _PyEval_EvalFrameDefault () at /usr/lib/libpython3.8.so.1.0
#34 0x00007ffff7d46838 in _PyFunction_Vectorcall () at /usr/lib/libpython3.8.so.1.0
#35 0x00007ffff7d3a967 in _PyEval_EvalFrameDefault () at /usr/lib/libpython3.8.so.1.0
#36 0x00007ffff7d349a4 in _PyEval_EvalCodeWithName () at /usr/lib/libpython3.8.so.1.0
#37 0x00007ffff7de4f03 in PyEval_EvalCode () at /usr/lib/libpython3.8.so.1.0
#38 0x00007ffff7df0868 in  () at /usr/lib/libpython3.8.so.1.0
#39 0x00007ffff7deaa43 in  () at /usr/lib/libpython3.8.so.1.0
#40 0x00007ffff7caa67b in PyRun_FileExFlags () at /usr/lib/libpython3.8.so.1.0
#41 0x00007ffff7caa0f2 in PyRun_SimpleFileExFlags () at /usr/lib/libpython3.8.so.1.0
#42 0x00007ffff7dfd82a in Py_RunMain () at /usr/lib/libpython3.8.so.1.0
#43 0x00007ffff7dd97b9 in Py_BytesMain () at /usr/lib/libpython3.8.so.1.0
#44 0x00007ffff7a77152 in __libc_start_main () at /usr/lib/libc.so.6
#45 0x000055555555504e in _start ()

I don't know what to do with this output though and hope you guys can me help so I know what to do next time something similar happens.

Offline

#2 2020-10-23 19:52:39

ed15v
Member
Registered: 2020-09-23
Posts: 4

Re: Anki not starting

Apparently it only starts in a Wayland session, does anyone have an idea why that is the case or how one could find out?

Offline

#3 2020-10-23 20:11:04

Zod
Member
From: Hoosiertucky
Registered: 2019-03-10
Posts: 636

Re: Anki not starting

Have you looked at the wiki page for anki?

Or the upstream website?

Offline

#4 2020-11-08 19:55:52

putte_xvi
Member
From: Sweden
Registered: 2009-04-10
Posts: 22

Re: Anki not starting

For anyone else having this problem (as I did), the wiki page and the upstream website do indeed have the solution, which is to change the hardware acceleration setting.

Last edited by putte_xvi (2020-11-08 19:56:30)

Offline

Board footer

Powered by FluxBB