transmission crashed with SIGSEGV in gtk_container_forall()

Bug #462472 reported by DimkaPro
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: transmission

but it look like works ok.

ProblemType: Crash
Architecture: i386
Date: Wed Oct 28 11:11:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
Package: transmission-gtk 1.75-0ubuntu2
ProcCmdline: transmission
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7bd19d4: mov (%eax),%edx
 PC (0xb7bd19d4) ok
 source "(%eax)" (0x00000003) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: transmission crashed with SIGSEGV in gtk_container_forall()
Uname: Linux 2.6.31-020631-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
DimkaPro (prostodimka) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gtk_box_forall (container=0x884c9c0, include_internals=1,
IA__gtk_container_forall (container=0x884c9c0,
gtk_container_expose (widget=0x884c9c0, event=0x81fe148)
_gtk_marshal_BOOLEAN__BOXED (closure=0x82159b0,
?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in transmission (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charles Kerr (charlesk) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Charles Kerr (charlesk)
Changed in transmission (Ubuntu):
status: New → Incomplete
Revision history for this message
Charles Kerr (charlesk) wrote :

Without more information, my best guess is that this is a duplicate of #319880. The traces are consistent with a couple of the traces I've seen for that ticket. Any further discussion regarding the bug should occur in the other report.

Feel free to continue to report any other bugs you may find, and thanks again for taking the time to report his bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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