Package: kicker
Version: 4:3.5.0-4
Severity: critical
Justification: breaks the whole system
Public File Server Applet tries to publish the service and crashes kicker
leaving KDestktop nearly unusable. Follows the backtrace:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread
Here's the output of dpkg-reconfigure
$ sudo dpkg-reconfigure linux-image-2.6.14-2-k7
Password:
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.14-5 was configured last, accord
I attach the output of "yaird -d -t" if it is useful.
Pau
A Saturday 17 December 2005 18:55, Sven Luther va escriure:
> On Fri, Dec 16, 2005 at 01:14:32PM +0100, Pau Capdevila wrote:
> > Package: linux-image-2.6.14-2-k7
> > Version: 2.6.14-5
> > Followup-For: Bug
:
> On Fri, Dec 16, 2005 at 01:14:32PM +0100, Pau Capdevila wrote:
> > Package: linux-image-2.6.14-2-k7
> > Version: 2.6.14-5
> > Followup-For: Bug #343443
> >
> >
> > The default installation did not boot failing to found hard disk devices.
>
> So, what
Package: linux-image-2.6.14-2-k7
Version: 2.6.14-5
Followup-For: Bug #343443
The default installation did not boot failing to found hard disk devices.
Generating initrd with old mkinitrd generated a valid initrd image. With all
the needed modules to boot my machine.
I figure it out only by look
Package: linux-image-2.6.14-1-k7
Version: 2.6.14-2
Severity: critical
Justification: breaks the whole system
Booting with original initrd gives black screen.
Regenerating initrd with yaird solved the problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT po
Subject: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534!
Package: kernel-image-2.6.10-1-686
Version: 2.6.10-6
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
When the following occurs:
Apr 3 21:59:31 localhost kernel: hd
7 matches
Mail list logo
