Public bug reported:
Binary package hint: update-manager
Update manager hung at "generating locales". Update finished with several
errors and several packages were not installed...
Upgrade finished with message that upgrade manager could not continue and
after reboot dpkg --configure -a would
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/16872197/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibrarian.net/16872201/VarLogDistupgradeApttermlog.gz
** Attachment added: "VarLogDistupgradeMainlog.gz"
/var/log/dist-upgrade/apt.log attached as requested.
** Attachment added: "apt.log"
http://launchpadlibrarian.net/16887810/apt.log
--
package update-manager None [modified: /var/lib/dpkg/info/update-manager.list]
failed to install/upgrade: ErrorMessage: SystemError in cache.commit():
E:Sub-
/var/log/dist-upgrade/main.log as requested.
** Attachment added: "main.log"
http://launchpadlibrarian.net/16887840/main.log
--
package update-manager None [modified: /var/lib/dpkg/info/update-manager.list]
failed to install/upgrade: ErrorMessage: SystemError in cache.commit():
E:Sub-proce
/var/log/dist-upgrade/main_pre_req.log
** Attachment added: "main_pre_req.log"
http://launchpadlibrarian.net/16887857/main_pre_req.log
--
package update-manager None [modified: /var/lib/dpkg/info/update-manager.list]
failed to install/upgrade: ErrorMessage: SystemError in cache.commit():
E:
/var/log/dist_upgrade/term.log as requested.
** Attachment added: "term.log"
http://launchpadlibrarian.net/16887865/term.log
--
package update-manager None [modified: /var/lib/dpkg/info/update-manager.list]
failed to install/upgrade: ErrorMessage: SystemError in cache.commit():
E:Sub-proces
/var/log/dist_upgrade/apt_term.log as requested.
** Attachment added: "apt-term.log"
http://launchpadlibrarian.net/16887877/apt-term.log
--
package update-manager None [modified: /var/lib/dpkg/info/update-manager.list]
failed to install/upgrade: ErrorMessage: SystemError in cache.commit():
Thanks Izzy. Your work-around solved this problem for me.
--
Gutsy->Hardy upgrade hangs in localedef
https://bugs.launchpad.net/bugs/249340
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.ub
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/13654423/dmesg.txt
--
Guidance-power-manager stopped working after upgrade to Gutsy
https://bugs.launchpad.net/bugs/220324
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-gu
Public bug reported:
Guidance-power-manager worked well under Dapper and Feisty on this
notebook PC. After upgrade from Feisty to Gutsy, the power
manager/battery monitor icon is not available. When I manually start
guidance-power-manager I get several error messages
Output of $ guidance-power-ma
I was able to run gnome-power-manager 1 time. It reported my cordless
mouse battery was at 14%. After I replaced the batteries in the mouse
the gnome-power-manager went away. It did not give my laptop's battery
condition or indicate whether the unit was plugged in or not.
I don't yet have Hardy in
It seems I need acpid running, but when I try to install acpid I get
powersaved errors...
[EMAIL PROTECTED]:/etc/init.d$ sudo apt-get install acpid
Reading package lists... Done
Building dependency tree
Reading state information... Done
acpid is already the newest version.
0 upgraded, 0 newly inst
ACPID was set to Not start at boot. Changed that and now power
management starts, but it still does not give any information about the
notebook battery. It assumes the battery is not present. The attached
screen capture shows the Power Manager window with all "Battery Powered"
functions disabled.
After removing powersaved and restarting my notebook, guidance-power-
manager is working again, however I am still not seeing my battery
status. The problem now seems to be that acpid is doing it's job and
reporting status for 2 batteries...
[EMAIL PROTECTED]:~$ grep -r "" /proc/acpi/battery/*
/pr
Here's the output of "hal-device `hal-find-by-capability --capability
battery`"...
udi = '/org/freedesktop/Hal/devices/usb_device_46d_c501_noserial'
info.capabilities = { 'battery' } (string list)
battery.command_interface = 'csr' (string)
linux.subsystem = 'usb' (string)
info.product =
I've run "hal-device `hal-find-by-capability --capability battery`"
again, this time with my wireless mouse disconnected. Output attached.
Rick
** Attachment added: "battery.txt"
http://launchpadlibrarian.net/13831480/battery.txt
--
Guidance-power-manager stopped working after upgrade to Gut
Here is the output of "hal-device `hal-find-by-capability --capability
battery`" after restarting hal "sudo /etc/init.d/hal restart".
[EMAIL PROTECTED]:/etc/init.d$ hal-device `hal-find-by-capability --capability
battery`
udi = '/org/freedesktop/Hal/devices/acpi_C171'
battery.serial = '16425'
Disregard my previous comment. It was meant for bug 220324.
Rick
--
01_proc_sys_batteries.patch causes a regression making gnome-power-manager not
detect the battery properly
https://bugs.launchpad.net/bugs/194719
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here is the output of "hal-device `hal-find-by-capability --capability
battery`" after restarting hal "sudo /etc/init.d/hal restart".
[EMAIL PROTECTED]:/etc/init.d$ hal-device `hal-find-by-capability --capability
battery`
udi = '/org/freedesktop/Hal/devices/acpi_C171'
battery.serial = '16425' (
At Wenzhuo's suggestion, I installed the Hardy kernel (linux-
image-2.6.24-15-386_2.6.24-15.27_i386.deb) and rebooted with this
kernel. This seems to have fixed the problem with my Via chipset. I am
able to boot the new kernel and my hard drives show up as SCSI devices
(/dev/sdxn) instead of IDE de
I have found that if kill guidance-power-manager, restart hal and then
start guidance-power-manager everything works. So, is this then a hal
error? It seems it may be related to or the same as bug 145611.
Rick Knight
--
Guidance-power-manager stopped working after upgrade to Gutsy
https://bugs.
I've found a work-around. I stumbled accross a bug involvoing Seagate
Hard Drives. One suggestion to fix that problem was to use kernel
parameter "all_generic_ide". I tried this parameter with my default,
unmodified Gutsy kernel (2.6.22-14-generic) but it did not work. Then I
tried it with my rebui
Brian,
You've marked this bug as won't fix. What "criteria for a stable release
update" does it not match? This seems to be a very common problem, so
much so that Via Technologies has released a patch for the Feisty
kernel. Marking this as won't fix will mean that anyone with a mobo that
has Via V
I agree, the old IDE drivers need to be kept around until this bug is
fixed. I have an HP DVD Writer 640v external usb drive that would not
work on Feisty even though it worked flawlessly on Dapper and previous
Kubuntus. I solved the problem by removing the drive from it's portable
housing and inst
I'm getting the same error. I upgraded from Feisty to Gutsy. I had one
problem in the upgrade and had to abort. I completed the upgrade in a
terminal with these commands...
sudo apt-get --configure -a
sudo apt-get update
sudo apt-get dist-upgrade
Th upgraded completed successfully. When I reboote
Public bug reported:
After an upgrade to Gutsy from Feisty I am unable to boot the Gutsy kernel. I
am able to boot the feisty kernel.
When I try to boot the Gutsy kernel, I get a busy box prompt (screen shots
(photos) attached) with a message that my drive is not available. I have 2 ATA
HDDs, 1
** Attachment added: "bug_report.txt"
http://launchpadlibrarian.net/13126258/bug_report.txt
--
Unable to boot Gutsy kernel after upgrade from Feisty
https://bugs.launchpad.net/bugs/212042
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Screen shot mentioned above.
** Attachment added: "dsc02121.jpg"
http://launchpadlibrarian.net/13126279/dsc02121.jpg
--
Unable to boot Gutsy kernel after upgrade from Feisty
https://bugs.launchpad.net/bugs/212042
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Tonight I downloaded the Kubuntu 8.04 Desktop ISO. I burned the ISO and
then booted from it into Live CD mode. All of my drives are listed and
easily accessible. The devices are installed as /dev/hd, not as /dev/sd.
So it looks like whatever is causing this problem has been fixed in
8.04.
--
Unab
I also have this issue. It started after I upgraded to Kubuntu14.04 LTS
from a clean, fresh install of Kubuntu 13.10. The 13.10 splash worked
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Received an auto-update for GRUB last week. Applied it hoping it would
have a fix for this issue. It DID NOT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed
I had the same problem running GTK apps. I tried removing libcanberra
but that didn't solve the problem for me. I read the post here from
Migrus and tried his solution, installing libcanberra-gtk0. It worked.
No more libcanberra errors.
--
You received this bug notification because you are a memb
Having the same problem on .avi and .wmv files. Tried installing from
SMPlayer source. Same problem. Mplayer works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878000
Title:
smplayer GUI hang
33 matches
Mail list logo
