Bug#931818: Please close this bug

2019-10-28 Thread Jeffrey E. Hundstad
Hello, Please close this bug.  I don't see anyone else that's having the same issue.  I now have a working cups installation myself. I removed all the cups packages and associated unique support packages.  I then followed: https://wiki.debian.org/SystemPrinting This instructed me to: apt

Bug#628864: Fldigi fails to start, gives getMenuItem error

2011-06-08 Thread Jeffrey E. Hundstad
Hello, I can replicate this problem. It happens on 32 and 64-bit Intel platforms. It also happens using gcc-4.6 or gcc-4.4. However if you disable Native Language Support (NLS) I now have a binary that functions. Sans NLS of course. I've used: ./configure --disable-nls I have reported

Bug#536321: python-tk: segmentation fault #536702

2009-08-09 Thread Jeffrey E. Hundstad
Quoting python-tk: segmentation fault Bug #536702 2.5.2-1.1 causes a segmentation error. 2.5.2-1 does not. Downgrading restores usability. When I do the same then wsjt works again. -- Jeffrey Hundstad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#335968: gramps: Segmentation fault

2005-10-26 Thread Jeffrey E. Hundstad
Alex Roitman wrote: On Wed, 2005-10-26 at 21:33 -0500, Jeffrey Hundstad wrote: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210210624 (LWP 10033)] 0xb7e49b2b in strlen () from /lib/tls/i686/cmov/libc.so.6 [snip] Since it segfaulted in the i686

Bug#323141: update on cpio

2005-08-30 Thread Jeffrey E. Hundstad
Here is some additional info: 1. I've verified that the current GNU version, http://ftp.gnu.org/gnu/cpio/cpio-2.6.tar.bz2 , DOES NOT have this bug. 2. Debian cpio version 2.6-4 still contains the bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?