SABnzbd Forums

On my Kubuntu 20.04 installation, SABnzbd crashes so frequently that it's useless. First I installed the version that you get from the ubuntu repositories. Then I removed it and followed the instructions on the Ubuntu PPA Repository page. First I chose the nobetas option and got the same results. Then I tried the option that makes the betas available. It wouldn't even start. Brave opens with a message that SABnzbd refused to connect. I eventually installed the windows version under wine. It works just fine. Any idea what happened? I looked around the support forum and saw nothing that mentioned the problem I have.

If SABnzbd crashes, it would give a traceback and tell what happened.

Other possibilities, but not crashes:
- that SABnzbd starts with an error message, and stops
- that SABnzbd starts, but you close the terminal, and it thus stops
- that SABnzbd is nicely running, but you cannot access it

So ... if you can give more info, we could help

The $*&#^($ board won't let me post links, so it rejects most of what I copied from the terminal window. I guess I'll find out if this gets through.

(sabnzbdplus:22096): Gdk-ERROR **: 20:32:50.042: The program 'sabnzbdplus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 22431 error_code 3 request_code 18 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Wow. SAB does nothing with X

Can you start from the command line, post the stdout logging on pastebin, and that url here with spaces in it

Edit: sab does put an icon onto the GUI, so maybe that is a cause ... ?

I started it this morning and it finished downloading the file. So I started another. I put in spaces like you said, but was rejected.

h t t p s colon slash slash pastebin dot com slash 7EhHMUUu

I used to have Kubuntu 18.04 installed on this machine and had no trouble with SABnzbd. When I installed 20.04, I saw a new version of SABnzbd.

It seems indeed the icon and/or notifications is the problem:
https://pastebin.com/raw/7EhHMUUu

You could try to disable the notifications in Config > Notifications.

Created a bug-report: https://github.com/sabnzbd/sabnzbd/issues/1570

I went into Config > notifications and unchecked everything. It happened again.

pastebin dot com / U2NMxGXL

That's unfortunate. Could you check the bug report? Some suggestion was given there that could work.

I don't know if this matters, but I have a GeForce GT 710 with 2GB RAM. The Nvidia X server settings app says I have NVIDIA driver version 440.100 installed.

safihre wrote: ↑August 10th, 2020, 12:18 am That's unfortunate. Could you check the bug report? Some suggestion was given there that could work.

I found these.
Usually its a 'we cant replicate it' and then the user eventually either says they fixed it by doing one of these two things:

Resetting Xfce Panels to default
I don't have Xfce

Close other apps that when open triggers the issue in another app
I don't have other apps that trigger this issue.

OP should turn on DEBUG in SAB to see if he has a line like this in sabnzbd.log

2020-08-10 17:57:46,030::DEBUG::[sabtraylinux:36] XApp not available, falling back to Gtk.StatusIcon

I tried sabnzbdplus -l 2 I only started it once today. Here is everything from sabnzbd.log dated today August 10.

pastebin dot com / dqzNcB5b

@delboy, a few questions:

Do the crashes happen at defined moments, so for example: at SAB startup, at download starts, at download finishes. Or ... at random moments.

When the crash happens, does SAB continue to run?


(FWIW: I think it is Kubuntu / KDE related, but at this moment I have no Kubuntu at hand to try to reproduce. Hopefully this weekend)

The crashes happen seemingly at random. SAB does not continue to run. I understand not having the same OS to try it out on. That would be a lot of resources to have available.

On my computer, I installed Gnome tonight. I logged out of KDE and into Gnome, then started SAB. I downloaded a 4.7GB file which took a little over an hour. SAB didn't crash once. I would suspect it's a KDE thing since it works fine under Gnome.