Bug 950868

Summary: KMix, KMixCtrl and kdeinit5 closed unexpectedly on login
Product: [openSUSE] openSUSE Distribution Reporter: Joachim Wagner <jo4su>
Component: KDE Workspace (Plasma)Assignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: forgotten_sM9JzehKpy, forgotten_XcZDXa8Cjf, wbauer
Version: Leap 42.1 RC1 1   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 42.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Joachim Wagner 2015-10-17 14:13:13 UTC 
In a fresh installation with Ext4 for / and XFS for /home (both with mount option noatime), the KDE crash handler greats on login with "We are sorry, KMix closed unexpectedly" and often same message for KMixCtrl and/or kdeinit5.

Running in a VM (KVM/qemu) with 2.4 GB RAM (host has 16 GB and runs OpenSUSE 13.1).

Number of crash reports seems to be lower but not zero if I leave the VM monitor window closed while the VM boots and autologins.

This problem wasn't there in Beta 1.

 - JJ
Comment 1 Forgotten User sM9JzehKpy 2015-10-17 14:23:53 UTC 
Marked as duplicate.

*** This bug has been marked as a duplicate of bug 950487 ***
Comment 2 Forgotten User XcZDXa8Cjf 2015-10-21 07:28:47 UTC 
I changed from Beta1 to RC1 and then after login the KDE crash handler says:"Es tut uns sehr leid, das Programm kdeinit5 wurde unerwartet beendet. Sie können diesen Fehler nicht melden, da die Anwendung kdeinit5 keine Adresse zum Melden von Fehlern angibt.
Details: Ausführbare Datei kdeinit5 PID 6619 Signal: Segmentation fault (11) Datum: 21.10.15 08:38:09"
Also, when I try to start Amarok, this program doesn't start with the same error.
Comment 3 Wolfgang Bauer 2015-10-21 11:38:33 UTC 
This still sounds like a duplicate.
The fix is not in Leap yet, but should be in the final release.

Use the workaround mentioned in the other bug report, and only reopen this one if it doesn't help.

I.e.:
Could you try to disable it, e.g. modifying in /etc/pulse/default.pa to replace the line

load-module module-native-protocol-unix

with

load-module module-native-protocol-unix srbchannel=no

*** This bug has been marked as a duplicate of bug 950487 ***