[Bug 31026] New: Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

Bug #: 31026
           Summary: Following ~/.wine/system.reg on a new profile
           Product: Wine
           Version: 1.5.7
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

If there is no profile for Wine but ~/.wine/system.reg is already existing as a
symlink to another file Wine doesn't follow this symlink if a new profile is
created (the symlink ~/.wine/system.reg will be overwritten with the regular
file). Only the file ~/.wine/.update-timestamp is followed if it is a symlink.
I think Wine should try to follow ~/.wine/system.reg too before overwriting it.

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

--- Comment #1 from Austin English  2012-06-26 12:46:17 CDT ---
It seems to me that the bug is that ~/.wine/.update-timestamp is followed as a
symlink if ~/.wine doesn't exist. Attempting to salvage partial configurations
like that seems like a recipe for disaster.

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

--- Comment #2 from [e-mail] 2012-06-26 12:58:05 CDT ---
> Attempting to salvage partial configurations
> like that seems like a recipe for disaster.

I'm using the system.reg, ..update-timestamp and the most parts of drive_c as a
symlink to /wine and the related subdirectories. So I can install applications
on the system and every user can use them but the local configurations like
user.reg, userdef.reg and the local directory in drive_c will still stay in
~/.wine.

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #3 from Austin English  2012-06-26 13:37:22 CDT ---
That's not supported. See bug 11112.

*** This bug has been marked as a duplicate of bug 11112 ***

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Ken Sharp  2012-06-28 02:37:05 CDT ---
Closing dup

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

--- Comment #5 from [e-mail] 2012-09-27 17:07:59 CDT ---
This ticket is more about the different behavior that a symlink is followed and
another not. Shouldn't be there the same behavior for both files? I don't care
if you decide that both symlinks are followed or not - but we should have a
strict solution then.

[Bug 31026] Following ~/.wine/system.reg on a new profile

http://bugs.winehq.org/show_bug.cgi?id=31026

--- Comment #6 from [e-mail] 2013-02-01 05:03:19 CST ---
I have figured out that this maybe happened because of a permission problem.
Now all is working fine.