February 2017 - Wine-bugs - list.winehq.org

[Bug 42413] New: NVIDIA Closed Drivers 256/ 8bpp Colour mode near Impossible with Current Workarounds.
by wine-bugs＠winehq.org 15 Feb '17

15 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42413 Bug ID: 42413 Summary: NVIDIA Closed Drivers 256/8bpp Colour mode near Impossible with Current Workarounds. Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: oiaohm(a)gmail.com Distribution: --- The workarounds to use 256/8bpp documented here https://wiki.winehq.org/256_Color_Mode of Xephyr, Xnest and Xinit do not work when using Nvidia binary drivers even basic glxinfo test will fail out with XLib unable to access GLX of course for wine wanting to use opengl this is now in trouble. The VNC suggestion leads users into the path of what VNC server some of those no longer work with 8bpp. https://www.x.org/wiki/Releases/7.8/ As noted here all of Xepher and Xnest are marked for future replacement by xf86-video-nested that may or may not fix the issue. Don't say use open source drivers because Nvidia has habit of not releasing firmware to do basic things like correctly run the cooling fans so the open source drivers are very limited use. Same applies to other closed source drivers. Nvidia is the most common desktop driver with this issue. Of course attempting to run wine on Android and the like the project will not be promised that the closed source drivers will support 8bpp mode directly. Solution could be inbuilt support for handling 8bpp mode. The hardware these days is 24/32 bit so it is possible for a future closed source driver to be missing the 16bpp randr modes as well. So while developers are looking at making 8bpp mode work without having to change screen to 8bpp adding support to-do the same with 16bpp would be good future proofing. Running application inside virtual desktop mode would be acceptable as this is like what using Xephr or Xnest are like this where they work. Basically wine project has got away with colour depth not be a problem the project has had to worry about. Problem is the systems that allowed this fact have failed for a decent percentage of users. I do suspect implementing from what has been said will cause stability problems so this could be a feature that has to start life in the staging branch. This is me reporting a bug from a support point of view. I am basically stuffed giving people advice how to make 256/8bpp applications in wine when they have NVIDIA closed source without some change. Also connecting every application with a 8bpp colour mode would be insane. -- 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 39002] New: ISAXXMLParser ignores charset property
by wine-bugs＠winehq.org 12 Feb '17

12 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=39002 Bug ID: 39002 Summary: ISAXXMLParser ignores charset property Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: ott(a)mirix.org Distribution: --- ISAXXMLParser (or its implementation in Wine to be correct) tries to detect the encoding of documents with xmlDetectCharEncoding and some custom heuristics in internal_parseBuffer and uses xmlDetectCharEncoding without additional heuristics through xmlCreatePushParserCtxt in internal_parseStream which violates the specification: "This setting [charset property] takes priority over the default encoding, which is implicitly UTF-16, or over the encoding specified in the byte order mark (BOM) of the XML document header." (https://msdn.microsoft.com/en-us/library/ms757826%28v=vs.85%29.aspx) Moreover, ISAXXMLParser returns E_NOTIMPL when setting the charset property. It should at least accept ASCII, UTF-8 and UTF-16 as these encoding are detected by internal_parseBuffer and internal_parseStream anyways and are supported by libxml2. A better option would be to support all enconding supported by Wine and reencode them as UTF-8 (when possible) and supply the UTF-8 encoding data to libxml2 via custom IO callbacks. -- 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 15084] New: ReadConsoleInputW() handles a NULL lpNumberOfEventsRead parameter incorrectly
by wine-bugs＠winehq.org 12 Feb '17

12 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=15084 Summary: ReadConsoleInputW() handles a NULL lpNumberOfEventsRead parameter incorrectly Product: Wine Version: 1.1.3 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dg(a)cowlark.com On the Windows console, if I try to read input events with ReadConsoleInputW() and pass in NULL as the pointer to the lpNumberOfEventsRead field, wine completes successfully where Windows XP fails and returns an error code. -- 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.

1 12

[Bug 42383] New: certmgr.exe is unable to import certificate in PKCS12 format
by wine-bugs＠winehq.org 12 Feb '17

12 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42383 Bug ID: 42383 Summary: certmgr.exe is unable to import certificate in PKCS12 format Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: info(a)winomega.com Distribution: --- Created attachment 57178 --> https://bugs.winehq.org/attachment.cgi?id=57178 error message Microsoft Certificate Manager Tool (certmgr.exe) is unable to import PKCS12 files. When this is attempted it failed with following error: "The file format is not recognized. Please select another file." I'm using the 32-bit version as published in Microsoft Visual Studio 2017 (freely downloadable). Its md5sum is: 322bf8029866cf3eb7f1de33f18fb07a certmgr.exe -- 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 42431] New: Video memory stew is displayed when in 3d rendering mode of Image Analysis
by wine-bugs＠winehq.org 11 Feb '17

11 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42431 Bug ID: 42431 Summary: Video memory stew is displayed when in 3d rendering mode of Image Analysis Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: Ubuntu After some use Image Analysis starts to display not the pieces of memory it have rendered the surface to, but some other memory: you can see there stew of pieces of another applications windows', own application window, pieces of surface and garbage. If GalliumNine is enabled the probability to see the stew increases. After you saw stew usually you can't make it render normally without app restart. How to reproduce: 1 download Image Analysis http://downloads.ntmdt.com/windows/nanoeducator/Image_Analysis-3.5.0.2066.e… 2 Check SHA256: 609ca31f719412f7905990bd0d9120c48ee02ec03c9dc91d1f4a6fd3c4b4200e 3 Install it. 4 Run it. 5 Load there anything it supports. For example you can drag there any BMP or JPEG image. PNG is not supported. 6 Click 3d at the bottom, rotate the surface, switch back to 2d. 7 Play with app a bit. 8 Switch to 3d again. 9 Enjoy the video memory stew. -- 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 1

[Bug 42429] New: BricsCad: Tricks "kidnapped" window focus
by wine-bugs＠winehq.org 11 Feb '17

11 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42429 Bug ID: 42429 Summary: BricsCad: Tricks "kidnapped" window focus Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tolikk91(a)yandex.ru Distribution: --- Created attachment 57258 --> https://bugs.winehq.org/attachment.cgi?id=57258 console_output When you move the toolbar, the window focus on the Transfer tooltip, as if she were separate containers for graphical window. -- 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 2

[Bug 40034] New: Trying to run a setup.exe from an installation disk for a linksys usb wireless adapter and it immediately opens the program error screen.
by wine-bugs＠winehq.org 11 Feb '17

11 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=40034 Bug ID: 40034 Summary: Trying to run a setup.exe from an installation disk for a linksys usb wireless adapter and it immediately opens the program error screen. Product: Wine Version: 1.9.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alyssianagrace(a)gmail.com Distribution: --- Created attachment 53486 --> https://bugs.winehq.org/attachment.cgi?id=53486 program error details report as generated by wine by pressing the 'show details' button on the program error screen Basically what it says in my summary. I inserted the disk into my disk drive and then had to navigate to the CD-ROM (I'm currently using Parrot Security OS if that matters). I right-clicked on the setup.exe and selected for it to run with 'a wine program'. When that opened the error code, I tried the other instance of 'a wine program', and then 'rundll32' and got the same error message. Attached is the backtrace.txt Wine generated when I tried 'rundll32'. Any help is appreciated but please note that I am very new to this OS and Wine. -- 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 45

[Bug 9221] Force Feedback doesn' t work but does after little source modification
by wine-bugs＠winehq.org 11 Feb '17

11 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #47 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- (In reply to Bruno Jesus from comment #44) > (In reply to madbad82 from comment #43) > > Created attachment 57205 [details] > > backtrace > > > > Backtrace of "wine control" with the experimental KLGDFF Logitec driver > > There are some well-known crashes in joy.cpl but since my controllers don't > support the other effects I can't reproduce myself so it is good that you > can test this. If you are able to compile Wine I can attach some patches. > > Anyway, please attach a +dinput patch when playing with all effects > sequentially. This is probably the same issue as described in https://www.winehq.org/pipermail/wine-devel/2014-March/103293.html (the out-of-scope problem). -- 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 8563] MechWarrior 4: Vengeance fails to start
by wine-bugs＠winehq.org 11 Feb '17

11 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=8563 --- Comment #42 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still there with current wine (tested with the demo https://archive.org/details/Mechwarrior4MercenariesDemo ) -- 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 42419] New: Dragon Ball Xenoverse 2 duplicate entry
by wine-bugs＠winehq.org 10 Feb '17

10 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42419 Bug ID: 42419 Summary: Dragon Ball Xenoverse 2 duplicate entry Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: winetest(a)luukku.com Distribution: --- https://appdb.winehq.org/objectManager.php?sClass=application&iId=17863 https://appdb.winehq.org/objectManager.php?sClass=application&iId=17873 -- 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 2