As a sidenote, some more investigation (by my friend) has come to the
conclusion that the faulty pointer doesn't mean :TIME **, it means **
EMIT:...
The full string is ** EMIT: charge-low (only the first 8 bytes are
used as a 64-bit 'pointer').
--
gnome-power-manager crashed with SIGSEGV in
I can confirm that James' patch fixes the problem.
--
gnome-power-manager crashes on low battery
https://bugs.launchpad.net/bugs/269083
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs
I don't think gstreamer is to blame. I don't get that error, and g-p-m
still segfaults for me when I disable use sound...
Also as said before, somewhere, the engine pointer sent to
gpm_cell_array_charge_low_cb (where the segfault occurs). Strange thing
is athat the pointer Mike's valgrind log
Yesterday, I found out using live CD's that the problem only seems to
exists when using amd64 architecture.
Some thorough investigation by me and a friend (with better C knowledge)
has led us to the macro _G_TYPE_CIT, defined at row 1479 in
gobject/gtype.h of the glib headers. The segfault seems
After some more hours of debugging we have pinpointed the problem to a
(most probable) memory corruption, memory seemingly owned by glib...
(Queue enthusiastic wahoo's.)
As to why or where this is happening, we haven't got a clue (yet?).
More detailed explanation:
The GpmEngine pointer (mostly
I get the same behaviour in version 2.24.0-0ubuntu3.
Also, when I run g-p-m in terminal with --no-daemon --verbose, I get the
following, quite suspicious output:
- ** EMIT: charge-low
** (gnome-power-manager:19145): CRITICAL **:
gpm_cell_array_charge_low_cb: assertion `engine != NULL' failed
*** This bug is a duplicate of bug 269083 ***
https://bugs.launchpad.net/bugs/269083
** Visibility changed to: Public
--
gnome-power-manager crashed with SIGSEGV in gpm_cell_array_charge_low_cb()
https://bugs.launchpad.net/bugs/279285
You received this bug notification because you are a
Some GDB backtracing tells me that the crash seems to happen on line 799
in gpm-engine.c (that is AFTER the ubuntu patches are applied). I fail
to fix it with my limited C knowledge, though...
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
Actually, as far as I can tell, the problem exists (and on the same line
of code, too) even without the ubuntu/debian patches. I couldn't get the
thing to run without having the package installed (whined about gconf
schemas), so my investigations may not be correct. If they are is
correct, though,
Jo,
Well make it a week or two. Running the computer with the electrical
cord in place does not count (although it does add data about how the
battery charges). You can check the progress by right clicking g-p-m in
the system tray, selecting power history and then in that box (near
the bottom),
5of0,
My bet is that use time doesn't help, because gnome-power-manager is
coded to work just like this (I've read the code).
Like I've said in a previous comment
(https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/135548/comments/88), gnome-power-manager WILL NOT DO
ANYTHING
As far as I could tell from the code, Anoop P B has the correct solution
(which I can see from the output of my g-p-m).
If the battery profile of the (primary) battery isn't good enough
(accuracy less than 40%), no action will be taken, and no warnings will
be shown. This is true even if
As I said in my last comment, I would submit my patch when I was done
with it, and here it is.
Cited from the changelog of my patched package:
* Added 11_policy_actions_fallback.patch which makes policy actions
fall back to per-percent policy if the battery profile is not good
enough
13 matches
Mail list logo
