Bug#872579: xjed does not receive keyboard input unless you kill ibus-daemon

Package: xjed Version: 1:0.99.19-7+b1 Severity: important I recently dist-upgraded to a new version of various packages and found that xjed (both 0.99.18+dfsg.1-11_amd64 and 0.99.19-7+b1_amd64) had stopped working at all. The symptoms are: - No response to keyboard input - No response to SIGINT -

Bug#739852: uhd-host: Patch for building uhd 3.7.0 in debian-unstable

rom 05c7af8edefc970a0fd86596a3e0c93fc794c911 Mon Sep 17 00:00:00 2001 From: Avery Pennarun Date: Sat, 22 Feb 2014 18:48:47 -0800 Subject: [PATCH] Add some inttypes.h/stdint.h to workaround some boost versions. It's slightly inelegant to add these C-style includes, but they've been standardized for a long

Bug#631169: bash prompts with newlines and hidden characters get confused

Package: bash Version: 3.2-4 Try the following command sequence on an 80-column terminal. mkdir -p /tmp/big-long-dir/with/lots/of/sub/directories cd /tmp/big-long-dir/with/lots/of/sub/directories mkdir -p so/this/gets/super/long/more/more/more/more/more cd so/this/gets/super/long/more/more/more/m

Bug#564600: bup package

On Thu, Apr 1, 2010 at 5:27 AM, Jon Dowland wrote: > I've put a (very) initial git repository for Debian > packaging in the collab-maint space > > > > clone from > > 'master' is tracking upstream/master -- the debian branch is > the intere

Bug#564600: bup package

Good news! There's a whole suite of man pages included in bup now. I think by the time the next Debian-stable release comes out, bup ought to be in very good shape for inclusion. It's still missing a few features, but it already makes useful backups. Avery -- To UNSUBSCRIBE, email to debian

Bug#541428: lighttpd doesn't do linger-on-close correctly, messing up pipelining clients

ailable) -- no debconf information commit 9ecb4c72816acd71f810c8d6db88cf829027fc10 Author: Avery Pennarun Date: Thu Aug 13 22:06:31 2009 -0400 Fix linger-on-close behaviour to avoid rare failure conditions. - Don't assume that when FIONREAD returns 0, that it's safe to c

Bug#485725: noip2 puts config file in /var instead of /etc

Package: noip2 Version: 2.1.7-9 Severity: normal Debian policy requires configuration files to be in /etc, not in /var, even for apps that use /var by default. noip2 should be patched to comply with this. -- System Information: Debian Release: lenny/sid APT prefers gutsy-updates APT policy:

Bug#339037: open(2) man page doesn't document potentia

On Thu, Nov 17, 2005 at 03:59:58PM +0100, Michael Kerrisk wrote: > > It appears you *have* to open in blocking mode in order to > > open a leased file at all, > > Yes. > > > but that's not clear from the description. > > Again, I would say that's fairly clear from the man page: > if the open()

Bug#339037: open(2) man page doesn't document potential EWOULDBLOCK return code

Package: manpages-dev Version: 1.60-2 We've just been bitten by this at work. If you read the LEASES section of fcntl(2), it explains that open() with O_NONBLOCK could cause open to return EWOULDBLOCK. This is not explained anywhere on the open() page; open() has many possible return codes, none

Bug#320400: Acknowledgement (gnupod-tools: gnupod uploads mp3 files that cannot be played by iPod)

I found out how to fix the problem. Near the top of /usr/share/perl5/GNUpod/XMLhelper.pm: use constant MAX_PATHLENGTH => 64; I changed it to: use constant MAX_PATHLENGTH => 50; And my problems went away. Since the filename itself is invisible from the iPod UI anyway, this see

Bug#320400: gnupod-tools: gnupod uploads mp3 files that cannot be played by iPod

Package: gnupod-tools Version: 0.98-2 Severity: normal I uploaded a bunch of mp3 files to my iPod using gnupod_addsong. It was very straightforward, but after I did it, many of the songs wouldn't play. After some investigation, I noticed a pattern: songs with particularly long names didn't seem

Bug#317527: [Popcon-developers] Bug#317527: Unclear questions during package configuration

On Sat, Jul 09, 2005 at 06:05:56PM +0200, Christian Perrier wrote: > > > During installation, I am asked the question: > > -- > > If you do not want to use HTTP, email is used instead. > > Use HTTP to submit reports? >