Search Criteria
Package Details: anki 24.11-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/anki.git (read-only, click to copy) |
---|---|
Package Base: | anki |
Description: | Helps you remember facts (like words/phrases in a foreign language) efficiently |
Upstream URL: | https://apps.ankiweb.net/ |
Keywords: | anki languages learning vocabulary |
Licenses: | AGPL3 |
Conflicts: | anki-bin, anki-git, anki-qt5 |
Submitter: | demize |
Maintainer: | AlexBocken |
Last Packager: | AlexBocken |
Votes: | 178 |
Popularity: | 4.93 |
First Submitted: | 2021-09-17 22:31 (UTC) |
Last Updated: | 2024-12-23 08:04 (UTC) |
Dependencies (30)
- python (python37AUR, python311AUR, python310AUR)
- python-beautifulsoup4
- python-certifi
- python-decorator
- python-distro
- python-flask-cors
- python-jsonschema
- python-markdown
- python-orjson (python-orjson-gitAUR)
- python-protobuf (python-protobuf-gitAUR)
- python-pyqt6-webengine
- python-pysocks
- python-requests
- python-send2trash
- python-waitress
- qt6-multimedia
- qt6-svg
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR) (make)
- mold (mold-gitAUR) (make)
- Show 10 more dependencies...
Required by (2)
- kindle2anki-git
- subs2srs (optional)
Latest Comments
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 31 Next › Last »
AlexBocken commented on 2022-06-03 21:08 (UTC)
@KaiSVK
You do have
base-devel
installed, right? That package group is assumed for all AUR packages to be present. If that's the case and it's a dependency issue this should be my issue.I'm currently struggling to recreate the issue or find anything online around this error. If it's working for anki-qt5 but not anki this sounds like a qt issue to me. Does the error persist if you install the whole
qt6
package group?KaiSVK commented on 2022-06-01 11:58 (UTC)
I got this with anki package:
xkbcommon: ERROR: Couldn't process include statement for 'us(qwerty)' xkbcommon: ERROR: Abandoning symbols file "(unnamed)" xkbcommon: ERROR: Failed to compile xkb_symbols xkbcommon: ERROR: Failed to compile keymap [115746:115776:0601/135102.603799:FATAL:xkb_keyboard_layout_engine.cc(641)] Keymap file failed to load: us-qwerty Trace/breakpoint trap (core dumped)
Perhaps it's my fault or missing deps, but anki-qt5 works like a charm for me.
AlexBocken commented on 2022-05-28 19:05 (UTC)
@Munzu I'm struggling to reproduce the issue in 2.1.52. I also had that issue with 2.1.51... As I believe Qt6 to be largely stable now I will keep this package on Qt6. For people with similar issues to yours I have now made available
anki-qt5
as a backup until we can figure out a way to fix this annoying bug. Any errors with Qt6 are of course still welcome to be reported here.Munzu commented on 2022-05-28 16:58 (UTC)
Now that the package is using Qt6 again, I'm having the same problem I previously had and reported on the Anki forums:
https://forums.ankiweb.net/t/2-1-51-qt6-doesnt-show-next-card-after-answering/19495/4
AlexBocken commented on 2022-05-28 07:39 (UTC)
anki
is now using Qt6 out of the box! Let me know if there are any errors that need fixing or maybe the creation of aanki-qt5
package, it seems quite stable on my side.Since no bugs where reported over the last few days here or on
anki-qt6
I went ahead with a merge request ofanki-qt6
intoanki
.yakoyakoyokuyoku commented on 2022-05-26 21:19 (UTC)
@AlexBocken No problems were found by removing
python-stringcase
and using that_bazel_build
function, on the contrary Anki (Qt6) launched as expected and the Bazel background service was killed. Qt5 is going to work as well too.AlexBocken commented on 2022-05-26 08:45 (UTC)
@yakoyakoyokuyoku Thanks for the recommendations, I implemented them.
With 2.1.52 Qt6 seems stable enough to consider updating to it. Addon-compatibility seems to be ensured via Qt5 shims that can optionally be disabled.
If you feel like it please check out the anki-qt6 package. If no errors are reported to me Ill merge soon.
yakoyakoyokuyoku commented on 2022-05-24 21:34 (UTC) (edited on 2022-05-26 21:20 (UTC) by yakoyakoyokuyoku)
Taking in consideration what @Lukas1818 said, the package build needs to make sure that the
bazel
server is killed before continuing or exiting on failure. I'd suggest to call the following function inbuild()
instead of runningbazel build
directly.Also
python-stringcase
can be dropped as it's already been vendored.LuckyTurtleDev commented on 2022-05-16 20:56 (UTC)
hi, bazel is still running after building this package and consume a lot of ram.
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 31 Next › Last »