date:20150522

** Branch linked: lp:~bregma/nux/lp-1379960

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

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window (after 2^31ms of uptime)

Status in Compiz:
  New
Status in Nux:
  Confirmed
Status in Unity:
  New
Status in nux package in Ubuntu:
  Confirmed

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)

2015-05-22 Thread Ubuntu Foundations Team Bug Bot

The attachment "Patch for nux-4.0.7+14.10.20141007" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window (after 2^31ms of uptime)

Status in Compiz:
  New
Status in Nux:
  Confirmed
Status in Unity:
  New
Status in nux package in Ubuntu:
  Confirmed

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

This bug was fixed in the package indicator-power -
12.10.6+15.10.20150522-0ubuntu1

---
indicator-power (12.10.6+15.10.20150522-0ubuntu1) wily; urgency=medium

  [ Charles Kerr ]
  * When powerd updates the backlight brightness, update the indicator
slider to show the new value. (LP: #1370791)

 -- CI Train Bot   Fri, 22 May 2015 17:54:53
+

** 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/1370791

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in indicator-power source package in Vivid:
  New
Status in powerd source package in Vivid:
  New

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)

2015-05-22 Thread Paul Sladen

Simon: excellent work.  I have a particular fondness for reading the
write-ups on this time of bug.  It reminds me a little of the infamous
"Doesn't print on Tuesdays" (bug #248619).

Once again, kudos to gradually narrowing down how to replicate it, then
finding it and finally offering the patch.

** Changed in: nux
   Status: New => Confirmed

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

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

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

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

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window (after 2^31ms of uptime)

Status in Compiz:
  New
Status in Nux:
  Confirmed
Status in Unity:
  New
Status in nux package in Ubuntu:
  Confirmed

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

This bug was fixed in the package systemd-shim - 9-1bzr3

---
systemd-shim (9-1bzr3) wily; urgency=medium

  * debian/patches/lp1390120.patch
- Cherrypicked: Use the ntp support for 'systemd-timesyncd.service'
  too (LP: #1390120)

 -- Ken VanDine   Mon, 18 May 2015 10:43:32
-0400

** Changed in: systemd-shim (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open "Time & 
Date" settings and select "Manually" under "Set the time and date:"
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the "Date Time Indicator" at top-right
  3a - Then restart Ubuntu Phone and "Date Time Indicator" shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time & Date settings agree with Old_Time and "Automatically" has been 
selected under "Set the time and date:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)

** Summary changed:

- Menu interaction in fully maximised window causes the next click on the title
bar to restore the window
+ Menu interaction in fully maximised window causes the next click on the title
bar to restore the window (after 2^31ms of uptime)

** Patch added: "Patch for nux-4.0.7+14.10.20141007"

https://bugs.launchpad.net/nux/+bug/1379960/+attachment/4402675/+files/launchpad-bug-1379960.patch

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

Title:
Menu interaction in fully maximised window causes the next click on
the title bar to restore the window (after 2^31ms of uptime)

Status in Compiz:
New
Status in Nux:
New
Status in Unity:
New
Status in unity package in Ubuntu:
New

Bug description:
(Using the Terminal window as an example)
1. Open a Terminal window
2. Maximise a window fully so that its title bar and menu share the top Unity
panel
3. Click the "View" menu (the menu opens)
4. Click the "Search" menu (the "View" menu closes)
5. Click anywhere on the title bar
6. The window restores to non-maximised size

It shouldn't do this, only a double-click should restore the window.

Alternative ways to trigger it:
3. Click the "Terminal" menu
4. Click the "Reset" option
5. Click anywhere on the title bar

3. Click the "Terminal" menu
4. Click inside the main area of the application
5. Click anywhere on the title bar

It looks like something is going wrong with the double-click detection
when a menu is opened and then closed.

Version: Ubuntu 14.04.1
unity 7.2.2+14.04.20140714-0ubuntu1.1
xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window

The bug affects unity via compiz (which uses libnux).

Version:
compiz 1:0.9.12+14.10.20140918-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/1379960

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window

Status in Compiz:
  New
Status in Nux:
  New
Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window

This is a bug in libnux-4.0-0 on amd64, caused by the code in
GraphicsDisplay::MousePress (NuxGraphics/GraphicsDisplayX11.cpp) which
converts the unsigned long timestamp to a signed int:

if ((double_click_counter_ == 1) && ((int)current_time -
(int)last_click_time_ < double_click_time_delay))


The timestamp is in milliseconds, so it becomes negative after about 24.86 days.

The comparison works ok until the final click on the title bar, when 
last_click_time_ is 0.
Subtracting 0 from the negative current_time results in a value that is always 
less than double_click_time_delay.
The unnecessary cast to int should be removed.


Version:
libnux-4.0-0 4.0.7+14.10.20141007-0ubuntu1

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

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

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

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window

Status in Compiz:
  New
Status in Nux:
  New
Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1455241] Re: Gnome window manager dies shortly after login

2015-05-22 Thread Dmitry Shachnev

Then it has nothing to do with gnome-panel, reassigning to Unity.

** Package changed: gnome-panel (Ubuntu) => unity (Ubuntu)

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

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

Title:
  Gnome window manager dies shortly after login

Status in unity package in Ubuntu:
  New

Bug description:
  Whenever I log in, the window manager dies immediately. The file menus
  goes missing in all windows and it is not possible to switch between
  windows with alt+tab. I always have to invoke gnome-wm --replace from
  the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-flashback 1:3.8.0-1ubuntu12.2
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 22:58:20 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-17 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1455241/+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 1455241] [NEW] Gnome window manager dies shortly after login

You have been subscribed to a public bug:

Whenever I log in, the window manager dies immediately. The file menus
goes missing in all windows and it is not possible to switch between
windows with alt+tab. I always have to invoke gnome-wm --replace from
the command line.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-session-flashback 1:3.8.0-1ubuntu12.2
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 14 22:58:20 2015
GsettingsChanges:
 
InstallationDate: Installed on 2015-03-17 (58 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty
-- 
Gnome window manager dies shortly after login
https://bugs.launchpad.net/bugs/1455241
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 1316320] Re: Screen Lock does not prompt for password

2015-05-22 Thread Alkis Georgopoulos

The "no tray" issue was fix-committed in 
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1457730
The "no lock screen" issue was fix-committed with LDM_PASSWORD_HASH.

** Changed in: ltsp
   Status: Triaged => 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/1316320

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Fix Committed
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash

With Onboard displayed on the screen and then opening the Dash, Onboard
is above the Dash and takes input and the Dash accepts this input.
Based on this, this bug is fixed and marking as verification-done.

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

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

Title:
Regression: Default on-screen keyboard Onboard not properly above dash

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

Bug description:
[ Impact ]

Users of the on-screen keyboard cannot properly use the Dash and the
on-screen keyboard at the same time.

[ Test Case ]

1. Install and start the on-screen keyboard Onboard.
2. Open the Dash.
3. Ensure you can interact with Onboard as you would expect.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

Hi,

Some recent update of broke the default on-screen Onboard to work
properly on dash.

In fact, Onboard is shown in dash, as if it was located under dash. It
is particularly visible, when the dash is maximized and covers the
whole screen. However, if I drag Onboard to position it under an icon
in dash and I click on the icon, the corresponding application is not
started; the click goes down to Onboard, which types the letter of the
Onboard key placed at the position of the click.

So, in a few words: dash draws Onboard as if it was covered by dash,
but Onboard behaves as if it is located over dash.

Having a vivid backup from about one month ago, we were able to
determine that the regression seem to have happened because of the
update of libunity-core and the related packages somewhere between one
month ago and today. In fact, the problem appeared in the test after
updating the following packages and versions to the version shipping
currently in the repositories.

libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1
libcairo-gobject2 1.13.0~20140204-0ubuntu1
libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1
libcairo2 1.13.0~20140204-0ubuntu1
libcairo2-dev 1.13.0~20140204-0ubuntu1
unity 7.3.1+15.04.20141128-0ubuntu1
unity-schemas 7.3.1+15.04.20141128-0ubuntu1
unity-services 7.3.1+15.04.20141128-0ubuntu1

Cheers

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413165/+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 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher

The Launcher icons now stay expanded and are not folded while in keynav
mode.  Marking verification-done.

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

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

Title:
  Going back from quicklist to launcher in key-nav mode doesn't unfold
  the launcher

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:
  Fix Committed

Bug description:
  [ Impact ]

  Users the use Launcher keynav mode may end up with a Launcher that is
  not displayed correctly, leaving a poor user experience.

  [ Test Case ]

  1. Make sure there are enough icons in the Launcher to cause the Launcher to 
fold.
  2. Press Alt+F1
  3. Press right-key
  4. Press left-key
  5. Observe the Launcher is not folder while still in keynav mode.

  [ Regression Potential ]

  None observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  1) Press Alt+F1
  2) Press right-key
  3) Press left-key

  Expected result:
  3) The launcher goes back to keynav mode and unfolds completely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1246891/+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 1308265] Re: First password letter not registered in lockscreen if screen off

This no longer occurs with Unity from -proposed.  Marking verification-
done.

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

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

Title:
  First password letter not registered in lockscreen if screen off

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:
  Fix Committed

Bug description:
  [ Impact ]

  Not having the first character registered when trying to unlock the
  lockscreen can most definitely lead to frustration and thus, poor user
  experience.

  [ Test Case ]

  1. Lock the screen and let the monitor blank as well.
  2. Try unlocking the screen by typing your password.
  3. Observe lockscreen unlocks.

  [ Regression Potential ]

  None observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308265/+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 932486] Re: showing quicklist from launcher keynav mode focuses last application

The application window no longer is focused until exiting Launcher
keynav mode. Marking verification-done.

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

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

Title:
showing quicklist from launcher keynav mode focuses last application

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:
Fix Committed

Bug description:
[ Impact ]

Poor user experience due to the app window not being focused as
expected.

[ Test Case ]

0. Have at least one application window open
1. Enter launcher keynav mode with Alt+F1
2. Select a launcher icon with the Up or Down keys.
3. Show the quicklist by pressing Right.
4. Collapse the quicklist by pressing Left.
5. Observe that the app window never has focus during the above steps.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

To reproduce:

0) Have at least one application window open
1) Enter launcher keynav mode with Alt+F1

* Note that when entering keynav mode, the application loses focus.
THe triangle to the right of it's launcher icon is no longer drawn,
and the window title is not displayed in the panel.

2) Select a launcher icon with the Up or Down keys.
3) Show the quicklist by pressing Right.

* Note that the application becomes active again - it's window title
is drawn to the panel, and the triangle to the right of the launcher
icon is drawn again.

4) Collapse the quicklist by pressing Left.

* The app loses focus again.

This seems like inconsistent behavior to me... either the app should
never lose focus when we enter keynav mode, or should not be activated
when we show a quicklist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/932486/+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 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

I have run these Autopilot tests and do not see failures.  Marking
verification-done.

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

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

Title:
  AP test failure:
  unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

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:
  Fix Committed

Bug description:
  [ Impact ]

  Failed Autopilot tests are not good.

  [ Test Case ]

  1. Run 'autopilot run 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click'
  2. Run 'autopilot run 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click'
  3. Observe that the tests don't fail.

  [ Regression Potential ]

  None observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  The following two AP tests consistently ERROR during regular Unity
  testing.

  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
  --
  Empty attachments:
    /var/log/syslog

  unity-log: {{{WARN  2015-03-24 13:43:02 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
128, in test_scaled_window_closes_on_middle_click
  self.assertWindowIsScaledEquals(target_xid, False)
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
    File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
    File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
    File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, self.timeout)
    File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 129, in _callable_wait_for
  new_value = refresh_fn()
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
67, in 
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
    File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 520, in __getattr__
  self.refresh_state()
    File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 474, in refresh_state
  _, new_state = self.get_new_state()
    File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
148832}.
  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
  --
  Empty attachments:
    /var/log/syslog

  unity-log: {{{WARN  2015-03-24 14:00:34 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
148, in test_scaled_window_closes_on_close_button_click
  self.assertWindowIsScaledEquals(target_xid, False)
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
    File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
    File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
    File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, self.timeout)
    File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 129, in _callable_wait_for
  new_value = refresh_fn()
    File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
67, in 
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.

[Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

This bug was fixed in the package lxc-android-config - 0.223

---
lxc-android-config (0.223) vivid; urgency=medium

  [ Oliver Grawert ]
  * usr/bin/tethering: reloading config to get tethering working again

  [Alfonso Sanchez-Beato]
  * fix regression with NM setting DEVICE_IFACE to "ril_0" instead of
"/ril_0" (LP: #1454625)

 -- Ken VanDine   Wed, 20 May 2015 13:17:34
-0400

** Changed in: lxc-android-config (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open "Time & 
Date" settings and select "Manually" under "Set the time and date:"
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the "Date Time Indicator" at top-right
  3a - Then restart Ubuntu Phone and "Date Time Indicator" shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time & Date settings agree with Old_Time and "Automatically" has been 
selected under "Set the time and date:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+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 1447821] Re: Lockscreen does not ask for ldap password

2015-05-22 Thread Fábio Lima

The status is still marked as "Incomplete". Is there any missing
information I need to post?

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

Title:
  Lockscreen does not ask for ldap password

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I manage desktops where the users log into an today updated ubuntu
  14.04.1 amd64 desktop using ldap users.

  When the desktop goes to lockscreen, in order to unlock I may [see 
IMG_20150423_182816.jpg attached]:
  1. Use my right ldap password: Unlock successfully;
  2. Use a wrong ldap password: It doesn't unlock, showing an error message;
  3. Don't use any password, just press "Enter":  Unlock successfully!

  This is a serious security failure. One unauthorized person walking
  around could access a machine and use it.

  There's no references in logs like syslog, auth.log, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1447821/+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 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

** Branch linked: lp:~charlesk/indicator-power/lp-1370791-15.10-adjust-
slider-when-brightness-is-changed-by-powerd

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

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in indicator-power source package in Vivid:
  New
Status in powerd source package in Vivid:
  New

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1456281] Re: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en

** Changed in: canonical-devices-system-image
   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/1456281

Title:
  Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime source package in Vivid:
  Confirmed

Bug description:
  This ticket is to track a missing alarm issue that seems to have
  started showing up between May 15 and 18th.

  in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc-
  proposed/bq-aquaris.en are not showing up at the right time; rather,
  they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that
  didn't go off until 8:30.

  Alesage in Orlando is also reporting missing alarms when he tests on
  arale.

  When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en
  (r9) I'm seeing the same behavior rerported by mzanetti. What's really
  odd though is when I apt-get source that version of indicator-datetime
  and run it myself, things work correctly.

  Alarms also working correctly on mako 15.10 r199.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456281/+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

Re: [Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

2015-05-22 Thread Iain Lane

On Fri, May 22, 2015 at 04:18:50PM +0100, Iain Lane wrote:
> On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
> > ** Changed in: canonical-devices-system-image
> >Status: Confirmed => Fix Released
> 
> I'm not sure what that means but if it means that it's supposed to be
> fixed then it's not yet. I only uploaded one piece to wily. I think
> seb128 is handling the rest (+ vivid/overlay).

Thought this was a different bug. Disregard. :)


-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open "Time & 
Date" settings and select "Manually" under "Set the time and date:"
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the "Date Time Indicator" at top-right
  3a - Then restart Ubuntu Phone and "Date Time Indicator" shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time & Date settings agree with Old_Time and "Automatically" has been 
selected under "Set the time and date:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window

Even restarting Xorg doesn't fix this, only a reboot resolves it.

com/canonical/unity/integrated-menus/double-click-wait is set to the
default (0ms)

If I set it to 300ms, then menu opening is delayed by 300ms but step 6
(The window restores to non-maximised size) occurs immediately upon
clicking as soon as the button is pressed (even if it is not 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/1379960

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window

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

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the "View" menu (the menu opens)
  4. Click the "Search" menu (the "View" menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the "Terminal" menu
  4. Click the "Reset" option
  5. Click  anywhere on the title bar

  3. Click the "Terminal" menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1379960/+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 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

2015-05-22 Thread Ken VanDine

** Changed in: lxc-android-config (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: systemd-shim (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open "Time & 
Date" settings and select "Manually" under "Set the time and date:"
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the "Date Time Indicator" at top-right
  3a - Then restart Ubuntu Phone and "Date Time Indicator" shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time & Date settings agree with Old_Time and "Automatically" has been 
selected under "Set the time and date:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash

2015-05-22 Thread Francesco Fumanti

Hi,

Unfortunately, I cannot be of much help anymore: My trusty installation
that I keep for testing purposes has not been showing the bug anymore
for some time. It may be due to it running a unity version from 20141212
and/or a newer version of Onboard from the Onboard PPA.

So I disabled the security, recommended, proposed, backports and Onboard
PPA sources in order to replicate the bug; but I was only able to
replicate it partially: in fact, Onboard looked after the downgrade as
if it was covered by Dash, but a click on it restored its look by making
it look as if it is above Dash. (If I remember correctly, in the
original bug description, Onboard behaved as if it was above Dash, but
looked all the time as if it was below Dash.)

Afterwards, I enabled the sources again, apart the Onboard PPA, and
installed all the updates. The problem disappeared again, but it
probably cannot count, as I was not able to replicate the exact original
bug.

Cheers

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

Title:
Regression: Default on-screen keyboard Onboard not properly above dash

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

Bug description:
[ Impact ]

Users of the on-screen keyboard cannot properly use the Dash and the
on-screen keyboard at the same time.

[ Test Case ]

1. Install and start the on-screen keyboard Onboard.
2. Open the Dash.
3. Ensure you can interact with Onboard as you would expect.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

Hi,

Some recent update of broke the default on-screen Onboard to work
properly on dash.

So, in a few words: dash draws Onboard as if it was covered by dash,
but Onboard behaves as if it is located over dash.

Cheers

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413165/+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 995188] Re: launcher stays on laptop screen even if configured to be on external one

Since I can't reproduce this issue and no one has said that it still
occurs, I'm going to mark this Fix Released.  If it does still occur,
then this bug report can be reopened or a new one can be opened.

Thanks!

** Changed in: unity
Milestone: 7.3.3 => None

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

** Changed in: unity (Ubuntu)
   Status: Incomplete => 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/995188

Title:
  launcher stays on laptop screen even if configured to be on external
  one

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Since I installed ubuntu 12.04, I don't care much for the sticky
  edges, so I want my launcher only on my left screen (my external
  screen).

  Behaviour of the launcher placement setting:
  1) All screens: works as expected
  2) Laptop: works as expected
  3) Kingston Tech Corporation 20" (my external monitor): launcher stays on 
laptop!

  My laptop is a Dell Studio 1557, Intel i5, AMD HD 5470 GPU. I think it
  is probably related to the fact that most people put there external
  monitor to the right of there laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/995188/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator

** Changed in: canonical-devices-system-image
   Status: In Progress => 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/1382861

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Vivid:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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

Re: [Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

2015-05-22 Thread Iain Lane

On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
> ** Changed in: canonical-devices-system-image
>Status: Confirmed => Fix Released

I'm not sure what that means but if it means that it's supposed to be
fixed then it's not yet. I only uploaded one piece to wily. I think
seb128 is handling the rest (+ vivid/overlay).

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open "Time & 
Date" settings and select "Manually" under "Set the time and date:"
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the "Date Time Indicator" at top-right
  3a - Then restart Ubuntu Phone and "Date Time Indicator" shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time & Date settings agree with Old_Time and "Automatically" has been 
selected under "Set the time and date:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+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 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

** Changed in: canonical-devices-system-image
   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/1370791

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in indicator-power source package in Vivid:
  New
Status in powerd source package in Vivid:
  New

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)