[Bug 110957] Re: g-p-m does not recognize power status after feisty upgrade
further indagating, manually restarting dbus daemon with: sudo /etc/init.d/dbus restart and then restarting gnome-power-manager enabled it to work properly. Since HAL (Hardware Abstraction Layer) is kickstarted subsequently to dbus I've dumped to file hal-device before and after having it restarted via dbus invocation. If you diff these two files attached (device1 is before restarting HAL+DBus, device2 is after having HAL+DBus restarted) it's clearly here that battery status is not recognized. I also attached an HAL error dump. ** Attachment added: "HAL dump febore restarting the service (buggy)" http://librarian.launchpad.net/7681280/lista_device1 -- g-p-m does not recognize power status after feisty upgrade https://bugs.launchpad.net/bugs/110957 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 110957] Re: g-p-m does not recognize power status after feisty upgrade
** Attachment added: "HAL error report" http://librarian.launchpad.net/7681284/1 -- g-p-m does not recognize power status after feisty upgrade https://bugs.launchpad.net/bugs/110957 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 110957] Re: g-p-m does not recognize power status after feisty upgrade
** Attachment added: "HAL dump after restarting the service (good)" http://librarian.launchpad.net/7681281/lista_device2 -- g-p-m does not recognize power status after feisty upgrade https://bugs.launchpad.net/bugs/110957 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 110957] g-p-m don't recognize power status after feisty upgrade
Public bug reported: I've got this problem after upgrading from Edgy 6.10 to Feisty 7.04 on my Dell Inspiron 6400/e1505 laptop: gnome-power-manager icon stays grayed everytime displaying the AC plug even when on battery. It does not recognize anymore when my laptop is powered on AC or when running on battey, since the power level is not diaplayed and the icon stays grayed all the time. In addition when I colse the laptop lid, the screen light remains stays turned ON, preventing me from doing this action If I check ACPI module status it seems correctly running and on a typical session on battery power it correctly reports: [CODE] [EMAIL PROTECTED]:~$ acpi -V Battery 1: discharging, 59%, 02:01:45 remaining Thermal 1: ok, 38.0 degrees C AC Adapter 1: off-line [/CODE] Instead, manually launching gnome-power manager right after the aforementioned command in the same power conditions, the icon is grayed and it does not recognise that laptop is powered on battery, instead it behaves like laptop is powered with AC cable and it reports: [CODE] [EMAIL PROTECTED]:~$ gnome-power-manager --verbose --no-daemon [gpm_debug_init] gpm-debug.c:217 (10:09:57): Verbose debugging enabled [main] gpm-main.c:205 (10:09:57):GNOME Power Manager 2.18.2 [gpm_proxy_connect] gpm-proxy.c:101 (10:09:57): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_proxy_connect] gpm-proxy.c:101 (10:09:57): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_ac_adapter_init] gpm-ac-adapter.c:234 (10:09:57): No devices of capability ac_adapter [gpm_control_init] gpm-control.c:863 (10:09:57): Using a supressed policy timeout of 5 seconds [gpm_refcount_add] gpm-refcount.c:101 (10:09:57):refcount now: 1 [gpm_refcount_add] gpm-refcount.c:102 (10:09:57):non zero, so sending REFCOUNT_ADDED [gpm_power_refcount_added] gpm-power.c:138 (10:09:57): Data is now not trusted [gpm_hash_new_kind_cache] gpm-power.c:1727 (10:09:57): creating cache [gpm_hash_new_device_cache] gpm-power.c:1761 (10:09:57): creating cache [gpm_warning_init] gpm-warning.c:260 (10:09:57): Using per-time notification policy [gpm_proxy_connect] gpm-proxy.c:101 (10:09:57): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_cpufreq_set_governor] gpm-cpufreq.c:191 (10:09:57): Doing SetCPUFreqGovernor (ondemand) [gpm_cpufreq_set_consider_nice] gpm-cpufreq.c:506 (10:09:57):Doing SetCPUFreqConsiderNice (0) [gpm_cpufreq_set_performance] gpm-cpufreq.c:126 (10:09:57): Doing SetCPUFreqPerformance (85) [gpm_proxy_connect] gpm-proxy.c:101 (10:09:57): emitting proxy-status TRUE: org.gnome.ScreenSaver [gpm_srv_backlight_sync_policy] gpm-srv-backlight.c:151 (10:09:57): choosing sensible default [gpm_srv_backlight_sync_policy] gpm-srv-backlight.c:153 (10:09:57): laptop, so use GPM_DPMS_METHOD_OFF [gpm_srv_backlight_sync_policy] gpm-srv-backlight.c:185 (10:09:57): SRV_BACKLIGHT parameters 0 0 0, method '4' [gpm_dpms_set_enabled] gpm-dpms.c:435 (10:09:57):setting DPMS enabled: 1 [x11_sync_server_dpms_settings] gpm-dpms.c:130 (10:09:57): Syncing DPMS settings enabled=1 timeouts=0 0 0 [x11_sync_server_dpms_settings] gpm-dpms.c:130 (10:09:57): Syncing DPMS settings enabled=1 timeouts=0 0 0 [gpm_idle_set_check_cpu] gpm-idle.c:306 (10:09:57): Setting the CPU load check to 0 [gpm_manager_init] gpm-manager.c:1564 (10:09:57):creating new inhibit instance [gpm_manager_init] gpm-manager.c:1575 (10:09:57):creating new control instance [gpm_manager_init] gpm-manager.c:1585 (10:09:57):creating new tray icon [gpm_manager_init] gpm-manager.c:1594 (10:09:57):initialising info infrastructure [gpm_hal_enable_power_save] gpm-hal.c:1414 (10:09:57): Doing SetPowerSave (1) [gpm_hal_enable_power_save] gpm-hal.c:1421 (10:09:57): ERROR: No powersave method found *** WARNING *** [gpm_hal_enable_power_save] gpm-hal.c:1426 (10:09:57): SetPowerSave failed! [gpm_idle_set_system_timeout] gpm-idle.c:357 (10:09:57): Setting system idle timeout: 0 [get_stock_id] gpm-tray-icon.c:680 (10:09:57): Trying CRITICAL icon: primary, ups, mouse, keyboard [get_stock_id] gpm-tray-icon.c:704 (10:09:57): Trying CHARGING icon: primary, ups [get_stock_id] gpm-tray-icon.c:721 (10:09:57): Trying PRESENT icon: primary, ups [get_stock_id] gpm-tray-icon.c:736 (10:09:57): Using fallback [gpm_tray_icon_sync] gpm-tray-icon.c:763 (10:09:57): Going to use stock id: gpm-ac-adapter [gpm_tray_icon_set_image_from_stock] gpm-tray-icon.c:155 (10:09:57): emitting icon-changed gpm-ac-adapter [gpm_tray_icon_set_image_from_stock] gpm-tray-icon.c:161 (10:09:57): Setting icon to gpm-ac-adapter [gpm_tray_icon_sync] gpm-tray-icon.c:773 (10:09:57): emitting description-changed gpm-ac-adapter [gpm_refcount_auto_decrement] gpm-refcount.c:75 (10:09:58): zero, so sending REFCOUNT_ZERO [gpm_power_refcount_zero] gpm-power.c:123 (10:09:58):
[Bug 77106] Re: 100% cpu load after 5' of inactivity
towsonu2003: >Could you please try to reproduce the problem again after a system update >(apt-get update && apt-get upgrade)? thanks for your bug report. The system is daily upgraded against ubuntu repositories and the bug is still present. Kevin: > 1) Please see if you can't get a version of 0.2.14 somewhere, overall its > nicer on the CPU/Ram then previous releases. Is there a repository where i can get updated packages or do i need to compile beagled from sources? > 2) A big part of what were seeing here is a behavioral thing. I think you're partially right, I mean I agree that is correct for beagled to work during idle times; what instead is wrong and makes this behaviour a bug is: a) beagled duty is spent all over one out of the two cores avaible on my processor, causing selective overheating (and consequent premature high speed fan activation). Possible fix -> make beagled background indexing multithreaded or debug current code if already multithreaded b) high cpu usage when idle keeps persisting over long periods (i've monitored the pc for about 2 hours and still beagled was indexing), this situation is quite strange since beagled preferences are told to index only my home directory (and recursively all the nested ones) but I don't have so many files to index. This scenario also suggest some bugs during the indexing operations, likely the one reported on bug #64326 where some file types took high time amounts to be indexed. -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
confirmed also on dell inspiron 6400 laptop -- bad hard disk noise on shutdown https://launchpad.net/bugs/67810 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74284] Re: acpi video module prevents brightness adjusting
*** This bug is a duplicate of bug 64308 *** Bug confirmed also on my machine: Dell Inspiron 6400. I've also compiled kernel 2.6.19 and the bug is still present in the video module. -- acpi video module prevents brightness adjusting https://launchpad.net/bugs/74284 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77106] Re: 100% cpu load after 5' of inactivity
Indagating with system monitor i've discovered is the process "beagled" start eating 2nd core power. Removing it (along with the deskbar) from startup program totally fixes the problem. I've also found that likely the same bug was reported before for beagled: https://launchpad.net/distros/ubuntu/+source/beagle/+bug/64326 Anyway the bug report states "Fix Released" but the bug is still exists today (my ubuntu system is daily updated). -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77106] Re: 100% cpu load after 5' of inactivity
** Description changed: - This bug is present on Inspiron 6400 cpu intel core duo T2500, Ubuntu - 6.10, kernel 2.6.17.1-10.34 generic. + This bug is present on laptop Dell Inspiron 6400, cpu intel core duo + T2500, Ubuntu 6.10, kernel 2.6.17.1-10.34 generic. When I leave my dell laptop without moving the mouse nor typing on the keyboard for more than 5 minutes, the cpu usage of the 2nd core goes to 100% and it remains locked at 100% unltil I move the mouse again (or press a key). This bug seems to be appeared after last week kernel update on my Ubuntu 6.10 (current kernel version: linux-image-2.6.17-10-generic 2.6.17.1-10.34): http://ubuntuforums.org/showthread.php?t=318005 Actually I've tested the following, but none of them changed the bug behaviour, still 100% load on 2nd core after 5' of inactivity: - Disabling the fan regulator daemon "dellfand" - Disabling acpi services from "adnimistration->services" menu - Disabling powernowd service from "adnimistration->services" menu Then i've tried this way: - Compiling a custom kernel version 2.6.19 from sources with the same setting of ubuntu's default. ..and the bug changed so that after 5' of inactivity the 1st core (and not anymore the 2nd core) goes 100% of load, this doesn't resolve the problem but maybe confirms it is something kernel-related. Please tell me if there is a useful log i can attach to this bug request. This bug is very critical for me because i'm not allowed to leave the laptop for more than 5' unless i risk cpu overheating. -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77106] Re: 100% cpu load after 5' of inactivity
The attached pictures shows a screenshot of cpu usage monitor gkrellm: On the left when i started the inactivity period. On the right, after 5' of inactivity, 2nd core usage goes drammatically high unless i exit IDLE my moving the mouse. ** Attachment added: "gkrellm monitor" http://librarian.launchpad.net/5547985/bug.png -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77106] Re: 100% cpu load after 5' of inactivity
** Description changed: This bug is present on Inspiron 6400 cpu intel core duo T2500, Ubuntu 6.10, kernel 2.6.17.1-10.34 generic. When I leave my dell laptop without moving the mouse nor typing on the keyboard for more than 5 minutes, the cpu usage of the 2nd core goes to 100% and it remains locked at 100% unltil I move the mouse again (or press a key). This bug seems to be appeared after last week kernel update on my Ubuntu 6.10 (current kernel version: linux-image-2.6.17-10-generic 2.6.17.1-10.34): http://ubuntuforums.org/showthread.php?t=318005 Actually I've tested the following, but none of them changed the bug behaviour, still 100% load on 2nd core after 5' of inactivity: - Disabling the fan regulator daemon "dellfand" - Disabling acpi services from "adnimistration->services" menu - Disabling powernowd service from "adnimistration->services" menu Then i've tried this way: - Compiling a custom kernel version 2.6.19 from sources with the same setting of ubuntu's default. ..and the bug changed so that after 5' of inactivity the 1st core (and - not anymore the 2nd core) goes 100% of load, this does not resolve the - situation. + not anymore the 2nd core) goes 100% of load, this doesn't resolve the + problem but maybe confirms it is something kernel-related. Please tell me if there is a useful log i can attach to this bug request. This bug is very critical for me because i'm not allowed to leave the - laptop for more than 5' unless i risk. cpu overheating. + laptop for more than 5' unless i risk cpu overheating. -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77106] 100% cpu load after 5' of inactivity
Public bug reported: This bug is present on Inspiron 6400 cpu intel core duo T2500, Ubuntu 6.10, kernel 2.6.17.1-10.34 generic. When I leave my dell laptop without moving the mouse nor typing on the keyboard for more than 5 minutes, the cpu usage of the 2nd core goes to 100% and it remains locked at 100% unltil I move the mouse again (or press a key). This bug seems to be appeared after last week kernel update on my Ubuntu 6.10 (current kernel version: linux-image-2.6.17-10-generic 2.6.17.1-10.34): http://ubuntuforums.org/showthread.php?t=318005 Actually I've tested the following, but none of them changed the bug behaviour, still 100% load on 2nd core after 5' of inactivity: - Disabling the fan regulator daemon "dellfand" - Disabling acpi services from "adnimistration->services" menu - Disabling powernowd service from "adnimistration->services" menu Then i've tried this way: - Compiling a custom kernel version 2.6.19 from sources with the same setting of ubuntu's default. ..and the bug changed so that after 5' of inactivity the 1st core (and not anymore the 2nd core) goes 100% of load, this doesn't resolve the problem but maybe confirms it is something kernel-related. Please tell me if there is a useful log i can attach to this bug request. This bug is very critical for me because i'm not allowed to leave the laptop for more than 5' unless i risk cpu overheating. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73286] Cannot change LCD brighness on Inspiron 6400
Public bug reported: Special hotkeys for setting up/down LCD screen brightness on Dell laptop Inspiron 6400 don't work in Ubuntu 6.10 This hotkey combination (Fn+PgUp/PgDown) works properly in Ubuntu 6.06 and works correctly before Xorg server is started (while the bubuntu logo is displayed during the boot process) Bug tested with Inspiron 6400 / E1505 bios revision A09 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Cannot change LCD brighness on Inspiron 6400 https://launchpad.net/bugs/73286 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
