euphoria crashed with SIGSEGV in strtoul()

[Kage]

Binary package hint: rss-glx

Can't give much info honestly, I wasn't at the computer when it happened. I was running an update for 10.04 beta 2 and when I looked, I had this error on the screen. Hope it's helpful on its own, cause I don't know how much help I'll be.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rss-glx 0.9.0-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Apr 17 21:14:19 2010
ExecutablePath: /usr/lib/xscreensaver/euphoria
InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
ProcCmdline: euphoria -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x4f8cc7: mov 0x4(%edx),%eax
 PC (0x004f8cc7) ok
 source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rss-glx
StacktraceTop:
 ?? () from /lib/libc.so.6
 strtoul () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: euphoria crashed with SIGSEGV in strtoul()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1056): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
glxinfo: Error: [Errno 2] No such file or directory

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /lib/libc.so.6
 strtoul () from /lib/libc.so.6
 ?? ()
 ?? ()

[Charlie Kravetz (cjkgeek)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log file '/var/log/dpkg.log/' to this bug report as separate attachments? Thanks in advance.

[Kage (superstar446)]

Requested file "dpkg.log" now attached

[Charlie Kravetz (cjkgeek)]

Thank you for the additional log file. Unfortunatly, examining the attachments, there is not enough information for the developers to determine the cause of this error. If you encounter this again, please file a new bug report. Please continue to file reports on those bugs you do encounter.