gnome-power-manager crashed with SIGSEGV in fclose()

[Aram Bayadyan]

Binary package hint: gnome-power-manager

logged into guest session, and logged back into member session

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-power-manager 2.32.0-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Thu Mar 17 05:24:27 2011
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GnomeSessionSuspendInhibited: Unknown
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0c45:6464 Microdia
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Sony Corporation VPCEB36GM
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=4c7302d1-583b-4c52-ba65-45258e290521 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fe69036c0e4 <fclose+4>: mov (%rdi),%ecx
 PC (0x7fe69036c0e4) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 fclose () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in fclose()
UpgradeStatus: Upgraded to natty on 2011-03-16 (0 days ago)
UserGroups:

dmi.bios.date: 10/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1140Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEB36GM:pvrC6071D4R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEB36GM
dmi.product.version: C6071D4R
dmi.sys.vendor: Sony Corporation

[Erlan Sergaziev (sergeant)]

Just one addition - it affects x86 edition also

[Lars Falk-Petersen (julenissen)]

For me, this occurred when using guest session and the brightness applet.

[christopher dewitt (dandilldo69)]

was on guest session, clicked shut down, was given a log in screen to return to my main, entered the password and was told power management had a problem. The laptop has still not shut down as I am writing this.

[Kevin K Schmidt (kkschmidt)]

I think this is the problem I'm having as well. I let some friends use my computer on a guest session, then I shut down the computer and started it back up again logging in as myself. I had not yet opened any programs, and my startup programs are pretty sparse since I just did a clean install of Natty.

[Vincent Ladeuil (vila)]

Almost same case as christopher above in comment #4.

I did as close as *nothing* in the guest session: click the 'guest' menu, went to the 'power' menu and 'Log out' from there.

laptop still up for report ;)

[Alejandro Meneses (alejandro9225)]

I was in my session, then I switched to guest session (Here, I want to add that in guest session windows borders don't appear), then I switched back to my session again and it just gets stuck in a black screen that says "getting battery status".

[John Carlyle-Clarke (jpcc)]

For me, this occurs when using the guest session and logging out or switching back to the original user session. It doesn't obviously cause any other problems apart from the error report - and the loss of the power status icon.

[Jason Artemis Winstanley (jtwinstanley)]

Still occurs in Natty Narwhal, 64bit.

[Dmitry (musickiller)]

Like in #6, but on shut down the screen was just like when you login... (but without login window)
Also I had no time to wait and just cut the power x)

[John Carlyle-Clarke (jpcc)]

Not sure if this is a duplicate or not, but I also now get this when inserting a DVD just after vlc activates.

[Joschi Poschi (joschiposchi)]

Just logged in to an VirtualBox installation. i386 version.

[Jens Bremmekamp (nem75)]

Same for me, crashed right upon login in virtualbox guest installation. Only difference: x64 version.

[Pedro Villavicencio (pedro)]

Thanks for the report, is this still an issue with latest packages there ? there's no new comments since April.

[John Carlyle-Clarke (jpcc)]

I've not seen this problem for some time. It seems to be fixed for me at least.

[PeterE (peter-sdi-baja)]

Pedro & John: yes, still an issue.
personally, I gave up on 11.04 for a working environment. It feels like I am being a perpetual beta tester for Conical. The continual patches just bring yet another issue... but I have gotten quite handy at formatting partitions and reinstalling on the various machines I play with.
In general 11.04 is way too buggy to depend on in a true working environment, or to recommend for the general public, but a fun play thing. I will keep my ear to the ground and perhaps will try Ubuntu if things improve.
Sorry for the sour grapes.

[John Carlyle-Clarke (jpcc)]

I don't use Ubuntu all the time at the moment, but I just specifically re-tested the two scenarios I mentioned above on a fully patched 11.04 system, and neither causes the crash now.

[Dmitry (musickiller)]

hm.. For me Ubuntu is main OS. Hasn't seen this bug for a while!)

[Pedro Villavicencio (pedro)]

Ok thanks all, please open a new bug with apport if you're still seeing this, thanks.

[Rogan Creswick (creswick)]

@Pedro: I'm still having this problem, and specifically didn't open a new bug when I registered interest because this is *precisely* the problem I'm having, today, with the latest packages.

[Pedro Villavicencio (pedro)]

We need a better backtrace anyways so please *do* open a new bug report with apport and let us to decide if it's *precisely* the same issue or not, thanks.

[Rogan Creswick (creswick)]

Hey, props to the apport team (in addition to the folks who fixed this bug) - I went to reproduce this bug and re-submit the issue, and it stopped me because I actually *hadn't* updated to the latest packages. After doing so, it seems to work.

My apologies, and thanks!