from:"Mateusz Stachowski"

That finally worked.

Changing launcher icons size works and workspaces also work without
unneeded animations.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Desktop-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

I've forced the lowgfx setting with command from comment #9 and the fade
in fade out animations are gone.

But I can't change the launcher icons size. The slider in control center
isn't working. Also The workspace switcher can't be enabled and it
disapeared from launcher. I have it enabled in regular gfx.

This is the version of unity-control-center:
15.04.0+16.04.20160705-0ubuntu1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Desktop-packages] [Bug 1584161] Re: Freedesktop Screensaver API is not implemented

The new command returns:

(false,)

Which I assume is how it should be when screensaver is inactive.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1584161

Title:
  Freedesktop Screensaver API is not implemented

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  This is what we get in an unity session:

  gdbus call --session --dest org.freedesktop.ScreenSaver --object-path
  /org/freedesktop/ScreenSaver --method
  org.freedesktop.ScreenSaver.GetActive

  Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod:
  Interfaccia "org.freedesktop" inesistente sull'oggetto nel percorso
  /org/freedesktop/ScreenSaver

  Side effect of this is bug #1415265

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1584161/+subscriptions

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

[Desktop-packages] [Bug 1584161] Re: Freedesktop Screensaver API is not implemented

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1584161

Title:
  Freedesktop Screensaver API is not implemented

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  This is what we get in an unity session:

  gdbus call --session --dest org.freedesktop.ScreenSaver --object-path
  /org/freedesktop/ScreenSaver --method
  org.freedesktop.ScreenSaver.GetActive

  Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod:
  Interfaccia "org.freedesktop" inesistente sull'oggetto nel percorso
  /org/freedesktop/ScreenSaver

  Side effect of this is bug #1415265

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1584161/+subscriptions

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

[Desktop-packages] [Bug 1584161] Re: Freedesktop Screensaver API is not implemented

Running that command still returns the same error.

I checked it in my Xenial install and also using Yakkety daily LiveCD.
Both return the error message.

** Tags removed: verification-needed
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1584161

Title:
  Freedesktop Screensaver API is not implemented

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  This is what we get in an unity session:

  gdbus call --session --dest org.freedesktop.ScreenSaver --object-path 
/org/freedesktop/ScreenSaver --method org.freedesktop.GetActive
  Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Interfaccia 
"org.freedesktop" inesistente sull'oggetto nel percorso 
/org/freedesktop/ScreenSaver

  Side effect of this is bug #1415265

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1584161/+subscriptions

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

[Desktop-packages] [Bug 1304388] Re: unity-control-center crashed with SIGSEGV in default_app_changed()

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1304388

Title:
  unity-control-center crashed with SIGSEGV in default_app_changed()

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Crash report and bug appeared straight after boot, cause unknown, though 
system went on to run normally after.
  Ubuntu 14.04 Beta 2

  [Test case]
  Set Firefox Nightly as default browser
  UCC should not crash in that case

  [Regression potential]
  This is a null-pointer check, there's nothing to worry about.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140407-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr  8 13:25:48 2014
  ExecutablePath: /usr/bin/unity-control-center
  ProcCmdline: unity-control-center
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xac26dcbd:mov(%eax),%ecx
   PC (0xac26dcbd) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/unity-control-center-1/panels/libinfo.so
   g_cclosure_marshal_VOID__VOID () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID__VOID()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1304388/+subscriptions

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

[Desktop-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

I tested it on my default install by enabling lowgfx through CCSM.

It did switch off all transparency effects. Also there are no preview
animations in Dash but I still have fade in and fade out animation for
showing windows (Super+W).

In my testing using virtual machine that animation was disabled so I
guess it works as intended. Also in virtual machine I can't enable
workspaces.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Desktop-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

2016-06-06 Thread Mateusz Stachowski

There is no snap package on Krita website they only provide appimages.

Also the current snap for Krita is 3.0-snap12. That's 3rd revision of
that package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1588192

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Fix Committed

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

2016-06-04 Thread Mateusz Stachowski

I'm wondering if the GLVND which is present in 361 drivers and not in
340 isn't the reason for all those problems.

https://devtalk.nvidia.com/default/topic/915640/multiple-glx-client-
libraries-in-the-nvidia-linux-driver-installer-package/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1588192

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Fix Committed

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

2016-06-03 Thread Mateusz Stachowski

I'm also on nvidia_340 and Krita is working now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1588192

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Fix Committed

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

2016-06-02 Thread Mateusz Stachowski

This of course is a problem for all NVIDIA drivers not only the 361. So
the other packages also need to be patched.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu.
https://bugs.launchpad.net/bugs/1588192

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-361 source package in Xenial:
  In Progress

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot

2016-05-27 Thread Mateusz Stachowski

For people reporting gedit with no menus when run as root there is
already bug report open about this issue:

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590

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

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1532226/+subscriptions

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

[Desktop-packages] [Bug 1527590] Re: gedit unusable when menu can't be displayed

2016-05-27 Thread Mateusz Stachowski

The #3 isn't relevant anymore because gedit is patched to disable CSD
(Client Side Decorations) on Unity.

However this patch doesn't work for point #2. So when you run gedit as
root you get it with CSD and this means no menus. And this affects menus
displayed on the panel and in the window titlebar.

This is how gedit looks with CSD normally:
http://2.bp.blogspot.com/-tAION31T1J4/VgKtBTmqWOI/W5k/qxa5fz7qXdo/s1600
/gedit-minimap.png

** Attachment added: "sudo gedit.png"
   
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+attachment/4671094/+files/sudo%20gedit.png

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

Title:
  gedit unusable when menu can't be displayed

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  There are multiple ways to use gedit where the menu is not being
  shown, rendering it unusable:

  1- use it over ssh
  2- do "sudo gedit"
  3- Enable rendering window menus in the window titlebar

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu4
  ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 07:16:30 2015
  InstallationDate: Installed on 2015-10-23 (55 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions

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

[Desktop-packages] [Bug 1577268] Re: Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04

2016-05-26 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04

Status in brasero package in Ubuntu:
  Fix Released
Status in brasero source package in Xenial:
  Fix Committed

Bug description:
  * Impact
  the libcss plugin can't be enable with the current libdvdcss version

  * Test case
  - install libdvdcss
  - start brasero
  - go to the plugins dialog, enable the libdvdcss plugin

  * Regression potential
  none, the plugin was not loading at all and it's only its loader being changed

  

  "I recently updated one of my rigs from 14.04 to 16.04. After
  upgrading Brasero tells me that it can't find libdvdcss. VLC play an
  inserted DVD, I see libdvdcss in /usr/lib/x86_64-linux gnu. However, i
  didn't see it simply in /usr/lib/ so I created a link there. Still
  didn't work, so I copied an older libdvdcss to /usr/lib. Still no joy.

  I checked to see what versions of libdvdcss I had installed - 2.2.0 in
  /usr/lib/x86_64-linux, 2.1.0 in /usr/lib * mv'ed the.2.1.0 to
  x86_64-linux * rm'ed the sym links to 2.2.0 * new sym link to 2.1.0 *
  works. "

  Originally reported here :

  
https://www.reddit.com/r/Ubuntu/comments/4h4pcn/anybody_using_brasero_to_rip_dvds_in_1604/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1577268/+subscriptions

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

[Desktop-packages] [Bug 1574090] Re: Brasero not translated at all on ubuntu 16.04

2016-05-26 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Brasero not translated at all on ubuntu 16.04

Status in Brasero:
  Unknown
Status in brasero package in Ubuntu:
  Fix Released
Status in brasero source package in Xenial:
  Fix Committed

Bug description:
  To the sponsor: Please use the same patch for Xenial, changing the
  version to 3.12.1-1ubuntu2.1.

  [Impact]

  Translations are not enabled. The attached patch fixes it.

  [Test Case]

  1. Install some other language but english and make it the display
  language.

  2. Start brasero and find that it's still displayed in English.

  [Regression Potential]

  Neglectable.

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

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

[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot

2016-05-26 Thread Mateusz Stachowski

When you run gedit as root it uses CSD (Client Side Decorations)
something that is patched out in Ubuntu but apparently the patch doesn't
work for root.

gedit with CSD should look like this:
http://2.bp.blogspot.com/-tAION31T1J4/VgKtBTmqWOI/W5k/qxa5fz7qXdo/s1600
/gedit-minimap.png

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

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1532226/+subscriptions

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

[Desktop-packages] [Bug 1565267] Re: Gnome Calendar has white corners

2016-05-18 Thread Mateusz Stachowski

Actually I'm not sure if it should be marked as verification-done.

That's because as far as I can see it only resolves the problem for
Ubuntu default themes Ambiance and Radiance all the other 3rd party
themes still render incorrectly. Even Adwaita the default GNOME theme
renders incorrectly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1565267

Title:
  Gnome Calendar has white corners

Status in GNOME Calendar:
  Fix Released
Status in Ubuntu theme:
  New
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Committed

Bug description:
  * Impact

  the gnome-calendar window corners don't look right (white squares
  instead of rounded)

  * Test case
  start gnome-calendar under unity and look at the windows corner, they should 
be rounded. The update also include a bugfix new revesion so make sure calendar 
events are correctly listed and that the calendar works correctly

  * Regression potential
  the update has only small bugfixes and should be safe but keep an eye for new 
issues

  --

  Gnome Calendar still looks like it is not using the proper CSD that
  other Gnome apps do (maps, weather, etc.) nor does it look like a
  patched Unity app.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.19.92-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  2 07:12:41 2016
  InstallationDate: Installed on 2016-03-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1565267/+subscriptions

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

[Desktop-packages] [Bug 1565267] Re: Gnome Calendar has white corners

2016-05-18 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1565267

Title:
  Gnome Calendar has white corners

Status in GNOME Calendar:
  Fix Released
Status in Ubuntu theme:
  New
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Committed

Bug description:
  * Impact

  the gnome-calendar window corners don't look right (white squares
  instead of rounded)

  * Test case
  start gnome-calendar under unity and look at the windows corner, they should 
be rounded. The update also include a bugfix new revesion so make sure calendar 
events are correctly listed and that the calendar works correctly

  * Regression potential
  the update has only small bugfixes and should be safe but keep an eye for new 
issues

  --

  Gnome Calendar still looks like it is not using the proper CSD that
  other Gnome apps do (maps, weather, etc.) nor does it look like a
  patched Unity app.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.19.92-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  2 07:12:41 2016
  InstallationDate: Installed on 2016-03-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1565267/+subscriptions

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

2015-09-16 Thread Mateusz Stachowski

Yes screen gets locked when menus are open since a couple of Unity
releases.

But right click context menus are a different story. For example when I
have right click menu opened in Nautilus the screen goes blank but when
I move the cursor I see the whole screen and then only after clicking
somwhere screen gets locked. So you can't interact with programs but you
can see everything.

Also with right click menu in Opera the screen never gets locked. But
right click menu opened in FireFox, Spotify, Ubuntu Web Browser gets
screen locked at the same time it blanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed
Status in gnome-screensaver source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Confirmed
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-07-26 Thread Mateusz Stachowski

A.J.Mac (macbunch) you can mute mail or edit the things that you will
get notified about on the right side it's between "Duplicates of this
bug" and "Other bug subscribers".

Anyway there shouldn't be much more e-mails about this bug now that it's
been verified for Trusty. I would expect only one e-mail about the
package released to trusty-updates the regular repo.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Committed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

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

[Desktop-packages] [Bug 1449959] Re: Running ./unity --replace ... terminates the session and starts a new one on vivid

2015-05-08 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1449959

Title:
  Running ./unity --replace ... terminates the session and starts a new
  one on vivid

Status in gnome-session package in Ubuntu:
  In Progress
Status in gnome-session source package in Vivid:
  Fix Committed

Bug description:
  [ Description ]

  Due to an error when merging with Debian, ubuntu's gnome-session file is
  inadvertantly starting compiz when it should instead be managed by
  upstart.  This means that we don't, for example, have unity restarted by
  upstart if it crashes and (as the reporter of this bug notes) unity
  --replace breaks due to gnome-session tearing the session down if one of
  its required components goes away and comes back.

  [ Fix ]

  Remove "compiz;" from ubuntu.session so that the unity7.conf shipped by
  unity is used.

  [ QA ]

  Verify that you see the following before upgrading

  laney@raleigh> status unity7
  unity7 stop/waiting
  laney@raleigh> pstree -s -p $(pidof compiz)
  
systemd(1)───lightdm(1625)───lightdm(10651)───upstart(10864)───gnome-session(11094)───compiz(11374)─┬─{dconf
 worker}(11382)
    
  ├─{gdbus}(11383)
    
  └─{gmain}(11376)

  i.e. compiz is a child of gnome-session, and the unity7 job isn't
  running.

  and this after

  laney@raleigh> status unity7
  unity7 start/running, process 8945
  laney@raleigh> pstree -s -p $(pidof compiz)
  
systemd(1)───lightdm(1625)───lightdm(8487)───upstart(8715)───compiz(8945)─┬─{dconf
 worker}(8972)
    
├─{gdbus}(8976)
    
└─{gmain}(8950)

  compiz is a direct child of upstart and the unity7 job is running.

  Additionally, verify that unity --replace kicks you back to the display
  manager before and unity is replaced in-session after.

  [ Regression potential ]

  unity's job is now used instead of upstart being started by
  gnome-session. This was the case since we started having upstart in the
  session, but make sure that login and logout still work properly.

  [ Original description ]

  Running ./unity --replace  on vivid  (systemd) exits the session
  and the login screen of lightdm appears. After log in, a new session
  starts.

  Steps:
  1- build unity
  2- run ./unity --replace with the env. variables and parameters you used
 on utopic
  3- see the lightdm login screen and login

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-session 3.14.0-2ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr 29 13:15:16 2015
  InstallationDate: Installed on 2014-07-04 (299 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1449959/+subscriptions

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

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

2015-04-15 Thread Mateusz Stachowski

As I mentioned earlier this bug was for situation when you locked the
screen with Super+L or Ctrl+Alt+L or from indicator-session monitor
never blanked off.

It is now fixed and when you lock the screen with any of the above
mentioned methods monitor blanks off after 2 seconds.

Any problems with multimonitor setups or screensaver not blanking the
screen should be reported as new bug.

** Description changed:

  [ATTENTION] This bug report is strictly for lockscreen. When user
- activates lockscreen with Ctrl+Alt+L shortcut or from indicator-session
- the screen should blank off after a couple seconds.
+ activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from
+ indicator-session the screen should blank off after a couple seconds.
  
  The new Unity lock screen doesn't turn off the monitor screen.
  
  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't turn off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5 seconds
  after unlocking).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1292041

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ATTENTION] This bug report is strictly for lockscreen. When user
  activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from
  indicator-session the screen should blank off after a couple seconds.

  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't turn off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions

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

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

2015-04-15 Thread Mateusz Stachowski

** Description changed:

+ [ATTENTION] This bug report is strictly for lockscreen. When user
+ activates lockscreen with Ctrl+Alt+L shortcut or from indicator-session
+ the screen should blank off after a couple seconds.
+ 
  The new Unity lock screen doesn't turn off the monitor screen.
  
  I can wait as long as 10 minutes after activating the lock screen and
- the monitor still doesn't trun off. Then when I unlock the screen and
+ the monitor still doesn't turn off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5 seconds
  after unlocking).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1292041

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ATTENTION] This bug report is strictly for lockscreen. When user
  activates lockscreen with Ctrl+Alt+L shortcut or from indicator-
  session the screen should blank off after a couple seconds.

  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't turn off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions

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

[Desktop-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards

2015-04-11 Thread Mateusz Stachowski

** Tags added: utopic

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Precise:
  Confirmed
Status in compiz-plugins-main source package in Precise:
  Confirmed
Status in compiz source package in Trusty:
  Fix Released
Status in compiz-plugins-main source package in Trusty:
  Invalid
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the "driver → nvidia" line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

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

[Desktop-packages] [Bug 957879] Re: Wine tooltips don't disappear entirely from screen

2015-04-06 Thread Mateusz Stachowski

This also happens with NVIDIA drivers. I'm on Vivid fully updated and
using the 340 series drivers.

I tried using the SumatraPDF and tooltips don't dissapear completely and
in my case they also flash. However if I select text in the opened .pdf
or move my cursor over link in the webbrowser or this comment field the
tooltips dissapear so in my case it isn't permament.

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

Title:
  Wine tooltips don't disappear entirely from screen

Status in Compiz:
  Triaged
Status in compiz package in Ubuntu:
  Triaged

Bug description:
  This bug does not happen with Unity 2D or Gnome-Shell. Same problem on
  both Oneiric and Precise (up-to-date).

  When a tooltip from a Wine app disappear, its shadow remains. This can 
quickly leads to an unusable window.
  To clean these shadows, I have to move the window.

  I confirmed this bug with Mathcad 14, GeNIe and some others not-known
  apps. It does not happen, for example, with VLC or Steam.

  If you want to test with something free and lightweight, you can try
  with Sumatra: http://blog.kowalczyk.info/software/sumatrapdf/download-
  free-pdf-viewer.html

  
  Attached is a picture of a rather extreme case (made with a non-free app).

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

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

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"

2015-03-22 Thread Mateusz Stachowski

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-340-updates (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1268257

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: "objdump: '... .tmp_nv.o': No such
  file"

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  New
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  New

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for "LUG" in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions

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

[Desktop-packages] [Bug 1312882] Re: Main menu of Qt apps locally integrated in the window title bar disappears after activation of any menu item

2015-02-20 Thread Mateusz Stachowski

*** This bug is a duplicate of bug 1312137 ***
https://bugs.launchpad.net/bugs/1312137

This bug is resolved in Vivid the current development release.

Also this should be marked as duplicate of Bug #1312137 even if that bug
has less people affected because it has target assigned for the next
Trusty SRU and this one doesn't.

** This bug has been marked a duplicate of bug 1312137
Local menus broken for Qt apps after opening dialog

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1312882

Title:
Main menu of Qt apps locally integrated in the window title bar
disappears after activation of any menu item

Status in Unity:
Confirmed
Status in unity package in Ubuntu:
Confirmed

Bug description:
[The bug]
When the integration of the app menus into the window title bars is turned
on, call of any dialogue from the menu leads to disappearance of the menu.
After that, the window title bar displays only the application title string.
The main menu cannot be seen and cannot be accessed until you switch to another
application and then return. The bug is observed only for unmaximized windows.
The main menu of maximized windows works fine.
This bug is observed only for Qt applications. I have “succeeded” to
reproduce it for VLC, Gwenview, digiKam, Krita, Calliga, VirtualBox,
GoldenDict, Mixx.

[How to reproduce]
1. Make sure that “Show the menus for a window” parameter (System Settings ->
Appearance -> Behavior) is set to “In the window's title bar”.
2. Start any Qt application, say, one of mentioned above. Let it be, for
example, Gwenview.
3. Unmaximize the app window.
4. Activate any dialogue from the main menu. For instance, File -> Open... or
Settings -> Configure Gwenview...
5. Press Cancel to close the dialogue.
6. Hover the mouse pointer over the window title bar.

[What is expected]
The app menu should appear and be accessible.

[What happens]
The app menu is not shown. Only the application title is displayed in the
title bar.

The following screencast shows the bug “in action”:
http://www.youtube.com/watch?v=WAfJXmwDJpg&feature=youtu.be

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,imgjpeg,decor,snap,move,gnomecompat,imgpng,vpswitch,place,grid,resize,text,imgsvg,unitymtgrabhandles,regex,mousepoll,session,wall,animation,fade,expo,workarounds,scale,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Apr 25 22:38:19 2014
InstallationDate: Installed on 2012-05-02 (723 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-21 (3 days ago)

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

[Desktop-packages] [Bug 1284981] Re: Locally-integrated menus stop working in Virtualbox and Transmission

2015-01-19 Thread Mateusz Stachowski

*** This bug is a duplicate of bug 1312137 ***
https://bugs.launchpad.net/bugs/1312137

Looks like the fixes for other LIM not clickable bugs that landed in
15.04 development release resolved this bug.

Besides VirtualBox is a Qt app and this bug is a duplicate of Bug
#1312137 which was fixed recently in Unity release for Vivid.

** This bug has been marked a duplicate of bug 1312137
   Local menus broken for Qt apps after opening dialog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1284981

Title:
  Locally-integrated menus stop working in Virtualbox and Transmission

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  With (the absolutely awesome) locally-integrated menus enabled, if you
  open the VirtualBox the menus initially work as expected, ie they
  appear in VirtualBox's titlebar when you hover the mouse over it.

  But if you open a popup window by clicking on New or Settings and then
  close it, it the menus no longer appear when you hover over the
  titlebar.

  One workaround is that the menus start working again if you focus on
  another application's window and then click on VirtualBox again so it
  regains focus, so it's as if the popup window has retained the focus
  for LIM even once it is closed.

  Also worth noting is that if you open a VirtualBox popup window and
  focus on another application without closing the VirtualBox popup
  window, when you go back to the popup window and close it, the menus
  work as expected.

  I tried reproducing this using the popup windows in Synaptic, gnome-
  disks, and gnome-terminal, but they all work fine.

  I'm running virtualbox-4.3 4.3.8-92456~Ubuntu~raring.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
  Uname: Linux 3.13.0-13-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb 26 13:31:49 2014
  InstallationDate: Installed on 2014-02-08 (17 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140207)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

2015-01-17 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Update manager is really small and not resizeable

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Triaged
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  : "The Updates
  Available window should be manually resizable only when it is in this
  expanded state."

  [ Test Case ]

  Run the Ubuntu update manager and attempt to resize the window.  See
  above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regressions.

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

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

[Desktop-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

2015-01-17 Thread Mateusz Stachowski

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Invalid
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [ Impact ]

  Window shadows can be seen on adjacent workspaces.

  [ Test Case ]

  To reproduce, launch a whole bunch (10, 20, a lot) of windows on
  workspace 2, and position them on or near the right edge.  Then switch
  to workspace 1, and observe the massive black blob on the left of the
  screen.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash or lockup.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

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

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

[Desktop-packages] [Bug 881376] Re: "Low disk space" warning popping up repeatedly.

2014-11-02 Thread Mateusz Stachowski

I also confirm that this is still a problem in 14.04.1. Although in my
case it started to be a problem recently.

I had two partitions excluded already from popping those messages and
they were quiet. But for some reason when I reached low disk space on
another partition they also started to bug me with low disk space
messages.

The curious thing is that if I check "Don't show any warnings again for
this file system" and then press "Ignore" the messages will display
endlessly for all the partitions with low disk space. But if I just
click "Ignore" for the first partition that display low disk space
dialog then I won't get any  more such messages (it will end on that
one).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/881376

Title:
  "Low disk space" warning popping up repeatedly.

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” source package in Precise:
  Triaged

Bug description:
  On Ubuntu 11.10 Oneiric Ocelot.
  Since that upgrade, I repeatedly get the warning

  "Low Disk Space"
  "The volume "..." has only [..] MB disk space remaining.
  This is for a few Windows partitions on a multiboot machine, which I mount by 
default on Linux startup.

  The problem:
  - I could not care less about disk space on these partitions, while on Linux. 
I want to take care of them while on Windows.
  - The dialog is showing up repeatedly for the same disk.
  - It's a disruptive popup dialog, instead of being a more subtle bubble 
notification (this is being discussed in a feature request somewhere on 
launchpad).
  - The "Don't show any warnings again for this file system" does not have any 
effect. Yes, it does change a setting somewhere in system settings, but the 
popup will show up nevertheless.
  - Trying to change the threshold or the exclude directories via system 
settings did not help either.
  - I did not find how to uninstall or disable this new "feature".

  This is just one of the many things that make the new 11.10 a horrible
  experience for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/881376/+subscriptions

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

[Desktop-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

Yes this is much better than having no solution at all and if this is
the best that can be done then it should land in main archives.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Desktop-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

Well VirtualBox grabs the keyboard even in widowed mode. At least the
Alt+F2 , Ctrl+Alt+T, Super+S and Super+W shortcuts are properly grabbed.

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Desktop-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open

The version in trusty-proposed works as per "Desired resolution". The
user is warned about other users being logged in and that those other
sessions will also be closed.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1281058

Title:
  [UIFe] The system shutdowns when multiple accounts are open

Status in Ayatana Design:
  Fix Committed
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  New
Status in “systemd” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  Fix Committed
Status in “unity-greeter” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Other users logged into a system may loose work if another user shuts
  down/reboots a system.  Data loss is not a Good Thing.

  [Test Case]

  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  [ Regression Potential]

  None.

  --
  Desired resolution:

  - Add a warning message informing the user that other users are logged in and 
then shutting down will also close their sessions as proposed in the mockup 
attached to comment #12
  - The warning message should be "Other users are currently logged in to this 
computer, shutting down now will also close these other sessions"

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

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

[Desktop-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

The trusty-proposed packages with suposedly contain fix for this bug
didn't actually fix it. The Super key is still intercepted in windowed
mode and Dash opens in both VirtualBox (tested with 12.04.4 and 14.04)
and in regular session. When running VirtualBox in fullscreen the Dash
opens only in virtual machine.

Also in virt-manager the Super key isn't intercepted when you open Dash
but is intercepted when you hold the Super key to display shortcuts
overlay.

** Tags added: verification-failed

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

2014-07-08 Thread Mateusz Stachowski

I confirm what Simon Buchan wrote in his comment.

- I start VirtualBox with Ubuntu 12.04.4 LTS as guest, fullscreen
- Wait for Unity lockscreen (timeout set to 1 minute for testing)
- Keyboard input does not seem to respond, mouse works fine.

Now there is other workaround to get input not going to the VM but to
lockscreen text box. I just need to switch off fullscreen for the VM
with keyboard shortcut Host + F (by default Right Ctrl + F) and then
open indicators and finally switch to the lockscreen password text box.

I have only one monitor.

@Simon this particular problem might be resolved with the Unity SRU
update. Christopher Townsend mentioned in comment #23 that the Compiz
SRU doesn't resolve all the problems and that Unity SRU has still some
fixes which should make this bettter.

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options->Focus & Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8< 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower "['b']"
  gsettings set org.gnome.desktop.wm.keybindings maximize "['Up']"
  gsettings set org.gnome.desktop.wm.keybindings unmaximize "['Down']"
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8< 

  But after restarting compiz, it changes the settings to:

  --- 8< 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['Up']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['Down']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8< 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=8f327c01-56d7-401c-8bd1-5442854e3c85 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET46WW (1.16 )
  dmi.board.name: 3323REG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3323REG
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1
  version.xserver-xorg-core: xserve

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Compiz can't resize a window vertically AND horizontally with
  keyboard.

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some users like to use the keyboard for many functions including
  resizing windows.  Due to this bug, resizing windows with the keyboard
  is not very easy.

  [Test case]

  1. Open a window such as gedit.  Make sure it is not maximized.
  2. Initiate keyboard resizing by hitting Alt+Space, then r.
  3. Use cursor keys to resize the window.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  when trying to resize a window using the keyboard (ALT+SPACE, then
  choose resize from the menu and then use the keyboard arrows) its not
  possible to resize both horizontally and vertically - like its
  possible using the mouse by grabbing a window corner.

  Normally one would expect that its possible to press the right arrow
  key repeatedly to enlarge the window horizontally, and then press the
  down arrow key repeatedly to enlarge the window vertically, before
  pressing ENTER to submit the changes

  What actually happens is that once the second button is pressed (down in this 
case), the previous dimension (horizontal) reverts to is old size and the new 
dimension is being adjusted. Try to press right arrow and the vertical 
dimension reverts back to its old value. In order to successfully resize a 
window both vertically and horizontally one needs to:
  1. start a resize action
  2. resize in one direction
  3. submit the changes
  4. start another resize action
  5. resize in the other direction
  6. submit the changes

  Making it twice as complicated to do. This may or may not be related
  to desktop effects being enabled, I haven't disabled them to check yet
  but I do not remember this being a problem with standard Metacity.

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-07-01 Thread Mateusz Stachowski

And how did it go?

If the newer version from proposed resolved the issue for you then
please change the tag to verification-done and if it didn't to
verification-failed.

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1333045] Re: Apps "locked" in a launcher-position get moved when opening app from dash

2014-06-28 Thread Mateusz Stachowski

Does this happen with other programs or only Writer.

In fresh installs Writer icon is always on third position and then you
have Calc and Impress so maybe that got something to do with this.

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

Title:
  Apps "locked" in a launcher-position get moved when opening app from
  dash

Status in Unity:
  Confirmed
Status in “compiz” package in Ubuntu:
  New
Status in “launcher” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  I have 9 apps in "locked" positions on the launcher. when I open an
  application from Dash (an app that is not locked to the launcher) the
  app opens in slot #3 on the launcher, pushing down "locked" icons from
  3-9.

  For example, I have Thunderbird locked to position 3 on the launcher.
  If I open Writer (which is an app not locked to my launcher), it opens
  in slot #3 on the launcher and thunderbird is shoved down to position
  #4 on the launcher. As a consequence, whenever I tap Super+3 to open
  Thunderbird, I end up opening Writer.

  Apps in locked positions on the launcher should be fixed and should
  not move when a new app is opened. Apps opened from the dash should
  appear on the Launcher at the end of the Launcher-List (below the
  locked-icons).

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

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

[Desktop-packages] [Bug 1335125] Re: Wrong number of ticks by application icon in launcher

2014-06-28 Thread Mateusz Stachowski

*** This bug is a duplicate of bug 1283775 ***
https://bugs.launchpad.net/bugs/1283775

** This bug has been marked a duplicate of bug 1283775
   Launcher: icon pips are not always updated properly

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1335125

Title:
  Wrong number of ticks by application icon in launcher

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 14.04 I've noticed that the number of ticks/markers
  that indicates the number of windows a the side of an application's
  icon is often incorrect. This seems to apply to Gnome Terminal,
  Firefox and Thunderbird and more.

  Reproduction #1:
  Open a terminal.
  Right click the launcher icon and choose "New terminal".
  Observe there's only one ticks.
  Left click the launcher icon to expose both terminals.
  Observe the number of ticks is corrected.
  Choose either, it doesn't matter.
  Close one of the terminals.
  Observe there's still two ticks.

  The number of ticks doesn't seem to refresh until something happens in
  the launcher - either you click on something in the launcher, but the
  ticks seems to correct themselves at other times that I can't quite
  put my finger on.

  This is extremely distracting and interrupts work all the time
  checking to see what's left open to find that there's nothing there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140423-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 27 14:26:07 2014
  DistUpgraded: 2014-04-28 12:24:37,637 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1033]
  InstallationDate: Installed on 2013-05-07 (415 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Calpella platform
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=1aab217a-e362-4aab-9283-0b04525b2bdf ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (60 days ago)
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1681IG6 VER.109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: Micro-Star International
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Micro-Star International
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1681IG6VER.109:bd07/21/2010:svnMicro-StarInternational:pnCalpellaplatform:pvrVer.001:rvnMicro-StarInternational:rnTobefilledbyO.E.M.:rvrVer.001:cvnMicro-StarInternational:ct9:cvrVer.001:
  dmi.product.name: Calpella platform
  dmi.product.version: Ver.001
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jun 26 09:47:01 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   input

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

2014-06-27 Thread Mateusz Stachowski

Doug what you describe in comment #10 is a different bug. This bug was
for situation when you locked the screen with Super+L or Ctrl+Alt+L and
while you had the lockscreen the monitor never blanked off.

BTW I tested the situation described by you in comment #10 and didn't
have any problems.

I set the screen blanking to 1 minute and screen locking to 2 minutes
and the screen didn't turn on even after 5 minutes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1292041

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in “gnome-screensaver” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-06-26 Thread Mateusz Stachowski

Jason you should have the version that is listed in comment #6.

apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.1+14.04.20140623-0ubuntu1

This version is in Trusty proposed. You can enable proposed by going to
"Software & Updates" and then on actualisations tab check trusty-
proposed.

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1184720] Re: Nautilus does not properly navigate symbolic links

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Nautilus does not properly navigate symbolic links

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “nautilus” source package in Trusty:
  Fix Committed

Bug description:
  Impact:
  Navigating symlinks in nautilus leads to incorrect directories

  Test case:
  1. Create a directory in Home called Folder
  2. Right click on Folder in Nautilus and select 'make link'
  3. Drag created link to Desktop
  4. Double-click on Link to Folder to open it in Nautilus

  Clicking the back arrow in Nautilus behaves as it should--it takes you
  back to Desktop, not the parent folder of the target of the link.

  However, the architecture displayed near the top of the Nautilus
  window shows the parent directory of the target, not of the link
  (i.e., it shows [Home][Folder], not [Home][Desktop][Link to Folder]

  Pressing alt+up also takes you to the parent of the target, not the
  link.

  Regression potential:
  check that creating symlinks and navigating those works correctly

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

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

[Desktop-packages] [Bug 1087090] Re: [raring][regression] Window management - Maximized windows aren't fullscreen in the workspace switcher

Christopher for some reason this bug is again listed for verification
process in Pending SRUs for Trusty.

http://people.canonical.com/~ubuntu-archive/pending-sru.html

Seems like it was incorrectly placed on that listing because here there
is no SRU test request and of course you reverted those changes in
updated packages.

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

Title:
  [raring][regression] Window management - Maximized windows aren't
  fullscreen in the workspace switcher

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Having a maximized window in Expo mode has kind of a jarring effect
  with a blank space where the Launcher and Panel should be.  This leads
  to poor visual experience for users.

  [Test case]

  1. Make sure workspaces are enabled.
  2. Open a window and make sure it's maximized.
  3. Initiate Expo by hitting Super+S.

  [Regression potential]

  None identified.

  * Debdiff is found at *

  Original description:

  Hello,

  Since today's updates of compiz, the workspace switcher don't work the
  same way as before. When you have a maximized windows and you click on
  the launcher's workspace icon, the workspace switcher appears but the
  maximized windows aren't fullscreened. You can see the voids that
  represent the launcher and the panel.

  I attached a screenshot for a better understanding of the problem.

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Compiz can't resize a window vertically AND horizontally with
  keyboard.

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some users like to use the keyboard for many functions including
  resizing windows.  Due to this bug, resizing windows with the keyboard
  is not very easy.

  [Test case]

  1. Open a window such as gedit.  Make sure it is not maximized.
  2. Initiate keyboard resizing by hitting Alt+Space, then r.
  3. Use cursor keys to resize the window.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  when trying to resize a window using the keyboard (ALT+SPACE, then
  choose resize from the menu and then use the keyboard arrows) its not
  possible to resize both horizontally and vertically - like its
  possible using the mouse by grabbing a window corner.

  Normally one would expect that its possible to press the right arrow
  key repeatedly to enlarge the window horizontally, and then press the
  down arrow key repeatedly to enlarge the window vertically, before
  pressing ENTER to submit the changes

  What actually happens is that once the second button is pressed (down in this 
case), the previous dimension (horizontal) reverts to is old size and the new 
dimension is being adjusted. Try to press right arrow and the vertical 
dimension reverts back to its old value. In order to successfully resize a 
window both vertically and horizontally one needs to:
  1. start a resize action
  2. resize in one direction
  3. submit the changes
  4. start another resize action
  5. resize in the other direction
  6. submit the changes

  Making it twice as complicated to do. This may or may not be related
  to desktop effects being enabled, I haven't disabled them to check yet
  but I do not remember this being a problem with standard Metacity.

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

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

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

I also confirm that it works and I also tested with disabling click to
focus. Several reboots later and this setting remains unset and focus
follows mouse is in use.

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

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options->Focus & Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8< 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower "['b']"
  gsettings set org.gnome.desktop.wm.keybindings maximize "['Up']"
  gsettings set org.gnome.desktop.wm.keybindings unmaximize "['Down']"
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8< 

  But after restarting compiz, it changes the settings to:

  --- 8< 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['Up']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['Down']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8< 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=8f327c01-56d7-401c-8bd1-5442854e3c85 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET46WW (1.16 )
  dmi.board.name: 3323REG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3323REG
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1

[Desktop-packages] [Bug 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse

I have 9600 GT and don't have this bug. I'm using 337 drivers and
currently updating to 340. Also I have proposed enabled on 14.04 LTS.

Everything here is smooth but I had some flickering launcher tooltips in
Unity. This happens very, very rarely and I don't know what triggers it
exactly.

I noticed that people here have newer NVIDIA GPU. Maybe this only
happens for some of those newer architecture graphics cards.

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

Title:
  [334] Parts of the UI randomly flicker when moving the mouse

Status in Compiz:
  Triaged
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  Nvidia 334.21 makes the UI jearky, googled and found this on Nvidia
  forums:

  "This looks like a problem caused by the system compositor not
  properly waiting for X rendering to finish before performing OpenGL
  rendering in response. The GL_EXT_x11_sync_object extension was
  designed to solve this problem, but it looks like cogl (the back-end
  library used by GNOME's compositor) doesn't use it yet. "

  more details:
  
https://devtalk.nvidia.com/default/topic/690704/linux/-334-16-parts-of-the-ui-randomly-flicker-when-moving-the-mouse/post/4128101/#4128101
  --- 
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É uma directoria: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-16-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   nvidia-331-updates, 331.38, 3.13.0-16-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:34fe]
  InstallationDate: Installed on 2014-03-03 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d2c3632d-4280-4961-91c8-0b7d3fe95be1 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Tags:  trusty trusty possible-manual-nvidia-install ubuntu single-occurrence 
reproducible compiz-0.9
  Uname: Linux 3.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0620
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-ASUS-SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0620:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-ASUS-SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:50:58 2014
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6

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

-- 
Mailing lis

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

I checked the Test Case from bug description.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options->Focus & Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8< 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower "['b']"
  gsettings set org.gnome.desktop.wm.keybindings maximize "['Up']"
  gsettings set org.gnome.desktop.wm.keybindings unmaximize "['Down']"
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8< 

  But after restarting compiz, it changes the settings to:

  --- 8< 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['Up']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['Down']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8< 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=8f327c01-56d7-401c-8bd1-5442854e3c85 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET46WW (1.16 )
  dmi.board.name: 3323REG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3323REG
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

I've checked the described Test Case with virt-manager and the window
appears in top left corner with window decoration fully visible.

I also didn't have any problems with gnome-disk-utility, Firefox,
Chrome, Image Viewer and LibreOffice.

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application