https://bugs.freedesktop.org/show_bug.cgi?id=58758
--- Comment #10 from Matthew Cope <[email protected]> --- (In reply to comment #9) > Do you edit these logs before you send them? According to the logs, your > machine-id is ${my_machine-id} and only four modules are loaded during > startup: module-device-restore, module-stream-restore, module-card-restore > and module-augment-properties. There's no sign of any ALSA modules getting > loaded, despite there being log messages from an ALSA sink. Also, it looks > like the log level is "info", not "debug" as instructed. Yes, I wasn't sure if machine-id value is sensitive from a security POV, so I have edited it out - if it isn't then I won't bother in future :-) I logged in and out a few times to check if there was still the delay and so the messages repeated a few times - I tried to cut it down to what looked like only one login event but I might have pruned a bit too much! The log level is definitely 'debug'. I'm getting the log by grepping /var/log/messages for pulseaudio. Looking at the log file now there are lines like: May 6 16:42:04 debian pulseaudio[7281]: (6648.654| 0.000) [alsa-sink] alsa-sink.c: Device suspended... So I must have messed up the debug log; I'll give it another go. > You could also try adding module-x11-xsmp back to start-pulseaudio-x11 and > commenting out module-x11-cork-request and/or module-x11-publish instead. > The idea would be to find out if one of the modules loaded by > start-pulseaudio-x11 causes the delay. Ok, will do. Thanks for the feedback. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
