Bug 485013

Summary:	Can't reopen ktorrent window from tray after closing with window controls
Product:	[Applications] ktorrent	Reporter:	Linus Kardell <linus.kardell>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nicolas.fella, perasugu
Priority:	NOR
Version First Reported In:	24.02.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Linus Kardell 2024-04-04 07:47:25 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
After closing the ktorrent window with the title bar window controls, there is no way to open it again without restarting the application.

STEPS TO REPRODUCE
1. Launch Ktorrent
2. Make sure tray icon is enabled in settings
3. (if set to be minimized to tray on start) Click tray icon to bring up the ktorrent window
4. Close the window with the x button in the title bar
5. Click the tray icon again

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Window reopens

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240329
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 Gibyte of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
Manufacturer: ASUS

Comment 1 Nili 2024-04-04 16:53:05 UTC

There is a bug to the system tray. 

See more at https://invent.kde.org/network/ktorrent/-/commit/d6c4520e82fdc2c14ce0677c1c2a80cc6e52e154

The upstream bug should fixed in Qt 6.7 been said.

At least for now until it fixed, "Don't click Close button on the titlebar", use tray/taskbar icon to show/hide torreng GUI.

Comment 2 Nicolas Fella 2024-04-05 13:26:38 UTC


*** This bug has been marked as a duplicate of bug 484598 ***