starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

macOS: Can't open a file directly by double clicking in the content tab (due to download folder name containing a space i.e. 'Misc Files') #16679

New issue

Open

opened 2026-02-22 03:20:03 -05:00 by deekerman · 16 comments

deekerman commented

2026-02-22 03:20:03 -05:00

Owner

Originally created by @casualbugs on GitHub (Mar 7, 2025).

qBittorrent & operating system versions

qBittorrent: 5.04 qt6 lt20
Operating system: macOS 15.3.1/M1

What is the problem?

Double clicking a file in the content tab used to open the file in the default app. It has stopped working after 5.04

Opening the folder and then double clicking the file works.

I have checked default associations and it happens on all file types i.e. txt, mp4 etc

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

Originally created by @casualbugs on GitHub (Mar 7, 2025). ### qBittorrent & operating system versions qBittorrent: 5.04 qt6 lt20 Operating system: macOS 15.3.1/M1 ### What is the problem? Double clicking a file in the content tab used to open the file in the default app. It has stopped working after 5.04 Opening the folder and then double clicking the file works. I have checked default associations and it happens on all file types i.e. txt, mp4 etc ### Steps to reproduce _No response_ ### Additional context _No response_ ### Log(s) & preferences file(s) NA

deekerman added the

Confirmed bug

OS: macOS

Has workaround

labels

2026-02-22 03:20:03 -05:00

deekerman commented

2026-02-22 03:20:07 -05:00

Author

Owner

@trafium commented on GitHub (Mar 8, 2025):

I can confirm this, and want to add that even right click and selecting "Open" does not work either. It was working previously.

@trafium commented on GitHub (Mar 8, 2025): I can confirm this, and want to add that even right click and selecting "Open" does not work either. It was working previously. ![Image](https://github.com/user-attachments/assets/7a01c31b-24e0-4be2-89a7-3556e2aaa739)

deekerman commented

2026-02-22 03:20:07 -05:00

Author

Owner

@casualbugs commented on GitHub (Mar 17, 2025):

Apparently this happens only when the download folder has a space in it?

@casualbugs commented on GitHub (Mar 17, 2025): Apparently this happens only when the download folder has a space in it?

deekerman commented

2026-02-22 03:20:07 -05:00

Author

Owner

@luzpaz commented on GitHub (Mar 18, 2025):

What's the name of you download folder ?

@luzpaz commented on GitHub (Mar 18, 2025): What's the name of you download folder ?

deekerman commented

2026-02-22 03:20:07 -05:00

Author

Owner

@luzpaz commented on GitHub (Mar 18, 2025):

@trafium please post your full about info so we know the details of what version and OS you reproduced on

@luzpaz commented on GitHub (Mar 18, 2025): @trafium please post your full about info so we know the details of what version and OS you reproduced on

deekerman commented

2026-02-22 03:20:07 -05:00

Author

Owner

@casualbugs commented on GitHub (Mar 22, 2025):

@luzpaz "Misc Files" is the folder name. I use categories to filter downloads.

This is my about info

Qt: 6.7.3
Libtorrent: 2.0.11.0
Boost: 1.86.0
OpenSSL: 3.4.1
zlib: 1.2.12

@casualbugs commented on GitHub (Mar 22, 2025): @luzpaz "Misc Files" is the folder name. I use categories to filter downloads. This is my about info Qt: 6.7.3 Libtorrent: 2.0.11.0 Boost: 1.86.0 OpenSSL: 3.4.1 zlib: 1.2.12

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@casualbugs commented on GitHub (Mar 22, 2025):

Have been experimenting with this. If I change the category (and by association) to a name without a space I can open the files through the content tab.

@casualbugs commented on GitHub (Mar 22, 2025): Have been experimenting with this. If I change the category (and by association) to a name without a space I can open the files through the content tab.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 23, 2025):

@luzpaz How did you reproduce/confirm this?

@xavier2k6 commented on GitHub (Mar 23, 2025): @luzpaz How did you reproduce/confirm this?

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 23, 2025):

How did you reproduce/confirm this?

Ok, I think I've got it.....but will need to re-confirm steps (Not specific to macOS)

@casualbugs @trafium Did either of you use the rename option within qBittorrent and/or rename files within windows explorer/macOS equivalent?

@xavier2k6 commented on GitHub (Mar 23, 2025): >How did you reproduce/confirm this? Ok, I think I've got it.....but will need to re-confirm steps (Not specific to macOS) @casualbugs @trafium Did either of you use the `rename` option within qBittorrent and/or rename files within windows explorer/macOS equivalent?

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@casualbugs commented on GitHub (Mar 23, 2025):

I didn't use the rename option. Just downloading direct to a category "Misc Files" which by default creates a "Misc Files" folder under my parent qBittorrent folder.

@casualbugs commented on GitHub (Mar 23, 2025): I didn't use the rename option. Just downloading direct to a category "Misc Files" which by default creates a "Misc Files" folder under my parent qBittorrent folder.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@glassez commented on GitHub (Mar 23, 2025):

How did you reproduce/confirm this?

Ok, I think I've got it.....but will need to re-confirm steps (Not specific to macOS)

@casualbugs @trafium Did either of you use the rename option within qBittorrent and/or rename files within windows explorer/macOS equivalent?

I'm confused. Is this not a macOS specific Issue?

@glassez commented on GitHub (Mar 23, 2025): > > How did you reproduce/confirm this? > > Ok, I think I've got it.....but will need to re-confirm steps (Not specific to macOS) > > [@casualbugs](https://github.com/casualbugs) [@trafium](https://github.com/trafium) Did either of you use the `rename` option within qBittorrent and/or rename files within windows explorer/macOS equivalent? I'm confused. Is this not a macOS specific Issue?

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 24, 2025):

I'm confused. Is this not a macOS specific Issue?

Not 100% sure.......I was able to reproduce a similar situation on windows where I used rename option in qBittorrent & removed any iteration of (dot) from the torrent name/file & replaced it with a space, did the same via windows explorer (for corresponding files in save location) double-click to open/play file wouldn't work.

I'm not sure for certain if it is a bug or that behavior is expected because of pebkac.

@xavier2k6 commented on GitHub (Mar 24, 2025): >I'm confused. Is this not a macOS specific Issue? Not 100% sure.......I was able to reproduce a similar situation on windows where I used `rename` option in qBittorrent & removed any iteration of (dot) from the torrent name/file & replaced it with a space, did the same via windows explorer (for corresponding files in save location) double-click to open/play file wouldn't work. I'm not sure for certain if it is a bug or that behavior is expected because of pebkac.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@casualbugs commented on GitHub (Apr 15, 2025):

Weirdly enough when a sub folder has a space you can open the file by double clicking

so "\Misc Files\file.ext" doesn't work but "\Misc Files\Sub Folder\file.ext" works.

@casualbugs commented on GitHub (Apr 15, 2025): Weirdly enough when a sub folder has a space you can open the file by double clicking so "\Misc Files\file.ext" doesn't work but "\Misc Files\Sub Folder\file.ext" works.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@KusanagiMajor commented on GitHub (Apr 18, 2025):

Confirming same issue on MacOS Sequoia 15.4.1 (24E263)
Bug still exists in version 5.0.5 (lt20), had to downgrade back to 5.0.3 where it works fine.

@KusanagiMajor commented on GitHub (Apr 18, 2025): Confirming same issue on MacOS Sequoia 15.4.1 (24E263) Bug still exists in version 5.0.5 (lt20), had to downgrade back to 5.0.3 where it works fine.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@eatstorming commented on GitHub (Jul 21, 2025):

Chiming in to add that I have this issue whenever the file name has brackets ([]) in it. It happens both if the original file name contains brackets, or if I rename a file and add brackets to it. If I remove the brackets from the name, it opens the file just fine.

macOS Sequoia 15.5 (24F74), qB 5.0.5.

@eatstorming commented on GitHub (Jul 21, 2025): Chiming in to add that I have this issue whenever the file name has brackets ([]) in it. It happens both if the original file name contains brackets, or if I rename a file and add brackets to it. If I remove the brackets from the name, it opens the file just fine. macOS Sequoia 15.5 (24F74), qB 5.0.5.

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@maximxt commented on GitHub (Jul 24, 2025):

I can confirm macOS Sequoia 15.5 - files with [ or ] in names open fine on 5.0.3 and not open on double-click on 5.0.4.

On macOS Monterey 12.7.6 double-clicking on files with [] works fine on any version 4.6.2-5.0.5.

I can't find anything that can cause this behavior in diffs 5.0.3...5.0.4

@maximxt commented on GitHub (Jul 24, 2025): I can confirm macOS Sequoia 15.5 - files with [ or ] in names open fine on 5.0.3 and not open on double-click on 5.0.4. On macOS Monterey 12.7.6 double-clicking on files with [] works fine on any version 4.6.2-5.0.5. I can't find anything that can cause this behavior in diffs 5.0.3...5.0.4

deekerman commented

2026-02-22 03:20:08 -05:00

Author

Owner

@liev000123 commented on GitHub (Feb 12, 2026):

Can confirm the issue is still here on 5.05.
5.03. appears to work.
I'm on Intel Mac, Sequoia 15.7.3 (and a recent reinstall, so the machine is clean).

@liev000123 commented on GitHub (Feb 12, 2026): Can confirm the issue is still here on 5.05. 5.03. appears to work. I'm on Intel Mac, Sequoia 15.7.3 (and a recent reinstall, so the machine is clean).