Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anki does not react anymore on Ctrl+Enter #178

Open
sommerluk opened this issue Nov 29, 2024 · 6 comments
Open

Anki does not react anymore on Ctrl+Enter #178

sommerluk opened this issue Nov 29, 2024 · 6 comments
Labels
bug Something isn't working question Further information is requested

Comments

@sommerluk
Copy link

Steps to reproduce:

  1. Open Anki
  2. Click on "Add"
  3. You see the dialog for adding a new note
  4. Fill it with some content
  5. Click Ctrl+Enter

Actual behaviour:

Nothing happens.

Expected behaviour:

Same as a click on the "Add" button: The card should be added.

Additional information:

This was working correctly before the last update.

System information:

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-126-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

@rayes0
Copy link
Collaborator

rayes0 commented Nov 29, 2024

I cannot reproduce this, the shortcut works fine on my end. Could be configuration or add-ons interfering. Please run Anki as follows: flatpak run net.ankiweb.Anki --safemode and try and add a card via the shortcut, and provide the full output.

@rayes0 rayes0 added the question Further information is requested label Nov 29, 2024
@sommerluk
Copy link
Author

Starting Anki as you described:

Preparing to run...
Qt warning: Qt: Session management error: Could not open network socket 
2024-11-29 13:40:52,263:INFO:aqt.mediasrv: Serving on http://127.0.0.1:35117
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
todo: windows paths in import screen
Starting main loop...

Opening the "add" dialog:

JS warning /_anki/js/editor.js:439 No version information available for component [tex]/noerrors
JS warning /_anki/js/editor.js:439 No version information available for component [tex]/mathtools
JS warning /_anki/js/editor.js:439 No version information available for component [tex]/mhchem

Making Ctrl+Enter:
No further output.

Closing Anki:

2024-11-29 13:45:16,375:WARNING:waitress: unhandled close event

@sommerluk
Copy link
Author

I've now tried it also with all add-ons disabled (thus not uninstalled): Same result.

@sommerluk
Copy link
Author

Not sure if this is related, but I've also noticed that since the update, Anki uses a wrong mouse cursor (different from the normal used mouse cursor used by all other apps).

@rayes0 rayes0 added the bug Something isn't working label Nov 30, 2024
@rayes0
Copy link
Collaborator

rayes0 commented Nov 30, 2024

I have confirmed this in kde plasma on both xorg and wayland. Does not appear to be an issue in gnome.

I have found an upstream forum issue: https://forums.ankiweb.net/t/ctrl-enter-doesnt-work-on-kde-plasma-if-anki-is-ran-through-pip-aqt/52206

It appears this is an upstream issue as it also occurs in the official aqt builds on pypi. Looks to affect the AUR build as well, but I am unsure why it does not affect the official bundled build.

@derivativeoflog7
Copy link

derivativeoflog7 commented Dec 3, 2024

It appears this is an upstream issue as it also occurs in the official aqt builds on pypi

I'm the creator of that thread. If I use a stable PyQt6 build (6.7.3) (because the Arch maintainers decided to ship 6.8.0 dev builds in the official repos) in a venv (outside flatpak), the issue isn't present - however, at the same time, the flatpak is reporting Qt 6.7.3 PyQt 6.7.1 and the issue is present; but not if I install PyQt 6.7.1 in the venv (all the "full" reported versions of every combo I tried are in that thread)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants