http://bugs.winehq.com/show_bug.cgi?id=1803
Summary: Steam Crashes With Fixme: errors.
Product: Wine
Version: CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: ryan(a)linux-gaming.com
This was trying to get steam to run.
fixme:commctrl:InitCommonControlsEx Unknown class! dwICC=0x8000
fixme:win32:PeekNamedPipe function not implemented
client callback thread error
fixme:ole:CoCreateInstance no instance created for interface {00000000-0000-0000
-c000-000000000046} of class {8856f961-340a-11d0-a96b-00c04fd705a2}, hres is
0x8
0040111
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1801
ryan(a)linux-gaming.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ryan(a)linux-gaming.com 2003-28-10 15:11 -------
I've figured out the problem in association with the bug, xfree-dga. I disabled it in xfree
and nothing crashes any longer.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1801
Summary: System Crash Black Screen
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: ryan(a)linux-gaming.com
Hello well i've tried this many times winex3 (cvs) doesn't seem to generate this
error. But here i go as best i can describe it, i am running gentoo linux (1.4
kernel 2.6.0-test9) when i launch anything with 'wine' my computers monitor
turns off, anyone know what i can do? And yes it does this with EVERY
application with wine.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1800
Summary: [user documentation] bad LANG_* definition location
Product: Wine
Version: CVS
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-documentation
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: jerome.bouat(a)wanadoo.fr
I generated the "wine-user.html" from CVS tree. The keyboard section indicated I
would find languages constants in "include/winnls.h".
But, in wine source root directory, command
---
find . -iname "*\.h" | xargs grep "define" | grep "LANG_"
---
gives include/winnt.h for the definition of "LANG_*" and "SUBLANG_*" constants.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1782
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From mike(a)theoretic.com 2003-27-10 04:28 -------
I'm going to tentatively mark this as FIXED on the grounds that I think I know
what caused it, but am not 100% sure.
If it happens again please reopen.
--
Configure bugmail: http://bugs.winehq.com/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.
http://bugs.winehq.com/show_bug.cgi?id=1799
------- Additional Comments From arlowatson(a)yahoo.com 2003-26-10 20:44 -------
Small change: when using existing windows drive, wine fails because
/mnt/windisk is readonly (it's NTFS), so I am compelled to not use existing
window drive.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1799
Summary: wineinstall err:seh:EXC_DefaultHandling
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-tools
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: arlowatson(a)yahoo.com
running tools/wineinstall, building from source wine-20031016 on Intel Pentium 4
linux kernel 2.4.22:
> Preparing to install default Wine registry entries...
> Installing default Wine registry entries...
>
> Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
> Could not stat /cdrom (No such file or directory), ignoring drive D:
> wine: Unhandled exception (thread 0009), starting debugger...
> err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr
0x40178805
> Registry install failed.
I understand that I get the "stat" errors because I don't have a floppy or CD in
the drives, and that this is OK. The "Unhandled exception" is the reason I'm
filing this bug.
What else can I tell you about my system?
$ uname -a
Linux localhost 2.4.22 #10 SMP Thu Oct 9 02:55:10 PDT 2003 i686 i686 i386 GNU/Linux
$ ./wine --debugmsg +relay,+file,+dosfs /mnt/windisk/WINDOWS/NOTEPAD.EXE 2>&1 | tail
trace:dosfs:GetDriveTypeW (L"Z:\\mnt\\windisk\\WINDOWS\\NOTEPAD.EXE")
trace:file:CreateFileW L"Z:\\mnt\\windisk\\WINDOWS\\comdlg32.dll" QUERY_ACCESS
FILE_SHARE_READ FILE_SHARE_WRITE OPEN_EXISTING attributes 0x0
trace:dosfs:DOSFS_GetFullName L"Z:\\mnt\\windisk\\WINDOWS\\comdlg32.dll" (last=1)
trace:dosfs:DOSFS_FindUnixName /,L"mnt\\windisk\\WINDOWS\\comdlg32.dll"
trace:dosfs:DOSFS_OpenDir "/"
wine: Unhandled exception (thread 0009), starting debugger...
trace:dosfs:DOSFS_GetFullName L"Z:\\mnt\\windisk\\WINDOWS\\winedbg.exe"
(last=1)trace:dosfs:DOSFS_FindUnixName /,L"mnt\\windisk\\WINDOWS\\winedbg.exe"
trace:dosfs:DOSFS_OpenDir "/"
err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr
0x40178805
I get the same errors whether or not I tell wineinstall to use the windows
installation on /mnt/windisk.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1782
------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-26-10 17:08 -------
I could not reproduce it on heavy loaded host (CPU intensive toys) with a 19
nice value given to winecfg.
I assume it is fixed although it was difficult to reproduce last time.
--
Configure bugmail: http://bugs.winehq.com/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.
http://bugs.winehq.com/show_bug.cgi?id=1787
jerome.bouat(a)wanadoo.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-26-10 15:38 -------
I could not use the tools/wineinstall program because I could not run it as root !
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1682
jerome.bouat(a)wanadoo.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-26-10 15:36 -------
I did not used the tools/wineinstall program because I could not get root rights.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1795
------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-26-10 14:39 -------
There is no reason at all to run GCC as root.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1795
------- Additional Comments From jerome.bouat(a)wanadoo.fr 2003-26-10 02:48 -------
Imagine I am a student which uses an University system. I will not be granted
for the "root" rights. Even if I choose an install in my home directory, the
install program will not complete just because I'm not root !
In my opinion, your install program discards some testers from the wine
community. Moreover, in the previous example, students could give you new
development forces.
You have to mean it as a feature enhancement:
"Offer user installation capability".
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1782
------- Additional Comments From mike(a)theoretic.com 2003-25-10 16:14 -------
Could you please try winecfg from CVS? I have a feeling this is caused by the
build in the last release trying to write to the wrong place in the registry....
--
Configure bugmail: http://bugs.winehq.com/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.
http://bugs.winehq.com/show_bug.cgi?id=1798
------- Additional Comments From mike(a)theoretic.com 2003-25-10 16:13 -------
This is a well known bug - try running the games in Desktop mode, and see if
that helps.
Basically we are using override-redirect to remove window borders for fullscreen
apps, and this plays silly buggers with keyboard focus. The right way to do this
is to use EWMH/MWM hints to switch off the borders. I don't know why we don't do
that currently.
--
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.
http://bugs.winehq.com/show_bug.cgi?id=1797
------- Additional Comments From mike(a)theoretic.com 2003-25-10 16:10 -------
Hey Dave,
Could you please attach a +relay,+seh trace (or upload one somewhere)
thanks -mike
--
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.
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.
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@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@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.
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.
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.
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.
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.
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.