A clean reinstall took care of the issue a long time ago. No longer an
issue. Thank you,
On Nov 30, 2012 5:45 AM, Thomas Hotz thomas.h...@gmail.com wrote:
Is this still an issue for you? What Ubuntu version do you use? Thank
you for telling us!
** Changed in: initramfs-tools (Ubuntu)
Public bug reported:
Binary package hint: konsole
Begining in Jaunty (Ubuntu 9.04) Konsole does not appear to respond to
the curs_set() curses function as it has previously, causing any curses
app that calls curs_set() to fail when accessed from Konsole.
In testing, the app still works fine on
I'm on a stock Jaunty install with all updates applied and I'm seeing
the EXACT same behaviour. kbluetooth4 starts in 'offline mode', and I
get:
arguments to dbus_message_new_method_call() were incorrect, assertion
path != NULL failed in file dbus-message.c line 1070
when running
Bug 223066 (which I just filed a few days ago) may be a duplicate of
this issue.
I saw the exact same behavior when upgrading from Fiesty to Gutsy. I
continued running with the fiesty kernel (2.6.20.15 I believe is the
only one that continues to boot), and I am still doing so even after
upgrading
Public bug reported:
Binary package hint: initramfs-tools
This has been an ongoing issue for me since kernel 2.6.20, but it was
the (once again) unsuccessful upgrade that caused me to finally report
it.
From what I can tell the initrd-x.x.xx-x-generic begining on 2.6.22+
fails to load any of
Modules, that should say. it builds the proper modules into the
image:
[EMAIL PROTECTED]:~$ cat init.out | grep ata
Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/libata.ko
Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/scsi/eata.ko
Copying module directory
I can confirm that this bug is NOT fixed in 2.6.24 (Hardy). I
experienced the same issue when upgrading from 2.6.20 (which boots) to
2.6.22 (which hangs immediately), and upgrading to 2.6.24 exhibits the
exact same behavior.
Status of this bug appears to be 'confirmed', so I'm not sure if I
I'm not even sure that my comment on this bug relates to the original issue
- but as far as I know yes, this still exists, at least with the latest
available Gutsy Kernel Anything 2.6.22 or newer fails to boot on my
laptop, complaining that it can't mount the root filesystem. 2.6.20 or older
I can't say for certain if this is the same issue - I upgraded to the
gibbon yesterday, and upon a reboot the system would not come up. The
recovery kernel (2.6.22-14-generic, I think) shows:
BEGIN: Waiting for root filesystem
and it never boots. The Edgy kernel, 2.6.20-16, boots fine. I thought
