← Back to team overview

dx-packages team mailing list archive

[Bug 1165420] Re: Unable to access indicators from HUD

 

It really would be appreciated. My experience with HUD-related bug
reports till now has been quite negative... It's like whatever they are
doing with the HUD, they don't want to communicate it to the community,
which is quite frustrating. For example, the bug where the HUD didn't
work with LibreOffice remained unassigned forever... Then in Saucy it
just started to work again. But now we lost the Indicators... But at
least now somebody told us it was really a (bad) design decision.

I would really like to see more communication about the HUD, as I think
it is the best and most distinctive feature of Unity.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1165420

Title:
  Unable to access indicators from HUD

Status in Ayatana Design:
  Confirmed
Status in Unity HUD:
  Confirmed
Status in “hud” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's "Update Status" option there, making status updates to Twitter easy and fast.
  I could also use HUD to change my status in Empathy from Available to Busy and vice-versa.

  In Ubuntu 13.04 Beta HUD no longer finds the "Update Status" option when typing "Update Status" or "Update"
  Also writing "Available" "Away" or "Busy" no longer gives any results.

  Other indicators however are accessible and I can use HUD to Suspend
  my computer or to view Skype status or Ubuntu one indicator options.

  Repeating:
  1. Press alt key to start HUD
  2. Write "Update status" or "Available"

  What was expected:
  HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator.

  What happened:
  HUD didn't find any results.

  Notes:
  I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1165420/+subscriptions