November 2015 - Wine-bugs - list.winehq.org

[Bug 39366] New: FILE_ATTRIBUTE_READONLY and FILE_ATTRIBUTE_HIDDEN should perhaps use BSD flags
by wine-bugs＠winehq.org 19 Sep '22

19 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=39366 Bug ID: 39366 Summary: FILE_ATTRIBUTE_READONLY and FILE_ATTRIBUTE_HIDDEN should perhaps use BSD flags Product: Wine Version: 1.7.9 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: guy(a)alum.mit.edu 4.4-Lite introduced per-file flags, which show up as the st_flags field of "struct stat" and can be set with the chflags() and fchflags() calls. For plain files, the UF_IMMUTABLE flag corresponds pretty closely to the Windows FILE_ATTRIBUTE_READONLY flag. OS X added the UF_HIDDEN flag. so that its kernel SMB client could report the Windows FILE_ATTRIBUTE_HIDDEN flag to userland. It might be useful for Wine to, on systems with the st_flags field in "struct stat" and the chflags() call, to report that a file is read-only if UF_IMMUTABLE is set, even if the file's permissions allow reading, and to set UF_IMMUTABLE as well as turning read permissions off if FILE_ATTRIBUTE_READONLY is set. (You probably want to turn off file permissions in case the file is on a server; the server might not support setting that flag if, for example, it's an NFS server.) On OSes that have them *and* that have UF_HIDDEN, the same (modulo file permissions) should perhaps be done for FILE_ATTRIBUTE_HIDDEN. This has been discussed in the past; see the thread starting at https://www.winehq.org/pipermail/wine-devel/2009-October/079038.html (It might also be worth looking at supporting NT ACLs on UN*Xes that have NT-style ACLs; OS X's ACLs are NT-style, and other UN*Xes might support them even if they call them NFSv4-style ACLs.) -- 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 15396] New: program doesn't draw text to dialog box properly
by wine-bugs＠winehq.org 18 Sep '22

18 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=15396 Summary: program doesn't draw text to dialog box properly Product: Wine Version: 1.1.5 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: deadlock(a)start.no Created an attachment (id=16248) --> (http://bugs.winehq.org/attachment.cgi?id=16248) Dialog box being drawn the wrong way When I try to save or load a game in The Journeyman Project 3 - Legacy of Time, the snapshoot is shown behind the dialog box, along with any text written on the dialog box. The same happens with any other dialog box in the game that shows text. It's like the function the game uses to draw, draws on the wrong layer. -- 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 13

[Bug 29443] New: Savestates not working in DeSmuME (the keyboard command is not being processed)
by wine-bugs＠winehq.org 13 Sep '22

13 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=29443 Bug #: 29443 Summary: Savestates not working in DeSmuME (the keyboard command is not being processed) Product: Wine Version: 1.3.35 Platform: x86 URL: http://desmume.org/download/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: cvoeten(a)gmail.com Classification: Unclassified I have no idea why this is not working, but every kind of input imaginable works, except for anything having to do with savestates. To reproduce: 1) Download DeSmuME: http://desmume.org/download/ 2) Download a ROM, for example from here: http://hive.ndshb.com/index.php/component/jdownloads/finish/4/183 3) run 'wine DeSmuME.exe' 4) File->Open ROM and select the ROM 5) Press F1 Expected result: an error message "Failed to load slot 1" is displayed. What happens: nothing. Remapping the 'load savestate 1' function to a regular key, say the letter E, does not make it work. I know this reeks of being an app-specific bug, but it works in Windows. As to the cause I can only speculate (and I'm not a programmer), however the only remotely reasonable explanation *I* can come up with is that perhaps the savestate actions are processed upon a key release event being recieved, whereas the other in-game keypresses are processed differently. But that's pure speculation, I haven't looked at the actual code (read: I don't have the skills to read it). -- 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 5

[Bug 24705] New: Unhandled page fault on write access to address in 32-bit code.
by wine-bugs＠winehq.org 10 Sep '22

10 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=24705 Summary: Unhandled page fault on write access to address in 32-bit code. Product: Wine Version: 1.3.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: publio.escipion.el.africano(a)gmail.com Created an attachment (id=31216) --> (http://bugs.winehq.org/attachment.cgi?id=31216) wine execution output, with debbuging information. The present issue affect wine-1.1.28 & wine-1.3.4, and, I guess, the versions between. The application is an educational software, available from: http://static.cedeti.cl/software/sl/SuenaLetrasInstalador_mx.exe My SO is: openSuSE 11.2 x86_64 + Updates, which relevant specifications are: Linux **** 2.6.31.14-0.1-desktop #1 SMP PREEMPT 2010-09-17 11:32:00 +0200 x86_64 x86_64 x86_64 GNU/Linux GNU bash, version 4.0.35(1)-release (x86_64-suse-linux-gnu) The problem takes place after the installation, when the program is launched. Wine complained: "wine: Unhandled page fault on write access to 0x00000000 at address 0x******** (thread ****), starting debugger... Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x********)." I also saw calls, or paths with character codification (MS Windows ISO-8859-1 or ISO-8859-15 vs. Linux UTF-8) issues. But I do not know if this is a relevant part of the problem, or simply a noise. Every thing is collected in the file attached. I do not know whether this information be enough so you might solve it, or whether it requires a workaround configuration to make it run. Thank you. -- 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 34277] New: Far2 file manager crashes on start up
by wine-bugs＠winehq.org 10 Sep '22

10 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=34277 Bug #: 34277 Summary: Far2 file manager crashes on start up Product: Wine Version: 1.7.0 Platform: x86 URL: http://www.farmanager.com/history/far2.x86.msi OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Classification: Unclassified Created attachment 45633 --> http://bugs.winehq.org/attachment.cgi?id=45633 backtrace In recent versions of Wine, Far 2 can no longer start. Half a year ago it worked just fine. It's a regression. $ wineconsole --backend=user Far.exe fixme:storage:create_storagefile Storage share mode not implemented. fixme:iphlpapi:NotifyAddrChange (Handle 0x152e8f0, overlapped 0x152e8fc): stub fixme:heap:HeapSetInformation 0x110000 0 0x33fdfc 4 *** glibc detected *** Far.exe: double free or corruption (!prev): 0x7cb5ef08 *** ======= Backtrace: ========= -- 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 22

[Bug 36644] New: regedit: user interface does not scale with dpi setting
by wine-bugs＠winehq.org 10 Sep '22

10 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=36644 Bug ID: 36644 Summary: regedit: user interface does not scale with dpi setting Product: Wine Version: 1.7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aerilius(a)googlemail.com Created attachment 48684 --> http://bugs.winehq.org/attachment.cgi?id=48684 Screenshot of regedit When setting the dpi to a higher value (2× = 192dpi, 2.5× = 240dpi), many user interface elements have inconsistent dimensions and font sizes. This heavily affects usability. • menu and context menues are too small • +/- expanders are too small to click, they seem not to render properly • column widths are by default too narrow • scrollbars are too small • statusbar is too small • slider grip (in winecfg) is too small • icons are too small While there are also visual inconsistencies on Windows itself, these elements are at least at usable sizes on Windows 7+. This affects also explorer.exe, notepad.exe, and third-party applications as well (though they might use different UI libraries), like 7-zip file manager, etc. -- 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 6

[Bug 36955] New: X-Com: Interceptor fails to start combat mode when 3D acceleration enabled
by wine-bugs＠winehq.org 10 Sep '22

10 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=36955 Bug ID: 36955 Summary: X-Com: Interceptor fails to start combat mode when 3D acceleration enabled Product: Wine Version: 1.7.22 Hardware: x86 URL: http://www.fileplanet.com/11584/10000/fileinfo/X-Com:- Interceptor-Demo OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com This is an old Directx5 game from 1998. When hardware acceleration enabled and the game switches to combat mode an error message is shown: 'ERROR: Can't get Direct3D Device2' Software rendering works. Terminal output: fixme:win:EnumDisplayDevicesW ((null),0,0x32f418,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:ddraw:d3d_device_create Only one Direct3D device per DirectDraw object supported. fixme:ddraw:ddraw7_FlipToGDISurface iface 0x1e35f0 stub! Steps to reproduce the problem with the demo: 1. unpack and install the demo, start the game with Interceptor.exe 2. go to <Settings> and select a 3D capable device 3. Singleplay -> choose difficulty -> OK -> Close 4. turn on time acceleration, click on the rightmost icon (24hours) under the globe on the right. 5. Launch mission -> select a plane -> activate time acceleration again until combat mode will be available Fedora 20 Nvidia binary drivers 340.24 -- 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 6

[Bug 37019] New: Summoner: Direct3D error at launch
by wine-bugs＠winehq.org 09 Sep '22

09 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=37019 Bug ID: 37019 Summary: Summoner: Direct3D error at launch Product: Wine Version: 1.7.23 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: ipickert55(a)gmail.com The Direct3d error states: Error: No Direct3D devices found! File: D:\projects\Summoner\pccode\vsdk\gr\directx\gr_direct3d.cpp - Line: 1061 A critical error has occurred and the program cannot continue -- 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 21

[Bug 27243] New: Wiggles: All renderers are unsupported
by wine-bugs＠winehq.org 09 Sep '22

09 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=27243 Summary: Wiggles: All renderers are unsupported Product: Wine Version: 1.3.19 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=34825) --> (http://bugs.winehq.org/attachment.cgi?id=34825) Wiggles Settings Window Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko 3) install Wiggles 4) patch Wiggles with Wiggles_Patch_1_0_844.exe 4) wine SetMode.exe Behaviour: All renderers are marked as unsupported which is not true. OK button is always grayed out. (see attachment) Expected behaviour: All renderers should be marked as supported. OK button shouldn't be always grayed out. Terminal output: fixme:ddraw:DirectDrawEnumerateExA flags 0x00000007 not handled fixme:win:EnumDisplayDevicesW ((null),0,0x32e7a4,0x00000000), stub! -- 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 18

[Bug 11999] New: Endless Online game window appears as white texture
by wine-bugs＠winehq.org 09 Sep '22

09 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=11999 Summary: Endless Online game window appears as white texture Product: Wine Version: CVS/GIT Platform: PC URL: http://files.endless-online.com/EOsetup028.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Created an attachment (id=11336) --> (http://bugs.winehq.org/attachment.cgi?id=11336) Terminal output with d3d traces. Using Wine version wine-0.9.57-84-g9ab07d5, launching the application simply results in a white screen without any UI elements shown. Attached are d3d traces and additional terminal output. -- 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 23