https://bugs.winehq.org/show_bug.cgi?id=54081
Bug ID: 54081
Summary: urlmon:protocol - The "http protocol direct read test"
sometimes causes a timeout in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
urlmon:protocol - The "http protocol direct read" test sometimes causes a
timeout in Wine:
protocol.c:3576: Testing http protocol (direct read)...
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000001
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
protocol.c:3438: Test failed: wait timed out
protocol.c:3439: Test failed: expected Switch
protocol.c:348: Test failed: unexpected call OnResponse
protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000002
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
urlmon:protocol:06f4 done (258) in 120s
See https://test.winehq.org/data/patterns.html#urlmon:protocol
This always happens in "Testing http protocol (direct read)...", never in the
https or "from urlmon" variants.
The first known instance happened on 2022-08-05 on debiant-wow32 (there was no
such failure in the previous 2 months) and the nightly WineTest runs have had
about one failure per month since.
--
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=54475
Bug ID: 54475
Summary: Hardwar UIM6.0 crashes in 8.0, doesn't in 6.0.3
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nickmarko(a)gmail.com
Distribution: ---
Created attachment 74024
--> https://bugs.winehq.org/attachment.cgi?id=74024
debug output of crash
Ran in Virtual Desktop mode to test version F2.0, which has no windowed mode
option and won't display full screen but does display in the virtual desktop.
F2.0 gets past the loading screen and the game doesn't crash.
I updated Wine from 6.0.3 (the version that is in the default Ubuntu repos) to
8.0 from the official WineHQ repos for Ubuntu Jammy and now UIM6.0 crashes when
the loading bar reaches 100%.
I downgraded to 6.0.3 and UIM6.0 no longer crashed. I updated back to 8.0 and
UIM6.0 crashes again.
Terminal output running F2.0: https://pastebin.com/mfLVj3Xd
Terminal output installing and running UIM6.0: https://pastebin.com/mDHSzMyM
--
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=52983
Bug ID: 52983
Summary: d3d8:device - test_wndproc() fails systematically on
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d8:device - test_wndproc() fails systematically on Wine:
device.c:3212: Test failed: Expected message 0x3 for window 0, but didn't
receive it, i=49.
device.c:3359: Test failed: Expected message 0x3 for window 0x1, but didn't
receive it.
https://test.winehq.org/data/patterns.html#d3d8:device
As far as I can tell the missing "message 0x3 for window 0x1" is present every
time, while the one for "window 0" is only present most of the time but not
necessarily on the same iteration.
--
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=33069
Bug #: 33069
Summary: Visual Basic 6 can't load any component
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: german_ant_82(a)yahoo.com
Classification: Unclassified
Created attachment 43719
--> http://bugs.winehq.org/attachment.cgi?id=43719
Fixme errors list for the components that can't be loaded
Visual Basic comes with a set of preloaded standard components and a set of
loadable extra components. These extra components can't be loaded.
List of components that can't be loaded:
AxBrowser
Cdlg
Microsoft ADO Data Control 6.0 (OLEDB)
Microsoft Calendar Control 8.0
Microsoft Chart Control 6.0 (OLEDB)
Microsoft Comm Control 6.0
Microsoft Common Dialog Control 6.0
Microsoft Data Bound Grid Control 5.0 (SP3)
Microsoft Data Bound List Controls 6.0
Microsoft DataGrid Control 6.0 (OLEDB)
Microsoft DataList Controls 6.0 (OLEDB)
Microsoft DataRepeater Control 6.0 (OLEDB)
Microsoft FlexGrid Control 6.0
Microsoft Hierarchical FlexGrid Control 6.0 (OLEDB)
Microsoft Internet Transfer Control 6.0
Microsoft MAPI Controls 6.0
Microsoft Masked Edit Control 6.0
Microsoft Multimedia Control 6.0
Microsoft PictureClip Control 6.0
Microsoft RemoteData Control 6.0
Microsoft Rich Textbox Control 6.0
Microsoft Script Control 1.0
Microsoft SysInfo Control 6.0
Microsoft Tabbed Dialog Control 6.0
Microsoft Windows Common Controls 5.0 (SP2)
Microsoft Windows Common Controls 6.0
Microsoft Windows Common Controls-2 5.0 (SP2)
Microsoft Windows Common Controls-2 6.0
Microsoft Windows Common Controls-3 6.0
Microsoft Winsock Control 6.0
MSFlexGrid Wizard 6.0
Package and Deployment Wizard
VB6 Application Wizard
VB6 Data Form Wizard 6.0
VB6 MSChart Wizard 6.0
VisModelBrowser
--
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=41013
Bug ID: 41013
Summary: Sourceinsight: the 'Window' menu click no response
Product: Wine
Version: 1.8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.hu(a)intel.com
Distribution: ---
Created attachment 55180
--> https://bugs.winehq.org/attachment.cgi?id=55180
'Window' menu list jump to top left
The menu of 'Window' click has no responses.
But other menu can work.
My workaround is to click its adjacent menu item then arrow key to move to
'Window' menu. But even so, it appears to left top of the window. See
attachment.
--
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=23064
Summary: Sourceinsight: no response clicking menu, untill
firstly right-click in main window area
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dwwwww(a)hotmail.com
OS: RHEL 4
Wine, 1.2-rc2
Open sourceinsight, click the menus, no response.
But it works after right click in main window area.
--
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=50281
Bug ID: 50281
Summary: fsync patch for wine 6.0-rc1 (without staging)
Product: Wine
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: michael.scott(a)quest-arts.co.uk
Distribution: ---
Created attachment 68830
--> https://bugs.winehq.org/attachment.cgi?id=68830
fsync patch that applies to vanilla wine 6.0-rc1
I have created a new fsync patch that can apply directly to wine 6.0-rc1
without needing esync from staging.
I have tested this patch applied to the latest wine sources (6.0-rc1) as of 7th
December 2020 using Star Citizen 3.11.
I have included it here for you to review for your convenience to review
whether to include it in a future wine version.
Current testing from myself and others in the Star Citizen LUG org when using
fsync enabled wine and kernels are resulting in a much smoother experience.
--
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=15480
Summary: Saving files in Word/Excel creates useless .lnk files
Product: Wine
Version: 1.1.5
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrew(a)etc.gen.nz
Hi,
In Word and Excel 2003 when we save files then a .lnk file is created in the
same directory as the source file. These files are useless for two reasons:
1) They're in the same directory as the original .doc or .xls files which have
Word and Excel associated with them respectively.
2) On a standard Debian Lenny machine running Gnome the .lnk files aren't
recognised by any apps and won't cause Word or Excel to run.
I've searched around the place to see if we can turn this "feature" off, but
haven't found anything. Is this possible? If not, could this please be added.
--
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=54141
Bug ID: 54141
Summary: console: pressing ctrl+4 in any console application
terminates it
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: taviso(a)gmail.com
Distribution: ---
Reproduce:
$ wine cmd.exe
Z:\home\taviso>
[Now press Ctrl+4]
I think all of the Ctrl+Number keys don't work (oddly, except Ctrl+2), but
Ctrl+4 is especially annoying because it immediately terminates the
application.
I was trying to use a Windows console application, but didn't have much luck
because of the missing keybindings.
--
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.