So sorry to say, James - bug still recurs with your patch.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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
Rich,
If somebody could catch the bug in the debugger then at least the full text can
be found.
It does not necessarily need to come from the g-p-m binary. It could be from
any of the loaded libs or even have been loaded from configuration.
But if this is text then one possible option how it
I've triggered this bug with gdb attached a number of times. Tragically,
I don't have gdb with the back-step patches installed, or this would be
infinitely easier.
Will produce complete text in a moment.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
Sorry boys and girls, it seems I had a bug in my installation
environment (one of my attempts to build from trunk left remnants in
/usr/local that I just found and cleaned out.)
Testing patch again to see whether this does, indeed, not fix it.
--
gnome-power-manager crashed with SIGSEGV in
Patch resolves the bug.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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 mailing
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 confirm the bug on an amd64 box. Hope you get it solved soon (and
wahoo for the investigation above :) )
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
i also get the crash with use sound to notify in event of an error
disabled.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
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 complains about
(0x3a54494d45202a2a) is exactly the same as the pointer it complains
about when I test it..
It is
In a brief glance, I can't find anywhere a TIME string could be coming
from - TIME as a string literal doesn't appear anywhere in the compiled
binary that I can see, nor does a toupper call.
How very novel.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
hi,
power manager crashed when battery about 25%
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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.
--
Shouldn't this bug be considered of high or even critical importance?
I mean, it apparently affects all amd64 laptop users and intrepid is due to be
released next week.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug
This bug should be marked critical, yes.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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.
--
Recompiling libglib with GCC/G++ 4.2 and then recompiling gnome-power-
mangler against that yielded no change.
Nor did compiling vanilla gnome-power-mangler.
Tragic.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug
Hi,
I believe that I have a fix for the bug. I have someone testing the patch,
and if they show that it is good then I will organise an upload.
Thanks,
James
** Changed in: gnome-power-manager (Ubuntu)
Assignee: (unassigned) = James Westby (james-w)
Status: Confirmed = In Progress
Hi I seem to hit this bug too.
When gpm crashes (my battery was discharging), I can relaunch it with
gnome-power-manager --verbose --no-daemon, after having plugged AC in,
and it seems stable (it hasn't recrashed since manual launch). At
relaunch, it shows 11% battery.
just after having launched
This must be my problem too. I'm not sure what charge level it was but
it was relatively low.
Hp tx2000z
used the above command (gnome-power-manager --verbose --no-daemon)
and it gives a 4.0% charge (which I don't think is right but it doesn't crash)
Kory
--
gnome-power-manager crashed with
Well in defiance of my previous belief, My computer really was at 4% because my
laptop turned off a minute after I posted that.
So I guess the only time the power manager crashes is when the battery is
discharging and gets around 15% or so..
Kory
--
gnome-power-manager crashed with SIGSEGV in
I can second this (gpm 2.24.0-0ubuntu3). Valgrind says:
==19505== Invalid read of size 8
==19505== at 0x40CB40: gpm_cell_array_charge_low_cb (gpm-engine.c:799)
==19505== by 0xCE2425C: g_closure_invoke (in
/usr/lib/libgobject-2.0.so.0.1800.1)
==19505== by 0xCE39F5C: (within
Not sure why gstreamer's audio resampling lib is segfaulting, yet, but
disabling use sound to notify in event of an error prevents the gpm
crash by preventing it from trying to play a sound.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
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
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,
Hi,
here on latest Intrepid, GPM crashes at 25% and can't start anymore.
BUT, if I launch it manually from terminal with --verbose --no-daemon, it
starts correctly and stays up (records battery related events, lid close/open,
etc).
--
gnome-power-manager crashed with SIGSEGV in
Me too, regardless of charge level.
Ubu Intrepid 8.10 on HP Pavilion dv6500
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Happens to me as well, around 10%. My battery indicator turns red around
the same time, so I believe this problem is triggered by the battery's
'critical' status.
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/269083
You received this bug
Happens on 25% battery for me (see duplicate bug 269636). This also
prevents g-p-m from starting when battery is = 25% for me.
** Bug watch added: GNOME Bug Tracker #550817
http://bugzilla.gnome.org/show_bug.cgi?id=550817
** Also affects: gnome-power via
** Changed in: gnome-power
Status: Unknown = New
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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
** Visibility changed to: Public
--
gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
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
32 matches
Mail list logo
