Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-07 Thread Laurence Abbott
I can confirm that adding "-v" to the two udevadm trigger commands,i.e., udevadm trigger --type=subsystems --action=add -v udevadm trigger --type=devices --action=add -v does indeed load the missing modules (on the second command) for me, too, and boot proceeds normally once I exit the initramfs

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-06 Thread Laurence Abbott
I'm pretty sure I came across the same issue yesterday: I ran a dist-upgrade on an X99-based system (the first for several months) and the system was left unbootable. My root system is on raid and booting failed with mdadm errors about it not being able to find any of the raid arrays listed in

Bug#410794: kmail: Imap messages become blank

2007-02-13 Thread Laurence Abbott
Package: kmail Version: 4:3.5.5.dfsg.1-6 Severity: grave Justification: causes non-serious data loss Sometimes an IMAP message becomes blank, i.e. shows no content. Using a different IMAP client shows that the content is still there. Looks like kmail is caching the messages locally and not