I have a number of things listed in KDE's Autostart menu. These all work correctly. One thing that isn't listed is Ktorrent, yet it starts on every session and has to be manually killed. I only ever use qBittorrent now though I've occasionally used Ktorrent in the distant past, so some cruft may have been left lying around. It isn't listed anywhere in /etc/xdg/autostart, nor in any of the usual .profile, .bashrc etc. places. Is there anywhere else I should look?

On Sun, 2021-06-06 at 19:03 +0800, Ed Greshko wrote: > On 06/06/2021 18:18, Patrick O'Callaghan wrote: >> I have a number of things listed in KDE's Autostart menu. These all >> work correctly. >> >> One thing that isn't listed is Ktorrent, yet it starts on every >> session >> and has to be manually killed. I only ever use qBittorrent now >> though >> I've occasionally used Ktorrent in the distant past, so some cruft >> may >> have been left lying around. >> >> It isn't listed anywhere in /etc/xdg/autostart, nor in any of the >> usual >> .profile, .bashrc etc. places. >> >> Is there anywhere else I should look? > Along with the possibility of it being a part of a saved session, the > question I would be > asking myself would be: "If I only used it in the distant past is > there anything stopping me > from using dnf to erase ktorrent?" No doubt that would work, however this behaviour dates from when I did a system reinstall for F34 (I had probably removed ktorrent in the past and simply forgot about it). IOW there's still an autostart configuration file lying around somewhere and I'd like to get rid of it.

On Sunday, June 6, 2021 11:18:33 AM WEST Patrick O'Callaghan wrote: > I have a number of things listed in KDE's Autostart menu. These all > work correctly. > > One thing that isn't listed is Ktorrent, yet it starts on every > session > and has to be manually killed. I only ever use qBittorrent now > though > I've occasionally used Ktorrent in the distant past, so some cruft > may > have been left lying around. > > It isn't listed anywhere in /etc/xdg/autostart, nor in any of the > usual > .profile, .bashrc etc. places. > > Is there anywhere else I should look? > > poc I have just question and not answers. :-) Could it be that it is starting with the desktop session and not in autostart? Is there a file for it in ~/.config/session/?

On 06/06/2021 20:30, Patrick O'Callaghan wrote: > On Sun, 2021-06-06 at 19:39 +0800, Ed Greshko wrote: > > > No doubt that would work, however this behaviour dates from > > > when I > > > did > > > a system reinstall for F34 (I had probably removed ktorrent in > > > the > > > past > > > and simply forgot about it). IOW there's still an autostart > > > configuration file lying around somewhere and I'd like to get > > > rid > > > of > > > it. > > Well, then my first step would be to login as a different user to > > determine if the "issue was system-wide or user-specific. > It isn´t system-wide. > Since you're not using it, does deleting ~/.config/ktorrent*  and the directory ~/.local/share/ktorrent change anything?

When it starts, is the full gui started or do you just find ktorrent in the background?  I ask that since could it be that ktorrent is on the systray and in someway hidden from view?

I would also use https://specifications.freedesktop.org/autostart-spec/autostart-spec-late...  to look for stray entries or should I say entries that have been missed?

On 07/06/2021 05:53, Patrick O'Callaghan wrote: > > When it starts, is the full gui started or do you just find > > ktorrent > > in the background?  I ask that since could > > it be that ktorrent is on the systray and in someway hidden from > > view? > The GUI is visible. I don't know how I could tell if it's in the > systray if I can't see it there. Well, in the preferences there is a check-box for the systray.

Also, if you "Configure Systray" when ktorrent is running you'll see it listed in Entries if it is.

> > > I would also use > > https://specifications.freedesktop.org/autostart-spec/autostart-spec-late... > >   to look > > for stray entries or should I say entries that have been missed? > I'll have to read that attentively. You may also want to check out "man systemd-xdg-autostart-generator"

> > > > I would also use > > > > https://specifications.freedesktop.org/autostart-spec/autostart-spec-late... > > > >     to look > > > > for stray entries or should I say entries that have been > > > > missed? > > > I'll have to read that attentively. > > You may also want to check out "man systemd-xdg-autostart- > > generator" > I'll look at that. > Also, you may want to do another "test".  Going to "System Settings" and "Startup and Shutdown" then in Desktop Session enter ktorrent in "Don't restore these applications".

On 07/06/2021 19:11, Patrick O'Callaghan wrote: > On Mon, 2021-06-07 at 18:17 +0800, Ed Greshko wrote: > > > > > > I would also use > > > > > > https://specifications.freedesktop.org/autostart-spec/autostart-spec-late... > > > > > >      to look > > > > > > for stray entries or should I say entries that have been > > > > > > missed? > > > > > I'll have to read that attentively. > > > > You may also want to check out "man systemd-xdg-autostart- > > > > generator" > > > I'll look at that. > > > > > Also, you may want to do another "test".  Going to "System > > Settings" > > and "Startup and Shutdown" then > > in Desktop Session enter ktorrent in "Don't restore these > > applications". > I did that, logged out and in, and it made no difference. > Then I ran Save Session, logged out and in, and now it seems to > have > worked, touch wood. > > This appears to have been caused by cruft left over from some > session > many years ago, however it's disconcerting that no amount of > searching > could tell me where it was being registered (I had previously run > 'find' on both .local and .config without turning up anything > useful). > > I'd report it as a bug but I doubt it's easily reproducible. > > Thanks (again) for your help Ed. > Welcome.... And one more thing as my brain seems to have turned on.  When the GUI of ktorrent is "closed" from the "x" in the top right corner ktorrent continues to run in the background.  If you "quit" from the menu it won't. Could be that the background process was the cause of some of the issue?