Transmission not opening when external drive is connected

[willryan042]

(or at least that's what I'm noticing)

I have transmission installed on the startup drive, and all my torrent data on an external. I've always used this setup and it's worked fine. I recently wiped out my hard drive to reinstall OS X, and now I'm running into a problem.

I was able to open Transmission initially and add all my torrents (about 1800). It went through the whole "verifying local data" process and all was well. After rebooting my computer and trying to open Transmission, it bounces for a minute or so in the dock, stops, and then nothing. If I right click the icon it says that the application is not responding and I have to force quit it.

If I eject the external where all the data is stored, Transmission starts right up (obviously with paused transfers however because the data can't be found). If I quit, plug the external back in, and then open Transmission, voila, it opens up (with the transfers still paused).

If I resume the transfers, quit, open again, it doesn't open and I have to force quit from the dock icon. So it seems like something's messed up with active transfers. I've tried downgrading Transmission, freshly reinstalling (deleting caches, preferences, etc.), same problem.

Any ideas?

[willryan042]

Weird, it seems to be working now... If it starts happening again I'll be sure to follow your instructions and see if that helps, thanks!

[GoodKat]

I've had this same problem for a while now with transmission failing to open and just bouncing on the dock until I have to force quit. I've never tried booting it by ejecting the externals where I seed from first, instead just doing what x190 suggested and using appzapper to delete everything, then replacing the key library files. A fresh reinstall usually fixes the problem.

This same issue came up again yesterday when I upgraded through transmission, but reinstalling fixed the problem. This is just really annoying, especially because it's persistent, and the fix takes a few minutes. I also have around 1300 torrents seeding and really really don't want to be put through the ordeal of reseeding everything if something goes wrong.

Has a ticket been made/is this a documented glitch?