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=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.
https://bugs.winehq.org/show_bug.cgi?id=54795
Bug ID: 54795
Summary: configure fails to find pcap development libraries
with libpcap <1.9.0 present
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wpcap
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Hello,
In my case, Debian 8 "Jessie" ships libpcap 1.6.2.
According to the man page, pcap_init was introduced in libpcap 1.9.0.
https://man7.org/linux/man-pages/man3/pcap_init.3pcap.html
The ~regression~ commit modifies configure to check for pcap_init() in lieu of
pcap_create(), which fails on such old OS.
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=54730
Bug ID: 54730
Summary: EverQuest: game compositor freezes during account
switching
Product: Wine-staging
Version: 8.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnherschelfreeman2013(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74235
--> https://bugs.winehq.org/attachment.cgi?id=74235
log after switching to another account and returning to account with game
running
During a switch to another account compositor window freezes and when switching
back to account executing the wine process video does not update in the
compositor window
--
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=46405
Bug ID: 46405
Summary: steam: crashes when opening game
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yuettingng(a)gmail.com
Distribution: ---
Created attachment 63166
--> https://bugs.winehq.org/attachment.cgi?id=63166
program error details
Game crashes when I started to play on steam
--
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=45983
Bug ID: 45983
Summary: Not working gamepad in windows steam games
Product: Wine-staging
Version: 3.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nickfaces(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
With 3.18-staging not working gamepad in windows steam games. No errors in
terminal. The problems in Arch and Ubuntu 18
--
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=45751
Bug ID: 45751
Summary: Sniper Elite V2 has missing objects or invisible
textures
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: noonetinone(a)gmail.com
Distribution: ---
Sniper Elite: V2 has missing objects or invisible textures in the main menu.
Gameplay is unaffected. The has occurred between 3.10 & 3.11 wine releases.
The problems has been present since then. I took the liberty to bisect the
offending commit. It is below.
________________________________________________________________________
537007525a8909a2295bd7cd123f0eb6ce1b77cb is the first bad commit
commit 537007525a8909a2295bd7cd123f0eb6ce1b77cb
Author: Józef Kucia <jkucia(a)codeweavers.com>
Date: Tue Jun 19 17:15:00 2018 +0200
wined3d: Use WINED3D_LOCATION_DISCARDED before initializing buffers with
data.
Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
:040000 040000 2dcb8443ae6f5ac506801053163f0b21be4af81d
0e4abd89b101fb9f27c0273cecfb4af3f71a901a M dlls
--
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=54770
Bug ID: 54770
Summary: missing check of malloc in loader/main.c
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: void0red(a)gmail.com
Distribution: ---
we put a fault injection fuzzing on wine,
and find two potential bugs in loader/main.c.
it may miss a malloc check before memcpy
the call stack looks like this:
main ->
load_ntdll ->
get_self_exe ->
build_path ->
memcpy
main ->
load_ntdll ->
remove_tail ->
memcpy
--
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=54665
Bug ID: 54665
Summary: Can't install EduPython
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: villemurclement(a)gmail.com
Distribution: ---
Created attachment 74180
--> https://bugs.winehq.org/attachment.cgi?id=74180
Crash Report
Before with wine 7.x it was working fine. Today I reinstalled my Debian and
install Wine 8.0 and when I was trying to install EduPython it was not working.
--
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=54438
Bug ID: 54438
Summary: Wine 8 Stage -> shell32.dll -> wrong icon and hold not
the standart of Windows
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blackcrack(a)blackysgate.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73987
--> https://bugs.winehq.org/attachment.cgi?id=73987
Screenshot of the Desktop with running wine and Listerplugin for show the
shell32.dll icons
I use Fedora 37
(more in the Screenshoot of versioning)
i guess there be troubles of over watching the Standards ?
okey, i be not a programmer as so in c, c++ and assembler,
but i be now more 25 Jears in the net and at 1999 directly at Linux,
but this, wonder me sure .. because i have logging me in at WineHQ :
the most heart of WinNT API, so in Wine is really wrong.. and you have not note
that before you have make a release ? wow.. heavy, this let show how less you
have you code under over watching and cleaning up.
i have in the last times again install wine in Fedora and have a bit an eye on
it.. because i use Total commander from Cris and have use an couple icons into
the Buttonbar from shell32.dll as standard Icons, because i have noticed, there
be wrong icons in the shell32.dll and i have thing.. wth.. wrong icons what's
goes on..
and i work over smbfs down from a server in my basement and i have a
serverinfrastructure via fedora(at moment 37) with smbfs and nfs for my
linuxclients and use the same Total Commander from Chris for all Win32/64
Systems/API's down from the network, where i have noticed to be something wrong
in the wine shell32.dll..
now my question.. do you not check over the files before you get out an
version..
okey, in clear text: Shell32.dll have the wrong ICONS (and use no standard),
look on the Picture attachemnt.
All Version's informations it is see in the Screenshot Attachment.
this is my first Bugreport here in WineHQ.. as a old man...oh wrong, old Geek
;)
best regards to the Team :)
Blacky
p.s.: and please, before you release an Wine-release, check also the files and
don't give out something ...hmmm (no, i say not crap *g*) we have now a couple
time behind us..(Wineteam and i am as user...) and there is not a really making
better Wine in Linux like it is now.. a bit wrong... and, me wonder, also
Reactos have Wine in the fingers.. and they are have say nothing about
shell32.dll and the icons ?|
ui...
so, all the best :)
--
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=49839
Bug ID: 49839
Summary: Steamwebhelper.exe crashes when running Steam
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: drnefarius(a)hotmail.com
Created attachment 68178
--> https://bugs.winehq.org/attachment.cgi?id=68178
steam webhelper crashing high sierra
SteamWebHelper keeps crashing. Steam will run, but the online contents, such as
the store, the library, news, etc. are all left blank. I can log into Steam
though, and update and download games. But I cannot run the game. This is for
Tracks The Train Set Game.
--
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=41262
Bug ID: 41262
Summary: It won't let me open Skyrim on my Steam
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abanwait1(a)gmail.com
Created attachment 55563
--> https://bugs.winehq.org/attachment.cgi?id=55563
This is the log that comes in whenever I ask the program error log sheet.
Downloaded Steam via a wineskin wrapper and downloaded Skyrim via that Steam.
Whenever I click on Skyrim to play it, it says the program Setup.exe has
encountered a serious problem and needs to close. We are sorry for the
inconvenience. The opening little menu window pops up but when I click play, it
goes back to the desktop. Please email with a response.
--
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=39173
Bug ID: 39173
Summary: age of pirates force close often
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adi.maryadi.1905.1985(a)gmail.com
Distribution: ---
Created attachment 52205
--> https://bugs.winehq.org/attachment.cgi?id=52205
Age of Pirates 2
force close often
--
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=51735
Bug ID: 51735
Summary: Resident Evil Village doesn't launch
Product: Wine
Version: 6.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Process hangs with
07c8:err:virtual:virtual_setup_exception stack overflow 2064 bytes in thread
07c8 addr 0x7bc739a4 stack 0x207f0 (0x20000-0x21000-0x420000)
wine-6.16-247-g0d22e8455a2
--
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=43874
Bug ID: 43874
Summary: Battlefront 2 (2005) broken multiplayer
Product: Wine-staging
Version: 2.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bellamorte42(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Attempted with both a 64-bit and 32-bit wineprefix. Single player works just
fine, but within a couple seconds of loading a multiplayer game it crashes back
to the menu with an 'unknown error'.
--
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=47198
Bug ID: 47198
Summary: League of Legends 9.10 Crash after champ select
Product: Wine
Version: 4.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: composizion3(a)hotmail.com
Distribution: ---
Created attachment 64453
--> https://bugs.winehq.org/attachment.cgi?id=64453
Console output.
9.10 patch broke the game on Linux; again; it crashes at the game start.
It should also be noted that it is the patch that officially ended win xp/vista
support.
--
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=54542
Bug ID: 54542
Summary: d3dx10_38:d3dx10, d3dx10_40:d3dx10, d3dx10_41:d3dx10,
d3dx10_42:d3dx10 & d3dx10_43:d3dx10 regularly get
D3DXERR_INVALIDDATA
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3dx10_38:d3dx10, d3dx10_40:d3dx10, d3dx10_41:d3dx10, d3dx10_42:d3dx10 &
d3dx10_43:d3dx10 regularly get unexpected hr values in test_get_image_info()
and test_create_texture().
For instance on 2023-02-15 on w1064 the 32-bit d3dx10_43:d3dx10 test got:
d3dx10.c:2677: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2686: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2677: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2686: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2868: Test failed: Test 0: Got unexpected hr 0x88760b59.
d3dx10.c:2870: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2881: Test failed: Test 0: Got unexpected hr 0x88760b59.
d3dx10.c:2883: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2868: Test failed: Test 2: Got unexpected hr 0x88760b59.
d3dx10.c:2870: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2881: Test failed: Test 2: Got unexpected hr 0x88760b59.
d3dx10.c:2883: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
See https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10
Where 0x88760b59 == D3DXERR_INVALIDDATA
This is similar to the d3dx10_34:d3dx10 issue bug 54541 but there are key
differences:
* In bug 54541 it is always the same two checks that fail, whereas here it's a
different set of failures with every run, with anywhere from 4 to 78 failures.
* Bug 54541 never had failures in test_create_texture().
* Also this bug's failures seem to have started some time around 2023-01-07,
i.e. much more recently than the ones in bug 54541.
--
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=52661
Bug ID: 52661
Summary: The Life and Suffering of Sir Brante Crashes Often
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: matthewcboyd(a)tutanota.com
Distribution: ---
Created attachment 71983
--> https://bugs.winehq.org/attachment.cgi?id=71983
Log File
I am trying to play The Life and Suffering of Sir Brante from GOG using Wine.
It crashes at different times always with the same error in the log file. Now
here's what's really interesting: it doesn't do this on the demo. I can
actually boot up the demo, get past where it crashes on the full version, copy
my save into the full game and keep going. Problem is it will crash again down
the road and I am more than convinced this will happen past where the demo
ends. The crashes are always at specific points and are reproducable.
The part of the log file that I think is interesting is this:
"ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so"
The file is installed properly and this happens on Manjaro as well as Mint.
My System:
AMD Ryzen 5 2600X | 16GB DDR4-3000 CL15 | MSI RX 580 8GB Gaming X | Mesa 21.2.6
| Linux Mint 20.3 | Mate 1.26.0 | Kernel 5.4.0-104-generic
--
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.