Bug 359163 – >=net-p2p/transmission-2.22: freezes up after upgrade (help needed, please see comment #12)

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Misha 2011-03-16 14:54:27 UTC]

Just updated to 2.22 from 2.21. It does start but after one seconded freezes up. Using gtk version:
Installed versions:  2.22(10:40:52 PM 03/12/2011)(gtk libnotify -gnome -kde -libcanberra -qt4)

after cleaning ~/.config/transmission it starts well.
So i played with files and got them back in config dir one by one. And found out it starts well without old lock file.

(the original bug is posted to transmission bugzilla as well and as it would be modareted i would add url)


Reproducible: Always

Steps to Reproduce:
1.launching from start menu or transmission-gtk from terminal
Actual Results:  
after gui appears it freezes up and i need to kill the process.


more people are needed to confirm, and if lock file is unimportant, than to delete it in ebuild script????

[Comment 1 Misha 2011-03-16 17:10:38 UTC]

As well it doesn't connect to tracker with emerged curl with USE flag ipv6, i think there is bug on T bugzilla, should be added as separate bug?

[Comment 2 Peter Volkov (RETIRED) 2011-03-17 05:08:25 UTC]

Misha, could you post upstream bug tracker URL here, please?

[Comment 3 Misha 2011-03-17 08:23:21 UTC]

url added to the bug to the T tracker 
seems like ipv6 was fixed in 2.22 (due bug tracker of T).

[Comment 4 Peter Volkov (RETIRED) 2011-03-22 14:43:46 UTC]

Hm, I've created lock file with `touch ~/.config/transmission/lock` started gtk gui and it works with no freezes. So I'm unable to reproduce this bug... Are you able? Could you strace transmission-gtk process?

[Comment 5 Misha 2011-03-23 07:09:00 UTC]

can't re create bug as well, but the problem was in config folder of transmission for sure, i was on 2.21 and same happened when i moved to 2.21-r1(this ebuild is not in portage anymore i think), so i moved back and waited till 2.22. but when it came out and error was there again i played with config folder and somehower managed to start it without freezing.


maybe u should try to backup config folder and move it somewhere re-emerge old transmission (2.21) and run it from fresh start(no configs), play with settings and add new torrent. and than to update to 2.22

[Comment 6 Lucas Treffenstädt 2011-03-28 08:27:29 UTC]

I can confirm this bug with USE="gtk libnotify qt4 -gnome -kde -libcanberra" using transmission-gtk. transmission-qt, however, works just fine.

From my testing, the problem seems to be unfinished torrents, because starting transmission-gtk clean (rm ~/.config/transmission/torrents/* ~/.config/transmission/resume/*), things work pretty well (I can download a whole torrent).

Also, .torrents with whitespaces in their names seem to trigger a freeze (using transmission-gtk).

[Comment 7 Peter Volkov (RETIRED) 2011-03-28 09:16:31 UTC]

lucas, thank you. Could you post your findings at upstream bug tracker? Do you have testcase to reproduce this issue (torrent file + steps to do)?

[Comment 8 Igor 2011-04-05 17:46:37 UTC]

Confirm for 2.13

2.04 worked good.

[Comment 9 Igor 2011-04-05 17:48:26 UTC]

(In reply to comment #4)
> Hm, I've created lock file with `touch ~/.config/transmission/lock` started gtk
> gui and it works with no freezes. So I'm unable to reproduce this bug... Are
> you able? Could you strace transmission-gtk process?

Did not help for me.

[Comment 10 Igor 2011-04-05 17:52:41 UTC]

(In reply to comment #6)


rm ~/.config/transmission/resume/*

Do help, but all torrents must be updated with proper location.

[Comment 11 Peter Volkov (RETIRED) 2011-04-06 14:39:48 UTC]

(In reply to comment #9)
> Did not help for me.

Igor, thank you! Next time, please, read this bug carefully. This was not a solution. 

In any case currently we are looking for somebody who experienced/experiences this issue to provide us either with steps or with some files to reproduce this issue.

For all, if you experience this issue, please, do backup ~/.config/transmission/ directory and if it's not very large, please, attach it here (or better at upstream bug report, where I'm subscribed too).

[Comment 12 Peter Volkov (RETIRED) 2011-04-19 16:50:16 UTC]

Guys if you experience this problem, please, provide us with:
1. strace output. Just emerge strace and then run
$ strace -f -o transmission.log transmission-gtk
2. gdb output. emerge gdb and then getting a backtrace when Transmission freezes:

 $ gdb transmission-gtk
 (gdb) handle SIGPIPE nostop noprint
 (gdb) r
 ... run until Transmission freezes, then type ctrl-c to return control to
 the debugger
 (gdb) thread apply all bt full

TIA.

[Comment 13 Peter Volkov (RETIRED) 2011-05-16 06:50:24 UTC]

Closing this bug as NEEDINFO since we really need info ;)

[Comment 14 Vladimir Woelfl 2011-11-01 08:36:49 UTC]

Similar problem here with transmission-gtk. In my particular case, Transmission just recently got upgraded from 2.12 to 2.22 (during 'emerge -avuDN world').

After a bit of tweaking, I've nailed the problem so that I can still use it, but I have to say, it's becoming quite annoying to have to kill it every time and delete certain files.

It hangs every time on exit, and after killing it, all files&dirs except 'resume', 'settings.json' and 'torrents' have to be deleted from the ~/.config/transmission directory, otherwise it just hangs the next time I start it. I'm not sure as to which files exactly have to be deleted, but e.g. deleting just the "lock" file doesn't do the trick.

Please let me know if any solution showed up in the meantime, or should I, as noted in #12, send the strace and gdb info.

Thanks!

[Comment 15 Misha 2011-11-01 17:55:43 UTC]

had those freeses all the time, after upgrade to 2.41 it was freezing less in 1 min, and downgrade back to 2.3* didn't help.

the solution was to delete all blocklists and dht.dat (i think the problem in the last one actually)