starred/qBittorrent

Fork 0

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

Pre-release (mac): Magnet links open app but don’t process link (QTBUG-134316) Fixed via Qt 6.8.3+ #16618

New issue

Closed

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

deekerman commented

2026-02-22 03:16:49 -05:00

Owner

Originally created by @lukemmtt on GitHub (Feb 19, 2025).

qBittorrent & operating system versions

qbittorrent: master branch
macOS: 15.3.0

What is the problem?

On mac, in the alpha build and master branch, clicking on a magnet link does not show a prompt or start the download. It opens the app, but nothing more. I observed this in my testing while preparing #22284.

Steps to reproduce

Install alpha/master
Click on a magnet link, like in safari
qbittorrent opens, but does nothing more.

Validation:

Install Stable build
Click on magnet link in safari
qbittorrent opens and begins downloading the magnet linked content

Originally created by @lukemmtt on GitHub (Feb 19, 2025). ### qBittorrent & operating system versions qbittorrent: master branch macOS: 15.3.0 ### What is the problem? On mac, in the alpha build and master branch, clicking on a magnet link does not show a prompt or start the download. It opens the app, but nothing more. I observed this in my testing while preparing #22284. ### Steps to reproduce - Install alpha/master - Click on a magnet link, like in safari - qbittorrent opens, but does nothing more. Validation: - Install Stable build - Click on magnet link in safari - qbittorrent opens and begins downloading the magnet linked content

deekerman

2026-02-22 03:16:49 -05:00

closed this issue
added the
OS: macOS

Qt bugs
labels

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@ShlomobCohen commented on GitHub (Feb 20, 2025):

This problem started after these two commits were applied to qtbase:-

github.com/qt/qtbase@664c7ffb21
github.com/qt/qtbase@e8e881ba35

Revert the above commits to test:-

git revert --no-commit 664c7ffb212eb898ed03f7b19c883400fa027b6b
git revert --no-commit e8e881ba35fe7009961cbeb4b89efedc5371d5b5

and recompile qt and the links should work as they should.

Not sure whether the above commits are broken or qBittorrent needs to be modified to handle the new scheme.

Hope this helps

@ShlomobCohen commented on GitHub (Feb 20, 2025): This problem started after these two commits were applied to qtbase:- https://github.com/qt/qtbase/commit/664c7ffb212eb898ed03f7b19c883400fa027b6b https://github.com/qt/qtbase/commit/e8e881ba35fe7009961cbeb4b89efedc5371d5b5 Revert the above commits to test:- git revert --no-commit 664c7ffb212eb898ed03f7b19c883400fa027b6b git revert --no-commit e8e881ba35fe7009961cbeb4b89efedc5371d5b5 and recompile qt and the links should work as they should. Not sure whether the above commits are broken or qBittorrent needs to be modified to handle the new scheme. Hope this helps

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@ShlomobCohen commented on GitHub (Feb 20, 2025):

The alpha build of qBittorrent uses qt-6.8.1.
The above mentioned commits are present in qt-6.8.1
https://github.com/qbittorrent/qBittorrent/issues/22303

@ShlomobCohen commented on GitHub (Feb 20, 2025): The alpha build of qBittorrent uses qt-6.8.1. The above mentioned commits are present in qt-6.8.1 https://github.com/qbittorrent/qBittorrent/issues/22303

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@ShlomobCohen commented on GitHub (Feb 20, 2025):

https://github.com/qt/qtbase/commits/6.8.1/src/plugins/platforms/cocoa?after=0db4321f2f13c6870283f3fcc0f1a462fd7cf663+34

@ShlomobCohen commented on GitHub (Feb 20, 2025): https://github.com/qt/qtbase/commits/6.8.1/src/plugins/platforms/cocoa?after=0db4321f2f13c6870283f3fcc0f1a462fd7cf663+34

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 20, 2025):

@lukemmtt @ShlomobCohen macOS is barely supported as previously announced on our main website.

The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers. If you are a macOS developer willing to help, just go to our bug tracker for a list of macOS related issues. Or try to fix bugs that you yourself have discovered and annoy you.

There are deprecations that have yet to be handled!

macOS related tickets

@xavier2k6 commented on GitHub (Feb 20, 2025): @lukemmtt @ShlomobCohen macOS is barely supported as previously announced on our main website. >The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers. If you are a macOS developer willing to help, just go to our bug tracker for a list of macOS related issues. Or try to fix bugs that you yourself have discovered and annoy you. There are deprecations that have yet to be handled! [macOS related tickets](https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22OS%3A%20macOS%22)

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@lukemmtt commented on GitHub (Feb 20, 2025):

@xavier2k6 Thank you for the quick response. I completely understand the challenges with macOS support—in fact, I just finished contributing a macOS-specific fix (#22284, merged yesterday into master) when I discovered this magnet link regression during testing.

I filed this issue to track what appears to be a notable regression in core functionality between stable and master/alpha builds. While I hadn't conducted extensive testing beyond my initial observation, I thought it worth reporting promptly, especially as it wasn't immediately clear if this issue might affect more prominently-supported platforms than macOS.

While @ShlomobCohen's investigation now clarifies that this issue is indeed likely specific to macOS (thanks!), I believe tracking such regressions is valuable for the project regardless of platform. I'm currently tied up with other commitments, but wanted to ensure this was properly documented.

@lukemmtt commented on GitHub (Feb 20, 2025): @xavier2k6 Thank you for the quick response. I completely understand the challenges with macOS support—in fact, I just finished contributing a macOS-specific fix (#22284, merged yesterday into master) when I discovered this magnet link regression during testing. I filed this issue to track what appears to be a notable regression in core functionality between stable and master/alpha builds. While I hadn't conducted extensive testing beyond my initial observation, I thought it worth reporting promptly, especially as it wasn't immediately clear if this issue might affect more prominently-supported platforms than macOS. While @ShlomobCohen's investigation now clarifies that this issue is indeed likely specific to macOS (thanks!), I believe tracking such regressions is valuable for the project regardless of platform. I'm currently tied up with other commitments, but wanted to ensure this was properly documented.

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 20, 2025):

Adding the relevant QTBUG-124340 report from @ShlomobCohen investigations.

@xavier2k6 commented on GitHub (Feb 20, 2025): Adding the relevant [QTBUG-124340](https://bugreports.qt.io/browse/QTBUG-124340) report from @ShlomobCohen investigations.

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Feb 21, 2025):

Our Info.plist has a CFBundleURLTypes entry for the magnet protocol here.
Maybe we're not installing it correctly?

@sledgehammer999 commented on GitHub (Feb 21, 2025): Our Info.plist has a `CFBundleURLTypes` entry for the `magnet` protocol [here](https://github.com/qbittorrent/qBittorrent/blob/master/dist/mac/Info.plist#L36). Maybe we're not installing it correctly?

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@glassez commented on GitHub (Feb 21, 2025):

Our Info.plist has a CFBundleURLTypes entry for the magnet protocol here.

As per Qt commit description:

This requires that the scheme is listed in the plist file
(CFBundleURLTypes and CFBundleURLSchemes).

So maybe the problem is about CFBundleURLSchemes?

@glassez commented on GitHub (Feb 21, 2025): > Our Info.plist has a `CFBundleURLTypes` entry for the `magnet` protocol [here](https://github.com/qbittorrent/qBittorrent/blob/master/dist/mac/Info.plist#L36). As per Qt commit description: >This requires that the scheme is listed in the plist file (CFBundleURLTypes and CFBundleURLSchemes). So maybe the problem is about `CFBundleURLSchemes`?

deekerman commented

2026-02-22 03:17:01 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Feb 22, 2025):

So maybe the problem is about CFBundleURLSchemes?

We define them too: https://github.com/qbittorrent/qBittorrent/blob/master/dist/mac/Info.plist#L41

Unless, we don't follow the Info.plist spec correctly.

@sledgehammer999 commented on GitHub (Feb 22, 2025): >So maybe the problem is about CFBundleURLSchemes? We define them too: https://github.com/qbittorrent/qBittorrent/blob/master/dist/mac/Info.plist#L41 Unless, we don't follow the Info.plist spec correctly.

deekerman commented

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

Author

Owner

@ShlomobCohen commented on GitHub (Feb 22, 2025):

I have recompiled qt reverting github.com/qt/qtbase@664c7ffb21 only.
QBittorent worked with the magnet urls.

Which leads me to believe that whatever is breaking magnet urls lies with this commit:
github.com/qt/qtbase@e8e881ba35

Hope this helps

@ShlomobCohen commented on GitHub (Feb 22, 2025): I have recompiled qt reverting https://github.com/qt/qtbase/commit/664c7ffb212eb898ed03f7b19c883400fa027b6b only. QBittorent worked with the magnet urls. Which leads me to believe that whatever is breaking magnet urls lies with this commit: https://github.com/qt/qtbase/commit/e8e881ba35fe7009961cbeb4b89efedc5371d5b5 Hope this helps

deekerman commented

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

Author

Owner

@sledgehammer999 commented on GitHub (Mar 4, 2025):

I filed QTBUG-134316.

@sledgehammer999 commented on GitHub (Mar 4, 2025): I filed [QTBUG-134316](https://bugreports.qt.io/browse/QTBUG-134316).

deekerman commented

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

Author

Owner

@sledgehammer999 commented on GitHub (Mar 9, 2025):

Apparently fixed upstream and will be available in Qt 6.8.3+
Until then I'll do the macOS releases based on the Qt 6.7 series.

@sledgehammer999 commented on GitHub (Mar 9, 2025): Apparently fixed upstream and will be available in Qt 6.8.3+ Until then I'll do the macOS releases based on the Qt 6.7 series.

deekerman commented

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

Author

Owner

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

Apparently fixed upstream and will be available in Qt 6.8.3+

Due for release Tues 18th March

Qt 6.8.3 will be the last public release from Qt 6.8 LTS

https://wiki.qt.io/Qt_6.8_Release
https://lists.qt-project.org/pipermail/releasing/2025-February/003046.html

Qt 6.9.0 - Scheduled for 25th March (RC is in a few days)

@xavier2k6 commented on GitHub (Mar 9, 2025): >Apparently fixed upstream and will be available in Qt 6.8.3+ Due for release Tues 18th March * Qt 6.8.3 will be the last public release from Qt 6.8 LTS https://wiki.qt.io/Qt_6.8_Release https://lists.qt-project.org/pipermail/releasing/2025-February/003046.html Qt 6.9.0 - Scheduled for 25th March (RC is in a few days)

deekerman commented

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

Author

Owner

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

@sledgehammer999 Qt 6.8.3 was released today, see https://download.qt.io/official_releases/qt/6.8/ & QTBUG-134316 is contained in the Fixes section of Qt 6.8.3 Release Notes

@xavier2k6 commented on GitHub (Mar 26, 2025): @sledgehammer999 Qt 6.8.3 was released today, see https://download.qt.io/official_releases/qt/6.8/ & QTBUG-134316 is contained in the Fixes section of [Qt 6.8.3 Release Notes](https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.8.3/release-note.md)