https://bugs.winehq.org/show_bug.cgi?id=54834
Bug ID: 54834
Summary: Some applications hang at startup with seemingly
frozen window since Wine 8.2
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 74336
--> https://bugs.winehq.org/attachment.cgi?id=74336
ImgBurn on Wine 8.1 (on commit 0692d07f) terminal output
Hello,
After an update from 8.0-rc5 to 8.5 some applications fails to start.
I did a regression test and the last working release is 8.1 (exact commit in
regression field).
The affected applications are:
Ubisoft connect (prevents ability to play many games) (on 32-bit and 64-bit).
ImgBurn.
Regards.
--
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=52767
Bug ID: 52767
Summary: wine: Unhandled page fault on read access to
0000000000000000 at address 00000003AF6DAE20 (thread
002c), starting debugger...
Product: Wine-staging
Version: 7.5
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Suddenly returned fault while to start Wine, terminal export the log:
winecfg
wine: created the configuration directory '/Users/avenjames/.wine'
0024:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.5 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
wine: Unhandled page fault on read access to 0000000000000000 at address
00000003AF6DAE20 (thread 002c), starting debugger...
002c:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 40 48" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: could not load kernel32.dll, status c0000135
192:~ avenjames$
tried to reinstall the Wine via Brew, clean prefix and .wine folder, fixed
permission of the disk, and remove all history of the terminal session, but
still the same.
I remember that before clean the prefix and the wine folder, it could run app
with a debug window but can't do anything, after clean the prefix and .wine, it
couldn't be started with wineboot or winecfg.
any idea bros?
OS: OSX 10.14 Mojave
Platform: RMBP mid-2015
--
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=52696
Bug ID: 52696
Summary: idk why this is happending
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ariannaperezlove(a)gmail.com
Distribution: ---
Created attachment 72043
--> https://bugs.winehq.org/attachment.cgi?id=72043
idk what happening
i was trying to play roblox than that happend !
--
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=51660
Bug ID: 51660
Summary: Adding setupapi to prefix and running EverQuest causes
game to never launch
Product: Wine
Version: 6.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: johnherschelfreeman2013(a)gmail.com
Distribution: ---
Created attachment 70534
--> https://bugs.winehq.org/attachment.cgi?id=70534
wine output after adding setupapi
launcher and game run fine pre adding setupapi post add produces log with +seh
--
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=40398
Bug ID: 40398
Summary: Aftter context_create "Failed to allocate fragment
pipeline context data.", the function referenced NULL
pointer.
Product: Wine
Version: 1.9.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: blackwingcat2000(a)gmail.com
Distribution: ---
L63E6DACE:
mov edx,[esp+50h]
mov eax,[edx+0000C8F8h]
mov eax,[eax]
mov [esp],eax
call SUB_L63F0913E
mov ebx,eax <- eax returns zero !
jmp L63E6D69D
L63E6D69D:
mov eax,ebx
call SUB_L63E6739A
SUB_L63E6739A:
push edi
push esi
push ebx
sub esp,00000020h
mov ebx,eax
test byte ptr [L63F31078],08h
jnz L63E673C6
L63E673AB:
mov eax,[ebx+00000FE8h] <- Crash
--
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=40175
Bug ID: 40175
Summary: bug
Product: Wine
Version: 1.9.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: regifraga_07(a)hotmail.com
Distribution: ---
Created attachment 53677
--> https://bugs.winehq.org/attachment.cgi?id=53677
Às vezes quando inicio o jogo apareci essa mensagem
bug, quando inicio apareci uma mensagem de erro
--
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=39835
Bug ID: 39835
Summary: Fullscreen Steam popup Flickering
Product: Wine
Version: 1.8-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: masterderth(a)gmail.com
Distribution: ---
Heyo, so I've been experiencing some screen flickering when I play games in
Wine.
It happens when I get a popup from Steam (Linux version).
To reproduce it.
1. Have Steam (Linux) running.
2. Launch a Wine game in fullscreen.
3. Alt Tab to Steam and get a friend to message you (Game must support alt
tabbing).
4. Quickly go back into the Wine Game and watch the corner where popups appear
at.
5. When friend messages, the screen will flicker.
I've tested it with The Sims 4 and Fallout New Vegas, Origin and Steam
(Windows).
I am on Linux Mint 17.3 running MATE.
--
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=55498
Bug ID: 55498
Summary: Multiple application and games have difficulties
connecting to their online servers
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 75061
--> https://bugs.winehq.org/attachment.cgi?id=75061
The Lord of the Rings Online default terminal output - wine 8.14
Hello,
Since a few days all the applications and games I tested, that uses online
services, have trouble connecting to their servers. This includes:
- Steam;
- Blizzard Battle.net;
- World of Warships;
- The Lords of the Rings Online;
- Dungeons and Dragons Online.
I've not tried any other windows application, yet.
- World of Warships is very slow to start, and sometimes ends up with 'not
connected to the server' in the port, with missing online content. I can play
online matches, though, but finding a match is slower than before. I think the
game tries hard to start and to reconnect.
- Blizzard Battle.net often fails to connect for the login screen. It says
'connecting' for a minute and then shows an blz#### splash screen with buttons
to go 'offline' or exit. It sometimes manages to connect, but then can fails to
load the online content (world of warcraft videos and news feed for instance),
with a message to retry.
- Steam is just being slow to open and to display online content, sometimes
staying at a blank space; It's overall functioning.
- The Lords of the Rings Online and Dungeons and Dragons Online both have
slowdowns when opening their respective launchers, and connecting to the world
servers fails constantly after several retries (20 retries in 1 sec. each).
Sometimes, the launcher display an error message about a socket error.
I attach the terminal output from The Lords of the Rings Online as it's the one
that does the most visible retries at connecting to its server and is
constantly failing.
The issue is present with my compiled wine version (from 8.11 to 8.14), as well
as the Debian wine 8.0~repack-4 package and the winehq-devel 8.14~bookworm-1
package (Those two I tested to be sure it was not my builds that were broken).
I've upgraded to Debian 12 in mid-July. All those applications and games were
working by then, with wine 8.11. I don't know what has changed on my system
since then that has broken everything. There were a few kernel updates and also
updates to those applications (WoWs 12.7, Steam on 1st of August, LOTRO & D&DO
had an in-game shop update, blizzard had an update, etc. but the symptoms seem
common and I doubt they are caused by individual updates.
I also have no more sound from another offline game that worked in July and had
no update as it doesn't connect to internet at all, but I'll leave that sound
issue for later. It may be a kernel/system library update, though.
I have no problem accessing internet from Linux programs including the native
Steam & Discord clients.
My system is Debian 12 Bookworm with 32 GB of RAM.
NVidia RTX 2070 with proprietary driver 535.104.05.
Regards.
--
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=54981
Bug ID: 54981
Summary: Visio 2003 When using ux theme icons are not rendered
on object property panels
Product: Wine
Version: 8.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs(a)copysoft.org
Distribution: ---
Created attachment 74520
--> https://bugs.winehq.org/attachment.cgi?id=74520
Icons in Visio2003 property panels are rendered blank when using light theme.
When using Visio 2003 in Wine 8.7 and 8.8 when the "Light Theme" is enabled in
the Desktop Integration panel of the Wine configuration if I select properties
in an object the icons are drawn blank, if I select "no theme" the icons are
drawn normally.
--
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=54959
Bug ID: 54959
Summary: winhttp:notification - test_websocket() times out on
Windows and Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winhttp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
winhttp:notification - test_websocket() times out on Windows and Wine:
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:118: Test failed: 994: expected status 0x20000 got 0x1
notification.c:123: Test failed: 994: expected callback 0x1 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x2
notification.c:123: Test failed: 994: expected callback 0x2 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4
notification.c:123: Test failed: 994: expected callback 0x4 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x8
notification.c:123: Test failed: 994: expected callback 0x8 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000
notification.c:123: Test failed: 994: expected callback 0x4000 to be called
from the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x10
notification.c:123: Test failed: 994: expected callback 0x10 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x20
notification.c:123: Test failed: 994: expected callback 0x20 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x40
notification.c:123: Test failed: 994: expected callback 0x40 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x80
notification.c:123: Test failed: 994: expected callback 0x80 to be called from
the same thread
notification.c:118: Test failed: 994: expected status 0x20000 got 0x200000
notification.c:123: Test failed: 994: expected callback 0x200000 to be called
from the same thread
winhttp:notification:1448 done (258) in 120s 9182B
This is not a regression but rather an issue with the server. lsof shows the
test stuck with a connection to 104.21.29.32 (but that's a CloudFlare IP). So
the server's behavior must have changed recently and if that's not temporary
the test will need to be adjusted.
--
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.