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.
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.
https://bugs.winehq.org/show_bug.cgi?id=56761
Bug ID: 56761
Summary: So when I install Blizzard.net setup exe its crashes
and gives me the backtrace log
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adampigeons(a)gmail.com
Distribution: ---
Created attachment 76555
--> https://bugs.winehq.org/attachment.cgi?id=76555
the log of the error
i launch battlenet exe setup then the window becomes unusable then i get the
backtrace log
--
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=55979
Bug ID: 55979
Summary: Blizzard Battle.net Launcher: New Version Released On
11/30/2023 Hangs During Installation
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: crashdance(a)charter.net
Distribution: ---
Created attachment 75569
--> https://bugs.winehq.org/attachment.cgi?id=75569
Terminal output when running the Battle.net client installer in a clean Wine
prefix
When attempting to install Battle.net in a clean 64-bit prefix on a clean
install of Linux Mint 21.2 with all needed dependencies, I get the attached
terminal output and the progress hangs at 45%.
Also, I know the maintainers of Bugzilla encourage reporting only one problem
per bug. That being said, the exact same time this started happening, my
existing Wine prefix for Battle.net (and my Battle.net games) caused thread
crashes when opening Battle.net after installing yesterday's update. The update
was installed from within the Battle.net client by clicking the green icon to
install the update. Prior to this update released yesterday on November 30,
2023, Battle.net and the games were running flawlessly.
Because I can only add a single attachment, the Pastebin links below will give
more detail on the related issue of thread crashes described above:
Existing prefix terminal output when the thread crash occurs:
https://pastebin.com/4UwxTsEP
Here is my system information:
https://pastebin.com/v3MVemgg
Was able to save a crash report for the thread crash issue:
https://pastebin.com/mYX68NrX
--
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=58446
Bug ID: 58446
Summary: Shift + Click to draw straight line using tablet pen
not working in CLIP STUDIO PAINT version 2
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: kas23997(a)gmail.com
Distribution: ---
I am using a Wacom Intuous PT S2, for reference. I've tried to toggle mouse
mode in CSP's settings, but neither works. The pen will just draw separate dots
instead of making a straight line.
It works if using a mouse, however.
Nothing appeared in the Terminal after the wine command, so let me know if
there's any other info I should provide.
--
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=58440
Bug ID: 58440
Summary: Dance eJay 6 and dance eJay 7 crash with advapi32
error
Product: Wine
Version: 10.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: rave002(a)o2.pl
Distribution: ---
Created attachment 78891
--> http://bugs.winehq.org/attachment.cgi?id=78891
Dance ejay 6 Reloaded crash log
Both applications used to run fine on the older versions of wine. I'm attaching
the logs for Dance eJay 6.0, but the one for Dance 7 is pretty much the same.
Tried winetricks to maybe install a "proper" version of advapi32, however
winetricks doesn't provide it.
I will try to add Dance eJay 7.0 crash log in a following comment if I'm able
to.
--
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.