http://bugs.winehq.org/show_bug.cgi?id=25773
Summary: Majesty 2: certain keyboard keys are not recognized
Product: Wine
Version: 1.3.11
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=32841)
--> (http://bugs.winehq.org/attachment.cgi?id=32841)
terminal output
I noticed the problem when trying to start a multiplayer game. Logging in to
Gamespy requires an email address but the period '.' sign used in the address
was not accepted in the input field.
It turned out that several other keys are not recognized by the game, e.g.:
~,[]/;'\=-+.
By default '~' is used to bring up the chat window.
The issue can be tested by creating a new profile in the game: the input field,
containing the name, should accept all of the above mentioned characters but
they're not recognized (only the letters and numbers work and some of the
special characters by using <Shift>: @!$%).
Installing native dinput8.dll (via winetricks) doesn't help in Majesty 2.
Fedora 14 / Gnome 2.32.0 / xorg-x11-server 1.9.3-3.fc14
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52683
Bug ID: 52683
Summary: Nothing happens when running KakaoTalk
Product: Wine-staging
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorentz0021(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72022
--> https://bugs.winehq.org/attachment.cgi?id=72022
A failed CLI trying log
Nothing happens when running KakaoTalk via both GUI and CLI, though the
installation succeeded.
I've tried on wine-7.3 (Staging) and wine-7.4 (Staging) several times, only 7.4
seems to have this issue.
OS: Ubuntu 21.10
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52700
Bug ID: 52700
Summary: When using Korean, can't see the next characters
properly.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: take-me-home(a)kakao.com
Distribution: ---
When using Korean, can't see the next characters properly.
Input methods : IBUS, KIME, NABI, NIMF ( except "inputStyle=root" IME ie.,
fcitx )
Reproduce :
1. XIMPreEditDrawCallback enabled
2. Input 0x314E(ㅎ), 0x314F(ㅏ), 0x3134(ㄴ)
3. Text(GUI) = 0xD55C(한) ( but, in-Composition. it is normal. )
4. Input 0x3131(ㄱ)
5. Text(GUI) = 0xD55C(한) .. (Expected 한ㄱ 0xD55C; 0x3131. it is bug. )
6. Input 0x3161(ㅡ)
6. Text(GUI) = 0xD55C(한)0xADF8(그) .. ( It is normal )
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52699
Bug ID: 52699
Summary: dlls/d3d11/tests/d3d11_test.exe: Fails in
test_negative_viewports
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: tatidev1454(a)protonmail.com
Distribution: ---
Created attachment 72051
--> https://bugs.winehq.org/attachment.cgi?id=72051
Failed tests log
When I run the tests suite the test_negative_viewports test fails.
I run it with wine 32 bits and I have intel i915 drivers with Mesa 21.2.6
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52646
Bug ID: 52646
Summary: Trying to run wit (Wimms Iso Tools) , it works, its
just when I start the iso extraction it gives me this
error.
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: madeinclt26(a)gmail.com
Distribution: ---
Created attachment 71966
--> https://bugs.winehq.org/attachment.cgi?id=71966
After it starts extracting the iso it says " The program wit.exe has
encountered a serious problem and needs to close. We are sorry for the
inconvenience.
After it starts extracting the iso it says " The program wit.exe has
encountered a serious problem and needs to close. We are sorry for the
inconvenience.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52650
Bug ID: 52650
Summary: A game is chrashing...
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: w.blackfield(a)yahoo.com
Distribution: ---
Created attachment 71970
--> https://bugs.winehq.org/attachment.cgi?id=71970
Game crash for unknown reason. =/
I'm new here and just starting a carrer in web developement with focus on
backend. I really enjoy old games and wine is great for playing them. Hope this
report can help somehow.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52693
Bug ID: 52693
Summary: ITextRange::MoveEnd implemented partially
(tomCharacter and tomStory only)
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: sergey.bychkow(a)gmail.com
Distribution: ---
function textrange_moveend(...) implemented only for tomCharacter and tomStory.
See riched20/richole.c for details. The full list of parameters accepted by
this function is (riched_tom.idl):
tomCharacter = 1,
tomWord = 2,
tomSentence = 3,
tomParagraph = 4,
tomLine = 5,
tomStory = 6,
tomScreen = 7,
tomSection = 8,
tomColumn = 9,
tomRow = 10,
tomWindow = 11,
tomCell = 12,
tomCharFormat = 13,
tomParaFormat = 14,
tomTable = 15,
tomObject = 16,
tomCharFormat is required at first.
Additionly, other ITextRange functions implemented only for tomCharacter, like
textrange_movestart, or not implemented at all.
The list of not implemented functions include:
ITextRange_fnMoveWhile
ITextRange_fnMoveStartWhile
ITextRange_fnMoveEndWhile
... etc.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52690
Bug ID: 52690
Summary: CubismEditor4: Crashes when two child windows are
present
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: borgonzam(a)gmail.com
Distribution: ---
Live2D Cubism Editor hangs when two child windows are present
1. Website from where to download cubism editor
https://www.live2d.com/en/download/cubism/
2. Install and run with wine
3. Close the welcome window
4. You can trigger this problem by just dragging any image (jpg, png) into the
main window
5. An import progress window will appear and another window indicating you to
import said kind of images later, this will make cubism editor become
unresponsive and get stuck, impossible to click anything, close the import
window or close the main window
there are other ways to make two child windows appear at the same time but that
is the fastest way to make the software hang under wine, the behavior is
exactly the same in any of the other cases, so is the same problem with the two
or more child windows
Website from where to download cubism editor
https://www.live2d.com/en/download/cubism/
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50710
Bug ID: 50710
Summary: relative paths in WINEDLLPATH (as created from $0) no
longer work in wine-5.11+
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: PuetzKevinA(a)JohnDeere.com
Distribution: ---
Winegcc's app_loader_template deriveds $appdir from $0,
and then adds this directory into WINEDLLPATH:
https://source.winehq.org/git/wine.git/blob/wine-6.0:/tools/winegcc/winegcc…
appdir=`dirname \"$0\"`
WINEDLLPATH=\"$appdir:$WINEDLLPATH\"
Presumably the intent here is to match LOAD_LIBRARY_SEARCH_APPLICATION_DIR;
windows also searches for dlls immediately beside the main executable.
However, it is not unusual in interactive use for $0 to be a relative path,
e.g. if an executable is invoked as ./hello.exe, and dirname preserves this.
This results in WINEDLLPATH containing relative-path entries; this seems
a bit inadvisable, but it worked through wine-5.10. Since then it does not.
0024:err:module:import_dll Loading library test_shared.dll (which is needed
by L"Z:\\home\\test\\\bin\\test_executable_shared.exe") failed (error
c000003b).
Bisecting first pointed at df5e4764870e8ad1d8b206cb3475a073bc034e48, but
this is just https://bugs.winehq.org/show_bug.cgi?id=49545; after the unix
cwd is lost, a relative-path entry no longer resolves to the right place.
cherry-picking that fix from cdaa72c728df3c80499c8a4f59e731f353347db0
restores functionality, but then it breaks again (for the reason that
is actually breaking it in 6.0) at 9ec262ebcc7f14d7373841d4ca082b855ed8090f
https://source.winehq.org/git/wine.git/blobdiff/a2e77268f2007f2819c2e3e8bd7…
Previously ntdll/unix/loader.c:open_builtin_file used unix_to_nt_file_name,
which looks like it would have just flipped the slashes to translate a
a relative unix path to a relative NT path, which would then use NT's cwd
(hence susceptibility to https://bugs.winehq.org/show_bug.cgi?id=49545),
But now it uses open_unix_file, which calls SERVER_START_REQ( create_file ),
which just refuses relative paths STATUS_OBJECT_PATH_SYNTAX_BAD
https://source.winehq.org/git/wine.git/blob/wine-6.0:/server/file.c#l214
This is an error other than STATUS_OBJECT_{PATH,NAME}_NOT_FOUND, so it stops
https://source.winehq.org/git/wine.git/blob/wine-6.0:/dlls/ntdll/unix/loade…
I'm not sure what the best fix here really is... relative paths in WINEDLLPATH
seem like a pretty bad idea (since the cwd may change as the process runs,
environment variables leak down into child processe, etc), but the launcher
script's been like this for a long time.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52682
Bug ID: 52682
Summary: Ashita v3: Unable to run Ashita.exe
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: teddybearforhire(a)protonmail.com
Distribution: ---
Created attachment 72021
--> https://bugs.winehq.org/attachment.cgi?id=72021
terminal output
[Ashita Download URL]:
https://git.ashitaxi.com/Ashita/Ashitav3-Launcher/raw/master/Ashita.exe
When I attempt to run Ashita.exe with wine, the program encounters a serious
problem and has to close.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.