| Summary: | ktorrent fails to launch after update | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Shaw <shawvrana> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | strace ktorrent | ||
|
Description
Shaw
2007-04-05 18:24:19 UTC
Created attachment 115522 [details]
strace ktorrent
I moved ~/.kde/share/apps/ktorrent directory to a backup location and ktorrent was able to start, so this looks like it may be a ktorrent backward compatibility issue. After it started up, I quit, and moved the tor#/ directories from their backup location to the newly created ktorrent/ directory. Ktorrent was unable to launch afterwards. (In reply to comment #2) Closing this bug and taking up the issue with ktorrent developers. Bug is here: http://bugs.kde.org/show_bug.cgi?id=143896 Wouldn't call that invalid. Developers not taking care on configuration data of previous versions is unfortunately a not to uncommon problem. As you'v taken it upstream... According to the Joris Guisson on the kde bugzilla, this issue has been fixed in ktorrent 2.1.3. Perhaps it would be appropriate to mask the 2.1.2 version to avoid some headaches? The ktorrent dev team has worked out a solution: http://ktorrent.org/forum/viewtopic.php?t=1264&postdays=0&postorder=asc&start=30&sid=5884866364c670041aed35d8d4560edf Now we need to wait to get it someone in the portage tree |
