Pulseaudio causing major slow down on almost all apps & mate-panel crashed with SIGABRT in g_assertion_message()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mate-panel (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
i've been experiencing major slow down of almost all menu and some apps like galculator for example. Multiple calls to pulseaudio seems to be the problem.
echo autospawn = no > $HOME/.
fixed the issue without me having to actually kill pulseaudio so i suppose it is crashing on its own
it may be important to note that i'm running a custom kernel right now because my sound card is not supported yet, see bug: https:/
i have done a trace along with galculator since it seemed to be more affected than the others will post the results.. sorry about the size, its the first time i do this... no idea what calls to include or not in the trace...
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: mate-panel 1.12.1-1
Uname: Linux 4.5.0-rc1-custom x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Thu Feb 11 18:57:44 2016
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2016-02-01 (10 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127.1)
ProcCmdline: mate-panel
Signal: 6
SourcePackage: mate-panel
StacktraceTop:
g_assertion_
g_assertion_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: mate-panel crashed with SIGABRT in g_assertion_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo tracing
XsessionErrors:
mate-session[
(nm-applet:1927): Gdk-CRITICAL **: gdk_window_
(blueman-
(tilda:1939): Gtk-WARNING **: Attempting to read the recently used resources file at '/home/
(mate-panel:1885): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/
information type: | Private → Public |
by the way, the trace was before the crash happened, when i figured pulseaudio was the culprit i turned it off once and it did fix my porblem. i turned it back on to be sure and the problem started again immediatly. once i finally turned it back off, this is when i got the crash.