cmus in Intrepid Ibex: no volume control

Bug #296229 reported by ecce berlin
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cmus (Ubuntu)
Expired
Medium
Unassigned
Intrepid
Invalid
Undecided
Unassigned

Bug Description

In Intrepid Ibex I can't control the volume in cmus anymore. Pressing +/- has no effect, nor does ":vol +10%" and the like. The current volume is not shown at all in the status bar. There is sound, but it's volume can't be controlled from within cmus.

Probably not a problem in cmus itself (same version worked flawlessly in Ubuntu 8.04).

ubuntu 8.10
cmus 2.2.0-1build1

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.

Revision history for this message
ecce berlin (ecce-berlin) wrote :

I've done a fresh install of Ubuntu 8.10 on a different machine, apt-get update/upgrade, then only installed cmus -- with the same result: no volume controls.

The requested information is attached and located here: http://www.alsa-project.org/db/?f=5d590441dbc7315cb4f05c6cb9527d18aa757321

Revision history for this message
xteejx (xteejx) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Revision history for this message
xteejx (xteejx) wrote :

Assigning to package "cmus"

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Can anyone confirm this bug on intrepid?

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Oops, s/intrepid/jaunty

Revision history for this message
Alfred Rossi (alfredr) wrote :

i'll confirm this bug for jaunty. volume doesn't work from inside of cmus.

Revision history for this message
spear1bearer (spear1bearer) wrote :

confirming on a freshly installed jaunty:

system status by utils_alsa-info.sh http://www.alsa-project.org/db/?f=19565336d25c12ac4a21450af83165284181310c

Revision history for this message
xteejx (xteejx) wrote :

Hi guys, we were wondering if this is still a problem for you in Karmic 9.10? If so, can you please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect -p alsa-driver 296229

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

Changed in cmus (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gregory Petrosyan (gregory-petrosyan) wrote :

Just in case this can help anybody:

cmus' maintainer, Timo Hirvonen, has disappeared nearly a year ago. Since that time, unofficial fork called 'cmus-unofficial' has been developed. Among various fixes and enhancements, you can find there native PulseAudio output plugin; -unofficial branch works very well on Karmic.

There are no PPA packages right now, but installation is trivial: usual "./configure; make; sudo make install" (you'll need various -dev packages for building input/output plugins).

Please try it: http://github.com/JasonWoof/cmus-unofficial

Revision history for this message
jessed (jesse-driskill) wrote : apport-collect data

Architecture: amd64
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: alsa-driver (not installed)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
Uname: Linux 2.6.31-19-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin sambashare vboxusers video
XsessionErrors: (firefox:12588): GLib-WARNING **: g_set_prgname() called multiple times

Changed in cmus (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
jessed (jesse-driskill) wrote :

    Yes, this is still a problem. I just ran the command requested by Teej.

Revision history for this message
xteejx (xteejx) wrote :

Marking Confirmed, Medium. Thank you for the above.

Changed in cmus (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
xteejx (xteejx) wrote :

Should have been marked Triaged. There should be enough information here for a developer to take a look at it. Thanks guys.

Changed in cmus (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
[euchrid] (euchrid) wrote :

I tried to follow Gregory Petrosyan's advice, but couldn't find the Pulseaudio output plugin. I installed the latest version of unofficial cmus, but was still left without a volume control.

Eventually, I got the cmus volume control back by removing Pulseaudio as per nullrend's instructions here:
http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1313253

I suggest that this problem is cause solely by Ubuntu's implementation of Pulseaudio in the the Intrepid and Karmic updates. Previously, I had not use Pulseaudio at all, so did not notice that this had now overridden my ALSA settings.

Hope this helps someone.

Revision history for this message
Gregory Petrosyan (gregory-petrosyan) wrote :

[euchrid] To build PulseAudio output plugin, you need libpulse-dev installed. If there are any problems with plugin, please report — there are no known bugs in it, and it is known to work flawlessly on at least 2 latest releases of Ubuntu, as well as on other distros.

Also, now cmus' code can be found at http://gitorious.org/cmus, and latest version is 2.3.2.

Revision history for this message
[euchrid] (euchrid) wrote :

Gregory - as per my above comment, I no longer have Pulseaudio installed, so cannot report on whether the output plugin causes me any problems. In any case, I could not FIND the Pulseaudio output plugin to install, as the page you linked to back in January appears to have changed since then.

As reported, I got cmus working correctly again by removing Pulseaudio and sticking with ALSA. I was not suggesting that your advice was in any way wrong - indeed, it looked the most helpful to me from all the advice on this page - it was simply that the advice did not work for me, as the output plugin was not available for me to use when I visited the page.

I was not suggesting that there was any problem with the Pulseaudio output plugin, only that the way Ubuntu has implemented Pulseaudio in this latest release may have caused this issue with cmus. I was not, furthermore, suggesting that Ubuntu had done anything wrong, or that they shouldn't have implemented Pulseaudio, only that it seemed to be the reason people were experiencing this issue.

Revision history for this message
Alessio Treglia (quadrispro) wrote : New upstream release: 2.3.3

Hi,

is this reproducible with the latest upstream release available in Maverick?

--
Alessio Treglia <email address hidden>
Debian & Ubuntu Developer | Homepage: http://www.alessiotreglia.com
0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0

Changed in cmus (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Alessio Treglia (quadrispro) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Changed in cmus (Ubuntu Intrepid):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cmus (Ubuntu) because there has been no activity for 60 days.]

Changed in cmus (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.