"Jump to track" is not active window when summoned with global hotkey

Bug #485477 reported by Ricky Wong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: audacious

I'm using 9.10-i386 with audacious package version 2.1-1ubuntu1.

I have "Jump to track" set as a global hotkey (super+alt+J). However, it doesn't become the active window on the display when I do so. (I have to click in the window to use it, which almost defeats the purpose of hotkeying it.) I have a dual display configuration (using NVidia TwinView and repo drivers.) Using GNOME.

Audacious in background + "Jump to track" global hotkey --> window not active.
Audacious as active window + "Jump to track" global hotkey --> window active (duh, similar to pressing 'j')

Yesterday I saw different behavior when the Audacious window was on the other monitor, but I can't seem to repro that right now.

ProblemType: Bug
Architecture: i386
Date: Thu Nov 19 12:21:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/audacious2
NonfreeKernelModules: nvidia
Package: audacious 2.1-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: audacious
Uname: Linux 2.6.31-14-generic i686
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
NonfreeKernelModules: nvidia
Package: audacious 2.3-1ubuntu4
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-23-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ricky Wong (rwong48) wrote :
Revision history for this message
Benjamin Drung (bdrung) wrote :

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 Audacious 2.3 from the latest stable Ubuntu version (10.04) or the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect #485477, and any other logs that are relevant for this particular issue.

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

Changed in audacious (Ubuntu):
status: New → Incomplete
Revision history for this message
Ricky Wong (rwong48) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Ricky Wong (rwong48) wrote :

Problem still exists with 10.04-x86_64 with audacious 2.3-1ubuntu4. Reproducible even when using regular 'j' hotkey with Audacious as the active window.

Now using nVidia TwinView with Xinerama.

Changed in audacious (Ubuntu):
status: Incomplete → New
Revision history for this message
Ricky Wong (rwong48) wrote :

Correction to comment 4 -- nVidia "separate X screen" for 4 displays, with Xinerama.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi Ricky,

Can you explain in further detail how you're setting up the keyboard shortcut? I can see in the global keyboard menu options for next/prev track, which on my system laptop to be mapped to the '<<' '>>' hotkeys but I don't think that's what you mean. I can reproduce a jump-to-track function in Audacious via the 'j' key, but there seem not to be any 'Jump to Track' item listed in the global keyboard shortcuts list. Are you adding a custom field? If so, what command line did you use?

I'm also curious that you've mentioned using the nvidia driver several times; can you elaborate on why you think that is a relevant point in this bug? (E.g. did you find it behaved properly when using the -nouveau driver?)

Changed in audacious (Ubuntu):
status: New → Incomplete
Revision history for this message
Ricky Wong (rwong48) wrote :

I am using the Global Hotkey plugin. Preferences, Plugins, Global Hotkey. "Jump to file" -> super+J.

That brings up a separate discussion - if this bug is in audacious or in the plugin - but nonetheless, if I just hit J in random places in the program, most of the time the newly-spawned "Jump to track" dialog won't be the active one.

Hm.. so the Global Hotkey plugin calls it "Jump to file" and audacious still calls it "jump to track"..

When the active window is main or equalizer and I hit J, the "jump to track" dialog is active. But when my last active window was the Playlist or an item inside the playlist (just click around the playlist), hitting j makes an inactive jump-to-track dialog.

I don't think the graphics driver is the main cause of the bug but it could be relevant - in case a developer saw a potential problem with this before. I can reproduce this issue with a single display now as well. I have only been using the nvidia restricted driver and not nouveau.

Changed in audacious (Ubuntu):
status: Incomplete → New
Revision history for this message
Benjamin Drung (bdrung) wrote :

Can you reproduce this issue with audacious in maverick or from my backports PPA [1]?

[1] https://launchpad.net/~bdrung/+archive/backports

Revision history for this message
Ricky Wong (rwong48) wrote :

I added your PPA to my Software Sources for Lucid and did a safe-upgrade on the audacious packages.

I still see the issue when using the global hotkey plugin, and don't seem to see it when hitting 'j' inside of audacious.

Should I be trying Maverick also or is Lucid backport good enough?

On a side note.. the "Jump to track" dialog gets hidden under any Audacious windows when the Always On Top feature is enabled. I feel like the dialog should have that property as well..?

Revision history for this message
Benjamin Drung (bdrung) wrote :

The lucid backport is identical to the maverick version. You might want to test maverick. This bug is maybe not a bug in audacious, but in compiz.

Revision history for this message
Tihamer Petrovics (tihameri) wrote :

Hi,

Here is a workaround for the issue with evrouter: http://ptichy.blogspot.com/2014/08/audacious-workaround-jump-to-track-is.html

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in audacious (Ubuntu):
status: New → Confirmed
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.