[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv

[Martin Pitt]

** Changed in: unity
   Status: Fix Committed => Fix Released

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

Title:
  Cannot uninstall upstart and install systemd-sysv

Status in Unity:
  Fix Released
Status in “avahi” package in Ubuntu:
  Fix Released
Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dovecot” package in Ubuntu:
  Fix Released
Status in “friendly-recovery” package in Ubuntu:
  Fix Released
Status in “hockeypuck” package in Ubuntu:
  Fix Released
Status in “pay-service” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “sysvinit” package in Ubuntu:
  Fix Released
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  upstart is currently quite deeply wired into our dependencies. Even in
  a minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:

  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).

  On a desktop the list is quite a bit longer:

   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd 
script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop 
that along with upstart for systemd images, systemd has readahead built in)
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
   init depends on upstart. (Not important right now, switch to alternative 
deps once systemd is ready)

  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are
  using session upstart on the desktop (unity-services etc.), for this
  we probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

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

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Treviño]

** Description changed:

- When scrolling on indicator-sound using the horizontal scrolling the
- result is the opposite to what we expect in unity (left scrolling
- increases the volume and right scrolling decreases it), while in general
- is not handled at all for indicator-ng indicators as both left and right
- scrolling always ends up in a "+1" delta scroll.
+ [Impact]
+ When scrolling on indicator-sound using the horizontal scrolling the result 
is the opposite to what we expect in unity (left scrolling increases the volume 
and right scrolling decreases it), while in general is not handled at all for 
indicator-ng indicators as both left and right scrolling always ends up in a 
"+1" delta scroll.
+ 
+ [Test case]
+ 1. Hover Indicator-sound in unity
+ 2. Scroll left: the volume should be reduced
+ 3. Scroll right: the volume should be increased
+ 
+ [Regression potential]
+ The horizontal scroll direction might be inverted with some touchpads

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  When scrolling on indicator-sound using the horizontal scrolling the result 
is the opposite to what we expect in unity (left scrolling increases the volume 
and right scrolling decreases it), while in general is not handled at all for 
indicator-ng indicators as both left and right scrolling always ends up in a 
"+1" delta scroll.

  [Test case]
  1. Hover Indicator-sound in unity
  2. Scroll left: the volume should be reduced
  3. Scroll right: the volume should be increased

  [Regression potential]
  The horizontal scroll direction might be inverted with some touchpads

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

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

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Treviño]

** Description changed:

+ [Impact]
+ Unity crashes when unlocking the session
+ 
+ [Test case]
+ 1. Lock the session
+ 2. Unlock the session
+ 3. No crash should happen
+ 
+ [Regression potential]
+ None
+ 
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that I
  was still seeing it quite a while ago, but got no reply to that.
  
  Crashes are being experienced in multiple machines, while unlocking the
  screen.  The stacktraces vary, but they always fail in the same function
  and same line.
  
  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
-() from /usr/lib/compiz/libunityshell.so
+    () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
-   from /usr/lib/compiz/libopengl.so
+   from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
-   from /usr/lib/compiz/libopengl.so
+   from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
-   from /usr/lib/compiz/libcomposite.so
+   from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()
  
  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
-   from /usr/lib/compiz/libopengl.so
+   from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
-   from /usr/lib/compiz/libopengl.so
+   from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
-   from /usr/lib/compiz/libcomposite.so
+   from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7f0076779ce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libgli

[Dx-packages] [Bug 1340992] Re: It's not possible to scroll over the dash overlay scrollbars as it happens in gtk applications

[Treviño]

** Description changed:

- Scrolling over the scrollbars thumbs makes the thumb to disappear
- instead that apply the scroll to its view.
+ [Impact]
+ Scrolling over the scrollbars thumbs makes the thumb to disappear instead 
that apply the scroll to its view.
+ 
+ [Test case]
+ 1. Open the dash, expand the search results so that scroll bars show
+ 2. Move the mouse over the scrollbar to make the thumb to show, and hover it
+ 3. Scroll over the scrollbars thumb and, and the related scrolled view should
+be properly scrolled up/down.

** Description changed:

  [Impact]
  Scrolling over the scrollbars thumbs makes the thumb to disappear instead 
that apply the scroll to its view.
  
  [Test case]
  1. Open the dash, expand the search results so that scroll bars show
  2. Move the mouse over the scrollbar to make the thumb to show, and hover it
  3. Scroll over the scrollbars thumb and, and the related scrolled view should
-be properly scrolled up/down.
+    be properly scrolled up/down.
+ 
+ [Regression potential]
+ Nothing known

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

Title:
  It's not possible to scroll over the dash overlay scrollbars as it
  happens in gtk applications

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Scrolling over the scrollbars thumbs makes the thumb to disappear instead 
that apply the scroll to its view.

  [Test case]
  1. Open the dash, expand the search results so that scroll bars show
  2. Move the mouse over the scrollbar to make the thumb to show, and hover it
  3. Scroll over the scrollbars thumb and, and the related scrolled view should
     be properly scrolled up/down.

  [Regression potential]
  Nothing known

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

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

[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.

[Treviño]

** Description changed:

- When the touchpad is used to scroll the dash sometimes scroll down is dected 
as scroll up and vice versa.
- Two fingers scroll must be ON!
- This is because horizontal scrolling is now enabled by default and can't be 
disabled using g-c-c.
+ [Impact]
+ Dash content flickers when two-finger scrolling on the touchpad
+ 
+ [Test case]
+ 1. Enable two fingers scroll from Unity Control Center -> Mouse and Touchpad
+ 2. Open the unity dash, expand the search results and start scrolling 
vertically
+ 3. Content should not flicker and should ignore horizontal scroll events
+ 
+ [Regression potential]
+ Scrolling on dash content does not work properly

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

Title:
  Dash content flickers when the touchpad is used to scroll it.

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Dash content flickers when two-finger scrolling on the touchpad

  [Test case]
  1. Enable two fingers scroll from Unity Control Center -> Mouse and Touchpad
  2. Open the unity dash, expand the search results and start scrolling 
vertically
  3. Content should not flicker and should ignore horizontal scroll events

  [Regression potential]
  Scrolling on dash content does not work properly

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

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

[Dx-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

[Treviño]

** Description changed:

+ [Impact]
+ Scrolling on the Alt+Tab has invalid behavior:
+ - Scrolling down, moves to the previous icon/window
+ - Scrolling up, moves to the next icon/window
+ - Scrolling left, moves to the next icon/window
+ - Scrolling right, moves to the previous icon/window
+ 
+ [Test case]
  1. Press Alt+Tab
- 2. While pressing use mouse scroll wheel to scroll vertically (and if 
possible horizontally)
+ 2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, 
if possible, horizontally)
  
  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window
  
- Actual behavior:
- - Scrolling down, moves to the previous icon/window
- - Scrolling up, moves to the next icon/window
- - Scrolling left, moves to the next icon/window
- - Scrolling right, moves to the previous icon/window
+ [Regression potential]
+ Vertical scrolling has not been touched by the change, so there's no 
possibility to regress in this sense.

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

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Scrolling on the Alt+Tab has invalid behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

  [Test case]
  1. Press Alt+Tab
  2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, 
if possible, horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  [Regression potential]
  Vertical scrolling has not been touched by the change, so there's no 
possibility to regress in this sense.

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

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

[Dx-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

[Treviño]

** Branch linked: lp:~unity-team/nux/sru-4.0.6.1

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

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Scrolling on the Alt+Tab has invalid behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

  [Test case]
  1. Press Alt+Tab
  2. While pressing the keys, use mouse scroll wheel to scroll vertically (and, 
if possible, horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  [Regression potential]
  Vertical scrolling has not been touched by the change, so there's no 
possibility to regress in this sense.

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

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

[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.

[Treviño]

** Branch linked: lp:~unity-team/nux/sru-4.0.6.1

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

Title:
  Dash content flickers when the touchpad is used to scroll it.

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  Fix Released

Bug description:
  When the touchpad is used to scroll the dash sometimes scroll down is dected 
as scroll up and vice versa.
  Two fingers scroll must be ON!
  This is because horizontal scrolling is now enabled by default and can't be 
disabled using g-c-c.

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

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

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Treviño]

** Branch linked: lp:~unity-team/nux/sru-4.0.6.1

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When scrolling on indicator-sound using the horizontal scrolling the
  result is the opposite to what we expect in unity (left scrolling
  increases the volume and right scrolling decreases it), while in
  general is not handled at all for indicator-ng indicators as both left
  and right scrolling always ends up in a "+1" delta scroll.

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

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

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/nux/sru-4.0.6.1

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Nux:
  In Progress
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7f0076779ce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7f0

[Dx-packages] [Bug 1347735] Re: Lockscreen capslock detection doesn't work well with remapped capslocks

[Treviño]

** Description changed:

- Hi,
+ [Impact]
+ Remapped keys to activate the caps-lock are not correctly detected by the 
unity lockscreen
+ 
+ [Test case]
+ 1. Configure the keyboard so that "Both shifts together toggles CapsLock"
+ 2. Lock the screen using Super+L or menus
+ 3. Press both shifts together to turn the capslock on
+ 4. The lockscreen input field should show a warning
+ 5. Press the shifts again, and the warning should be hidden
+ 
+ [Regression potential]
+ None
+ 
+ 
+ -
  
  Version: 7.2.2+14.04.20140714-0ubuntu1 (trusty)
  
  Some users like to remap the way the activate capslock.  For example,
  using gnome-tweak-tool it's possible to set the CapsLock key to behave
  as an extra Ctrl, or an extra Alt (or several other extras) and then set
  "Both shifts together toggle CapsLock".
  
  This works perfectly well inside Unity, the hardware keyboard led
  indicator shows up, etc.  However, the lockscreen detector doesn't
  correctly warn or not warn when this setup is used.
  
  * If the lockscreen was activated with capslock on, then the double-shift 
makes capslock go away, but not the warning.
  * If the lockscreen was activated with capslock off, then the double-shift 
makes capslock on, but no warning shows up.
  
  I believe the problem is in this piece of code in unity-
  shared/TextInput.cpp:
  
  void TextInput::OnKeyUp(unsigned keysym,
- unsigned long keycode,
- unsigned long state)
+ unsigned long keycode,
+ unsigned long state)
  {
-   if (!caps_lock_on && keysym == NUX_VK_CAPITAL)
- caps_lock_on = true;
-   else if (caps_lock_on && keysym == NUX_VK_CAPITAL)
- caps_lock_on = false;
+   if (!caps_lock_on && keysym == NUX_VK_CAPITAL)
+ caps_lock_on = true;
+   else if (caps_lock_on && keysym == NUX_VK_CAPITAL)
+ caps_lock_on = false;
  }
  
  This is checking for specific key, instead of the fact that CapsLock was
  activated or not.

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

Title:
  Lockscreen capslock detection doesn't work well with remapped
  capslocks

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Remapped keys to activate the caps-lock are not correctly detected by the 
unity lockscreen

  [Test case]
  1. Configure the keyboard so that "Both shifts together toggles CapsLock"
  2. Lock the screen using Super+L or menus
  3. Press both shifts together to turn the capslock on
  4. The lockscreen input field should show a warning
  5. Press the shifts again, and the warning should be hidden

  [Regression potential]
  None

  
  -

  Version: 7.2.2+14.04.20140714-0ubuntu1 (trusty)

  Some users like to remap the way the activate capslock.  For example,
  using gnome-tweak-tool it's possible to set the CapsLock key to behave
  as an extra Ctrl, or an extra Alt (or several other extras) and then
  set "Both shifts together toggle CapsLock".

  This works perfectly well inside Unity, the hardware keyboard led
  indicator shows up, etc.  However, the lockscreen detector doesn't
  correctly warn or not warn when this setup is used.

  * If the lockscreen was activated with capslock on, then the double-shift 
makes capslock go away, but not the warning.
  * If the lockscreen was activated with capslock off, then the double-shift 
makes capslock on, but no warning shows up.

  I believe the problem is in this piece of code in unity-
  shared/TextInput.cpp:

  void TextInput::OnKeyUp(unsigned keysym,
  unsigned long keycode,
  unsigned long state)
  {
    if (!caps_lock_on && keysym == NUX_VK_CAPITAL)
  caps_lock_on = true;
    else if (caps_lock_on && keysym == NUX_VK_CAPITAL)
  caps_lock_on = false;
  }

  This is checking for specific key, instead of the fact that CapsLock
  was activated or not.

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

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

[Dx-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

[Treviño]

** Also affects: nux
   Importance: Undecided
   Status: New

** Changed in: nux
   Status: New => Fix Committed

** Changed in: nux
   Importance: Undecided => Medium

** Changed in: nux
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux
Milestone: None => 4.0.7

** Also affects: nux/trusty
   Importance: Undecided
   Status: New

** Changed in: nux/trusty
   Importance: Undecided => Medium

** Changed in: nux/trusty
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux/trusty
Milestone: None => 4.0.6.1

** Changed in: nux/trusty
   Status: New => In Progress

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

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  1. Press Alt+Tab
  2. While pressing use mouse scroll wheel to scroll vertically (and if 
possible horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  Actual behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

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

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

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Treviño]

** Also affects: nux/trusty
   Importance: Undecided
   Status: New

** Changed in: nux/trusty
   Status: New => In Progress

** Changed in: nux/trusty
   Importance: Undecided => High

** Changed in: nux/trusty
 Assignee: (unassigned) => Erkin Bahceci (cornelius1)

** Changed in: nux/trusty
Milestone: None => 4.0.6.1

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Nux:
  In Progress
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libc

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Treviño]

** Changed in: nux/trusty
Milestone: None => 4.0.6.1

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When scrolling on indicator-sound using the horizontal scrolling the
  result is the opposite to what we expect in unity (left scrolling
  increases the volume and right scrolling decreases it), while in
  general is not handled at all for indicator-ng indicators as both left
  and right scrolling always ends up in a "+1" delta scroll.

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

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

[Dx-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.

[Treviño]

** Changed in: nux/trusty
   Status: Triaged => In Progress

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

Title:
  Dash content flickers when the touchpad is used to scroll it.

Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in “nux” package in Ubuntu:
  Fix Released

Bug description:
  When the touchpad is used to scroll the dash sometimes scroll down is dected 
as scroll up and vice versa.
  Two fingers scroll must be ON!
  This is because horizontal scrolling is now enabled by default and can't be 
disabled using g-c-c.

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

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

[Dx-packages] [Bug 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Treviño]

** Branch linked: lp:~3v1n0/nux/horizontal-scroll-delta

** Also affects: nux
   Importance: Undecided
   Status: New

** Changed in: nux
   Status: New => Fix Committed

** Changed in: nux
   Importance: Undecided => Medium

** Changed in: nux
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux
Milestone: None => 4.0.7

** Also affects: nux/trusty
   Importance: Undecided
   Status: New

** Changed in: nux/trusty
   Status: New => In Progress

** Changed in: nux/trusty
   Importance: Undecided => Medium

** Changed in: nux/trusty
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When scrolling on indicator-sound using the horizontal scrolling the
  result is the opposite to what we expect in unity (left scrolling
  increases the volume and right scrolling decreases it), while in
  general is not handled at all for indicator-ng indicators as both left
  and right scrolling always ends up in a "+1" delta scroll.

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

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

[Dx-packages] [Bug 1342208] Re: Scroll wheel uses inverted logic to switch between applications/windows in the switcher

[Treviño]

** Branch linked: lp:~3v1n0/nux/horizontal-scroll-delta

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

Title:
  Scroll wheel uses inverted logic to switch between
  applications/windows in the switcher

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  1. Press Alt+Tab
  2. While pressing use mouse scroll wheel to scroll vertically (and if 
possible horizontally)

  Expected behavior:
  - Scrolling down, moves to the next icon/window
  - Scrolling up, moves to the previous icon/window
  - Scrolling left, moves to the previous icon/window
  - Scrolling right, moves to the next icon/window

  Actual behavior:
  - Scrolling down, moves to the previous icon/window
  - Scrolling up, moves to the next icon/window
  - Scrolling left, moves to the next icon/window
  - Scrolling right, moves to the previous icon/window

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

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

[Dx-packages] [Bug 1342152] Re: GetActive method for the screensaver reports False even when screensaver is active

[Treviño]

Lockscreen != Screensaver.

So, this is false when the screen is not turned off for power saving
reasons, and that's fine.

You can instead check if the session has been locked using this call instead:
  gdbus call --session --dest com.canonical.Unity \
--object-path /com/canonical/Unity/Session \
--method com.canonical.Unity.Session.IsLocked

** Changed in: unity
   Status: New => Won't Fix

** Changed in: unity (Ubuntu)
   Status: New => Won't Fix

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

Title:
  GetActive method for the screensaver reports False even when
  screensaver is active

Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Won't Fix

Bug description:
  Hi!

  unity version: 7.2.1+14.04.20140513-0ubuntu2 (Trusty)

  I have an application that checks the state of the screen saver via
  dbus.  Unity implements an interface for using org.gnome.ScreenSaver,
  so as far as I can see, this should work (Python example):

  import dbus
  session_bus = dbus.SessionBus()
  session_manager = session_bus.get_object('org.gnome.ScreenSaver', 
'/org/gnome/ScreenSaver')
  session_manager.GetActive(dbus_interface='org.gnome.ScreenSaver')

  This correctly returns False when the screensaver is not active,
  however, when I lock the screen and check (using a call to
  time.sleep), it also returns False.

  I have checked that calling:
  session_manager.SetActive(True, dbus_interface='org.gnome.ScreenSaver')

  Correctly activates the screensaver, so that part seems to be working.
  However, even in that case, if after activating the screensaver I call
  GetActive it returns False.

  From looking at the code [1], I suspect the problem is that when I
  lock the screen via Ctrl-Alt-L, the internal _active member is not
  being set to True, but I'm not sure what might be going on with the
  variable after SetActive is called.

  [1]: http://bazaar.launchpad.net/~unity-greeter-team/unity-
  greeter/trunk/view/head:/src/settings-daemon.vala#L172

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

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

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Treviño]

** Changed in: nux
   Status: New => In Progress

** Changed in: nux
   Importance: Undecided => High

** Changed in: nux
Milestone: None => 4.0.7

** Changed in: nux
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
   Status: Confirmed => Won't Fix

** Changed in: unity (Ubuntu)
   Status: Confirmed => Won't Fix

** No longer affects: unity

** No longer affects: unity (Ubuntu)

** Changed in: nux (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: nux (Ubuntu)
   Importance: Undecided => High

** Changed in: nux
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Erkin Bahceci (cornelius1)

** Changed in: nux (Ubuntu)
 Assignee: (unassigned) => Erkin Bahceci (cornelius1)

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Nux:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in Com

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/nux/areas-unqueue-relayout

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Nux:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7f0076779ce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7f007677a048 in ?? () from /lib/x86

[Dx-packages] [Bug 1340996] Re: Overlay scrollbars doesn't scale to match the current DPI settings

[Treviño]

** Description changed:

- Dash scrollbars should scale, matching the current DPI settings for the
- monitor they're in.
+ [Impact]
+ Dash scrollbars do not respect the configured monitor scaling
+ 
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
+different from 1.0 (might be both bigger and smaller, your choice).
+ 2. Open the dash, expand the results so that the scrollbars show
+ 3. Hover a scrollbar and the overlay scrollbar thumb should appear
+ 4. Both the scrollbar and the thumb should be scaled matching the current DPI 
settings
+for the monitor the dash is in
+ 
+ The same should happen in previews.
+ 
+ [Regression potential]
+ Very low. A possibility might be missing scrollbars somewhere in the dash.

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

Title:
  Overlay scrollbars doesn't scale to match the current DPI settings

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Dash scrollbars do not respect the configured monitor scaling

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, expand the results so that the scrollbars show
  3. Hover a scrollbar and the overlay scrollbar thumb should appear
  4. Both the scrollbar and the thumb should be scaled matching the current DPI 
settings
 for the monitor the dash is in

  The same should happen in previews.

  [Regression potential]
  Very low. A possibility might be missing scrollbars somewhere in the dash.

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

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

[Dx-packages] [Bug 1340477] Re: The HUD doesn't support scaling on HiDPI monitors

[Treviño]

** Description changed:

- The HUD is not scaled in HiDPI monitors
+ [Impact]
+ The HUD is not scaled on HiDPI monitors
+ 
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
+different from 1.0 (might be both bigger and smaller, your choice).
+ 2. Open the Hud
+ 3. Both the view, the text and the search results should be properly scaled to
+match current monitor scaling factor
+ 
+ [Regression potential]
+ Very low, but the hud might have visual issues (nothing found so far)

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

Title:
  The HUD doesn't support scaling on HiDPI monitors

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  The HUD is not scaled on HiDPI monitors

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the Hud
  3. Both the view, the text and the search results should be properly scaled to
 match current monitor scaling factor

  [Regression potential]
  Very low, but the hud might have visual issues (nothing found so far)

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

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

[Dx-packages] [Bug 1340394] Re: Overlay borders aren't scaled to match monitor DPI scaling

[Treviño]

** Description changed:

+ [Impact]
  The dash or Hud borders aren't scaled to match the current settings
+ 
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
+different from 1.0 (might be both bigger and smaller, your choice).
+ 2. Open the dash first, then the Hud
+ 3. The borders ribbon should be scaled to respect the current monitor scaling 
factor
+ 
+ [Regression potential]
+ Textures aren't properly shown around the unity overlays

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

Title:
  Overlay borders aren't scaled to match monitor DPI scaling

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  The dash or Hud borders aren't scaled to match the current settings

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash first, then the Hud
  3. The borders ribbon should be scaled to respect the current monitor scaling 
factor

  [Regression potential]
  Textures aren't properly shown around the unity overlays

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

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

[Dx-packages] [Bug 1340171] Re: Dash filters don't scale up/down to match the current monitor scale factor

[Treviño]

** Description changed:

- Scale filters need scaling support.
+ [Impact]
+ Dash filters does not respect the configured monitor scaling
+ 
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
+different from 1.0 (might be both bigger and smaller, your choice).
+ 2. Open the dash, expand the filters on the right
+ 3. The filter buttons and texts should respect the current monitor scaling, 
in each scope
+ 
+ [Regression potential]
+ The change mostly consisted in making the old sizes to be always multiplied 
for the scaling factor, then nothing should change when multiplying by 1.
+ Although there might still be visual regressions in the dash search and 
filters widgets.

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

Title:
  Dash filters don't scale up/down to match the current monitor scale
  factor

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Dash filters does not respect the configured monitor scaling

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, expand the filters on the right
  3. The filter buttons and texts should respect the current monitor scaling, 
in each scope

  [Regression potential]
  The change mostly consisted in making the old sizes to be always multiplied 
for the scaling factor, then nothing should change when multiplying by 1.
  Although there might still be visual regressions in the dash search and 
filters widgets.

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

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

[Dx-packages] [Bug 1339629] Re: Dash Previews don't scale correctly when the scale factor changes

[Treviño]

** Description changed:

- When the user performs a dash search and right clicks a result, the Preview 
is always rendered with scale factor 1.0.
- We should fix the scaling.
+ [Impact]
+ When scaling is set to a value different to 1.0 and the user performs a dash 
search and right clicks a result, the Preview is always rendered with scale 
factor 1.0.
+ 
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
+different from 1.0 (might be both bigger and smaller, your choice).
+ 2. Open the dash, [search something], right click over a result
+ 3. The preview items should respect the previously set monitor scaling
+ 
+ [Regression potential]
+ This is a big change that involved lots of changes in the unity dash code, 
although we
+ didn't notice any regression due to this change. At the contrary we improved 
a lot the old code we worked on. Although it's still possible that some 
component of the dash previews might be hidden/distorted or not shown as it 
used to be.

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

Title:
  Dash Previews don't scale correctly when the scale factor changes

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  When scaling is set to a value different to 1.0 and the user performs a dash 
search and right clicks a result, the Preview is always rendered with scale 
factor 1.0.

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, [search something], right click over a result
  3. The preview items should respect the previously set monitor scaling

  [Regression potential]
  This is a big change that involved lots of changes in the unity dash code, 
although we
  didn't notice any regression due to this change. At the contrary we improved 
a lot the old code we worked on. Although it's still possible that some 
component of the dash previews might be hidden/distorted or not shown as it 
used to be.

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

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

[Dx-packages] [Bug 1320071] Re: Power buttons do not work when the screen is locked

[Treviño]

** Description changed:

- Pressing keyboard Sleep, Suspend, Hibernate and Power buttons should
- trigger the action defined by unity settings daemon power plugin.
+ [Impact]
+ Keyboard power buttons do not work in the lockscreen
+ 
+ [Test case]
+ 1. Lock the screen (using Super+L or menus)
+ 2. Pressing keyboard Sleep, Suspend, Hibernate and Power buttons should 
trigger the
+action defined by unity settings daemon power plugin;
+so by default:
+- Pressing power button should open the shutdown dialog
+- Pressing suspend button should suspend the computer
+- Pressing hibernate button should hibernate the computer
+- Pressing the screensaver button should blank the display
+ 
+ [Regression Potential]
+ Nothing known

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

Title:
  Power buttons do not work when the screen is locked

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Keyboard power buttons do not work in the lockscreen

  [Test case]
  1. Lock the screen (using Super+L or menus)
  2. Pressing keyboard Sleep, Suspend, Hibernate and Power buttons should 
trigger the
 action defined by unity settings daemon power plugin;
 so by default:
 - Pressing power button should open the shutdown dialog
 - Pressing suspend button should suspend the computer
 - Pressing hibernate button should hibernate the computer
 - Pressing the screensaver button should blank the display

  [Regression Potential]
  Nothing known

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

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

[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session

[Treviño]

** Changed in: unity/7.2
   Status: Triaged => In Progress

** Changed in: unity (Ubuntu Trusty)
   Status: Triaged => In Progress

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided => Medium

** Description changed:

- Hi!
- 
  I'm trying to get a setup with two different Unity desktop sessions
  running at the same time.  One for the local desktop, one for a remote
  desktop.  This almost works, except that when starting the second Unity
  session, the compiz process that belongs to the first one is killed
  because of this code in /usr/bin/unity:
  
- # kill a previous compiz if was there (this is a hack as compiz can
- # sometimes get stuck and not exit on --replace)
- subprocess.call (["pkill", "-9", "compiz"])
+ # kill a previous compiz if was there (this is a hack as compiz can
+ # sometimes get stuck and not exit on --replace)
+ subprocess.call (["pkill", "-9", "compiz"])
  
  Commenting this line makes both desktop sessions work fine.
  
  This kill is far too harsh.  If you want to kill compiz, you should make
  sure that you are killing it in the same DISPLAY as the session that you
  are about to start, and not just every possible compiz process that is
  running.
  
  Please consider either removing the kill or making it apply only to
  processes in the same DISPLAY.
  
- Thanks.
+ 
+ [Impact]
+ Running unity script will kill the unity processes in different displays
+ 
+ [Test case]
+ - Run unity in DISPLAY=:0 and in DISPLAY=:1
+ - Launch the unity script in DISPLAY=:1, it should kill and restart only the 
unity
+   instance running in DISPLAY=:1

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

Title:
  Unity kills running compiz, even if it belongs to a different Unity
  session

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

Bug description:
  I'm trying to get a setup with two different Unity desktop sessions
  running at the same time.  One for the local desktop, one for a remote
  desktop.  This almost works, except that when starting the second
  Unity session, the compiz process that belongs to the first one is
  killed because of this code in /usr/bin/unity:

  # kill a previous compiz if was there (this is a hack as compiz can
  # sometimes get stuck and not exit on --replace)
  subprocess.call (["pkill", "-9", "compiz"])

  Commenting this line makes both desktop sessions work fine.

  This kill is far too harsh.  If you want to kill compiz, you should
  make sure that you are killing it in the same DISPLAY as the session
  that you are about to start, and not just every possible compiz
  process that is running.

  Please consider either removing the kill or making it apply only to
  processes in the same DISPLAY.

  
  [Impact]
  Running unity script will kill the unity processes in different displays

  [Test case]
  - Run unity in DISPLAY=:0 and in DISPLAY=:1
  - Launch the unity script in DISPLAY=:1, it should kill and restart only the 
unity
instance running in DISPLAY=:1

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

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

[Dx-packages] [Bug 1320051] Re: Shutdown dialog should not allow to lock a session if it's not allowed by settings

[Treviño]

** Description changed:

- Disable lockscreen with:
-   gsettings set org.gnome.desktop.lockdown disable-lock-screen true
+ [Test case]
+ 1. Disable lockscreen with:
+     gsettings set org.gnome.desktop.lockdown disable-lock-screen true
+ 2. When pressing the power button or requesting a logout, unity should not 
show the lock
+options in the shutdown dialog
  
- When pressing the power button or requesting a logout, unity should not
- show the lock options in the shutdown dialog
+ [Regression potential]
+ Lock button might not be shown to other users as well, but this is very 
unlikely to happen.

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

Title:
  Shutdown dialog should not allow to lock a session if it's not allowed
  by settings

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Test case]
  1. Disable lockscreen with:
  gsettings set org.gnome.desktop.lockdown disable-lock-screen true
  2. When pressing the power button or requesting a logout, unity should not 
show the lock
 options in the shutdown dialog

  [Regression potential]
  Lock button might not be shown to other users as well, but this is very 
unlikely to happen.

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

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

[Dx-packages] [Bug 1306211] Re: Trying to lock screen in a guest session leads to an unusable session

[Treviño]

** Description changed:

- That's using current current trusty with the recent fixes to stop using 
gnome-screensaver
+ [Inpact]
+ Screen is dimed and woken up in a loop when trying to lock a guest session
+ 
+ [Test case]
  - log into a guest session
  - pick logout
  - misclick and hit "lock"
- 
- see how the screen is dimed out and woken up in loop, making the session
- un-usable
+ - Nothing should happen

** Description changed:

- [Inpact]
+ [Impact]
  Screen is dimed and woken up in a loop when trying to lock a guest session
  
  [Test case]
  - log into a guest session
  - pick logout
  - misclick and hit "lock"
  - Nothing should happen

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

Title:
  Trying to lock screen in a guest session leads to an unusable session

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Screen is dimed and woken up in a loop when trying to lock a guest session

  [Test case]
  - log into a guest session
  - pick logout
  - misclick and hit "lock"
  - Nothing should happen

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

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

[Dx-packages] [Bug 1312107] Re: Minimised applications show briefly before lock and after unlock (again)

[Treviño]

** Description changed:

- With the new locking scheme in unity7, minimized applications appear
- briefly after unlocking
+ [Impact]
+ With the new locking scheme in unity7, minimized applications appear briefly 
after unlocking
+ Here is a video showing the problem: 
https://www.dropbox.com/s/ai5r2krtgbo93im/2014-04-24%2009.51.52.mp4
  
- To reproduce:
- 
+ [Test case]
  1. Open some applications (in my case psensor and steam)
  2. Minimize them
  3. Press CTRL+ALT+L or Super+L to lock the screen
- Observe the minimized windows briefly popup before the screen locks.
+ The minimized windows should never briefly popup before the screen locks.
+ 
  4. Unlock screen
- Observe the minimized windows re-appear, then re-minimize.
+ The minimized windows should never re-appear and then re-minimize.
  
- I would expect minimized applications to stay minimised through the
- lock/unlock process.
+ The minimized applications must stay minimised through the lock/unlock
+ process.
  
- Here is a video showing the problem:
- https://www.dropbox.com/s/ai5r2krtgbo93im/2014-04-24%2009.51.52.mp4
+ [Regression Potential]
+ Nothing known
+ 
  
  There is another bug about this but it is marked as fixed.. so I guess
  the problem wasn't fixed after all? #1291402
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
+ ProblemType: BugDistroRelease: 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
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3
  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: Thu Apr 24 12:41:24 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:21cf]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:21cf]
  InstallationDate: Installed on 2014-03-26 (28 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1)
  MachineType: LENOVO 42433ZG
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c3c7f36f-ca42-443e-819f-5553fe3d040a ro quiet splash vt.handoff=7
- SourcePackage: unity
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c3c7f36f-ca42-443e-819f-5553fe3d040a ro quiet splash 
vt.handoff=7SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42433ZG
  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:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn42433ZG:pvrThinkPadT520:rvnLENOVO:rn42433ZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42433ZG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-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-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  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
  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: Tue Apr 15 12:18:55 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1415 
-  vendor SAM
+  product id1415
+  vendor SAM
  xserver.version: 2:1.15.1-0ubuntu1

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

Title:
  Minimised applications show briefly before lock and after unlock
  (again)

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package 

[Dx-packages] [Bug 1292391] Re: lockscreen - wallpaper is not properly resized when unplugging monitors

[Treviño]

** Description changed:

- Steps to repoduce:
+ [Inpact]
+ Wallpapers have an invalid aspect ratio in the lockscreen, when 
attaching/detaching monitors, while the screen is locked
+ 
+ I attached photos taken of the same screen with and without aritfacts
+ (same size, though the dots have different spacing). Wallpaper used is
+ from the current default selection.
+ 
+ [Test case]
  - Have 2 monitors/displays with different resolutions setup on your trusty 
installation. (In my case: Primary 1600x900 laptop screen and secondary 
1920x1080 external monitor.)
  - Lock the screen via shortcut.
  - Remove one monitor. (In my case: Remove the external one.)
- - Result: The display setup change is detected but the wallpaper on the 
remaining screen shows artifacts of improper resizing. Unlocking and locking 
the screen again will display the wallpaper properly resized without artifacts.
- - Settings for background images in control center are set to resize for each 
screen (the 2nd option).
+ - Result: The display setup change is detected and the wallpaper on the 
remaining screen
+   is properly resized to respect the new aspect ratio. 
  
- 
- I attached photos taken of the same screen with and without aritfacts (same 
size, though the dots have different spacing). Wallpaper used is from the 
current default selection.
+ [Regression potential]
+ None

** Description changed:

- [Inpact]
+ [Impact]
  Wallpapers have an invalid aspect ratio in the lockscreen, when 
attaching/detaching monitors, while the screen is locked
  
  I attached photos taken of the same screen with and without aritfacts
  (same size, though the dots have different spacing). Wallpaper used is
  from the current default selection.
  
  [Test case]
  - Have 2 monitors/displays with different resolutions setup on your trusty 
installation. (In my case: Primary 1600x900 laptop screen and secondary 
1920x1080 external monitor.)
  - Lock the screen via shortcut.
  - Remove one monitor. (In my case: Remove the external one.)
  - Result: The display setup change is detected and the wallpaper on the 
remaining screen
-   is properly resized to respect the new aspect ratio. 
+   is properly resized to respect the new aspect ratio.
  
  [Regression potential]
  None

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

Title:
  lockscreen - wallpaper is not properly resized when unplugging
  monitors

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Wallpapers have an invalid aspect ratio in the lockscreen, when 
attaching/detaching monitors, while the screen is locked

  I attached photos taken of the same screen with and without aritfacts
  (same size, though the dots have different spacing). Wallpaper used is
  from the current default selection.

  [Test case]
  - Have 2 monitors/displays with different resolutions setup on your trusty 
installation. (In my case: Primary 1600x900 laptop screen and secondary 
1920x1080 external monitor.)
  - Lock the screen via shortcut.
  - Remove one monitor. (In my case: Remove the external one.)
  - Result: The display setup change is detected and the wallpaper on the 
remaining screen
    is properly resized to respect the new aspect ratio.

  [Regression potential]
  None

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

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

[Dx-packages] [Bug 1283415] Re: 1px gap between launcher and dash on high-dpi screen

[Treviño]

** Description changed:

- There is a 1px gap between the launcher and the dash.
+ [Impact]
+ When desktop scaling is enabled, there is a 1px gap between the launcher and 
the dash.
  
  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
+ [Test case]
+ 1. From Unity Control Center -> Displays -> Change the monitor scaling to a 
value bigger
+than 1.5 (best at 2.0 or more)
+ 2. Open the dash
+ 3. There should be no "fully transparent" gab between dash and launcher (as 
shown in this
+image https://launchpadlibrarian.net/167262841/unity-dash-dpi.png
+ 
+ [Regression Potential]
+ Nothing known, dash borders might be distorted
+ 
+ 
+ ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.13.2-0ubuntu5
  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: Sat Feb 22 12:41:11 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
-  virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
+  virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
+  virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:3978]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7
- SourcePackage: unity
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
vt.handoff=7SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140218-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~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  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-1ubuntu2
  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: Sat Feb 22 12:08:14 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   16970 
-  vendor SDC
+  product id   16970
+  vendor SDC
  xserver.version: 2:1.15.0-1ubuntu6

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

Title:
  1px gap between launcher and dash on high-dpi screen

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  When desktop scaling is enabled, there is a 1px gap between the launcher and 
the dash.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  [Test case]
  1. From Unity Control Center -> Displays -> Change the monitor scaling to a 
value bigger
 than 1.5 (best at

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Treviño]

** Changed in: unity/7.2
   Importance: Undecided => High

** Changed in: unity/7.2
   Status: New => Triaged

** Changed in: unity/7.2
Milestone: None => 7.2.3

** Changed in: unity/7.2
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Branch linked: lp:~andyrock/unity/fix-1308540

** Changed in: unity (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: unity/7.2
   Status: Triaged => In Progress

** Changed in: unity
   Status: Triaged => Fix Committed

** Changed in: unity/7.2
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity/7.2
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: unity
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Andrea Azzarone (andyrock)

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  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 i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1369264] Re: unity-panel-service crashed with signal 5 in g_type_create_instance()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1201947, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203638/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203640/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203642/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203643/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203644/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203645/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1369264/+attachment/4203646/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1201947
   unity-panel-service crashed with signal 5 in g_type_create_instance() from 
bamf_matcher_get_default()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  unity-panel-service crashed with signal 5 in g_type_create_instance()

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

Bug description:
  Not any application show in applications tab;
  Not found any appication in dash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-appmenu 13.01.0+14.04.20140404-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CrashCounter: 1
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Sun Sep 14 19:21:08 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  ProcCmdline: /usr/lib/unity/unity-panel-service
  Signal: 5
  SourcePackage: indicator-appmenu
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libbamf3.so.2
   g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with signal 5 in g_type_create_instance()
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (147 days ago)
  UserGroups: adm admin audio cdrom dialout dip firebird floppy fuse lpadmin 
plugdev sambashare scanner users video

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

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

[Dx-packages] [Bug 1300650] Re: Should use separate schema for launcher items

[Treviño]

** Changed in: unity
   Importance: Undecided => High

** Changed in: unity
   Status: New => Fix Released

** Changed in: unity
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  Should use separate schema for launcher items

Status in The Sevilerow project:
  New
Status in Unity:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Won't Fix
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  We're using the schema from unity for launcher items, but we should
  instead use a custom one, since unity7 will never support click
  packages, so they're not compatible already.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140327.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14-0ubuntu1
  Architecture: armhf
  Date: Tue Apr  1 09:30:11 2014
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1364453] Re: Brightness setting does not persist across reboots

[Alberto Aguirre]

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Brightness setting does not persist across reboots

Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1364453/+subscriptions

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

[Dx-packages] [Bug 1370069] Re: Login does not work

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  Login does not work

Status in “unity” package in Ubuntu:
  New

Bug description:
  After screen lock the login does not display a field where a password
  can be typed and thus there seems to be no way to login to machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Sep 16 16:53:05 2014
  DistUpgraded: 2014-04-11 11:51:55,755 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Hewlett-Packard Company Device [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:90b8]
  InstallationDate: Installed on 2013-11-05 (315 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=ef4f067e-192b-4f3f-873d-bfb295641eec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-04-11 (158 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-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.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Sep  4 10:17:39 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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

[Dx-packages] [Bug 1370069] [NEW] Login does not work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After screen lock the login does not display a field where a password
can be typed and thus there seems to be no way to login to machine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Sep 16 16:53:05 2014
DistUpgraded: 2014-04-11 11:51:55,755 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Subsystem: Hewlett-Packard Company Device [103c:18e4]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:90b8]
InstallationDate: Installed on 2013-11-05 (315 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=ef4f067e-192b-4f3f-873d-bfb295641eec ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to trusty on 2014-04-11 (158 days ago)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.18
dmi.board.asset.tag: CZC3427KBP
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC3427KBP
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-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.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Sep  4 10:17:39 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug false-gpu-hang freeze trusty ubuntu
-- 
Login does not work
https://bugs.launchpad.net/bugs/1370069
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

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

[Dx-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator

[Pat McGowan]

I would propose this is needed for ship

** Tags added: rtm14

** Tags added: usability

** Changed in: indicator-sound (Ubuntu)
   Importance: High => Critical

** Changed in: indicator-sound (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  [Indicators] Silent mode control in the indicator

Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  Should the indicator expose the control for silent mode for easy
  access?

  Implementing in settings now but would like to leverage a common
  implementation

  --

  I've attached a wireframe which shows an additional setting in the
  sound indicator for turning on and off silent mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1342151/+subscriptions

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

[Dx-packages] [Bug 1172649] Re: Spotify icon is displayed twice in Unity Launcher

[Kai Mast]

Have the same problem with google chrome now, since I upgraded to
utopic...

** Tags added: utopic

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

Title:
  Spotify icon is displayed twice in Unity Launcher

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

Bug description:
  I'm using Ubuntu 13.04 and latest Spotify version. The spotify icon
  (when the application is not running) it's sticked on the launcher,
  and this is ok. When I click on it, another icon appears (see the
  attached picture).

  This happened also in older versions of Unity. Could someone please
  fix this?

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

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

[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv

[Launchpad Bug Tracker]

This bug was fixed in the package pay-service -
2.0.0+14.10.20140916-0ubuntu1

---
pay-service (2.0.0+14.10.20140916-0ubuntu1) utopic; urgency=low

  [ Martin Pitt ]
  * Adjust upstart dependency to upstart-bin. (LP: #1351306)
 -- Ubuntu daily releaseTue, 16 Sep 2014 
18:31:43 +

** Changed in: pay-service (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Cannot uninstall upstart and install systemd-sysv

Status in Unity:
  Fix Committed
Status in “avahi” package in Ubuntu:
  Fix Released
Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dovecot” package in Ubuntu:
  Fix Released
Status in “friendly-recovery” package in Ubuntu:
  Fix Released
Status in “hockeypuck” package in Ubuntu:
  Fix Released
Status in “pay-service” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “sysvinit” package in Ubuntu:
  Fix Released
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  upstart is currently quite deeply wired into our dependencies. Even in
  a minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:

  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).

  On a desktop the list is quite a bit longer:

   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd 
script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop 
that along with upstart for systemd images, systemd has readahead built in)
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
   init depends on upstart. (Not important right now, switch to alternative 
deps once systemd is ready)

  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are
  using session upstart on the desktop (unity-services etc.), for this
  we probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

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

[Dx-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2

[Bill Filler]

** Tags added: touch-2014-09-25

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

Title:
  VoiceMail notification pretends there are 255 messages. It is not true
  there are only 2

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Triaged

Bug description:
  Mako build #175

  The VoiceMail notification indicates there are 255 voice messages (cf
  screenshot)  on voice mail while there were only 2 new messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Wed Aug  6 11:57:43 2014
  InstallationDate: Installed on 2014-08-06 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140806-020204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions

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

[Dx-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/utopic-proposed/pay-service

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

Title:
  Cannot uninstall upstart and install systemd-sysv

Status in Unity:
  Fix Committed
Status in “avahi” package in Ubuntu:
  Fix Released
Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dovecot” package in Ubuntu:
  Fix Released
Status in “friendly-recovery” package in Ubuntu:
  Fix Released
Status in “hockeypuck” package in Ubuntu:
  Fix Released
Status in “pay-service” package in Ubuntu:
  In Progress
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “sysvinit” package in Ubuntu:
  Fix Released
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-lens-applications” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  upstart is currently quite deeply wired into our dependencies. Even in
  a minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:

  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).

  On a desktop the list is quite a bit longer:

   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd 
script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0). (No need to fix -- can just drop 
that along with upstart for systemd images, systemd has readahead built in)
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
   init depends on upstart. (Not important right now, switch to alternative 
deps once systemd is ready)

  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are
  using session upstart on the desktop (unity-services etc.), for this
  we probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

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

[Dx-packages] [Bug 1359802] Re: header's timestamp can take a minute to update after resume from suspend

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
13.10.0+14.10.20140915-0ubuntu1

---
indicator-datetime (13.10.0+14.10.20140915-0ubuntu1) utopic; urgency=low

  [ Charles Kerr ]
  * Update the time strings when a powerd Wakeup signal is detected.
(LP: #1359802)
 -- Ubuntu daily releaseMon, 15 Sep 2014 
21:03:00 +

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  header's timestamp can take a minute to update after resume from
  suspend

Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  Not the same as the bug #1328646, where the clock fell completely out-
  of-sync and never came back.

  This bug has a milder but similar symptom, the clock is set to update
  once per minute, so after resume from suspend it will still show the
  wrong time until that periodic update timer triggers.

  In addition to the periodic update, indicator-datetime should listen
  to powerd's Wakeup signal, or better yet, to
  com.canonical.Unity.Screen's DisplayPowerStateChange signal
   to ensure
  that it makes the timestamp up-to-date whenever the screen is turned
  on.

  Reported by ogra and dednick in #ubuntu-touch.

  *edit:* also discussed by kgunn72 and aacid @
  https://code.launchpad.net/~nick-
  dedekind/unity8/lp1328646/+merge/231335

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1359802/+subscriptions

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

[Dx-packages] [Bug 1364453] Re: Brightness setting does not persist across reboots

[Alberto Aguirre]

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Invalid

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

Title:
  Brightness setting does not persist across reboots

Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1364453/+subscriptions

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

[Dx-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[Micheal Waltz]

This bug also causes all users home directories to mount if they're
setup in autofs. This is especially detrimental if your autofs maps
contain thousands of users. Lightdm and autofs will slowly grind through
mounting home directories looking for:

~/.dmrc
~/.face
~/.face.icon

These mounts stay around in /etc/mtab, which causes reboots/shutdowns to
take extremely long while the system then umounts all the directories.

This not only affects the local system, but if hundreds of systems in an
environment are doing this it causes unnecessary load on backend
services.

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

Title:
  Unable to hide users from login screen / user switcher

Status in D-Bus interfaces for querying and manipulating user account 
information:
  Confirmed
Status in “accountsservice” package in Ubuntu:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Dx-packages] [Bug 1364453] Re: Brightness setting does not persist across reboots

[Charles Kerr]

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-power (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-power (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Brightness setting does not persist across reboots

Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1364453/+subscriptions

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

[Dx-packages] [Bug 1370190] [NEW] .desktop files in .local/share/applications not processed correctly

[teo1978]

Public bug reported:

I had this file:  ~/.local/share/applications/jetbrains-android-
studio.desktop

whose content is:
-
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Android Studio (Preview) 0.4.6
Icon=jetbrains-android-studio.png
Path=/home/teo/
#Exec=/usr/lib/jvm/java-7-oracle/bin/java -Xms128m -Xmx750m 
-XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -ea 
-Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true 
-Didea.project.structure.max.errors.to.show=0 -XX:+UseCodeCacheFlushing 
-XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 
-XX:+HeapDumpOnOutOfMemoryError -Dawt.useSystemAAFontSettings=lcd 
-Djb.vmOptionsFile=Documents/programmi/android-studio/bin/studio64.vmoptions 
-Xbootclasspath/a:Documents/programmi/android-studio/bin/../lib/boot.jar 
-Didea.paths.selector=AndroidStudioPreview -Didea.platform.prefix=AndroidStudio 
-Djb.restart.code=88 com.intellij.idea.Main
Exec=/home/teo/Documents/programmi/android-studio/bin/studio.sh
StartupNotify=false
#StartupWMClass=jetbrains-android-studio
OnlyShowIn=Unity;
X-UnityGenerated=true
-

I wanted to use this as a model for creating a desktop file for a
completely unrelated application. So this is what I did:

I copied the file verbatim to
~/.local/share/applications/telegram.desktop

and then edited it. Its content now is:

-
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Telegram Desktop
Path=/home/teo/
Exec=/home/teo/Documents/programmi/Telegram/Telegram
StartupNotify=true
OnlyShowIn=Unity;
X-UnityGenerated=true
-

You can see that there's absolutely nothing in the first file that
matches the string "telegram", and also you can see that the second file
(the one called "telegram.desktop") has "Telegram Desktop" as its
application name, NOT Android Studio, and doesn't contain anything
related to "Android Studio".


So, the expected behavior is that if I type "Telegram" in the Dash, an item 
should be displayed under Applications, with the name Telegram Desktop, and 
with either the default icon embedded in the executable, if any, or some 
default icon.

Instead, I get this: see screenshot.

It looks like the list of applications got somehow "cached" when I
created the new file, but it didn't get updated when I modified the
file.

If I click on the wrongly-named "Android Studio (etc)" application, it
does load the correct one, which is Telegram.

Perhaps this will be fixed at the next reboot, but it shouldn't take a
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Sep 16 19:44:17 2014
InstallationDate: Installed on 2013-10-11 (340 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (115 days ago)

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: "Screenshot from 2014-09-16 20:03:43.png"
   
https://bugs.launchpad.net/bugs/1370190/+attachment/4205676/+files/Screenshot%20from%202014-09-16%2020%3A03%3A43.png

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

Title:
  .desktop files in .local/share/applications not processed correctly

Status in “unity” package in Ubuntu:
  New

Bug description:
  I had this file:  ~/.local/share/applications/jetbrains-android-
  studio.desktop

  whose content is:
  -
  [Desktop Entry]
  Encoding=UTF-8
  Version=1.0
  Type=Application
  Name=Android Studio (Preview) 0.4.6
  Icon=jetbrains-android-studio.png
  Path=/home/teo/
  #Exec=/usr/lib/jvm/java-7-oracle/bin/java -Xms128m -Xmx750m 
-XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -ea 
-Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true 
-Didea.project.structure.max.errors.to.show=0 -XX:+UseCodeCacheFlushing 
-XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 
-XX:+HeapDumpOnOutOfMemoryError -Dawt.useSystemAAFontSettings=lcd 
-Djb.vmOptionsFile=Documents/programmi/android-studio/bin/studio64.vmoptions 
-Xbootclasspath/a:Documents/programmi/android-studio/bin/../lib/boot.jar 
-Didea.paths.selector=AndroidStudioPreview -Didea.platform.prefix=AndroidStudio 
-Djb.restart.code=88 com.intellij.idea.Main
  Exec=/home/teo/Documents/programmi/android-studio/bin/studio.sh
  StartupNotify=false
  #StartupWMClass=jetbrains-android-studio
  OnlyShowIn=Unity;
  X-UnityGenerated=true
  -

  I wanted to use this as a model for creating a desktop file for a
  completely unrelated application. So this is what I did:

  I copied the file verbatim to
  ~/

[Dx-packages] [Bug 1340952] Re: Video and Music scopes should provide non-file:/// based URIs

[Bill Filler]

don't we need a photo:// url for the "My Photos" scope as well?

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

Title:
  Video and Music scopes should provide non-file:/// based URIs

Status in Media Player App:
  In Progress
Status in Unity Media Scanner Scope:
  Confirmed
Status in QML plugin for Scopes:
  Confirmed
Status in “url-dispatcher” package in Ubuntu:
  In Progress

Bug description:
  There are some mp4 videos found/indexed by mediascanner-service-2.0 from 
~/Pictures. The thumbnails of those are shown in the Video scope but can not be 
played. If the video is moved over to ~/Videos, the videos are played just fine.
  mako utopic r119

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1340952/+subscriptions

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

[Dx-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay

[Stephen M. Webb]

** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  Wrong keyboard shortcuts for Workspaces in Dash overlay

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When you hold the Super key and the overlay with the keyboard shortcut
  opens:

  Under "Workspaces" it says:

  Ctrl + Alt + Left + Arrow Keys: Switches Workspaces
  Shift + Ctrl + Alt + Left + Arrow Keys: Moves focused window to another 
workspace

  
  The shortcuts are wrong, the "+ Left" makes no sense. Is this supposed to be 
"Left Alt"? But on the other hand all other shortcuts do not say "Left Alt" but 
just "Alt", so that's probably not it.

  Anyway, the correct shortcuts are:

  Ctrl + Alt + Arrow Keys: Switches Workspaces
  Shift + Ctrl + Alt + Arrow Keys: Moves focused window to another workspace

  This is also what it says on the official help:
  https://help.ubuntu.com/14.04/ubuntu-help/shell-keyboard-shortcuts.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,ezoom,unityshell,expo,scale]
  CurrentDesktop: Unity
  Date: Sun Aug 31 01:58:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-15 (714 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (154 days ago)

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

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

[Dx-packages] [Bug 1369737] Re: Send button does not enable until you press spacebar

[Tiago Salem Herrmann]

As a reminder, we need to call Qt.inputMethod.commit() so the buffer
gets committed and the text property is correctly set.

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

Title:
  Send button does not enable until you press spacebar

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  krillin build 40, rtm image

  - make sure word prediction/preditive text is turned on (this is now the 
default)
  - receive a text message on your phone
  - pull down messaging indicator
  - click on the message
  - type "Hello" in the entry field

  Expected result:
  - the send button should become active as soon as you start typing

  Actual result:
  - send button stays disabled until you press the spacebar

  The send button should not wait until the word is committed before
  becoming active, but instead should listen for any change and enable
  the button accordingly. The messaging app does this correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1369737/+subscriptions

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

[Dx-packages] [Bug 1359802] Re: header's timestamp can take a minute to update after resume from suspend

[Olli Ries]

** Changed in: indicator-datetime (Ubuntu)
   Importance: High => Critical

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

Title:
  header's timestamp can take a minute to update after resume from
  suspend

Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  Not the same as the bug #1328646, where the clock fell completely out-
  of-sync and never came back.

  This bug has a milder but similar symptom, the clock is set to update
  once per minute, so after resume from suspend it will still show the
  wrong time until that periodic update timer triggers.

  In addition to the periodic update, indicator-datetime should listen
  to powerd's Wakeup signal, or better yet, to
  com.canonical.Unity.Screen's DisplayPowerStateChange signal
   to ensure
  that it makes the timestamp up-to-date whenever the screen is turned
  on.

  Reported by ogra and dednick in #ubuntu-touch.

  *edit:* also discussed by kgunn72 and aacid @
  https://code.launchpad.net/~nick-
  dedekind/unity8/lp1328646/+merge/231335

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1359802/+subscriptions

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

[Dx-packages] [Bug 1300650] Re: Should use separate schema for launcher items

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+14.10.20140915-0ubuntu1

---
unity (7.3.1+14.10.20140915-0ubuntu1) utopic; urgency=low

  [ Michael Zanetti ]
  * add "items" key to Launcher schema to be used by unity8 (LP:
#1300650)

  [ Andrea Azzarone ]
  * Use COMPIZ_METAKEY where needed. (LP: #1363534)
 -- Ubuntu daily releaseMon, 15 Sep 2014 
12:35:45 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Should use separate schema for launcher items

Status in The Sevilerow project:
  New
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Won't Fix
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  We're using the schema from unity for launcher items, but we should
  instead use a custom one, since unity7 will never support click
  packages, so they're not compatible already.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140327.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14-0ubuntu1
  Architecture: armhf
  Date: Tue Apr  1 09:30:11 2014
  InstallationDate: Installed on 2014-04-01 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.1+14.10.20140915-0ubuntu1

---
unity (7.3.1+14.10.20140915-0ubuntu1) utopic; urgency=low

  [ Michael Zanetti ]
  * add "items" key to Launcher schema to be used by unity8 (LP:
#1300650)

  [ Andrea Azzarone ]
  * Use COMPIZ_METAKEY where needed. (LP: #1363534)
 -- Ubuntu daily releaseMon, 15 Sep 2014 
12:35:45 +

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Wrong keyboard shortcuts for Workspaces in Dash overlay

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When you hold the Super key and the overlay with the keyboard shortcut
  opens:

  Under "Workspaces" it says:

  Ctrl + Alt + Left + Arrow Keys: Switches Workspaces
  Shift + Ctrl + Alt + Left + Arrow Keys: Moves focused window to another 
workspace

  
  The shortcuts are wrong, the "+ Left" makes no sense. Is this supposed to be 
"Left Alt"? But on the other hand all other shortcuts do not say "Left Alt" but 
just "Alt", so that's probably not it.

  Anyway, the correct shortcuts are:

  Ctrl + Alt + Arrow Keys: Switches Workspaces
  Shift + Ctrl + Alt + Arrow Keys: Moves focused window to another workspace

  This is also what it says on the official help:
  https://help.ubuntu.com/14.04/ubuntu-help/shell-keyboard-shortcuts.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,ezoom,unityshell,expo,scale]
  CurrentDesktop: Unity
  Date: Sun Aug 31 01:58:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-15 (714 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (154 days ago)

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

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

[Dx-packages] [Bug 1370129] Re: With music-app closed, the controls in the sound menu are dummy

[Omer Akram]

** Attachment added: "sound.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1370129/+attachment/4205411/+files/sound.png

** Also affects: indicator-sound
   Importance: Undecided
   Status: New

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

Title:
  With music-app closed, the controls in the sound menu are dummy

Status in Sound Menu:
  New
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  1. ensure music-app is not running
  2. drag down the sound menu
  3. tap on the 'play' icon.

  What happens:
  Nothing

  What should happen:
  Either the controls should not be there by default or tapping the play icon 
must start the music app and start playing something.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'mute': (true, signature '', []), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': (true, 'i', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (false, '', [<{'running': , 
'state': <'Stopped'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Stopped'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Sound'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', [])},)
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 20:50:00 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1370129/+subscriptions

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

[Dx-packages] [Bug 1370129] [NEW] With music-app closed, the controls in the sound menu are dummy

[Omer Akram]

Public bug reported:

1. ensure music-app is not running
2. drag down the sound menu
3. tap on the 'play' icon.

What happens:
Nothing

What should happen:
Either the controls should not be there by default or tapping the play icon 
must start the music app and start playing something.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ActionStates: ({'mute': (true, signature '', []), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': (true, 'i', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (false, '', [<{'running': , 
'state': <'Stopped'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Stopped'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Sound'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', [])},)
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
Date: Tue Sep 16 20:50:00 2014
InstallationDate: Installed on 2014-09-16 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-sound
 Importance: Undecided
 Status: New

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf qa-touch utopic

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

Title:
  With music-app closed, the controls in the sound menu are dummy

Status in Sound Menu:
  New
Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  1. ensure music-app is not running
  2. drag down the sound menu
  3. tap on the 'play' icon.

  What happens:
  Nothing

  What should happen:
  Either the controls should not be there by default or tapping the play icon 
must start the music app and start playing something.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ActionStates: ({'mute': (true, signature '', []), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': (true, 'i', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (false, '', [<{'running': , 
'state': <'Stopped'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Stopped'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Sound'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', [])},)
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 20:50:00 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1370129/+subscriptions

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

[Dx-packages] [Bug 1367817] Re: Revert icon to previous 'envelope' design

[kevin gunn]

so after chasing a little, the visual just needs to be updated, no need
to change the name in the code.

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes
   Importance: Undecided => Critical

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

Title:
  Revert icon to previous 'envelope' design

Status in Themes for Ubuntu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  "The previous 'envelope' icon worked better".

  UX Testing Finding: "All participants associated the icon with an
  alarm or reminder.  They all failed to interact with it when looking
  for missed calls and unread messages. They had to go to the dialer and
  messages separately to check."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1367817/+subscriptions

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Gabriel Zellmer]

I am also happy to report that after installing Marco Trevisan's patch
on 05SEP2014 I am no longer experiencing this glitch. Usually I was
experiencing this glitch daily to every other day but have not since
patching it.

Thank you Marco Trevisan for taking the time to work this glitch, it is
greatly appreciated!!

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  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 i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2

[Jussi Kangas]

So what I think is happening here is that voice call notification
messages are stored to SIM ( as they should in my opinion, see ETSI TS
TS 123 038) and not really read ever. Count is read at startup from the
SIM and it just keeps rising.

I can reproduce this in the lab now but I need some extra digging to
verify the details.

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

Title:
  VoiceMail notification pretends there are 255 messages. It is not true
  there are only 2

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Triaged

Bug description:
  Mako build #175

  The VoiceMail notification indicates there are 255 voice messages (cf
  screenshot)  on voice mail while there were only 2 new messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Wed Aug  6 11:57:43 2014
  InstallationDate: Installed on 2014-08-06 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140806-020204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions

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

[Dx-packages] [Bug 1370100] Re: Brigtness bar should get greyed out when auto-brightness is on

[Omer Akram]

** Attachment added: "battery_menu.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1370100/+attachment/4205349/+files/battery_menu.png

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

Title:
  Brigtness bar should get greyed out when auto-brightness is on

Status in “indicator-power” package in Ubuntu:
  New

Bug description:
  Note: THIS bug is for the power menu that is dragged from the top, see
  attached image.

  1. Drag down battery icon from the top
  2. make sure auto-brghtness is enabled
  3. try dragging the slider

  What happens:
  Nothing happens when you move the slider

  What should happen:
  If the slider is of no use during auto-brightness it should not be movable at 
all.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-power 12.10.6+14.10.20140912-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:53:00 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-power.log: (process:3237): libnotify-WARNING **: Failed to 
connect to proxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1370100/+subscriptions

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

[Dx-packages] [Bug 1370100] [NEW] Brigtness bar should get greyed out when auto-brightness is on

[Omer Akram]

Public bug reported:

Note: THIS bug is for the power menu that is dragged from the top, see
attached image.

1. Drag down battery icon from the top
2. make sure auto-brghtness is enabled
3. try dragging the slider

What happens:
Nothing happens when you move the slider

What should happen:
If the slider is of no use during auto-brightness it should not be movable at 
all.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-power 12.10.6+14.10.20140912-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
Date: Tue Sep 16 19:53:00 2014
InstallationDate: Installed on 2014-09-16 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
SourcePackage: indicator-power
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.indicator-power.log: (process:3237): libnotify-WARNING **: Failed to 
connect to proxy

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf qa-touch utopic

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

Title:
  Brigtness bar should get greyed out when auto-brightness is on

Status in “indicator-power” package in Ubuntu:
  New

Bug description:
  Note: THIS bug is for the power menu that is dragged from the top, see
  attached image.

  1. Drag down battery icon from the top
  2. make sure auto-brghtness is enabled
  3. try dragging the slider

  What happens:
  Nothing happens when you move the slider

  What should happen:
  If the slider is of no use during auto-brightness it should not be movable at 
all.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-power 12.10.6+14.10.20140912-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:53:00 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-power.log: (process:3237): libnotify-WARNING **: Failed to 
connect to proxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1370100/+subscriptions

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

[Dx-packages] [Bug 1369737] Re: Send button does not enable until you press spacebar

[Bill Filler]

This can be fixed in the same way it's done in the messaging-app, by
checking the following properties:

enabled: (textField.text != "" || textField.inputMethodComposing)

This will cause the send button to be enabled if there is text in the
field or text is being composed

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

Title:
  Send button does not enable until you press spacebar

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  krillin build 40, rtm image

  - make sure word prediction/preditive text is turned on (this is now the 
default)
  - receive a text message on your phone
  - pull down messaging indicator
  - click on the message
  - type "Hello" in the entry field

  Expected result:
  - the send button should become active as soon as you start typing

  Actual result:
  - send button stays disabled until you press the spacebar

  The send button should not wait until the word is committed before
  becoming active, but instead should listen for any change and enable
  the button accordingly. The messaging app does this correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1369737/+subscriptions

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

[Dx-packages] [Bug 1369738] Re: Can reply to SMS even when screen is locked

[Bill Filler]

invalid, there is a setting buried under System Settings->Lock that will
turn off interacting with notifications bar

** Changed in: indicator-messages (Ubuntu)
   Status: New => Invalid

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

Title:
  Can reply to SMS even when screen is locked

Status in “indicator-messages” package in Ubuntu:
  Invalid

Bug description:
  krilling build 40 on rtm image

  - setup a pin lock for your phone
  - lock your phone
  - send an sms to your phone
  - pull down messaging-menu

  Expected results:
  - should not see any messages, or if you can you should not be able to reply

  Actual results:
  - I can reply to any sms message. Seems like a big security hole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1369738/+subscriptions

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

[Dx-packages] [Bug 1350977] Re: i have desktop background but no icons or menus

[Stephen M. Webb]

The symptom you have described is of Compiz (Unity) not running.  Now
that this bug has been properly assigned to the Unity package, if you
could open a terminal and issue the following command

  apport-collect 1350977

the system will collect additional information that might help us
identify the case of your problem.

** Changed in: unity (Ubuntu)
   Status: New => Incomplete

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

Title:
  i have desktop background but no icons or menus

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  uping on upgrade from 12.04 lts to 14.04 lts

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Jul 30 12:27:25 2014
  Dependencies:
   gcc-4.6-base 4.6.3-1ubuntu5
   libc6 2.19-0ubuntu6
   libgcc1 1:4.6.3-1ubuntu5
   multiarch-support 2.15-0ubuntu10.5
  DuplicateSignature: package:libc6:2.19-0ubuntu6:subprocess new 
pre-installation script returned error exit status 128
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 128
  UpgradeStatus: Upgraded to trusty on 2014-07-30 (1 days ago)

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

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

[Dx-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply

[kevin gunn]

** Tags removed: touch-2014-09-11
** Tags added: touch-2014-09-25

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

Title:
  Messaging indicator sometimes fails to send a reply

Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Open the messaging app
  2. Send a message to your own phone
  3. Close the messaging app
  4. Hit the power button
  5. Drag down the indicator
  6. Reply to the message
  7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead 
saves it.

  See attached screenshot  note the greyed send button

  WORKAROUND:
  Remove all messages from the indicator and use the messaging app once to 
reply, you will then be good till your indicator locks up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Thu Jun 12 12:01:29 2014
  InstallationDate: Installed on 2014-06-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140612)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1329289/+subscriptions

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

[Dx-packages] [Bug 1350977] Re: i have desktop background but no icons or menus

[Daniel Llewellyn]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this
bug as a bug in unity.

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://help.ubuntu.com/community/ReportingBugs.

** Package changed: ubuntu => unity (Ubuntu)

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

Title:
  i have desktop background but no icons or menus

Status in “unity” package in Ubuntu:
  New

Bug description:
  uping on upgrade from 12.04 lts to 14.04 lts

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Jul 30 12:27:25 2014
  Dependencies:
   gcc-4.6-base 4.6.3-1ubuntu5
   libc6 2.19-0ubuntu6
   libgcc1 1:4.6.3-1ubuntu5
   multiarch-support 2.15-0ubuntu10.5
  DuplicateSignature: package:libc6:2.19-0ubuntu6:subprocess new 
pre-installation script returned error exit status 128
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 128
  UpgradeStatus: Upgraded to trusty on 2014-07-30 (1 days ago)

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

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

[Dx-packages] [Bug 1350977] [NEW] i have desktop background but no icons or menus

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

uping on upgrade from 12.04 lts to 14.04 lts

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Wed Jul 30 12:27:25 2014
Dependencies:
 gcc-4.6-base 4.6.3-1ubuntu5
 libc6 2.19-0ubuntu6
 libgcc1 1:4.6.3-1ubuntu5
 multiarch-support 2.15-0ubuntu10.5
DuplicateSignature: package:libc6:2.19-0ubuntu6:subprocess new pre-installation 
script returned error exit status 128
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
MarkForUpload: True
SourcePackage: eglibc
Title: package libc6 2.19-0ubuntu6 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 128
UpgradeStatus: Upgraded to trusty on 2014-07-30 (1 days ago)

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package needs-reassignment trusty
-- 
i have desktop background but no icons or menus
https://bugs.launchpad.net/bugs/1350977
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

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

[Dx-packages] [Bug 1369993] Re: implement new indicator reveal interaction design

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1368856
   [Indicators] [design] Update indicators to match the latest design

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

Title:
  implement new indicator reveal interaction design

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  place holder to disccus and implement this work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1369993/+subscriptions

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

[Dx-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2

[Jussi Kangas]

Tested with Anritsu in simulated GSM and UMTS networks, but nothing
comes through. Since ubuntu-touch ofono does not support
UNSOL_RESPONSE_NEW_SMS_ON_SIM I don't see how the voice mail interface
could work. Need to discuss with others before proceeding

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

Title:
  VoiceMail notification pretends there are 255 messages. It is not true
  there are only 2

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Triaged

Bug description:
  Mako build #175

  The VoiceMail notification indicates there are 255 voice messages (cf
  screenshot)  on voice mail while there were only 2 new messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Wed Aug  6 11:57:43 2014
  InstallationDate: Installed on 2014-08-06 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140806-020204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Margarita Manterola]

Several  users in my company were experiencing this issue, and it was
gone after installing the test packages provided by Marco.  Please
backport this to Trusty ASAP.

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  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 i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Dx-packages] [Bug 1367818] Re: Mute causes no indication of a change in [icon] state.

[Victor Tuson Palau]

** Tags added: rm-14

** Tags removed: rm-14
** Tags added: rtm-14

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => High

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

Title:
  Mute causes no indication of a change in [icon] state.

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  - "When the sound is muted, the volume icon to the left of the volume slider 
should have a red "/" running through it."
  - "Add an explicit "Mute" button to the sound indicator menu."
  - "Pressing and holding the icon to the left of the volume slider should mute 
volume straight away."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1367818/+subscriptions

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

[Dx-packages] [Bug 1367817] Re: Revert icon to previous 'envelope' design

[Victor Tuson Palau]

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided => Critical

** Tags added: rtm-14

** Changed in: indicator-messages (Ubuntu)
   Status: New => Confirmed

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

Title:
  Revert icon to previous 'envelope' design

Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  "The previous 'envelope' icon worked better".

  UX Testing Finding: "All participants associated the icon with an
  alarm or reminder.  They all failed to interact with it when looking
  for missed calls and unread messages. They had to go to the dialer and
  messages separately to check."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367817/+subscriptions

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

[Dx-packages] [Bug 1369993] Re: implement new indicator reveal interaction design

[Victor Tuson Palau]

design to add description so we can review with engineering

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

Title:
  implement new indicator reveal interaction design

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  place holder to disccus and implement this work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1369993/+subscriptions

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

[Dx-packages] [Bug 1369993] [NEW] implement new indicator reveal interaction design

[Victor Tuson Palau]

Public bug reported:

place holder to disccus and implement this work

** Affects: ubuntu-ux
 Importance: Undecided
 Status: Confirmed

** Affects: indicator-messages (Ubuntu)
 Importance: Critical
 Assignee: Pat McGowan (pat-mcgowan)
 Status: Confirmed


** Tags: rtm-14

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ux
   Status: New => Confirmed

** Changed in: indicator-messages (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided => Critical

** Tags added: rtm-14

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

Title:
  implement new indicator reveal interaction design

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  place holder to disccus and implement this work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1369993/+subscriptions

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

[Dx-packages] [Bug 1066971] Re: Launcher "count" overflows when displaying 5+ digits

[Adolfo Jayme]

** Project changed: ayatana-design => hundredpapercuts

** No longer affects: hundredpapercuts

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

Title:
  Launcher "count" overflows when displaying 5+ digits

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  What happens:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The "count" becomes an unreadable mess.

  What shoul happen:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The "count" stretches, allowing for up to 8-9 digits to be displayed.
  3b. The "count" is truncated, still showing the most important parts of the 
number.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Oct 15 18:47:19 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121014)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[ubuntu-tester]

I installed Marco Trevisan's unity package 
(https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) on 
Monday, September 8 and I haven't had this issue since. Usually, I have this 
issue every couple of days so this package seems to correct it.
For information, I have a very very very little display bug : after typing my 
password, when I press enter to unlock, some pixels of the arrow on the right 
of the password field appears to "flicker" (this is not a problem for me).

This package will be released in official repositories ?

Thanks.

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

Title:
  After locking screen there is no input field to type password for
  unlock

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

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  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 i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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