[Dx-packages] [Bug 1666623] Re: Windows disappear on disconnecting external monitor

2017-02-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: compiz-plugins-main (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/123

Title:
  Windows disappear on disconnecting external monitor

Status in compiz-plugins-main package in Ubuntu:
  Confirmed

Bug description:
  When I undock my laptop and the external displays are disconnected,
  sometimes the windows which were on those displays end up on my
  laptop's internal display. This is useful.

  Often, however, they don't. I can still see them in the panel, and I
  can click on them to bring them back... but nothing happens. They are
  somewhere off-screen and I cannot find any way to recover those
  windows except to kill the application and restart it.

  Often when this happens, even redocking the laptop and bringing those
  displays back doesn't actually get the windows back — those monitors
  are empty when they come back, or have only a subset of the "missing"
  windows.

  This is an HP EliteBook 850 G3 running Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/123/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1666623] Re: Windows disappear on disconnecting external monitor

2017-02-21 Thread Marc Olson
I have seen similar behavior on a Lenovo X1 Carbon (4th Gen) running
Ubuntu 16.04, both directly attached, and through the OneLink+ dock.

I've "solved" this by disabling the internal display when I have an
external display attached, and only attaching a single external display.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/123

Title:
  Windows disappear on disconnecting external monitor

Status in compiz-plugins-main package in Ubuntu:
  Confirmed

Bug description:
  When I undock my laptop and the external displays are disconnected,
  sometimes the windows which were on those displays end up on my
  laptop's internal display. This is useful.

  Often, however, they don't. I can still see them in the panel, and I
  can click on them to bring them back... but nothing happens. They are
  somewhere off-screen and I cannot find any way to recover those
  windows except to kill the application and restart it.

  Often when this happens, even redocking the laptop and bringing those
  displays back doesn't actually get the windows back — those monitors
  are empty when they come back, or have only a subset of the "missing"
  windows.

  This is an HP EliteBook 850 G3 running Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/123/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1666623] [NEW] Windows disappear on disconnecting external monitor

2017-02-21 Thread dwmw2
Public bug reported:

When I undock my laptop and the external displays are disconnected,
sometimes the windows which were on those displays end up on my laptop's
internal display. This is useful.

Often, however, they don't. I can still see them in the panel, and I can
click on them to bring them back... but nothing happens. They are
somewhere off-screen and I cannot find any way to recover those windows
except to kill the application and restart it.

Often when this happens, even redocking the laptop and bringing those
displays back doesn't actually get the windows back — those monitors are
empty when they come back, or have only a subset of the "missing"
windows.

This is an HP EliteBook 850 G3 running Ubuntu 16.04.

** Affects: compiz-plugins-main (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/123

Title:
  Windows disappear on disconnecting external monitor

Status in compiz-plugins-main package in Ubuntu:
  New

Bug description:
  When I undock my laptop and the external displays are disconnected,
  sometimes the windows which were on those displays end up on my
  laptop's internal display. This is useful.

  Often, however, they don't. I can still see them in the panel, and I
  can click on them to bring them back... but nothing happens. They are
  somewhere off-screen and I cannot find any way to recover those
  windows except to kill the application and restart it.

  Often when this happens, even redocking the laptop and bringing those
  displays back doesn't actually get the windows back — those monitors
  are empty when they come back, or have only a subset of the "missing"
  windows.

  This is an HP EliteBook 850 G3 running Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/123/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-02-21 Thread Treviño
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1600136

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in libappindicator source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1600136/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp


[Dx-packages] [Bug 1606246] Re: Hard-coded X11 calls cause Unity 8 to fail to run on desktop

2017-02-21 Thread Treviño
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Hard-coded X11 calls cause Unity 8 to fail to run on desktop

Status in appmenu-qt5:
  Fix Released
Status in Mir:
  Triaged
Status in appmenu-qt5 package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in unity8-desktop-session source package in Xenial:
  New

Bug description:
  The appmenu-qt5 code has hardcoded Xlib calls that cause Unity 8 (or
  any other Qt-based applicaiton) to die on startup when run on Mir
  instead of X11.

  This library extension should either not hardcode X11 (preferred) or
  check for the presence of a $DISPLAY  environment variable and avoid
  code paths that assume X11.

  The Unity 8 desktop currently has a hard-coded check for
  $QT_QPA_PLATFORMTHEME and unsets it as a workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1606246/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp