Bug 466943 - gnome-power-manager dies when battery is low
gnome-power-manager dies when battery is low
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gnome-power-manager (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-14 13:17 EDT by Jeremy Fitzhardinge
Modified: 2008-10-15 04:06 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-15 03:33:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeremy Fitzhardinge 2008-10-14 13:17:21 EDT
Description of problem:
When the battery gets low, gnome-power-manager dies, and dies each time I try to restart it.  When the battery is charged, it runs again.

Version-Release number of selected component (if applicable):
gnome-power-manager-2.24.0-6.fc10.x86_64


How reproducible:
Often.

Steps to Reproduce:
1. Start gnome-power-manager
2. Run on batteries until they get low
3.
  
Actual results:
gnome-power-manager dies

Expected results:
It should not.

Additional info:
: abulafia:pts/11; gdb /usr/bin/gnome-power-manager 
GNU gdb Fedora (6.8-24.fc10)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) run --no-daemon
Starting program: /usr/bin/gnome-power-manager --no-daemon
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff7fbd7f0 (LWP 26680)]
Detaching after fork from child process 26689.
Detaching after fork from child process 26690.
Detaching after fork from child process 26691.

Program received signal SIGSEGV, Segmentation fault.
0x000000000040bfc0 in gpm_cell_array_charge_critical_cb (cell_array=0x8643f0, 
    percent=<value optimized out>, engine=0x4357ee) at gpm-engine.c:825
825		g_return_if_fail (GPM_IS_ENGINE (engine));
Missing separate debuginfos, use: debuginfo-install avahi.x86_64 bug-buddy.x86_64 e2fsprogs.x86_64 elfutils.x86_64 expat.x86_64 gcc.x86_64 gstreamer-plugins-base.x86_64 gstreamer-plugins-good.x86_64 gtk2-engines.x86_64 keyutils.x86_64 krb5.x86_64 libXau.x86_64 libXcomposite.x86_64 libXcursor.x86_64 libXdamage.x86_64 libXdmcp.x86_64 libXfixes.x86_64 libXi.x86_64 libXinerama.x86_64 libXres.x86_64 libcanberra.x86_64 libcap.x86_64 libogg.x86_64 libpng.x86_64 libselinux.x86_64 libtool.x86_64 libvorbis.x86_64 libxcb.x86_64 openssl.x86_64 pixman.x86_64 samba.x86_64 startup-notification.x86_64 zlib.x86_64
(gdb) bt
#0  0x000000000040bfc0 in gpm_cell_array_charge_critical_cb (
    cell_array=0x8643f0, percent=<value optimized out>, engine=0x4357ee)
    at gpm-engine.c:825
#1  0x0000003bdc20b7bd in IA__g_closure_invoke (closure=<value optimized out>, 
    return_value=<value optimized out>, n_param_values=<value optimized out>, 
    param_values=<value optimized out>, invocation_hint=<value optimized out>)
    at gclosure.c:767
#2  0x0000003bdc2214ad in signal_emit_unlocked_R (node=<value optimized out>, 
    detail=<value optimized out>, instance=<value optimized out>, 
    emission_return=<value optimized out>, 
    instance_and_params=<value optimized out>) at gsignal.c:3244
#3  0x0000003bdc222b58 in IA__g_signal_emit_valist (
    instance=<value optimized out>, signal_id=<value optimized out>, 
    detail=<value optimized out>, var_args=<value optimized out>)
    at gsignal.c:2977
#4  0x0000003bdc223083 in IA__g_signal_emit (instance=<value optimized out>, 
    signal_id=<value optimized out>, detail=<value optimized out>)
    at gsignal.c:3034
#5  0x0000000000411025 in gpm_cell_array_collection_changed (
    cell_array=0x8643f0) at gpm-cell-array.c:786
#6  0x00000000004114a3 in gpm_cell_array_add_device_id (cell_array=0x8643f0, 
    device_id=0xa89090 "/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0") at gpm-cell-array.c:841
---Type <return> to continue, or q <return> to quit---
#7  0x0000000000411613 in gpm_cell_array_coldplug (cell_array=0x8643f0)
    at gpm-cell-array.c:879
#8  0x0000000000411a7f in gpm_cell_array_set_type (cell_array=0x8643f0, 
    kind=GPM_CELL_UNIT_KIND_PRIMARY) at gpm-cell-array.c:902
#9  0x000000000040b198 in gpm_engine_start (engine=0xa3ea20)
    at gpm-engine.c:1027
#10 0x0000000000420cbe in gpm_manager_init (manager=0x864270)
    at gpm-manager.c:1794
#11 0x0000003bdc22c5aa in IA__g_type_create_instance (
    type=<value optimized out>) at gtype.c:1674
#12 0x0000003bdc210b1b in g_object_constructor (type=<value optimized out>, 
    n_construct_properties=<value optimized out>, 
    construct_params=<value optimized out>) at gobject.c:1334
#13 0x0000003bdc211163 in IA__g_object_newv (
    object_type=<value optimized out>, n_parameters=<value optimized out>, 
    parameters=<value optimized out>) at gobject.c:1211
#14 0x0000003bdc211cb7 in IA__g_object_new_valist (
    object_type=<value optimized out>, 
    first_property_name=<value optimized out>, var_args=<value optimized out>)
    at gobject.c:1274
#15 0x0000003bdc211dfc in IA__g_object_new (object_type=<value optimized out>, 
    first_property_name=<value optimized out>) at gobject.c:1056
#16 0x000000000041f8d2 in gpm_manager_new () at gpm-manager.c:1858
---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) q
The program is running.  Exit anyway? (y or n) y
Comment 1 Richard Hughes 2008-10-15 03:33:00 EDT
Upstream: http://bugzilla.gnome.org/show_bug.cgi?id=550817
Comment 2 Jeremy Fitzhardinge 2008-10-15 03:50:42 EDT
What's the procedure for these kinds of bugs?  Shouldn't it remain open until its actually fixed in Fedora?
Comment 3 Richard Hughes 2008-10-15 04:06:32 EDT
I'm going to upload a new snapshot this afternoon when I've fixed the logout interaction.

Note You need to log in before you can comment on or make changes to this bug.