http://bugs.winehq.org/show_bug.cgi?id=30752
Bug #: 30752
Summary: Open/save file dialog "New Folder" button doesn't show
new folder
Product: Wine
Version: 1.3.25
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aeikum(a)codeweavers.com
Classification: Unclassified
See the description from Bug 18606, which was fixed by
0a55ec2c9e1dc5fd0b99ad1202fd7849b0187808. The bug is back again, but no test
failures show in <dlls/shell32/tests>.
Regression testing reveals:
cde4993d625decec31d25485c7a588a3b772ef8b is the first bad commit
commit cde4993d625decec31d25485c7a588a3b772ef8b
Author: Jay Yang <jkelleyy(a)gmail.com>
Date: Mon Jul 11 17:35:35 2011 -0400
shell32: Have the default shell view call SHChangeNotifyRegister with
unixfs pidls.
:040000 040000 833232977eb625754bef7c0d2f09c065574df0d9
cccb55d925c166ba3838b0179cbdd655a44ba26a M dlls
--
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=52315
Bug ID: 52315
Summary: Fractal AX8 Edit: Crash after I/O operations
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nurtyll(a)pm.me
Distribution: ---
Created attachment 71476
--> https://bugs.winehq.org/attachment.cgi?id=71476
Error message
The program crashes recently, see error report (attachment).
Software version used: 1.9.1
https://www.fractalaudio.com/ax8-edithttps://appdb.winehq.org/objectManager.php?sClass=version&iId=38748
System information:
Wine build: wine-6.23
Platform: i386 (WOW64)
Version: Windows 7
Host system: Linux
Host version: 5.15.7-1-MANJARO
Note: The error can only be reproduced with associated hardware (Fractal Audio
AX8).
I could identify two reasons to reproduce the error:
1) When the program starts and the hardware (AX8) is connected, the program
reads some blocks of the current state, this sometimes leads to crashes.
2) If I want to navigate through different memory banks (called Banks), the
program crashes while reading out the preview of the banks.
Workaround for 1): just restart the program and at some point (after some
crashes) it will load the preset and works just fine.
The error was not there approximately two months ago. I tried also to run the
program in a 32 bit
Thank you for your help.
--
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=27419
Summary: Mouse problem in Heroes of Might and Magic 3
Product: Wine
Version: 1.3.21
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cdar07(a)gmail.com
When I go into the castle, then fort and click on a unit picture, new window
appear in which I can decide how many of those I want to buy. I click on the
maximum button and nothing is happening. From that moment, mouse click is not
working. Moving cursor is just fine, only click makes problems.
Everything is ok on wine 1.3.5 from
http://wine.budgetdedicated.com/archive/binary/.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=25486
Summary: Lego Stunt Rally: 3d scene is black
Product: Wine
Version: 1.3.9
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: support.intranet(a)libero.it
In Lego Stunt Rally 1.0, both in racing and costruction mode, the 3d scene is
black, as if no textures were present. Only a few lights are displayed.
--
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=52024
Bug ID: 52024
Summary: App Never Receives Winsock FD_* Messages After
FD_ACCEPT
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: jbrown(a)statslog.com
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 71023
--> https://bugs.winehq.org/attachment.cgi?id=71023
Broken +server,+winsock Trace from 6.x
I'm using a 32-bit Wine 6.21devel prefix on Ubuntu 20.04.3. I have a custom
application written in VB6 that uses the winsock (ws2_32.dll) API to listen for
network connections and respond to requests.
I use the following winetricks:
DISPLAY=:99 winetricks -q vcrun2008
DISPLAY=:99 winetricks -q vcrun2010
DISPLAY=:99 winetricks -q msxml6
DISPLAY=:99 winetricks -q corefonts
DISPLAY=:99 winetricks -q vb6run
I run the application with the following command line:
WINEARCH="win32" WINEDLLOVERRIDES="oleaut32=n" wine RCWebServerTest.exe &
NOTE: I've tried both with and without the oleaut32 native override.
The application is able to bind OK to 127.0.0.1:8080, but when try to curl to
it with the following command:
curl http://127.0.0.1:8080
curl is able to connect to the application, but the application does not
subsequently respond to the request.
Some debugging shows that the I'm receiving an FD_ACCEPT message in my app's
socket windowproc, but unexpectedly I receive no other FD_ messages (notably,
no FD_READ message).
After dumping +server,+winsock debug channels (attached), I see the server's
"get_message" and "select" calls are apparently "stuck" in a PENDING state,
with many repeated log messages along these lines:
0024: get_message( flags=00000000, get_win=00000000, get_first=00000000,
get_last=ffffffff, hw_id=00000000, wake_mask=00000000, changed_mask=00000000 )
0024: get_message() = PENDING { win=00000000, msg=00000000, wparam=00000000,
lparam=00000000, type=0, x=0, y=0, time=00000000, active_hooks=80000001,
total=0, data={} }
0024: select( flags=2, cookie=0031ef4c, timeout=infinite, size=8,
prev_apc=0000, result={}, data={WAIT,handles={007c}}, context={} )
0024: select() = PENDING { call={APC_NONE}, apc_handle=0000, context={} }
I've tried the exact same app on 5.x versions of Wine and it works as expected
- curl connects and receives data from my application. I performed a similar
+server,+winsock dump under the working 5.x version, and 2 things that stand
out are that the 5.x series performs periodic "flush" calls, and the
"get_message" and "select" calls never have a "PENDING" status. For example:
0009: flush(
async={handle=0004,event=0000,iosb=0032ee10,user=006414b8,apc=00000000,apc_context=00000000}
)
0009: flush() = 0 { event=00d8 }
0009: select( flags=2, cookie=0032eadc, timeout=infinite, prev_apc=0000,
result={}, data={WAIT_ALL,handles={00d8}} )
0009: select() = 0 { timeout=infinite, call={APC_NONE}, apc_handle=0000 }
0009: get_message( flags=00000001, get_win=00000000, get_first=00000000,
get_last=ffffffff, hw_id=00000000, wake_mask=00000000, changed_mask=00000000 )
0009: get_message() = 0 { win=0001006c, msg=00000804, wparam=000000d4,
lparam=00000001, type=6, x=0, y=0, time=a00af81e, active_hooks=80000001,
total=0, data={} }
The attached working & broken logs are quite large, but if you search for
FD_ACCEPT, that's where the curl connection gets accepted, and then the
subsequent lines are where the problem is evident in the broken log (or
expected behaviour is evident in the working log).
At this point I am stumped and not sure what else I can do to get the app
working under Wine 6.x, as I believe that there is a bug that is beyond my
capabilities to diagnose & fix.
Thank you in advance for any help, and If there's any additional information
needed from me, I will provide it.
--
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=51263
Bug ID: 51263
Summary: [Regression] Frostpunk crash after updating to Wine
wine-6.10 on Fedora
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: roidal(a)googlemail.com
Distribution: ---
Created attachment 70141
--> https://bugs.winehq.org/attachment.cgi?id=70141
STDOUT and STDERR
After updating to wine-6.10 frostpunk is crashing before able to create a
window.
STDOUT is attached.
Iam on Fedora 34 with an AMD-GPU.
Maybe it is related to Bug https://bugs.winehq.org/show_bug.cgi?id=51244
Let me know if you need more details.
--
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=51063
Bug ID: 51063
Summary: Version changes in Wine 6.7 break Spitfire Audio
plugins
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)robbertvanderhelm.nl
Regression SHA1: 04a8213ba9e3b8aa1f980d19b240929948da5abe
Distribution: ---
The LABS and BBC Symphony Orchestra Discover plugins can no longer find their
sample libraries as of Wine 6.7, and they'll show a generic 'Error #1:
Something went wrong' error message instead. After bisecting, it seems like
commit 04a8213 caused this regression. That commit changes WINE_FILEVERSION and
WINE_PRODUCTVERSION to match Windows 10 instead of Windows 7. There aren't any
new or different warnings or fixmes printed between Wine 6.6 (where those
plugins did work correctly) and Wine 6.7 (where they don't), but I've only
tested that with WINEDEBUG's defaults. Reverting the commit on the master
branch makes the plugins work again as expected. I tested this with the 64-bit
VST3 versions of BBCSOD 1.1.9 and LABS 1.3.7 under yabridge 3.1.1 (or, well,
the version that's to become 3.1.1).
https://source.winehq.org/git/wine.git/commit/04a8213ba9e3b8aa1f980d19b2409…
--
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=49401
Bug ID: 49401
Summary: Desperados 3 suffering from wrong colors
Product: Wine
Version: 5.10
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 67474
--> https://bugs.winehq.org/attachment.cgi?id=67474
Log Output on High Details
No matter if you play on high details or low details,
The Desperados 3 Release has a purple roads and other graphic curiosities
during the tutorial level
--
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=45505
Bug ID: 45505
Summary: Trying to open PEsS2017 settings.exe
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: donnisnoni.tid3(a)gmail.com
Distribution: ---
Created attachment 61881
--> https://bugs.winehq.org/attachment.cgi?id=61881
some bug when i try to open pes2017 settings.exe
I already install directx
--
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=52199
Bug ID: 52199
Summary: Grand Theft Auto Vice City doesn't start.
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
Grand Theft Auto Vice City and GTA 3 doesn't start.
--
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.