This is little bug, but perhaps could be easy to fix.
When I move the pointer to the project Homepage hyperlink coming from the bottom of the hyperlink,, when it is an I-beam, then it will stay an I-beam even when hovering over the hyperlink, instead of changing to the hand pointer.
I have also seen this bug in all versions I can remember, currently gpk-application 2.27.2 -- very often, not only will the I-beam cursor be shown when hovering the "Project: Homepage" link, but it will also take exactly 3 clicks in order to get the proper focus and click for the link to be triggered.
Some further troubleshooting reveals that if you carefully move your mouse down from directly above the link, it will properly change to a hand and the first click will properly open the link.
However, if you move your mouse from the left side (where the description is) over to the link, it will not function without the bugginess. In fact, coming from any angle other than directly above the link will produce the undesirable side-effects.
If you overshoot the link (i.e. if you are coming from above but move your mouse slightly too far and then move it back up to the link), it will produce the same buggy results.
Experimentation shows that it can actually take an infinite amount of clicks for the link to be properly focused and activated -- if reproducing the bug as described, you could click the link, move your mouse back over text such as "Download Size" etc., then click the link again, move your mouse over some of the other labels, and just keep doing it forever, the link will never activate until the link is either clicked several times in succession or until the mouse is moved back up to the package list then moved carefully down over the link from directly above.
Hope this helps.
This bug report is very old and based on a version not supported anymore. By upgrading to a newer version of PackageKit you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of PackageKit.
Please feel free to reopen this bug if the problem still occurs with the latest version.