Bug 156505 - Kmix is crashing on KDEmod startup...
Summary: Kmix is crashing on KDEmod startup...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
: 159645 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-23 21:06 UTC by Julian Cvetkov
Modified: 2009-05-10 18:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Cvetkov 2008-01-23 21:06:28 UTC
Version:           2.6.1 (using KDE 3.5.8)
Installed from:    Unlisted Binary Package
Compiler:          gcc version 4.2.2 Thread model: posix
OS:                Linux

Kmix version 2.6.1 using KDEmod 3.5.8 is crashing at system startup...It`s not happening on all KDEmod startups ,but it`s often...
After the crash I run Kmix and is loading & operating quite normal..

Here is the debug trace...
--------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb69c2a80 (LWP 6755)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7f9c410 in __kernel_vsyscall ()
#7  0xb6be8dc5 in raise () from /lib/libc.so.6
#8  0xb6bea6a1 in abort () from /lib/libc.so.6
#9  0xb6be211e in __assert_fail () from /lib/libc.so.6
#10 0xb66303f5 in snd_hctl_handle_events () from /usr/lib/libasound.so.2
#11 0xb663bc61 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
#12 0xb67692ad in Mixer_ALSA::prepareUpdateFromHW ()
   from /opt/kde/lib/libkdeinit_kmix.so
#13 0xb676b38b in Mixer::readSetFromHW () from /opt/kde/lib/libkdeinit_kmix.so
#14 0xb67699a3 in Mixer::qt_invoke () from /opt/kde/lib/libkdeinit_kmix.so
#15 0xb722690d in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3
#16 0xb75496ce in QSignal::signal () from /opt/qt/lib/libqt-mt.so.3
#17 0xb72420a7 in QSignal::activate () from /opt/qt/lib/libqt-mt.so.3
#18 0xb7249153 in QSingleShotTimer::event () from /opt/qt/lib/libqt-mt.so.3
#19 0xb71c8eaa in QApplication::internalNotify ()
   from /opt/qt/lib/libqt-mt.so.3
#20 0xb71c99a6 in QApplication::notify () from /opt/qt/lib/libqt-mt.so.3
#21 0xb78e1082 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4
#22 0xb71be24e in QEventLoop::activateTimers () from /opt/qt/lib/libqt-mt.so.3
#23 0xb7178db4 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3
#24 0xb71df520 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3
#25 0xb71df3b6 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3
#26 0xb71c890f in QApplication::exec () from /opt/qt/lib/libqt-mt.so.3
#27 0xb6768b36 in kdemain () from /opt/kde/lib/libkdeinit_kmix.so
#28 0xb77225d4 in kdeinitmain () from /opt/kde/lib/kde3/kmix.so
#29 0x0804e525 in launch ()
#30 0x0804ec41 in handle_launcher_request ()
#31 0x0804f0f0 in handle_requests ()
#32 0x0804fb4a in main ()
Comment 1 Christian Esken 2008-01-23 23:13:33 UTC
This looks more like an ALSA bug: From the stack trace I see an assertion failure in snd_hctl_handle_events(), which is an ALSA library function. Thus it's probably a better idea to report this at the ALSA bugtracker. Also I had once another bug report like this, which was fixed by upgrading the ALSA driver.
Comment 2 Julian Cvetkov 2008-01-23 23:18:49 UTC
But the ALSA is working fine. No recived errors from any alsa libs ,all ot the sound system functions are working fine and with no problems.
Between this i update my ALSA-driver many times and also recompiled from source becouse I`m using ARCHlinux with pacman package system ,but the bug exist from the installation to present.
Comment 3 Christian Esken 2008-01-23 23:39:08 UTC
Currently I have no idea, because the corresponding code hasn't been tocuhe for over a year.
But bugs creep in ALSA from time to time. See bug 105079 and bug 101870 for references where upgrading or downgrading ALSA fixed or partially fixed the issue. Also people report that ALSA has sometimes trouble if it is used immeditely after loading a soundcard kernel module (which can happen during startup).

It is also possible that the KDEMod maintainers managed to undo my patch as described in comment 5 of bug 105079 . It's hard to tell, because KDEmod (as the name tells) uses modified KDE code.

In any case (it might help):
----------------------------
Please post the ouput of "amixer" (or "amixer -c 1" or any other number that corresponds to the affected soundcard).

Please also report if other mixers work (e.g. alsamixer).

Please also post the permissions of your sound card devices, using
 getfacl /dev/snd/controlC0  (or controlC1 or any other number that corresponds to the affected soundcard).


Comment 4 Julian Cvetkov 2008-01-24 00:06:13 UTC
Here is the output from 'amixer' version 1.0.15 and just for info my sound dev.
ATI Technologies Inc SBx00 Azalia
-------------------------------------
Simple mixer control 'Master',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [0.00dB] [on]
  Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 15
  Front Left: Capture 0 [0%] [0.00dB] [off]
  Front Right: Capture 0 [0%] [0.00dB] [off]
Simple mixer control 'Capture Mux',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 4
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Digital',0
  Capabilities: cvolume
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 120
  Front Left: Capture 60 [50%] [0.00dB]
  Front Right: Capture 60 [50%] [0.00dB]
Simple mixer control 'Input Source',0
  Capabilities: cenum
  Items: 'Mic'
  Item0: 'Mic'
------------------
alsamixer is working fine at any time ,under X 'KDEmod' & multiuser shell...
------------------
The output from getfacl 2.2.45
------------------
# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
group::rw-
other::---

My user for X is in audio group...
Comment 5 Julian Cvetkov 2008-01-25 18:27:38 UTC
What are yours suggestions about this ?
Should I report this bug to ArchLinux community or wait for yours comments ?
Could I post any information for this issue that can help to you guys ?
I only want to say that the problem exist and under KDE 3.5.8, not KDEmod only...

Comment 6 Jan Mette 2008-01-25 21:42:19 UTC
Hi there,

i am one of the KDEmod packagers. We have added only one patch to KMix, this one:

http://www.kde-apps.org/content/show.php?content=51691

I guess the patch is not the culprit for the crash...

Julian, which kernel are you running? I have experienced some troubles with alsa when using a customized kernel like -kamikaze or -zen...
Comment 7 Christian Esken 2008-01-25 23:54:32 UTC
Julian,

I see three possible ways to resolve this:

1) File a bug report at ALSA
Actually I do consider this to be a bug in ALSA, as the called ALSA function produces an assertion failure, which it should never do under normal circumstances. This function should return a "negative error code on failure" as documented on http://www.alsa-project.org/alsa-doc/alsa-lib/group___mixer.html#ga5d17a7d0e70b4c198fcf9d23e6b8514

2) You could create a debuggable version (e.g. compile KMix yourself, with debugging enabled), and try to get it crashed while running Kmix in a debugger.

3) While running KMix, run another mixer (e.g. alsamixer), and try to change all controls, until KMix crashes.


-----------------


As a side note the output you posted looks fine, except for one control:

Simple mixer control 'Input Source',0 
   Capabilities: cenum 
   Items: 'Mic' 
   Item0: 'Mic' 

I have never seen the capability "cenum" before. My guess is that this is "capture enumeration". It is also a very "stupid" enum, as it has only one possible value.

Comment 8 Christian Esken 2008-05-18 19:35:18 UTC
I really have not an idea what could be the reason here. It is VERY unlikely that I will be able to find that without the possibility to reproduce it, or to get a usable stack trace.
As KDE4 is out for some time I won't fix this in KDE3. Sorry, but I simply see no chane how to do that.
Closing unresolved (sigh!).
Comment 9 Christian Esken 2008-05-18 19:48:45 UTC
Hmmm, one more bug report like this. Lets reopen.
Comment 10 Christian Esken 2008-05-18 19:53:45 UTC
One more idea: Please check whetehr it also happens when you disable the KMix volume restauration?
Comment 11 Christian Esken 2008-05-18 19:54:13 UTC
*** Bug 159645 has been marked as a duplicate of this bug. ***
Comment 12 Julian Cvetkov 2008-05-18 23:27:45 UTC
Hello there.
I use kernel 2.6.24-ARCH #1 SMP PREEMPT
This is the output of 'uname -a' ...I`m not using custom kernel compiled
from me...
I can give to you more info about handling the hole
KDEmod-kdemultimedia-kmix...It is strange that the problems reproduce not in
every boot up of KDE mod using (kdm)...


Hello there.<br>I use kernel 2.6.24-ARCH #1 SMP PREEMPT<br>This is the output of &#39;uname -a&#39; ...I`m not using custom kernel compiled from me...<br>I can give to you more info about handling the hole KDEmod-kdemultimedia-kmix...It is strange that the problems reproduce not in every boot up of KDE mod using (kdm)...<br>
<br clear="all"><br>-- <br>In a world without walls, who need Windows? 
Comment 13 Julian Cvetkov 2008-05-19 01:08:37 UTC
When I mute the 'master' in my kMix in all boots kmix is loading well, with no problems ,with no crashes.
I`m using 2.6.24-ARCH #1 SMP PREEMPT kernel...The stock from pacman (ArchLinux)...
Strange ,hu ?
Comment 14 Christian Esken 2009-05-10 18:37:54 UTC
Very straange. And very interesting that this only happens in Arch / KDEmod. Looks very much like a downstream problem (Downstream => KDEMod). thus I think I can't help you here.

I will close this bug report. If you find another distribution with the problem, please let me know.

Downstream => KDEMod / Arch