+++ This bug was initially created as a clone of Bug #927950 +++ Description of problem: I have two issues with docky - this one [unable to pin a specific app] and another [unable to launch caja]. It has taken some time to ber sufficiently annoyed to raise these issues. I have a company developed Java application that I am not able to "PIN" to dock. It appears as a running application in docky which can be manipulated but not pinned. The app has a .desktop launcher and it appears in my menu system and I have place it in my favourites, but I would dearly like to have in docky. Version-Release number of selected component (if applicable): docky-2.1.4-1.fc18.x86_64 How reproducible: The running app, has right click properties, but pin is not available. Steps to Reproduce: 1. Start app from menu or favourites or Gnome search 2. The running app appears in Docky as an active application 3. Right click the app in the dock and it has properties 4. PIN is not an available option Actual results: Docky is not able to automatically add application Expected results: To be able to PIN the application in docky Additional info: As a work-around, I have found that I can create a desktop launcher short-cut which I can then drag onto docky and dock it that way. I was not able to do it that way from the Gnome favourites.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.