Rhythmbox goes crazy if I change keyboard layout

Bug #1046066 reported by Kirsanov Vitaliy on 2012-09-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)

Bug Description

Description: Ubuntu 12.04.1 LTS
Release: 12.04
  Installed: 2.96-0ubuntu4.1
  Candidate: 2.96-0ubuntu4.1
  Version table:
 *** 2.96-0ubuntu4.1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.96-0ubuntu4 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages


Not so trivial to explain but I'll try.

 1. Launch Rhythmbox
 2. Insert a CD in the CD-ROM
 3. The CD is not automatically identified (it's of a not very famous Russian band)
 4. I'm manually setting track names and...
 5. Magic, black magic! If I change the keyboard layout (RU <-> EN) during editing then Rhythmbox kicks me out of the editing. So if a track name contains both Russian and English words I'm compelled to write one part, press Enter (so that the changes are not lost), change layout, click on the track name, write another part in the opposite layout. In some tricky names I have to do this several times.

By the way, I use Alt+Shift to change layout. With Ctrl+Shift it works much better. Any ideas?

description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rhythmbox (Ubuntu):
status: New → Confirmed

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers