starred/librespot
1
0
Fork 0
mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00
Code Issues 95 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1290] Librespot starts spamming the new status of the song #591

New issue
Closed
opened 2026-02-27 19:31:25 +03:00 by kerem · 5 comments
kerem commented 2026-02-27 19:31:25 +03:00
Owner
Copy link

Originally created by @fabirednik on GitHub (Jun 1, 2024).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1290

Describe the bug
After listening to music for x amount of time, Librespot starts spamming the new status of the song, which causes interruptions in the music and a bugging progress bar on Spotify.

Log
Jun 01 14:41:02 rednikbox bash[1838]: [2024-06-01T12:41:02Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay
Jun 01 14:41:02 rednikbox bash[1838]: [2024-06-01T12:41:02Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay]
Jun 01 14:41:06 rednikbox bash[1838]: [2024-06-01T12:41:06Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay
Jun 01 14:41:06 rednikbox bash[1838]: [2024-06-01T12:41:06Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay]
Jun 01 14:41:10 rednikbox bash[1838]: [2024-06-01T12:41:10Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay
Jun 01 14:41:10 rednikbox bash[1838]: [2024-06-01T12:41:10Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay]
Jun 01 14:41:13 rednikbox bash[1838]: [2024-06-01T12:41:13Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay
Jun 01 14:41:13 rednikbox bash[1838]: [2024-06-01T12:41:13Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay]
Jun 01 14:41:17 rednikbox bash[1838]: [2024-06-01T12:41:17Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay
Jun 01 14:41:17 rednikbox bash[1838]: [2024-06-01T12:41:17Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay]

Host (what you are running librespot on):

  • OS: Linux
  • Platform: Raspberry pi zero

Additional context
Restart helps, but not for long, now maybe this is my 5th such case, and I've been using librespot since yesterday

Originally created by @fabirednik on GitHub (Jun 1, 2024). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1290 **Describe the bug** After listening to music for x amount of time, Librespot starts spamming the new status of the song, which causes interruptions in the music and a bugging progress bar on Spotify. **Log** Jun 01 14:41:02 rednikbox bash[1838]: [2024-06-01T12:41:02Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay Jun 01 14:41:02 rednikbox bash[1838]: [2024-06-01T12:41:02Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay] Jun 01 14:41:06 rednikbox bash[1838]: [2024-06-01T12:41:06Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay Jun 01 14:41:06 rednikbox bash[1838]: [2024-06-01T12:41:06Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay] Jun 01 14:41:10 rednikbox bash[1838]: [2024-06-01T12:41:10Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay Jun 01 14:41:10 rednikbox bash[1838]: [2024-06-01T12:41:10Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay] Jun 01 14:41:13 rednikbox bash[1838]: [2024-06-01T12:41:13Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay Jun 01 14:41:13 rednikbox bash[1838]: [2024-06-01T12:41:13Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay] Jun 01 14:41:17 rednikbox bash[1838]: [2024-06-01T12:41:17Z TRACE librespot_connect::spirc] ==> kPlayStatusPlay Jun 01 14:41:17 rednikbox bash[1838]: [2024-06-01T12:41:17Z TRACE librespot_connect::spirc] Sending status to server: [kPlayStatusPlay] **Host (what you are running `librespot` on):** - OS: Linux - Platform: Raspberry pi zero **Additional context** Restart helps, but not for long, now maybe this is my 5th such case, and I've been using librespot since yesterday
kerem 2026-02-27 19:31:25 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-27 19:31:26 +03:00
Author
Owner
Copy link

@roderickvd commented on GitHub (Aug 21, 2024):

Please provide a full debug log.

<!-- gh-comment-id:2302897660 --> @roderickvd commented on GitHub (Aug 21, 2024): Please provide a full debug log.
kerem commented 2026-02-27 19:31:26 +03:00
Author
Owner
Copy link

@fabirednik commented on GitHub (Aug 21, 2024):

Please provide a full debug log.

There is nothing else about the problem in the logs

<!-- gh-comment-id:2302957966 --> @fabirednik commented on GitHub (Aug 21, 2024): > Please provide a full debug log. There is nothing else about the problem in the logs
kerem commented 2026-02-27 19:31:26 +03:00
Author
Owner
Copy link

@roderickvd commented on GitHub (Aug 21, 2024):

Still, I'd like to see it. Without it, it is anyway unactionable and I will have to close this issue.
Do let me know when you've further isolated it.

From the issue template:

**Log**
A full log so we may trace your problem (launch `librespot` with `--verbose`). Format the log as code.
<!-- gh-comment-id:2302961771 --> @roderickvd commented on GitHub (Aug 21, 2024): Still, I'd like to see it. Without it, it is anyway unactionable and I will have to close this issue. Do let me know when you've further isolated it. From the issue template: ``` **Log** A full log so we may trace your problem (launch `librespot` with `--verbose`). Format the log as code. ```
kerem commented 2026-02-27 19:31:26 +03:00
Author
Owner
Copy link

@fabirednik commented on GitHub (Aug 21, 2024):

Still, I'd like to see it. Without it, it is anyway unactionable and I will have to close this issue.
Do let me know when you've further isolated it.

From the issue template:

**Log**
A full log so we may trace your problem (launch `librespot` with `--verbose`). Format the log as code.

Please reopen this issue, I will send logs in few days, now i'm not at home

Edit:
btw, I wonder if it will work, because usually the problem occurs after a few hours of listening, I don't know if the full log will fit

<!-- gh-comment-id:2302966816 --> @fabirednik commented on GitHub (Aug 21, 2024): > Still, I'd like to see it. Without it, it is anyway unactionable and I will have to close this issue. > Do let me know when you've further isolated it. > > From the issue template: > > ``` > **Log** > A full log so we may trace your problem (launch `librespot` with `--verbose`). Format the log as code. > ``` Please reopen this issue, I will send logs in few days, now i'm not at home Edit: btw, I wonder if it will work, because usually the problem occurs after a few hours of listening, I don't know if the full log will fit
kerem commented 2026-02-27 19:31:26 +03:00
Author
Owner
Copy link

@fabirednik commented on GitHub (Aug 21, 2024):

@roderickvd

<!-- gh-comment-id:2302980774 --> @fabirednik commented on GitHub (Aug 21, 2024): @roderickvd
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
v0.8.0
v0.7.1
v0.7.0
v0.6.0
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.0
v0.1.6
v0.1.5
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
A-Alsa

   
SpotifyAPI

   
Tokio 1.0

   
audio

   
bug

   
can't reproduce

   
compilation

   
dependencies

   
duplicate

   
enhancement

   
good first issue

   
help wanted

   
high priority

   
imported

   
imported

   
invalid

   
new api

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
reverse engineering

   
wiki

   
wontfix
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/librespot#591
No description provided.