Improper Exit when using shortcut Ctr+Q #5445

New issue

Closed

opened 2026-02-21 17:51:26 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 17:51:26 -05:00

Owner

Originally created by @usmanahmed on GitHub (Apr 16, 2017).

qBittorrent version: 3.3.12
Operating System: Windows 10 x64

When I quit qBittorrent using shorkey Ctr+Q and reopen it, It first start to check the files instead of start downloading immediately. like it was not properly quit.

But when I exit it from the file menu. It works fine.

Originally created by @usmanahmed on GitHub (Apr 16, 2017). qBittorrent version: 3.3.12 Operating System: Windows 10 x64 When I quit qBittorrent using shorkey Ctr+Q and reopen it, It first start to check the files instead of start downloading immediately. like it was not properly quit. But when I exit it from the file menu. It works fine.

deekerman

2026-02-21 17:51:26 -05:00

closed this issue
added the
autoCloseOldIssue
label

deekerman commented

2026-02-21 17:51:29 -05:00

Author

Owner

@thalieht commented on GitHub (Apr 17, 2017):

But it's the same thing... Maybe win 10 does something with Ctrl + Q because in win 7 it works as expected (for me).

@thalieht commented on GitHub (Apr 17, 2017): But it's the same thing... Maybe win 10 does something with Ctrl + Q because in win 7 it works as expected (for me).

deekerman commented

2026-02-21 17:51:30 -05:00

Author

Owner

@zeule commented on GitHub (Apr 21, 2017):

Ctrl+Q does not work in Plasma when main menu is moved to a title bar button.

@zeule commented on GitHub (Apr 21, 2017): Ctrl+Q does not work in Plasma when main menu is moved to a title bar button.

deekerman commented

2026-02-21 17:51:30 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.

deekerman referenced this issue

2026-02-21 18:48:12 -05:00

The port reported to Tracker will be "0" even the proxy and anonymous mode are both turned off. #7138