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: 117
Popularity: 4.16
First Submitted: 2021-10-21 08:27 (UTC)
Last Updated: 2024-11-30 12:00 (UTC)

Latest Comments

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

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!

kageyama commented on 2024-07-14 18:20 (UTC) (edited on 2024-07-14 18:21 (UTC) by kageyama)

@derivativeoflog7, i am also not able to replicate your bug. On my system Ctrl+enter works.

Try these things ->

  1. https://archlinux.org/packages/extra/x86_64/wev/ use this package to check if Ctrl+Enter is even passed to system. You can also use something like https://aur.archlinux.org/packages/showmethekey

  2. Create new user account, and try launching anki there and see if it happenes there too. The purpose of new user account is to avoid your current config/data/cache of anki.

derivativeoflog7 commented on 2024-07-14 13:59 (UTC) (edited on 2024-07-14 15:57 (UTC) by derivativeoflog7)

@escape0707 I've just finished installing Arch on my desktop, also with KDE Plasma on Wayland, and immediately tried with this package after all was set up, and I'm having the same issue on there too I've also tried to log in on X11 instead of Wayland, but it didn't help

EDIT: CTRL+Enter works from the official download on GitHub, even if I run it after install.sh, and regardless if it's running on Wayland or X11 (XWayland)

escape0707 commented on 2024-07-11 13:15 (UTC) (edited on 2024-07-11 13:25 (UTC) by escape0707)

@derivativeoflog7 Thank you for your detailed information. But I still can't reproduce the behavior you are suffering now.

To exclude the possibility of your own PC/OS's problem, can you try to install it on another computer (maybe a VM) and see if you can get the normal behavior?

This one reports Python 3.12.4 Qt 6.7.2 PyQt 6.7.0

This is the expected behavior as Arch is running this Python package with all the latest dependencies.

If you can still reproduce the bugged behavior, as this package is merely just downloading the upstream wheel and introducing the dependencies required by the upstream, maybe you can try the upstream suggested way to install it and start reporting the issue to the upstream?

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