Bug 99826 - crash after connecting second monitor
Summary: crash after connecting second monitor
Status: RESOLVED WORKSFORME
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-15 14:11 UTC by laurie
Modified: 2017-02-17 05:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
crash report (8.38 KB, text/plain)
2017-02-15 14:11 UTC, laurie
Details

Description laurie 2017-02-15 14:11:28 UTC
Created attachment 129637 [details]
crash report

second monitor ok until login, then both monitors go black
Comment 1 Tanu Kaskinen 2017-02-16 08:24:55 UTC
Does syslog (or wherever ksmserver puts its log output) have any messages containing the word "Assertion"? The crash seems to be an assertion failure in libpulsecommon.

Can you install the debug symbols for libpulse and libpulse-glib-mainloop? Without the debug symbols the backtrace doesn't show the exact location of the crash.
Comment 2 laurie 2017-02-17 04:39:12 UTC
Yast control centre, miscellaneous, System log shows no file found. cannot find ksmserver log

libpulse-mainloop-glib0 & libpulse-mainloop-glib0-debuginfo found in repositories and now installed.

updated to latest tumbleweed kernel 4.9.9.12 today. pulse audio crash cannot be repeated and all monitors are now working correctly
Comment 3 Tanu Kaskinen 2017-02-17 05:46:58 UTC
Ok, since this can't be reproduced any more, I'll close the bug.


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.