http://bugs.winehq.org/show_bug.cgi?id=2615
------- Additional Comments From tony_lambregts(a)telusplanet.net 2005-01-01 16:47 -------
I am able to run it fine with the 20031016 snapshot but after that there are
various regressions. So it is very difficult to difficult to regression test it.
On my system (RH9) I see tons of these mesages before the crash.
fixme:win:GetThreadDesktop (9): stub
When I ran with WINEDEBUG=+relay I ran out of diskspace after several hours
without a wine desktop poping up.
It is definitely interesting that it works with your RH7.3 system.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=2633
Summary: RH9 RPMs incompatible with RH9 -- total showstopper
Product: Wine
Version: 20041201
Platform: PC
URL: http://www.winehq.org/site/download-rh
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P1
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: 2blkbelt(a)nemontel.net
RH9 out-of-box system, "everything" installed.
Installation of wine-20041201-1rh9winehq.i686.rpm goes fine with "rpm -Uvh"
Typing "wine[enter]", however, generates an error message as follows...
/usr/bin/wineserver: relocation error: /usr/bin/wineserver: symbol epoll_create,
version GLIBC_@.3.2 not defined in file libc.so.6 with link time reference
...the problem here is that the "RH9" version requires components that are not
part of, or native to, RH9. We're not talking about a trivial just "go and get
the stuff" thing, either; installing a different version of glibc is highly
problematic, according to the glibc website. Move this, rename that, this won't
work, that won't work, the usual litany of "we didn't think upgrades through, so
you're screwed, have a nice day." So very few people are going to be able to
pull this off (install the new glibc, I mean.)
If I were you people, I'd take that RPM down until I could come up with one that
installs into a freshly installed RH9 system with no mods, using the RH9-shipped
glibc. You have GOT to pay more attention to the environment!
--
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.
http://bugs.winehq.org/show_bug.cgi?id=2632
Summary: Couldn't connect to web sites
Product: Wine
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-net
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fasici(a)linux-sevenler.org
When I try to connect to a web site with wine it fails. For example,
flashget gives an error message like this:
Sat Jan 01 21:49:25 2005 Connecting www.kernel.org:0
Sat Jan 01 21:49:36 2005 Connecting www.kernel.org [IP=204.152.189.116:0]
Sat Jan 01 21:49:40 2005 Error occured! Socket Error=10061 Connection
refused. Please read user manual for more information.
If I write the port number 80 with URL it connects and downloads successfully.
Good work...
--
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.
http://bugs.winehq.org/show_bug.cgi?id=2615
------- Additional Comments From dclark(a)akamail.com 2005-01-01 12:48 -------
Neither of you mentioned where of how this is crashing. I spent a little time
looking at Myst, and see rather odd (to me) symptoms. What I see is that for
Wine compiled under RH 9 on two different machines, Myst can generally play the
intro, but crashes upon attempting to actually enter the game. This occurs for
me with CVS versions going back to Oct 03, before which Wine does not run for me
on RH 9 (I think maybe this was when the pthread work was done?). The backtraces
from the traces do not look real. But the relay traces up to the crash generally
look like:
0009:Call hook proc 0x43ca95 (id=WH_GETMESSAGE,code=0,wp=00000001,lp=40733d78)
... code deleted.
0009:Call winmm.timeGetTime() ret=0043cb02
0009:Call kernel32.GetTickCount() ret=409302d5
0009:Ret kernel32.GetTickCount() retval=00008ac8 ret=409302d5
0009:Ret winmm.timeGetTime() retval=00008ac8 ret=0043cb02
0009:Call kernel32.UnhandledExceptionFilter(407355c8) ret=00441195
It appears that there is no problem with the timeGetTime calls... it has been
called from the same place many times previously without crashing. Normally at
this point another call to timeGetTime would be made; Myst seems to always call
the function twice.
I don't really know how to go about debugging this. Since this error appears in
all versions of runable Wine on two different RH9 machines, I cannot narrow it
down with a regression test. The backtraces appear to show junk, and I don't
really know how to go about getting additional info.
I have a third machine with RH7.3. This one behaves rather different. Myst seems
to work pretty well with a lot of CVS versions, but various bugs are introduced
(and sometimes fixed) with different CVS versions. With a current CVS version,
Myst seems to be prone to random freezes for me (but it doesn't crash). I'm
going through to see whether I can at least find that, since it is definitely an
introduced error.
--
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.