← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus

 

Accepted sni-qt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sni-
qt/0.2.7+16.04.20170217.1-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: sni-qt (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sni-qt (Ubuntu Xenial)
       Status: New => Fix Committed

** No longer affects: unity (Ubuntu Xenial)

** No longer affects: unity (Ubuntu)

** No longer affects: compiz (Ubuntu Xenial)

** No longer affects: compiz (Ubuntu)

** Project changed: compiz => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: unity => ubuntu-translations

** No longer affects: ubuntu-translations

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/627195

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in sni-qt package in Ubuntu:
  New
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in empathy source package in Xenial:
  New
Status in indicator-messages source package in Xenial:
  New
Status in indicator-sound source package in Xenial:
  New
Status in libdbusmenu source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed
Status in tomboy source package in Xenial:
  New
Status in ubuntuone-client source package in Xenial:
  New

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  ====Some other observations=====
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again

  =====Comment from Ted Gould=====
  <om26er> tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible

  <tedg> om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =====The good rule=====
  3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations.

  For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     https://archive.is/2tLX6
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

  ===================================

  SRU for sni-qt:

  [Test case]

  git clone https://github.com/3v1n0/indicators-examples-snaps
  cd indicators-examples-snaps/qt4-systray
  qmake-qt4
  ./systray

  Close the app, now try to restore it from in the indicator (after having played with some app writing text on it such as gnome-terminal or gedit).
  The app should be in foreground now

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