MacOS Big Sur hang: storage.lock #11233

New issue

Closed

opened 2026-02-21 21:16:00 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 21:16:00 -05:00

Owner

Originally created by @arnstein99 on GitHub (Nov 18, 2020).

Please provide the following information

qBittorrent version and Operating System

v4.3.0 MacOS Big Sur

If on linux, libtorrent-rasterbar and Qt version

N/A

What is the problem

qBittorrent hangs on launch. No response to keyboard or mouse events. "Force quit" is required to get rid of it.

What is the expected behavior

qBittorrent becomes responsive to keyboard and mouse inputs.

Steps to reproduce

Launch qBittorrent.

Extra info(if any)

Problem was resolved after I deleted file ~/Library/Application Support/qBittorrent/rss/articles/storage.lock

Originally created by @arnstein99 on GitHub (Nov 18, 2020). **Please provide the following information** ### qBittorrent version and Operating System v4.3.0 MacOS Big Sur ### If on linux, libtorrent-rasterbar and Qt version N/A ### What is the problem qBittorrent hangs on launch. No response to keyboard or mouse events. "Force quit" is required to get rid of it. ### What is the expected behavior qBittorrent becomes responsive to keyboard and mouse inputs. ### Steps to reproduce Launch qBittorrent. ### Extra info(if any) Problem was resolved after I deleted file ~/Library/Application Support/qBittorrent/rss/articles/storage.lock

deekerman

2026-02-21 21:16:00 -05:00

closed this issue
added the
Core

OS: macOS
labels

deekerman commented

2026-02-21 21:16:10 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 8, 2024):

Maybe related to other storage.lock ticket: https://github.com/qbittorrent/qBittorrent/issues/20408#issuecomment-1938604786
But ticket is old. Closing and redirecting anyone still experiencing this issue to above ticket

@luzpaz commented on GitHub (Aug 8, 2024): Maybe related to other `storage.lock` ticket: https://github.com/qbittorrent/qBittorrent/issues/20408#issuecomment-1938604786 But ticket is old. Closing and redirecting anyone still experiencing this issue to above ticket