gnome-session crashed with SIGSEGV

[Brian J. Murrell]

Binary package hint: gnome-session

This is on Hardy, including proposed updates.

When I log in I get the all-too-familiar "your session lasted less than 10 seoconds" schpeel which is of course a result of gnome-session crashing.

ProblemType: Crash
Architecture: i386
Date: Thu Jul 3 17:14:06 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-session
NonfreeKernelModules: nvidia
Package: gnome-session 2.22.1.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/gnome-session
ProcCwd: /home/brian
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/brian/bin:/home/brian/bin:/sbin:/bin:/usr/sbin/:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/StarOffice-3.1/linux-x86/bin
 LANG=en_CA.UTF-8
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gnome-session crashed with SIGSEGV
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio audio cdrom cdrom dialout dialout dip dip floppy floppy lpadmin mythtv plugdev plugdev scanner scanner video video

[Brian J. Murrell (brian-interlinx)]

This looks similar to #118348, and in fact I used a hint from there to run gnome-splashscreen-manager and disable the gnome splash screen altogether and now gnome-session doesn't segfault on me any more.

[Brian J. Murrell (brian-interlinx)]

Perhaps upstream bug 446997 is also the same.

[Apport retracing service (apport)]

StacktraceTop:update_icon_with_effect (si=0x825b3d8) at splash-widget.c:661
layout_icon (sw=0x80cd808, si=<value optimized out>, area=<value optimized out>)
layout_icon (sw=0x80cd808, si=<value optimized out>, area=<value optimized out>)
splash_widget_add_icon (sw=0x80cd808, executable_name=0x80c8b20 "evince")
splash_update (text=0x80c8b20 "evince") at splash-widget.c:720

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.