[Bug 258600] [NEW] package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg re
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 be run. ProblemType: Package Architecture: i386 Date: Sat Aug 16 09:48:10 2008 Dependencies: DistroRelease: Ubuntu 8.04 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) NonfreeKernelModules: nvidia Package: update-manager None [modified: /var/lib/dpkg/info/update-manager.list] PackageArchitecture: all SourcePackage: update-manager Title: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Uname: Linux 2.6.22-15-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
** Attachment added: "VarLogDistupgradeAptlog.gz" http://launchpadlibrarian.net/16872197/VarLogDistupgradeAptlog.gz ** Attachment added: "VarLogDistupgradeApttermlog.gz" http://launchpadlibrarian.net/16872201/VarLogDistupgradeApttermlog.gz ** Attachment added: "VarLogDistupgradeMainlog.gz" http://launchpadlibrarian.net/16872202/VarLogDistupgradeMainlog.gz ** Attachment added: "VarLogDistupgradeMainprereqlog.gz" http://launchpadlibrarian.net/16872203/VarLogDistupgradeMainprereqlog.gz ** Attachment added: "VarLogDistupgradeTermlog.gz" http://launchpadlibrarian.net/16872204/VarLogDistupgradeTermlog.gz -- package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
/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-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
/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-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
/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:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
/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-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 258600] Re: package update-manager None [modified: /var/lib/dpkg/info/update-manager.list] failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg retu
/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(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/258600 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 249340] Re: Gutsy->Hardy upgrade hangs in localedef
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
** 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 220324] [NEW] Guidance-power-manager stopped working after upgrade to Gutsy
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-manager guidance-power-manager & [2] 9208 [1] Doneguidance-power-manager [EMAIL PROTECTED]:~$ No battery found. No AC adapter found - assume that we are on batteries. Warning: While setting SystemPowerManagement to True : org.freedesktop.Hal.Device.SystemPowerManagement.NotSupported: No powersave method found No AC adapter found - assume that we are on batteries. No AC adapter found - assume that we are on batteries. Traceback (most recent call last): File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1120, in mainWindow = PowermanagerApp(None, "main window") File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1064, in __init__ self.pmwidget.prepare() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 101, in prepare self._initLid() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 140, in _initLid self.powerHasBeenUnplugged() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 927, in powerHasBeenUnplugged msg = self.checkCpuFreq() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 902, in checkCpuFreq if not policy in self.cb_freq: AttributeError: cb_freq Error in sys.excepthook: Traceback (most recent call last): File "/var/lib/python-support/python2.5/apport_python_hook.py", line 42, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0])) IndexError: list index out of range Original exception was: Traceback (most recent call last): File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1120, in mainWindow = PowermanagerApp(None, "main window") File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1064, in __init__ self.pmwidget.prepare() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 101, in prepare self._initLid() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 140, in _initLid self.powerHasBeenUnplugged() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 927, in powerHasBeenUnplugged msg = self.checkCpuFreq() File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 902, in checkCpuFreq if not policy in self.cb_freq: AttributeError: cb_freq Output of $ dmesg attached Thanks, Rick Knight ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: New -- 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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 installed. I'll have to download the RC first. -- 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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 installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up powersaved (0.14.0-7ubuntu1) ... * Starting power management daemon powersaved [fail] ## # ACPI system but acpid not running. # # Please install acpid package, then restart powersaved! # ## invoke-rc.d: initscript powersaved, action "start" failed. /var/lib/dpkg/info/powersaved.postinst: 11: check_return_code: not found dpkg: error processing powersaved (--configure): subprocess post-installation script returned error exit status 127 Errors were encountered while processing: powersaved E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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. ** Attachment added: "power_manager_window.jpg" http://launchpadlibrarian.net/13730664/power_manager_window.jpg -- 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 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 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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/* /proc/acpi/battery/C170/alarm:present: no /proc/acpi/battery/C170/state:present: no /proc/acpi/battery/C170/info:present: no /proc/acpi/battery/C171/alarm:alarm: unsupported /proc/acpi/battery/C171/state:present: yes /proc/acpi/battery/C171/state:capacity state: ok /proc/acpi/battery/C171/state:charging state: charged /proc/acpi/battery/C171/state:present rate:0 mA /proc/acpi/battery/C171/state:remaining capacity: 3764 mAh /proc/acpi/battery/C171/state:present voltage: 16715 mV /proc/acpi/battery/C171/info:present: yes /proc/acpi/battery/C171/info:design capacity: 3764 mAh /proc/acpi/battery/C171/info:last full capacity: 3764 mAh /proc/acpi/battery/C171/info:battery technology: rechargeable /proc/acpi/battery/C171/info:design voltage: 14400 mV /proc/acpi/battery/C171/info:design capacity warning: 189 mAh /proc/acpi/battery/C171/info:design capacity low: 38 mAh /proc/acpi/battery/C171/info:capacity granularity 1: 100 mAh /proc/acpi/battery/C171/info:capacity granularity 2: 100 mAh /proc/acpi/battery/C171/info:model number:Primary /proc/acpi/battery/C171/info:serial number: 16425 2005/05/26 /proc/acpi/battery/C171/info:battery type:LIon /proc/acpi/battery/C171/info:OEM info:Hewlett-Packard Notice this at the top ... /proc/acpi/battery/C170/alarm:present: no /proc/acpi/battery/C170/state:present: no /proc/acpi/battery/C170/info:present: no /proc/acpi/battery/C170 is for an optional external battery (that I don't have). /proc/acpi/battery/C171 is for the standard internal battery. I believe guidance-power-manage is showing the status for C170 and not for C171. Prior to upgrading from Feisty to Gutsy the power- manager worked correctly and showed status for the internal battery and showed the external battery as not present. Something was changed during the upgrade that now makes guidance-power-manage not show status for the correct battery. Is this a bug or a configuration issue? How can this be adjusted? If it can't, how can I make guidance-power- manage show both C171 and C170. Rick Knight -- 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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 = 'Mouse Receiver' (string)
usb_device.device_revision_bcd = 2320 (0x910) (int)
battery.csr.has_sms = false (bool)
info.category = 'battery' (string)
usb_device.product = 'USB Receiver' (string)
battery.csr.is_dual = false (bool)
usb_device.product_id = 50433 (0xc501) (int)
usb_device.speed = 1.5 (double)
usb_device.vendor = 'Logitech' (string)
usb_device.can_wake_up = true (bool)
usb_device.configuration_value = 1 (0x1) (int)
usb_device.linux.device_number = 3 (0x3) (int)
battery.charge_level.design = 7 (0x7) (int)
battery.charge_level.current = 7 (0x7) (int)
info.linux.driver = 'usb' (string)
battery.is_rechargeable = true (bool)
usb_device.device_class = 0 (0x0) (int)
info.addons = { 'hald-addon-usb-csr' } (string list)
info.parent = '/org/freedesktop/Hal/devices/usb_device_0_0__00_1d_1'
(string)
usb_device.bus_number = 2 (0x2) (int)
battery.csr.has_res = false (bool)
usb_device.device_protocol = 0 (0x0) (int)
usb_device.is_self_powered = false (bool)
info.subsystem = 'usb_device' (string)
info.vendor = 'Logitech' (string)
usb_device.version = 1.1 (double)
usb_device.num_interfaces = 1 (0x1) (int)
usb_device.vendor_id = 1133 (0x46d) (int)
usb_device.speed_bcd = 336 (0x150) (int)
usb_device.version_bcd = 272 (0x110) (int)
battery.present = true (bool)
info.udi = '/org/freedesktop/Hal/devices/usb_device_46d_c501_noserial'
(string)
usb_device.linux.sysfs_path = '/sys/devices/pci:00/:00:1d.1/usb2/2-1'
(string)
usb_device.num_configurations = 1 (0x1) (int)
info.bus = 'usb_device' (string)
battery.type = 'mouse' (string)
linux.device_file = '/dev/2-1' (string)
battery.charge_level.last_full = 7 (0x7) (int)
battery.charge_level.percentage = 100 (0x64) (int)
usb_device.num_ports = 0 (0x0) (int)
usb_device.max_power = 50 (0x32) (int)
linux.hotplug_type = 2 (0x2) (int)
usb_device.device_subclass = 0 (0x0) (int)
linux.sysfs_path = '/sys/devices/pci:00/:00:1d.1/usb2/2-1' (string)
If I'm reading this right, this command is showing the 2 AA batteries in
my cordless mouse!
I am also attaching the output of lshal
Rick
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/13831399/lshal.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 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 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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 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-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 194719] Re: 01_proc_sys_batteries.patch causes a regression making gnome-power-manager not detect the battery properly
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' (string)
info.capabilities = { 'battery' } (string list)
battery.charge_level.warning = 2721 (0xaa1) (int)
info.category = 'battery' (string)
info.product = 'Battery Bay' (string)
battery.technology = 'lithium-ion' (string)
battery.reporting.warning = 189 (0xbd) (int)
battery.rechargeable.is_discharging = false (bool)
battery.model = 'Primary' (string)
battery.charge_level.granularity_1 = 1440 (0x5a0) (int)
battery.charge_level.granularity_2 = 1440 (0x5a0) (int)
linux.acpi_path = '/proc/acpi/battery/C171' (string)
battery.charge_level.design = 54201 (0xd3b9) (int)
battery.charge_level.low = 547 (0x223) (int)
battery.reporting.last_full = 3764 (0xeb4) (int)
battery.reporting.technology = 'LIon' (string)
battery.charge_level.current = 54201 (0xd3b9) (int)
battery.reporting.granularity_1 = 100 (0x64) (int)
battery.is_rechargeable = true (bool)
battery.reporting.current = 3764 (0xeb4) (int)
battery.reporting.granularity_2 = 100 (0x64) (int)
battery.voltage.unit = 'mV' (string)
battery.charge_level.capacity_state = 'ok' (string)
info.parent = '/org/freedesktop/Hal/devices/computer' (string)
battery.rechargeable.is_charging = false (bool)
battery.reporting.rate = 0 (0x0) (int)
battery.charge_level.rate = 0 (0x0) (int)
battery.reporting.design = 3764 (0xeb4) (int)
battery.present = true (bool)
info.udi = '/org/freedesktop/Hal/devices/acpi_C171' (string)
linux.acpi_type = 0 (0x0) (int)
battery.voltage.design = 14400 (0x3840) (int)
battery.reporting.low = 38 (0x26) (int)
battery.type = 'primary' (string)
battery.reporting.unit = 'mAh' (string)
battery.voltage.current = 16713 (0x4149) (int)
battery.charge_level.last_full = 54201 (0xd3b9) (int)
battery.charge_level.percentage = 100 (0x64) (int)
battery.vendor = 'Hewlett-Packard' (string)
linux.hotplug_type = 4 (0x4) (int)
battery.charge_level.unit = 'mWh' (string)
--
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 is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194719] Re: 01_proc_sys_batteries.patch causes a regression making gnome-power-manager not detect the battery properly
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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' (string)
info.capabilities = { 'battery' } (string list)
battery.charge_level.warning = 2721 (0xaa1) (int)
info.category = 'battery' (string)
info.product = 'Battery Bay' (string)
battery.technology = 'lithium-ion' (string)
battery.reporting.warning = 189 (0xbd) (int)
battery.rechargeable.is_discharging = false (bool)
battery.model = 'Primary' (string)
battery.charge_level.granularity_1 = 1440 (0x5a0) (int)
battery.charge_level.granularity_2 = 1440 (0x5a0) (int)
linux.acpi_path = '/proc/acpi/battery/C171' (string)
battery.charge_level.design = 54201 (0xd3b9) (int)
battery.charge_level.low = 547 (0x223) (int)
battery.reporting.last_full = 3764 (0xeb4) (int)
battery.reporting.technology = 'LIon' (string)
battery.charge_level.current = 54201 (0xd3b9) (int)
battery.reporting.granularity_1 = 100 (0x64) (int)
battery.is_rechargeable = true (bool)
battery.reporting.current = 3764 (0xeb4) (int)
battery.reporting.granularity_2 = 100 (0x64) (int)
battery.voltage.unit = 'mV' (string)
battery.charge_level.capacity_state = 'ok' (string)
info.parent = '/org/freedesktop/Hal/devices/computer' (string)
battery.rechargeable.is_charging = false (bool)
battery.reporting.rate = 0 (0x0) (int)
battery.charge_level.rate = 0 (0x0) (int)
battery.reporting.design = 3764 (0xeb4) (int)
battery.present = true (bool)
info.udi = '/org/freedesktop/Hal/devices/acpi_C171' (string)
linux.acpi_type = 0 (0x0) (int)
battery.voltage.design = 14400 (0x3840) (int)
battery.reporting.low = 38 (0x26) (int)
battery.type = 'primary' (string)
battery.reporting.unit = 'mAh' (string)
battery.voltage.current = 16713 (0x4149) (int)
battery.charge_level.last_full = 54201 (0xd3b9) (int)
battery.charge_level.percentage = 100 (0x64) (int)
battery.vendor = 'Hewlett-Packard' (string)
linux.hotplug_type = 4 (0x4) (int)
battery.charge_level.unit = 'mWh' (string)
--
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-guidance in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
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 devices (/dev/hdXN). The pata_via module is loaded as well as libata. The IDE modules are not loaded. It seems that the problem with Gutsy has been fixed in Hardy. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220324] Re: Guidance-power-manager stopped working after upgrade to Gutsy
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.launchpad.net/bugs/220324 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
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 rebuilt Gutsy kernel that had PATA_VIA enabled. This worked. I am able to boot to the Gutsy kernel and have access to all my drives. All drives are installed as SCSI devices. The IDE modules are no longer being loaded, instead modules pata_via, ata_generic and libata are loading. So the steps to get the Via IDE chipset to work with Gutsy are... Build a new Gutsy kernel adding just pata_via module support Install this new kernel Add "all_generic_ide" to menu.lst for the kernel parameter for the new kernel Reboot to the new kernel Rick Knight -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
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 VT82C586A/B, VT82C686A/B, VT823xA/C IDE chipset will not be able to run Gutsy out of the box. Rick Knight -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109211] Re: feisty doesn't work with external CD writers anymore
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 installing it internally, but this solution won't work for most users. Also, I created bug report 212042, https://bugs.launchpad.net/bugs/212042, with a similar problem with my hard drives, Via IDE chipset and Gutsy. The cutting edge is nice, but we still need some compatibility with older devices, at least until the bugs are fixed. Rick Knight -- feisty doesn't work with external CD writers anymore https://bugs.launchpad.net/bugs/109211 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 190588] Re: After upgrade from Feisty to Gutsy, Gutsy boot drops to initramfs
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 rebooted there was a long delay at the splash screen then this... Check root= bootarg cat /proc/cmdline or missing modules,devices: cat /proc/modules ls /dev ALERT! /dev/disk/by-uuid/(boot disk uuid) does not exist. Dropping to a shell. Then I get the Busy Box banner and prompt (initramfs) I have used blkid to verify the uuid is correct. I've edited /boot/grub/menu.lst and /etc/fstab to use drive path (/dev/hdb5 & /dev/sdb5) instead of uuid. I also modified /etc/initramfs-tools/modules and added these lines (from a post at Launchpad)... # added for support of older, standard hdx drives piix ide_generic ide_cd ide_disk # black-list bad driver ata_piix # prevent unnecessary modules from loading (optional) blacklist ata_generic blacklist libata blacklist scsi_mod And then ran... sudo initramfs-tools -u 2.6.22-14-generic to rebuild the init image. I have also removed and re-installed the kernel image (while booted into my Feisty kernel) but that, too did not work. So far nothing has worked. I still boot to a busy box prompt with a message indicating my hard drives can't be found. I am able to boot to my Feisty kernel without any problems. This seems to be an ongoing bug. Is there any hope of a fix? I really DO NOT want to have to reformat my PC to solve this upgrade problem. Rick Knight -- After upgrade from Feisty to Gutsy, Gutsy boot drops to initramfs https://bugs.launchpad.net/bugs/190588 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 212042] [NEW] Unable to boot Gutsy kernel after upgrade from Feisty
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 IDE/ATA CDROM and 1 IDE/ATA DVD. When I run "ls /dev/disk" no drives are listed and the folders /by-id, /by-path, /by-uuid and /by-label do not exist. I have verified the disk UUID using vol_id and blkid. I have verified /boot/grub/menu.lst has the correct drive UUID. I have verified /etc/fstab is also correct. I have removed un-needed devices from /etc/fstab. I have rebuilt /boot/initrd.img-2.6.22-14-generic to specifically load IDE_DISK, IDE_CD, IDE_GENERIC and VIA82CXXX and also to disable libata and the ata drivers. When I upgraded from Dapper to Feisty my system would not boot with the /dev/sd style drive path and I had to change /boot/grub/menu.lst and /etc/fstab to /dev/hd. That hasn't worked with Gutsy as it doesn't create the /dev/hd devices. I think this is due to an incompatibility between my Via VT82C586 chipset and libata. ** Affects: ubuntu Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212042] Re: Unable to boot Gutsy kernel after upgrade from Feisty
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. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: error: malformed file, press any key to continue
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/1311247 Title: error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
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 file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872172] Re: libcanberra-gtk0 should recommend Gtk2 and Gtk3 module to fix: Gtk-Message: Failed to load module "canberra-gtk-module"
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872172 Title: libcanberra-gtk0 should recommend Gtk2 and Gtk3 module to fix: Gtk- Message: Failed to load module "canberra-gtk-module" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/872172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878000] Re: smplayer GUI hangs with 100% CPU usage when trying to play anything
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 hangs with 100% CPU usage when trying to play anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smplayer/+bug/878000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
