Bug 336691 - ktorrent - when closed doesnt get erased from memory / if reboot then starts automatically --- even if i dont want it to
Summary: ktorrent - when closed doesnt get erased from memory / if reboot then starts ...
Status: RESOLVED WORKSFORME
Alias: None
Product: ktorrent
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.3.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-25 09:05 UTC by Simon Andric
Modified: 2023-02-03 05:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Andric 2014-06-25 09:05:57 UTC
Hello!
several issues (which i think are maybe connected):

- when i close ktorrent - wither by clicking file+exit or by clicking on X button, or by right clicking in the system tray and selecting exit, ktorrents GUI closes, the download/uploads stops also, but if i look at system activity ktorrent is still present in the memory... and even if i leave it like this ovenight it wont get erased from memory. that also prevents from starting it again - unless i kill it + forcibly kill it (just killing doesnt cut it).
if i reboot the system with ktorrent still in memory after reboot ktorrent will start (in the memory) BUT sometimes wont show GUI or wont start DL/UL, or even wotn display the icon in system tray..so.. again i have to kill/forcibly killl...wait a little and the nstart it again.

right now in the queue i have ~190 files and all of them are on the external hard drive connected to the computer via USB 2.0/3.0

thank you!

Symon :)


Reproducible: Always
Comment 1 Simon Andric 2014-06-25 09:07:23 UTC
ps .wanted to add that after reboot when it starts automatically, because of above mentioned problem with closing - it is not something i want, it means in settings this feature is turned OFF...


thank you
Simon :)
Comment 2 Andrew Crouthamel 2018-11-12 02:50:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:24:02 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-04 07:05:30 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-19 05:14:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-02-03 05:03:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!