App closes after downloading podcasts

[pedro2555]

Prerequisites

• I have searched the Issues list for open and closed issues and believe this is a unique, currently unreported bug.

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

1. Add podcasts to your library (I have Joe Rogan and the Portal only)
2. Reboot
3. Open the app
4. Wait a few seonds (probably for the network)
5. App closes with a notification that new podcasts have been added to your library.

Expected behavior

The must not close by itself.

Platform Information

Please share as many of the following details as possible:

• Linux distrubution: Elementary OS 5.1.3 Hera Ubuntu 18.04.3 LTS Linux 5.3.8-050308-generic

Please check the applicable option below:

• I'm using the latest version from git that I've manually compiled
• I'm using the latest version of the Flatpak, downloaded from Flathub.org
• I'm using the latest version available from AppCenter
• I'm using a different version (please note here) :

[Hanouta]

Could you launch vocal from the terminal and post the log (if the application closes/crashes) here?
I couldn't reproduce this issue on my system.

[pedro2555]

How does one start the app from the terminal?

$ vocal
vocal: command not found

[Hanouta]

$ com.github.needle-and-thread.vocal

[pedro2555]

Ok. So from the terminal I can see that Segmentation Fault happens.

What I did

1. Run the app from the terminal, like bellow:

$ com.github.needle-and-thread.vocal > vocal.log 2>&1

2. Started playing a podcast

Results

• The app crashed about 2 minutes into the podcast.
• A notification saying Fresh content has been added to your library. appears.
• On the terminal window Segmentation fault appears.

vocal.log

if you need anything else, let me know. Very much appreciated.

[Hanouta]

This doesn't make a lot of sense to me, because the Notification is only being sent after updating the Podcasts, but I don't see the "Checking for updates" message(which is being sent before it starts updating) in your log. The only assumption I have would be that your database(located in ~/.config/vocal/database) is corrupted somehow(did you reboot the PC while Vocal was running?), but even if this would be the case, it should still show the "Checking for updates" message.

[pedro2555]

About rebooting while vocal was running. Its a bit hard to say so, not that I remember but totally possible. (I ocassionally reboot to a Windows installation and I do care very little to closing running apps on linux, simply hit restart; but again I do not recall that this happened).

As for the database, if it is corrupted, it was the app that corrupted it in some way or another.

From installation to starting to see this, was pretty much no time at all. But I did manage to listen to one of the latest Joe Rogan podcasts (not all of it, but that is because I intentionally switched to the phone). Ever since then, which is the next day, this happens.

Here's the db if it helps. I've added a third subscription there for the sake of pin pointing the issue. This started happening with Joe Rogan and The Portal podcasts only.

vocal.db.zip

[Hanouta]

Strange, even with your database I can't reproduce this issue. The only crashes I've experienced were immediately at startup, and I think the cause for that has already been fixed(should be part of the next release). I guess you'll have to wait for the next release and hope it doesn't happen anymore(there will be a couple of crash fixes in the next version).

[pedro2555]

Sounds good. I'll keep you posted.

…

On Fri, 17 Apr 2020, 18:09 Brn9hrd7, ***@***.***> wrote: Strange, even with your database I can't reproduce this issue. The only crashes I've experienced were immediately at startup, and I think the cause for that has already been fixed(should be part of the next release). I guess you'll have to wait for the next release and hope it doesn't happen anymore(there will be a couple of crash fixes in the next version). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMRYN7ZOVX7AFT25T6DA2TRNCENZANCNFSM4MKVIJRQ> .

[nathandyer]

Hi @pedro2555, thanks for your report! Just to confirm what @brn9hrd7 has said, I also can't reproduce this issue, and I'm also fairly certain this has already been fixed for the next release. We'll leave your issue open and then, once it's out, ask you to try again to confirm if it is indeed fixed for you or not.

[pedro2555]

@nathandyer perfecto.

[pedro2555]

@nathandyer any advance?