gnome-power-man segfault at 1 ip 00007f136998180e sp 00007fffa5c02700 error 4 in libgtk-x11

Bug #560261 reported by Joel Cogen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

I'm running Ubuntu Lucid Beta2.

gnome-power-manager 2.30.0-0ubuntu1 crashed twice with the following message in dmesg:

gnome-power-man[1291]: segfault at 1 ip 00007f136998180e sp 00007fffa5c02700 error 4 in libgtk-x11-2.0.so.0.2000.0[7f136987b000+415000]

I was running apt at both times, but I don't think it's related. However it's the only common factor I found... I was idle during installation, so it's not a response to a particular user action.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 10 22:06:30 2010
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: CLEVO CO. M860TU
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=d24023f0-50ea-4353-863d-ea6fc491c8e1 ro quiet splash
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f136998180e: movsbl 0x0(%rbp),%eax
 PC (0x7f136998180e) ok
 source "0x0(%rbp)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1295): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1286): GLib-CRITICAL **: g_bookmark_file_load_from_data: assertion `length != 0' failed
 (nautilus:1285): GLib-CRITICAL **: g_bookmark_file_load_from_data: assertion `length != 0' failed
 (gnome-terminal:1746): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:2101): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
dmi.bios.date: 04/08/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.02.16
dmi.board.asset.tag: Tag 12345
dmi.board.name: M860TU
dmi.board.vendor: CLEVO CO.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.02.16:bd04/08/2009:svnCLEVOCO.:pnM860TU:pvrNotApplicable:rvnCLEVOCO.:rnM860TU:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.name: M860TU
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

Revision history for this message
Joel Cogen (joel-cogen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #552276, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.