Bug#804740: apper: Won't ask for password and fails to do action

2015-11-10 Thread Eric Christensen
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

Bug#797844: kmail: TLSv1.1 and TLSv1.2 are not supported

2015-09-02 Thread Eric Christensen
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

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-03 Thread Eric Christensen
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

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-03 Thread Eric Christensen
On Mon, 03 Aug 2015 13:32:19 -0400 Eric Christensen e...@christensenplace.us 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

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-03 Thread Eric Christensen
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

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-03 Thread Eric Christensen
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

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-03 Thread Eric Christensen
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,

Bug#794436: cqrlog: LoTW import/export does not work due to Error: ssl_openssl

2015-08-02 Thread Eric Christensen
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

Bug#793879: Failed to connect to the mount manager in win64

2015-07-31 Thread Eric Christensen
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:

Bug#793879: Failed to connect to the mount manager in win64

2015-07-31 Thread Eric Christensen
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): $

Bug#793879: Failed to connect to the mount manager in win64

2015-07-31 Thread Eric Christensen
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

Bug#793879: Failed to connect to the mount manager in win64

2015-07-28 Thread Eric Christensen
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

Bug#793879: wine: Failed to connect to the mount manager

2015-07-28 Thread Eric Christensen
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

Bug#793879: (no subject)

2015-07-28 Thread Eric Christensen
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 LMountMgr failed to start:

Bug#793879: [pkg-wine-party] Bug#793879: (no subject)

2015-07-28 Thread Eric Christensen
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

Bug#793879: [pkg-wine-party] Bug#793879: (no subject)

2015-07-28 Thread Eric Christensen
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