I installed Kubuntu (wow, that is beautiful), ran SABnzbd from git, did a few downloads, got nice icons and popup icon, and no crashes.
I'll do some more downloads to see what happens.
SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Have you tried the version here?
sabnzbd dot org / wiki / installation / install-ubuntu-repo
I'll see if I can figure out how to install it from git.
sabnzbd dot org / wiki / installation / install-ubuntu-repo
I'll see if I can figure out how to install it from git.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Note: I think you can now post URLs and texts
I've tried the (K)Ubuntu repo version, and the git version. Not yet the PPA version as mentioned on https://sabnzbd.org/wiki/installation/i ... buntu-repo. So I'll do that, but I do not expect any differences
Update: no problems with PPA version either.
I've tried the (K)Ubuntu repo version, and the git version. Not yet the PPA version as mentioned on https://sabnzbd.org/wiki/installation/i ... buntu-repo. So I'll do that, but I do not expect any differences
Update: no problems with PPA version either.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
I tried to install from git, but kept getting errors. Something is happening here. I wonder why it's crashing for me but not you. I am using the nvidia drivers for my video card. Are you? Any idea what else might be the problem?
The manual for the motherboard says it's a Gigabyte GA-P35=D3SL/S3L. Dmidecode returned this
sudo dmidecode -t 2
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: P35-DS3L
Version: x.x
Serial Number:
Here are the results from less /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
microcode : 0xba
cpu MHz : 2707.580
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti tpr_shadow vnmi flexpriority dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6000.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
microcode : 0xba
cpu MHz : 2599.396
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti tpr_shadow vnmi flexpriority dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6000.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
The manual for the motherboard says it's a Gigabyte GA-P35=D3SL/S3L. Dmidecode returned this
sudo dmidecode -t 2
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: P35-DS3L
Version: x.x
Serial Number:
Here are the results from less /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
microcode : 0xba
cpu MHz : 2707.580
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti tpr_shadow vnmi flexpriority dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6000.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz
stepping : 11
microcode : 0xba
cpu MHz : 2599.396
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti tpr_shadow vnmi flexpriority dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 6000.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
No, I use an Intel GPU.
Do you get crashes from other programs?
Worth a try:
If you go to http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable and click on Test Notification, what happens?
And on that same http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable , if you uncheck Enable NotifyOSD, and let SAB do downloads, do you get crashes?
Do you get crashes from other programs?
Worth a try:
If you go to http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable and click on Test Notification, what happens?
And on that same http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable , if you uncheck Enable NotifyOSD, and let SAB do downloads, do you get crashes?
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
I use gmail. I filled in the email server information and clicked Test Email, but nothing ever arrived in the inbox. Next to Test Email the envelope icon keeps gounf round and round. I suspect the problem sending emails is related to not being able to set any encyption options .sander wrote: ↑August 14th, 2020, 11:45 pm No, I use an Intel GPU.
Do you get crashes from other programs?
Worth a try:
If you go to http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable and click on Test Notification, what happens?
And on that same http://127.0.0.1:8080/sabnzbd/config/no ... osd_enable , if you uncheck Enable NotifyOSD, and let SAB do downloads, do you get crashes?
Before I tried to send the test email, nothing was checked or filled in on that page.It crashed while I was trying to fill in the email server data. It doesn't have anything to download, yet still crashes. Here's what I found in the terminal window. https://pastebin.com/0Ppu4Kbh
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Oh, no, you went into mail stuff. Not good. Please reread my post, and click on the URL I posted.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
I had all the notification stuff turned off. Everything on that page was unchecked. After I clicked the option to enable the notification script, I saw the Test Notification button. I saw the test notification and the following in the terminal window.
2020-08-15 12:50:55,104::DEBUG::[api:121] API-call from 127.0.0.1 [Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36] {'mode': 'test_osd', 'apikey': '4b905ad827f749c1b393d7d43217ba8b', 'output': 'json', 'ntfosd_enable': '1', 'ntfosd_prio_startup': '1', 'ntfosd_prio_download': '1', 'ntfosd_prio_pp': '1', 'ntfosd_prio_complete': '1', 'ntfosd_prio_failed': '1', 'ntfosd_prio_queue_done': '1', 'ntfosd_prio_disk_full': '1', 'ntfosd_prio_new_login': '1', 'ntfosd_prio_warning': '1', 'ntfosd_prio_error': '1', 'ntfosd_prio_other': '1', 'ntfosd_cats': '*'}
2020-08-15 12:50:55,107::INFO::[api:759] Sending OSD notification
2020-08-15 12:50:55,109::INFO::[notifier:178] Send to NotifyOSD: SABnzbd / Test Notification
Sometimes I could click test notification several times before it would crash. Other times I could click test notification once or it would crash before I could click it.
Here's what I get in the terminal window when it crashes. It mentions running it with the GDK_SYNCHRONIZE environment variable to help debug the program. How do I do this?
(sabnzbdplus:15133): Gdk-ERROR **: 12:55:40.880: 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 3922 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)
2020-08-15 12:50:55,104::DEBUG::[api:121] API-call from 127.0.0.1 [Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36] {'mode': 'test_osd', 'apikey': '4b905ad827f749c1b393d7d43217ba8b', 'output': 'json', 'ntfosd_enable': '1', 'ntfosd_prio_startup': '1', 'ntfosd_prio_download': '1', 'ntfosd_prio_pp': '1', 'ntfosd_prio_complete': '1', 'ntfosd_prio_failed': '1', 'ntfosd_prio_queue_done': '1', 'ntfosd_prio_disk_full': '1', 'ntfosd_prio_new_login': '1', 'ntfosd_prio_warning': '1', 'ntfosd_prio_error': '1', 'ntfosd_prio_other': '1', 'ntfosd_cats': '*'}
2020-08-15 12:50:55,107::INFO::[api:759] Sending OSD notification
2020-08-15 12:50:55,109::INFO::[notifier:178] Send to NotifyOSD: SABnzbd / Test Notification
Sometimes I could click test notification several times before it would crash. Other times I could click test notification once or it would crash before I could click it.
Here's what I get in the terminal window when it crashes. It mentions running it with the GDK_SYNCHRONIZE environment variable to help debug the program. How do I do this?
(sabnzbdplus:15133): Gdk-ERROR **: 12:55:40.880: 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 3922 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)
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Oh, you had NotifyOSD off?! Hmmm ... very weird.
Answering your questions based on some Google searches:
If sab crashes, hopefully there is a core file.
With another program, I created a crash and core dump, and the core file showed this:
Hopefully you have a core file and tells which binary crashes. As sabnzbd is not a binary (but a python script), I expect another binary in the core file.
Answering your questions based on some Google searches:
Code: Select all
export GDK_SYNCHRONIZE=1
printenv | grep GDK_SYNCHRONIZE # check that it is set
ulimit -c unlimited # to allow core files
sabnzbdplus # start SAB
With another program, I created a crash and core dump, and the core file showed this:
Code: Select all
$ file core
core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from './hello_crasher', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: './hello_crasher', platform: 'x86_64'
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Oh, wow, update: I got a crash on Kubuntu! I don't use that Kubuntu much, so I only see it now.
So, the good news: I get a crash, on my Intel GPU, so not related to Nvidia. And not related to your specific setup.
So, I ran the commands I gave above on my system
which immediately gives the crash, ... plus a core file:
Hmmmm. Problem in the python3 binary?
And after disabling OSD, the crash happens immediately
Wow
FWIW
So, the good news: I get a crash, on my Intel GPU, so not related to Nvidia. And not related to your specific setup.
Code: Select all
2020-08-14 07:57:27,032::DEBUG::[__init__:926] [sabnzbd.save_admin] Saving data for watched_data2.sab in /home/sander/.sabnzbd/admin
2020-08-14 07:57:27,032::INFO::[postproc:132] Saving postproc queue
2020-08-14 07:57:27,032::DEBUG::[__init__:994] [sabnzbd.postproc.save] Saving data for postproc2.sab
2020-08-14 07:57:27,033::DEBUG::[__init__:926] [sabnzbd.save_admin] Saving data for postproc2.sab in /home/sander/.sabnzbd/admin
2020-08-14 07:57:27,033::INFO::[notifier:178] Send to NotifyOSD: SABnzbd / Queue finished
(sabnzbdplus:84773): Gdk-ERROR **: 08:27:21.381: 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 224976 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)
sander@kubuntu2004:~/git/sabnzbd$
Code: Select all
export GDK_SYNCHRONIZE=1
printenv | grep GDK_SYNCHRONIZE
ulimit -c unlimited
./SABnzbd.py
Code: Select all
$ file core
core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/python3 -OO ./SABnzbd.py', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: './SABnzbd.py', platform: 'x86_64'
And after disabling OSD, the crash happens immediately
Code: Select all
$ cat ~/.sabnzbd/sabnzbd.ini | grep -i osd_enable
ntfosd_enable = 0
FWIW
Code: Select all
2020-08-16 00:22:45,755::DEBUG::[sabtraylinux:33] XApp found: <XAppProxyModule <IntrospectionModule 'XApp' from '/usr/lib/x86_64-linux-gnu/girepository-1.0/XApp-1.0.typelib'>>
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
OK, after also installing python3.7 and using that for SABnzbd, SAB is stable.
SAB runs, but the notifications don't work at all anymore. When I click on Test Notification, the GUI says "Cannot send, missing required data"
Note: python3.8 is still there, as python3, so no effect on your install.
Code: Select all
# Install python3.7:
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt-get update
sudo apt-get upgrade
sudo apt install python3.7
python3.7 -V
# Now get the source of SAB, and install the requirements into python3.7:
cd
wget https://github.com/sabnzbd/sabnzbd/archive/3.0.0.zip
unzip 3.0.0.zip
cd sabnzbd-3.0.0/
python3.7 -m pip install -r requirements.txt -U # Note the -U at the end!!!
# and run SAB:
python3.7 SABnzbd.py
Note: python3.8 is still there, as python3, so no effect on your install.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Kubuntu has detected the python3.8 crash, and has reported it via Apport. Title is "python3.8 crashed with signal 5 in _XReply()"
I cannot find it (yet?) on https://bugs.launchpad.net/
I cannot find it (yet?) on https://bugs.launchpad.net/
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
Based on https://github.com/sabnzbd/sabnzbd/issu ... -657738536 , I removed gir1.2-xapp-1.0, but still a crash with python3.8. Pity.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
OK, an easier workaround:
in SABnzbd.py / sabnzbdplus, find the line
around line 1249, and comment it out:
That way the sabnzbd.sabtraylinux.StatusIcon() is not called, and no more crashes.
in SABnzbd.py / sabnzbdplus, find the line
Code: Select all
sabnzbd.LINUXTRAY = sabnzbd.sabtraylinux.StatusIcon()
Code: Select all
# sabnzbd.LINUXTRAY = sabnzbd.sabtraylinux.StatusIcon()
That way the sabnzbd.sabtraylinux.StatusIcon() is not called, and no more crashes.
Re: SABnzbd 3.0.0 crashes frequently in Kubuntu 20.04
You can disable it by switch off the Special Setting "win_menu". If you can't reach the Special Setting's page, you can also do it in your sabnzbd.ini.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate