transmission crashed with SIGSEGV in tr_fdFileReturn()

Bug #413958 reported by Bratmaxe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: transmission

i do nothing but brosing the web , then the error appears suddendly

ProblemType: Crash
Architecture: amd64
Date: Sat Aug 15 07:30:20 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
NonfreeKernelModules: nvidia
Package: transmission-gtk 1.73-1ubuntu1
ProcCmdline: transmission
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x463fd8 <tr_fdFileReturn+8>: mov 0x10(%rax),%rbx
 PC (0x00463fd8) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_fdFileReturn ()
 ?? ()
 tr_ioWrite ()
 ?? ()
 ?? ()
Title: transmission crashed with SIGSEGV in tr_fdFileReturn()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Bratmaxe (marcel-456) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:tr_fdFileReturn (fd=41) at fdlimit.c:486
readOrWriteBytes (tor=0xe7ad20, ioMode=1,
tr_ioWrite (tor=0xe7ad20,
readBtPiece (msgs=0x7f83b4176320,
canRead (io=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in transmission (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.

The function where Transmission crashed in your trace -- tr_fdFileReturn() -- is no longer in the nightly builds. Would it be possible for you to try a nightly build, or to try 1.74 when it's released, and let me know if the problem persists?

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

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Bratmaxe (marcel-456) wrote :

i have try the 1.74 and it works fine for me

Charles Kerr (charlesk)
Changed in transmission (Ubuntu):
status: Incomplete → Fix Released
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.