Package Details: sabnzbd 3.4.2-2

Git Clone URL: (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL:
Keywords: network usenet
Licenses: GPL
Submitter: kvasthval
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 261
Popularity: 0.078905
First Submitted: 2007-11-09 16:21
Last Updated: 2021-12-13 16:09

Pinned Comments

fryfrog commented on 2022-01-26 22:58

@gee: thanks for the information, I confirmed break and resolve by downgrade myself too.

Suggest aur/downgrade package: sudo downgrade python-jaraco super easy mode.

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 14 ... Next › Last »

martinm1000 commented on 2020-08-05 03:50


You can forget this, it works !

I changed the Group=%I to Group=users

I don't known why it worked before and just stopped, and if its related to systemd or sabnzbd.

martinm1000 commented on 2020-08-05 03:44


Here is my old file that do not work anymore, but the ExecStart does work when running in a terminal:

Description=SABnzbd binary newsreader

ExecStart=/usr/lib/sabnzbd/ --logging 0 --browser 0 --config-file /home/%I/.sabnzbd.ini


As described in

My ~/.sabnzbd.ini is a directory, but the problem isn't there.

fryfrog commented on 2020-08-05 03:41

@martinm1000: I don't use that method of .service, can you describe a little bit about how you do it and I can try it on mine?

fryfrog commented on 2020-08-04 18:53

I "tested" by just removing the 2.3.9 sabnzbd package and it leaves a lot of trash around in /opt/sabnzbd that isn't related. And the defaults are an admin and logs folder and the sabnzbd.ini. I think someone who's queue/history didn't get properly moved needs to tell me their setup. My guess is that they've change the values for "Administrative Folder" and/or "Log Folder" which means they could be anywhere.

I'll improve the little bit of output from the package and I think maybe I should improve and link the wiki w/ some details.

But in the end, it'll be a one time pain at least. :/

fryfrog commented on 2020-08-04 18:45

That is a good point, let me have a look.

Kr1ss commented on 2020-08-04 18:41

Well, at the time of execution of post_upgrade() the files in /opt/sabnzbd/ which belong to the package should already be removed, since the actual upgrade has already been done. I think, therefore only configuration files should be left there.

I did not actually test that though, and I can't do so atm.

fryfrog commented on 2020-08-04 18:35

@mkomko: The old /opt/sabnzbd folder has everything in it, the configs and the installation. It'd be a hot mess to copy everything, I think.

On a default installation of 3.0.0, all the queue and history files are in the admin folder and it defaults to admin folder. Let me go back and install the last version and see how that is.

mkomko commented on 2020-08-04 18:23

@fryfrog: Couldn't you just move "everything"? That's what I would expect.

fryfrog commented on 2020-08-04 17:35

@tixetsal: Can you poke around in your /opt/sabnzbd and see what file you need to move to /var/lib/sabnzbd/ to get your history to come over? It might be history1.db and some *.sab files looking at my install. I'll play around on my test nas and see if I can figure out what I've missed too. Thanks for reporting!

tixetsal commented on 2020-08-04 16:46

I just upgraded from 3.0.0 to 3.0.0-2 and like others, I had to manually fix my config file location when upgrading from 2.x to 3. I also had to manually move in my instance. I lost all my sab history and had to overwrite the keys sab wanted me to use after install.

Is it normal to have to overwrite the key that gets generated? I'm guessing the loss of history was a problem with the upgrade script from 2.x to 3, but I was surprised to lose my history again after the 3.0.0 to 3.0.0-2 upgrade. ?