Bug#804740: apper: Won't ask for password and fails to do action
Package: apper Version: 0.9.1-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was trying to install a package (this also is effected when trying to do updates). * What exactly did you do (or not do) that was effective (or ineffective)? I selected a package to install. * What was the outcome of this action? Apper goes through the process of finding the package dependencies and then fails because it says I didn't provide a password. I was never prompted to authenticate. * What outcome did you expect instead? I would be asked for a password and the package would install. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') 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 apper depends on: ii apper-data 0.9.1-2 ii kde-runtime 4:4.14.2-2 ii libappstream10.7.3-1 ii libc62.19-18+deb8u1 ii libdebconf-kde0 0.3-1 ii libgcc1 1:4.9.2-10 ii libgee-0.8-2 0.16.1-1+deb8u1 ii libglib2.0-0 2.42.1-1 ii libkcmutils4 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdeui54:4.14.2-5 ii libkemoticons4 4:4.14.2-5 ii libkidletime44:4.14.2-5 ii libkio5 4:4.14.2-5 ii libkprintutils4 4:4.14.2-5 ii libkutils4 4:4.14.2-5 ii libkworkspace4abi2 4:4.11.13-2 ii liblistaller-glib0 0.5.9-4 ii libpackagekitqt4-0 0.9.5-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xmlpatterns 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libsolid44:4.14.2-5 ii libstdc++6 4.9.2-10 ii packagekit 1.0.1-2 ii policykit-1-gnome0.105-2 ii polkit-kde-1 0.99.1-1 ii software-properties-kde 0.92.25debian1 Versions of packages apper recommends: ii appstream-index 0.7.3-1 Versions of packages apper suggests: pn debconf-kde-helper ii listaller 0.5.9-4 -- no debconf information
Bug#797844: kmail: TLSv1.1 and TLSv1.2 are not supported
Package: kmail Version: 4:4.14.1-1 Severity: important Dear Maintainer, While doing some routine server hardening I noticed that Kmail will not connect to my IMAP server using TLSv1.2 or TLSv1.1. Since I only offer TLSv1 and higher it will only connect using TLSv1. I'm not sure if this is a compiling issue or if it's supported upstream but it seems pretty important to support TLSv1.2 in current products. Thanks! -- System Information: Debian Release: 8.1 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 kmail depends on: ii kde-runtime 4:4.14.2-2 ii kdepim-runtime4:4.14.2-3 ii kdepimlibs-kio-plugins4:4.14.2-2+b1 ii libakonadi-calendar4 4:4.14.2-2+b1 ii libakonadi-contact4 4:4.14.2-2+b1 ii libakonadi-kde4 4:4.14.2-2+b1 ii libakonadi-kmime4 4:4.14.2-2+b1 ii libakonadiprotocolinternals1 1.13.0-2 ii libc6 2.19-18 ii libcalendarsupport4 4:4.14.1-1 ii libfollowupreminder4 4:4.14.1-1 ii libgcc1 1:4.9.2-10 ii libgpgme++2 4:4.14.2-2+b1 ii libgrantlee-core0 0.4.0-2 ii libincidenceeditorsng44:4.14.1-1 ii libkabc4 4:4.14.2-2+b1 ii libkalarmcal2 4:4.14.2-2+b1 ii libkcalcore4 4:4.14.2-2+b1 ii libkcalutils4 4:4.14.2-2+b1 ii libkcmutils4 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdepim44:4.14.1-1 ii libkdeui5 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libkleo4 4:4.14.1-1 ii libkmanagesieve4 4:4.14.1-1 ii libkmime4 4:4.14.2-2+b1 ii libknewstuff3-4 4:4.14.2-5 ii libknotifyconfig4 4:4.14.2-5 ii libkontactinterface4a 4:4.14.2-2+b1 ii libkparts44:4.14.2-5 ii libkpgp4 4:4.14.1-1 ii libkpimidentities44:4.14.2-2+b1 ii libkpimtextedit4 4:4.14.2-2+b1 ii libkpimutils4 4:4.14.2-2+b1 ii libkprintutils4 4:4.14.2-5 ii libksieveui4 4:4.14.1-1 ii libktnef4 4:4.14.2-2+b1 ii libmailcommon44:4.14.1-1 ii libmailimporter4 4:4.14.1-1 ii libmailtransport4 4:4.14.2-2+b1 ii libmessagecomposer4 4:4.14.1-1 ii libmessagecore4 4:4.14.1-1 ii libmessagelist4 4:4.14.1-1 ii libmessageviewer4 4:4.14.1-1 ii libpimcommon4 4:4.14.1-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtwebkit4 2.3.4.dfsg-3 ii libsendlater4 4:4.14.1-1 ii libsolid4 4:4.14.2-5 ii libstdc++64.9.2-10 ii libtemplateparser44:4.14.1-1 ii perl 5.20.2-3+deb8u1 Versions of packages kmail recommends: ii gnupg-agent 2.0.26-6 ii gnupg22.0.26-6 ii pinentry-gtk2 [pinentry-x11] 0.8.3-2 Versions of packages kmail suggests: pn clamav | f-prot-installer ii kaddressbook 4:4.14.1-1 ii kleopatra4:4.14.1-1 ii procmail 3.22-24 pn spamassassin | bogofilter | annoyance-filter | spambayes | bsfi -- no debconf information
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
On Monday, August 03, 2015 07:09:37 PM Colin Tuckley wrote: > Have you checked that the Internet proxy settings in > "Preference->Program" are correct/sensible? For most people they should > be blank. Yep, no proxy here and it's all blank. > I'd suggest asking about this on the cqrlog forum, but first, have you > tried running cqrlog with the debug flag set on the command line and > looking through the output to see if anything obvious is visible? Nothing obvious shows up on the debug. I've opened a bug over on the forum. Maybe I'll have a quick resolution. http://www.cqrlog.com/node/1485 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
On Mon, 03 Aug 2015 13:32:19 -0400 Eric Christensen wrote: > On Monday, August 03, 2015 03:32:23 PM Colin Tuckley wrote: > > On 03/08/15 14:47, Eric Christensen wrote: > > > No, that fails too. I *can* go directly to TrustedQSL with an .adi and > > > have it sign and upload from there. Not sure why CQRLOG is failing. > > > > Can you please try the 1.9.0 package from testing. It installs and runs > > okay on a stable system without any problems. > > I still get the same error after upgrading to 1.9.0. Looking around at some of the other "issues" I've been having with CQRLOG (after moving to Debian) I think I see a pattern. It appears that CQRLOG doesn't recognize a connection to the Internet. Things like publishing the log to Clublog or using the DXCluster all seem to fail. >From the log publishing feature: HamQTH: Uploading WA3GFZ HamQTH: Upload failed! Check Internet connection I clearly have an Internet connection. Why would CQRLOG not see it? 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
On Monday, August 03, 2015 03:32:23 PM Colin Tuckley wrote: > On 03/08/15 14:47, Eric Christensen wrote: > > No, that fails too. I *can* go directly to TrustedQSL with an .adi and > > have it sign and upload from there. Not sure why CQRLOG is failing. > > Can you please try the 1.9.0 package from testing. It installs and runs > okay on a stable system without any problems. I still get the same error after upgrading to 1.9.0. 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
On Monday, August 03, 2015 03:32:23 PM Colin Tuckley wrote: > On 03/08/15 14:47, Eric Christensen wrote: > > No, that fails too. I *can* go directly to TrustedQSL with an .adi and > > have it sign and upload from there. Not sure why CQRLOG is failing. > > Can you please try the 1.9.0 package from testing. It installs and runs > okay on a stable system without any problems. I'd love to. I'm new to Debian, however, and I'm not sure how to grab the "testing" version. Could you provide me the proper magic for apt-get, please? 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
Do you have the TrustedQSL package installed? Yes. Do LoTW *uploads/exports* work okay? No, that fails too. I *can* go directly to TrustedQSL with an .adi and have it sign and upload from there. Not sure why CQRLOG is failing. 73, Eric WG3K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#794436: cqrlog: LoTW import/export does not work due to "Error: ssl_openssl"
Package: cqrlog Version: 1.8.2-1.1 Severity: important Dear Maintainer, * What led up to the situation? When I try to import LoTW QSLs I get the following error: NOT logged Error: 0 Error: Host not found Error: ssl_openssl This used to be caused by an openssl package not being installed but I think I've got everything installed properly. * What was the outcome of this action? The above error happened. * What outcome did you expect instead? I expected CQRLOG to pull down the QSLs from LoTW. -- 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 cqrlog depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libhamlib-utils 1.2.15.3-2+b1 ii libhamlib2 1.2.15.3-2+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libssl-dev 1.0.1k-3+deb8u1 ii libx11-6 2:1.6.2-3 ii mysql-client 5.5.44-0+deb8u1 ii mysql-client-5.5 [mysql-client] 5.5.44-0+deb8u1 Versions of packages cqrlog recommends: pn mysql-server | mariadb-server pn xplanet cqrlog suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: Failed to connect to the mount manager in win64
On Friday, July 31, 2015 05:33:23 PM jre wrote: > On 07/31/2015 05:15 PM, Eric Christensen wrote: > > On Friday, July 31, 2015 04:33:12 PM jre wrote: > >> Make a clean reinstall. First remove all wine packages (please post the > >> output) (one line): > >> > >> $ sudo apt-get purge wine wine-binfmt wine32 wine64 wine32-dev-tools > >> wine32-tools wine64-dev-tools wine64-tools fonts-wine libwine-dev > >> libwine-dbg libwine libwine:i386 wine-bin wine64-bin libwine-alsa > >> libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 > >> libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane > > Ups, the "fonts-wine" package does not exist in Jessie, therefore the > first command failed. Drop "fonts-wine" from the above command, then > repeat every other step, for the "ls -l" command use (one line): > > $ ls -l /usr/bin/wine32 /usr/lib/i386-linux-gnu/wine/bin/wine32 > /usr/lib/i386-linux-gnu/wine/bin/wine /usr/bin/wine64 And this fixes everything. Hmmm... Do you still want the outputs or the knowledge that all is right with the world again? It's all very odd. --Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: Failed to connect to the mount manager in win64
On Friday, July 31, 2015 04:33:12 PM jre wrote: Yeah, this is getting really strange... > Have you done any special > configuration or are you using a non-default filesystem? Not that I'm aware of. > Make a clean reinstall. First remove all wine packages (please post the > output) (one line): > > $ sudo apt-get purge wine wine-binfmt wine32 wine64 wine32-dev-tools > wine32-tools wine64-dev-tools wine64-tools fonts-wine libwine-dev > libwine-dbg libwine libwine:i386 wine-bin wine64-bin libwine-alsa > libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 > libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane > > Then reinstall the needed packages (again please post the output): > > $ sudo apt-get install wine wine32 wine64 libwine libwine:i386 > > > Then repeat all steps from my last mail. user@box:~$ sudo apt-get purge wine wine-binfmt wine32 wine64 wine32-dev-tools wine32-tools wine64-dev-tools wine64-tools fonts-wine libwine-dev libwine-dbg libwine libwine:i386 wine-bin wine64-bin libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package fonts-wine user@box:~$ sudo apt-get install wine wine32 wine64 libwine libwine:i386 Reading package lists... Done Building dependency tree Reading state information... Done wine is already the newest version. libwine:i386 is already the newest version. libwine:i386 set to manually installed. wine32:i386 is already the newest version. The following extra packages will be installed: libmpg123-0 Suggested packages: cups-bsd The following NEW packages will be installed: libmpg123-0 libwine wine64 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/16.1 MB of archives. After this operation, 125 MB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libmpg123-0:amd64. (Reading database ... 128324 files and directories currently installed.) Preparing to unpack .../libmpg123-0_1.20.1-2_amd64.deb ... Unpacking libmpg123-0:amd64 (1.20.1-2) ... Selecting previously unselected package libwine:amd64. Preparing to unpack .../libwine_1.6.2-20_amd64.deb ... Unpacking libwine:amd64 (1.6.2-20) ... Selecting previously unselected package wine64. Preparing to unpack .../wine64_1.6.2-20_amd64.deb ... Unpacking wine64 (1.6.2-20) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libmpg123-0:amd64 (1.20.1-2) ... Setting up libwine:amd64 (1.6.2-20) ... Setting up wine64 (1.6.2-20) ... Processing trigg
Bug#793879: Failed to connect to the mount manager in win64
On Wednesday, July 29, 2015 03:38:09 AM jre wrote: > Please run the following command and post the output after "-- System > Information:": > > reportbug --template -T none -s none -S normal -b --list-cc none -q 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 file1:5.22+15-2 ii wine32 1.6.2-20 wine recommends no packages. Versions of packages wine suggests: pn avscan | klamav | clamav ii binfmt-support 2.1.5-1 pn ttf-mscorefonts-installer pn winbind -- no debconf information > Also check the executable links themselves (errors in the link are not > catched: > > ls -l /usr/bin/wine32 /usr/bin/wine64 > ls -l --dereference /usr/bin/wine32 /usr/bin/wine64 $ ls -l /usr/bin/wine32 /usr/bin/wine64 ls: cannot access /usr/bin/wine64: No such file or directory lrwxrwxrwx 1 root root 37 Feb 23 01:40 /usr/bin/wine32 -> ../lib/i386-linux- gnu/wine/bin/wine32 $ ls -l --dereference /usr/bin/wine32 /usr/bin/wine64 ls: cannot access /usr/bin/wine32: No such file or directory ls: cannot access /usr/bin/wine64: No such file or directory > Verify your settings: > ls -l ~/.wine ~/.wine64 > echo "$WINEPREFIX , $WINELOADER , $WINEDEBUG , $WINEARCH , $WINEPREFIX" > $ ls -l ~/.wine ~/.wine64 ls: cannot access /home/user/.wine: No such file or directory ls: cannot access /home/user/.wine64: No such file or directory $ wine Downloads/amhc34062b.exe error: unable to find wine executable. this shouldn't happen. > Then try (one line!): > WINEARCH=win32 WINEDEBUG="fixme+all,err+all" WINEPREFIX="$HOME/.wine" wine > amhc34062b.exe $ WINEARCH=win32 WINEDEBUG="fixme+all,err+all" WINEPREFIX="$HOME/.wine" wine amhc34062b.exe error: unable to find wine executable. this shouldn't happen. So it appears that it's not creating ~/.wine any more. :/ --Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: Failed to connect to the mount manager in win64
On Wednesday, July 29, 2015 01:33:22 AM Jens Reyer wrote: > Given your "file" results your exe is 32-bit, so use this (again, after > deleting your old .wine and .wine64): > export WINEARCH=win32 > wine amhc34062b.exe Okay, so this is weird: $ wine amhc34062b.exe error: unable to find wine executable. this shouldn't happen. Before this: $ rm -fr .wine $ rm -fr .wine64/$ $ export WINEARCH=win32 $ wine amhc34062b.exe wine: created the configuration directory '/home/echristensen/.wine64' wine: '/home/echristensen/.wine64' is a 32-bit installation, it cannot support 64-bit applications. >From there, I made sure I removed wine64 and even removed wine and reinstalled it. That yielded the "unable to find wine executable" error. --Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: [pkg-wine-party] Bug#793879: (no subject)
On Tuesday, July 28, 2015 03:12:56 PM Austin English wrote: > >> > wine: Bad EXE format for Z:\home\echristensen\Downloads\amhc34062b.exe. > >> > >> Could you run 'file' on that executable? > > > > $ file amhc34062b.exe > > amhc34062b.exe: PE32 executable (GUI) Intel 80386, for MS Windows > > That's a 32-bit executable, not a 64-bit one. Try wine/wine32 instead of > wine64. $ wine amhc34062b.exe wine: Bad EXE format for Z:\home\echristensen\Downloads\amhc34062b.exe. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: [pkg-wine-party] Bug#793879: (no subject)
On Tuesday, July 28, 2015 02:39:45 PM Austin English wrote: > You're not getting any messages about creating a WINEPREFIX, so it > looks like you're using an existing one still. How do I find out what's being used? I didn't see WINEPREFIX being set anywhere that I grep'd. > > > wine: Bad EXE format for Z:\home\echristensen\Downloads\amhc34062b.exe. > > Could you run 'file' on that executable? $ file amhc34062b.exe amhc34062b.exe: PE32 executable (GUI) Intel 80386, for MS Windows Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: (no subject)
I'm trying to run these from directly from the command line so there isn't a WINEPREFIX involved in this. When I try to use wine64 to reinstall the program I get this: $ wine64 Downloads/amhc34062b.exe fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2 wine: Bad EXE format for Z:\home\echristensen\Downloads\amhc34062b.exe. --Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#793879: wine: Failed to connect to the mount manager
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 file1: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 ii binfmt-support 2.1.5-1 pn ttf-mscorefonts-installer pn winbind -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
