Docky is not target for minimize animation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Docky |
New
|
Undecided
|
Unassigned |
Bug Description
Using Compiz with the Animations plugin I find that using minimize animations that normally target the taskbar - such as "zoom" or "glide 2" - often fails to minimize "towards" Docky. That is to say, instead of targeting the launcher in Docky, the window minimizes towards the cursor, or rather towards the point on the screen where the minimize animation was originally triggered.
The problem only seems to affect applications that have a launcher on Docky. If an applications is launched that doesn't have a launcher on Docky, the minimize animation for that window will work as expected.
Windows that were initially started from a launcer on Docky will eventually start behaving correctly. However, I am not able to consistently recreate conditions under which this happens. Usually I will simply notice, after a few minutes of doing various other things, that the window has started minimizing correctly.
Terminal output does not seem to give any relevant information other than version numbers.
[Info 11:38:22.696] Docky version: 2.0.2 Release
[Info 11:38:22.703] Kernel version: 2.6.32.21
[Info 11:38:22.704] CLR version: 2.0.50727.1433
[Debug 11:38:22.941] [UserArgs] BufferTime = 0
[Debug 11:38:22.941] [UserArgs] MaxSize = 2147483647
[Debug 11:38:22.941] [UserArgs] NetbookMode = False
[Debug 11:38:22.941] [UserArgs] NoPollCursor = False
[Info 11:38:23.021] [DockController] Setting theme: Classic
[Info 11:38:24.924] [DrawingService] Could not find 'deluge', using fallback of 'extension'.
[Info 11:38:24.928] [DrawingService] Could not find 'gajim', using fallback of 'extension'.
[Info 11:38:24.932] [DrawingService] Could not find 'gtg', using fallback of 'extension'.
[Info 11:38:24.950] [DrawingService] Could not find 'pidgin', using fallback of 'extension'.
I see this has been marked as a duplicate of bug #495065, but as far as I can tell that bug does not deal with the issue I described, but rather with the issue of misplaced window previews. Despite my own lack of technical insight I suppose I can imagine that these two issues are both symptomatic of the same underlying bug, but this is certainly not obvious to the untrained eye. Is there any chance my bug report was erroneously marked as a duplicate?