Qbit 4.4.2 not working on MAC with M1, Monterey 12.3. Crashes, freezes, cannot see attached HD, or local folders

[Jimmy-Smith]

qBittorrent & operating system versions

Qbit 4.4.2 from SourceForge not working on MAC with M1 chip, Monterey 12.3.

What is the problem?

Crashes, freezes, cannot see attached HD, or local folders. Constantly asks for file / folder / attached drive permissions, but granting permissions has no effect, and flag will never go away. Granting permissions through MAC security settings fails also. Quit the app fails. Changing default download location hangs app, a force quit is the only way out.

Steps to reproduce

Get a MAC with M1 chip, Monterey version 12.3. Install 4.4.2 and try to run it. Use attached HD, try to point to folders in the HD. Change default drive, see the beach ball! Try to quit app.

Additional context

No response

Log(s) & preferences file(s)

No response

[glassez]

Get a MAC with M1 chip, Monterey version 12.3.

Sadly, this particular step is not reproducible for the main qBittorrent developers. That's the problem.

[cybercho]

I'm experiencing the same issue the OP reported (Constantly asks for file / folder / attached drive permissions, but granting permissions has no effect, and flag will never go away). Tried uninstalling/reinstalling to no avail. Enabled Qbittorrent full access in "Full Disk Access" and "Files and Folders" sections of the [Security and Privacy] System Preference in Mac OS 12.3 on a Mac mini with an M1 chip.

[fjsdljfdlksdjf]

This software is just complete and total trash on the Mac. Version 4.3.9 just about works, but don't even dream of using 4.4.2 or you are in for a world of heartache with that crap. It looks like they just don't do adequate testing of this software on Mac.

[Jimmy-Smith]

I got 4.4.2 to work on Mac Mini M1 with MacOS 12.3. Note it runs as a native M1 program.

At one point while installing I right clicked on my main (and also external) drive within Finder, and from there allowed Qbit to access the volume and folder.

Seems it has to be done there, whereas after the installation via the Qbit dialog box about it or directly in the Mac security settings, it never has complete access, and intermittently fails.

All other issues evaporated.

Apr 1, 2022, 08:16 by @.***:

This software is just complete and total trash on the Mac. Version 4.3.9 just about works, but don't even dream of using 4.4.2 or you are in for a world of heartache with that crap. It looks like they just don't do adequate testing of this software on Mac.

— Reply to this email directly, > view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/16747#issuecomment-1086026016> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AGAI7X4DAT4NAZGQ23WYBEDVC4HM5ANCNFSM5RXRJW5A> . You are receiving this because you authored the thread.> Message ID: > <qbittorrent/qBittorrent/issues/16747/1086026016> @> github> .> com>

[daBee]

I had the same issues. Reinstalled 4.3.9 and everything works now. Needs much more testing on new boxes (2 iterations now with Mx Apple Silicon).

[glassez]

Needs much more testing on new boxes (2 iterations now with Mx Apple Silicon).

This is the problem. We have neither active Mac developers nor qualified Mac testers, not to mention some kind of testing on M1 based Macs.

[fjsdljfdlksdjf]

Needs much more testing on new boxes (2 iterations now with Mx Apple Silicon).

This is the problem. We have neither active Mac developers nor qualified Mac testers, not to mention some kind of testing on M1 based Macs.

Kind of pathetic. This doesn’t seem like such a great project after all.

[glassez]

This doesn’t seem like such a great project after all.

It is what it is. I don't know what you expected from a completely non-commercial project. Everyone contribute in it what he/she has, can and wants to contribute. Unfortunately, Mac support in qBittorrent is not enough contributed.

[fjsdljfdlksdjf]

@fjsdljfdlksdjf Well I'm not aware of any other "kinda pathetic" free or paid torrenting client that has no annoying issues or has release builds made publicly available as often as this. Even famous paid software and operating systems have long-term issues or new ones introduced after fixing some or after adding some features or performance and security improvements, so it's silly to argue, blame or label anyone in hopes others will do as you wish after calling something as "complete trash".

Yes, it is sad that there's issues and that latest computers with macOS aren't cheap enough for everyone. So it's kinda pathetic that popular software has many users who like to complain and only few who are willing to take time to learn coding or help the free project get better with anything else than just unhelpful criticism.

Just like no one is forcing you to buy new computer with different CPU and OS or to use newest qBittorrent version if older one is working, same way around it's silly to try to force others to spend free time and money to buy new computer or to learn coding to get new build released more often outside of GitHub.

At least some users have shared information that some new macOS related qBittorrent issues are because of the latest Qt6 dependency and where even kind enough to publicly share workarounds to solve these new Qt6 issues until Qt developers fix it on their side, so at least there's something shared for those affected who don't wish to use older versions, which release date is still is not as old as some other torrenting clients.

I don't develop anything and don't use macOS or plan to buy one with that anytime soon, so unfortunately I can't currently help or confirm if previously shared workarounds in this and other open issues related to macOS work or not and you don't have to try them at all if not interested to do so.

The only thing it has to do is work.

[daBee]

This is the problem. We have neither active Mac developers nor qualified Mac testers, not to mention some kind of testing on M1 based Macs.

OK, but a published release is to say it's valid.

At any level, even minimal, which is how I think I'm qualified for, I'm donating my experience. I'm not looking for hate, nor trying to disrupt anything. I'm just reporting my experience. If you would like me to participate, then there's a way of creating that community.

While I understand that recent massive changes in hardware/OS are mammoth, there's nothing in the dev community of such packages that can't publish "we need more on this platform". Packages are abound with the need on this platform. As long as dependencies are minimal (non-invasive to my dev environment so that rollback is possible with a MacOS desktop GUI dragging/deletion), I'd be fully game. Explaining that need, is very much part of the "business" of such a package. Don't over-tech it. We're humans.

My point: Don't 'release' software that might not be tested, because of lack of testing. Publish something on a website somewhere, that lists green light per OS, and perhaps orange that asks for insight. Apple Silicon is indeed new. Expected. Developers not thinking this might not be an issue when continuing on the Intel deployment, are expecting problems. If anything, this major transition is just that. None of this is new to developers. It should be expected.

Denying this change in the MacOS, is to be in denial. The label of 'non-commercial' is a cop-out. The project is destined to fail because of expected iterations of operation systems in the near future? This app is nothing small. Don't publish thinking it won't create threads like this. A version published is volition that it works. Issue reports from people means including investment on their part. That is an anchor when the last version seems to work properly.

[daBee]

The only thing it has to do is work.

It doesn't. Reported multiple barfs amongst many people, all on new hardware obviously with a new/recent according OS.

[ackerthehacker2]

I just got my M1 and willing to help where I can

[barhom]

I'm using the latest version on my M1 pro. It does randomly hang up, crash, ask for permissions multiple times. The biggest issue right now is that I have no idea how to debug it or how to provide further data to any of the developers of this project.

I can download a torrent, if it is only 1 torrent running I can usually finish downloading it but at some point it crashes so I can't really be seeding.

How can I do a full debug and provide any logs that might be necessary?

[daBee]

@barhom Use 4.3.9 as it seems stable for me.

[amalv]

I've got a Macbook Pro M1 with Monterey (12.1) and I use bittorrent 4.5, it runs without any issues for me.

[lucein1774]

Since 4.4.0, I have seen multiple issues with the software on a Macbook pro Intel and Macbook Pro M1. Tested it on a Mackbook Intel running 12.1 and an M1 Macbook pro with 12.6

1. starting with the 4.4.0 version, the app every time I want to access a file in the torrent list or torrent file previously idle is requested. I get a popup, "qBittorrent" would like to access files on a removable volume.

because of this popup, files being shared do not start until I click OK or allow access. and its a constant thing that happens.
a. The app has full disk access to all volumes b. the current user and root users have full read/write permissions to the volume and directory.

the app should not be asking for permission to access each time a file accessed. With full disk access set in the system preferences. My guess is that there is a disconnect to with the app, no reading that it has full disk access set in the prefs.

2. if Qbittorrent needs to close with any torrents still downloading. When you reopen the app, it locks or hangs while it is trying to recheck the files and never recovers.

I did find a work around for this. But it requires removing all the ".fastresume" files from directory:

/Users/%USERNAME%/Library/Application Support/qBittorrent/BT_backup

a. Make sure the app is closed and is not running in Activity monitor or Force Quit Applications dialog (opt + cmmd + esc) b. goto the folder: /Users/%USERNAME%/Library/Application Support/qBittorrent/BT_backup (make sure the replace the USERNAME with your user directory c. Delete or move all the .fastresume files out of the directory. d. relaunch the app. e. re-add the torrent files back to the app.

I have also tried re-adding the .fasterume files back to the directory one at a time. launching the app, making sure it is working. but this requires that you close and open the app with adding back each .fastresume file.

The fastest way to get back up and running is to delete or remove the fastresume files and add the torrents back. that way you dont have to open and close the app again and again.

I have found that the torrent files listed in this directory can be used to re-add them back to the app. Then the app will take a bit to recheck the files. My recommendation is to only load 3 -5 torrents at a time, so that it does not get overwhelmed. As my tests have shown that adding more than that at time after a ".fastresume" purge. Can cause the app to lock and go unresponsive. Putting you back into the same situation as before. requiring you to start over and delete the fastresume files again.

then relaunching the app and having to drag and re-add the torrent files back to the app. this has been much better with the 4.5.0 version. As before I could not have more than 10 files in the app at a time before the app would go into 'Not Responding" and I would have to force quit the app.

it still happens with 4.5.0 and again hit me last night and to do this procedure above

If anyone has testing they would like me to perform, I would be happy to test the results and report any work arounds that I find.

Unfortunately I have not found a work around for the popup issue. Any suggestions would be greatly appreciated.

[daBee]

Get a MAC with M1 chip, Monterey version 12.3.

Sadly, this particular step is not reproducible for the main qBittorrent developers. That's the problem.

One year later, and this version was released. The problem is the attitude of developers like you that have no clue that you don't release versions that aren't compatible with the marketplace. Yet another dev that has no clue about business.

What's even more ludicrous is that you down-thumb options like I posted, revealing versions that work for people running certain operating systems. Mommy must be proud of you. When you grow up, you'll enter the real world of business where fractional/segmented software simply is not acceptable. The problem lies with immature little devs like you that live in your own little bubble.

If the software landscape was littered with this behaviour, then tech would not progress. Oh, some other news: ARM is a new platform. So is RISC-V. I'm guessing you want those people (a disruptive movement, labelled by many, including Intel itself) to just run your PC? This is the reality of tech. If you don't like it, don't sad-face those showing you this reality.

[fjsdljfdlksdjf]

Get a MAC with M1 chip, Monterey version 12.3.

Sadly, this particular step is not reproducible for the main qBittorrent developers. That's the problem.

One year later, and this version was released. The problem is the attitude of developers like you that have no clue that you don't release versions that aren't compatible with the marketplace. Yet another dev that has no clue about business.

What's even more ludicrous is that you down-thumb options like I posted, revealing versions that work for people running certain operating systems. Mommy must be proud of you. When you grow up, you'll enter the real world of business where fractional/segmented software simply is not acceptable. The problem lies with immature little devs like you that live in your own little bubble.

If the software landscape was littered with this behaviour, then tech would not progress. Oh, some other news: ARM is a new platform. So is RISC-V. I'm guessing you want those people (a disruptive movement, labelled by many, including Intel itself) to just run your PC? This is the reality of tech. If you don't like it, don't sad-face those showing you this reality.

I definitely second this. I just switched to Transmission on Mac. This entire thing has been a huge pain in the butt.

[glassez]

You can see the following on the main download page:

The macOS version is not well supported, because we don't have active macOS developers/contributors.

What did you expect? Currently macOS build is kept afloat only by inertia in anticipation of new contributors. Well, and if I'm not mistaken, there are still some enthusiasts who manage to use it despite these drawbacks. All your emotional opuses aimed at trying to offend current developers/contributors cannot in any way affect the correction of these shortcomings, so they are useless.

P.S. You can buy an excellent BitTorrent client software from Apple, and enjoy life. ;)

[fjsdljfdlksdjf]

You can see the following on the main download page:

The macOS version is not well supported, because we don't have active macOS developers/contributors.

What did you expect? Currently macOS build is kept afloat only by inertia in anticipation of new contributors. Well, and if I'm not mistaken, there are still some enthusiasts who manage to use it despite these drawbacks. All your emotional opuses aimed at trying to offend current developers/contributors cannot in any way affect the correction of these shortcomings, so they are useless.

P.S. You can buy an excellent BitTorrent client software from Apple, and enjoy life. ;)

That wasn't even added until recently. It should've been added years ago imo

[ackerthehacker2]

Just run in docker …that’s what I do on my M1 ...

On Feb 9, 2023, at 10:17 PM, Vladimir Golovnev @.***> wrote:

You can see the following on the main download page:

The macOS version is not well supported, because we don't have active macOS developers/contributors.

What did you expect? Currently macOS build is kept afloat only by inertia in anticipation of new contributors. Well, and if I'm not mistaken, there are still some enthusiasts who manage to use it despite these drawbacks. All your emotional opuses aimed at trying to offend current developers/contributors cannot in any way affect the correction of these shortcomings, so they are useless.

P.S. You can buy an excellent BitTorrent client software from Apple, and enjoy life. ;)

— Reply to this email directly, view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/16747#issuecomment-1425153348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJHJFL3YBIVTRFFCO6XXZMDWWW6NNANCNFSM5RXRJW5A. You are receiving this because you commented.

[daBee]

What did you expect?

To not get into downloading software that didn't work. If it isn't working, then don't release it. That's not anticipation. Releasing software that doesn't work, is not only useless, it erodes your market. Perhaps get some remedial business education and you'll see why. Your smug attitude isn't useful anywhere and is unfortunately witnessed amongst developers that are young, inexperienced, and simply a detriment to any software.

[glassez]

Just to clarify for those who do not understand my personal position and who allow themselves to express inadequate judgments.

Personally, macOS related problems are parallel to me. It is in the mathematical sense that they are parallel, simply because I do not have the opportunity to develop on this platform. Moreover, the project has not had any active macOS developer for quite a long time, so there is no one to maintain compatibility with all sorts of innovations added to macOS. All I (personally) could do lately was try to make it clear to users that this project really has problems with macOS support. I also tried to exert possible influence on the project maintainer (who seems to be somewhat frivolous about this) in order to publicly admit this problem and stop making official releases for macOS. The only thing we have achieved so far is the publication of the above-mentioned statement on the download page.