Bug#578937: Problem still exists with courier 0.65.0-2

Niccolo Rigacci wrote: > I got the same problem after a system upgrade. > > The /usr/bin/imapd binary contains the correct string (with the > space between "*" and "OK"), but still the IMAP client complains. > So the problem seems not to be the space. If I'm not mistaken, the upstream bug Guill

Bug#533604: Doesn't bind to IPv6 addresses by default

Stefan Bauer schrieb: > Am 27.02.2010 17:43, Fabian Knittel schrieb: >> With a few tweaks to /etc/gai.conf I managed to change the order: >> >> $ python -c "import socket; print socket.getaddrinfo(None, 'auth', >> 0, socket.SOCK_STREAM, 0, socket.AI_PA

Bug#533604: Doesn't bind to IPv6 addresses by default

Stefan Bauer schrieb: > Sounds logical, i just cant confirm this thesis: Ah sorry, I didn't realise that you couldn't confirm the bug report. I thought we were only discussing the best possible solution. > black:/home/sb# cat /proc/sys/net/ipv6/bindv6only > 0 > > black:/home/sb# ps aux |grep oid

Bug#533604: Doesn't bind to IPv6 addresses by default

Stefan Bauer schrieb: > Am 25.02.2010 12:53, Fabian Knittel schrieb: >> That's really weird... I can properly see both sockets (IPv4 and IPv6) >> with lsof and netstat (bindv6only=0). >> >> But I'm running squeeze and linux kernel image 2.6.32-trunk-amd64,

Bug#533604: Doesn't bind to IPv6 addresses by default

Stefan Bauer schrieb: > Follow up - tested on a lenny machine which turns me nuts: > > bindv6only=0 > /etc/default/oidentd is without any -a stanzas > black:/home/sb# lsof -itcp:113 > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > oidentd 19499 oident6u IPv6 47082698 TCP *:a

Bug#533604: Doesn't bind to IPv6 addresses by default

tag 533604 +patch thanks Hi, Stefan Bauer wrote: > Am 23.02.2010 12:15, Philipp Kern schrieb: >> Stefan, >> >> am Tue, Feb 23, 2010 at 12:06:04PM +0100 hast du folgendes geschrieben: >>> i'm aware of that problem but still seeking for an easy solution as >>> i'm not familiar with socket programm

Bug#563911: libgl1-mesa-dri: [r600] drmRadeonCmdBuffer: -22.

Hello, in January, I was able to reproduce the reported problems, but current squeeze appears to have slightly improved things: I no longer see the reported errors and OpenGL applications start-up fine. Unfortunately, the textures are completely broken, so accelerated 3D is still unusable. The go

Bug#560493: guessnet: FTBFS: string.h:63: error: 'vasprintf' was not declared

The build failure seems to concern libwibble-dev instead of guessnet. In addition, it appears that the problem was resolved, as the guessnet build succeeds for current lenny and sid environments (as soon as #570306 is fixed). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.or

Bug#570306: FTBFS: runner/fake.cc:32: error: 'printf' was not declared in this scope

Package: guessnet Version: 0.51-1 Severity: important Tags: patch Justification: fails to build from source Apparently guessnet no longer builds from source: g++ -DHAVE_CONFIG_H -I. -I.. -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -DSCRIPTDIR=\"/usr/share/guessnet/test\"

Bug#507815: consolekit: race condition during D-Bus activation

Package: consolekit Version: 0.2.10-2 Severity: normal Hello, on a system where ConsoleKit is only used sporadically, a race condition caused by the interaction between D-Bus' activation code and console-kit-daemon's backgrounding has surfaced. If console-kit-daemon backgrounds quickly enough th

Bug#423928: libpam-pgsql: unnecessarily SQL-escapes option values from trusted source

ckages. -- no debconf information This patch removes unnecessary SQL escaping of the options table name and column names. This allows more complex SQL constructs within the aforementioned options when specified via the configuration file. -- Fabian Knittel <[EMAIL PROTECTED]> diff -urN pam-pgsql

Bug#279581: Bug 279581, libnss-pgsql1: Christian's patch fails to work for libpq4

Hi, unfortunately, Christian's patch (using PQconnectdb instead of PQsetdbLogin) does not work / suffice for libpq4. Without a running nscd, PQconnectdb attempts to setup the SSL environment and searches for $HOME/.postgresql/server.crt (or similar), calling getpwuid to retrieve the home-director

Bug#344563: Easy fix ?

[ Sorry, Nikita, private mail was unintentional. ] Hi, On Thu, Apr 27, 2006 at 11:42:12AM +0400, Nikita V. Youshchenko wrote: > > Removing the databases in /var/db/nscd/ resolved the problem. > > So why not just remove old files on nscd package upgrade?.. Deleting the corrupted cache only temp

Bug#307366: libpam-pgsql: new package misses features/fixes from NMUs

Package: libpam-pgsql Version: 0.5.2-8 Severity: important Hi, since 0.5.2-8 the perfectly working MD5 support included in 0.5.2-7.2 has been removed again. Apparently the fixes from the NMUs since 0.5.2-7 weren't included (at least the changelog completely omits them - although this might be com

Bug#203222: libpam-modules: Can't change expired password with NIS

Hi Sam, On Thu, Jul 31, 2003 at 03:43:50PM -0400, Sam Hartman wrote: [...] > Which is exactly the problem. pam_unix should only work with > /etc/shadow or NIS for the passwd entry point. If getpwnam is used, > it might get far enough to try and change the password of an ldap > account or somethi