[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#776784: marked as done (winecfg won't run)



Your message dated Sun, 1 Feb 2015 19:53:22 -0500
with message-id <CANTw=MMBKsYPTiMReJx7yaRDavedYMrMUuAEv45=S_UY0=g7+w@mail.gmail.com>
and subject line Fwd: [pkg-wine-party] Bug#776784: winecfg won't run
has caused the Debian Bug report #776784,
regarding winecfg won't run
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.)


-- 
776784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776784
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wine
Version: 1.6.2-19
Severity: important

Dear Maintainer,

when I run winecfg, I get the following error:

solitone@aldous:/$ winecfg
cat: /home/solitone/.wine/system.reg: No such file or directory
/usr/bin/winecfg: 32: exec: winecfg.exe: not found

Regards

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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.20-2
ii  wine32  1.6.2-19
ii  wine64  1.6.2-19

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 ---
> Yes, that's right, thanks!

Closing since there is a workaround.

Best wishes,
Mike

--- End Message ---

Reply to: