| Summary: | [usability] no sound due to faulty presets | ||
|---|---|---|---|
| Product: | [Applications] kmix | Reporter: | Kenobi <kazmirzak> |
| Component: | general | Assignee: | Christian Esken <esken> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | francescortiz |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Kenobi
2008-05-10 20:14:27 UTC
I have an irc report of someone that hit that in a gentoo build from trunk, so apparently I'm wrong in thinking it's a distro thing. It seems kind of nasty usability-wise, so I'm adding that tag. Does it also happen when you disable sound restoration in KMix. For testing: 1) Disable sound restoration in KMix's configuration dialog. 2) Set reasonable sound levels 3) Reboot machine and login again. Yes, when I set reasonable sound levels then it works, of course. This post is about Ubuntu delivering Linux with unreasonable sound levels. This WILL be a problem for thousands of novices. OK, then this is an issue of Ubuntu. Please report it there, as KMix is not responsible for setting reasonable volume levels. The distribution (really!) has to do that. So did I understand you correct, that it is independent from KMix's sound restoration? Without further investigations I dare to say that this is a problem of KDE and all KDE Projects including KUbuntu. I don't believe that it is correct in KDE and only "broken-patched" by Kubuntu. Any official statements on this?? Where does KMIX get its default values from?? And it has nothing to do with sound restoration. All I had to do is fix the level of a couple of sliders, and there was the sound. Neither KDE, nor KMix is responsible for setting the soundcard. The distribution (really, really, really!) has to do that. Many/most distributions do that. If KUbuntu doesn#t do it, please report it there. Repeating in other words: KDE has NOTHING to do with setting initial volumes. This has to be done by the operating system, for example during booting the system. ALSA provides the tool alsactl for that, and distributions have to use that. Short investigation shows that it seems to be a common problem while upgrading to 8.04. See for example http://ubuntuforums.org/showthread.php?t=765443 By the way, this is not the first time I experience this problem. So there is at least more than one distro affected. And it was not an upgrade, it was a fresh installation. But you might be right that it not a problem of KDE. Any idea where else I should post this then? Ubuntu-Launchpad was referring me to bugs.kde.org. OK. I'll reopen this until we can get to some solution with Ubuntu. As a reference, this is https://bugs.launchpad.net/ubuntu/+source/kdebase-kde4/+bug/225836 . OK, this was and is still an upstream bug. Closing this with resolution "UPLSTREAM". In my case it was pulseaudio. My master and front channels got muted after login (but not during login). I saw that gconfd-2 and pulseaudio got started with my session. I solved the situation uninstalling pulseadio. As you can see, pulseaudio has some tendency to mute channels: http://www.google.es/search?q=pulseaudio+login+muted |