https://bugs.winehq.org/show_bug.cgi?id=55405
Bug ID: 55405
Summary: FreeCommander crashing immediately after it starts,
when Windows version is set above Windows XP
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 74965
--> https://bugs.winehq.org/attachment.cgi?id=74965
Console log from start of FreeCommander with Windows version set to v10
Installation of FreeCommander 32bit is working without any error.
When it should start it crashes. Depending on the version Windows is set to, it
behaves like this:
Windows XP: works
Windows 7: crash at the start with a stack overflow error, show in a message
box
Windows 10: a window came up and disappears immediately without any message
(box)
Console output for Windows 10 is attached.
--
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=41662
Bug ID: 41662
Summary: Carmageddon (windows 95 version) flickering menus
(possible ddraw issue)
Product: Wine
Version: 1.9.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaronbpaden(a)gmail.com
Distribution: ---
Created attachment 56059
--> https://bugs.winehq.org/attachment.cgi?id=56059
log
AfteCarmageddonr playing a race in Carmadeddon and returning to the menus, the
tops and bottoms of the screen flicker with an image from the last race.
I'm on radeonsi and it could be a driver issue, but from the logs I think it's
a ddraw issue.
It's not a huge problem as far as Carmageddon is concerned, because the menu is
still fully visible and usable.
--
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=54026
Bug ID: 54026
Summary: user32:msg receives unexpected messages in the 49000+
range on w11pro64_nv
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg receives unexpected messages in the 49000+ range on w11pro64_nv:
msg.c:13518: Test failed: msg.message = 49667 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49815 instead of WM_TIMER
or
msg.c:13549: Test failed: msg.message = 49663 instead of WM_TIMER
msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1
msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER
msg.c:13566: Test failed: msg.message = 275 instead of WM_USER
msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1or
or
msg.c:13518: Test failed: msg.message = 49650 instead of WM_TIMER
msg.c:13521: Test failed: msg.message = 275 instead of WM_USER
msg.c:13523: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13534: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13536: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13546: Test failed: msg.message = 275 instead of WM_USER
msg.c:13549: Test failed: msg.message = 1024 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49668 instead of WM_TIMER
msg.c:13503: Test failed: msg.message = 49668 instead of WM_TIMER
See http://winetest.dolphin/data/patterns.html#user32:msg
Where:
275 == WM_TIMER
1024 == WM_USER
These failures don't happen on other w11pro64 test configurations so it is
likely that these messages are generated by some part of the NVIDIA driver
despite it being installed without its GUI precisely to avoid this type of
issue. So it seems the test will have to accommodate these extra messages
despite their value changing from one run to the next.
--
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=43081
Bug ID: 43081
Summary: Final Fantasy VII 2012: Buggy rendering of graphics
during fights and dialogs
Product: Wine
Version: 2.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b33lzebob(a)googlemail.com
Distribution: ---
Created attachment 58266
--> https://bugs.winehq.org/attachment.cgi?id=58266
Archive including screenshots of this graphics bug, sed DLLs and terminal
output.
Strange display of character graphics during fights and dialogs (see
attachment).
System Information:
Wine version: 2.0.1
OS: Ubuntu Gnome 17.04 64bit
CPU: AMD® A4-3305m apu with radeon(tm) hd graphics × 2
GPU: ATI Radeon HD 6480 (Sumo2)
Things I've tried:
- update from Ubuntu Gnome 16.04 to 17.04 to provide form actual graphics
driver
- Added DDLs like described at https://appdb.winehq.org
/objectManager.php?sClass=version&iId=28519 via winetricks
- selected different versions of windows (Windows XP, 7, 8 & 10)
- installed steam- and non-stream-version of this 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.
http://bugs.winehq.org/show_bug.cgi?id=24559
Summary: Final Fantasy 7: error when installing 'Movie Player'
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=31005)
--> (http://bugs.winehq.org/attachment.cgi?id=31005)
Clicking 'Install MoviePlayer' option
Using Ubuntu 10.04
Final Fantasy 7 setup program gives you the option to 'Install Movie Player'
clicking this appears to fail with the error message
DirectShow Setup failed with error code: -2147023829
terminal log attached
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=53802
Bug ID: 53802
Summary: Steam - new Login UI renders as a black screen
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: gcenx83(a)gmail.com
Steams new reactlogin login has been rolled out to all users and at least on
macOS this renders as a black window.
To avoid this steam can be launched with the following launch command
-noreactlogin, this forces the older Login UI that renders correctly.
This occurs on brand a brand new wineprefix and installing steam via
winetricks.
--
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=55639
Bug ID: 55639
Summary: OSS driver sends output to wrong device
Product: Wine
Version: 8.16
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineoss.drv
Assignee: wine-bugs(a)winehq.org
Reporter: sean-freebsd(a)farley.org
Created attachment 75175
--> https://bugs.winehq.org/attachment.cgi?id=75175
trace:oss of test sound using default device in winecfg
Sometime after Wine 8.11, the OSS driver sends to the device node one higher
than selected. Whether the "System Default" or the specific node device is
picked in winecfg, the "Test Sound" goes to one higher than chosen.
In my case, the speakers are on /dev/dsp4. In the log, that device is
considered the default devnode. However, the devnode chosen for output is
/dev/dsp5. If I chose /dev/dsp3 specifically, then the audio will be output
via the speakers.
It definitely looks like an off-by-one bug.
Workaround: select lower device by number
--
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=55515
Bug ID: 55515
Summary: MotorM4X crashes due to missing 'tex1D' handling
Product: vkd3d
Version: 1.8
Hardware: x86-64
URL: http://www.gamepressure.com/download.asp?ID=21182
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Distribution: ---
0024:err:d3dcompiler:D3DCompile2 <anonymous>:97:26: E5005: Function "tex1D"
is not defined.
--
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=55208
Bug ID: 55208
Summary: Array size expressions should not allow every possible
expression
Product: vkd3d
Version: 1.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Distribution: ---
Sample shader would be:
float4 main() : sv_target
{
int x;
float a[(x = 2)];
return 0;
}
--
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.