Bug#628237: Info received (slapd refuses to start ... just to let you know ;))

Recompiling the package solves my problem. BTW, I have cyrus and cyrus updated sasl and then slapd broke at restart... :S On 2011-06-02, at 1:39 AM, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an aut

Bug#628237: slapd refuses to start ... just to let you know ;)

-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#620321: cyrus-imapd-2.4: When upgrading to cyrus 2.2/2.4, it shouldn't try to restart it

Package: cyrus-imapd-2.4 Version: 2.4.7-3 Severity: critical Tags: experimental Justification: breaks the whole system When upgrading to cyrus 2.2/2.4, it cannot start with the following messages: Mar 31 20:14:27 wolfe cyrus/lmtpunix[21633]: incorrect version of Berkeley db: compiled against 5.1

Bug#564322: {Spam?} with kernel 2.6.33-rc2, udev wrongfuly whines about signalfd and inotify_user not being compiled in the kernel

Package: udev Version: 149-2 Severity: critical Justification: breaks the whole system What: - inotify(2) (CONFIG_INOTIFY_USER) - signalfd(2) (CONFIG_SIGNALFD) It is present: $ zcat config.gz | egrep -i "inotify|signalfd"

Bug#547614: ircd-irc2: Fatal Error: No working P-line in ircd.conf

Package: ircd-irc2 Version: 2.11.2p1+dfsg-1 Severity: grave Justification: renders package unusable When I try to start ircd, I get this error message: opening stream socket irc.localhost:Address family not supported by protocol Fatal Error: No working P-line in ircd.conf According to my readings

Bug#327097: Debugging code for XDM

DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value  /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value  /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.au

Bug#327121: xdm: Can't remotely connect to this computer using XDMCP protocol.

Package: xdm Version: 6.8.2.dfsg.1-6 Severity: grave Justification: renders package unusable It previously worked but doesn't anymore. It does the samethign on two computers running unstable. I tried to run gdb on it, but didn't find anything. I found that in /var/log/xdm.log Mon Aug 22 23:21

Bug#327097: xdm: Can't connect remotely to the XDM server since last upgrade.

Package: xdm Version: 6.8.2.dfsg.1-6 Severity: grave Justification: renders package unusable What I found in /var/log/xdm.log: Wed Sep 7 11:58:34 2005 xdm info (pid 11335): not sourcing /usr/X11R6/lib/X11/xdm/Xsetup (No such file or directory) Wed Sep 7 11:59:36 2005 xdm info (pid 11326): shut

Bug#325277: Kmerlin: kmerlin is broken (javascript?)

Package: Kmerlin Version: 1.4.2-3 Severity: grave Justification: renders package unusable Well, it seems it just can't work! It should be removed or fixed. If it's not fixed, remove it... if it's fixed, keep it. But it's been a month or so and still no answer from the maintainer. Well, it is

Bug#325092: kmail: Kmail segfault with libqt3c102-mt but works fine with libqt3-mt, but this situation isn't a livable one.

Package: kmail Version: 4:3.3.2-3 Severity: grave Justification: renders package unusable GDB= Received signal SIGSEGV, Segmentation fault. [Switching to Thread -1244882720 (LWP 29713)] 0xb758e95b in QString::QString () from /usr/lib/libqt-mt.so.3 quite simple from this point of vue! dpkg --fo