ggl-gtk crashed with SIGSEGV

Bug #448436 reported by Cristopher Thomas
104
This bug affects 17 people
Affects Status Importance Assigned to Milestone
google-gadgets (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Crashes immediately after starting up. Here's the output from when I attempted to run in from a terminal window:

$ ggl-gtk
Not a regular file: /
Not a regular file: /
Not a regular file: /
No permission to read file.
No permission to access device status.
No permission to access device status.
No permissions to access D-Bus.
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 621 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.)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 10 23:12:16 2009
Disassembly: 0xb5e1c5d4: Cannot access memory at address 0xb5e1c5d4
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ggl-gtk
Package: google-gadgets-gtk 0.10.5-0.2ubuntu1
ProcCmdline: /usr/bin/ggl-gtk
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0xb5e1c5d4: Cannot access memory at address 0xb5e1c5d4
 PC (0xb5e1c5d4) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: google-gadgets
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: ggl-gtk crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristopher Thomas (crisnoh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

This should have been fixed in 0.10.5-0.2ubuntu2. Can anyone still reproduce this crash in the Karmic final release?

Changed in google-gadgets (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
J.M. Hardin (jmhardin) wrote :

I had that crash yesterday morning with all updates available as of the day before. I'll try running it from the terminal sending the responses to a file since if I launch ggl-gtk from a terminal the crash usually takes out my terminal as well.

Revision history for this message
J.M. Hardin (jmhardin) wrote :

Sure enough, I ran it from a terminal and as soon as I switched back to Epiphany it crashed, although without taking the terminal with it. This is what I got in the terminal:
:~$ ggl-gtk -s > gGadgets_run_2009-11-04_0845
ggl-gtk: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
Aborted
:~$

I'm also attaching the file that was generated.

Changed in google-gadgets (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in google-gadgets (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.