[PR #1780] [MERGED] Add a profile for bitcoin-qt #4071

New issue

Closed

opened 2026-05-05 10:13:12 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:13:12 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/1780
Author: @baryluk
Created: 2/20/2018
Status: ✅ Merged
Merged: 2/20/2018
Merged by: @Fred-Barclay

Base: master ← Head: master

📝 Commits (6)

e2e565b Add a profile for Bitcoin Core QT client / wallet
8495dc2 Remove unecassary blacklist for bitcoin-qt config. Comment about private-lib
254d2a9 Also whitelist .bitcoin-testnet just in case
90dba32 Revert "Also whitelist .bitcoin-testnet just in case"
88462e3 Revert "Also whitelist .bitcoin-testnet just in case"
5568c39 Merge branch 'master' of github.com:baryluk/firejail

📊 Changes

1 file changed (+47 additions, -0 deletions)

View changed files

➕ etc/bitcoin-qt.profile (+47 -0)

📄 Description

Works just fine, including remembering all settings.

libGL / mesa-loader errors out when trying to detect device or trying to load drivers, but it still works fine with no3d.

It even works just fine with private-lib, but qt then complains about openssl incompatibilities. So for now, I left it commented out.

It appears also removing machine-id does not make any harm either, but I have seen it in ktorrent.profile (which was my starting point somehow), so I am not sure.

In syslog only thing I see is:

Feb 20 18:13:05 xyz firejail[9]: blacklist violation - sandbox 30207, exe bitcoin-qt, syscall opendir, path /dev/dri

but that is expected due no3d thingy. It is fine. Would be nice to be able to ignore that from logging.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/1780 **Author:** [@baryluk](https://github.com/baryluk) **Created:** 2/20/2018 **Status:** ✅ Merged **Merged:** 2/20/2018 **Merged by:** [@Fred-Barclay](https://github.com/Fred-Barclay) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (6) - [`e2e565b`](https://github.com/netblue30/firejail/commit/e2e565bedc777a3ed327ff5209af478a40355a44) Add a profile for Bitcoin Core QT client / wallet - [`8495dc2`](https://github.com/netblue30/firejail/commit/8495dc20df4c1ef881a46e9a5f7d30da0068dd85) Remove unecassary blacklist for bitcoin-qt config. Comment about private-lib - [`254d2a9`](https://github.com/netblue30/firejail/commit/254d2a9d9b6e752c0e3188fa90e4c5856eae5979) Also whitelist .bitcoin-testnet just in case - [`90dba32`](https://github.com/netblue30/firejail/commit/90dba32583ec07749d16821c2006cf877798c7f0) Revert "Also whitelist .bitcoin-testnet just in case" - [`88462e3`](https://github.com/netblue30/firejail/commit/88462e369cb24cda7d354ce6aa784bba6680736e) Revert "Also whitelist .bitcoin-testnet just in case" - [`5568c39`](https://github.com/netblue30/firejail/commit/5568c395e1cf357405d8df0ce8f10a33f033e632) Merge branch 'master' of github.com:baryluk/firejail ### 📊 Changes **1 file changed** (+47 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `etc/bitcoin-qt.profile` (+47 -0) </details> ### 📄 Description Works just fine, including remembering all settings. libGL / mesa-loader errors out when trying to detect device or trying to load drivers, but it still works fine with no3d. It even works just fine with private-lib, but qt then complains about openssl incompatibilities. So for now, I left it commented out. It appears also removing machine-id does not make any harm either, but I have seen it in ktorrent.profile (which was my starting point somehow), so I am not sure. In syslog only thing I see is: Feb 20 18:13:05 xyz firejail[9]: blacklist violation - sandbox 30207, exe bitcoin-qt, syscall opendir, path /dev/dri but that is expected due no3d thingy. It is fine. Would be nice to be able to ignore that from logging. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>