[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13 -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There's a related thread on Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=402758 According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda* A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
I used dist-upgrade from edgy->feisty. After I edited /etc/fstab
manually and replaced /dev/hda* with UUID, the system boots and mounts
disks - but there are still no /dev/hda* devices so this breaks hdparm
and other things.
On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.
Comparing 'fdisk -l' output on the same host booted single-user mode
with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda ->
/dev/sdc:
{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start End Blocks Id System
> /dev/sdc1 * 1195815727603+ 7 HPFS/NTFS
> /dev/sdc219592695 5919952+ 83 Linux
> /dev/sdc326963296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc43297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc532978395409576867 HPFS/NTFS
> /dev/sdc683968518 987966 82 Linux swap / Solaris
> /dev/sdc78519 1992991658826 83 Linux
--
Kernel 2.6.20-14 does not boot anymore
https://bugs.launchpad.net/bugs/104232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104232] Re: Kernel 2.6.20-14 does not boot anymore
There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc* -- Kernel 2.6.20-14 does not boot anymore https://bugs.launchpad.net/bugs/104232 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Something similar here. Yesterday I have upgraded from Intrepid to Jaunty (dist-upgrade) and now when I use the logout button, there is no action. More than that, kwin stops responding to mouse events - I can switch between applications/dekstops using keyboard, and mouse works in application windows. But when I click on the root window or panel, nothing happens. Then after about a minute kwin starts responding again (but still no logout). Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
I have found a thread discussing Nvidia driver problems, https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335879 After upgrading to 180.37 driver (using URLs provided in the thread mentioned above) I don't see the problem anymore - logout/shutdown works perfectly. It seems that Nvidia driver 180.35 had broken signal processing. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 325543] Re: KDE does not always logout/shutdown/reboot successfully
Hi Michael, did you try to look at the contents of ~/.xsession-errors from text console? It often helps a lot as it might contain error messages. And it makes sense to look at dmesg output, to see whether audit prevents some operations. Alex -- KDE does not always logout/shutdown/reboot successfully https://bugs.launchpad.net/bugs/325543 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340301] [NEW] powernowd does not start cleanly on Jaunty
Public bug reported:
The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice
LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'`
But modern module-init-tools package installs /bin/lsmod, not
/sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see
recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that
the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in
postinstallation script, I reinstalled it - no link has been created.
** Affects: powernowd (Ubuntu)
Importance: Undecided
Status: New
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340301] Re: powernowd does not start cleanly on Jaunty
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
software...)
We probably need to submit a separate bugreport for acpid.
Alex
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386715] Re: Digikam not working with kde 4.3 beta 2
This is due to changes in marble. If you look at ~/.xsession-errors you will see an unresolved symbol. Downgrading just marble packages makes digikam work again, I used ii libmarble4 4:4.2.2-0ubuntu1 Marble globe widget library ii marble 4:4.2.2-0ubuntu1 Marble globe and map widget ii marble-data4:4.2.2-0ubuntu1 data files for Marble The problem is described in http://www.csamuel.org/2009/05/23/digikam-problem-with-kde-43-beta-1, digikam needs to be rebuilt. According to URL above, it is already rebuilt as part of deb http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu jaunty main -- Digikam not working with kde 4.3 beta 2 https://bugs.launchpad.net/bugs/386715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
