| Summary: | Pulseaudio fails to start with network down | ||
|---|---|---|---|
| Product: | PulseAudio | Reporter: | muesli4 |
| Component: | modules | Assignee: | pulseaudio-bugs |
| Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | lennart |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | A log file from pulseaudio. | ||
It seems to be module-rtp-recv that fails: ( 0.486| 0.027) I: [pulseaudio] module-rtp-recv.c: Joining mcast group failed: No such device ( 0.487| 0.000) E: [pulseaudio] module.c: Failed to load module "module-rtp-recv" (argument: ""): initialization failed. ( 0.487| 0.000) E: [pulseaudio] main.c: Module load failed. ( 0.487| 0.000) E: [pulseaudio] main.c: Failed to initialize daemon. If you don't need RTP, then the obvious workaround is to not load that module. If you want to keep the module in your configuration but ignore errors, you can use the .nofail and .fail directive in default.pa: .nofail load-module module-rtp-recv .fail It would be good if module-rtp-recv could detect when the network becomes available. Patches welcome. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/95. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 127823 [details] A log file from pulseaudio. I'm using module-native-protocol-tcp and module-zeroconf-publish. Everything is working absolutely perfect as long as a network cable is connected on startup. My guess is that one or both of those modules cause pulseaudio to fail starting. I would expect it to at least ignore any failures of those modules on startup (that may be my fault with a wrong configuration on my side). Optionally, the module should reconnect once a connection is there.