[ktorrent] [Bug 363852] New: Ktorrent no longer starts hidden in tray

[Matt Scheirer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363852

Bug ID: 363852
Summary: Ktorrent no longer starts hidden in tray
Product: ktorrent
Version: 5.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ***@gmail.com
Reporter: ***@gmail.com

GUI::loadState has functionality to start ktorrent minimized when
Settings::showSystemTrayIcon() && hidden_on_exit is true. Since 5.0, this code
still works, but something else (outside GUI) is showing the window, when I
overrided QWidget::setVisible it would always happen twice - first, the
loadState function is called, and then QWidget is set visible even when
loadState sets it false, within 2 log entries every time.

The only other functionality within ktorrent itself that interacts with widget
visibility is the function GUI::showOrHide, which is linked to the signal
show_kt_action, which is NOT what causes the visibility toggle.

So whatever it is, its somewhere up the stack, in either KMainWindow or
QWidget, and it probably has something to do with refactoring in the Qt5 widget
changes, but I'm personally out of ideas at this point and spent way too much
time recompiling ktorrent wondering why in the world this was happening!
Hopefully someone else has an idea.

[Matt Scheirer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363852

Matt Scheirer <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[David Zaslavsky]

https://bugs.kde.org/show_bug.cgi?id=363852

David Zaslavsky <***@ellipsix.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ellipsix.net

--- Comment #1 from David Zaslavsky <***@ellipsix.net> ---
I'm experiencing the same issue, that KTorrent always starts up with a full
window, whereas I'd like it to start minimized in the tray. Unfortunately I'm
not familiar with the code base so I'm unlikely to be of much help fixing the
bug, but I suppose this is some kind of independent confirmation that it does
happen.

[Mirosław Zalewski]

https://bugs.kde.org/show_bug.cgi?id=363852

Mirosław Zalewski <***@poczta.onet.pl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@poczta.onet.pl

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=363852

Lastique <***@mail.ru> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@mail.ru

--- Comment #2 from Lastique <***@mail.ru> ---
Happens to me as well on Kubuntu 17.10, Ktorrent 5.1.0.

[Janek]

https://bugs.kde.org/show_bug.cgi?id=363852

Janek <***@web.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@web.de

--- Comment #3 from Janek <***@web.de> ---
This is still happening! It bugs me that a KTorrent window opens every single
time upon startup. I might stop it from autostarting due to that, which means
I'd stop seeding. I don'T want to do that, but why is such a seemingly simple
issue still not fixed?

[Kevin Zeidler]

https://bugs.kde.org/show_bug.cgi?id=363852

Kevin Zeidler <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #4 from Kevin Zeidler <***@gmail.com> ---
I'm also experiencing this. Kubuntu 18.04, Ktorrent 5.1.0. Oddly, attempts to
activate the window elicit a stale notification warning about attempting to add
a duplicate torrent. When I asked Kubuntu not to notify me of those events, it
started warning me instead that "preferences" is a malformed URL. It also keeps
sending erroneous notifications that a particular large file I'm downloading
(70GB) is finished downloading. Strange stuff. Seems like it's having trouble
transitioning out of error states, like it didn't release a warning it
broadcast earlier to ibus so every interaction it thinks is an error condition.

[Ashark]

https://bugs.kde.org/show_bug.cgi?id=363852

Ashark <***@linuxcomp.ru> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@linuxcomp.ru

--- Comment #5 from Ashark <***@linuxcomp.ru> ---
As a partial workaround, I have done the following:
Right click on the window title -> More Actions -> Special Application
Settings... New window will appear. Go to "Size & Position" tab and enable
checkbox "Minimized", choose "Apply Initially" and enable "yes" radio button.
Then press OK button.

Now KTorrent window will be minimized in task manager every startup. But still
it will not be completely hidden in system tray and you need to close minimized
window by right clicking in task manager. At least this workaround makes your
desktop less cluttered at startup (which is especially annoying when you reboot
often).

[Ashark]

https://bugs.kde.org/show_bug.cgi?id=363852

--- Comment #6 from Ashark <***@linuxcomp.ru> ---
Why there is no such option to start KTorrent in tray? For example, in Kopete
there is checkbox "Start with hidden main window" in Behavior settings. I would
like to see the same checkbox in KTorrent.
I have also found Bug 251864, but they suggested that ktorrent was double
starting and because of that its window appeared (second calling of ktorrent
just showed ktorrent window of already running application instead of launching
second instance of application). It is not a case for me, because I do not have
ktorrent in autostart applications, so it is starting once when session is
restoring after login in kde.

[Ashark]

https://bugs.kde.org/show_bug.cgi?id=363852

--- Comment #7 from Ashark <***@linuxcomp.ru> ---
I have found a better workaround. You can download my script at
https://github.com/Ashark/Ashark-bin/blob/master/ktorrent-window-closer and set
kde to autostart it.
The main idea is to run wmctrl -x -c "ktorrent" command, which closes ktorrent
window.
Now it behaves exactly as expected: no window at startup (at all, not
minimized to task manager), but still running in tray.