http://bugs.winehq.org/show_bug.cgi?id=33545
Bug #: 33545 Summary: Dragon Age 2 : Problem with azerty keyboard type Product: Wine Version: 1.5.29 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: scrimekiler@yahoo.fr Classification: Unclassified
When playing with my azerty keyboard, some of the keys aren't recognized in the game. For example the "2" key, "4" key and most other number keys (because 2 does "é" symbol)
That's a problem because in this game, it controls what spell you use (one of the key you must hit the most to play...)
http://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #1 from Someone scrimekiler@yahoo.fr 2013-10-31 12:57:46 CDT --- Problem still there with wine-1.7.0
http://bugs.winehq.org/show_bug.cgi?id=33545
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions@gmail.com
--- Comment #2 from Berillions berillions@gmail.com --- (In reply to comment #1)
Problem still there with wine-1.7.0
Can you tried the latest patch in this bug report ? http://bugs.winehq.org/show_bug.cgi?id=15350
https://bugs.winehq.org/show_bug.cgi?id=33545
Someone scrimekiler@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Dragon Age 2 : Problem with |Dragon Age 1 and 2 : |azerty keyboard type |Problem with azerty | |keyboard type
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #3 from Someone scrimekiler@yahoo.fr --- (In reply to Berillions from comment #2)
(In reply to comment #1)
Problem still there with wine-1.7.0
Can you tried the latest patch in this bug report ? http://bugs.winehq.org/show_bug.cgi?id=15350
One key was not working but now works with this patch : the key 4
But the other number keys are still bugged with both Dragon Age : 2-7-9-0
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #4 from Someone scrimekiler@yahoo.fr --- Oh, And I forgot to mention those tests have been made on wine-1.7.33
https://bugs.winehq.org/show_bug.cgi?id=33545
Marc Bessières marc.bessieres@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.bessieres@gmail.com
--- Comment #5 from Marc Bessières marc.bessieres@gmail.com --- Hello,
This looks like Bug 30984. To confirm, could you check if reverting 43984f355a2905e16075a9df3d7fbe463761e853 makes it work?
If so then, it would be a duplicate.
Cheers, Marc
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #6 from Someone scrimekiler@yahoo.fr --- (In reply to Marc Bessières from comment #5)
Hello,
This looks like Bug 30984. To confirm, could you check if reverting 43984f355a2905e16075a9df3d7fbe463761e853 makes it work?
If so then, it would be a duplicate.
Cheers, Marc
From the post you link, that weird chain of characters is a reference to a
commit from a git repo somewhere ?
So you suggest I try a patch or ... ? By "reverting" you mean a regression ?
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #7 from Marc Bessières marc.bessieres@gmail.com --- Hello,
Sorry I was not clear enough. Yes that chain of character is a reference to a commit into a git repository, the official wine one.
I think the issue you're reporting is the same as the one in bug 30984. This was introduced by the mentionned commit.
To verify that, it would be good that you build wine from the source, see in the FAQ, the part about compiling wine: http://wiki.winehq.org/FAQ And that before you launch the compilation you should run the command: git revert 43984f355a2905e16075a9df3d7fbe463761e853
which would "remove"/negate that commit.
If after running your program with that wine, you can see that the bug is gone, it would mean that that commit introduced a regression, and that your bug is in fact a duplicate of bug 30984. We try to keep only one open bug for the same issue, so this one would need to be closed as duplicate. Then I recommend you to put yourself in CC of the other bug, so you know when it is corrected, and you can check the solution works for you too.
I hope I'm clear enough.
Cheers, Marc
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #8 from Someone scrimekiler@yahoo.fr --- (In reply to Marc Bessières from comment #7)
I think the issue you're reporting is the same as the one in bug 30984. This was introduced by the mentionned commit. git revert 43984f355a2905e16075a9df3d7fbe463761e853
which would "remove"/negate that commit.
If after running your program with that wine, you can see that the bug is gone, it would mean that that commit introduced a regression, and that your bug is in fact a duplicate of bug 30984. Cheers, Marc
I applied this revert and now the number keys work.
It confirms that as you thought it's a duplicate of bug 30984
https://bugs.winehq.org/show_bug.cgi?id=33545
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to Someone from comment #8)
I applied this revert and now the number keys work.
It confirms that as you thought it's a duplicate of bug 30984
Thanks for testing and thanks to Marc for the insight.
*** This bug has been marked as a duplicate of bug 30984 ***
https://bugs.winehq.org/show_bug.cgi?id=33545
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Béla Gyebrószki gyebro69@gmail.com --- Closing all abandoned/duplicated/invalid bugs.
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #11 from Someone scrimekiler@yahoo.fr --- (In reply to Béla Gyebrószki from comment #10)
Closing all abandoned/duplicated/invalid bugs.
Not solved ? This bug is still affecting me...Why closing it ?
https://bugs.winehq.org/show_bug.cgi?id=33545
--- Comment #12 from Someone scrimekiler@yahoo.fr --- Oh sorry nevermind I thought bug 30984 was closed too