"Jump to track" is not active window when summoned with global hotkey
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
NonfreeKernelMo
Package: audacious 2.1-1ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
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)
NonfreeKernelMo
Package: audacious 2.3-1ubuntu4
PackageArchitec
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: lucid
Uname: Linux 2.6.32-23-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.]