Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles

2012-07-07 Thread Joshua
Package: linux-2.6 Version: 3.0.0-3 Severity: important Dear Maintainer, I have some nonstandard console settings that require running /etc/init.d/kbd to configure console. Using the newer console-setup is a non-starter for reasons that are not relevant at this time. Somewhere in the last two

Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles

2012-07-07 Thread Jonathan Nieder
Hi, Joshua wrote: > Version: 3.0.0-3 [...] > I have some nonstandard console settings that require running > /etc/init.d/kbd to configure console. Using the newer console-setup > is a non-starter for reasons that are not relevant at this time. > > Somewhere in the last two months (it's hard to t

Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles

2012-07-07 Thread Joshua Hudson
For some reason a new apt-get dist-upgrade fixed bug. A new kernel package was pulled but the version did not change. On 7/7/12, Jonathan Nieder wrote: > Hi, > > Joshua wrote: > >> Version: 3.0.0-3 > [...] >> I have some nonstandard console settings that require running >> /etc/init.d/kbd to conf

Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles

2012-07-07 Thread Jonathan Nieder
Hi, Joshua Hudson wrote: > For some reason a new apt-get dist-upgrade fixed bug. A new kernel > package was pulled but the version did not change. You can get the version of the kernel package with dpkg-query -W linux-image-$(uname -r) or cat /proc/version Perhaps the package

Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles

2012-07-08 Thread Joshua Hudson
Package version changed from 3.0.0-2 to 3.0.0.3. Incidentally I have upgraded to 3.2 and the problem does not occur there either. On 7/7/12, Jonathan Nieder wrote: > Hi, > > Joshua Hudson wrote: > >> For some reason a new apt-get dist-upgrade fixed bug. A new kernel >> package was pulled but the