[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Jean-Baptiste Lallement]

I've a similar issue on Groovy. I got it 2 days in a row after my daily package 
update.
Reverting the machine to a state before the upgrade and re-upgrading the same 
packages doesn't reproduce the issue. However, when it worked with the same 
package update the message "Unexpected error response from GetNameOwner()" is 
not present in the logs.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[12

[Dx-packages] [Bug 1391981] Re: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других приме

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1751595
   package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent 
d'autres instances du paquet libunity9:i386

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

Title:
  package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to
  install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-
  loader“, који се разликује од других примерака пакета „libunity9:i386“

Status in libunity:
  New
Status in libunity package in Ubuntu:
  New

Bug description:
  Random crash on startup

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libunity9 7.1.4+14.10.20140808-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Wed Nov 12 18:45:13 2014
  DuplicateSignature: package:libunity9:7.1.4+14.10.20140808-0ubuntu1:покушавам 
да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других 
примерака пакета „libunity9:i386“
  ErrorMessage: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, 
који се разликује од других примерака пакета „libunity9:i386“
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: libunity
  Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to 
install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, 
који се разликује од других примерака пакета „libunity9:i386“
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1391981/+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 1748952] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: intentando sobreescribir el compartido `/usr/bin/unity-scope-loader', que es distinto de otra

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1751595
   package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent 
d'autres instances du paquet libunity9:i386

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: intentando sobreescribir el compartido `/usr/bin
  /unity-scope-loader', que es distinto de otras instancias del paquetes
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  i lose my ubuntu store and unity tweak tool, so i install again store
  software ubuntu.

  when i try install unity tweak tool, don't work, and said broken
  pagetes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Feb 11 19:56:16 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
  InstallationDate: Installed on 2017-09-04 (161 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
  UpgradeStatus: Upgraded to xenial on 2018-02-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1748952/+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 1606002] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other insta

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of bug 1605911
   package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/bin/unity-scope-loader', which is different 
from other instances of package libunity9:i386
** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  not sure from this error message was poped up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 18:38:14 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1606002/+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 1582399] Re: package libunity9 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/bin/unity-scope-loader« zu überschreiben, welches verschie

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+15.10.20151002-0ubuntu2 failed to
  install/upgrade: Versuch, gemeinsam benutztes »/usr/bin/unity-scope-
  loader« zu überschreiben, welches verschieden von anderen Instanzen
  des Paketes libunity9:i386 ist

Status in libunity package in Ubuntu:
  New

Bug description:
  I installed ScummVM from the Lubuntu Software Center. But it didn't work. I 
removed it with the Lubuntu Software Center.
  After that I downloaded ScummVM 1.8.0 Ubuntu package from their website. 
While trying to install it, the error occured.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 16 22:28:58 2016
  ErrorMessage: Versuch, gemeinsam benutztes »/usr/bin/unity-scope-loader« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libunity9:i386 ist
  InstallationDate: Installed on 2016-04-17 (29 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+15.10.20151002-0ubuntu2 failed to 
install/upgrade: Versuch, gemeinsam benutztes »/usr/bin/unity-scope-loader« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libunity9:i386 ist
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1582399/+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 1504989] Re: libunity9: File conflict in Multi-Arch: same package

[Jean-Baptiste Lallement]

** Summary changed:

- package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/bin/unity-scope-loader', which is different 
from other instances of package libunity9:i386
+ libunity9: File conflict in Multi-Arch: same package

** Summary changed:

- libunity9: File conflict in Multi-Arch: same package
+ libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  libunity9: File conflict in Multi-Arch: same package (/usr/bin/unity-
  scope-loader)

Status in libunity:
  Confirmed
Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  This happened when I tried to install unity-webapps-service after a
  forced an upgrade to Wily with sudo do-release-upgrade -d

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 11 19:54:49 2015
  DuplicateSignature: package:libunity9:7.1.4+15.10.20151002-0ubuntu1:trying to 
overwrite shared '/usr/bin/unity-scope-loader', which is different from other 
instances of package libunity9:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2013-05-04 (890 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: Upgraded to wily on 2015-10-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1504989/+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 1325524] Re: package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other insta

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity:
  Confirmed
Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I installed lubuntu, a clean install. Then on top of that I installed
  older packages through dpkg. These packages were also from a
  relatively clean install. During dpkg install libunity failed.

  After a reboot of the system I get "No session for pid " which is
  for lxsession -s Lubuntu -e LXDE. In the logout menu shutdown and
  reboot is also missing. This bug might be related to this one:
  https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-
  privileges/+bug/1240336

  I'm using Lubuntu 14.10

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Mon Jun  2 12:36:29 2014
  DuplicateSignature: package:libunity9:7.1.4+14.04.20140210-0ubuntu1:trying to 
overwrite shared '/usr/bin/unity-scope-loader', which is different from other 
instances of package libunity9:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2014-06-02 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: libunity
  Title: package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1325524/+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 1605911] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other insta

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I don't know what's going on.  All I know is that I'm trying to
  install some programs to Ubuntu and it isn't working.  I tried the
  apt-get install -f to no avail.  I'm trying to install the Chrome
  browser from Google and Tetravex plus some updates and they won't
  install.   I'm new to Ubuntu and wanted to try it out as an
  alternative to Windows.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 13:35:07 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1605911/+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 1629450] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other insta

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  got unexpected error during installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Sep 30 21:57:57 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libunity9:i386 (7.1.4+16.04.20160701-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libunity9_7.1.4+16.04.20160701-0ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared '/usr/bin/unity-scope-loader', which is 
different from other instances of package libunity9:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2014-04-27 (886 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1629450/+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 1725933] Re: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" (condiviso), diverso da altre istanze

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1504989
   libunity9: File conflict in Multi-Arch: same package 
(/usr/bin/unity-scope-loader)

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

Title:
  package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to
  install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-
  loader" (condiviso), diverso da altre istanze del pacchetto
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libunity9 7.1.4+17.10.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 11:39:29 2017
  ErrorMessage: tentata sovrascrittura di "/usr/bin/unity-scope-loader" 
(condiviso), diverso da altre istanze del pacchetto libunity9:i386
  InstallationDate: Installed on 2017-10-12 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: libunity
  Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to 
install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" 
(condiviso), diverso da altre istanze del pacchetto libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1725933/+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 1747265] Re: libunity9 7.1.4+17.10.20170605-0ubuntu1: File conflict in Multi-Arch: same package

[Jean-Baptiste Lallement]

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

** Summary changed:

- package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent 
d'autres instances du paquet libunity9:i386
+ libunity9 7.1.4+17.10.20170605-0ubuntu1: File conflict in Multi-Arch: same 
package

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

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

** This bug has been marked a duplicate of bug 1504989
   package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/bin/unity-scope-loader', which is different 
from other instances of package libunity9:i386

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

Title:
  libunity9 7.1.4+17.10.20170605-0ubuntu1: File conflict in Multi-Arch:
  same package

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  cannot upgrade because of this

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libunity9 7.1.4+17.10.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   libunity9:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Feb  4 15:42:43 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-04  15:42:29
   Commandline: apt --fix-broken install
   Requested-By: bouet (1000)
   Install: libunity9:i386 (7.1.4+17.10.20170605-0ubuntu1, automatic)
  ErrorMessage: tentative de remplacement de « /usr/bin/unity-scope-loader », 
qui est différent d'autres instances du paquet libunity9:i386
  InstallationDate: Installed on 2017-06-02 (246 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to 
install/upgrade: tentative de remplacement de « /usr/bin/unity-scope-loader », 
qui est différent d'autres instances du paquet libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747265/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Jean-Baptiste Lallement]

I reopened bug 1654241

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Jean-Baptiste Lallement]

I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders
the device completely unusable (cf bug 1654241)

Marking as verification-failed.

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

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Committed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1579837] Re: Issue after wizard with policykit

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: backlog => 13

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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 1584849] Re: Creating a log on a non-default thread causes it to hang

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Creating a log on a non-default thread causes it to hang

Status in Canonical System Image:
  Fix Committed
Status in Zeitgeist Framework:
  Unknown
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  When creating a Log object it creates a mainloop to wait on the proxy
  object. It unfortunately does this with NULL has its context which
  means it uses the main thread's context instead of the thread it is
  running on. This causes a hang as no one gets events then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584849/+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 1597251] Re: It is always located as "Shanghai" once you select a city of China in wizard.

[Jean-Baptiste Lallement]

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  It is always located as "Shanghai" once you select a city of China in
  wizard.

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 119
  device name: turbo
  channel: ubuntu-touch/rc-proposed/meizu-pd.en
  last update: 2016-06-29 14:55:38
  version version: 119
  version ubuntu: 20160629
  version device: 20160617-82a5c0d
  version custom: 20160626-981-7-5

  Precondition:
  New flashed phone.

  Steps:
  1.Boot the phone and the phone boots ,then the UI enters
  wizard interface.
  2.Following the wizard and enter any China city name ,such as 
"Beijing","Shenzhen" to setup the timezone, and then complete the wizard.
  3.Swipe down from the notification bar and select "Time&Date".Check the 
location.

  Actual result:
  The location is "Shanghai" in "Time&Date" option.
  Expected result:
  I think it should be the city name what you set in  the wizard,instead of 
always displaying "Shanghai"

  Notes:
  If you select any foreign city in the wizard,such as "New York" ,the issue is 
not reproduced.
  And the issue is not reproduced in other device,such as Arale,Krillin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597251/+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 1470080] Re: Broken icon in indicator when iphone attached

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Broken icon in indicator when iphone attached

Status in Canonical System Image:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470080/+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 1593523] Re: Indicator should not show events from unselected calendars

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Indicator should not show events from unselected calendars

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  The indicator should not display events from calendars that are
  unselected on evolution or calendar app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593523/+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 1593692] Re: Individual instances of recurring events is not displayed right on indicator

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Individual instances of recurring events is not displayed right on
  indicator

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  If you create a recurring event and change the time of only one
  instance of this event, this is not propagated to the indicator. The
  indicator still showing info from the parent event.

  HOW TO REPRODUCE
  =

  1 - Create a recurring event every day starting 2 days ago
  2 - Edit Today instance of this event to happen 2 hours late

  EXPECTED RESULT
  
  Indicator get update with the new time for the event

  CURRENT RESULT
  ==
  Indicator still showing the event at the parent's time

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593692/+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 1576316] Re: User cannot change Input source

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Incomplete => Won't Fix

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

Title:
  User cannot change Input source

Status in Canonical System Image:
  Won't Fix
Status in accountsservice package in Ubuntu:
  Expired
Status in ubuntu-system-settings package in Ubuntu:
  Expired

Bug description:
  Log:
  http://pastebin.ubuntu.com/16097735/

  Could be related to bug 1512002?

  What happens:
  User tries to change input source on own user and is asked to authenticate:

  phablet@ubuntu-phablet:~$  gdbus call -y -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User32011 -m 
org.freedesktop.Accounts.User.SetInputSources "[{'xkb': 'en'}]"
  Error: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: 
Authentication is required
  (According to introspection data, you need to pass 'aa{ss}')

  What should happen:
  Not sure if this is a regression or what? We call this from System 
Settings—do we have to change it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576316/+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 1588162] Re: Time in header is UTC instead oft UTC+2

[Jean-Baptiste Lallement]

There is something wrong in the screenshot, it shouldn't show Etc/UTC or
Europe/Berlin but the name of the city instead, like "Berlin". Also it
is not possible to select UTC as timezone.

could you connect to the device (adb, ssh or terminal all) and paste the output 
of the following commands:
- system-image-cli -i
- timedatectl

Can you also reboot your device, and if the problem occurs reliably,
attach /var/log/syslog and /home/phablet/.cache/upstart/indicator-
datetime.log

I also noticed in the screenshot that the SIM is in roaming mode, not
sure if it's important.

Thanks.

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

Title:
  Time in header is UTC instead oft UTC+2

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I think it happened After OTA 11. All other time displays are correct
  also the alarm matches the real time, checked the kalendar too the red
  time indicator is also correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1588162] Re: Time in header is UTC instead oft UTC+2

[Jean-Baptiste Lallement]

@Roascio, it seems to be a slightly different issue.Your saying the events are 
forwarded +2h but the time in the top panel is correct, while the original 
issue in this report is that the date in the indicator is incorrect (similar to 
bug 1567940)
If your issue doesn't exactly match the problem described here can you please 
file a new bug report? Thanks.

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

Title:
  Time in header is UTC instead oft UTC+2

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I think it happened After OTA 11. All other time displays are correct
  also the alarm matches the real time, checked the kalendar too the red
  time indicator is also correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1588162] Re: Time in header is UTC instead oft UTC+2

[Jean-Baptiste Lallement]

Thanks for your report.

does the problem disappear after a reboot? 
if the time on the greeter also incorrect?


** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

Title:
  Time in header is UTC instead oft UTC+2

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I think it happened After OTA 11. All other time displays are correct
  also the alarm matches the real time, checked the kalendar too the red
  time indicator is also correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1588162] Re: Time in header is UTC instead oft UTC+2

[Jean-Baptiste Lallement]

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Time in header is UTC instead oft UTC+2

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I think it happened After OTA 11. All other time displays are correct
  also the alarm matches the real time, checked the kalendar too the red
  time indicator is also correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1581089] Re: Clock app opened when closing Alarms

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  Clock app opened when closing Alarms

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Recently, when my alarm goes off in the morning, and I tap the OK
  button to close it, that when I later unlock my phone for the first
  time, the clock app is opened. The clock app should not be opened
  whenever I cancel an alarm.

  This is on rc-proposed on hammerhead (Nexus 5), but I don't see any
  reason this would be device specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581089/+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 1559731] Re: Battery indicator turns red at 30% on desktop

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
Milestone: None => 12

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

Title:
  Battery indicator turns red at 30% on desktop

Status in Canonical System Image:
  Fix Committed
Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-power source package in Xenial:
  Triaged

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1559731/+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 1581089] Re: Clock app opened when closing Alarms

[Jean-Baptiste Lallement]

** Tags added: regression-proposed

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

Title:
  Clock app opened when closing Alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Recently, when my alarm goes off in the morning, and I tap the OK
  button to close it, that when I later unlock my phone for the first
  time, the clock app is opened. The clock app should not be opened
  whenever I cancel an alarm.

  This is on rc-proposed on hammerhead (Nexus 5), but I don't see any
  reason this would be device specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581089/+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 1579837] Re: Issue after wizard with policykit

[Jean-Baptiste Lallement]

removed the blocker tags and retarget to OTA12. The package has been
unseeded which temporarily fixes the issue for OTA11

** Tags removed: lt-blocker regression-proposed

** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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 1401802] Re: [Scopes] Calendar reminder notifications became queued, non-interactive and easy to miss

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
Milestone: None => 11

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

Title:
  [Scopes] Calendar reminder notifications became queued, non-
  interactive and easy to miss

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  With the recent indicator-datetime update the reminder notifications time out 
and are not interactive any more, meaning that:
  - can't dismiss (have to wait for the sound/notification to time out)
  - can't snooze (I know the feature didn't work, but that was a missing 
feature, not a thing we didn't want?)
  - if you missed the notification, you missed the reminder

  Not sure if the reason is the same, but they started queueing, too,
  i.e. if there's two reminders for the same time, sound will play for
  both (bug #1340248), but the two notifications will be shown one after
  another.

  This is a UX regression in my opinion, even if it fixes bug #1320880.

  There is actually no clear design for this, I'm afraid,
  
https://sites.google.com/a/canonical.com/apps-and-platform-team/3-platform/2-notifications

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20141208-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: armhf
  Date: Fri Dec 12 08:59:10 2014
  InstallationDate: Installed on 2014-12-12 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141212-020204)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  -- UX Comment --

  We've added the desired behaviour in the latest specification for
  notifications bubbles:

  Pages: 10-22 Notification bubble in normal use
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.6g43lpfdbptu

  Specific to remiders notifications: Notifications from missed calls,
  calendar events and reminders, are exceptions and won't ever be
  presented in a summary layout because of their different nature. They
  are time-sensitive (especially if these events involve other people
  actively waiting on a response) and may change the user's behaviour in
  the real world.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1401802/+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 1508438] Re: Do not notify for events marked as not attending

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
Milestone: None => 11

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

Title:
  Do not notify for events marked as not attending

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508438/+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 1567940] Re: time displayed wrongly on production phone

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: None => 11

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

Title:
  time displayed wrongly on production phone

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1566341] Re: ``Tomorrow'' appears untranslated

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  ``Tomorrow'' appears untranslated

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16''
  thread:

  Richard Somlói:
  >  "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the 
previous images. Could somebody confirm it with another language?

  sil2100:
  > I just checked the indicator-datetime language pack and see Tomorrow as 
translated in all possible places there, so at least it's not a problem with 
the langpack itself. I would recommend filling in a bug against 
indicator-datetime so that the developers can take a look what's wrong.
  > But there is certainly something wrong since I get the same issue with the 
Polish locale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566341/+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 1567940] Re: time displayed wrongly on production phone

[Jean-Baptiste Lallement]

read: but* different

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

Title:
  time displayed wrongly on production phone

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1567940] Re: time displayed wrongly on production phone

[Jean-Baptiste Lallement]

Thanks.

I reproduced a similar for different issue on my krillin. The difference
is that I get 3 different time for RTC, universal and local time.

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Status: Incomplete => Confirmed

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  time displayed wrongly on production phone

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  My phone displays the time an hour out on the lockscreen and notification 
bar. It is a production BQ 4.5 phone, and I am using it in the UK where 
Canonical are based, so this isn't a weird edge case situation at all. I have 
reflashed it altogether, and upgraded yesterday to OTA-10. It has a read only 
filesystem.
  If I go to time and date, and try to change my timezone it shows 
Europe/London UTC+1 and below it shows the correct time ticking away with BST 
at the end of it.
  If I try to change the timezone I get the daft list of cities, selecting them 
now highlights them in blue rather than orange, but I can't choose any of them. 
I have zero clue where there might be any indication of an error log to look 
for.

  
  http://people.ubuntu.com/~alanbell/phone/timezone.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567940/+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 1563213] [NEW] Indicator session not localized

[Jean-Baptiste Lallement]

Public bug reported:

Test case.
- Flash the device.
- Switch to Spanish.
- Open indicator session.

Expected result.
- Indicator session is translated to Spanish.

Actual result.
- Indicator session is shown in English.

current build number: 66
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
device name: frieza

There are no indicator-session.mo files shipped in the system. Is
indicator-session configured to export the translations to langpacks?

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: Alejandro J. Cura (alecu)
 Status: Confirmed

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

** Also affects: indicator-session (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
   Indicator session not localized

Status in Canonical System Image:
  Confirmed
Status in indicator-session package in Ubuntu:
  New

Bug description:
  Test case.
  - Flash the device.
  - Switch to Spanish.
  - Open indicator session.

  Expected result.
  - Indicator session is translated to Spanish.

  Actual result.
  - Indicator session is shown in English.

  current build number: 66
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  device name: frieza

  There are no indicator-session.mo files shipped in the system. Is
  indicator-session configured to export the translations to langpacks?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563213/+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 1560188] Re: unity8 hang w/ CPU pegged

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  unity8 hang w/ CPU pegged

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  To trigger:
  1. Wipe (or freshly flash) rc-proposed on a krillin or mako
  2. Log in, configure time zone
  3. Tilt the phone to make the screen rotate

  At this point, the UI stopped responding and 'top' showed 100% CPU
  being used by unity8.

  I tried to get data from gdb, but it wasn't very helpful:
  (gdb) bt
  #0  0xa803cce2 in ?? ()
  #1  0xa803cb98 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  More details are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560188/+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 1560359] Re: External drives needs a better icon

[Jean-Baptiste Lallement]

** Also affects: humanity-icon-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Low

** Also affects: ciborium (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  External drives needs a better icon

Status in Canonical System Image:
  Confirmed
Status in ciborium package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  The icon for external drives has no background. While the icon itself
  is quite nice, the combination of no background and the UbuntuShape in
  the dash make it look really out of place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560359/+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 1557571] Re: Upcoming event ETA appears to fall out of sync

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Upcoming event ETA appears to fall out of sync

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Described by ToyKeeper @ https://trello.com/c/S0yjk9mW/2892-893
  -ubuntu-landing-003-indicator-datetime-dbarth:

  > Also, the indicator sometimes gets the wrong time until an event is
  scheduled to start. As an example, I had an event scheduled for 23:50.
  At 23:43 I pulled down the indicator and it said 7 minutes 'till. At
  23:45 I tried again and it still said 7 minutes. I checked again at
  23:47 and it said 3 minutes till. I checked again at 23:50 and it
  still said 3 minutes. At 23:51 the item disappeared, even though the
  event was an hour long. So, it updates infrequently and doesn't show
  events while they're active (except for the first minute).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557571/+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 1474078] Re: Provide a way to disable notifications from calendar events

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Provide a way to disable notifications from calendar events

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  While I like having the calendar on the phone I do not want an audible 
notification for the events. 
  Would we simply add the calendar app to the Notifications page?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474078/+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 1532731] Re: Battery indicator still wrong on BQ Aquaris 4.5

[Jean-Baptiste Lallement]

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

Thanks for your report. This is a duplicate of bug 1471913. The problem
is being investigated.

** This bug has been marked a duplicate of bug 1471913
   Battery statistics are incorrect on MTK based devices

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

Title:
  Battery indicator still wrong on BQ Aquaris 4.5

Status in Canonical System Image:
  New
Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  The Battery indicator still works wrong on BQ Aquaris 4.5 with OTA
  8.5.

  The indicator claims that the remaining charge is X percent (lets say
  50%), but within minutes the phone switches off.

  OS: ATA-8.5
  Build: Ubuntu 15.04 - armhf (20151210-005527)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532731/+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 1470767] Re: No audible warning about low battery charge

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  No audible warning about low battery charge

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  In Progress
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-touch-sounds package in Ubuntu:
  In Progress

Bug description:
  Note: I'm not sure if this is the right project for this bug report.

  Phone bq Aquaris E4.5 Ubuntu Edition
  OS Ubuntu 15.04 (r23)

  There's no audible warning when the battery charge is very low. Only
  way to know about the low charge is by looking at the phone screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470767/+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 1515924] Re: Indicator-datetime events are in wrong time format with other language

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1512924
   Timestamps not localized in notifications

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

Title:
  Indicator-datetime events are in wrong time format with other language

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hey!

  Indicator-datetime events are in wrong time format with other
  language.I use the rc-channel with the build of 12th November. I
  changed the language to Hungarian and added some events in the
  calendar, then I checked the datetime indicator:

  Expected:

  Névtelen17.00
  NévtelenHolnap 9.00
  Riasztás  H 7.00
  NévtelenNov. 21. Szo 9.00

  What I see:

  Névtelen17:00
  NévtelenTomorrow 09:00
  Riasztás  H 7:00
  NévtelenSzo 21. nov. 09:00

  So it's fully untranslated (tomorrow), partly untranslated (H 7:00)
  and in wrong format (Szo 21. nov. 09:00) It was okay with OTA-7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515924/+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 1515924] Re: Indicator-datetime events are in wrong time format with other language

[Jean-Baptiste Lallement]

I confirm that in French 'Tomorrow' is not translated either.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  Indicator-datetime events are in wrong time format with other language

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hey!

  Indicator-datetime events are in wrong time format with other
  language.I use the rc-channel with the build of 12th November. I
  changed the language to Hungarian and added some events in the
  calendar, then I checked the datetime indicator:

  Expected:

  Névtelen17.00
  NévtelenHolnap 9.00
  Riasztás  H 7.00
  NévtelenNov. 21. Szo 9.00

  What I see:

  Névtelen17:00
  NévtelenTomorrow 09:00
  Riasztás  H 7:00
  NévtelenSzo 21. nov. 09:00

  So it's fully untranslated (tomorrow), partly untranslated (H 7:00)
  and in wrong format (Szo 21. nov. 09:00) It was okay with OTA-7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515924/+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 1483854] Re: url-dispatcher stops working, can't open links from scopes or apps

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  url-dispatcher stops working, can't open links from scopes or apps

Status in Canonical System Image:
  Fix Committed
Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  Trying to use the url dispatcher I got this error when trying to go to
  this url and other too:

  ** (process:31929): WARNING **: Unable to dispatch url
  
'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'scope://com.canonical.scopes.photos_photos' is not handleable by
  the URL Dispatcher

  then in the log I found this:

  ** (process:2011): WARNING **: Unable to create tables: database is locked
  ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed

  
  After all, ted suggested that restarting the url dispatcher would work and it 
did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483854/+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 1417188] Re: Shell frozen/crashed when alarm triggered

[Jean-Baptiste Lallement]

We are closing  this bug report because it lacks the information we need to 
investigate the problem, as described in the previous comments. Please reopen 
it if you can give us the missing information, and don't hesitate to submit bug 
reports in the future. 
To reopen the bug report you can click on the current status, under the Status 
column, and change the Status back to "New". 
Thanks again!

** Changed in: canonical-devices-system-image
   Status: Incomplete => Invalid

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

Title:
  Shell frozen/crashed when alarm triggered

Status in Canonical System Image:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  rtm build 224 on krillin

  - I set an alarm for 9am with the clock app and then went to bed
  - The alarm was ringing in the morning
  - The phone screen was black
  - I pressed the power button to turn on the screen and there was no 
notification on the screen, just the greeter
  - The shell was completely frozen. I couldn't unlock or do anything, yet the 
alarm played on

  I had to hold down the power key to hard boot the phone as there was
  no way to silence the alarm, the volume keys were not working either.

  Found the attached crash file in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417188/+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 1476029] Re: Bluetooth settings contradict

[Jean-Baptiste Lallement]

** 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-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1476029

Title:
  Bluetooth settings contradict

Status in Canonical System Image:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released

Bug description:
  In ota4 if bluetooth is switched to "on" in the quick settings bar, it
  still remains in "off" position  in the System Settings. Then, if
  bluetooth is set to "on" with the System Settings app, it's status is
  switched to the opposite ("off") in the quick settings bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476029/+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 1317860] Re: the phone should switch itself off before completely draining battery

[Jean-Baptiste Lallement]

** Tags added: power-bugs

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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 1415480] Re: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  [indicators]/OSD provide no visual clue that they modify bluetooth
  device volumes

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Triaged
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu:
  Fix Committed

Bug description:
  Connect a bluetooth audio device (headset, speakers) to the ubuntu
  phone.

  Play music/enter into a call, so that you have active audio to the
  device.

  Adjust the volume, using the UI or keys on the ubuntu phone.

  The volume of the bluetooth headset changes (good) but the ui contains
  no clue that this is what the phone is doing (less good). The standard
  volume indicator is shown. This can lead to user confusion if they are
  not currently using the paired bluetooth accessory, and have forgotten
  it is paired. On other devices the volume indicator changes to provide
  visual feedback that the bluetooth device volume is being set.

  --

  Desired resolution:

  Please use this icon to replace the volume icon. The icon is bluetooth
  volume which we had design already.

  https://www.dropbox.com/s/a5r3ro1h0917p0a/audio-speakers-bluetooth-
  symbolic.svg?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415480/+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 1489037] Re: Change default alarm sound to "Alarm clock.ogg"

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015

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

Title:
  Change default alarm sound to "Alarm clock.ogg"

Status in Canonical System Image:
  In Progress
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  With OTA-6 (as per bug 1354370), the default alarm sound has been
  changed from "Suru arpeggio.ogg" to "Alarm clock.ogg". Indicator-
  datetime will have to set this as default on its end.

  Note: Clock App will set "Alarm clock.ogg" as the default alarm sound
  for new alarms created by the user starting with clock app v3.5.362.
  This bug is to ensure that the fallback alarm played by indicator-
  datetime is also "Alarm clock.ogg" (which is used when the user sets
  an invalid alarm tone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489037/+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 1502787] Re: User session doesn't start

[Jean-Baptiste Lallement]

I moved away ~/.cache/compizconfig-1 and reset the dconf settings and it
somehow fixed the problem.

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

Title:
  User session doesn't start

Status in unity package in Ubuntu:
  New

Bug description:
  On wily, after applying latest updates, my user session doesn't start
  properly. There is only a background, a cursor and context menus but
  no panel or launcher. Guest session works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150921-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct  5 09:48:57 2015
  InstallationDate: Installed on 2013-09-03 (761 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=fr_FR.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/ubuntu/+source/unity/+bug/1502787/+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 1502787] Re: User session doesn't start

[Jean-Baptiste Lallement]

** Attachment added: "compiz.strace.gz"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1502787/+attachment/4484456/+files/compiz.strace.gz

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

Title:
  User session doesn't start

Status in unity package in Ubuntu:
  New

Bug description:
  On wily, after applying latest updates, my user session doesn't start
  properly. There is only a background, a cursor and context menus but
  no panel or launcher. Guest session works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150921-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct  5 09:48:57 2015
  InstallationDate: Installed on 2013-09-03 (761 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=fr_FR.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/ubuntu/+source/unity/+bug/1502787/+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 1502787] [NEW] User session doesn't start

[Jean-Baptiste Lallement]

Public bug reported:

On wily, after applying latest updates, my user session doesn't start
properly. There is only a background, a cursor and context menus but no
panel or launcher. Guest session works fine.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity 7.3.2+15.10.20150921-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Mon Oct  5 09:48:57 2015
InstallationDate: Installed on 2013-09-03 (761 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  User session doesn't start

Status in unity package in Ubuntu:
  New

Bug description:
  On wily, after applying latest updates, my user session doesn't start
  properly. There is only a background, a cursor and context menus but
  no panel or launcher. Guest session works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150921-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct  5 09:48:57 2015
  InstallationDate: Installed on 2013-09-03 (761 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=fr_FR.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/ubuntu/+source/unity/+bug/1502787/+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 1502787] Re: User session doesn't start

[Jean-Baptiste Lallement]

~/.xsession-errors
~/.cache/upstart
/var/log/lightdm

** Attachment added: "1502787.logs.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1502787/+attachment/4484387/+files/1502787.logs.tgz

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

Title:
  User session doesn't start

Status in unity package in Ubuntu:
  New

Bug description:
  On wily, after applying latest updates, my user session doesn't start
  properly. There is only a background, a cursor and context menus but
  no panel or launcher. Guest session works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150921-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct  5 09:48:57 2015
  InstallationDate: Installed on 2013-09-03 (761 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=fr_FR.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/ubuntu/+source/unity/+bug/1502787/+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 1370008] Re: URL Dispatcher Should Prompt on Bad URL

[Jean-Baptiste Lallement]

** No longer affects: gallery-app (Ubuntu)

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

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370008/+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 1466769] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1370008
   URL Dispatcher Should Prompt on Bad URL

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-
  service:url-dispatcher-bad-url

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-datetime.  This problem was most recently seen
  with version 13.10.0+15.10.20150515-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/c1163bf25c27b7a34f210cc8e712ce6c828d0f0b
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1466769/+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 1481913] Re: UI volume warnings need revision

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  UI volume warnings need revision

Status in Canonical System Image:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  As raised in OEM bug #1474364 (the title there is poor), the warning
  scheme used by Ubuntu does not currently follow the letter of the EU
  regulations for mobile devices (it seems to follow the spirit).

  Design have now reviewed the regulations (bug #1480912), and propose:

  https://wiki.ubuntu.com/Sound#limits

  This is the diff:
  https://wiki.ubuntu.com/Sound?action=diff&rev2=146&rev1=145

  The UI notification scheme needs to be updated to match the new
  design.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+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 1473029] Re: notification (image update, gmail, calls) displayed twice

[Jean-Baptiste Lallement]

There is no log file named indicator-messages.log (only old archived
files)

** Changed in: indicator-messages (Ubuntu)
   Status: Incomplete => 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/1473029

Title:
  notification (image update, gmail, calls) displayed twice

Status in Canonical System Image:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes notifications are displayed twice in the indicator. It
  happens randomly with all kind of notifications (image update, gmail,
  calls) Push client logs shows a single notification. There is nothing
  specific to reproduce, sometimes it happens, sometimes it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+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 1473029] Re: notification (image update, gmail, calls) displayed twice

[Jean-Baptiste Lallement]

It just happened for a system update notification. Here is the output
(slightly reindented) that shows 2 identical x-canonical-message-actions
sections:

$ gdbus call --session --dest com.canonical.indicator.messages --object-path 
/com/canonical/indicator/messages/phone --method org.gtk.Menus.Start [0,1]
([
(uint32 0, uint32 0, [{'action': <'indicator.messages'>, 'action-namespace': 
<'indicator'>, 'x-canonical-type': <'com.canonical.indicator.root'>, 
':submenu': <(uint32 1, uint32 0)>}]),
(1, 0, [{':section': <(uint32 1, uint32 1)>}, {':section': <(uint32 1, uint32 
2)>}, {':section': <(uint32 1, uint32 3)>}]),
(1, 1,
[
{'x-canonical-message-actions': <<@aa{sv} []>>, 'target': , 
'x-canonical-time': , 'x-canonical-type': 
<'com.canonical.indicator.messages.messageitem'>, 'x-canonical-app-icon': 
<('file', <'file:///usr/share/ubuntu/settings/system/system-settings.png'>)>, 
'x-canonical-message-id': <'7f97870a-2d8658-2d4da9-2d819f-2d3f503499bc4f'>, 
'label': <'Il existe une image du système à jour.'>, 'icon': <('file', 
<'file:///usr/share/ubuntu/settings/system/icons/settings-system-update.svg'>)>,
 'x-canonical-text': <'Appuyez pour ouvrir le gestionnaire de mise à jour du 
système.'>, 'x-canonical-subtitle': <''>, 'action': 
<'ubuntu-system-settings.msg.7f97870a-2d8658-2d4da9-2d819f-2d3f503499bc4f'>},
{'x-canonical-message-actions': <<@aa{sv} []>>, 'target': , 
'x-canonical-time': , 'x-canonical-type': 
<'com.canonical.indicator.messages.messageitem'>, 'x-canonical-app-icon': 
<('file', <'file:///usr/share/ubuntu/settings/system/system-settings.png'>)>, 
'x-canonical-message-id': <'7f97870a-2d8658-2d4da9-2d819f-2d3f503499bc4f'>, 
'label': <'Il existe une image du système à jour.'>, 'icon': <('file', 
<'file:///usr/share/ubuntu/settings/system/icons/settings-system-update.svg'>)>,
 'x-canonical-text': <'Appuyez pour ouvrir le gestionnaire de mise à jour du 
système.'>, 'x-canonical-subtitle': <''>, 'action': 
<'ubuntu-system-settings.msg.7f97870a-2d8658-2d4da9-2d819f-2d3f503499bc4f'>}
]
),
(1, 3, [{'action': <'remove-all'>, 'label': <'Tout effacer'>, 
'x-canonical-type': <'com.canonical.indicator.button'>}])
],)

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

Title:
  notification (image update, gmail, calls) displayed twice

Status in Canonical System Image:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes notifications are displayed twice in the indicator. It
  happens randomly with all kind of notifications (image update, gmail,
  calls) Push client logs shows a single notification. There is nothing
  specific to reproduce, sometimes it happens, sometimes it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+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 1377286] Re: Update Indicator Title Strings

[Jean-Baptiste Lallement]

Fixed on stable builds.

** Changed in: canonical-devices-system-image
   Status: New => 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, dx-packages
https://bugs.launchpad.net/bugs/1377286

Title:
  Update Indicator Title Strings

Status in Canonical System Image:
  Fix Released
Status in Bluetooth Menu:
  Invalid
Status in Indicator Date and Time:
  Fix Released
Status in Indicator Display:
  Fix Released
Status in Indicator Location:
  Invalid
Status in Messaging Menu:
  Fix Released
Status in Network Menu:
  Invalid
Status in indicator-power:
  Invalid
Status in The Sound Menu:
  Invalid
Status in Transfer Indicator:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-display package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  New

Bug description:
  Design change

  The space available for the title has changed, so the strings need to
  as well:

  Transfer: "Files"
  Location: "Location"
  Bluetooth: "Bluetooth"
  Network: "Network"
  Messaging: "Notifications" (also in System Settings > "Notifications")
  Power: "Battery"
  Datetime: "Time & Date"
  Sound: "Sound"
  Display: "Rotation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377286/+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 1473029] Re: notification (image update, gmail, dialer) displayed twice

[Jean-Baptiste Lallement]

** Summary changed:

- Image update notification displayed twice
+ notification (image update, gmail, dialer) displayed twice

** Description changed:

  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34
  
- Sometimes image updates notification are displayed twice in the
- indicator. Push client logs shows a single notification. There is
- nothing specific to reproduce, sometimes it happens, sometimes it
- doesn't.
+ Sometimes notifications are displayed twice in the indicator. It happens
+ randomly with all kind of notifications (image update, gmail, dialer)
+ Push client logs shows a single notification. There is nothing specific
+ to reproduce, sometimes it happens, sometimes it doesn't.

** Summary changed:

- notification (image update, gmail, dialer) displayed twice
+ notification (image update, gmail, calls) displayed twice

** Description changed:

  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34
  
  Sometimes notifications are displayed twice in the indicator. It happens
- randomly with all kind of notifications (image update, gmail, dialer)
+ randomly with all kind of notifications (image update, gmail, calls)
  Push client logs shows a single notification. There is nothing specific
  to reproduce, sometimes it happens, sometimes it doesn't.

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

Title:
  notification (image update, gmail, calls) displayed twice

Status in Canonical System Image:
  New
Status in indicator-messages package in Ubuntu:
  New

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes notifications are displayed twice in the indicator. It
  happens randomly with all kind of notifications (image update, gmail,
  calls) Push client logs shows a single notification. There is nothing
  specific to reproduce, sometimes it happens, sometimes it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+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 1473029] Re: Image update notification displayed twice

[Jean-Baptiste Lallement]

push client logs

** Attachment added: "ubuntu-push-client.log"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1473029/+attachment/4426948/+files/ubuntu-push-client.log

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Image update notification displayed twice

Status in the base for Ubuntu mobile products:
  New
Status in indicator-messages package in Ubuntu:
  New

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes image updates notification are displayed twice in the
  indicator. Push client logs shows a single notification. There is
  nothing specific to reproduce, sometimes it happens, sometimes it
  doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+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 1473029] [NEW] Image update notification displayed twice

[Jean-Baptiste Lallement]

Public bug reported:

current build number: 54
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-09 08:43:49
version version: 54
version ubuntu: 20150708.1
version device: 20150706-a9e00a0
version custom: 20150707-800-5-34

Sometimes image updates notification are displayed twice in the
indicator. Push client logs shows a single notification. There is
nothing specific to reproduce, sometimes it happens, sometimes it
doesn't.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20150709_131843194.png"
   
https://bugs.launchpad.net/bugs/1473029/+attachment/4426947/+files/screenshot20150709_131843194.png

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

Title:
  Image update notification displayed twice

Status in the base for Ubuntu mobile products:
  New
Status in indicator-messages package in Ubuntu:
  New

Bug description:
  current build number: 54
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-09 08:43:49
  version version: 54
  version ubuntu: 20150708.1
  version device: 20150706-a9e00a0
  version custom: 20150707-800-5-34

  Sometimes image updates notification are displayed twice in the
  indicator. Push client logs shows a single notification. There is
  nothing specific to reproduce, sometimes it happens, sometimes it
  doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473029/+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 1435871] Re: Only clock shows after reboot

[Jean-Baptiste Lallement]

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

** Package changed: unity (Ubuntu) => unity8 (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/1435871

Title:
  Only clock shows after reboot

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when I reboot my device, I see a darkened screen with only
  the clock visible, and no interaction seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity (not installed)
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: armhf
  Date: Tue Mar 24 13:57:01 2015
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1435871/+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 1424966] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_

[Jean-Baptiste Lallement]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-
  
service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in the base for Ubuntu mobile products:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  It happened randomly but several time on RTM/krillin. According to
  errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid
  and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM.

[ Charles Kerr ]
* change the WallClock to detect time changes from
  TFD_TIMER_CANCEL_ON_SET, e.g. when ntp<-->manual is toggled

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-datetime.  This problem was most recently seen with version 
13.10.0+15.04.20150213.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 
contains more details.

  current build number: 242
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-23 08:07:23
  version version: 242
  version ubuntu: 20150223
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

  Trace:
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1424966/+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 1424966] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_

[Jean-Baptiste Lallement]

** Description changed:

+ It happened randomly but several time on RTM/krillin
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-datetime.  This problem was most recently seen with
  version 13.10.0+15.04.20150213.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000
  contains more details.
+ 
+ 
+ current build number: 242
+ device name: krillin
+ channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
+ last update: 2015-02-23 08:07:23
+ version version: 242
+ version ubuntu: 20150223
+ version device: 20150216-fe747ac
+ version custom: 20150216-561-29-186

** Description changed:

- It happened randomly but several time on RTM/krillin
+ It happened randomly but several time on RTM/krillin. According to
+ errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid
+ and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM.
  
- The Ubuntu Error Tracker has been receiving reports about a problem
- regarding indicator-datetime.  This problem was most recently seen with
- version 13.10.0+15.04.20150213.1-0ubuntu1, the problem page at
- https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000
- contains more details.
  
+ The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-datetime.  This problem was most recently seen with version 
13.10.0+15.04.20150213.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 
contains more details.
  
  current build number: 242
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-23 08:07:23
  version version: 242
  version ubuntu: 20150223
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186
+ 
+ Trace:
+ 
https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate

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

** Description changed:

  It happened randomly but several time on RTM/krillin. According to
  errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid
  and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM.
+ 
+   [ Charles Kerr ]
+   * change the WallClock to detect time changes from
+ TFD_TIMER_CANCEL_ON_SET, e.g. when ntp<-->manual is toggled
  
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-datetime.  This problem was most recently seen with version 
13.10.0+15.04.20150213.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 
contains more details.
  
  current build number: 242
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-23 08:07:23
  version version: 242
  version ubuntu: 20150223
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186
  
  Trace:
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-
  
service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  It happened randomly but several time on RTM/krillin. According to
  errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid
  and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM.

[ Charles Kerr ]
* change the WallClock to detect time changes from
  TFD_TIMER_CANCEL_ON_SET, e.g. when ntp<-->manual is toggled

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-datetime.  This problem was most recently seen with version 
13.10.0+15.04.20150213.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 
contains more details.

  current build number: 242
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-23 08:07:23
  version version: 242
  version ubuntu: 20150223
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

  Trace:
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aind

[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Jean-Baptiste Lallement]

I downgraded to  indicator-datetime 13.10.0+14.10.20141009-0ubuntu1 and
cannot reproduce the problem

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Jean-Baptiste Lallement]

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

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

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

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171/+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 1395709] Re: Silence mode goes unchecked after 1 second

[Jean-Baptiste Lallement]

** Tags added: beta

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

Title:
  Silence mode goes unchecked after 1 second

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

Bug description:
  Using the phone in version 9, rtm English channel, but configured in
  Spanish.

  Steps to reproduce:

  1) Go to system-settings/sound and enable silent mode
  2) Reboot the phone
  3) Unlock the SIM
  4) Open the Sound Indicator and leave it open
  5) Toggle Silence mode
  6) Leave the indicator open and wait.

  Expected results
  * Silent mode is already checked on boot (bug 1391164)
  * Silence mode stays checked

  Actual results
  * Silence mode goes back unchecked after 0.5 seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395709/+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 1395709] Re: Silence mode goes unchecked after 1 second

[Jean-Baptiste Lallement]

** Description changed:

  Using the phone in version 9, rtm English channel, but configured in
  Spanish.
  
  Steps to reproduce:
  
- 1) Turn off the phone with your sound on
- 2) Start the phone
+ 1) Go to system-settings/sound and enable silent mode
+ 2) Reboot the phone
  3) Unlock the SIM
  4) Open the Sound Indicator and leave it open
- 5) Check Silence mode
+ 5) Toggle Silence mode
+ 6) Leave the indicator open and wait.
  
  Expected results
+ * Silent mode is already checked on boot (bug 1391164)
  * Silence mode stays checked
  
  Actual results
  * Silence mode goes back unchecked after 0.5 seconds.

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

Title:
  Silence mode goes unchecked after 1 second

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

Bug description:
  Using the phone in version 9, rtm English channel, but configured in
  Spanish.

  Steps to reproduce:

  1) Go to system-settings/sound and enable silent mode
  2) Reboot the phone
  3) Unlock the SIM
  4) Open the Sound Indicator and leave it open
  5) Toggle Silence mode
  6) Leave the indicator open and wait.

  Expected results
  * Silent mode is already checked on boot (bug 1391164)
  * Silence mode stays checked

  Actual results
  * Silence mode goes back unchecked after 0.5 seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395709/+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 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted

[Jean-Baptiste Lallement]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => 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/1387231

Title:
  [regression][clock] alarm still rings once it's been disabled or
  deleted

Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  (r135)

  Steps to reproduce:

  1. Create a single type alarm to ring in the next 5 minutes.
  2. Wait for the alarm to ring.
  3. After dismissing the alarm, delete it from the clock app.

  Actual behaviour:

  Once the alarm's been deleted, it still rings!

  Expected behaviour:

  Once you delete the alarm, this shouldn't ring anymore.

  

  Mako, Image #5 ubuntu rtm,

  Steps to reproduce:

  1. Create an alarm to ring in the next 5 minutes.
  2. Disable the alarm after it is created.

  Actual Behaviour:

  Alarm still rings!

  Expected Behaviour:

  Once you disable an alarm, it shouldn't ring anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+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 1391909] Re: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked

[Jean-Baptiste Lallement]

Reproduced with the steps in the description.

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

Title:
  Caller number not loaded in dialler when Call Back or phone icon is
  clicked in missed call notification and the device is locked

Status in “dialer-app” package in Ubuntu:
  New
Status in “indicator-messages” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Place a call to the device and hang up on the other end (to generate a 
missed call notification)
  2. Ensure the greeter is locked
  3. Swipe down on the notifications indicator (message icon)
  4. Tap on the missed call
  5. Tap on Call Back
  6. Unlock the screen

  Expected result:

  Dialler application opens with the number loaded ready to call

  Actual result:

  Dialler application opens but the number is not loaded

  N.B. At step 4 we can tap on the phone icon in the missed call
  notification to get the same effect, it appears to be functionally
  equivalent to the Call Back button

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov 12 14:50:42 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-030205)
  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/dialer-app/+bug/1391909/+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 1389761] [NEW] Don't show the volume overlay when changing the volume with the slider

[Jean-Baptiste Lallement]

Public bug reported:

The overlay and the slider are redundant when the user changes the
volume with the slider and the overlay shouldn't be displayed.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Wed Nov  5 16:58:35 2014
InstallationDate: Installed on 2014-11-05 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf beta 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/1389761

Title:
  Don't show the volume overlay when changing the volume with the slider

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

Bug description:
  The overlay and the slider are redundant when the user changes the
  volume with the slider and the overlay shouldn't be displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov  5 16:58:35 2014
  InstallationDate: Installed on 2014-11-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389761/+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

[Jean-Baptiste Lallement]

** Tags added: beta

-- 
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:
  Confirmed

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 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled

[Jean-Baptiste Lallement]

** Tags added: beta qa-daily-testing rtm14

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

Title:
  Bluetooth is always enabled after reboot even if it was disabled

Status in Bluetooth Menu:
  Invalid
Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “rfkill” package in Ubuntu:
  Triaged
Status in “urfkill” package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1342151] Re: [Indicators] Silent mode control in the indicator

[Jean-Baptiste Lallement]

** Tags added: beta qa-daily-testing

-- 
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:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Incomplete

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 1285951] Re: bluetooth indicator disappears after turning off bluetooth

[Jean-Baptiste Lallement]

** Tags added: qa-daily-testing rtm14 unity8

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

Title:
  bluetooth indicator disappears after turning off bluetooth

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

Bug description:
  Although bug 1126108 is marked as "Fix released", my indicator-
  bluetooth icon disappears after I use it to turn bluetooth off. See
  the attached animated gif.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-bluetooth 0.0.6+13.10.20131016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Feb 27 22:37:17 2014
  InstallationDate: Installed on 2013-01-12 (411 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1285951/+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

[Jean-Baptiste Lallement]

** Tags added: qa-daily-testing rtm14

-- 
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:
  New

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 1367270] Re: Message is lost when user replies to an SMS from the indicator without a default SIM

[Jean-Baptiste Lallement]

** Summary changed:

- Message is lost when user replies to an SMS from the indicator without a 
deault SIM
+ Message is lost when user replies to an SMS from the indicator without a 
default SIM

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

Title:
  Message is lost when user replies to an SMS from the indicator without
  a default SIM

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

Bug description:
  
  TEST CASE:
  Pre-requisite: Dual SIM device without a default SIM selected
  1. Send an SMS to the device under test
  2. On notification, open the message indication
  3. Tap the incoming message to show the input field
  4. Type an answer and send.

  ACTUAL RESULT:
  The message is not sent and is lost.

  EXPECTED RESULT
  Either the system asks which SIM to use or replying from the indicator is 
locked without a default SIM.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu 
RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Tue Sep  9 14:37:03 2014
  InstallationDate: Installed on 2014-09-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140909-030205)
  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/1367270/+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 1367270] [NEW] Message is lost when user replies to an SMS from the indicator without a deault SIM

[Jean-Baptiste Lallement]

Public bug reported:


TEST CASE:
Pre-requisite: Dual SIM device without a default SIM selected
1. Send an SMS to the device under test
2. On notification, open the message indication
3. Tap the incoming message to show the input field
4. Type an answer and send.

ACTUAL RESULT:
The message is not sent and is lost.

EXPECTED RESULT
Either the system asks which SIM to use or replying from the indicator is 
locked without a default SIM.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu 
RTM]
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Tue Sep  9 14:37:03 2014
InstallationDate: Installed on 2014-09-09 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140909-030205)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf qa-daily-testing rtm14 third-party-packages utopic

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

Title:
  Message is lost when user replies to an SMS from the indicator without
  a deault SIM

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

Bug description:
  
  TEST CASE:
  Pre-requisite: Dual SIM device without a default SIM selected
  1. Send an SMS to the device under test
  2. On notification, open the message indication
  3. Tap the incoming message to show the input field
  4. Type an answer and send.

  ACTUAL RESULT:
  The message is not sent and is lost.

  EXPECTED RESULT
  Either the system asks which SIM to use or replying from the indicator is 
locked without a default SIM.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu 
RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Tue Sep  9 14:37:03 2014
  InstallationDate: Installed on 2014-09-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140909-030205)
  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/1367270/+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 1366695] [NEW] New voicemail messages notification without new message on voicemail

[Jean-Baptiste Lallement]

Public bug reported:

The message indicator reports that there are new messages on voicemail
each time I unlock my SIM card, even if there is no new message on the
voicemail or the voicemail is empty (nothing archived even)

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu 
RTM]
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Mon Sep  8 09:37:44 2014
InstallationDate: Installed on 2014-09-08 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140908-030254)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf third-party-packages utopic

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

Title:
  New voicemail messages notification without new message on voicemail

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

Bug description:
  The message indicator reports that there are new messages on voicemail
  each time I unlock my SIM card, even if there is no new message on the
  voicemail or the voicemail is empty (nothing archived even)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu 
RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep  8 09:37:44 2014
  InstallationDate: Installed on 2014-09-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140908-030254)
  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/1366695/+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 1365410] Re: No French translations in fr.po

[Jean-Baptiste Lallement]

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

Yes it is the same indicator-bluetooth.mo is not in the language pack. I
verified and it is in latest upload (1:14.10+20140903) It should be
fixed on next image build with this version.

** This bug has been marked a duplicate of bug 1365401
   indicator-sound.mo not in language-pack-touch-XX

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

Title:
  No French translations in fr.po

Status in “indicator-bluetooth” package in Ubuntu:
  Incomplete

Bug description:
  The French strings in fr.po are empty although the project is
  translated in launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:38:12 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1365410/+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 1365530] [NEW] Time in indicator out of sync on resume from suspend

[Jean-Baptiste Lallement]

Public bug reported:

mako: 221
krillin: 16
last known good build: ?
Similar defect: bug 1328646

When the device is resumed by pressing the power button and the device
is not connected over USB to any power source the clock on the greeter
and the date/time indicator is out of sync.

TEST CASE
1. Unplug the device from its USB cable
2. Press the power button to switch to suspend mode
3. Wait a moment (several minutes)
4. Press the power button again to resume the device
5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.

EXPECTED RESULT
Clocks are in sync

ACTUAL RESULT
Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 13:57:35 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: apport-bug armhf qa-daily-testing rtm14 utopic

** Attachment added: "clock_out_of_sync.jpg"
   
https://bugs.launchpad.net/bugs/1365530/+attachment/4195423/+files/clock_out_of_sync.jpg

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
- is not connected over USB the clock on the greeter and the date/time
- indicator is out of sync
+ is not connected over USB to any power source the clock on the greeter
+ and the date/time indicator is out of sync
  
  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.
  
  EXPECTED RESULT
  Clocks are in sync
  
  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power source the clock on the greeter
- and the date/time indicator is out of sync
+ and the date/time indicator is out of sync.
  
  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait a moment (several minutes)
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on another 
system or with the clock app.
  
  EXPECTED RESULT
  Clocks are in sync
  
  ACTUAL RESULT
  Time on the device is behind by several minutes. The time on the clock app is 
always correct. The screenshot attached shows that time in the indicator is 
13:48 and 13:49 in the clock app (correct time) after waiting less than 10 
minutes. The time difference can be several minutes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 13:57:35 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  mako: 221
  krillin: 16
  last known good build: ?
  Similar defect: bug 1328646
  
  When the device is resumed by pressing the power button and the device
  is not connected over USB to any power source the clo

[Dx-packages] [Bug 1365401] Re: indicator-sound.mo not in language-pack-touch-XX

[Jean-Baptiste Lallement]

Sorry, I've been confused by a link from a spreadsheet to the upstream
project instead of the ubuntu project. The translations are corrects.
The problem is that indicator-sound.mo is not installed on the device.
It should probably be installed by language-pack-touch-XX

** Summary changed:

- No POT file in source tree
+ indicator-sound.mo not in language-pack-touch-XX

** Changed in: indicator-sound (Ubuntu)
   Status: Incomplete => Confirmed

** Description changed:

- There is no POT file for this application in the source tree and it is
- not translatable.
+ indicator-sound.mo is not present in language-pack-touch-fr and the
+ indicator is not translated.
  
  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: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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

Title:
  indicator-sound.mo not in language-pack-touch-XX

Status in “language-pack-touch-fr” package in Ubuntu:
  In Progress

Bug description:
  indicator-sound.mo is not present in language-pack-touch-fr and the
  indicator is not translated.

  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: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-touch-fr/+bug/1365401/+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 1350544] Re: Some translations are not loaded

[Jean-Baptiste Lallement]

** Tags added: rtm-i18n

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

Title:
  Some translations are not loaded

Status in Ubuntu Translations:
  Incomplete
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  The translations for some messages don't seem to be loaded. E.g.
  "Tomorrow" always appears in English in the list of upcoming events
  when sliding down the indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1350544/+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 1365410] [NEW] No French translations in fr.po

[Jean-Baptiste Lallement]

Public bug reported:

The French strings in fr.po are empty although the project is translated
in launchpad.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 09:38:12 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf rtm-i18n utopic

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

Title:
  No French translations in fr.po

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

Bug description:
  The French strings in fr.po are empty although the project is
  translated in launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:38:12 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1365410/+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 1350544] Re: Some translations are not loaded

[Jean-Baptiste Lallement]

What is the status of this bug, 'Tomorrow' is still untranslated on
krillin #15 and apparently the string is not extracted from the source
code.

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

Title:
  Some translations are not loaded

Status in Ubuntu Translations:
  Incomplete
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  The translations for some messages don't seem to be loaded. E.g.
  "Tomorrow" always appears in English in the list of upcoming events
  when sliding down the indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1350544/+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 1365401] [NEW] No POT file in source tree

[Jean-Baptiste Lallement]

Public bug reported:

There is no POT file for this application in the source tree and it is
not translatable.

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: ({'desktop-settings': (true, signature '', @av []), 'mic-volume': 
(true, '', [<1.0>]), 'mute': (true, '', []), 'phone-settings': (true, 
'', []), 'volume': (true, 'i', [<0.9399871826171875>]), 'root': (true, '', 
[<{'title': <'Sound'>, 'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
ApportVersion: 2.14.7-0ubuntu1
Architecture: armhf
Date: Thu Sep  4 09:21:17 2014
InstallationDate: Installed on 2014-09-04 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

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


** Tags: apport-bug armhf rtm-i18n 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/1365401

Title:
  No POT file in source tree

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

Bug description:
  There is no POT file for this application in the source tree and it is
  not translatable.

  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: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [<1.0>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'volume': (true, 'i', 
[<0.9399871826171875>]), 'root': (true, '', [<{'title': <'Sound'>, 
'accessible-desc': <'Volume (93%)'>, 'icon': <('themed', 
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>, 
'visible': }>]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Thu Sep  4 09:21:17 2014
  InstallationDate: Installed on 2014-09-04 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140904-020205)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: ** (process:9134): CRITICAL **: 
volume_control_set_volume_internal: assertion '_tmp1_ == PA_CONTEXT_READY' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1365401/+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 1359125] [NEW] Use a discreet notification when there is an active call

[Jean-Baptiste Lallement]

Public bug reported:

build #199

When there is an incoming call during an active call, the notification
uses the configured ringtone. It's very loud to the point you cannot
talk anymore until the notification is dismissed.

This is very intrusive and the notification should be more discreet like
a small beep and a vibration. This behaviour should be the same for all
the notifications (alarms, messages) when a call is active.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.6-0ubuntu1
Architecture: armhf
Date: Wed Aug 20 09:27:50 2014
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140819-020204)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf rtm14 utopic

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

Title:
  Use a discreet notification when there is an active call

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

Bug description:
  build #199

  When there is an incoming call during an active call, the notification
  uses the configured ringtone. It's very loud to the point you cannot
  talk anymore until the notification is dismissed.

  This is very intrusive and the notification should be more discreet
  like a small beep and a vibration. This behaviour should be the same
  for all the notifications (alarms, messages) when a call is active.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: armhf
  Date: Wed Aug 20 09:27:50 2014
  InstallationDate: Installed on 2014-08-19 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140819-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/1359125/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%

[Jean-Baptiste Lallement]

** Tags removed: rtm
** Tags added: rtm14

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

Title:
  ubuntu-touch-session needs to be able to start even if the homedir is
  filled to 100%

Status in Ubuntu CI Services:
  New
Status in “android” package in Ubuntu:
  Invalid
Status in “dbus” package in Ubuntu:
  Confirmed
Status in “hud” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-session” package in Ubuntu:
  Confirmed

Bug description:
  When the ~/phablet tree has media files added to it by the user, it is
  possible for the storage space to be filled, and consequently for the
  device not to boot.

  From the OEM project bug:

  "After further investigation this problem was caused by the following:

   1) Files were pushed to ~phablet/
   2) The files filled the home partition completely
   3) Upon a restart of the phone the upstart session job 
/usr/share/upstart/sessions/dbus.conf is attempted
   4) Because the partition is full, the final line of the pre-start stanza 
fails as $HOME/.cache/upstart/dbus-session cannot be created
   5) As there is no running dbus session instance unity8 fails to start

  Clearing space on the home partition allows unity8 to start again."

  Posted here, since following discussion in #ubuntu-touch it has the
  same underlying cause as bug #1270248, also reported on this package.

  Raised as a separate bug, because this was caused by user action,
  rather than simply the system failing to do log housekeeping.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

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

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1350666] Re: Time is not updated on the welcome screen until the next minute

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1328646
   Clock out of sync on resume from suspend

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

Title:
  Time is not updated on the welcome screen until the next minute

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

Bug description:
  I originally noticed this bug in flight mode, but I've seen it
  happening without flight mode too. It seems the time on the welcome
  screen is not updated instantly when the screen is on, but only the
  next time a minute passes. I'm using image 172.

  Original description
  I've noticed that time is updated neither on the welcome screen nor in the 
indicator if Flight Mode is on and time and date is set up to update 
automatically.

  In this case, the time at the bottom of the Time and Date page in
  u-s-s is still updated normally, but the indicator and the welcome
  screen's time is frozen to the value when the Flight Mode was enabled.

  A workaround for the time to update is to set the update mode to
  Manually, but in any case, as a user, when I set Flight Mode on at the
  flick of the switch, I wasn't expecting to have to open u-s-s for time
  to be kept.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1350666/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

9:14 on the watch, 9:14 on the clock of the phone and 9:10 in the
indicator (and the greeter before I unlocked it)

** Attachment added: "image20140807_0002.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171734/+files/image20140807_0002.jpg

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

On this photo mako shows 9:10 but it's 9:13 (both devices were in sync
at the beginning of the test)

** Attachment added: "image20140807_0001.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171732/+files/image20140807_0001.jpg

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

The difference can be several hours. This morning, at 07:38 the time on
the phone was 04:09

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

** Attachment removed: "2316_2318.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171442/+files/2316_2318.jpg

** Attachment removed: "2216_2317.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171441/+files/2216_2317.jpg

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

And on this photo, 1 minute later...

The time on the watch is 23:18 and on the phone it's 23:18 on the clock
and 23:16 in the indicator (and the greeter before I unlocked it)

The time on these 2 devices was in sync at the beginning of the test.

** Attachment added: "2316_2318.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171442/+files/2316_2318.jpg

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

The proof! :)

The watch (time is set by GPS) indicates 23:17 and the phone indicates
23:16 in the indicator and the greeter

** Attachment added: "2216_2317.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171441/+files/2216_2317.jpg

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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 1328646] Re: Clock out of sync on resume from suspend

[Jean-Baptiste Lallement]

It happens to me all the time, your device have to be unplugged from
usb. Sometimes the time different is not a couple of minutes but like
half an hour.

** Changed in: unity8
   Status: Incomplete => Confirmed

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  New
Status in The Unity 8 shell:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+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] [NEW] VoiceMail notification pretends there are 255 messages. It is not true there are only 2

[Jean-Baptiste Lallement]

Public bug reported:

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)

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


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

** Attachment added: "255-new-message.png"
   
https://bugs.launchpad.net/bugs/1353379/+attachment/4170977/+files/255-new-message.png

** Tags added: qa-touch

-- 
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:
  New

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 1351308] Re: Changing language has no effect

[Jean-Baptiste Lallement]

** Description changed:

- broken on mako #165
+ broken on mako #164
  Last known good image: #163
  
  TEST CASE:
  1. On a device in English, go to "System Settings/Language & Text/Display 
Language"
  2. Scroll down the list and select another language i.e "Français (France)"
  3. Tap "Confirm"
  
  ACTUAL RESULT
  Language did not change (the label in front of "Display language" is still 
English) and is still English (even after a reboot)
  
  EXPECTED LANGUAGE
  Setting is set to French and UI is localized after a reboot.
  
  Same problem with the wizard. The language changes *inside* the wizard
  but changes are not written to ~/.pam_environment
  
+ 
+ Downgrading accountsservice to 0.6.37-1ubuntu6 on #167 fixes the issue
+ Upgrading accountsservice to 0.6.37-1ubuntu7 on #164 reproduces the issue
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: armhf
  Date: Fri Aug  1 15:05:35 2014
  InstallationDate: Installed on 2014-08-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140801-020205)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Changing language has no effect

Status in “accountsservice” package in Ubuntu:
  Confirmed

Bug description:
  broken on mako #164
  Last known good image: #163

  TEST CASE:
  1. On a device in English, go to "System Settings/Language & Text/Display 
Language"
  2. Scroll down the list and select another language i.e "Français (France)"
  3. Tap "Confirm"

  ACTUAL RESULT
  Language did not change (the label in front of "Display language" is still 
English) and is still English (even after a reboot)

  EXPECTED LANGUAGE
  Setting is set to French and UI is localized after a reboot.

  Same problem with the wizard. The language changes *inside* the wizard
  but changes are not written to ~/.pam_environment

  
  Downgrading accountsservice to 0.6.37-1ubuntu6 on #167 fixes the issue
  Upgrading accountsservice to 0.6.37-1ubuntu7 on #164 reproduces the issue

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: armhf
  Date: Fri Aug  1 15:05:35 2014
  InstallationDate: Installed on 2014-08-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140801-020205)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1351308/+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