<br><br><div><span class="gmail_quote">2008/2/13, Duncan <<a href="mailto:1i5t5.duncan@...">1i5t5.duncan@...</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Mark Haney" <<a href="mailto:mhaney@...">mhaney@...</a>> posted<br><a href="mailto:47B22624.7000109@...">47B22624.7000109@...</a>, excerpted below, on Tue, 12 Feb 2008<br>
18:05:08 -0500:<br><br>> I recently upgraded to KDE 3.5.8 and now one of my favorite features,<br>> the ability to adjust my sound volume from within KDE (via Audacious or<br>> Amarok) isn't working. I have to adjust it directly with alsamixer.<br>
><br>> I've not made any major adjustments to make.conf or anything, so what am<br>> I overlooking?<br><br>Do you use arts or not? Even if you keep it disabled (as I do now), many<br>KDE applications don't include much of their sound functionality if<br>
merged without the arts USE flag. Thus, even if you don't actually /use/<br>arts, you likely still want the arts USE flag on, or you'll be missing a<br>lot more than arts. (I found that out the hard way.)<br><br>
That's one of the good things to look forward to with KDE4. No more<br>virtually unending hassles with arts! Unfortunately, it'll be KDE 4.1<br>(at least) before it's the functional match of KDE 3.5.x. That's set for<br>
June IIRC, which means July or later before it goes stable. Figure<br>second half of the year...<br><br>So if you had USE=-arts for anything, remerge it with USE=arts, and see<br>if that helps. You may have to remerge all of KDE if you didn't merge<br>
the arts package itself.<br><br>If it's not that, it depends. The whole thing is rather a mess, with<br>arts being one of the biggest festering sores of KDE 3 because it has had<br>minimal maintenance for some time as it's a pile of patches on patches<br>
that no one has wanted to touch. There are often ways to get things<br>working, but they differ so much by installation and individual problem<br>that it's very difficult to troubleshoot remotely, and even locally, it<br>
often ends up being a case of trying random things until you either give<br>up or get lucky. Thus, even if little else changed, getting rid of arts<br>is reason enough to rejoice and eagerly await KDE4 (or install the 4.0.1<br>
Gentoo testing versions, in the tree but masked, if you don't mind some<br>other stuff not working as smoothly as later KDE 3 has).</blockquote><div><br>i use -arts pulseaudio. this fixes the problems and lets you use pulseaudio if you want. i got pulseaudio not started at startup and the sound still works fine. also be sure to have the alsa-oss modules since they're still needed by a lot of apps. even if you disable oss by default there are still there some dark packages that still use oss. this shouldn't be the amarok or xine case (i have them working well with -arts pulseaudio without pulseaudio started) but when you try to use mplayer with amarok in the tray you get an error for the sound device still occupied. i suspect that i need to run pulseaudio to get rid of this minor issue, but i don't care much since i only use mplayer very rarely. <br>
</div><br></div><br>-- <br>dott. ing. beso
|
