I was using the 25.09 version until now without issues, and I tried to upgrade to the latest 26.05. I admit I first went a bit fast and tried to upgrade through the launcher. It didn’t work and it’s normal as I discovered later in a post here.
So I went to the website and downloaded the latest version. I installed it through CLI and had no error message. I can’t launch the program though.
This is what I have when I launch ./anki --safemode :
Starting Anki 26.05...
2026-06-18 10:17:43,675:INFO:aqt.mediasrv: Serving on http://127.0.0.1:43743
Qt warning: GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
Starting main loop...
Segmentation fault
… And then it quits. I think a terminal window quickly flashes, but the main window doesn’t show up at all. Is there a way I can get more error logs or anything else I can do to diagnose where the problem is?
I’m on Debian stable, my desktop environment is XFCE, and I don’t have anything fancy on my system, no backports or anything. My system is up to date.
In the meantime I uninstalled version 26.05, and re-installed version 25.09.4 through the CLI launcher. It works so I’m not completely blocked from using Anki desktop, but I’d love to be able to update later!
So I can go back and forth between both versions which is handy for testing. I’m using ./anki --safemode to launch the 26.05 one in a terminal from its folder.
I’ve tried switching auto/software/vulkan in the file ~/.local/share/Anki2/gldriver6, but it doesn’t change anything. I switched it back to auto before trying again the 25.09.4 and it’s still fine. In the v25 preferences it shows as “OpenGL (default)”.
I’m not on Wayland so forcing Wayland doesn’t seem to fit. I tried anyway but yeah it doesn’t change anything either. Is it certain that it’s a display issue?
Anki tries to use X11 by default if it’s available (due to various issues). If you don’t see a message saying “Wayland support is disabled by default due to bugs” at startup then setting ANKI_WALAND won’t make a difference in your case.
It’s just one possible cause. Qt was updated in this release and there are apparently a lot of graphics changes in Qt 6.10/6.11
I’ve run “QT_DEBUG_PLUGINS=1 ./anki --safemode > qt_debug.txt”, then replaced my /home/username by ~/ in the file, and made it a pdf because I couldn’t directly upload a txt file as an attached document. The word “missing” does not appear in the log and there’s no warning as far as I can tell, so I’d say Qt seems happy?
Thanks to both of you for trying to help! I’ll definitely check the Github issue to see how it goes.
So I installed gdb (through apt) and ran it as you instructed.
Here’s the log https://pastes.io/W5JQaAss
I’ve only changed the username/pc/home path before pasting. When prompted to type “ret” for more that’s the option I chose, so there should be the whole thing.
Just after typing “r” the main window actually appeared and stayed until the end of the process, but it’s content was empty and I couldn’t interact with it.
So it might have been the main window flashing before and not a terminal window as I thought, it’s so fast I can’t say.
That makes sense. Gdb keeps the window “alive” if a crash happens, because the normal “exit / crash the program” flow is being interrupted.
Very likely, yes.
Regarding the log, it shows this:
fcitx::FcitxQtInputContextProxy::FcitxQtInputContextProxy(fcitx::FcitxQtWatcher*, QObject*) ()
from ~/apps/anki/anki-26.05-linux-x86_64/app_packages/PyQt6/Qt6/plugins/platforminputcontexts/../dbusaddons/libFcitx5Qt6DBusAddons.so.1
Makes me wonder if there is anything wrong with Fcitx on your system.
I use debian stable too (with gnome though) and Anki 26.05 works fine for me. If QT dependencies that anki ships were the issue, I’d expect to see the issue on other systems (like my debian system) as well. But I’m only a novice at programming. Abdo probably knows more.
Oooh I hadn’t seen that! I have fcitx installed system wide. Actually iirc I haven’t had the courage to upgrade to fcitx5 when the latest stable was released, because my language input setup is complicated, so I’m still on version 4. The error mentions fcitx5, so there might be an issue with conflicting versions/librairies…?
I added the fcitx5 plugin in #4886 but so far I only got confirmation that it’s working from the original poster. fcitx5 was working out of the box for me on Ubuntu even without these files. I’ve not tested with fcitx4 though.
I’ll definitely check the Github issue to see how it goes.