starred/qBittorrent

Fork 0

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

qbittorrent Linux 3.3.7 - Asking me everytime I add a torrent the box one gets when you install it first, if you agree or not #4828

New issue

Closed

opened 2026-02-21 17:31:36 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-21 17:31:36 -05:00

Owner

Originally created by @flzzjw72z on GitHub (Oct 30, 2016).

It's pretty annoying, is there a way to turn that off?. I have to turn off qbittorrent too, or else it will be turning on a fresh empty copy of qbittorrent. Could this be caused by Firefox being in Firejail? Firejail-tools autodetects programs it can run in a sandbox and qbittorrent is there...I don't dislike the idea, but all of my seeding and things I haven't looked at yet in the completed list are not there. I think Firejailed-Firefox calls on a sandboxed qbittorrent, I'm not sure.

In any case, if I download a .torrent file, firefox asks me with what I want to open it, as I want it to be, with qbittorrent being the default choice, and then the "first-time-turning-qbit-on-agreement-window" shows up and I got to say agree all the time.

I know some of the problem is likely on my side, but should a non sandboxed qbittorrent ask me this, as it's chilling in my notification area?

Originally created by @flzzjw72z on GitHub (Oct 30, 2016). It's pretty annoying, is there a way to turn that off?. I have to turn off qbittorrent too, or else it will be turning on a fresh empty copy of qbittorrent. Could this be caused by Firefox being in Firejail? Firejail-tools autodetects programs it can run in a sandbox and qbittorrent is there...I don't dislike the idea, but all of my seeding and things I haven't looked at yet in the completed list are not there. I think Firejailed-Firefox calls on a sandboxed qbittorrent, I'm not sure. In any case, if I download a .torrent file, firefox asks me with what I want to open it, as I want it to be, with qbittorrent being the default choice, and then the "first-time-turning-qbit-on-agreement-window" shows up and I got to say agree all the time. I know some of the problem is likely on my side, but should a non sandboxed qbittorrent ask me this, as it's chilling in my notification area?

deekerman closed this issue

2026-02-21 17:31:38 -05:00

deekerman commented

2026-02-21 17:31:41 -05:00

Author

Owner

@thalieht commented on GitHub (Oct 30, 2016):

qbit stores it's settings in
~/.config/qBittorrent/qBittorrent.conf
so it's probably not allowed to write to that file.

[LegalNotice]
Accepted=true

is what you're looking for. If it's not in there write it yourself.

~/.local/share/data/qBittorrent/ for the .torrents and fastresume data.

@thalieht commented on GitHub (Oct 30, 2016): qbit stores it's settings in `~/.config/qBittorrent/qBittorrent.conf` so it's probably not allowed to write to that file. > [LegalNotice] > Accepted=true is what you're looking for. If it's not in there write it yourself. `~/.local/share/data/qBittorrent/` for the .torrents and fastresume data.

deekerman commented

2026-02-21 17:31:41 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 30, 2016):

If multiple instances of qbt are running together then that means that each one sees a different TMP path, and can't communicate with the first instance(it actually doesn't see the first instance)

@sledgehammer999 commented on GitHub (Oct 30, 2016): If multiple instances of qbt are running together then that means that each one sees a different TMP path, and can't communicate with the first instance(it actually doesn't see the first instance)

deekerman commented

2026-02-21 17:31:41 -05:00

Author

Owner

@flzzjw72z commented on GitHub (Oct 31, 2016):

Thanks thalieht. As for what you're saying sledgehammer999, when I have an already running qbit in the notification area, it's one instance, when I call up a new .torrent from my browser, it goes to them..now, it used to...for some reason there is 2 qbittorrent the applications list in Firefox and one opens a brand new one, probably a feature of Firejail, since it's already offering Firejail for qbittorrent in the Firejail-Tools menu-gui thing. Although, I've never started it this way, knowing obviously it would be like a brand new copy.

@flzzjw72z commented on GitHub (Oct 31, 2016): Thanks thalieht. As for what you're saying sledgehammer999, when I have an already running qbit in the notification area, it's one instance, when I call up a new .torrent from my browser, it goes to them..now, it used to...for some reason there is 2 qbittorrent the applications list in Firefox and one opens a brand new one, probably a feature of Firejail, since it's already offering Firejail for qbittorrent in the Firejail-Tools menu-gui thing. Although, I've never started it this way, knowing obviously it would be like a brand new copy.

deekerman commented

2026-02-21 17:31:41 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 31, 2016):

So your true problem is that the popup keeps getting displayed from the non-jailed instance.
That means that for some reason, it cannot write to the config file.
Can you check the log(after at least 5secs)? One of these lines might be present:

"An access error occurred while trying to write the configuration file."
"A format error occurred while trying to write the configuration file."

What happens if you open qbittorrent yourself(non jail), close it and reopen it? Does it still show the popup?

@sledgehammer999 commented on GitHub (Oct 31, 2016): So your true problem is that the popup keeps getting displayed from the non-jailed instance. That means that for some reason, it cannot write to the config file. Can you check the log(after at least 5secs)? One of these lines might be present: 1. "An access error occurred while trying to write the configuration file." 2. "A format error occurred while trying to write the configuration file." What happens if you open qbittorrent yourself(non jail), close it and reopen it? Does it still show the popup?

deekerman commented

2026-02-21 17:31:42 -05:00

Author

Owner

@flzzjw72z commented on GitHub (Oct 31, 2016):

What? When I have qbittorrent, I have it set to minimize/close to the notification area, and when I load a new torrent from firefox, that one instance will pick it up. Which it does. But I get the "first-time use" warning all the time all of a sudden.

@flzzjw72z commented on GitHub (Oct 31, 2016): What? When I have qbittorrent, I have it set to minimize/close to the notification area, and when I load a new torrent from firefox, that one instance will pick it up. Which it does. But I get the "first-time use" warning all the time all of a sudden.

deekerman commented

2026-02-21 17:31:42 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 31, 2016):

But I get the "first-time use" warning all the time all of a sudden.

What do you mean by all the time? Is it occurring every X seconds or after you load a new torrent?

Also for testing do the following:

Start qbt and accept the popup.
Close qbt
Open it again. Does it show the popup?

@sledgehammer999 commented on GitHub (Oct 31, 2016): > But I get the "first-time use" warning all the time all of a sudden. What do you mean by all the time? Is it occurring every X seconds or after you load a new torrent? Also for testing do the following: 1. Start qbt and accept the popup. 2. Close qbt 3. Open it again. Does it show the popup?

deekerman commented

2026-02-21 17:31:42 -05:00

Author

Owner

@flzzjw72z commented on GitHub (Oct 31, 2016):

First, I have to say, I've never loaded qbittorrent through firejail. Only Firefox and Thunderbird are. I don't know where you got this impression from.

Starting qbittorrent from the icon I placed in my top panel will not bring up the message.

The problem is, as I said in post #1, Firejailed Firefox opens a seemingly jailed qbittorrent with the first-time use message. I looked in the Applications in the Firefox preferences and there was 2 qbittorrent instances, I made it pick the other one. Now, the never-jailed, in the notification area qbittorrent that is running, the regular one, will still give me this first-use warning but when I click I agree it will add to the rest of the material that's already there.

Hope that's clear now.

@flzzjw72z commented on GitHub (Oct 31, 2016): First, I have to say, I've never loaded qbittorrent through firejail. Only Firefox and Thunderbird are. I don't know where you got this impression from. Starting qbittorrent from the icon I placed in my top panel will not bring up the message. The problem is, as I said in post #1, Firejailed Firefox opens a seemingly jailed qbittorrent with the first-time use message. I looked in the Applications in the Firefox preferences and there was 2 qbittorrent instances, I made it pick the other one. Now, the never-jailed, in the notification area qbittorrent that is running, the regular one, will still give me this first-use warning but when I click I agree it will add to the rest of the material that's already there. Hope that's clear now.

deekerman commented

2026-02-21 17:31:42 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 31, 2016):

I am asking specific questions here.

Let's forget about the jailed version. Let's talk about the non-jailed one which you already run. I want to know at what point does the popup appear. Is it everytime you load a torrent from firefox? If yes, then do the following. Don't dismiss the popup. Open your "task manager" app (or similar) and see the processes running. Do you see 2 entries of qbittorrent there?

@sledgehammer999 commented on GitHub (Oct 31, 2016): I am asking specific questions here. Let's forget about the jailed version. Let's talk about the non-jailed one which you already run. I want to know at what point does the popup appear. Is it everytime you load a torrent from firefox? If yes, then do the following. Don't dismiss the popup. Open your "task manager" app (or similar) and see the processes running. Do you see 2 entries of qbittorrent there?

deekerman commented

2026-02-21 17:31:42 -05:00

Author

Owner

@Balls0fSteel commented on GitHub (Jan 20, 2017):

Closing this as OP disappeared.
Also, firejail can make any application behave weird, it is a security software.
If you want some permanent security, use Tomoyo, AppArmor, SELinux, etc.

Firejail is more like a one time thing. The arguments you call it with also matters a ton.

@Balls0fSteel commented on GitHub (Jan 20, 2017): Closing this as OP disappeared. Also, firejail can make any application behave weird, it is a security software. If you want some permanent security, use Tomoyo, AppArmor, SELinux, etc. Firejail is more like a one time thing. The arguments you call it with also matters a ton.