You are not logged in.
Pages: 1
I have some problem with the wine 1.5.23 package in cooking. When I run winecfg, I cannot manage drives and I have an error in the console:
[c]err:winecfg:open_mountmgr failed to open mount manager err 2[/c]
Is this a known bug? The only post I found suggested to erase .wine. I tried, but it didn't solve my problem.
Is there missing anything in the description of my problem or nobody has an idea about it?
You must completely remove wine and configuration files.
And make a new and clean installation.
This problem happens when the wine has files are overwritten.
Offline
I have already removed .wine and deinstalled wine but it didn't solve it. Is there anything else to remove?
I tried both wine 1.5.23 and the current stable version wine 1.4.1 on a clean full install of cooking.
Both versions have the same problem with mount manager error. I googled for over an hour to try to find a solution and finally gave up.
Offline
Thank you mojo! I feel less lonely with this problem that I try to solve since a few weeks...
I have tried the same versions of wine on other distributions and they work. It doesn't seem to be a problem from upstream.
I do not have this error.
This "bug" was reported on the Wine website and is old.
http://bugs.winehq.org/show_bug.cgi?id=18614#c0
Offline
@holkfoor
Maybe we should hire you to fix it 
Offline
Is it just me or has nobody noticed that wine doesn't have it's config files in just one place. So deleting just .wine wouldn't be deleting ALL it's config files and probably wouldn't fix anything.
Local:
~/.wine
~/.config/menus/applications-merged
~/.local/share/applications/wine
~/.local/share/desktop-directories
~/.local/share/mime
~/.local/share/icons
Global:
/usr/share/wine
Offline
As far as I know, /usr/share/wine is removed when you deinstall the package.
From all the files you have listed, I only have ~/.wine. Could be a part of the problem...
As Mojo has said, it appears also on a clean full install of cooking - I mean a fresh installation of the cooking ISO. 
Hmm, so it's not creating the local folders, which probably means it's failing to initialize completely. Does running applications with it work or does it fail with the same error? I remember having this error before with the original SliTaz Cooking that became SliTaz 4, but it disappeared during the RC phase. Looks like it's back again...
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]