wine-bugs May 2024

wine-bugs@winehq.org

1 participants
2261 discussions

[Bug 33982] New: Steam windows can be resized to 1x1 despite minimum size
by wine-bugs＠winehq.org 30 May '24

30 May '24

http://bugs.winehq.org/show_bug.cgi?id=33982 Bug #: 33982 Summary: Steam windows can be resized to 1x1 despite minimum size Product: Wine Version: 1.6-rc2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Classification: Unclassified Steam's windows can be resized to 1x1. On Windows they can't. The minimum size for the main steam window is supposed to be 900x600 and for chat windows 396x351 according to tests. Using openbox 3.5.0 -- 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.

2 9

[Bug 13076] New: untangle: resize fails
by wine-bugs＠winehq.org 30 May '24

30 May '24

http://bugs.winehq.org/show_bug.cgi?id=13076 Summary: untangle: resize fails Product: Wine Version: 0.9.61. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)wnoise.ofb.net After any of the games in Simon Tatham's portable puzzle collection is resized, it only redraws the portion of the window that is the original size. Under windows, these games rescale to fit in the new window size. These may all be downloaded at http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ and have full source available. -- 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.

2 14

[Bug 37864] New: When I resize a maximized MDI window it assumes the new size instead of remaining maximized
by wine-bugs＠winehq.org 30 May '24

30 May '24

https://bugs.winehq.org/show_bug.cgi?id=37864 Bug ID: 37864 Summary: When I resize a maximized MDI window it assumes the new size instead of remaining maximized Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryampolsky(a)yahoo.com Distribution: --- Created attachment 50431 --> https://bugs.winehq.org/attachment.cgi?id=50431 Screenshot showing a maximized MDI child after resizing 'unmaximizes' it. My app is a 'smart terminal' that supports multiple sessions in MDI windows. The size of the MDI child windows can be changed by the app running on the server, so at the end of each transaction, if the app has changed the window dimenensions, I resize the window. If my MDI window is maximized, this has no effect on a Windows system (except that if I later unmaximize the MDI child, it will display at the correct new size). But on recent WINE builds (Linux and Mac), when I resize the MDI child, the window assumes the new size, even though it's techincally in the 'mdi maximized' state (i.e., the MDI buttons are still there on the menubar. If I switch between MDI children, they get redrawn correctly maximized (including the one I just resized). I coded a workaround in my app where I don't resize the window if it's maximized, and that seems to work okay under WINE (though I guess the new size info is getting lost). In any case, that verifies that the problem is definitely happening in response to my resize operation. F.Y.I., my resize operation uses SetWindowPlacement() to change the position and size of the window - specifically because I don't want it to affect the window if it's minimized or maximized. Only if it's in the normal state. It's been a long time since I wrote this code, but again, it's always worked on all versions of Windows. I have a feeling it might have worked a while back in WINE - though I rarely run maximized, so I may have just recently noticed a bug that's always been there... Here's the basic code logic. SizeWindowForScreenDimentions calls SetWindowPlacement based on the size calculated for the new row/column grid. The code below has the workaround that prevents the problem in WINE. Also attached a screenshot showing the unmaximized children with the MDI buttons still on the menubar. // If base screen dimensions don't match prior dimensions, resize the window here. // (unless mdi-maximized, in which case, doing this unmaximizes in WINE) if (!mdi_maximized) { if ((rows != old_rows) || (cols != old_cols)) { SizeWindowForScreenDimensions(scr, rows, cols, &resizeable); } } // In case window was hidden under an initial popup, show it now. ShowWindow(scr->hScreenWnd, SW_SHOW); -- 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.

2 4

[Bug 7007] putty 0.60 window does not resize when wm resizes it
by WineHQ Bugzilla 30 May '24

30 May '24

https://bugs.winehq.org/show_bug.cgi?id=7007 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imwellcushtymelike(a)gmail.co | |m --- Comment #21 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- This seems to work for me with Wine 9.9. Can someone else check this? -- 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.

1 0

[Bug 52515] New: Resizing/maximizing foobar2000 has stale rendering errors (more in Light Blue theme)
by WineHQ Bugzilla 30 May '24

30 May '24

https://bugs.winehq.org/show_bug.cgi?id=52515 Bug ID: 52515 Summary: Resizing/maximizing foobar2000 has stale rendering errors (more in Light Blue theme) Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: nyanpasu64(a)tuta.io Distribution: --- Created attachment 71815 --> https://bugs.winehq.org/attachment.cgi?id=71815 Screenshot of list header, scrollbar, and resize handle rendering incorrectly - Install foobar2000 v1.6.9. - (optional) In winecfg, switch to Light Blue theme, then open foobar2000. - In "Quick Appearance Setup", pick "Album List + Properties". - Add some files to the playback list (preferably enough for a vertical scrollbar). - (Optional) Press Ctrl+N to show playlist tabs. - Resize and enlarge the window slowly horizontally. Then shrink the window horizontally, and tile or maximize the window (expanding it quickly). When resizing the window slowly, you will get vertical lines in the sort header, and stale resize handles in the window's bottom right corner (faintly visible). When maximizing the window, a scrollbar will mistakenly render in the song list (which remains when resizing the window further, moves when you scroll the song list, and gets cleared when you select/deselect the songs behind it). I also saw entire stale tabs to the right of real tabs, but was unable to replicate this bug. On (No Theme) and Light "Classic Blue", when maximizing, the glitched scrollbar rendering occurs as well. When resizing slowly, the stale resize handles are *more* visible, but the vertical lines do not occur. Confirmed on Xfce and KDE Plasma X11, with X11/Wine running at 96 and 120 DPI. Video at https://youtu.be/jch76UQpn2w. I assume this is a Wine rendering bug, but perhaps it could be a foobar2000 redrawing bug, or an interaction between Wine and foobar2000's redraw events. Operating System: Arch Linux Kernel Version: 5.16.4-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 (proprietary drivers 470.103.01) -- 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.

1 12

[Bug 53805] New: Photoshop is crashing... and it's annoying.
by WineHQ Bugzilla 29 May '24

29 May '24

https://bugs.winehq.org/show_bug.cgi?id=53805 Bug ID: 53805 Summary: Photoshop is crashing... and it's annoying. Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: choord(a)protonmail.com Distribution: --- Created attachment 73312 --> https://bugs.winehq.org/attachment.cgi?id=73312 This is only the backtrace gived by WineHQ I want to use Photoshop with Wine, as it is the only program I really know well about. I come from Windows and I really need help because I can use a little bit Photoshop, but after some minutes, or on clicking on some buttons (it can be random), the application just crash, which make it useless for making picture editing. Thanks for your reply, and if you know how to fix this problem, please reply to my email adress ! (choord(a)protonmail.com) -- 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.

1 3

[Bug 56742] New: testfont fails by selecting Noto Sans instead of Tahoma
by WineHQ Bugzilla 29 May '24

29 May '24

https://bugs.winehq.org/show_bug.cgi?id=56742 Bug ID: 56742 Summary: testfont fails by selecting Noto Sans instead of Tahoma Product: Mono Version: main Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: libgdiplus Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com CC: madewokherd(a)gmail.com Distribution: --- Test output: testfont: testfont.c:897: verifyFontFamily: Assertion `stringsEqual (name, expectedName) || stringsEqual (name, alternateExpectedName)' failed. FAIL testfont (exit status: 134) The expected font names are "Tahoma" or "DejaVu Sans". The font is created with the name "Tahoma". Some extra debug code revealed that the actual font returned was "Noto Sans". I couldn't find any special cases for either font in the code, so I'm not sure how this is expected to work (particularly the fallback to DejaVu Sans). -- 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.

1 0

[Bug 56741] New: Rise of the Tomb Raider stuck on loading screen
by WineHQ Bugzilla 29 May '24

29 May '24

https://bugs.winehq.org/show_bug.cgi?id=56741 Bug ID: 56741 Summary: Rise of the Tomb Raider stuck on loading screen Product: Wine Version: 9.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- When starting a new game or continue savegame 07a0:err:d3d:wined3d_debug_callback 00007F9BB59F8DF0: "GL_INVALID_OPERATION in glTexParameter(immutable texture)". 07a0:err:d3d:wined3d_debug_callback 00007F9BB59F8DF0: "GL_INVALID_ENUM in glTexBufferRange(internalFormat GL_RGB10_A2)". 07a0:err:d3d:wined3d_debug_callback 00007F9BB59F8DF0: "GL_INVALID_OPERATION in glIsTextureHandleResidentARB(handle)". 07a0:err:d3d:wined3d_debug_callback 00007F9BB59F8DF0: "GL_INVALID_OPERATION in glMakeTextureHandleResidentARB(handle)". 9.9-173-ga3b22d3bf7f -- 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.

1 0

[Bug 56712] New: Vampire: The Masquerade - Bloodlines intro videos are not displayed
by WineHQ Bugzilla 29 May '24

29 May '24

https://bugs.winehq.org/show_bug.cgi?id=56712 Bug ID: 56712 Summary: Vampire: The Masquerade - Bloodlines intro videos are not displayed Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: accounts.winehq.org(a)vv221.fr Distribution: --- The introduction videos of Vampire: The Masquerade - Bloodlines are played with a black screen. Video is not rendered, but audio is played. Starting the game in a virtual desktop does not help, it only replaces the black screen with the blue background of the virtual desktop. The videos can still be skipped, so this does not prevent reaching the game menu and starting a game. All GStreamer plugins are installed (base, good, ugly, bad, libav). Despite the bug metadata being set to WINE 9.8, the current 9.9 build is affected too (but is not proposed when opening a new bug report). This behaviour has been noticed on a Wayland setup with an AMD GPU and Mesa drivers. I should be able to try reproducing it on X.org and with nVIDIA non-free drivers too, I will report back once it is done. The videos used to be played correctly on the same computer, but I would need to run more tests to ensure this is a WINE regression and not a Mesa or GStreamer one. -- 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.

1 11

[Bug 56735] New: Rekordbox: Mark drive as external to support library export/sync
by WineHQ Bugzilla 28 May '24

28 May '24

https://bugs.winehq.org/show_bug.cgi?id=56735 Bug ID: 56735 Summary: Rekordbox: Mark drive as external to support library export/sync Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johannespfau(a)gmail.com Distribution: --- Created attachment 76513 --> https://bugs.winehq.org/attachment.cgi?id=76513 Registry keys for patched wine to report drive as external Hello all, to support library syncing in rekordbox (rekordbox.com), a drive must be recognized as an external device. Rekordbox uses a combination of GetVolumeInformationW/GetDriveTypeW/QueryDosDeviceW and setupapi to detect if a drive is external. I've filed individual bug reports for the sub-problems involved: * Specify filesystem type for folder-backed drives: https://bugs.winehq.org/show_bug.cgi?id=56731 * setupapi: Registry information for drives missing: https://bugs.winehq.org/show_bug.cgi?id=56732 * setupapi: SPDRP_PHYSICAL_DEVICE_OBJECT_NAME not implemented: https://bugs.winehq.org/show_bug.cgi?id=56734 * GetDriveTypeW aways returns DRIVE_FIXED: https://bugs.winehq.org/show_bug.cgi?id=16091 I've attached a reduced test-case program (in D) and compiled which performs all steps that are required by rekordbox. Please note that the program is dumb and assumes that a R drive exists. Unpatched wine output: ---------------------------------------------------------------------------------------- GetVolumeInformationW: Path: USB_STICK Name: FAT32 Serial: 2923885786 Len: 255 Flag: 2 GetDriveTypeW: 3 QueryDosDeviceW: \Device\HarddiskVolume3 Querying SetupAPI DeviceSet is 6FFEE0. Valid: true std.windows.syserror.WindowsException(a)test.d(43): No more data available. (error 259) ---------------------------------------------------------------------------------------- Patched wine + usb_final.reg output: ---------------------------------------------------------------------------------------- GetVolumeInformationW: Path: USB_STICK Name: FAT32 Serial: 2923885786 Len: 255 Flag: 2 GetDriveTypeW: 2 QueryDosDeviceW: \Device\Harddisk1 Querying SetupAPI DeviceSet is 8506C0. Valid: true Entry: 0 SetupDiGetDeviceRegistryPropertyW 1 \Device\Harddisk1 std.windows.syserror.WindowsException(a)test.d(43): No more data available. (error 259) ---------------------------------------------------------------------------------------- Windows output: ---------------------------------------------------------------------------------------- GetVolumeInformationW: Path: USB_STICK Name: FAT32 Serial: 2923885786 Len: 255 Flag: 131590 GetDriveTypeW: 2 QueryDosDeviceW: \Device\HarddiskVolume2 Querying SetupAPI DeviceSet is 456B80. Valid: true Entry: 0 SetupDiGetDeviceRegistryPropertyW 1 \Device\HarddiskVolume2 Entry: 1 SetupDiGetDeviceRegistryPropertyW 1 \Device\HarddiskVolume1 std.windows.syserror.WindowsException(a)test.d(43): No more data available. (error 259) ---------------------------------------------------------------------------------------- As a workaround / proof-of-concept, my patched branch here has some minor changes that enable this to work: https://github.com/jpf91/proton-wine/commits/Proton8-26/# In addition to this patched wine, you will also need to load the attached usb_final.reg file. Then create a symlink for the r drive: ---------------------------------------------------------------------------------------- cd $WINEPREFIX/dosdevices ln -s /run/media/jpfau/USB_STICK r: ---------------------------------------------------------------------------------------- This should be enough to get library sync to an external device working in Rekordbox. Best Johannes -- 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.

1 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs May 2024