gnome-session-save crashed with SIGSEGV

[Danilo]

Binary package hint: gnome-session

angelica@angelica-desktop:~$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
angelica@angelica-desktop:~$ apt-cache policy gnome-session
gnome-session:
  Installato: 2.30.0-0ubuntu1
  Candidato: 2.30.0-0ubuntu1
  Tabella versione:
 *** 2.30.0-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-session-bin 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Wed Aug 18 06:26:15 2010
ExecutablePath: /usr/bin/gnome-session-save
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: gnome-session-save --shutdown-dialog
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xf026f1: ret
 PC (0x00f026f1) ok
 destination "(%esp)" (0xbf9e0ee8) ok
 SP (0xbf9e0ee8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gnome-session
Stacktrace:
 #0 0x00f026f1 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so
 No symbol table info available.
 #1 0xbf9e0f38 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so
 ?? ()
Title: gnome-session-save crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1227): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1532): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.