http://bugs.winehq.org/show_bug.cgi?id=16779
Summary: Wine always crashes when drive_c is a symlink Product: Wine Version: 1.1.12 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: info@goldenelite.com
Hi! I was running Wine 1.1.12 without problems on my Ubuntu 8.10 x64 desktop, when i decided i wanted my drive_c to be on another drive which has more space available. But after i moved the drive_c and symlinked it, i could no longer launch any application - not even winecfg! It always crashes with a page fault.
Steps to reproduce:
1. rm -rf ~/.wine 2. winecfg (creates fresh .wine dir) 3. Install Winamp (works) 4. mv ~/.wine/drive_c /jfs/drive_c 5. ln -s /jfs/drive_c ~/.wine/drive_c 6. Launching "winecfg" results in page fault:
--- vortex@vortex-desktop:/jfs/drive_c/Program Files/Winamp$ padsp wine winamp.exe wine: Unhandled page fault on write access to 0x004502e6 at address 0x7bc46c61 (thread 001b), starting debugger... wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. ---
Notes: - I'm not sure if its the symlink or JFS which is bugging Wine. - The permissions of /jfs and /jfs/drive_c are 777; owner is set to my user account. - Both my root filesystem and the /jfs (seperate filesystem) mounts are JFS volumes. - /etc/fstab snippets:
# /dev/sda1 = data partition (mounted /jfs) /dev/sda1 /jfs jfs user,relatime,errors=remount-ro 0 1 # /dev/sda5 = system partition (mounted /) UUID=5347c06f-5619-41b7-a0db-d6ec096c9ab4 / jfs relatime,errors=remount-ro 0 1
Any pointers on how to provide debug/trace/coredump information are welcome.
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2009-01-03 21:49:28 --- upgrade to latest git and try again.
http://bugs.winehq.org/show_bug.cgi?id=16779
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-01-04 00:02:16 --- Tested jfs myself, works fine with latest git. Duplicate of bug 16732.
*** This bug has been marked as a duplicate of bug 16732 ***
http://bugs.winehq.org/show_bug.cgi?id=16779
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Jeff Zaroyko jeffz@jeffz.name 2009-01-04 00:02:27 --- closing duplicate
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #4 from Sander info@goldenelite.com 2009-01-04 11:51:02 --- Compiled & installed the git source. But now, i get this message with all apps i tested:
vortex@vortex-desktop:/jfs/drive_c/Program Files/Winamp$ padsp wine winamp.exe err:module:attach_process_dlls "NSCRT.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files\Winamp\winamp.exe" failed, status c0000005
On the web i read alot of this status c0000005 and it is said to be a permission problem (noexec mounted filesystem) or when using FAT/NTFS filesystems. Would my use of JFS cause this as well? I'm not using FAT/NTFS and my filesystems are NOT mounted "noexec".
I'm still testing to see if these are seperate bugs or the same thing. Any pointers on how to properly diagnose/debug these problems are welcome. Should i file a new bug or use support forums instead?
http://bugs.winehq.org/show_bug.cgi?id=16779
Sander info@goldenelite.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|DUPLICATE |
--- Comment #5 from Sander info@goldenelite.com 2009-01-04 16:10:50 --- I swapped in a new disk, formatted it Ext3 and mounted it /home which so my .wine directory or drive_c directory are no longer symlinked. This fixed the status c00000005 issue for me.
Now, when i symlink my .wine folder as per instructions below to my JFS-partition i get the c0000005 error again. I tested with yesterdays git, version: wine-1.1.12-35-g62d6a4e
Steps to reproduce:
Situation: - new Ext3 is mounted /home in fstab - .wine directory resides on the Ext3 disk, without any symlinks - applications load normally, there is no c0000005 bug - when i try to symlink to my JFS-partition mounted /jfs, i get the c0000005 error again - /jfs/winecur and ~/.wine are exact copies
Commands used: <working state from here> vortex@vortex-desktop:~$ mv .wine wine-good vortex@vortex-desktop:~$ ln -s /jfs/winecur .wine vortex@vortex-desktop:~/.wine/drive_c/Program Files/Winamp$ padsp wine winamp.exe err:module:attach_process_dlls "NSCRT.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files\Winamp\winamp.exe" failed, status c0000005 <after symlinking all apps needing to load some dll fail with this error>
Reopening bug - to me its not clear yet whether it's JFS or the Symlink which is causing this error.
http://bugs.winehq.org/show_bug.cgi?id=16779
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2009-01-04 17:09:17 --- (In reply to comment #5)
vortex@vortex-desktop:~$ ln -s /jfs/winecur .wine
You can't do that. WINEPREFIX have to be a real directory. You can put it anywhere you want to, but WINEPREFIX env var have to point to a real directory.
Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=16779
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Vitaliy Margolen vitaliy@kievinfo.com 2009-01-04 17:09:24 --- Closing
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #8 from Sander info@goldenelite.com 2009-01-04 17:56:49 --- Could you please clarify? Because i also tried symlinking just the drive_c folder and not the .wine directory itself, but that did not work either. Does this mean no symlinks are allowed whatsoever in any subdirectories of .wine ?
In either case, maybe this limitation should be mentioned in the FAQ?
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #9 from Vitaliy Margolen vitaliy@kievinfo.com 2009-01-05 00:15:34 --- (In reply to comment #8)
Because i also tried symlinking just the drive_c folder and not the .wine.
This is not supported either. That have to be a real directory as well. The symlink is under .wine/dosdevices.
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #10 from Alexandre Julliard julliard@winehq.org 2009-01-05 04:03:50 --- Having .wine or drive_c as a symlink works just fine. The problem is most likely with JFS.
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #11 from Sander info@goldenelite.com 2009-01-05 09:06:02 --- Confirmed.
When symlinking drive_c to a directory within the /home mount (a seperate Ext3 formatted disk) there is no problem. Only when symlinking to JFS.
Commands used:
<working state from here> vortex@vortex-desktop:~/.wine$ mv drive_c drive_c_good vortex@vortex-desktop:~/.wine$ ln -s drive_c_good drive_c vortex@vortex-desktop:~/.wine/drive_c/Program Files/Winamp$ padsp wine winamp.exe <works!>
vortex@vortex-desktop:~/.wine$ rm drive_c vortex@vortex-desktop:~/.wine$ ln -s /jfs/winecur/drive_c vortex@vortex-desktop:~/.wine/drive_c/Program Files/Winamp$ padsp wine winamp.exe err:module:attach_process_dlls "NSCRT.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files\Winamp\winamp.exe" failed, status c0000005 <doesn't work anymore>
This might not be a bug in wine, but perhaps in JFS or the way JFS is integrated into Ubuntu 8.10.
http://bugs.winehq.org/show_bug.cgi?id=16779
--- Comment #12 from Sander info@goldenelite.com 2009-01-05 10:14:07 --- I think i fixed my issue. I had this in my /etc/fstab:
/dev/sda1 /jfs jfs user,relatime,errors=remount-ro 0 1
i changed it to:
/dev/sda1 /jfs jfs relatime,errors=remount-ro 0 1
After removing the 'user' mount option, the bug disappears. The manpage says:
" (iii) Normally, only the superuser can mount file systems. However, when fstab contains the user option on a line, anybody can mount the corresponding system."
So it sounds harmless but apparantly can cause problems. Either way this seems more and more like not a bug in wine, but i hope people with similar problems will find this through Google. Thanks for your time, i consider my problem fixed.
-
wine-bugs＠winehq.org