Bug 71

Summary: Asunder completely crashes out when there is no DNS server availaible
Product: Asunder Reporter: benjaminulrich67
Component: AllAssignee: Andrew Smith <asmith22+bugs>
Status: CONFIRMED ---    
Severity: normal CC: asmith22+bugs
Priority: ---    
Version: Older   
Hardware: PC   
OS: Linux   

Description benjaminulrich67 2021-05-22 07:35:24 EDT
Using version 2.9.7, from Archlinux on an AMD 64 platform, I had Asunder launched without any DNS server available. Thus, when trying to resolve informations from the CDDB database, Asunder completely crashed. It seemed that could not resolve anything, and then Asunder closed itself. In doing this, it also didn't try to extract any music file.

Problem: instead of crashing, it should only show that it can't find any information or that it couldn't connect to the database. When finding no information, it shouldn't quit, Asunder shouldn't stop, and the user should have the available choice to go on and extract the music files without additional information from the database.

Precise message I got:

"*** longjmp causes uninitialized stack frame ***: terminated
Abandon (core dumped)"

Reproducing the bug:

Insert a CDROM. Unconfigure DNS in /etc/resolv.conf (by using for example and arbitrary IP) previously, on Archlinux with Asunder 2.9.7. Launch Asunder. It will not be able to connect to the CDDB database, and will suddenly quit. 

Additional information: the CDROM Asunder was trying to find informations on the database wasn't referenced in the database. But, once connected through a DNS server, although it had no information on the album nor any of its tracks, it didn't crash at all and I coud extract all the music files. Therefore, the actual problem seems to be the DNS connection, and not the fact that my CDROM is unknown to CDDB.
Comment 1 Andrew Smith 2021-05-22 20:05:13 EDT
Hi Benjamin

Thanks for the bug report. I cannot reproduce the crash. When I follow the steps, I just get: "libcddb: error: unknown host name" in the terminal and everything else works as expected.

I wonder if it's a libcddb problem. Can you please run "locate libcddb" on your machine and tell me what version it is? I've got this on my machine:

/usr/lib/x86_64-linux-gnu/libcddb.a
/usr/lib/x86_64-linux-gnu/libcddb.so
/usr/lib/x86_64-linux-gnu/libcddb.so.2
/usr/lib/x86_64-linux-gnu/libcddb.so.2.2.3