gnome-web-photo.real crashed with SIGSEGV in js_NextActiveContext()

[Andrey Kolchenko]

Binary package hint: gnome-web-photo

Description: Ubuntu maverick (development branch)
Release: 10.10
gnome-web-photo: 0.8-0ubuntu4
Sometimes this error appears. I have this package does not use.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-web-photo 0.8-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Sep 22 19:12:22 2010
ExecutablePath: /usr/bin/gnome-web-photo.real
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/gnome-web-photo.real --mode=thumbnail --timeout=16 --size=128 file:///home/username/Documents/%D0%A0%D0%95%D0%97%D0%95%D0%A0%D0%92/%D0%9C%D0%BE%D0%B8%20%D1%84%D0%B0%D0%B9%D0%BB%D1%8B/%D0%92%D1%8B%D0%B2%D0%BE%D0%B4%20%D0%BA%D1%80%D1%83%D0%B3%D0%BE%D0%B2%D0%BE%D0%B9%20%D0%B4%D0%B8%D0%B0%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D1%8B.html /tmp/.gnome_desktop_thumbnail.B0ZDJV
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-web-photo
StacktraceTop:
 js_NextActiveContext () from /usr/lib/xulrunner-1.9.1.9/libmozjs.so
 ?? () from /usr/lib/xulrunner-1.9.1.9/libxul.so
 ?? () from /usr/lib/libnspr4.so
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
Title: gnome-web-photo.real crashed with SIGSEGV in js_NextActiveContext()
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 _pt_root (arg=0xb6c3716c) at ptthread.c:228
 start_thread () from /lib/libpthread.so.0
 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #639753, so it 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. Feel free to continue to report any other bugs you may find.