Bug 293043 - Doesn't store microphone levels and recording levels when using Gstreamer.(actually the same with Xine backend)
Summary: Doesn't store microphone levels and recording levels when using Gstreamer.(ac...
Status: RESOLVED FIXED
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: 4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
: 294290 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-02-01 12:54 UTC by Roman
Modified: 2014-07-12 11:04 UTC (History)
17 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 Roman 2012-02-01 12:54:27 UTC
Version:           4 (using KDE 4.8.0) 
OS:                Linux

After restart KMix volume levels dropped. Recording levels and so on are restored as "0"(off).

Reproducible: Always

Steps to Reproduce:
Set any voluve levels for recording. Select Gstreamer backend as preffered. Restart computer. Recording levels(microphone and so on will be "0").

Actual Results:  
Set any voluve levels for recording. Select Gstreamer backend as preffered. Restart computer. Recording levels(microphone and so on will be "0").

Expected Results:  
On previous version of KDE(4.7.4) levels were saved and restored.

Using OpenSuSE 12.1 RPMs. Kernel version 3.2.2. Hope, that's enough information.
Comment 1 Carlos Alberto Espinal 2012-02-01 15:18:28 UTC
Same occurs with KDE 4.8 in Kubuntu 11.10.
Comment 2 Roman 2012-02-01 18:35:00 UTC
One more note. Just a few minutes ago, KMix stalled(stopped responding) when tried to change volume... And finaly crashed with an error.
Comment 3 Roman 2012-02-06 07:21:12 UTC
Are any fixes coming?
Comment 4 Vasyl Demin 2012-02-08 19:01:56 UTC
Same on Arch Linux x86_64, KDE 4.8.0
Comment 5 Roman 2012-02-08 21:09:48 UTC
Seems that's global bug. Strange, that developers do not react at all... bug report is being ignored.
Comment 6 fxeon 2012-02-19 08:32:52 UTC
Same here on Arch x86_64

workaround: revert to 4.7.4-1
only a workaround of course.
Comment 7 Jekyll Wu 2012-02-19 11:16:52 UTC
*** Bug 294290 has been marked as a duplicate of this bug. ***
Comment 8 Roman 2012-02-20 03:17:09 UTC
(In reply to comment #6)
> Same here on Arch x86_64
> 
> workaround: revert to 4.7.4-1
> only a workaround of course.

Yes, you're right. You just need to remember, that any KDE version *.*.0 up to *.*.3 is unstable trash. Max it deserves to be called - Beta3 or RC1. Even *.*.4 releases always have unfixed bugs.
Comment 9 Alberto Gonzalez 2012-02-28 17:02:35 UTC
Same problem here with Arch Linux and KDE 4.8.0. Every time I log in I have to open Kmix and restore the volume of the "Digital" channel so that my mic works and I can use Skype. With 4.7.4 it was working correctly.
Comment 10 Roman 2012-02-28 18:13:14 UTC
(In reply to comment #9)
> Same problem here with Arch Linux and KDE 4.8.0. Every time I log in I have to
> open Kmix and restore the volume of the "Digital" channel so that my mic works
> and I can use Skype. With 4.7.4 it was working correctly.

Yeah, that's the way it is. Sad to see, that this bug report is being ignored by developers
Comment 11 wazyk 2012-02-29 13:04:26 UTC
Same on Arch Linux x86_64, KDE 4.8.0, Lenovo Thinkpad E520 ==> Pb with internal mic. Not tested with external mic.

Is it alsa or kmix problem ?
Comment 12 Alberto Gonzalez 2012-02-29 13:12:03 UTC
(In reply to comment #11)
> Is it alsa or kmix problem ?

It is Kmix or some other KDE component. Before logging into KDE the alsa levels are correctly restored, but when KDE starts some channels are muted. Even if you turn the volume up again manually and log out and in again into KDE the channels are muted again.
Comment 13 wazyk 2012-02-29 13:16:03 UTC
Forgot to mention that I use gstreamer Phonon backend.
Comment 14 Flavio 2012-03-04 19:21:17 UTC
The same problem occurs on Gentoo Linux with kernels 3.2.9 and 3.2.6, and KDE 4.8.0.

Please fix it.
Comment 15 Peter 2012-03-07 21:22:52 UTC
I experience the same bug with the VLC backend, on Archlinux.
Comment 16 Flavio 2012-03-07 21:43:55 UTC
The problem is that the "Digital" slider in alsamixer (Capture) is always decreased to zero. Restoring it, solves the problem. I don't understand if the cause is KDE or alsa.
Comment 17 Alberto Gonzalez 2012-03-07 23:49:26 UTC
(In reply to comment #16)
> The problem is that the "Digital" slider in alsamixer (Capture) is always
> decreased to zero. Restoring it, solves the problem. I don't understand if
> the cause is KDE or alsa.

Yes, I have that same problem, "Digital" channel is set to zero each time I log in. The problem is in KDE, not in ALSA.

Tried KDE 4.8.1 and the problem is still present.
Comment 18 Flavio 2012-03-08 08:56:55 UTC
(In reply to comment #17)
> Yes, I have that same problem, "Digital" channel is set to zero each time I
> log in. The problem is in KDE, not in ALSA.
Yes, I am convinced of that too now.

> 
> Tried KDE 4.8.1 and the problem is still present.
Oh no! Unbelievable. :(
Comment 19 Flavio 2012-03-08 10:23:44 UTC
I've found a possible workaround for the moment.

The following command could be put in the Autostart KDE directory, in order to restore the Digital slider at the desired value.
For instance, I prefer 81%, and this is the command to do that:

amixer -c 0 set Digital 25dB

Could you try if this works? For me yes (but I haven't tryed to reboot with this script enabled at boot yet).
Comment 20 Flavio 2012-03-14 11:59:52 UTC
(In reply to comment #19)
> I've found a possible workaround for the moment.
> 
> The following command could be put in the Autostart KDE directory, in order
> to restore the Digital slider at the desired value.
> For instance, I prefer 81%, and this is the command to do that:
> 
> amixer -c 0 set Digital 25dB
By the way, this workaround works great for me!

Enjoy!
Comment 21 Daimonion 2012-03-27 20:56:10 UTC
*** This bug has been confirmed by popular vote. ***
Comment 22 Daimonion 2012-03-27 22:19:54 UTC
The problem appears to be in kmixctrl if you try to load mixer settings with "kmixctrlc -r". My first guess the problem is somewhere in Mixer::volumeLoad function from mixer.cpp.

The following workaround works for me:

 * login to your KDE
 * using Kmix mixer set desired mixer values
 * run in console: `kmixctrl -s` to save your settings
 * UNCHECK option in Kmix -> Settings -> Configure Kmix -> Restore volumes upon login
 * Edit file /usr/share/autostart/restore_kmix_volumes.desktop replacing on line 3 (X-KDE-autostart-condition=kmixrc:Global:startkdeRestore:true) "true" with "false"
 * save file, logout, log back in
Comment 23 André Fettouhi 2012-04-07 09:21:14 UTC
Bug is still present in KDE SC 4.8.2 on Arch Linux 64 bit.
Comment 24 Alberto Gonzalez 2012-04-07 09:25:07 UTC
(In reply to comment #23)
> Bug is still present in KDE SC 4.8.2 on Arch Linux 64 bit.

Easiest workaround is to disable the option in kmix to restore volumes on login. Arch Linux stores the alsa levels and restores them on every boot anyway.
Comment 25 André Fettouhi 2012-04-07 09:28:02 UTC
(In reply to comment #24)
> (In reply to comment #23)
> > Bug is still present in KDE SC 4.8.2 on Arch Linux 64 bit.
> 
> Easiest workaround is to disable the option in kmix to restore volumes on
> login. Arch Linux stores the alsa levels and restores them on every boot
> anyway.

I did Mladen's proposed workaround and that works for me :).
Comment 26 Martux 2012-04-09 01:03:00 UTC
(In reply to comment #25)
> (In reply to comment #24)
> > (In reply to comment #23)
> > > Bug is still present in KDE SC 4.8.2 on Arch Linux 64 bit.
> > 
> > Easiest workaround is to disable the option in kmix to restore volumes on
> > login. Arch Linux stores the alsa levels and restores them on every boot
> > anyway.
> 
> I did Mladen's proposed workaround and that works for me :).

That works for me too. Nasty. I mean, someone changed the behaviour between 4.7.3 and 4.7.4 release clearly, annoying a lot of people. So what is the deal of just restoring the old behaviour? That is so typical for OS projects, that's why they sometimes suck...
Comment 27 Torrie Fischer 2012-05-17 19:39:24 UTC
(In reply to comment #26)
> (In reply to comment #25)
> > (In reply to comment #24)
> > > (In reply to comment #23)
> > > > Bug is still present in KDE SC 4.8.2 on Arch Linux 64 bit.
> > > 
> > > Easiest workaround is to disable the option in kmix to restore volumes on
> > > login. Arch Linux stores the alsa levels and restores them on every boot
> > > anyway.
> > 
> > I did Mladen's proposed workaround and that works for me :).
> 
> That works for me too. Nasty. I mean, someone changed the behaviour between
> 4.7.3 and 4.7.4 release clearly, annoying a lot of people. So what is the
> deal of just restoring the old behaviour? That is so typical for OS
> projects, that's why they sometimes suck...

The two commits between 4.7.3 and 4.7.4 didn't change anything related to this. Thats why this is hard to track down. It is being worked on now though.
Comment 28 Alberto Gonzalez 2012-05-17 22:43:19 UTC
> The two commits between 4.7.3 and 4.7.4 didn't change anything related to
> this. Thats why this is hard to track down. It is being worked on now though.

But the problem was not introduced between 4.7.3 and 4.7.4, the problem appeared in 4.8.0.

Thanks for looking into it.
Comment 29 Daniel Duris 2012-06-01 09:27:56 UTC
Plus it crashes a lot.
Comment 30 Christian Esken 2012-08-14 07:12:30 UTC
Fixed on Tue, 03 Jul 2012 for KDE4.9.0:

http://quickgit.kde.org/index.php?p=kmix.git&a=commit&h=1137eacf33158b55f8361d2f2ccf8ea0f0d478e7
Comment 31 Christian Esken 2012-08-14 07:14:58 UTC
Fixed during the Summer 2012 bugfix run.
Comment 32 jens 2014-07-12 11:04:36 UTC
This bug seems to exist still on KDE 4.12.5 on Gentoo. If I remember correctly, it existed in  all versions since 4.8.0 .
Is there maybe a problem with distros which restore alsa settings before? 
Here it affected not only recording levels, but all settings including output select (line-out, headphone)  etc.

The proposed fix from Comment 22 works fine for all problems and for the first time my settings don't move anymore, even after a reboot