Ubuntu
transmission package

transmission doesn't want to start

Bug #418853 reported by Alex Ivasyuv
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Transmission
Fix Released
Unknown
transmission (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: transmission-common

Same times, when I shut down transmission and start it again, it doesn't want to start.
The follow error message appear in console:

** Message: err: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

OS: Ubuntu 9.10 (up to date)
Kernel: 2.6.31-7-generic-pae i686
transmission: 1.73-1

Revision history for this message
xtknight (xt-knight) wrote :

I can't reproduce this on amd64 karmic.

Revision history for this message
Alex Ivasyuv (industral) wrote :

Yes, it's reproduce some times.

Charles Kerr (charlesk)
Changed in transmission (Ubuntu):
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in transmission:
status: Unknown → Fix Released
Revision history for this message
Charles Kerr (charlesk) wrote :

What's happening here is that there's a running instance of the Transmission GTK+ client somewhere, but it's not responding. The new instance is asking the first one to pop up and show itself to the user. This request is made via dbus, and the error message the OP is seeing is from that low-level failure.

I've added an error popup to help explain the situation, and its resolution, to end users:
http://trac.transmissionbt.com/attachment/ticket/2387/lockfile-err.jpg

However, this only addresses the symptom... not the question of why there's a unresponsive copy of Transmission lying around somewhere.

If this is repeatable, Alex, could you please use gdb to attach to the unresponsive version of Transmission to see what it's doing?
To do this, there are three steps: (1) find the transmission pid, such as through ps or the Gnome System Monitor (2) attach to it with gdb: "% gdb attach $pid" (3) get a backtrace in gdb: "(gdb) thread apply all bt"

If you want more help doing this, I'm happy to help.

Revision history for this message
Alex Ivasyuv (industral) wrote :

It's not reproducible, but if it happen one more time I'll provide backtrace.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package transmission - 1.75-0ubuntu1

---------------
transmission (1.75-0ubuntu1) karmic; urgency=low

  * New upstream version (LP: #429483)
    - Don't wait so long on unresponsive trackers if there are other trackers
      to try
    - Adding corrupt/invalid torrents could crash Transmission
    - Fix 1.74 bug that caused a high CPU load on startup
    - Fix 1.74 bug that stopped multitracker if a single tracker sent an error
      message
    - Fix bug in converting other charsets to UTF-8 (LP: #414129)
    - Handle HTTP redirects more gracefully
    - Faster verification of local data for torrents with small piece size
    - Fix 1.74 build error when compiling without DHT
    - Fix "sort by time remaining"
    - Fix the turtle toggle button on old versions of GTK+
    - Fix startup error if another copy of the Transmission GTK client is
      running (LP: #418853)
    - Fix clang build issue
  * Refreshed patches:
    - 99_autoreconf.patch

 -- Krzysztof Klimonda <email address hidden> Wed, 23 Sep 2009 10:01:22 +0200

Changed in transmission (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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