dx-packages team mailing list archive

[Franko Burolo <franko.burolo@xxxxxxxxx>]

The bug was reported a year ago, but they have hopefully just started
fixing it. First they told us this was a DESIGN DECISION, take a look at
commect #8. but days before the Trusty release Mark intervened, and then
he told us he was told it was a REGRESSION caused by some changes in
gtk... So go and figure out... :-/ Anyhow, I doubt they were doing
anything about it before Mark's intervention. But I do hope they really
are working on this now. Some more feedback from the people doing it
would also be nice. Since the HUD teams seems to be kind of autistic
towards bug reporters -- they don't communicate much about them, which
is pretty frustrating.

-- 
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