Transmission interferes with opening folders

[will]

Binary package hint: transmission

Lenovo R500 Ubuntu 10.10 64bit, every time I try to open any folder in the "Places" menu (be it Downloads, Pictures, Documents) on my tool bar I get the message "Couldn't add corrupt torrent" and then immediately the Transmission opens on its' own. If the transmission is open while I am trying to open a folder I get the message "Transmission cannot be started"-"Transmission is already running" I have to uninstall Transmission every time I want to navigate my home folder

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: transmission-gtk 2.04-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
Architecture: amd64
Date: Sat Feb 12 10:43:31 2011
ExecutablePath: /usr/bin/transmission
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: transmission
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1602): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (totem:2040): Gtk-WARNING **: Refusing to add non-unique action 'device1' to action group 'devices-action-group'
 (rhythmbox:1860): Rhythmbox-CRITICAL **: playing_stream_cb: assertion `entry != NULL' failed

[Charles Kerr (charlesk)]

Hi Will,

Thanks for taking the time to report this bug and helping to make Ubuntu better. This sounds like it might be some kind of configuration issue with your system, rather than a bug with the Transmission application. If you log in under a different account, does the problem persist?

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #667071, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

You can find the steps to solve this issue in the description of byug #667071.