Bug#1051161: postfix: Postfix does not start with default configuration

ed (exited)". journalctl for the service just says that "A start job for unit postfix.service has finished successfully." but no processes are running. It is possible to start Postfix with the command "postfix start", then it runs as expected. But I would expect the systemd co

Bug#981921: dovecot-imapd: imapd crashes with "Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0)"

Package: dovecot-imapd Version: 1:2.3.4.1-5+deb10u5 Severity: normal Dear Maintainer, since late january I have seen a couple of crashes of imapd in the logs. The error message logged is Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count >

Bug#856733: linux-image-3.16.0-4-amd64: Xen guest has multiple stack dumps, ending with spontaneous reboot

Package: src:linux Version: 3.16.39-1+deb8u1 Severity: important Dear Maintainer, after installing the latest linux-image update, one of my Xen guests suddenly logged multiple kernel stacktraces. The initial one was this: Mar 4 03:05:14 saltmaster kernel: [798533.537459] WARNING: CPU: 1 PID:

Bug#759809: linux-image-3.2.0-4-amd64: USB 3 devices fail, logging xHCI xhci_drop_endpoint called with disabled ep ffff8802165db0c0

Package: src:linux Version: 3.2.60-1+deb7u3 Severity: normal Dear Maintainer, Yesterday morning I rebooted a machine running Wheezy (stable) after installing kernel upgrade 3.2.60-1+deb7u3. Upon reboot, the machine hung while detecting two USB-3 attached harddisks. After unplugging the two

Bug#741989: linux-image-3.2.0-4-amd64: Regression bug #741989 also in Stable kernel 3.2.60-1+deb7u3 Followup-For: Bug #741989 Package: src:linux Version: 3.2.60-1+deb7u3

Dear Maintainer, This morning I rebooted a machine runnig Wheezy (stable) after installing kernel upgrade 3.2.60-1+deb7u3. Upon reboot, the machine hung while detecting two USB-3 attached harddisks. After unplugging the two harddisks, boot continued. Re-connecting them caused the same errors

Bug#708183: linux-image-3.2.0-4-amd64: File access via symlink on tmpfs filesystem gives permission denied

Package: src:linux Version: 3.2.41-2 Severity: important Dear Maintainer, on the 3.2.0-4 kernel, access to a directory via a symlink on a tmpfs filesystem gives permission denied - if the tmpfs filesystem mountpoint is not owned by root. The same setup on a 2.6.32-5 (Squeeze) system works fine.

Bug#651205: tumgreyspf: Please include upstream fix for accepting mail when SPF record has an error

Package: tumgreyspf Version: 1.35-7 Severity: wishlist tumgreyspf 1.35 (current version in Debian) causes mail to be rejected, if the sender-domain has an invalid SPF record (SPF check returns a Permerror). This can cause valid mail to be rejected. In version 1.36, released a couple of weeks

Bug#615589: installation-reports: Partitioning completes without creating bios_boot partition required by GRUB

Package: installation-reports Severity: minor Tags: d-i During manual partitioning - at least on 2 TB+ harddisks - the Debian installer creates a GUID partition table (GPT). This type of partitioning requires a small BIOS boot partition to be set aside for use by GRUB. However, this is not

Bug#615215: installation-reports: Boot failure after install w/ GPT partitioning on Intel motherboard(s)

Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable During installation, the partitioning creates a GPT (GUID partition table) on disk, i.e. the old-style MBR partition only has a single type 0xEE partition listed. The 0xEE partition is created

Bug#516571: gdb on SPARC fails with regcache.c:175: internal-error: register_size: assertion failure

Package: gdb Version: 6.4.90.dfsg-1 Severity: normal While trying to debug a program on Debian/SPARC I loaded the binary and a core-dump into gdb. A simple bt then caused the following error (after displaying part of the backtrace, but not all of it):

Bug#422324: Acknowledgement (linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs NWFPE: ntpd[1694] takes exception 00000001)

Hi Martin, I'm sorry, but I no longer have access to this hardware so I cannot tell if the problem has been resolved. Regards, Henrik On Tue, Jun 10, 2008 at 11:16:25AM +0200, Martin Michlmayr wrote: * Henrik Stoerner [EMAIL PROTECTED] [2007-05-05 11:02]: I checked the kernel logs looking

Bug#422324: linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs NWFPE: ntpd[1694] takes exception 00000001

Package: linux-image-2.6.18-4-footbridge Version: 2.6.18.dfsg.1-12etch1 Severity: grave Justification: causes non-serious data loss After updating to the kernel version released with DSA-1286-1, the system has begun to spontaneously reboot. This is a small Netwinder system, which has been

Bug#422324: Acknowledgement (linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs NWFPE: ntpd[1694] takes exception 00000001)

I checked the kernel logs looking for this error message. The system was upgraded to Etch on April 10, and there are NO entries of the NWFPE log until after the DSA-1286-1 security update is installed. So it looks like this might be related to the changes introduced with this update. Going

Bug#327083: dhcping: Loops indefinitely while parsing commandline options

Package: dhcping Version: 1.2-2 Severity: grave Tags: patch Justification: renders package unusable dhcping uses getopt(3) to parse commandline options. In doing this, it goes into an infinite loop while parsing the command dhcping -c 172.16.10.3 -s 172.16.10.2 -h 00:10:57:C0:1B:E6 The code in

Bug#315549: kernel-image-2.6.8-2-sparc64: Fails to recognize and start md2 during boot

Package: kernel-image-2.6.8-2-sparc64 Version: 2.6.8-15 Severity: normal This kernel fails to recognize all LVM RAID-1 devices. It will automatically detect md0 and md1, but fails to detect md2. During bootup it therefore fails to mount the filesystem on this partition and drops to a console