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.
https://bugs.winehq.org/show_bug.cgi?id=52680
Bug ID: 52680
Summary: EVE Online memory leak in GPU memory
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: n.andrew.walsh(a)gmail.com
Distribution: ---
Created attachment 72016
--> https://bugs.winehq.org/attachment.cgi?id=72016
EVE Online internal memory-usage monitor after ~2h minimal gameplay
Ever since the 2022-02-06 update to EVE Online, the GPU memory gradually fills
up over time with texture data, eventually leading to a client slowdown,
freeze, and disconnect. This is particularly bad on high-memory-usage
activities (for example, in big fleets jumping gates), but even in
barely-active states the GPU memory usage gradually increases.
Attached is a screenshot of the client after running for a couple hours. I'm
not doing anything special: mostly in-station, occasionally undocking to go to
a different station in the same system, etc. As you can see, memory use,
particularly textures, increases over time.
This is likely a problem with the EVE client itself, but since it seems to only
affects Linux, CCP likely won't touch it. Any idea what's going wrong here? Is
there a workaround that wine could implement? What other data do you need from
me?
--
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=52565
Bug ID: 52565
Summary: CD/DVD Druckerei v6.0 - can't detect original DVD
media because of ProtectDisc
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: vaxxabait(a)gmail.com
Distribution: ---
CD/DVD Druckerei is a disc labeling software primarily for German-speaking
market. It installs fine on Wine, but after starting it checks and ask to
insert original DVD media in the drive although it is in the drive.
The path to DVD is added as D: drive of CDROM type in Winecfg.
It is the same D: drive software has been installed from.
I set up Windows 2000 in Winecfg because software seems to be roughly from this
age.
I've checked the main executable with Protection_ID v0.6.8.5, which
detects:
[!] ProtectDISC v6.6 [Build 0xC744 / 51012]
[!] protection level: Basic
So seems like it prevents software to start.
According to https://wiki.winehq.org/Copy_Protection, ProtectDISC is not
supported yet. Since original issue
(https://bugs.winehq.org/show_bug.cgi?id=9484) is closed as abandoned now, I
would like to raise the topic again.
--
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=52615
Bug ID: 52615
Summary: The Godfather 2
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
Created attachment 71941
--> https://bugs.winehq.org/attachment.cgi?id=71941
The Godfather 2 log
When launching the game through wine in the terminal black screen. When
launching the game through Lutris+wine, the game starts, but when you select a
new game there is an endless load.
--
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=52632
Bug ID: 52632
Summary: Failure to complete installation of Keil uVision 5
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: gawlikaj(a)gmail.com
Distribution: ---
Created attachment 71956
--> https://bugs.winehq.org/attachment.cgi?id=71956
Backlog trace from attempt to install Keil uVision 5.3
Attempted to install Keil uVision v5.3 on 32-bit Wine Prefix. Encountered a
page fault toward the end of the installation, however the installer continued
successfully. Attempting to launch results in a message: "No RTE pack path
specified, RTE will be disabled". The suspicion is that the final actions that
the installer normally performs on windows (I have installed it successfully on
windows in the past) failed to be performed most likely due to the crash of the
installer due to one of the components: user32, kernel32, ntdll.
This may be the incorrect component selected for the bug report as there are
three components referenced in the backtrace log: user32, kernel32, and ntdll
--
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.