September 2006 - Wine-bugs - list.winehq.org

[Bug 6159] New: DeviceLock installer crashes in NdrSendReceive()
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6159 Summary: DeviceLock installer crashes in NdrSendReceive() Product: Wine Version: 0.9.20. Platform: PC URL: http://www.protect-me.com/dl/download.html (Europe) OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: saulius.krasuckas(a)elst.vtu.lt I run it in silent mode (/s), but that happens during interactive setup too. Setup app should install DeviceLock Service for Windows NT/2000/XP/2003, but crashes with following output: $ ./wine dlock/setup.exe /s fixme:win:LockWindowUpdate ((nil)), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! fixme:actctx:CreateActCtxW 0x33d30c 00000088 fixme:rpc:RpcBindingSetAuthInfoExW unsupported AuthnLevel 0 fixme:rpc:RpcMgmtSetComTimeout (0x1634b8, 0): stub wine: Unhandled exception 0x000006d9 at address 0x7ee98d80 (thread 0009), starting debugger... This may be an important part for searching in bug DB: Backtrace: =>1 0x7ee98e0b RaiseException+0x8b(code=0x6d9, flags=0x0, nbargs=0x0, args=0x0) [...dlls/kernel/except.c:85] in kernel32 (0x7ee98e0b) 2 0x7dbc55cb RpcRaiseException+0x1f(exception=0x6d9) [...dlls/rpcrt4/rpcrt4_main.c:209] in rpcrt4 (0x7dbc55cb) 3 0x7dbb83a5 NdrSendReceive+0xe5(stubmsg=0x33cec8, buffer=0x16aa90) [...dlls/rpcrt4/ndr_midl.c:315] in rpcrt4 (0x7dbb83a5) 4 0x7dbba54d NdrClientCall2+0xb79(pStubDesc=0x18444a0, pFormat=0x1843786) [...dlls/rpcrt4/ndr_stubless.c:935] in rpcrt4 (0x7dbba54d) 5 0x0182fdaa in dli (+0x4fdaa) (0x0182fdaa) 6 0x0182e6ef in dli (+0x4e6ef) (0x0182e6ef) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6152] Lineage 2 complains about DirectX version
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6152 ------- Additional Comments From jan.wine(a)zerebecki.de 2006-07-09 04:27 ------- No don't install native dx. I suspect it's because of registry entries from an older version. Try if rerunning wineprefixcreate help and/or does this happen with a fresh .wine (move or delete the old one)? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 4951] Fixme errors in FireWorks Install
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=4951 truiken(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From truiken(a)gmail.com 2006-07-09 01:17 ------- This is fixed in CVS. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 4770] BlackBerry Device Manager fails to install under wine
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=4770 ------- Additional Comments From truiken(a)gmail.com 2006-07-09 00:02 ------- Created an attachment (id=3554) --> (http://bugs.winehq.org/attachment.cgi?id=3554&action=view) +ole,+typelib,+rpc,+msi,+relay log only between the custom action RIM_CheckForDesktopDowngrade -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 4770] BlackBerry Device Manager fails to install under wine
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=4770 truiken(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rob(a)codeweavers.com AssignedTo|truiken(a)gmail.com |wine-bugs(a)winehq.org Status|ASSIGNED |NEW Component|wine-msi |wine-ole ------- Additional Comments From truiken(a)gmail.com 2006-07-09 00:01 ------- I believe this is an ole bug. Some interesting parts of the log: trace:rpc:RPCRT4_MakeBinding (RpcBinding == ^0x7d973a74, Connection == ^0x19d258) trace:rpc:RPCRT4_MakeBinding binding: 0x19d330 trace:rpc:RPCRT4_Receive (0x19d258, 0x7d973a78, 0x19d2f8) warn:rpc:RPCRT4_Receive Short read of header, -1 bytes warn:rpc:RPCRT4_io_thread receive failed with error 6c0 trace:rpc:RPCRT4_DestroyConnection connection: 0x19d258 trace:rpc:RPCRT4_CloseConnection (Connection == ^0x19d258) and then the custom action fails. Nothing else happens during the custom action. I'll attach the log. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 6158] Wine build uses the wrong libwine.so file
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6158 ------- Additional Comments From docbill+bugzilla(a)freeshell.org 2006-06-09 21:27 ------- Created an attachment (id=3553) --> (http://bugs.winehq.org/attachment.cgi?id=3553&action=view) the compile error I was seeing before applying my patch This is the compiler error I was seeing before applying my patch I had the 0.9.7 version of wine installed at the time. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6158] Wine build uses the wrong libwine.so file
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6158 ------- Additional Comments From docbill+bugzilla(a)freeshell.org 2006-06-09 21:20 ------- Created an attachment (id=3552) --> (http://bugs.winehq.org/attachment.cgi?id=3552&action=view) proposed patch to fix the problem This is the patch I used to fix the problem. winegcc.c has the usage of -lwine hardcoded, which is why it had to be patched as well. My patch is probably not sufficient for all platforms, as I assume a .so extension. I do not know if wine is build on platforms with use different extensions for libwine. However, I expect this patch is sufficient for wine developers to see the problem and understand how to fix it. Bill -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6158] New: Wine build uses the wrong libwine.so file
by Wine Bugs 07 Sep '06

07 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6158 Summary: Wine build uses the wrong libwine.so file Product: Wine Version: 0.9.20. Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-tools AssignedTo: wine-bugs(a)winehq.org ReportedBy: docbill+bugzilla(a)freeshell.org I have been investigating why whenever I attempted to upgrade Wine that my build would fail with unresolved symbols, even though it apparently works for thousands of others without problems. I finally figured out the problem is the build will use the version of libwine.so previously installed, instead of the new version of libwine.so from the source code being built. The fundamental flaw in the build process is the path to the shared library is specified as: -L$(TOPBUILDDIR)/libs/wine -lwine However, this simply appends $(TOPBUILDDIR)/libs/wine to the library paths and does not guarentee that libwine.so will be taken from that path. In fact quite the opposite, if an old version of libwine.so has already been installed in the standard library path, that version will be used instead. I have verified this bug has existed in the last few releases of wine (probabyl much longer) and the current snapshots. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6149] The printout of 2 proprietary applications does not fit on the paper
by Wine Bugs 06 Sep '06

06 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6149 wine.dev(a)web.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev(a)web.de ------- Additional Comments From wine.dev(a)web.de 2006-06-09 17:37 ------- Strange, that wineps get's "DefaultResolution = 0" during ParsePPD, but i have no Idea, if this affect the Output. I added a cups-pdf - Printer with "HP LaserJet 5M Postscript (recommended)" as Driver and got "DefaultResolution = 600". I suggest to use an A4-Printer as default (The PPD from your Lexmark E312 has "DefaultPageSize: Letter") Can you please Retry with the Driver from cups-pdf. Vendor: "Generic" Driver: "postscript color printer rev3b" The Log-Size can be reduced with: "grep --line-number -v WriteSpool full.log >smaller.log" When the app uses the default Print-Dialog (+commdlg) and the Checkmark "Redirect to a File" is disable or hiden, you can modify "dlls/comdlg32/printdlg.c" to display and Enable them (983,985,1132,1134: PD_DISABLEPRINTTOFILE and PD_HIDEPRINTTOFILE) Another way to redirect the Postscript-Code is a simple Reg-Key in : "HKEY_CURRENT_USER\Wine\Printing\Spooler" Add a String with the Portname ("LPR:lexmark" as example) as Name and the full Unix-Path as Value You can also overwrite the PPD-File for a Printer: "HKEY_CURRENT_USER\Wine\Printing\PPD Files" Add a String with the Printername ("lexmark" as example) as Name and the full Unix-Path to the PPD-File as Value Is the Output different, when using "generic.ppd" from Wine? -- By by ... Detlef -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6087] Reopen Secure-Nexus Mailclient don't work on editing or creating emails!
by Wine Bugs 06 Sep '06

06 Sep '06

http://bugs.winehq.org/show_bug.cgi?id=6087 ------- Additional Comments From xerox_xerox2000(a)yahoo.co.uk 2006-06-09 16:13 ------- It might be better to find out what causes the run time error. Run something like WINEDEBUG=+tid,+seh,+relay wine Memo.exe &> /tmp/relay.log && \ grep -A 20 -B 5000 "MessageBox" /tmp/relay.log > /tmp/relay.txt && bzip2 /tmp/relay.txt and attach the relay.txt.bz2 to this bug, so people can have a look at it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0