Summary: | Please make debugging easier | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Martin Steigerwald <Martin> |
Component: | daemon | 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: |
Description
Martin Steigerwald
2014-10-26 12:08:53 UTC
It would be good if users want to help with bug reporting do not have to go through this https://bugs.freedesktop.org/show_bug.cgi?id=85445#c2 and this https://bugs.freedesktop.org/show_bug.cgi?id=85445#c3 to just provide a (hopefully) usable debug log. Actual results: I had to search around for approaches of doing a PulseAudio debug log and none of them I found actually worked. Expected results: From a running desktop session I do: - something like pulseaudio-debug > file - reproduce the issue - Ctrl-C pulseaudio-debug - send the file along with the bug report I know this needs some implementation effort, but the core functionality for logging is already there. And it would save cost on bug reporting considerably. Killing PulseAudio daemon and restarting with debug option just didn´t work in a KDE session here. Maybe it works in other desktops tough. But if its supposed to work everywhere, then feel free to take this as a bug instead. But I don´t know how KDE would be special there. Yes, regarding to Phonon, the multimedia framework they use… but PlaneShift was using OpenAL directly so no Phonon there, but still didn´t play anything after I stopped the pulseaudio daemon started with the desktop session and start a debugging one. Also as wish: Some ducumentation on how to do debugging with PulseAudio. I am offering to at least add the hints how I managed to get a log with KDE session. Hmmm, okay, now I found KDE debugging information: For the second option, PA will need to be restarted for the changes in daemon.conf to take effect. A reboot is simplest, but running pulseaudio -k; start-pulseaudio-x11; start-pulseaudio-kde should also suffice. You can then grab the data from your syslog (as root) via grep pulseaudio /var/log/messages. Please try not to include unnecessary information and try and isolate the particular run that causes problems when including the debug log in bug reports. If you can, it would be great to annotate the log at particular points where some anomaly occurs. http://www.freedesktop.org/wiki/Software/PulseAudio/Desktops/KDE/ So at least it seems to be documented. To start PulseAudio with LANG=C in /usr/bin/start-pulseaudio-kde could help a bit with debugging, cause even the doc I quoted in previous comment would produce german logs on german language Debian setups. -- 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/539. |
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.