wine-bugs September 2011

wine-bugs@winehq.org

1 participants
9380 discussions

[Bug 20636] New: Can't get a COM-object's properties (App: Cardiris), workaround: winetricks dcom98
by wine-bugs＠winehq.org 23 Feb '15

23 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=20636 Summary: Can't get a COM-object's properties (App: Cardiris), workaround: winetricks dcom98 Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ld(a)gardschwingdoazah.de Created an attachment (id=24614) --> (http://bugs.winehq.org/attachment.cgi?id=24614) Debug trace of failed run; failing property is "CodePage" This is a problem with the application Cardiris v3.5 by I.R.I.S. (business card recognition). The application itself (interactive) runs well, the problem is only with the COM API. I'm accessing it through a piece of plain C code. The code *works* on Windows XP, *works* on wine 1.1.32 with dcom98 installed through winetricks, but *doesn't work* with wine 1.1.32 with builtin dcom. The COM works in general, I can create an application object and call methods on it, but on another object (returned by a method call), access to any property results in the following error: Object doesn't support this property or method: 'CodePage' (Note: Property name is spelled correctly, any other property doesn't work either.) Attaching a debug trace with WINEDEBUG=+comcat,+ole (hope that combination makes sense), but I will gladly produce any other required debug trace -- just let me know which WINEDEBUG setting you need. -- 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 8

[Bug 21573] New: Need heap overrun detection at beginning of buffers, too
by wine-bugs＠winehq.org 23 Feb '15

23 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=21573 Summary: Need heap overrun detection at beginning of buffers, too Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com On Linux, valgrind gives nice warnings when you access before the first byte. It'd be nice if valgrinding Windows apps under Wine gave the same warnings. For instance, the following program should give three warnings under valgrind+wine just as it does under valgrind: #include <stdio.h> #include <stdlib.h> int badness_before_n_after ( char* p ) { return p[-1] + p[10]; } int main ( void ) { char* p = malloc(10); int who_knows = badness_before_n_after(p); // expect 2 x invalid address yelpage who_knows += p[5]; if (who_knows == 42) printf("It's 42 (!)\n"); else printf("It's not 42 (dull but unsurprising)\n"); free(p); return 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.

1 4

[Bug 16264] New: Builtin Tahoma unreadable when small
by wine-bugs＠winehq.org 23 Feb '15

23 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=16264 Summary: Builtin Tahoma unreadable when small Product: Wine Version: 1.1.9 Platform: Other URL: http://www.linuxtechs.net/kruch/tb/forum/viewtopic.php?t =2152&postdays=0&postorder=asc&start=15 OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: fonts AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user said that ConvWPT ran in Wine, but gave a very complicated recipe, so I tried simplifying it. Along the way, I noticed that ConvWPT's installer used teeny tiny nearly unreadable fonts; installing Tahoma fixed that (now they're just small, but readable). Recipe to reproduce: 1) Visit http://www.linuxtechs.net/kruch/tb/forum/viewtopic.php?t=2152 scroll down to message "Setup Package Part 1 / 4", and download and unpack each of the four files Setup.part1.rar, Setup.part2.rar, ... Setup.part4.rar Ignore warnings from rar about duplicate files. 2) Run the resulting setup.exe The setup program uses small Tahoma text on some screens, and that's very nearly unreadable unless you install native tahoma, e.g. with winetricks tahoma. -- 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 21082] New: Artrage3 studio pro demo : export fails
by wine-bugs＠winehq.org 23 Feb '15

23 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=21082 Summary: Artrage3 studio pro demo : export fails Product: Wine Version: 1.1.35 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: meho_r(a)yahoo.com Created an attachment (id=25286) --> (http://bugs.winehq.org/attachment.cgi?id=25286) Output of terminal when running AR3 from it. Export function in ArtRage 3 Studio Pro Demo version (as well as in full version) doesn't work. When trying to export a painting as an image, an error occurs which states: "Generic Failure. Not enough memory to perform action." However, it is not lack of RAM that is the cause of problem (at the time of testing I had over 2GB free RAM). Also, in ArtRage 2.5 export function works as expected on the same machine. I tested this on Ubuntu 9.10 (64bit) and Mandriva 2010.0 (32bit) with multiple versions of wine (from 1.0.1 to 1.1.3.5). -- 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 13

[Bug 11926] New: House of the dead 3 won' t draw 3d stuff after the 1st level
by wine-bugs＠winehq.org 21 Feb '15

21 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=11926 Summary: House of the dead 3 won't draw 3d stuff after the 1st level Product: Wine Version: 0.9.57. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugz(a)chipsugar.plus.com After the first level where everything is fine all the 3d models & scenery is black. Possibly textures aren't being rendered. Also the words in the menu list when starting the game don't get drawn. Maybe that's part of the same bug. -- 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 24

[Bug 28524] New: urlmon:url test case is ok after the 2nd attempt
by wine-bugs＠winehq.org 20 Feb '15

20 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=28524 Bug #: 28524 Summary: urlmon:url test case is ok after the 2nd attempt Product: Wine Version: 1.3.29 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: toralf.foerster(a)gmx.de Classification: Unclassified I'm wondering why repeatedly often the 1st attempt failed and 2nd works (sometimes it works even in at the 1st attempt) : tfoerste@n22 ~/devel/wine-git/dlls/urlmon/tests $ rm *.ok tfoerste@n22 ~/devel/wine-git/dlls/urlmon/tests $ make test ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so generated.c && touch generated.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so misc.c && touch misc.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so protocol.c && touch protocol.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so sec_mgr.c && touch sec_mgr.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so stream.c && touch stream.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so uri.c && touch uri.ok ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so url.c && touch url.ok url.c:1804: Test failed: binding failed: 800c0019, expected 00000000 url.c:2884: Test failed: IMoniker_BindToStorage failed: 800c0019 url.c:2885: Test failed: unk == NULL url.c:2887: Test failed: Expected security problem to be ignored. make: *** [url.ok] Error 4 tfoerste@n22 ~/devel/wine-git/dlls/urlmon/tests $ make test ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so url.c && touch url.ok -- 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 7

[Bug 28470] New: qmgr tests deadlock with WINEDEBUG=warn+heap on slower machines
by wine-bugs＠winehq.org 20 Feb '15

20 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=28470 Summary: qmgr tests deadlock with WINEDEBUG=warn+heap on slower machines Product: Wine Version: 1.3.28 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: qmgr AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com On my e8400, when run with WINEDEBUG=warn+heap, the qmgr conformance tests seem to lock up very frequently. Here's a backtrace gotten with btall: Backtracing for thread 0034 in process 0008 (Z:\home\dank\wine-git\dlls\qmgr\tests\qmgr_test.exe): Backtrace: =>0 GLIBC_2+0x830() in ld-linux.so.2 (0x0043e738) 1 ReadFile+0x265(hFile=0x4c, buffer=0x43e86c, bytesToRead=0x10, bytesRead=0x43e80c, overlapped=(nil)) [dlls/kernel32/file.c:439] 2 rpcrt4_conn_np_read+0x3c(Connection=0x12c080, buffer=0x43e86c, count=0x10) [dlls/rpcrt4/rpc_transport.c:420] 3 RPCRT4_receive_fragment+0xb4(Connection=0x12c080, Header=0x43e96c, Payload=0x43e908) [dlls/rpcrt4/rpc_binding.h:177] 4 RPCRT4_ReceiveWithAuth+0x7c(Connection=0x12c080, Header=0x43e96c, pMsg=0x33fb54, auth_data_out=(nil), auth_length_out=0x0(nil)) [dlls/rpcrt4/rpc_message.c:1396] 5 I_RpcReceive+0x7b(pMsg=0x33fb54) [dlls/rpcrt4/rpc_message.c:1553] 6 I_RpcSendReceive+0x7f(pMsg=0x33fb54) [dlls/rpcrt4/rpc_message.c:1911] 7 rpc_sendreceive_thread+0x23(param=0x12d134) [dlls/ole32/rpc.c:794] 8 worker_thread_proc+0xe1(param=0x0(nil)) [dlls/ntdll/threadpool.c:114] 9 call_thread_func+0xb() in ntdll (0x0043ea78) 10 call_thread_entry_point+0x6d(entry=0x7bc7ec30, arg=0x0(nil)) [dlls/ntdll/signal_i386.c:2499] 11 start_thread+0xf7(info=0x7ffd4fb8) [dlls/ntdll/thread.c:405] Backtracing for thread 0009 in process 0008 (Z:\home\dank\wine-git\dlls\qmgr\tests\qmgr_test.exe): Backtrace: =>0 GLIBC_2+0x830() in ld-linux.so.2 (0x0033f228) 1 NTDLL_wait_for_multiple_objects+0x232(count=0x2, handles=0x33f4a8, flags=0x4, timeout=(nil), signal_object=<?>) [dlls/ntdll/sync.c:1124] 2 NtWaitForMultipleObjects+0x5a(count=0x2, handles=0x33f4a8, wait_all=0, alertable=0, timeout=(nil)) [dlls/ntdll/sync.c:1162] 3 WaitForMultipleObjectsEx+0xee(count=0x2, handles=0x33f67c, wait_all=0, timeout=0xffffffff, alertable=0) [dlls/kernel32/sync.c:188] 4 nulldrv_MsgWaitForMultipleObjectsEx+0x31(count=0x2, handles=0x33f67c, timeout=0xffffffff, mask=0x4ff, flags=0) [dlls/user32/driver.c:359] 5 wait_message+0x47(count=0x2, handles=0x33f67c, timeout=0xffffffff, mask=0x4ff, flags=0) [dlls/user32/winproc.c:1126] 6 MsgWaitForMultipleObjectsEx+0x109(count=0x1, pHandles=0x12d154, timeout=0xffffffff, mask=0x4ff, flags=0) [dlls/user32/message.c:3944] 7 CoWaitForMultipleHandles+0xd6(dwFlags=0, dwTimeout=0xffffffff, cHandles=0x1, pHandles=0x12d154, lpdwindex=0x33f91c) [dlls/ole32/compobj.c:3712] 8 ClientRpcChannelBuffer_SendReceive+0x5fb(iface=0x12c220, olemsg=0x33fb54, pstatus=0x33f96c) [dlls/ole32/rpc.c:903] 9 NdrProxySendReceive+0x71(This=0x12d02c, pStubMsg=0x33fa74) [dlls/rpcrt4/cproxy.c:487] 10 IRemUnknown_RemRelease_Proxy+0x1c6(This=0x12d02c, cInterfaceRefs=0x1, InterfaceRefs=0x33fbd4) [dlls/ole32/dcom_p.c:639] 11 ifproxy_release_public_refs+0xe3(This=0x12c190) [dlls/ole32/marshal.c:673] 12 ifproxy_destroy+0x24(This=0x12c190) [dlls/ole32/marshal.c:708] 13 ClientIdentity_Release+0xc8(iface=0x12b940) [dlls/ole32/marshal.c:1109] 14 IUnknown_Release_Proxy+0x65(iface=0x12c1f4) [dlls/rpcrt4/cproxy.c:418] 15 func_enum_files+0x179() [dlls/qmgr/tests/enum_files.c:98] 16 run_test+0x143(name="enum_files.c") [dlls/qmgr/tests/../../../include/wine/test.h:556] 17 main+0x161(argc=0x33f248, argv=0x682a6a9f) [dlls/qmgr/tests/../../../include/wine/test.h:624] >From the second stack, it looks like it was just trying to tear down the test. Race condition and/or reference count problem, perhaps? -- 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 3

[Bug 28503] New: comctl32/treeview.ok fails occasionally
by wine-bugs＠winehq.org 20 Feb '15

20 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=28503 Summary: comctl32/treeview.ok fails occasionally Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This failed just now on Austin's buildslave with WINEDEBUG=warn+heap: ../../../tools/runtest -q -P wine -M comctl32.dll -T ../../.. -p comctl32_test.exe.so treeview.c && touch treeview.ok treeview.c:1512: Test failed: got 0x20318a treeview.c:1518: Test failed: got 0x20318a and again on his buildslave without WINEDEBUG: treeview.c:1512: Test failed: got 0x201c8b treeview.c:1518: Test failed: got 0x201c8b I see it's happened at least once before, last month, to someone else: http://test.winehq.org/data/6ee95c77381791299ae040248897ac58c74f49f6/linux_… and I think I recall seeing it one other time on the buildbot (not sure which slave). Austin's buildslave's info: os: Debian GNU/Linux testing (wheezy), 3.0.0-1-686-pae, , Advanced Linux Sound Architecture Driver Version 1.0.24. ram: 8113 MB cpu: AMD Phenom(tm) II X4 940 Processor gpu: GeForce 9800 GTX+/PCI/SSE2/3DNOW! 3.3.0 NVIDIA 285.03 It's possible this is caused by someone playing with the mouse or keyboard while the tests are running, but seeing it twice in a row is suspicious. -- 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 7

[Bug 28323] New: urlmon/tests/protocol.ok slightly flaky: protocol.c:2892: Test failed: ref=2
by wine-bugs＠winehq.org 20 Feb '15

20 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=28323 Summary: urlmon/tests/protocol.ok slightly flaky: protocol.c:2892: Test failed: ref=2 Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: urlmon AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com I've seen this twice in two days: ../../../tools/runtest -q -P wine -M urlmon.dll -T ../../.. -p urlmon_test.exe.so protocol.c && touch protocol.ok ... protocol.c:979: Test failed: unexpected call ReportResult protocol.c:984: Test failed: hrResult = 80004004, expected: 00000000 protocol.c:989: Test failed: dwError == ERROR_SUCCESS protocol.c:2892: Test failed: ref=2 protocol.c:746: Test failed: unexpected call ReportProgress_CONNECTING This time, it was with WINEDEBUG=warn+heap, on a system with: os: Ubuntu 10.04.3 LTS, 2.6.32-33-generic, pulseaudio 0.9.21-63-gd3efa-dirty, Advanced Linux Sound Architecture Driver Version 1.0.21. ram: 3212 MB cpu: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz gpu: GeForce GT 240/PCI/SSE2 3.2.0 NVIDIA 195.36.24 I see a few vaguely similar problems on windows at http://test.winehq.org/data/tests/urlmon:protocol.html so perhaps these tests still need some love. -- 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 3

[Bug 28298] New: riched20/editor.ok cursort position test flaky
by wine-bugs＠winehq.org 20 Feb '15

20 Feb '15

http://bugs.winehq.org/show_bug.cgi?id=28298 Summary: riched20/editor.ok cursort position test flaky Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com I just had a test fail (under WINEDEBUG=warn+heap, but I doubt that matters) like this: ../../../tools/runtest -q -P wine -M riched20.dll -T ../../.. -p riched20_test.exe.so editor.c && touch editor.ok ... editor.c:6026: Test failed: Cursor is at 0 instead of 8 That's not a new problem; it was mentioned back in http://www.winehq.org/pipermail/wine-devel/2008-September/069299.html and showed up here: http://www.winehq.org/pipermail/wine-devel/2010-December/088198.html -- 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 8

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 September 2011