Permission screwup making Wine a pain to use

BorbingoBoy · 2021-02-21 11:49:40

Certain software used with Wine, such as Bethesda.net Launcher updater and GTA Connected have permission problems for whatever reason. All said programs needed to do was to write inside the Wine prefix.
I tried owning the home directory and giving all permissions in the home directory to my user, but that didn't work. Errors in the words of 'permission denied' kept appearing, making the use impossible.

Any suggestions? Nothing I searched for has worked. Such software used to work flawlessly on my old installation. I presume everything worked on my current install until as of recently.

V1del · 2021-02-21 11:56:24

That usually happens if you started wine as root at some time for some reason which you should never do. Have you tried a fresh wine prefix to check whether it's something there? "tried owning home, giving permissions in the home directory" also give me pause, as that should already be the case if we are talking about /home/$USER what's the actual situation here? Post in

[code]code tags[/code]

stat /home /home/$USER /home/$USER/.wine

BorbingoBoy · 2021-02-21 12:04:44

  File: /home
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10302h/66306d   Inode: 2621441     Links: 4
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-02-20 20:04:50.063944840 +0100
Modify: 2020-12-30 22:02:24.728684004 +0100
Change: 2020-12-30 22:02:24.728684004 +0100
 Birth: 2020-12-30 18:31:27.432962235 +0100
  File: /home/pro7o63n
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10302h/66306d   Inode: 2621442     Links: 81
Access: (0775/drwxrwxr-x)  Uid: ( 1000/pro7o63n)   Gid: ( 1000/pro7o63n)
Access: 2021-02-21 13:02:21.444969837 +0100
Modify: 2021-02-21 13:02:19.981625870 +0100
Change: 2021-02-21 13:02:19.981625870 +0100
 Birth: 2020-12-30 20:00:58.079032332 +0100
  File: /home/pro7o63n/.wine
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10302h/66306d   Inode: 3282712     Links: 4
Access: (0775/drwxrwxr-x)  Uid: ( 1000/pro7o63n)   Gid: ( 1000/pro7o63n)
Access: 2021-02-21 12:07:12.786211288 +0100
Modify: 2021-02-20 21:00:21.873515200 +0100
Change: 2021-02-21 12:04:24.883209703 +0100
 Birth: 2021-01-01 13:46:06.673608333 +0100
  File: /home/pro7o63n/.winebeth
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10302h/66306d   Inode: 2646178     Links: 4
Access: (0755/drwxr-xr-x)  Uid: ( 1000/pro7o63n)   Gid: ( 1000/pro7o63n)
Access: 2021-02-21 13:01:15.751141481 +0100
Modify: 2021-02-21 13:01:44.274694278 +0100
Change: 2021-02-21 13:01:44.274694278 +0100
 Birth: 2021-02-21 13:00:56.357654731 +0100

For testing purposes, I'm using a different prefix, so I included that too. No difference however.

V1del · 2021-02-21 12:24:17

Looks okay (... aside from that you really want 0700 on the perms on your own home, but I assume that's a fallout from you testing things), are you sure the issue is due to write permissions and not an actual bug in potentially the current Wine version? What actual terminal output when starting an affected program? What file system is your home dir on? if you check the output of "mount" does it show the relevant partition as read only?

BorbingoBoy · 2021-02-21 12:29:22

As for BNL it used to work on both Wine and Proton 5.0, not a Wine issue.
No additional terminal output.
ext4
rw, realtime

seth · 2021-02-21 13:48:00

BorbingoBoy wrote:

No additional terminal output.

What is the *actual* (literal) output that makes you assume this is a problem about writing to the wine prefix?

BorbingoBoy · 2021-02-21 13:56:43

Especially the second one. In both instances, files in Wine prefixes are being accessed. I'm certain since all installation files are located inside.
Neither the software nor Wine itself are the culprit as n1 (Bethesda Launcher) used to work for me and n2 (GTAC) generally works for everyone.

Last edited by BorbingoBoy (2021-02-21 13:58:20)

V1del · 2021-02-21 13:58:10

What exactly is your E: drive mapped to in winecfg ? I'd normally expect a Z: or C: path.

BorbingoBoy · 2021-02-21 13:58:34

I checked and it's the working directory.

V1del · 2021-02-21 14:00:40

Then that's likely wrong. If you aren't in the literal directory when invoking wine it will refer to an invalid path.

BorbingoBoy · 2021-02-21 14:03:40

Correction: it seems to have changed? I think I was looking at the wrong thing, but now I've double-checked and E: is the NTFS drive it tries to access. I never had issues with NTFS drives.
Regardless, the two issues may be unrelated, but they seem to point towards a permission issue outside of Wine itself.

Last edited by BorbingoBoy (2021-02-21 14:05:55)

seth · 2021-02-21 14:28:45

files in Wine prefixes are being accessed

Which files exactly?
Do the paths exist and what is the permission cascade ?

Edit: also the ntfs module was removed and you'll have to install ntfs-3g to get read (and write) access to ntfs partitions.

Last edited by seth (2021-02-21 14:29:47)

BorbingoBoy · 2021-02-21 14:41:08

The directory where n1 tries to download files to:

drwxrwxrwx 5 pro7o63n pro7o63n 4.0K Feb 21 15:30 'Bethesda.net Launcher'/

Its contents (excluding what it cannot create):

-rwxrwxr-x 1 pro7o63n pro7o63n  11M Sep 25 16:57 BethesdaNetLauncher.exe*
-rwxrwxr-x 1 pro7o63n pro7o63n 205K Sep 25 16:57 BethesdaNetReporter.exe*
-rwxrwxr-x 1 pro7o63n pro7o63n 1.9M Sep 25 16:57 BethesdaNetUpdater.exe*
-rwxrwxr-x 1 pro7o63n pro7o63n 317K Sep 25 16:57 BsSndRpt.exe*
-rwxrwxr-x 1 pro7o63n pro7o63n 299K Sep 25 16:57 BugSplat.dll*
-rwxrwxr-x 1 pro7o63n pro7o63n 105K Sep 25 16:57 BugSplatRc.dll*
-rw-r--r-- 1 pro7o63n pro7o63n   36 Feb 21 15:34 cdpprod.dch
-rwxrwxr-x 1 pro7o63n pro7o63n 1.4M Sep 25 17:25 ClientLibrary.dll*
-rwxrwxr-x 1 pro7o63n pro7o63n 239K Sep 25 16:57 concrt140.dll*
drwxrwxr-x 2 pro7o63n pro7o63n 4.0K Feb 21 11:52 imageformats/
-rwxrwxr-x 1 pro7o63n pro7o63n 113K Sep 25 16:57 loc.dch*
drwxrwxr-x 2 pro7o63n pro7o63n 4.0K Feb 21 15:34 logs/
-rwxrwxr-x 1 pro7o63n pro7o63n 430K Sep 25 16:57 msvcp140.dll*
drwxrwxr-x 2 pro7o63n pro7o63n 4.0K Feb 21 11:52 platforms/
-rwxrwxr-x 1 pro7o63n pro7o63n 4.8M Sep 25 16:57 Qt5Core.dll*
-rwxrwxr-x 1 pro7o63n pro7o63n 4.9M Sep 25 16:57 Qt5Gui.dll*
-rwxrwxr-x 1 pro7o63n pro7o63n 4.6M Sep 25 16:57 Qt5Widgets.dll*
-rwxrwxr-x 1 pro7o63n pro7o63n  70K Feb 21 11:52 unins000.dat*
-rwxrwxr-x 1 pro7o63n pro7o63n 1.4M Feb 21 11:52 unins000.exe*
-rwxrwxr-x 1 pro7o63n pro7o63n  82K Sep 25 16:57 vcruntime140.dll*

I would ignore n2 for now as it seems to access a nonexistent directory on NTFS. However, I have installed ntfs-3g already and never had issues with NTFS drives.

Last edited by BorbingoBoy (2021-02-21 14:43:19)

V1del · 2021-02-21 14:53:38

How are you mounting the drive? Can you post the output of mount ? If you reuse that and have a hibernating windows or so it's possible that ntfs-3g mounted the drive read only

BorbingoBoy · 2021-02-21 14:59:27

Drive is mounted using fstab.

UUID=724A687D4A684049 /mnt/wd40 ntfs defaults 0 0

/dev/sdb1 on /mnt/wd40 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

Nope, additionally I can read and write from it.

It appears that I've run into a completely different issue entirely, as I've copied over downloaded files for n1 / Bethesda Launcher on Windows. Bethesda login does not work for some reason.
I never had this sort of thing happen before. I'm genuinely clueless at this point and if it's a Wine issue or not.
Nobody else seems to be having this issue either.

Last edited by BorbingoBoy (2021-02-21 15:07:16)

Arch Linux

#1 2021-02-21 11:49:40

Permission screwup making Wine a pain to use

#2 2021-02-21 11:56:24

Re: Permission screwup making Wine a pain to use

#3 2021-02-21 12:04:44

Re: Permission screwup making Wine a pain to use

#4 2021-02-21 12:24:17

Re: Permission screwup making Wine a pain to use

#5 2021-02-21 12:29:22

Re: Permission screwup making Wine a pain to use

#6 2021-02-21 13:48:00

Re: Permission screwup making Wine a pain to use

#7 2021-02-21 13:56:43

Re: Permission screwup making Wine a pain to use

#8 2021-02-21 13:58:10

Re: Permission screwup making Wine a pain to use

#9 2021-02-21 13:58:34

Re: Permission screwup making Wine a pain to use

#10 2021-02-21 14:00:40

Re: Permission screwup making Wine a pain to use

#11 2021-02-21 14:03:40

Re: Permission screwup making Wine a pain to use

#12 2021-02-21 14:28:45

Re: Permission screwup making Wine a pain to use

#13 2021-02-21 14:41:08

Re: Permission screwup making Wine a pain to use

#14 2021-02-21 14:53:38

Re: Permission screwup making Wine a pain to use

#15 2021-02-21 14:59:27

Re: Permission screwup making Wine a pain to use

Board footer