[GH-ISSUE #332] Crashes on startup on FreeBSD #176

Open
opened 2026-03-02 23:45:14 +03:00 by kerem · 6 comments
Owner

Originally created by @pepe82sh on GitHub (Jan 6, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/332

Describe the bug
I've just installed Spotify-Player inside a freeBSD jail. It has been built with the default options. On calling spotify_player my it'll start rendering the "window" but then fails fatally creating a core dump.

To Reproduce
Install on FreeBSD and run.

Expected behavior
Application not crashing.

Log and backtrace
Core dump can be provided upon request. Buildlog:
spotify-player-0.16.3.buildlog.txt

Screenshots
Screenshot 2024-01-06 at 23 31 04

Environment

  • OS: FreeBSD 13.2 (jailed)
  • Application version: spotify_player 0.16.3
  • Application features: see buildlog

Additional context

This device has no sound connected. In the end it's meant to create a stream to another device that'll ultimately output the audio.

Originally created by @pepe82sh on GitHub (Jan 6, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/332 **Describe the bug** I've just installed Spotify-Player inside a freeBSD jail. It has been built with the default options. On calling `spotify_player` my it'll start rendering the "window" but then fails fatally creating a core dump. **To Reproduce** Install on FreeBSD and run. **Expected behavior** Application not crashing. **Log and backtrace** Core dump can be provided upon request. Buildlog: [spotify-player-0.16.3.buildlog.txt](https://github.com/aome510/spotify-player/files/13851564/spotify-player-0.16.3.buildlog.txt) **Screenshots** <img width="817" alt="Screenshot 2024-01-06 at 23 31 04" src="https://github.com/aome510/spotify-player/assets/35840364/cef97046-1669-4f89-bc80-55fbb01ed190"> **Environment** - OS: FreeBSD 13.2 (jailed) - Application version: spotify_player 0.16.3 - Application features: see buildlog **Additional context** This device has no sound connected. In the end it's meant to create a stream to another device that'll ultimately output the audio.
Author
Owner

@aome510 commented on GitHub (Jan 7, 2024):

Can you see any logs/backtraces in the .cache/spotify_player folder?

<!-- gh-comment-id:1880211593 --> @aome510 commented on GitHub (Jan 7, 2024): Can you see any logs/backtraces in the `.cache/spotify_player` folder?
Author
Owner

@aome510 commented on GitHub (Jan 16, 2024):

Hi any updates on this issue? Otherwise, I'll close it.

<!-- gh-comment-id:1893178418 --> @aome510 commented on GitHub (Jan 16, 2024): Hi any updates on this issue? Otherwise, I'll close it.
Author
Owner

@pepe82sh commented on GitHub (Jan 16, 2024):

Sorry, I was very sure I had sent an answer. The only thing I can see there is the core dump I was mentioning in the original ticket. It's a bit too big to add it to the ticket, but if anyone can use it I'm happy to figure out a way to provide the dump to someone working on it.

<!-- gh-comment-id:1893321151 --> @pepe82sh commented on GitHub (Jan 16, 2024): Sorry, I was very sure I had sent an answer. The only thing I can see there is the core dump I was mentioning in the original ticket. It's a bit too big to add it to the ticket, but if anyone can use it I'm happy to figure out a way to provide the dump to someone working on it.
Author
Owner

@aome510 commented on GitHub (Jan 17, 2024):

Can you send me the core dump to phamducthang1234@gmail.com? I can take a look to see if there is a problem.

Sorry, I was very sure I had sent an answer. The only thing I can see there is the core dump I was mentioning in the original ticket

Very weird because normally if you can spawn the UI window, there should be a log and backtrace created in the cache folder.

<!-- gh-comment-id:1895679735 --> @aome510 commented on GitHub (Jan 17, 2024): Can you send me the core dump to phamducthang1234@gmail.com? I can take a look to see if there is a problem. > Sorry, I was very sure I had sent an answer. The only thing I can see there is the core dump I was mentioning in the original ticket Very weird because normally if you can spawn the UI window, there should be a log and backtrace created in the cache folder.
Author
Owner

@Nafanya commented on GitHub (Jan 24, 2024):

Probably not related, but had similar issue -- in my case spotify_player just exited after a couple of seconds. The issue was an already running spotifyd instance. In the logs I had this error:

ERROR spotify_player: Encountered an error when running the application: Failed to initialize the Spotify data: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Used v0.16.3 on NixOS.

<!-- gh-comment-id:1907187460 --> @Nafanya commented on GitHub (Jan 24, 2024): Probably not related, but had similar issue -- in my case `spotify_player` just exited after a couple of seconds. The issue was an already running `spotifyd` instance. In the logs I had this error: ``` ERROR spotify_player: Encountered an error when running the application: Failed to initialize the Spotify data: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ``` Used v0.16.3 on NixOS.
Author
Owner

@miguelbarao commented on GitHub (Apr 16, 2024):

Maybe it's jail related?
Running on FreeBSD 14 outside a jail and it works perfectly.
Installed with pkg.

<!-- gh-comment-id:2059808031 --> @miguelbarao commented on GitHub (Apr 16, 2024): Maybe it's jail related? Running on FreeBSD 14 outside a jail and it works perfectly. Installed with `pkg`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#176
No description provided.