Package Details: anki-bin 24.11-1

Git Clone URL: https://aur.archlinux.org/anki-bin.git (read-only, click to copy)
Package Base: anki-bin
Description: Helps you remember facts (like words/phrases in a foreign language) efficiently. Installed with wheel.
Upstream URL: https://apps.ankiweb.net/
Keywords: anki anki-bin
Licenses: AGPL3
Conflicts: anki
Provides: anki
Submitter: Grafcube
Maintainer: escape0707 (Flammkuchen)
Last Packager: Flammkuchen
Votes: 121
Popularity: 5.99
First Submitted: 2021-10-21 08:27 (UTC)
Last Updated: 2024-11-30 12:00 (UTC)

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

rossvor commented on 2024-12-16 10:54 (UTC)

I think python-pip-system-certs needs to be added to dependencies -- it fails to launch without it. Error is: "Python module pip_system_certs is not installed. System certificate store and custom SSL certificates may not work. See: https://github.com/ankitects/anki/issues/3016"

escape0707 commented on 2024-12-04 09:02 (UTC)

@derivativeoflog7 Then it's a distro specific problem. I'm sorry that I'm being quite occupied recently and can't help you (I'm using Gnome and it would be a problem, too.). i suggest you look up Qt's runtime debug flag environment variable and use them to check the debug log during your Ctrl+Enter.

derivativeoflog7 commented on 2024-12-03 22:02 (UTC) (edited on 2024-12-04 08:59 (UTC) by derivativeoflog7)

@escape0707 Using PyPi's PyQt6 package (on 6.7.3) instead of the system-wide package from the Arch repos (on 6.8.0-dev builds) seems to fix the issue; so it seems that the issue could be fixed by having the venv not inherit system-wide packages and installing PyQt6 and all the rest from PyPi (installing PyQt6-WebEngine seems to pull all the needed dependencies). https://forums.ankiweb.net/t/ctrl-enter-doesnt-work-on-kde-plasma-if-anki-is-ran-through-pip-aqt/52206/4

derivativeoflog7 commented on 2024-11-21 17:56 (UTC)

@kageyama what I discovered is that the official Anki builds from GitHub and these AUR packages install Anki in a fundamentally different way: if I understand correcly the official builds copy a binary to PATH, while these two packages create a python venv and install Anki as a python module (aqt); and evidently, based on the issue you're encountering and the different one I'm encountering, these two aren't exactly equivalent

escape0707 commented on 2024-11-21 17:54 (UTC) (edited on 2024-11-21 17:58 (UTC) by escape0707)

@derivativeoflog7 If you can reproduce your problem with a pip installation, then it's definitely fine to directly report your problem to the upstream (Anki). dae (the author) should be able to troubleshoot your issue with you. No matter if it's an Anki issue or KDE/Qt issue.

derivativeoflog7 commented on 2024-11-21 17:51 (UTC)

@escape0707 the issue seems to be with aqt; if I follow the official instructions to install Anki as a Python module (with venv and all), Ctrl+Enter doesn't work there either.... I have no idea where to go from now though, or where to report the issue

kageyama commented on 2024-10-25 11:05 (UTC)

@escape0707 i use xeyes. But the problem got solved. Don't know how or when. I first tested in my friend device and Anki rendered perfectly. Then i tried testing in my system and it was fixed.

escape0707 commented on 2024-10-25 07:29 (UTC)

@kageyama Sorry for the late reply. But could you please also share the method you used to confirm that both your AUR Anki and your Anki installed from Anki official website are running under Wayland? And how exactly did you install Anki?

kageyama commented on 2024-09-29 01:10 (UTC)

aur/anki-bin and aur/anki both packages are producing pixelated text in anki under wayland. But https://apps.ankiweb.net/ works perfectly. Do you have any idea? An i missing some font? How can i troubleshoot this?

escape0707 commented on 2024-07-15 04:31 (UTC) (edited on 2024-07-15 04:32 (UTC) by escape0707)

@derivativeoflog7 I asked one of my friend to replicate your issue on their KDE, and they can reproduce the same behavior. I'm personally using Gnome, so I think this is the crucial difference. I'd suggest you to file this issue to the upstream or KDE or Qt. Before doing that, you might want to look up how to generate Qt application's debug info with some debug environment variables. I'm afraid I have to say that my KDE / Qt related knowledge could only be worse than yours, so I personally might not be able to help you troubleshoot that further. If there are other things I can do, please feel free to tell me!

1 2 3 4 5 6 .. 13 Next › Last »