wine-bugs September 2008

wine-bugs@winehq.org

1 participants
5258 discussions

[Bug 14035] New: Microsoft Virtual Earth 3D beta installer fails to download .net framework
by wine-bugs＠winehq.org 14 Feb '21

14 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=14035 Summary: Microsoft Virtual Earth 3D beta installer fails to download .net framework Product: Wine Version: CVS/GIT Platform: Other URL: http://www.microsoft.com/Downloads/details.aspx?FamilyID =e9298080-50c4-4f2e-9fc4-4009074996ba&displaylang=en OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: wininet AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com To get past bug 11517, do 'winetricks gdiplus'. The next problem is it fails downloading .net 2.0 sp1. The installer offers to show you a log, but can't find the log itself when you ask; it's really at ~/.wine/dosdevices/c:/windows/temp/VirtualEarth3DInstallLog.txt and it says [2008/06/21 12:35:44.709] DownloadManager: HTTP Status String: 'OK' for 'http://go.microsoft.com/fwlink/?LinkId=87970' [2008/06/21 12:35:44.710] DownloadManager: HttpQueryInfo(HTTP_QUERY_CONTENT_LENGTH) failed for 'http://go.microsoft.com/fwlink/?LinkId=87970' (System Error Code: 12150 (unknown), WinInet Error Code: 12150 ()) +wininet shows trace:wininet:HTTP_GetResponseHeaders raw headers: L"HTTP/1.1 200 OK\r\nContent-Length: 24758792\r\nContent-Type: application/octet-stream\r\nLast-Modified: Thu, 08 Nov 2007 00:36:49 GMT\r\nAccept-Ranges: bytes\r\nETag: \"dfcf19739f21c81:8037\"\r\nServer: Microsoft-IIS/6.0\r\nX-Powered-By: ASP.NET\r\nDate: Sat, 21 Jun 2008 12:45:10 GMT\r\nConnection: k"... ... trace:wininet:HttpQueryInfoW Attribute: HTTP_QUERY_CONTENT_LENGTH Modifier: HTTP_QUERY_FLAG_NUMBER trace:wininet:HTTP_GetCustomHeaderIndex L"Content-Length" trace:wininet:HTTP_GetCustomHeaderIndex Return: -1 trace:wininet:HttpQueryInfoW 0 <-- 001a:Ret wininet.HttpQueryInfoW() retval=00000000 ret=00404710 So we can't retrieve content-length for some reason, even though we've received 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 8

[Bug 14697] New: wineserver: debug events can block completion of queued user APCs
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=14697 Summary: wineserver: debug events can block completion of queued user APCs Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, consider the following scenario... A debugger is attached to a debuggee. The debuggee has two threads. The debugger processes debug events and queries virtual memory info of remote process using VirtualQueryEx in its main loop. VirtualQueryEx -> NtQueryVirtualMemory -> enqueues APC_VIRTUAL_QUERY user APC for remote process (debuggee). The calling thread is blocked until the APC is completed. Following is the "good" case: tid=0009 (debugger process, calling thread, main debugger loop) tid=001a (debuggee thread 1) --- snip --- .. 0009: queue_apc( thread=(nil), process=0x54, call={APC_VIRTUAL_QUERY,addr=0x7fff0000} ) 001a: *wakeup* signaled=192 cookie=0x7ffdb7b4 0009: queue_apc() = 0 { handle=0x68, self=0 } 0009: select( flags=4, cookie=0x32d30c, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x68} ) 0009: select() = PENDING { apc_handle=(nil), timeout=infinite, call={APC_NONE} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=(nil), timeout=1c8f097946d2824 (-0.1787600), result={}, handles={} ) 001a: select() = USER_APC { apc_handle=0x68, timeout=1c8f097946d2824 (-0.1787600), call={APC_VIRTUAL_QUERY,addr=0x7fff0000} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=0x68, timeout=1c8f097946d2824 (-0.1792110), result={APC_VIRTUAL_QUERY,status=40000002,base=(nil),alloc_base=(nil),size=0,state=0,prot=0,alloc_prot=0,alloc_type=0}, handles={} ) 0009: *wakeup* signaled=0 cookie=0x32d30c 001a: select() = PENDING { apc_handle=(nil), timeout=1c8f097946d2824 (-0.1792110), call={APC_NONE} } 0009: get_apc_result( handle=0x68 ) 0009: get_apc_result() = 0 { result={APC_VIRTUAL_QUERY,status=40000002,base=(nil),alloc_base=(nil),size=0,state=0,prot=0,alloc_prot=0,alloc_type=0} } --- snip --- Now the interesting one, which ultimately leads to block of calling thread ... tid=0009 (debugger process, calling thread, main debugger loop) tid=001a (debuggee thread 1) tid=001b (debuggee thread 2) --- snip --- 0009: continue_debug_event( pid=0019, tid=001a, status=65538 ) 001a: *wakeup* signaled=258 cookie=0x7ffdb7b4 001b: *wakeup* signaled=258 cookie=0x7ffd77b4 0009: continue_debug_event() = 0 .. 0009: read_process_memory( handle=0x54, addr=0x7ffd8000 ) 001a: *signal* signal=19 0009: read_process_memory() = 0 { data= {} } 0009: read_process_memory( handle=0x54, addr=0x7ffd4000 ) 001a: *signal* signal=19 0009: read_process_memory() = 0 { data={} } 0009: queue_apc( thread=(nil), process=0x54, call={APC_VIRTUAL_QUERY,addr=(nil)} ) 001b: *wakeup* signaled=192 cookie=0x7ed44874 0009: queue_apc() = 0 { handle=0x68, self=0 } 001a: load_dll( handle=(nil), base=0x61090000, size=102400, dbg_offset=0, dbg_size=0, name=0x13e468, filename=L"C:\\windows\\system32\\msacm32.dll" ) 001a: *sent signal* signal=10 001b: *sent signal* signal=10 001a: load_dll() = 0 .. 0009: select( flags=4, cookie=0x32d30c, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x68} ) 0009: select() = PENDING { apc_handle=(nil), timeout=infinite, call={APC_NONE} } 001a: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context= {...}) 001a: set_thread_context() = 0 { self=1 } 001b: select( flags=4, cookie=0x7ed44874, signal=(nil), prev_apc=(nil), timeout=infinite, result={}, handles={0x4c} ) 001b: select() = USER_APC { apc_handle=0x68, timeout=infinite, call={APC_VIRTUAL_QUERY,addr=(nil)} } 001a: select( flags=4, cookie=0x7ffdb7b4, signal=(nil), prev_apc=(nil), timeout=0, result={}, handles={} ) 001a: select() = PENDING { apc_handle=(nil), timeout=1c8f09794c8b694 (+0.0000000), call={APC_NONE} } 001b: set_thread_context( handle=0xfffffffe, flags=00010007, suspend=1, context= {...}) 001b: set_thread_context() = 0 { self=1 } 001b: select( flags=4, cookie=0x7ffd77b4, signal=(nil), prev_apc=(nil), timeout=0, result={}, handles={} ) 001b: select() = PENDING { apc_handle=(nil), timeout=1c8f09794c90dc4 (+0.0000000), call={APC_NONE} } ... --- snip --- At this point, tid=0009 (debugger) is blocked forever. When the APC_VIRTUAL_QUERY user APC is queued, remote thread 001b is selected/destined to carry out the APC. After thread 001a and 001b woke up, a dynamic library is loaded from thread 001a which results in LOAD_DLL_DEBUG_EVENT dispatched. This initiates the suspension of all threads in the child process (SIGUSR1 is sent for 001a and 001b). Thread 001a is suspended first, 001b next. The suspension of 001b happens to a time when 001b is about to carry out the APC_VIRTUAL_QUERY. Meanwhile thread 0009 (calling process) is waiting for APC completion result forever because it's blocked by VirtualQueryEx in debugger loop, unable to receive and process any debug event. Regards -- 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 21

[Bug 10249] New: Battlefield2/SafeDisc 4. x and Punkbuster services cause lockup: child processes debugging misconception
by wine-bugs＠winehq.org 11 Feb '21

11 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=10249 Summary: Battlefield2/SafeDisc 4.x and Punkbuster services cause lockup: child processes debugging misconception Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-kernel AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=8876) --> (http://bugs.winehq.org/attachment.cgi?id=8876) WINEDEBUG=-all,+server,+tid,+loaddll,+seh wine ./BF2.exe +fullscreen 0 +szx 800 +szy 600 &>/tmp/debug_pipe Hello, while testing some PunkBuster stuff on popular games, I came across Battlefield 2 which employs SafeDisc 4.x It seems there is a problem with debuggers in chained child processes. Consider following scenario: --- snip process list --- pid threads parent executable (all id:s are in hex) 0000001b 1 00000008 'PnkBstrA.exe' 0000000c 2 00000008 'explorer.exe' 0000000a 2 00000008 '~e5.0001' 00000008 4 00000000 'BF2.exe' --- snip process list --- --- snip thread list --- process tid prio (all id:s are in hex) 0000001b 0000001c 0 0000000c 00000010 0 0000000d 0 0000000a 00000012 0 0000000b 0 00000008 0000001a 1 00000014 15 00000013 0 00000009 0 --- snip thread list --- "BF2.exe" = parent (game) "~e5.0001" = 1st child = SafeDisc 4.x process = "debugger" "PnkBstrA.exe" = 2nd child = PunkBuster Update Service The 1st child acts as debugger for the parent "BF2.exe" and receives all debug events (process, thread creation, dll load/unload...) There are lots of breakpoint events triggered from parent. This is part of SafeDisc 4.x and used for on-the-fly decryption of code sections (child decrypts code of father). When PunkBuster is initialized (loading of pbcl = client, pbag = agent), the following services should get started: PnkBstrA.exe, PnkBstrB.exe and finally the kmode driver PnkBstrK.exe The service process "PnkBstrA.exe" is started from main process "BF2.exe" (which is a debuggee itself). No debug flags (DEBUG_PROCESS | DEBUG_ONLY_THIS_PROCESS) are specified in process creation flags. The debugger (child of parent, receives the process creation event) does not make debugger_attach() to the newly created child process. The child process seems to inherit the state of being a "debuggee": wine server -> new_process -> set_process_debugger( process, parent->debugger ); The parent got its process->debugger from debugger_attach(). This leads to a problem in child process startup code: "dlls/kernel32/process.c:start_process()" checks the PEB->BeingDebugged field and if set, a system breakpoint is encountered before the entry code is called. This breakpoint results in debug event - seen by debugger. Unfortunately this event is _not_ expected by debugger because it didn't expect another debuggee (child) to be created. Ok, long story short solution: If you debug a process by attaching to an already created process, you _must_ treat default debugging flags as if the process has been created with DEBUG_ONLY_THIS_PROCESS, meaning that all childs created by debuggee will NOT automagically become debuggees. Short and (hopefully) acceptable patch snippet: --- snip --- diff --git a/server/debugger.c b/server/debugger.c index a64a17a..c59f3a0 100644 --- a/server/debugger.c +++ b/server/debugger.c @@ -444,6 +444,7 @@ static int debugger_attach( struct process *process, struct thread *debugger ) resume_process( process ); return 0; } + process->create_flags |= DEBUG_ONLY_THIS_PROCESS; return 1; error: --- snip --- And yes, the patch (snippet) works as intended (tm) ;-) Attached for sake of completeness is relevant server trace. Search for "001c:trace:seh:raise_exception code=80000003 flags=0 addr=0x7b870ed8 " to the point where the entry system breakpoint is triggered. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 17

[Bug 13249] New: Putty: Yes/No/Cancel dialog moving with keyboard arrows
by wine-bugs＠winehq.org 10 Feb '21

10 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=13249 Summary: Putty: Yes/No/Cancel dialog moving with keyboard arrows Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: munozferna(a)gmail.com I was trying to create an automated test for putty, and I noticed that there is a problem between the Cancel and No button on a Yes/No/Cancel dialog. There seem to be '2' controls between them when you move through the buttons with the keyboard arrows. This dialog appears when establishing a connection to a server, putty asks for a confirmation to accept rsa2 keys. I also noticed that the OK / Cancel dialog seems to have 'two' more tabs position, so instead of going to OK when you press arrow key on Cancel, it goes 'nowhere' two times. If you use the tab key it seems to work fine. I am currently using wine-1.0-rc1. -- 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 25

[Bug 12263] New: Sketchup Cannot initialize OpenGL - ChoosePixelFormat fails
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=12263 Summary: Sketchup Cannot initialize OpenGL - ChoosePixelFormat fails Product: Wine Version: 0.9.58. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: opengl AssignedTo: wine-bugs(a)winehq.org ReportedBy: gioloi72(a)gmail.com Created an attachment (id=11713) --> (http://bugs.winehq.org/attachment.cgi?id=11713) the console log of wine 0.9.58 launching sketchup In Ubuntu 7.10 Gutsy I have updated wine from 0.9.46 (comes with gutsy) to 0.9.58. In 0.9.46 I was able to run Google Sketchup 6 stable enough to work (only the toolbars and menus don't refresh correctly). After the update to 0.9.58 Sketchup no longer runs and I don't get any error message. Then in the registry key HKEY_CURRENT_USER\Software\Google\SketchUp6\GLConfig\Display\HW_OK changing value from 1 to 0 (It was set to 1 because Sketchup worked with 0.9.46) cause Sketchup to show a popup window with error "Can't initialize OpenGL: ChoosePixelFormat fails" After uninstalling 0.9.58 and reinstalling 0.9.46 Sketchup works again... Excuse my english Attached console log -- 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 12136] New: Sketchup6: crashes on x86-64 right after startup
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=12136 Summary: Sketchup6: crashes on x86-64 right after startup Product: Wine Version: CVS/GIT Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: apersaud(a)lbl.gov Created an attachment (id=11532) --> (http://bugs.winehq.org/attachment.cgi?id=11532) console output from crash Installed openSUSE wine snapshot 0.9.57.20080320 on x86-64. Moved .wine to .wineold. Run "winecfg" to create new clean .wine directory. Downloaded installer for Sketchup (version 6). Run installer (worked without problems). Run Sketchup, wants to install Gecko for html rendering, installs fine. Some openGL problem(?) comes up, which seems to be fixed once I change the registry: HKEY_CURRENT_USER/SOFTWARE/GOOGLE/SKETCHUP6/GLCONFIG/DISPLAY/HW_OK to 0x1 (from 0x0) If I then restart Sketchup the main window pops up, together with two small windows (help and some setup window). In the main window the menu bar is displayed correctly, but the drawing window shows garbage (just white with some odd lines drawn on it, no coordinate system, etc. which is normally displayed). The setup window has a "continue" button, once I press it the application shuts down and a google bug reporting window comes up. Bug reproduces every time I run Sketchup. I attached the console output of "wine c:/.../sketchup.exe" HTH -- 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 11

[Bug 14044] New: Google SketchUp fails to run
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=14044 Summary: Google SketchUp fails to run Product: Wine Version: 1.0.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: brett.jr.alton(a)gmail.com After installing Google SketchUp 6.4.112 (http://filehippo.com/download_google_sketchup/) Google SketchUp failed to run. I've attached the CLI log. -- 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 9

[Bug 11219] New: SketchUp crashes and cripples whole linux system
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=11219 Summary: SketchUp crashes and cripples whole linux system Product: Wine Version: 0.9.53. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: hotmejladress(a)hotmail.com When trying to save in sketchup, the program crashes. After it crashes, wine contionues to write very big .dmp files in the wine c:\windows\temp directory. Theese files are in the order of 1-2 GB! It still autosaves so one can still try to use sketchup, with occational crashes. But these big files add up, suddenly u run out of harddrive, wine continues to write in the background until the computer comes to a standstill. After resetting the computer with the powerbutton, I had trouble even getting linux to start again, cause the disk was so full. On the AppDB there is some guy who prevented theese crashes by commenting out something in the kernel. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 5

[Bug 11954] New: Google Sketchup, Google bug splat never finish sending report.
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=11954 Summary: Google Sketchup, Google bug splat never finish sending report. Product: Wine Version: 0.9.57. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: hotmejladress(a)hotmail.com Created an attachment (id=11279) --> (http://bugs.winehq.org/attachment.cgi?id=11279) output from wine, gooogle bug squash When Google sketchup crashes, which it does frequently, google bug splat starts. If you describe what happens and send a report, bug splat starts transmitting something but will never finish. The little 'sending error report'-window can not be shut down. You have to use the gnome-system monitor to shut down that process. I think this bug should be prioritised so that the google developers see the Sketchup crashes, and can go on to fix the bugs. I attached the 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 11

[Bug 13377] New: SketchUp crashing on first click in drawing window
by wine-bugs＠winehq.org 08 Feb '21

08 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=13377 Summary: SketchUp crashing on first click in drawing window Product: Wine Version: 1.0-rc2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: panagiotis(a)gmail.com Created an attachment (id=13280) --> (http://bugs.winehq.org/attachment.cgi?id=13280) Back trace of SketchUp crashing. After installing SketchUp, I clicked in the main window which caused it to crash immediately. -- 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 6

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 2008