Ubuntu
google-gadgets package

ggl-gtk crashed with SIGSEGV

Bug #332184 reported by Lafa on 2009-02-20

This bug report is a duplicate of: Bug #448436: ggl-gtk crashed with SIGSEGV. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	google-gadgets (Ubuntu)	New	Undecided	Unassigned

Bug Description

I left ggl-gtk running for a day, with several gadgets on the desktop, when I looked at it in the morning, it was crashed.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x7fd5518df034:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ggl-gtk
NonfreeKernelModules: nvidia
Package: google-gadgets-gtk 0.10.5-0.1ubuntu1
ProcCmdline: /usr/bin/ggl-gtk -sa -nd -gp /usr/share/google-gadgets/designer.gg
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: google-gadgets
Stacktrace: #0 0x00007fd5518df034 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: ggl-gtk crashed with SIGSEGV
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Tags:

Revision history for this message

Lafa (luis-alves) wrote on 2009-02-20:

CoreDump.gz Edit (10.4 KiB, application/x-gzip)
Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (50.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (783 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-02-20: Symbolic stack trace

Stacktrace.txt (retraced) Edit (31 bytes, text/plain)

StacktraceTop:?? ()

Revision history for this message

userdce (userdce) wrote on 2009-09-29:

ggl-gtk
Not a regular file: /
Not a regular file: /
Not a regular file: /
main.js:44: uncaught exception: XMLHttpRequestException: 12 Syntax Error
The program 'ggl-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 298 error_code 5 request_code 19 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)