https://bugs.winehq.org/show_bug.cgi?id=52732
Bug ID: 52732 Summary: Garbage user-name crated with wine, not the proper user-name like in older versions. Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: rencer@euromail.hu Distribution: ---
I'm not sure exactly when (the latest 7.4 version or which previous version) this started to happen, because for a very long time I used Lutris to manage Wine-versions and my Windows programs. Because of Lutris,I don't even have Wine installed system-wide.
Sadly with the newest system (Manjaro XFCE) update someting in Python is totally broken, and because of that Lutris won't work anymore, so I had to install wine from system repo. The latest version in 7.4
The problem is when I createa a new (or try to change an existing wineprefix to use this system version), the user name is not my real username that I logged in with. Now wine creates a strange garbage user name: "u@". Previously it was correct and alway created the proper user folder, with the user who logged in and run wine.
Long time ago, before I started using Lutris (I'm not sure which wine version that was, around 4.x) I used command line to run wine, create prefixes, or run any Windows programs and never was this bug. Also most of the progrmas I installed with older versions and later never changed it, I think the last version that I used with Lutris is 6.something and it also don't had this user-name bug.
Problem is that all programs in any existing Wine-prefixes that was created with Lutris, (with the PROPER user-name) are broken, settings are lost, saves won't find, etc.,etc.,etc. because all the settings/saves are located in the correct user-name folder and not in this new bugged garbage "@u" name. First I thouth I lost all my files, and when I checked them with file-manager, that is how I realised this strange behaviour.
Copying the files to the new garbage name location in NOT working all the time, because many times programs store their settings, saved files, etc. in the registry-database, so, this bug really broke many things.