GNOME Bugzilla – Bug 440847
won't load on powerpc / brightness weirdness
Last modified: 2007-05-24 06:40:54 UTC
Debian bug #421886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421886 If I run gnome-power-manager, it gets stuck looping down through lines like: [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621032 of 14) *** WARNING *** Where the large number decrements each time. I am using Debian (unstable + experimental) on an iBook "2.2" (dual-usb, 800MHz). Note that despite not having g-p-m running, I can still suspend & use the built-in keyboard brightness controls. I presume the kernel is controlling them? (I can kill pmud and still use the backlight controls). ===================== mibus@kappa:~$ dpkg -l gnome-power-manager \*dbus\* \*hal\*|grep ^ii ii dbus 1.0.2-4 simple interprocess messaging system ii dbus-1-utils 1.0.2-4 simple interprocess messaging system (utilit ii gnome-power-manager 2.18.2-1 frontend for gnome-powermanager ii hal 0.5.8.1-9 Hardware Abstraction Layer ii hal-device-manager 0.5.8.1-9 Hardware Abstraction Layer user interface ii libdbus-1-2 0.62-4 simple interprocess messaging system ii libdbus-1-3 1.0.2-4 simple interprocess messaging system ii libdbus-1-dev 1.0.2-4 simple interprocess messaging system (develo ii libdbus-glib-1-2 0.73-2 simple interprocess messaging system (GLib-b ii libdbus-glib-1-dev 0.73-2 simple interprocess messaging system (GLib i ii libhal-storage1 0.5.8.1-9 Hardware Abstraction Layer - shared library ii libhal1 0.5.9-2 Hardware Abstraction Layer - shared library ii pulseaudio-module-hal 0.9.5-7 HAL device detection module for PulseAudio s ii python-dbus 0.80.2-2 simple interprocess messaging system (Python ===================== mibus@kappa:~$ uname -a Linux kappa 2.6.18-1-powerpc #1 Sun Sep 24 16:07:14 CEST 2006 ppc GNU/Linux ===================== /proc/acpi doesn't exist kappa:/home/mibus# cat /proc/pmu/battery_0 flags : 00000013 charge : 2627 max_charge : 3599 current : 709 voltage : 12438 time rem. : 4935 ===================== [after running killall gnome-power-manager] mibus@kappa:~$ gnome-power-manager --no-daemon --verbose [gpm_debug_init] gpm-debug.c:217 (09:10:13): Verbose debugging enabled [main] gpm-main.c:205 (09:10:13): GNOME Energieverwaltung 2.18.2 [gpm_proxy_connect] gpm-proxy.c:101 (09:10:13): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_proxy_connect] gpm-proxy.c:101 (09:10:13): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_control_init] gpm-control.c:863 (09:10:14): Using a supressed policy timeout of 5 seconds [gpm_refcount_add] gpm-refcount.c:101 (09:10:14): refcount now: 1 [gpm_refcount_add] gpm-refcount.c:102 (09:10:14): non zero, so sending REFCOUNT_ADDED [gpm_power_refcount_added] gpm-power.c:138 (09:10:14): Data is now not trusted [gpm_hash_new_kind_cache] gpm-power.c:1727 (09:10:14): creating cache [gpm_hash_new_device_cache] gpm-power.c:1761 (09:10:14): creating cache [gpm_warning_init] gpm-warning.c:260 (09:10:14): Using per-time notification policy [gpm_proxy_connect] gpm-proxy.c:101 (09:10:14): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_cpufreq_set_governor] gpm-cpufreq.c:191 (09:10:14): Doing SetCPUFreqGovernor (ondemand) [gpm_cpufreq_set_governor] gpm-cpufreq.c:197 (09:10:14): ERROR: No governor 'ondemand' available *** WARNING *** [gpm_cpufreq_set_governor] gpm-cpufreq.c:202 (09:10:14): SetCPUFreqGovernor failed! [gpm_cpufreq_get_governor] gpm-cpufreq.c:444 (09:10:14): Doing GetCPUFreqGovernor [gpm_cpufreq_set_consider_nice] gpm-cpufreq.c:496 (09:10:14): not valid for current governor! [gpm_cpufreq_set_performance] gpm-cpufreq.c:126 (09:10:14): Doing SetCPUFreqPerformance (85) [gpm_cpufreq_set_performance] gpm-cpufreq.c:136 (09:10:14): not valid for current governor! [gpm_proxy_connect] gpm-proxy.c:101 (09:10:14): emitting proxy-status TRUE: org.gnome.ScreenSaver [gpm_proxy_connect] gpm-proxy.c:101 (09:10:15): emitting proxy-status TRUE: org.freedesktop.Hal [gpm_brightness_lcd_init] gpm-brightness-lcd.c:607 (09:10:15): Laptop panel levels: 15 [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:110 (09:10:15): ERROR: An unknown error occured *** WARNING *** [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:115 (09:10:15): GetBrightness failed! [gpm_brightness_lcd_init] gpm-brightness-lcd.c:614 (09:10:15): current hw brightness: 269621032 [gpm_brightness_lcd_init] gpm-brightness-lcd.c:621 (09:10:15): Starting: (269621032 of 14) [gpm_brightness_lcd_dim_hw] gpm-brightness-lcd.c:260 (09:10:15): new_level_hw=14 [gpm_brightness_lcd_dim_hw_step] gpm-brightness-lcd.c:199 (09:10:15): new_level_hw=14, current_hw=269621032 *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621032 of 14) *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621031 of 14) *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621030 of 14) *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621029 of 14) *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:15): set outside range (269621028 of 14) *** WARNING *** [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:153 (09:10:16): set outside range (269621027 of 14) (etc...) ===================== mibus@kappa:~$ gconftool-2 -R /apps/gnome-power-manager display_icon_policy = always cpufreq_battery_policy = ondemand ignore_inhibit_requests = false show_actions_in_menu = true can_hibernate = true battery_time_very_low = 600 policy_suppression_timeout = 5 ac_sleep_computer = 0 laptop_panel_dim_brightness = 30 show_recalled_battery_warning = true ac_brightness_kbd = 100 ac_brightness = 100 action_button_power = interactive laptop_uses_external_monitor = false enable_sounds = true battery_percentage_action = 2 cpufreq_battery_performance = 25 statistics_show_axis_labels = false notify_ac_adapter = true battery_time_action = 120 action_button_suspend = nothing battery_percentage_very_low = 5 graph_data_max_time = 21600 action_ac_sleep_type = suspend battery_time_critical = 300 statistics_show_events = true notify_low_power = true action_battery_critical = nothing invalid_timeout = 500 cpufreq_consider_nice = false action_button_hibernate = hibernate display_ambient = true use_time_for_policy = true use_lowpower_battery = true battery_brightness = 10 battery_percentage_low = 10 battery_percentage_critical = 3 ac_sleep_display = 0 check_type_cpu = false show_cpufreq_ui = false battery_event_when_closed = false ac_dpms_sleep_method = default cpufreq_ac_performance = 85 notify_hal_error = true display_state_change = true battery_time_low = 1200 networkmanager_sleep = true ac_dim_on_idle = false battery_dim_on_idle = true action_battery_button_lid = blank action_ups_low = nothing battery_sleep_computer = 0 lock_use_screensaver_settings = true battery_sleep_display = 900 battery_brightness_kbd = 50 use_lowpower_ups = true statistics_graph_type = power rate_exponential_average_factor = 80 cpufreq_ac_policy = ondemand lock_on_blank_screen = true statistics_show_legend = true action_sleep_type = suspend notify_fully_charged = true can_suspend = true action_ups_critical = shutdown action_ac_button_lid = blank battery_dpms_sleep_method = default action_battery_sleep_type = hibernate use_lowpower_ac = false lock_on_suspend = true lock_on_hibernate = true ===================== gnome-power-manager has no entries for the last 3+ weeks in /var/log/messages (btw. the bugs.html page says "message" not "messages") ===================== My hald has no "--retain-privilidges" hald log without that (run as root for a few seconds, after killing the original hald) will be attached in a minute. ===================== Thanks!
Created attachment 88708 [details] hald verbose log
You need to update to 2.18.3 *** This bug has been marked as a duplicate of 436570 ***