I’m on Opensuse fxce. I use the anki package from the officially mantained repo. After the latest update today (version above) I found myself unable to type in japanese inside any anki window, like Add, Edit, Browse.
I don’t remember which version I had prior, maybe the 25.07.2 but don’t quote me on that. (if you know how I can check that, I’m all ears)
I’ve always used Fcitx + Mozc, activating the keyboard switch with Ctrl+Space.
Everywhere else works as intended as always.
Not only the buttons combination doesn’t change the input method, trying to “force” the change via the icon in the taskbar doesn’t work either.
So, for now, I have to keep a notepad window open ready for when I need to type something in jap and then copy paste the text inside anki.
I searched online/in the forum and found threads from Jan 22, Dec 22, Jan 23 but no solutions…
I went through the troubleshooting steps so don’t give me that lazy reply.
Maybe don’t scoff at the “lazy reply,” since it solves 95% of the issues folks ask about. But since you already did it (good job!), I’ll give you the other “lazy reply” –
Did you search for other posts before posting? This one seems related.
*That* troubleshooting? Restarting and resizing apps? Thank God it’s not a cartridge or it would suggest to blow on it too.
I’m getting confrontational because it’s frustrating. It’s not the first time that a (major?) update brings problems.
Yes I had come across that thread, and hoped it would not be suggested. I guess I’ll try that ibus alternative if it’s not above my level, but I don’t approve the general philosophy where
1 anki changes/ anki disables features/ anki stops compatibility/…
2 user has to change (perfectly viable) system configs just to accomodate anki.
1-2 years ago I was on Linux mint where there was less support (u had the old repo package, the .deb route or just compiling it yourself) . I lived with the infamous processing freeze (like others lamented for years). The solution? I had to change distro…
Currently you’re using a free OS with free software asking for free help in a forum. Nobody wanted to break your Japanese input with the new version, but it did as a side effect of other necessary changes (at least for now). You can always decide to use an older version that works for you if you don’t like the work being provided on the newer ones.
Everything is free, doesn’t mean users cannot complain.
Anki is an excellent project with a great Docs, community support, etc.
But, IMHO there has been a communication problem from developers. There were no mentions about a feature removal, support removal, etc. on any change log, then users upgraded and ended up to lose a lot of time trying to fix something they were not aware of. That’s all.
Cutting off an input method is a pretty big change, should have been told. Especially, after having released several revisions.
Furthermore, the fix isn’t clear at all yet.
My point was that your messages did (including your most recent) construe the situation in a way where someone somehow “cut off an input method” intentionally, which I think isn’t the truth. Necessary changes in packaging simply led to a situation where now another type of build of a dependency (not even code developed at the Anki project) is being used, which then influenced input method compatibility on Linux.
I think it is very valid to point this out and for example suggest changes to packaging etc. — I don’t think the way you were going about it helps a lot, though.
Respectfully, that’s your deduction, I didn’t tell “intentionally”. Anyway, they didn’t intentionally, they did it practically due to the introduction of a new piece of software: “anki-launcher”
This forum is the official mean to publish issues, it’s been published several times, but despite new revisions were published and betas are ongoing, no one is mentioning this bug. Is there something not working in the process or not? It seems to be users are suggesting something but it hasn’t been taken in consideration yet or we don’t have visibility about that.
It should help to bring up in evidence that something is going wrong in the process of bug tracking.
Anyway you replied a user:
”Currently you’re using a free OS with free software asking for free help in a forum.”
What does it mean? He didn’t agree with a philosophy that states: “changing a system-wide input-method of a OS should be the solution to remediate a single software bug”.
He was completely right IMHO and that’s not related to the fact that user is using a free OS or not.
He was just telling: “guys, let’s look for a real solution, let’s do a real troubleshooting”.
I don’t think the way you were going helped a lot too.
My point is: “let’s take in consideration this bug, track it and aim to a solution making the process visible to users”.
Subsumming the OP’s posts: “I’m having a problem, don’t bother about usual troubleshooting steps, I’m obviously above any of that. Oh and that other forum post which outlines exactly my issue in a neutral way and explains that it’s currently broken and how to work around it? Well whatever I know about that thread but I don’t like the state of things, so I made a new thread and now expect another magical better solution. That solution doesn’t exist currently? Well I guess now I don’t like your project’s philosophy. Nothing should ever break my workflow, I have to always be able to use the newest release version on whatever system I want to use.”
I think he could’ve just used the already existing thread and add something like: “I’m also experiencing this. It would be great to have a real solution to this in the future, as switching to another input method or compiling your own Anki binaries is not viable for everyone. Is this something we can expect to get solved in the near future? If not, what does it take to get to a real solution and how to bring that along?”
Sorry for confusing you with the OP in my previous message.
I must have missed that the thread was recent enough to be able to post under it (probably because it was already flagged as solved), that was my bad.
About my vile horrid remark on troubleshooting, I wanted to avoid the all too common situation where you receive as reply just a one-liner pointing to the troubleshooting, however appropriate it might be.
The other thread is of course very good… if you can follow it. Guys out there making dissertations on computer science, compiling, spinning python wheels, surfing the world wide web and what not.
Why is it on the users who can’t keep up to ask for customized instructions, to ask a dev to give any sort of explanation-tutorial?
Even the top dog himself chimed in and just said IBus works
Of couse he was talking to an user who knows his way around so nothing more was needed, but what about the rest of us reading it?
What irritated me is seeing that the problem I experienced for the first time is actually years old, and keeps reappearing again and again.
My dude. No new solution is expected or needed. The solution was already there because It was working fine. If this issue to-be was known prior publishing the release, we can debate about it, about shipping a package out that made two/three/five steps forward and one step back.
Your wording suggestions are good and effective so I’ll copy them here (now that a user in need is asking the questions explicitly, there are no more excuses, right?) It would be great to have a real solution to this in the future, as switching to another input method or compiling your own Anki binaries is not viable for everyone. Is this something we can expect to get solved in the near future? If not, what does it take to get to a real solution and how to bring that along?”
