October 2003 - Wine-Bugs - list.winehq.org

[Bug 1795] [wineinstall] requires root user
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1795 ------- Additional Comments From dclark(a)akamail.com 2003-25-10 14:57 ------- This is true for virtually every program a user compiles and installs. Almost always the installation is done as root, and there are very few users that actually audit the source first. We all go on the basis of our trust of the source. Wine does not present present any special risks in this regard, and there is no need to treat it differently from any other compiled program, and long as it is always *executed* as a normal user. -- Configure bugmail: http://bugs.winehq.com/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 1798] New: Keyboard focus to terminal, not the game
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1798 Summary: Keyboard focus to terminal, not the game Product: Wine Version: unspecified Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.com ReportedBy: spmirowski(a)shaw.ca With the latest build of wine, 20031016, I have been able to install games I haven't before. The problem is, that the terminal receives focus 90% of the time, instead of the game making games impossible to play. The games that I have tested so far: Star Trek: Elite Force (plus Expansion), the leaked Doom III alpha Demo, Star Wars: Mystery Of The Sith, and Call of Duty Demo. Elite force is the only game that I haven't had to crash to exit, therefor saved my terminal info: mirostep(a)localhost Star Trek Voyager Elite Force]$ wine stvoy.exe | >> /home/mirostep/wine.txt fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported fixme:xrandr:X11DRV_XRandR_SetCurrentMode Need to update SYSMETRICS after resizing display (now 1280x1024) err:dsound:DirectSoundCreate8 dsound already opened 5555555vhvghdg h^[dt q 1v wvqae^[^[fixme:xrandr:X11DRV_XRandR_SetCurrentMode Need to update SYSMETRICS aft er resizing display (now 1280x1024) fixme:winmm:MMDRV_Exit Closing while ll-driver open [mirostep(a)localhost Star Trek Voyager Elite Force]$ 5555555vhvghdg ht q1vwvqae the 5s and various letters are the keys I was mashing on while in the game menu of Elite Force. The only game I was able to get working on the september build was Call of Duty demo which had the same sporatic keyboard functionality. -- Configure bugmail: http://bugs.winehq.com/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 1516] regedit generates a segmentation fault
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1516 ------- Additional Comments From alexander.janssen(a)gmx.de 2003-25-10 14:28 ------- If you want to run "ls" for example, do the following: sh-2.05b$ gdb ls GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) r Starting program: /bin/ls (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 2659)] ####### output of program here ####### one three two typescript ####### end of output ####### (no debugging symbols found)... Program exited normally. (gdb) quit sh-2.05b$ Note that i inserted the "### outpur here###" statements. However, if you want to run "ls -l" or generally a program with an arguemt, you have to do a bit more since "gdb ls -l" does not work: sh-2.05b$ gdb ls GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) set args -l (gdb) r Starting program: /bin/ls -l (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 2665)] total 0 (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... -rw-r--r-- 1 test users 0 Oct 25 21:23 one -rw-r--r-- 1 test users 0 Oct 25 21:23 three -rw-r--r-- 1 test users 0 Oct 25 21:23 two -rw-r--r-- 1 test users 0 Oct 25 21:24 typescript (no debugging symbols found)...(no debugging symbols found)... Program exited normally. (gdb) quit Do the same for wineinstall. If the program crashes, you will land on the gdb console again. There you have to type "bt" for backtrace. If everyting fails inside "make install", you would have to do: $ gdb make GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) set args install (gdb) r [... output here ...] [program crashes here] (gdb) bt [lots of stackstrace] (gdb) quit Provide the output of your debugging session. Hope that helps, Alex. -- Configure bugmail: http://bugs.winehq.com/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 1795] [wineinstall] requires root user
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1795 ------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-25-10 14:24 ------- I was not enough clear. I don't want that the install process itself run in "root" user. A user don't exactly knows what the install program makes. -- Configure bugmail: http://bugs.winehq.com/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 1797] New: fetch.exe (part of DigiGuide) will not run
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1797 Summary: fetch.exe (part of DigiGuide) will not run Product: Wine Version: CVS Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.com ReportedBy: dave(a)aagames.co.uk fetch.exe, part of DigiGuide 6.1 [http://www.digiguide.com/] fails to run in wine - it is impossible to "register" and update, as a concequence. This bug happens every time I try to update DigiGuide, and has done from yesterday's (2003-10-24) CVS, to quite a long time ago. DigiGuide 6.1 beta was working fine several months ago, but I don't know if this is a change in WINE or DigiGuide. I get the following console output: Starting C:\Program Files\DigiGuide TV Guide\Fetch.exe fixme:imagehlp:SymGetOptions (): stub fixme:imagehlp:SymSetOptions (0x00000014): stub fixme:imagehlp:SymInitialize (0xffffffff, (null), 1): stub wine: Unhandled exception (thread 0009), starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x4037001c "?" wait timed out in thread 000a, blocked by 0009, retrying (60 sec) [the last message repeats many times] I don't know if this is a good bug report or not (not having submitted a WINE bug before), so if it's a crap report, please tell me in what way. -- Configure bugmail: http://bugs.winehq.com/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 1796] Menus in Delphi 7 does not display properly.
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1796 ------- Additional Comments From poczta(a)vogel.w.pl 2003-25-10 13:14 ------- Created an attachment (id=397) --> (http://bugs.winehq.com/attachment.cgi?id=397&action=view) Delphi7's menus under Wine Too short menus without 'submenu marks' in Delphi7. -- Configure bugmail: http://bugs.winehq.com/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 1796] New: Menus in Delphi 7 does not display properly.
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1796 Summary: Menus in Delphi 7 does not display properly. Product: Wine Version: unspecified Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.com ReportedBy: poczta(a)vogel.w.pl In Delphi 7 menus are drawing in XP-like style, even in Win9x. It is done by (I think) using WM_DRAWITEM and WM_MEASUREITEM messages. In Wine (I used wersions from 2003-03 to 2003-10, with Win98, WinXP and Win2000 emulation mode) menus aren't displayed properly: they are too short (only two items shows), and they doesn't have 'submenu marks'. Steps to reproduce: 1.) Go to www.borland.com and get Delphi 7 Architect Trial, get the Key, and install Delphi 7 on your machine 2.) Run Delphi 7 3.) Click the File menu. -- Configure bugmail: http://bugs.winehq.com/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 1620] X11drvX11DRV_ChangeDisplaySettingsExW No matching mode found
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1620 ------- Additional Comments From alexander.janssen(a)gmx.de 2003-25-10 13:07 ------- Errr: OK, description follows: All three testcases made WITH xv-entensions. 1. called binary with an absolute UNIX-path: WORKED 2. called binary direct from the directory where the binary is: FAILED 3. called binary in 'wine "C:\Program Files\.....\binary.exe" notation: WORKED. I *don't* think anymore that this is due to a X-problem, eh? Cheers, a confused Alex. -- Configure bugmail: http://bugs.winehq.com/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 1620] X11drvX11DRV_ChangeDisplaySettingsExW No matching mode found
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1620 ------- Additional Comments From alexander.janssen(a)gmx.de 2003-25-10 13:05 ------- Created an attachment (id=396) --> (http://bugs.winehq.com/attachment.cgi?id=396&action=view) Results of my three testcases as described in the bug. -- Configure bugmail: http://bugs.winehq.com/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 1620] X11drvX11DRV_ChangeDisplaySettingsExW No matching mode found
by Wine Bugs Oct. 25, 2003

Oct. 25, 2003

http://bugs.winehq.com/show_bug.cgi?id=1620 ------- Additional Comments From alexander.janssen(a)gmx.de 2003-25-10 12:42 ------- Now that was strange; i disabled the video mode extension. From XF86Config-4(5x): Option "DisableVidModeExtension" "boolean" This disables the parts of the VidMode extension used by the xvidtune client that can be used to change the video modes. Default: the VidMode extension is enabled. Not sure if that was the right thing, but i tried anyway and included: Option "DisableVidModeExtension" "true" Well, now something weird happened: The first time i started the program in question (Marble Blast Demo) a window from the program actually appeared (instead of that wine immediately dropped into the debugger) and complained about some missing files; allright, that is something which is a problem of the program and not of wine. I tried again, then the error appeared again. The program never started again. Weird, uh? Not reproducable. And dumb me didn't save the debugging information. Is it worth trying to reproduce that behaviour? Alex. -- Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0