Changing volume with function keys hangs the system when Rhythmbox is in focus

Bug #258559 reported by Ezra Morris
66
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Lucid by Matew

Bug Description

If I put the focus on any other window, the volume changes immediately, but if I switch focus to Rhythmbox, it takes about 20 seconds to change and I can not change to another application until the volume changes.

On #144330 (same bug reported to 'Rhythmbox'), Sebastien Bacher on 2008-06-27 assures us that this is a linux bug not rythmbox.

Ubuntu 8.04

apt-cache policy rhythmbox
rhythmbox:
  Installed: 0.11.5-0ubuntu8
  Candidate: 0.11.5-0ubuntu8
  Version table:
 *** 0.11.5-0ubuntu8 0
        500 http://gb.archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     0.11.5-0ubuntu6 0
        500 http://gb.archive.ubuntu.com hardy/main Packages

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ezra Morris (ezramorris) wrote :

@Leann Ogasawara:
Where should I download the 2.6.27 package from? I'm attempting to download the linux-image-2.6.27-2-generic package from http://packages.ubuntu.com/intrepid/i386/linux-image-2.6.27-2-generic/download , but none of the mirrors seem to work.

Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi emrrois,

Hrm, I just tested and the mirrors seem to work here. Although note the message at the top of that page:

"If you are running Ubuntu, it is strongly suggested to use a package manager like aptitude or synaptic to download and install packages, instead of doing so manually via this website.

You should be able to use any of the listed mirrors by adding a line to your /etc/apt/sources.list like this:

deb http://fr.archive.ubuntu.com/ubuntu intrepid main

Replacing fr.archive.ubuntu.com/ubuntu with the mirror in question."

Just curious if you tried enabling the Intrepid repository as instructed above to install the package. Thanks.

Revision history for this message
Ezra Morris (ezramorris) wrote :

Hi,
Woops, I completely forgot about this bug.
I can confirm this bug is now fixed in Intrepid Alpha 5, in the live CD at least. I have not tested alpha 6 due to the serious network bug.

Changed in linux:
status: New → Fix Released
Revision history for this message
eugrus (eugrus) wrote :

Hmmm... What is about a package for our PCs at last?

This bug is far too old............. :(((

Revision history for this message
Ezra Morris (ezramorris) wrote :

@eugrus:
sorry, I didn't understand the first line.

Revision history for this message
Richard Jonsson (richard-jonsson-bredband) wrote :

This bug is still there with intrepid!
rhythmbox:
  Installerad: 0.11.6svn20081008-0ubuntu3
  Kandidat: 0.11.6svn20081008-0ubuntu3

It affects muting too. A laymans guess is that rhythmbox gets confused by the mixer changes, or intercepts the keypresses and collides someway with the global key-handling.

Changed in linux:
status: Fix Released → Confirmed
Revision history for this message
Ezra Morris (ezramorris) wrote :

Yeah, I only tested this on the live CD. Once I upgrade to Intrepid, I will try again.

Revision history for this message
Richard Jonsson (richard-jonsson-bredband) wrote :

Only gnome apps are frozen (rhythmbox, firefox, gnome-terminal). I can choose open in the menu in kaffeine for example, and browse directories, or executing commands in xterm. Tabbing between windows works at least with compiz enabled.

Revision history for this message
Topher (hunt-topher) wrote :

From reading comments on duplicate bugs in the past, I think I remember that this bug only affects GTK-based apps - so I'm guessing that that would explain why Kaffeine and xterm etc. aren't affected by the bug. Since so much of Gnome is dependent on GTK, this will remain a pretty serious bug if it has not been fixed by the final release.

Revision history for this message
Topher (hunt-topher) wrote :

I've installed the beta of Intrepid and the bug seems fixed! For the moment, at least.
Ryhthmbox 0.11.6
Kernel: 2.6.27-4-generic (#1 SMP Wed Sep 24 01:30:51 UTC 2008)

Revision history for this message
Richard Jonsson (richard-jonsson-bredband) wrote :

The bug is very much NOT fixed at least on my system. Fully updated intrepid, last checked minutes ago.

Can someone tell what package is responsible for osd-handling when volume is changed?
I have filed another bugreport 286102 "brightness-keys react slowly" which I believe is related, and which also has this osd window showing up. Everything works fine until the window pops up.

Revision history for this message
Ezra Morris (ezramorris) wrote :

Bug fixed (for me) on my Intrepid install after I reassigned the keys in 'keyboard shortcuts'.

Revision history for this message
eugrus (eugrus) wrote :

This bug still bugs for me ;(

Rhythmbox 0.11.5

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Since Ezra is the original bug reporter and has commented this appears to be resolved I'm setting this bug's status to Fix Released for Intrepid.

@eugrus, it's likely you have a slightly different issue and should open a separate bug report. Thanks.

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Richard Jonsson (richard-jonsson-bredband) wrote :

@Leann:
I have the exact same problem as original reporter in the bug description, so should I copy-paste original reporters bug description into a new report then?
I have reassigned my volume keys too. They didn't work at all after upgrade to intrepid. I didn't have the issue before reassigning them, but obviously I got it after making them work.

Revision history for this message
Ezra Morris (ezramorris) wrote :

I would say create a new one, and report it in your own words.
This will allow the bug to become 'New' again, and will wait for someone to confirm it.
In theory, we could just mark this as new again, but it has already been 'fixed' for some people.

In your bug report, it would probably be best to link to this bug report and make a point that you still have the problem, even though it has 'already been fixed' to avoid it being reported as a dupe.

Revision history for this message
Victor Osadci (victor-os) wrote :

This bug is still present for me in Ubuntu 9.04.

I'm reopening this bug as there are still people that experience the problem.

Changed in linux:
status: Fix Released → New
Revision history for this message
eugrus (eugrus) wrote :

+1

Revision history for this message
Jacob Hume (windigo) wrote :

Also finding this in Ubuntu Jaunty 9.04, with Rhythmbox 0.12.0.

This doesn't have any effect on other GTK applications for me; only with Rhythmbox, and only while playing audio. I have checked other GTK applications and other multimedia applications, and only this combination seems to be effected.

Revision history for this message
Dave-B (david-balch) wrote :

I'm getting this on 9.04, Rhythmbox 0.12.0, using the volume wheel on my Toshiba Tecra A9.

Running RB with --debug gives this:

# A whole bunch of startup stuff
# A whole bunch of tick messages

(22:06:17) [0x20f7500] [tick_cb] rb-shell-player.c:3615: tick: [file:///home/david/media/music/c/Charles%20Mingus/Blues%20&%20Roots/10%20-%20E's%20Flat%20Ah's%20Flat%20Too%20(alternate%20take).ogg, 149:407(1)]
(22:06:17) [0x20f7500] [window_focus_cb] rb-mmkeys-plugin.c:142: window got focus, re-grabbing media keys

# RB freezes, window greys-out
# 25 seconds later, RB thaws...

(22:06:42) [0x20f7500] [maybe_add_current_song_to_queue] rb-audioscrobbler.c:591: Skipping detected; not submitting current song
(22:06:42) [0x20f7500] [rhythmdb_read_enter] rhythmdb.c:1176: counter: 1

I've attached more debug output for context.

I'd guess that RB is grabbing the multimedia keys, rather than leaving them to modify the master control, and then getting confused...

Revision history for this message
Ezra Morris (ezramorris) wrote :

I am getting this again in Jaunty.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi Ezra,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p alsa-base 258559

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-sound
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Pablo Estigarribia (pablodav) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pablodav 2003 F.... pulseaudio
 /dev/snd/pcmC0D0p: pablodav 2003 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdcf8000 irq 20'
   Mixer name : 'Silicon Image SiI1392 HDMI'
   Components : 'HDA:10ec0888,14622fb3,00100001 HDA:11c11040,11c10001,00100200 HDA:10951392,ffffffff,00100000'
   Controls : 28
   Simple ctrls : 15
CheckboxSubmission: 6f06e30d09a12205caac862637a2396b
CheckboxSystem: 541faccbc95727ce16da92de0db5c2b7
DistroRelease: Ubuntu 9.10
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=es_UY.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
Tags: ubuntu-unr
Uname: Linux 2.6.31-17-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Pablo Estigarribia (pablodav) wrote :

This bug is stil active on latest release for Karmic Koala with Rythmbox 0.12.5

Revision history for this message
eugrus (eugrus) wrote :

Hey, Pablo! Why don't you use a single post?

Revision history for this message
Pablo Estigarribia (pablodav) wrote :

All those post was added automatically by apport-collect -p alsa-base 258559, sorry....

Revision history for this message
A. Robert Johnson (johnson-adam-r) wrote :

I was having trouble with this in karmic, but then I saw this other bug report that suggests turning off accessibility. Maybe this will work for someone here as well

https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/308370

System > Assistive Technologies > disable

That bug has supposedly been fixed, but it's still there in on my x64 karmic system.

Revision history for this message
Hans van den Bogert (hbogert) wrote :

It only happens when I'm pushing cntrl+ alt + Fn-volumeUp,
in conjunction with easystroke (nifty little program) this happens a lot.

Revision history for this message
Bernard van der Velden (bernard-vyper) wrote :

Turning off accessibility ("System > Assistive Technologies > disable") worked for me, so it seems there is a workaround for this bug...

I have an x64 system running Lucid (Ubuntu 10.04).

Revision history for this message
Giorgi Maghlakelidze (dracid) wrote :

Hi all!
I am using HP Pavilion DV5 1000. It has a kind of sensor on the panel, to control the volume. Does exactly the same, as you've all said - freezes the whole system for around 15-25 seconds. If the Rythmbox window is NOT active - works fine.

I confirm that the problem is still there in Lucid, x32 with all latest updates!

Also, I confirm that disabling Assistive Technologies fixes it somehow... How are those related?

And... How come this hasn't been fixed for so many years? (since 2007)

Changed in linux (Ubuntu):
status: New → Triaged
tags: added: kernel-acpi kernel-needs-review
Revision history for this message
penalvch (penalvch) wrote :

Ezra Morris, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (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.