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

Apostrophes, tilde (~) and hat (^) accents doubled #1341

Closed
lazka opened this issue Mar 15, 2015 · 4 comments
Closed

Apostrophes, tilde (~) and hat (^) accents doubled #1341

lazka opened this issue Mar 15, 2015 · 4 comments
Labels

Comments

@lazka
Copy link
Member

lazka commented Mar 15, 2015

Original issue 1341 created by CharlesOBlack on 2014-03-05T12:41:56.000Z:

Whenever Quod Libet is running, my accents all get displayed doubly.

This means that whenever I type apostrophe once, two of it get typed on whatever program I'm using.

I've tried disabling all plugins and the bug persists. I've also tried switching software keyboard layouts, and the accents get fixed when I do that.

Relevant information:

Quod Libet v. 2.6.3
Windows 7 Professional SP1
Software Keyboard United States-International

I'm not sure exactly what causes this. If I close Quod Libet, accents get back to normal; if I run the program again, accents go back to being doubled.

Any suggestions? I can also provide more info if required.

@lazka
Copy link
Member Author

lazka commented Mar 15, 2015

Comment #1 originally posted by CharlesOBlack on 2014-03-05T12:46:13.000Z:

Ran a search for "apostrophe", couldn't find anything. Posted this, ran a search for 'accent', found something from May 2013 (10 months ago).

Also found out someone else posted the same issue about 4 days ago.

Apparently it's pyHook related. Renaming or deleting C:\Programs\Quod Libet\bin\pyHook fixes it.

Sorry for posting the same bug twice!

@lazka
Copy link
Member Author

lazka commented Mar 15, 2015

Comment #2 originally posted by reiter.christoph on 2014-03-05T13:02:42.000Z:

Thanks for the report.

@lazka lazka closed this as completed Mar 15, 2015
@chrisfls
Copy link

chrisfls commented Jun 4, 2016

Just a note here: This bug still happens in the current version (3.6.1)

@lazka
Copy link
Member Author

lazka commented Jun 5, 2016

This will be fixed in the next release, see #1168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants