lorenz crashed with SIGSEGV

[jerodian]

Binary package hint: rss-glx

While selecting a screensaver to use, I attempted to preview Lorenz Attractor and Lorenz promptly crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Oct 11 00:58:57 2009
Disassembly: 0xf9f898: Cannot access memory at address 0xf9f898
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xscreensaver/lorenz
Package: rss-glx 0.9.0-2ubuntu3
ProcCmdline: lorenz -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
Signal: 11
SourcePackage: rss-glx
Stacktrace:
 #0 0x00f9f898 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfbeddfc
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 2184):
 #0 0x00f9f898 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfbeddfc
Title: lorenz crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors:
 (gnome-settings-daemon:1915): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1915): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2003): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2016): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2130): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
SegvAnalysis:
 Segfault happened at: 0xf9f898: Cannot access memory at address 0xf9f898
 PC (0x00f9f898) ok
 SP (0xbfbedda0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file 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!.