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

[Bug 11847] New: Adobe Acrobat Pro 7 -- How To window does not work
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

http://bugs.winehq.org/show_bug.cgi?id=11847 Summary: Adobe Acrobat Pro 7 -- How To window does not work Product: Wine Version: 0.9.56. Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jens(a)porup.com On start, Acrobat Pro shows a How To window on the right side of the screen. It can also be accessed from Help --> How To --> How To Window. Currently this does not work -- clicking on any topic shows a blank window. -- 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 36

[Bug 36554] New: valgrind shows a definite leak in ieframe/tests/intshcut.c
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

https://bugs.winehq.org/show_bug.cgi?id=36554 Bug ID: 36554 Summary: valgrind shows a definite leak in ieframe/tests/intshcut.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M ieframe.dll -p ieframe_test.exe.so intshcut && touch intshcut.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ole:CoCreateInstance Class {fbf23b40-e3f0-101b-8488-00aa003e56f8} does not support aggregation fixme:ieframe:UniformResourceLocatorA_SetUrl ignoring unsupported flags 0x1 fixme:ieframe:UniformResourceLocatorA_SetUrl ignoring unsupported flags 0x1 preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 fixme:ntdll:NtLockFile I/O completion on lock not implemented yet err:menubuilder:wWinMain failed to build menu item for L"C:\\users\\austin\\Temp\\testshortcut.url" ==13135== 256 bytes in 1 blocks are definitely lost in loss record 484 of 669 ==13135== at 0x7BC4C75D: notify_alloc (heap.c:255) ==13135== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==13135== by 0x5240855: IMalloc_fnAlloc (ifs.c:186) ==13135== by 0x5241170: CoTaskMemAlloc (objidl.h:1236) ==13135== by 0x692E9A0: get_profile_string (intshcut.c:429) ==13135== by 0x692ED1D: PersistFile_Load (intshcut.c:473) ==13135== by 0x4648C58: Process_URL (objidl.h:5279) ==13135== by 0x464A11D: wWinMain (winemenubuilder.c:3701) ==13135== by 0x464A869: wmain (exe_wmain.c:51) ==13135== by 0x464A744: __wine_spec_exe_wentry (exe_wentry.c:36) ==13135== by 0x7B864247: ??? (process.c:1045) ==13135== by 0x7B864394: start_process (process.c:1097) ==13135== by 0x7BC87137: ??? (signal_i386.c:2571) ==13135== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==13135== by 0x7BC87115: ??? (signal_i386.c:2571) ==13135== by 0x7BC5A270: start_process (loader.c:2856) ==13135== by 0x401D03C: ??? (port.c:60) ==13135== -- 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 4

[Bug 9875] New: moving dialogs shows artifacts on window behind it
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

http://bugs.winehq.org/show_bug.cgi?id=9875 Summary: moving dialogs shows artifacts on window behind it Product: Wine Version: 0.9.46. Platform: PC URL: http://ftp.ldscatalog.com/PAF5AllLangs.exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: wine-x11driver AssignedTo: wine-bugs(a)winehq.org ReportedBy: cjstimpson(a)utwire.net Start PAF, and go to the "Family" view. Open any dialog in PAF, or any other application that makes a new top level window. When moving that window around, it leaves trails of itself on the family view in PAF. I have to minimize PAF and restore it or equivalent to get the window to refresh itself. If you move the window slowly, one pixel at a time, it doesn't happen. I put some printouts in X11DRV_Expose() and BeginPaint() and noticed that when the two are called in turn, things are fine. If X11DRV_Expose is called twice or more before BeginPaint() for the family view, the trails start showing up. Any ideas out there? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 17

[Bug 11835] New: Adobe Acrobat Pro 7 -- Comments don't work
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

http://bugs.winehq.org/show_bug.cgi?id=11835 Summary: Adobe Acrobat Pro 7 -- Comments don't work Product: Wine Version: 0.9.56. Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jens(a)porup.com Before I report this bug, a HUGE thanks to everyone for getting Acrobat Pro 7 to install!! I now have 80-90% functionality in Linux. Yay! Now, the bug: The Comment fields do not work properly. First, when I open an existing pdf document with Comments, and click on the Comments tab at the bottom left corner of the screen, the text of the existing comments is not shown. (The username is shown, but not the comment.) Hovering the mouse cursor over the comment does bring a popup yellow window that reveals the comment. Also, creating a new comment fails. It creates the comment, but the text is not saved, so when you go back to the comment you just created, the text has vanished. This is obviously a show stopper for those of us who need to use the comments functionality. happy to provide debug logs, please let me know what command line switches will be most useful in this instance. cheers! -- 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 38

[Bug 33066] New: resident evil 6 pc benchmark Black screen
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

http://bugs.winehq.org/show_bug.cgi?id=33066 Bug #: 33066 Summary: resident evil 6 pc benchmark Black screen Product: Wine Version: 1.5.24 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: levanchelidze(a)gmail.com Classification: Unclassified Created attachment 43712 --> http://bugs.winehq.org/attachment.cgi?id=43712 Terminal output I managed to start this game with help of this gentleman http://bugs.winehq.org/show_bug.cgi?id=33057#c6 But know I am getting black screen http://i.imgur.com/Timb2Qw.png -- 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 25

[Bug 38216] New: Wrong screen in Civilization V with new engines. Good with old 1.7.18.
by wine-bugs＠winehq.org 13 Jan '17

13 Jan '17

https://bugs.winehq.org/show_bug.cgi?id=38216 Bug ID: 38216 Summary: Wrong screen in Civilization V with new engines. Good with old 1.7.18. Product: Wine Version: 1.7.38 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 51009 --> https://bugs.winehq.org/attachment.cgi?id=51009 Screen with engine 1.7.36 I got Civilization V working with engines up to 1.7.18. Screenshot attached. But with new engines 1.7.36, 1.7.38 initial screen is broken. Screenshot attached too. Log differences are in those lines: 1.7.36 fixme:d3dx:D3DXLoadSurfaceFromMemory Format conversion missing 0x33545844 -> 0x33545844 fixme:d3dx:D3DXLoadSurfaceFromMemory Format conversion missing 0x35545844 -> 0x35545844 fixme:d3dx:D3DXLoadSurfaceFromMemory Format conversion missing 0x35545844 -> 0x35545844 while not in 1.7.18 -- 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 48

[Bug 37116] New: Audio Reset Failed with TextAloud MP3 1.459 + AT&T Natural Voices 1.4
by wine-bugs＠winehq.org 12 Jan '17

12 Jan '17

https://bugs.winehq.org/show_bug.cgi?id=37116 Bug ID: 37116 Summary: Audio Reset Failed with TextAloud MP3 1.459 + AT&T Natural Voices 1.4 Product: Wine Version: 1.7.24 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: porparek(a)gmail.com Created attachment 49346 --> https://bugs.winehq.org/attachment.cgi?id=49346 wine.log with channels +tid,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio,+seh,+msgbox Hi I use TextAloud MP3 version 1.459 with AT&T Natural Voices (Mike voice) version 1.4 (any other 1.x version of TextAloud MP3 I tested is vulnerable). I receive periodically the following error popup window: "Audio Reset Failed: Access violation at address 7BC4DDFA in module 'ntdll.dll'. Write of address F82A011C" The message is the same every time. The addresses are also the same. When it occurs the audio hangs up and only the restart of the wine application helps. I use 64-bit Arch Linux and run 32 bit wine applications. Wine version is wine 1.7.24 (32 bit). The /proc/<wine app's PID>/maps is as follows. I can see that memroy region ffbd0000-ffbf0000 is not writtable. 7bc00000-7bc10000 r-xp 00000000 08:02 13247900 /usr/lib32/wine/ntdll.dll.so 7bc10000-7bc11000 r-xp 00000000 00:00 0 7bc11000-7bcc6000 r-xp 00011000 08:02 13247900 /usr/lib32/wine/ntdll.dll.so 7bcc6000-7bcc7000 r--p 000c5000 08:02 13247900 /usr/lib32/wine/ntdll.dll.so 7bcc7000-7bcd1000 rwxp 000c6000 08:02 13247900 /usr/lib32/wine/ntdll.dll.so f7707000-f7709000 r--p 00000000 00:00 0 f7709000-f770a000 r-xp 00000000 00:00 0 [vdso] f7710000-ffa10000 ---p 00000000 00:00 0 ffa19000-ffa3a000 rw-p 00000000 00:00 0 ffa40000-ffbf0000 ---p 00000000 00:00 0 ffbf0000-ffff0000 rwxp 00000000 00:00 0 wine.log with the following channels enabled has been attached to this bug. +tid,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio,+seh,+msgbox wine.log contains all the information from the moment wine starts until the moment when "Audio Reset Failed" popup window occurs. I found that adding "+relay" channel causes a bug not to reproduce. I suspect that it is because writing to a wine.log file takes to much time what causes the delays between "read" and "stop" become too long. dmesg sound related entries are: snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X sound hdaudioC0D0: autoconfig: line_outs=1 (0x12/0x0/0x0/0x0/0x0) type:line sound hdaudioC0D0: speaker_outs=1 (0x13/0x0/0x0/0x0/0x0) sound hdaudioC0D0: hp_outs=1 (0x11/0x0/0x0/0x0/0x0) sound hdaudioC0D0: mono: mono_out=0x0 sound hdaudioC0D0: inputs: sound hdaudioC0D0: Mic=0x14 sound hdaudioC0D0: Line=0x15 input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input5 input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6 input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7 input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8 input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 lsmod sound related entries are: snd_hda_codec_analog 9595 1 snd_hda_codec_generic 56366 1 snd_hda_codec_analog snd_hda_intel 22831 0 snd_hda_controller 22975 1 snd_hda_intel snd_hda_codec 104665 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_controller,snd_hda_codec_analog snd_hwdep 6652 1 snd_hda_codec snd_pcm_oss 41901 0 snd_mixer_oss 14598 1 snd_pcm_oss snd_pcm 83207 4 snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_controller snd_timer 19294 1 snd_pcm snd 61276 9 snd_pcm_oss,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_mixer_oss,snd_hda_codec_analog soundcore 5551 2 snd,snd_hda_codec The sound card is Integrated High Definition audio with ADI1884 codec, 3D audio compliant with AC'97 Rev. 2.3. The computer is HP COMPAQ DC7800. The steps to reproduce a bug are as follows: - activate the Mike's AT&T voice - use keybord shortcuts to navigate the speech. Press read (ctrl+f) and stop (ctrl+d) and then read and stop speaking and so on a few times in a sequense. The delays between read, stop, read, stop etc. should be as short as possible (e.g. 1 second). This is why the keyboard shortcuts are necessary. It takes me about a minute to reproduce a bug. One may also use read, pause (ctrl+g), pause, pause etc. sequence to reproduce it. The delay between actions should also be about 1 second. Be aware that TextAlound starts reading but after a while it fails. It is not like it is silent and does not read anything. -- 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 38103] New: Process Hacker 2.x needs ntoskrnl.exe.ProbeForRead
by wine-bugs＠winehq.org 11 Jan '17

11 Jan '17

https://bugs.winehq.org/show_bug.cgi?id=38103 Bug ID: 38103 Summary: Process Hacker 2.x needs ntoskrnl.exe.ProbeForRead Product: Wine Version: 1.7.36 Hardware: x86 URL: http://processhacker.sourceforge.net/downloads.php OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 38102 Distribution: --- Created attachment 50771 --> https://bugs.winehq.org/attachment.cgi?id=50771 patch +++ This bug was initially created as a clone of Bug #38102 +++ You'll need winetricks comctl32 to work around bug 34465. I used the portable binaries. Extract, run the x86 version, then Hacker > Computer > Shutdown. Restart the program, you'll see several: wine: Call from 0x7b83957c to unimplemented function ntoskrnl.exe.ProbeForRead, aborting wine: Call from 0x7b83957c to unimplemented function ntoskrnl.exe.ProbeForRead, aborting austin(a)debian-home:~$ sha1sum processhacker-2.33-bin.zip 2738c909fa6b37a22a4aa256e5d7e733449b905e processhacker-2.33-bin.zip austin(a)debian-home:~$ du -h processhacker-2.33-bin.zip 2.7M processhacker-2.33-bin.zip austin(a)debian-home:~$ wine --version wine-1.7.36-28-ga679cae -- 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 9

[Bug 12707] New: some winemenubuilder processes never exit
by wine-bugs＠winehq.org 11 Jan '17

11 Jan '17

http://bugs.winehq.org/show_bug.cgi?id=12707 Summary: some winemenubuilder processes never exit Product: Wine Version: 0.9.51. Platform: PC URL: http://wiki.winehq.org/AdobePhotoshop OS/Version: Linux Status: UNCONFIRMED Keywords: download, regression Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com I noticed with Adobe Photoshop 6, the installer running in silent mode with the '/s /SMS /w' switches would never finish. It turns out its waiting for the winemenubuilder processes for Adobe Photoshop 6.0.lnk and Adobe ImageReady 3.0.lnk. Those two processes are stuck in WaitForParentProcess(). This started happening between Wine 0.9.50 and 0.9.51. Git bisect says: f65e04770dc5748521a0de73814cea0b085bf3f8 is first bad commit commit f65e04770dc5748521a0de73814cea0b085bf3f8 Author: Rob Shearman <rob(a)codeweavers.com> Date: Fri Nov 30 18:06:07 2007 +0000 ole32: Always create a window for the main apartment. PS 5.5 is affected as well, with different .lnk files. -- 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 5

[Bug 38032] New: "Broken NVIDIA RandR detected" warning needs improvement
by wine-bugs＠winehq.org 11 Jan '17

11 Jan '17

https://bugs.winehq.org/show_bug.cgi?id=38032 Bug ID: 38032 Summary: "Broken NVIDIA RandR detected" warning needs improvement Product: Wine Version: 1.7.36 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- This relates to bug #34348 "Wine xrandr12 failure", which concerns nVidia proprietary drivers not adhering to expected RandR 1.0+ behaviour. Until nVidia addresses the problems preventing Wine from using RandR 1.3 reliably for its intended purpose, Wine warns the user that it is falling back to RandR 1.0 as a workaround. It does this by printing the following warning message very frequently: "Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead." (line 488 of dlls/winex11.drv/xrandr.c as of 1.7.36) The user is reminded of this every time winex11.drv is loaded, which is apparently quite frequently - even for command-line applications. Due to the overuse of the warning, it comes off very strong and may cause unnecessary worry. It may also present annoyances for developers looking through future bug reports that are filled with this message. I suggest this situation can be improved by the following two proposals: 1. this only be printed the first time winex11.drv is loaded. 2. the message changed to point to a wiki page or man page with a short description of the problem, or even the URL of bug #34348. eg. "Broken NVIDIA RandR detected, falling back to RandR 1.0. Please refer to http://wiki.winehq.org/RandR" This would allow users to understand what has happened and decide for themselves what course of action should be taken. Otherwise, I don't think a user will get a sufficient level of understanding from one line of text, and (unlike most Wine output) this one is aimed at the user and not so much at developers debugging something. -- 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 10