You are not logged in.
Pages: 1
Topic closed
Hello,
Yesterday afternoon, I found out Office (using Wine) started to refuse to open files, claiming they don't exist.
No way to save a file either.
Last Excel file I saved was yesterday morning, so it's probably linked to a system upgrade after that time.
After some dig up, it seems there is a problem with access rights :
winecfg
then click Drive throws the following error :
wine: Read access denied for device L"\\??\\E:\\", FS volume label and serial are not available.
Selecting a drive (Z: for instance) and clicking on "Browse" does nothing.
wine notepad
from my directory, when I try to save, throws :
01e4:err:commdlg:IShellBrowserImpl_BrowseObject could not browse to folder
The save windows opens but shows nothing instead of the current directory content.
With:
sudo winecfg
(or sudo wine notepad)
no error.
Clicking on Browse opens a windows to browse disk as expected.
My user does have access to / (hopefully )
I tried downgrading all package that were updated yesterday :
[2021-12-27T09:57:21+0100] [ALPM] upgraded expat (2.4.1-1 -> 2.4.2-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded expat (2.4.1-1 -> 2.4.2-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded libxml2 (2.9.12-5 -> 2.9.12-6)
[2021-12-27T09:57:21+0100] [ALPM] upgraded grub (2:2.06-2 -> 2:2.06-3)
[2021-12-27T09:57:21+0100] [ALPM] upgraded iniparser (4.1-3 -> 4.1-4)
[2021-12-27T09:57:21+0100] [ALPM] upgraded intel-gmmlib (21.3.3-1 -> 21.3.5-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded iproute2 (5.15.0-1 -> 5.15.0-2)
[2021-12-27T09:57:21+0100] [ALPM] upgraded ldns (1.7.1-2 -> 1.8.1-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded lib32-expat (2.4.1-1 -> 2.4.2-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded libglvnd (1.3.4-1 -> 1.4.0-1)
[2021-12-27T09:57:21+0100] [ALPM] upgraded lib32-libglvnd (1.3.4-1 -> 1.4.0-1)
[2021-12-27T09:57:22+0100] [ALPM] upgraded python (3.10.1-1 -> 3.10.1-2)
[2021-12-27T09:57:22+0100] [ALPM] upgraded s-nail (14.9.22-1 -> 14.9.23-1)
[2021-12-27T09:57:22+0100] [ALPM] upgraded tbb (2021.4.0-3 -> 2021.5.0-1)
No effect.
Googling the error message does not give very usefull tips...
I'm not very happy to use wine as root... what could have caused this?
I use an ext4 encrypted system, but changed nothing (fstab, cryptab, partitions...) in more that a year, so I expect it's something at a higher level.
Last edited by JeanLucJ (2021-12-29 09:11:58)
Offline
sudo with wine is a bad idea. Maybe that was your original problem?
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
sudo with wine is a bad idea. Maybe that was your original problem?
Hello,
Thanks for your reply
I had the problem in the first place, and used sudo wine to troubleshoot it, so it is the other way around.
I checked permissions for .wine and the various prefixes I use. No problem with permissions, and same error (cannot access filesystem with notepad, cannot browse filesystem with winecfg)
As a side note, I'm not sure the wiki you point is still accurate, as sudo wine created a wine prefix in /root
Offline
For any future reference, I'm not quite sure what caused this problem, but removing and resintalling wine solved it, though some manual work is needed afterward :
Before
wine notepad
(or any command, it seems) in any existing prefix (I had a bunch of them for games and did copies to test) causes the problem and seems to break the prefix.
Something changes in user.reg that makes Wine unable to acess filesystem.
remove wine, reinstall wine
After that :
-Any new prefix created then has not the problem.
-The problem persists in all previously tested prefix -> get the specific config of this prefix, delete it, recreate it, reconfig it -> Problem solved
-The problem is not present in all previously existing but untested prefix
sudo chown -R $USER:$USER .wine
does not fix a compromised prefix.
Deleting user.reg sometimes works when installed program does not rely on config inside the file.
As far as I can tell, the wine upgrade broke something, though nothing appears in pacman.log, and a simple reinstall solved it.
Recreating old prefix with many tweaks can be a hassle, though.
Last edited by JeanLucJ (2021-12-29 09:15:34)
Offline
For future reference, In my case the problem was caused by deleting the "Desktop" folder in my home folder. Simply re-adding the folder fixed the issue.
mkdir ~/Desktop
Offline
Thanks for the addition but this thread is from december 2021 .
Please check the rules on necro bumping .
Closing this thread.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1
Topic closed