http://bugs.winehq.org/show_bug.cgi?id=17955
--- Comment #31 from Marc-Olivier Barre marco@marcochapeau.org 2009-07-19 07:52:58 --- (In reply to comment #30)
Playing it with lowest possible graphics still produces the error, running from Terminal shows a message:
wine: Unhandled page fault on read access to 0x59ab14c8 at address 0x3b79435 (thread 001b), starting debugger... XIO: fatal IO error 11 (Resursen tillfälligt otillgänglig) on X server ":0.0" after 75 requests (75 known processed) with 0 events remaining. joxe@joxe-desktop:~$ fixme:x11drv:X11DRV_DestroyNotify window 0x1003a/4800005 destroyed from the outside
"page fault on read access" does it have anything to do with what files Wine wants to use? Running it from sudo just tells me that ~/.wine/ isn't owned by me. Seems like I'm having a different problem than the original poster (not the same error message).
You probably are having a different problem, but we can't really tell can we. what wine version ? how does the crash happen ?
Anyways, you have an X error showing up on your output, so I suspect it's something completely different.
And for the record: - Running wine with sudo is extremely foolish and insecure - ~/.wine/ belongs to you, sudo runs things as root, so yes, it's a different user. - "page fault on read access" has nothing to do with access rights to files. It refers to an invalid access to a zone in memory.