http://bugs.winehq.com/show_bug.cgi?id=1164
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|wine-bugs(a)winehq.com |vberon(a)mecano.gme.usherb.ca
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-11-28 13:34 -------
Yeah we are trying to make it easier to use however we broke it for some. For me
it was a relitivly simple fix to manually change the Makefile so that SRCDIR =
.. instead of SRCDIR = . YMMV.
I am assigning this bug to Vincent Beron since he is working on it.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1164>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1165
7ownq0k402(a)sneakemail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|wine-misc |wine-x11driver
------- Additional Comments From 7ownq0k402(a)sneakemail.com 2002-11-28 10:23 -------
Did some serious gdb debugging on the problem.
Conclusion: This is an X11driver problem, moving to x11driver component
Motes on the debug session follows:
The problem occurs as 1st wine processs exits with error code 1.
After this the wineserver process (and possibly another wine process seem to go
mad).
They cause 100% kernel load, and 100% use of swap.
did breakpoint on exit()
in gdb wine, on the 1st process (desktop???)
got following stack trace
#0 0x402761dd in exit () from /lib/libc.so.6
#1 0x4106913a in _XDefaultError () from /usr/X11R6/lib/libX11.so.6
#2 0x40ff66bd in error_handler (display=0x80a0e08, error_evt=0x406d18a4)
at x11drv_main.c:136
#3 0x4106924d in _XError () from /usr/X11R6/lib/libX11.so.6
#4 0x4106787b in _XReply () from /usr/X11R6/lib/libX11.so.6
#5 0x4106319a in XSync () from /usr/X11R6/lib/libX11.so.6
#6 0x40fef7c4 in TSXSync (a0=0x80a0e08, a1=0) at ts_xlib.c:614
#7 0x40ff148f in X11DRV_CreateWindow (hwnd=0x10051, cs=0x406d1c00, unicode=0)
at window.c:893
#8 0x4086c1d0 in WIN_CreateWindowEx (cs=0x406d1c00, classAtom=49155,
type=WIN_PROC_32A) at ../../windows/win.c:1166
#9 0x4086c63b in CreateWindowExA (exStyle=0, className=0x10156c0 "edit",
windowName=0x10974a4 "", style=1073807488, x=5, y=6, width=101, height=16,
parent=0x10026, menu=0x177b, instance=0x400000, data=0x0)
at ../../windows/win.c:1320
The contents of error_evt was:
(gdb) print error_evt
$1 = (XErrorEvent *) 0x406d18a4
(gdb) print error_evt->type
$2 = 0
(gdb) print error_evt->display
$3 = (Display *) 0x80a0e08
(gdb) print error_evt->resourceid
$4 = 77594636
(gdb) print error_evt->serial
$5 = 911
(gdb) print error_evt->error_code
$6 = 8 '\b'
(gdb) print error_evt->request_code
$7 = 7 '\a'
(gdb) print error_evt->minor_code
$8 = 0 '\000'
And what's the error:
(gdb) call XGetErrorText(display,error_evt->error_code,1076119904,1000)
$15 = 0
(gdb) print (char*)(1076119904)
$16 = 0x40244960 "BadMatch (invalid parameter attributes)"
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1165
------- Additional Comments From 7ownq0k402(a)sneakemail.com 2002-11-27 14:10 -------
It turns out that Photoshop removes all top level windows from
the KDE panel.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1165
------- Additional Comments From 7ownq0k402(a)sneakemail.com 2002-11-27 10:57 -------
Looking closely, the Window Manager controlled parts of the window disappear too.
This suggests some foulup relating to X11 communication, as the area is
obviously grabbed, but there's not title bar to minimise the grabbed window with.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1122
------- Additional Comments From hoffmajs(a)gmx.de 2002-11-27 09:21 -------
Yes that patch was the culprit. Are you sure that the fix for it was in the
cvs update you checked? just look at dlls/dinput/dinput_main.c around line 58
the line should read ..."KeyboardCallback, inst, 0 );" instead of
"KeyboardCallback, 0, 0 );".
If its the latter just change the first zero to "inst" and im sure it will
work :)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1122>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1129
------- Additional Comments From kniederk(a)math.uni-koeln.de 2002-11-27 08:41 -------
Today I'm using IE, so I hope this helps with the formatting.
Could someone tell me, if the tile-bitmaps are loaded or is there some way to
find this out? I guess that wine does not have problems with capital-letters
and such in filenames (since Windows does not distiguish them as far as I know).
Anyway in case this is not the error, I have been doing some "reverse-
engineering" in dink-smallwood, maybe someone can give me a hint on what to
test next:
Basically Dink Smallwood uses a Display-Surface with a Front- and Backbuffer
(640x480), an offscreen-memory-surface of the same size and some smaller
surfaces containing objects.
When the player enters a new room the offscreen-memory-surface is painted with
the ground-tiles and this remains fixed until the player enters another room.
Every time a frame is drawn the offscreen-surface is copied first to the
backbuffer (to paint the floor) and then the other several objects (trees,
people, etc.) are copied directly to the backbuffer. When this is finished, the
Back- and frontbuffers are switched and the steps above repeat.
What I am wondering is, why the objects are visible, but the floor-tiles are
not. The only differences I see for now, is that the objects are copied
directly to the backbuffer, while the floor-tiles are copied first to the
offscreen-memory and then to the backbuffer and the second difference is that
the floor-tiles are stored in regular *.bmp files, while the objects are stored
in some format, which I do not recognize.
What could I test next? Thanks
Klaus
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1129>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1165
------- Additional Comments From 7ownq0k402(a)sneakemail.com 2002-11-27 06:40 -------
In the bug report, I didn't complete this paragraph:
I am happy to provide debug reports, but I'll need guidance as to how to
proceed, because all debug logs I've created are large, and Photoshop must run
at a reasonable rate so I can kill it before it consumes all memory.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1165
Summary: Photoshop6 hangs, can potentially lock X server, and
machine.
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: 7ownq0k402(a)sneakemail.com
Wine build: Build 20021031 (Not in version list)
Steps to reproduce:
1. Run Photoshop6
2. Photoshop starts running.
3. Photoshop main window comes up (sometimes badly drawn)
4. The splash screen comes up.
5. Towards the end of the load ("Initialising..." is in splash screen) the main
window disappears, as does the splash screen.
6. The whole screen is now locked apart from the KDE panel, with the cursor
showing the hourglass.
7. When menus are lauched from the panel. the mouse works properly in menu.
Menu is draw correctly, but when leave menu, nothing is re-drawn.
8. Sometimes (especially if left in locked state) Photoshop 6 will use all
available memory (real & swap), and linux will hang.
Repeatability:
Always.
Workarounds attempted (None succeded):
1. Attempted using the following DLLs native:
shell,shell32,commtrl,comctl32,commdlg,comdlg32,shlwapi,
ole32,rpcrt4,shlwapi,oleaut32,msvcrt20,msvcrt,msvcp60,shfolder
2. Removed the native wintab32.dll
3. Tried with "Synchronous" = "Y"
This improved the drawing, but didn't fix the bug.
4. Tried with OS set to Win 98.
Wine config:
Is based upon a win98 install.
Photoshop6 was installed in Win98.
Options for exiting lock:
1. Go to a console (CTRL-ALT-FNKEY), and kill wineserver, and any wine apps.
2. Shutdown computer (sometimes possible from KDE panel menu.
3. Reset computer.
Looks almost as if a X grab has occured, on the whole screen apart
from the KDE panel.
I am happy to provide debug reports, but I'll need guidance as to how to
proceed, because all debug logs I've created are large, and Photoshop must run
at a reasonable rate so I can kill it before
Something to do with shfolder.dll?????
Seems to occur near wher dll is loaded.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1129
------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-11-27 00:48 -------
VFAT_IOCTL_READDIR_BOTH doesn't matter, since it's on a non-VFAT partition
and we just probe for VFAT properties.
Apart from that, no idea.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1129>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.