Chocobo1

> It seems to only affect private torrents so i suspect it's because of the new libtorrent's `clear_peers` we introduced in 4.3.0 for private torrents. > > https://github.com/qbittorrent/qBittorrent/blob/61770ad69edea4a59d1597a4081a36532f16de15/src/base/bittorrent/torrenthandleimpl.cpp#L376-L377 > >...

Although not strictly required, it would also be nice to add the option to webui. You'll only need to add a few code to appcontroller.cpp and preferences.html.

> > I am thinking out loud. I don't have strong feelings towards it. I can implement your proposal tomorrow probably. > > Let's get @Chocobo1 opinion. I think the...

>What's the hold up? Is this not ready to merge? Wait for sledgehammer999 to merge it himself.

>@Chocobo1 should I follow @HanabishiRecca recommendation (apply dark class) or do you have something else to propose? I think it is fine. I would also add a code comment about...

@ngosang , I am inclined to this way: https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-35165918

The whole SELinux seems rather painful to setup. Anyway it is good that you have filed the issue. I'm sure others that encountered the same issue is able to find...

>:Z is the correct option, unless there are more than one instances of qbittorrent sharing the same config/downloads folder. Won't it prevent the host from accessing the folders? At least...

>I kept it since technically the host should not write to the folder either. Do you mean the host can still read it but cannot write it? If the host...

@Piccirello @skomerko Just in case you are interested in it.