http://bugs.winehq.org/show_bug.cgi?id=58369
Bug ID: 58369
Summary: Clip Studio Paint 4 crashes when starting
ClipStudioPaint.exe using compatiblity mode for
Windows 10 or 11
Product: Wine
Version: 10.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ignacykuchcinski(a)gmail.com
Distribution: ---
Created attachment 78775
--> http://bugs.winehq.org/attachment.cgi?id=78775
backtrace file
Using Clip Studio Paint 4: https://www.clipstudio.net/en/dl/ (Free trial
download)
The launcher ClipStudio.exe manages to launch, but when starting
ClipStudioPaint.exe by clicking the draw button in the top left corner, that
program will crash shortly after launch with backtrace provided in the
attachement.
The program works well under compatiblity mode for Windows 8.1 and 7, including
all app features.
Dependencies installed: vcredist2022, dotnet481
I've collected unique error messages during the installation, running of the
launcher and the program itself before the crash in the attachement "errors",
the one that occurs in the ClipStudioPaint.exe just before the crash is as
follows:
032c:err:combase:RoGetActivationFactory Failed to find library for
L"Windows.UI.Input.RadialController"
Possibly related, but not identical:
https://bugs.winehq.org/show_bug.cgi?id=58254
--
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=39688
Bug ID: 39688
Summary: Crash in file browser dialog (probably because of >
MAX_PATH)
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: n296869(a)rtrtr.com
Distribution: ---
Wine's GetOpenFileNameW/GetSaveFileNameW seems to crash when encountering a
very long path name (i.e. longer than MAX_PATH characters).
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58388
Bug ID: 58388
Summary: the application krita is what i was trying to draw but
the programme just wont open.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ntsrkr(a)duck.com
Distribution: ---
it doesn't want to open. as soon as I try to open it wine crashes
download link https://krita.org/en/post-download/
version is krita-x64-5.2.9-setup.exe
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58303
Bug ID: 58303
Summary: make install for arm-linux-gnueabihf on
aarch64-linux-gnu host fails at libaclui.a
Product: Wine
Version: 10.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alex(a)alexrp.com
Distribution: ---
I did the following:
git clone https://gitlab.winehq.org/wine/wine.git
cd wine
mkdir build32 build64
cd build64
../configure --enable-win64
make -j$(nproc)
cd ../build32
PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf ../configure
--with-wine64=../build64 --host=arm-linux-gnueabihf
make -j$(nproc)
That all succeeds. However, when I try to `make install` in `build32`, I
eventually get:
../build64/tools/winebuild/winebuild -w --implib -o dlls/aclui/libaclui.a
-b arm-linux-gnueabihf --export \
../dlls/aclui/aclui.spec
tmp68634c48/libaclui-00000000.s: Assembler messages:
tmp68634c48/libaclui-00000000.s:2: Error: unrecognized symbol type ""
tmp68634c48/libaclui-00000000.s:9: Error: junk at end of line, first
unrecognized character is `,'
winebuild: /usr/bin/arm-linux-gnueabihf-as failed with status 1
make: *** [Makefile:1602: dlls/aclui/libaclui.a] Error 1
Unfortunately, I'm not familiar enough with the build system to know how to get
at that temporary file to try to diagnose the problem.
This is on a Ubuntu 25.04 machine, FWIW.
--
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=53008
Bug ID: 53008
Summary: When playing civilizatin2, winevdm crash
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: clabbe.montjoie(a)gmail.com
Distribution: ---
Created attachment 72378
--> https://bugs.winehq.org/attachment.cgi?id=72378
backtrace of winevdm
When playing civilization 2, game menu start, but after some time, game crash.
I am sure that it worked before, but i need some time digging backup to find
which version of wine I used.
--
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=57811
Bug ID: 57811
Summary: wikis/Building-Wine contains broken/obsolete link
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: depaoli.renzo(a)gmail.com
Distribution: ---
As per instruction on the 404 website
"If you followed a link from a WineHQ.org page and reached this page in error,
please report it to the WineHQ.org Bugzilla.":
The link on the Wine Wiki
https://gitlab.winehq.org/wine/wine/-/wikis/Building-Winehttps://www.winehq.org/pipermail/wine-devel/2016-January/111245.html
is broken resulting in 404.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58451
Bug ID: 58451
Summary: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer
when implemented'
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: winehq-bugs_serge_180716(a)gautherie.fr
Distribution: ---
wine-1.1.18
https://gitlab.winehq.org/wine/wine/-/commit/5f6ae94ad0163341c2cd79a89f29b2…
added
{
/* FIXME: should use CreateTimerQueueTimer when implemented */
thread = CreateThread(NULL, 0, rpcrt4_http_timer_thread, timer_data, 0,
NULL);
}
although CreateTimerQueueTimer() was already implemented, by
wine-1.1.2
https://gitlab.winehq.org/wine/wine/-/commit/d343f2baf76413eb690cbc44a0d56e…
{
NTSTATUS status = RtlCreateTimer(phNewTimer, TimerQueue, Callback,
Parameter, DueTime, Period, Flags);
}
Check and fix that FIXME.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58450
Bug ID: 58450
Summary: Total Annihilation (GOG, demo) – Wayland black screen
on startup.
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: karol23145(a)gmail.com
Distribution: ---
Created attachment 78901
--> http://bugs.winehq.org/attachment.cgi?id=78901
WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`.
### Summary
Total Annihilation (GOG version and demo) shows a black screen on native
Wayland (Mutter 48.3). On X11 it works perfectly, and on XWayland the game has
a minor fullscreen issue (see Bug 57482).
### Steps to reproduce
1. Download the Total Annihilation demo (or use the GOG version).
GAME DEMO CAN BE DOWNLOADED FROM:
https://archive.org/details/TotalAnnihilation_201405
2. Launch the game executable (`TotalA.exe`) under Wine on a native Wayland
session (No XWayland).
### Current behavior
The game process starts, sound can be heard, and keyboard input works (buttons
can be pressed), but the entire game window is black. The window is also not
fullscreen.
### Expected behavior
The game's intro videos should play, followed by the main menu, which should be
visible and interactive.
### Relevant logs, screenshots, screencasts etc.
*Attached are the following files:*
1. `TA.log`: Full Wine debug log captured with
`WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`.
2. `system_info.txt`: Output of `inxi -Fxxxza`.
### System Details
- **Wine Version:** Custom build from source (also tested with Wine development
branch, same result)
- **Windowing System:** Mutter 48.3 (Wayland session)
- **Distribution:** Fedora 42
- **Graphics Driver:** Mesa 25.0.7
- **Kernel version:** 6.15.4
--
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=52999
Bug ID: 52999
Summary: Redout fails to detect visual c++ runtimes
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 72366
--> https://bugs.winehq.org/attachment.cgi?id=72366
Logfile
When i try to run Redout, it says you need to install the c++ runtime.
The log does not indicate anything going wrong:
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub
0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub
007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub
007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub
0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
0000000000B9FD70
--
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.