[PR #1000] [MERGED] Bump libmdns to 0.7 #1180

New issue

Closed

opened 2026-02-27 20:01:28 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:01:28 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/librespot-org/librespot/pull/1000
Author: @Gnarflord
Created: 5/19/2022
Status: ✅ Merged
Merged: 5/19/2022
Merged by: @roderickvd

Base: dev ← Head: dev

📝 Commits (1)

10c9a0f Use libmdns 0.7 to avoid packet 47 error

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 discovery/Cargo.toml (+1 -1)

📄 Description

On my machine I'm getting spammed with warnings of this type:

[2022-05-19T16:56:38Z WARN  libmdns::fsm] couldn't parse packet from 192.168.178.112:5353: type 47 is invalid
[2022-05-19T16:56:45Z WARN  libmdns::fsm] couldn't parse packet from 192.168.178.114:5353: type 47 is invalid
[2022-05-19T16:56:45Z WARN  libmdns::fsm] couldn't parse packet from 192.168.178.28:5353: type 47 is invalid

This is because some devices in my network use mDNS to talk to each other, broadcasting messages to other mDNS devices like the machine running librespot. But this packet type 47 hasn't been implemented in libmdns, so the warning is printed.

As I use librespot as a systemd daemon all those messages end up in my journal and accumulate to >1000 warning per day. This warning has been fixed 11 days ago in libmdns (see https://github.com/librespot-org/libmdns/issues/19).

I've locally compiled with the new libmdns version 0.7 instead of 0.6 and the messages disappear, so the bug seems to be resolved

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/librespot-org/librespot/pull/1000 **Author:** [@Gnarflord](https://github.com/Gnarflord) **Created:** 5/19/2022 **Status:** ✅ Merged **Merged:** 5/19/2022 **Merged by:** [@roderickvd](https://github.com/roderickvd) **Base:** `dev` ← **Head:** `dev` --- ### 📝 Commits (1) - [`10c9a0f`](https://github.com/librespot-org/librespot/commit/10c9a0f8eab743a2d59268eed0a2eac53a270ab8) Use libmdns 0.7 to avoid packet 47 error ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `discovery/Cargo.toml` (+1 -1) </details> ### 📄 Description On my machine I'm getting spammed with warnings of this type: ``` [2022-05-19T16:56:38Z WARN libmdns::fsm] couldn't parse packet from 192.168.178.112:5353: type 47 is invalid [2022-05-19T16:56:45Z WARN libmdns::fsm] couldn't parse packet from 192.168.178.114:5353: type 47 is invalid [2022-05-19T16:56:45Z WARN libmdns::fsm] couldn't parse packet from 192.168.178.28:5353: type 47 is invalid ``` This is because some devices in my network use mDNS to talk to each other, broadcasting messages to other mDNS devices like the machine running librespot. But this packet type 47 hasn't been implemented in libmdns, so the warning is printed. As I use librespot as a systemd daemon all those messages end up in my journal and accumulate to >1000 warning per day. This warning has been fixed 11 days ago in libmdns (see [https://github.com/librespot-org/libmdns/issues/19](https://github.com/librespot-org/libmdns/issues/19)). I've locally compiled with the new libmdns version 0.7 instead of 0.6 and the messages disappear, so the bug seems to be resolved --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-27 20:01:28 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-02-27 20:01:47 +03:00

[PR #1180] Add Resampling Support #1266

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/librespot#1180

No description provided.

Rows
Columns