[pkg-wine-party] Bug#793879: marked as done (wine: Failed to connect to the mount manager)
Your message dated Tue, 28 Jul 2015 22:26:03 +0200
with message-id <55B7E55B.4060607@gmail.com>
and subject line Re: [pkg-wine-party] Bug#793879: Bug#793879: (no subject)
has caused the Debian Bug report #793879,
regarding wine: Failed to connect to the mount manager
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
793879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793879
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wine
Version: 1.6.2-20
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Attempted to get a Windows program to work under WINE.
* What exactly did you do (or not do) that was effective (or ineffective)?
Using an existing install (from Fedora 21) I launched the program only to
receive several errors. It appears that the errors revolve around Wine
Configuration not being able to connect to the mount manager leading to no
drives being configured. I've uninstalled and reinstalled wine and have
removed my ~/.wine.
* What was the outcome of this action?
Problem still exists.
$ winecfg
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr"
failed to start: 2
err:winecfg:open_mountmgr failed to open mount manager err 2
* What outcome did you expect instead?
Program would run under wine.
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages wine depends on:
ii file 1:5.22+15-2
ii wine32 1.6.2-20
ii wine64 1.6.2-20
wine recommends no packages.
Versions of packages wine suggests:
pn avscan | klamav | clamav <none>
ii binfmt-support 2.1.5-1
pn ttf-mscorefonts-installer <none>
pn winbind <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Jul 28, 2015 at 7:47 AM, Eric Christensen
<eric@christensenplace.us> wrote:
> $ winecfg
> fixme:service:scmdatabase_autostart_services Auto-start service
L"MountMgr"
> failed to start: 2
> err:winecfg:open_mountmgr failed to open mount manager err 2
Ok, I can reproduce this:
# Delete (move) old wineprefixes
mv ~/.wine ~/.wine.old
mv ~/.wine64 ~/.wine64.old
# Force 64-bit
export WINEARCH=win64
# Create a new wineprefix with wine 1.7.47
wineboot-development
# Downgrade it
wineboot
# Run winecfg
winecfg
Output:
fixme:service:scmdatabase_autostart_services Auto-start service
L"MountMgr" failed to start: 2
So this seems to be the result of
- an downgraded wineprefix
- for WINEARCH win64 (or perhaps WoW64) and
- another symptom of https://bugs.debian.org/784280 (use "wine winecfg"
in Debian Jessie).
Therefore closing.
To convince me I'm wrong please post the output of:
echo $WINEARCH
echo $WINEPREFIX
ls ~/.wine ~/.wine64
All these should give no result. Just then reinstall your program and
try it.
Greets
jre
--- End Message ---
Reply to: