[Touch-packages] [Bug 1608953] Re: Issue with systemd issue when run inside a container

2016-08-17 Thread Martin Pitt
FTR, there is a similar bug 1611973 about postgresql not starting in a
cloud instance, but this is specific to cloud-init, not to LXC. How sure
are you that this is really due to the low FDs of pid 1, as opposed to
that bug? Do you have  some useful logs to look at, like a journal
output from that container? (although generators don't log into journal,
they run earlier than journald starts -- on a "real" system their error
messages land in dmesg, not sure if containers are allowed to do that).

** Summary changed:

- Issue with systemd issue when run inside a container
+ PostgreSQL does not start in container

** Changed in: systemd (Ubuntu)
   Status: Fix Released => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1608953

Title:
  PostgreSQL does not start in container

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  

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

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


[Touch-packages] [Bug 1608953] Re: Issue with systemd issue when run inside a container

2016-08-17 Thread Martin Pitt
I tried again with "classic" LXC (not lxd), and there the FDs look
differently: In xenial they point to /dev/pts/4, in yakkety they point
to /dev/pts/1. But installing postgresql in both xenial and yakkety
works fine.

I also tried with lxc-start-ephemeral, but in that case the low FDs are
again pointing to /dev/null and things work fine (but I suppose you
don't use emphemeral containers).

So, I'm happy to backport the patch, but I'm unable to create an SRU
test case or verify the fix myself.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1608953

Title:
  PostgreSQL does not start in container

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  

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

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


[Touch-packages] [Bug 1614369] [NEW] 18.082016

2016-08-17 Thread Mita
Public bug reported:

sice 18.08.2016.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Aug 18 07:27:55 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller 
[1043:16cd]
   Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:16cd]
InstallationDate: Installed on 2016-06-03 (75 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X555LN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=7d0453c9-ea92-4810-b9f0-751c43c5d78f ro plymouth:debug drm.debug=0xe 
vesafb.invalid=1 nopat
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LN.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LN.309:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X555LN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Aug 18 07:23:25 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614369

Title:
  18.082016

Status in xorg package in Ubuntu:
  New

Bug description:
  sice 18.08.2016.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 18 07:27:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:16cd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] 

[Touch-packages] [Bug 1608953] Re: Issue with systemd issue when run inside a container

2016-08-17 Thread Martin Pitt
Thanks for the initial analysis! This is very helpful. I'm marking this
as fixed in yakkety and add a xenial task.

I tried to reproduce this. I created a standard xenial and yakkety
container:

  lxc launch images:ubuntu/xenial/amd64 x1
  lxc launch images:ubuntu/yakkety/amd64 y1

In both of them pid1's low fds look okay:

$ lxc exec x1 -- ls -l /proc/1/fd/{0,1,2}
lrwx-- 1 root root 64 Aug 18 05:10 /proc/1/fd/0 -> /dev/null
lrwx-- 1 root root 64 Aug 18 05:10 /proc/1/fd/1 -> /dev/null
lrwx-- 1 root root 64 Aug 18 05:10 /proc/1/fd/2 -> /dev/null

(same for y1)

PostgreSQL starts fine after installation:

$ lxc exec x1 -- apt install -y postgresql
$ lxc exec x1 -- pg_lsclusters
Ver Cluster Port Status OwnerData directory   Log file
9.5 main5432 online postgres /var/lib/postgresql/9.5/main 
/var/log/postgresql/postgresql-9.5-main.log

(again, same for y1)

The generator ran:

$ lxc exec x1 -- ls -lR /run/systemd/generator/postgresql.service.wants
/run/systemd/generator/postgresql.service.wants:
total 0
lrwxrwxrwx 1 root root 39 Aug 18 05:13 postgresql@9.5-main.service -> 
/lib/systemd/system/postgresql@.service

So I'm afraid I cannot reproduce this for testing the fix. This is a
requirement for SRUs. Can you please describe how this can be
reproduced?

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1608953

Title:
  Issue with systemd issue when run inside a container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  

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

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


[Touch-packages] [Bug 1614365] Re: lightdm multi monitor layout does not respect user setting

2016-08-17 Thread Christian González
Additionally: I think that the display setting (resolution etc) is more
or less no "user specific" setting, as mostly monitors are placed
physically and left there - most users on a multi-user desktop system
won't regularly move the monitors around and use custom user specific
settings then.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1614365

Title:
  lightdm multi monitor layout does not respect user setting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Using Ubuntu 16.04.1, and lightdm 1.18.2-0ubuntu2 during login, lightdm does 
not respect my multi monitor settings. In my user session, my external monitor 
is on the left, the laptop monitor right.
  On the login screen, it's the other way round, external right, laptop left, 
which does not respect my physical setting.

  This leads to wrapping the mouse around the edges awkwardly, and seems
  to produce bugs like flickering and displaying crap of a buffer (see
  Bug 850885) during transition to the user session.

  I know that lightdm does not respect the ~/.config/monitors.xml file,
  and that file could be copied to /etc - but this seems weird to me.

  I propose to add a setting in unity-control-center -> Displays (needs
  to be unlocked like in user settings) th "use that configuration on
  login screen".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 18 06:52:29 2016
  InstallationDate: Installed on 2016-07-24 (24 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1614365] [NEW] lightdm multi monitor layout does not respect user setting

2016-08-17 Thread Christian González
Public bug reported:

Using Ubuntu 16.04.1, and lightdm 1.18.2-0ubuntu2 during login, lightdm does 
not respect my multi monitor settings. In my user session, my external monitor 
is on the left, the laptop monitor right.
On the login screen, it's the other way round, external right, laptop left, 
which does not respect my physical setting.

This leads to wrapping the mouse around the edges awkwardly, and seems
to produce bugs like flickering and displaying crap of a buffer (see Bug
850885) during transition to the user session.

I know that lightdm does not respect the ~/.config/monitors.xml file,
and that file could be copied to /etc - but this seems weird to me.

I propose to add a setting in unity-control-center -> Displays (needs to
be unlocked like in user settings) th "use that configuration on login
screen".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Aug 18 06:52:29 2016
InstallationDate: Installed on 2016-07-24 (24 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Summary changed:

- lightdm multi monitor on wrong side
+ lightdm multi monitor layout does not respect user setting

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1614365

Title:
  lightdm multi monitor layout does not respect user setting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Using Ubuntu 16.04.1, and lightdm 1.18.2-0ubuntu2 during login, lightdm does 
not respect my multi monitor settings. In my user session, my external monitor 
is on the left, the laptop monitor right.
  On the login screen, it's the other way round, external right, laptop left, 
which does not respect my physical setting.

  This leads to wrapping the mouse around the edges awkwardly, and seems
  to produce bugs like flickering and displaying crap of a buffer (see
  Bug 850885) during transition to the user session.

  I know that lightdm does not respect the ~/.config/monitors.xml file,
  and that file could be copied to /etc - but this seems weird to me.

  I propose to add a setting in unity-control-center -> Displays (needs
  to be unlocked like in user settings) th "use that configuration on
  login screen".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 18 06:52:29 2016
  InstallationDate: Installed on 2016-07-24 (24 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1533267] Re: gcr-prompter is logging too much

2016-08-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/1533267

Title:
  gcr-prompter is logging too much

Status in gcr package in Ubuntu:
  Confirmed

Bug description:
  When prompted to unlock a SSH private key, gcr-prompter logs no less
  than 29 messages in auth.log:

Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: received 
BeginPrompting call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: preparing a prompt 
for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: creating new 
GcrPromptDialog prompt
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: automatically 
selecting secret exchange protocol
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: generating public key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: beginning the secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: receiving secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving shared 
transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: starting password 
prompt for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gtk: GtkDialog mapped 
without a transient parent. This is discouraged.
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: completed password 
prompt for callback :1.2@/org/gnome/keyring/Prompt/p4
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: encrypting data
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: sending the secret 
exchange: [sx-aes-1]\npublic=pub-base64\nsecret=secret-base64==\n
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: closing the prompt
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptDone method on /org/gnome/keyring/Prompt/p4@:1.2, and ignoring reply

  
  This looks like debug logging to me. Also, it's probably best to avoid 
logging the secret exchange (obfuscated above).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gcr 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 12 10:54:14 2016
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1572587] Re: mouse cursor trails on second monitor

2016-08-17 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1572587

Title:
  mouse cursor trails on second monitor

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Using a second monitor with my lenovo laptop. 
  The mouse cursor forms a trail only on the second monitor and slowly 
disappears after a few seconds or a right mouse click .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 20 09:46:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:191d] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:222e]
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:222e]
  InstallationDate: Installed on 2016-03-30 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: LENOVO 20ENCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=5dac-b187-4366-8994-da3fb720de50 ro vga=791
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET41W(1.15):bd12/31/2015:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 18 14:45:37 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   39984 
   vendor VSC
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Touch-packages] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

2016-08-17 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1585094

Title:
  Random stuck keys on Lenovo Yoga 13

Status in xorg package in Ubuntu:
  Expired

Bug description:
  pressing arrow keys leads randomly to the effect of stuck number key
  and produces output in consoles or text editors like: "22" or
  "88". Pressing some other key stops the infinite flooding.

  This may (or not) be related to the following flooding in
  /var/log/system

  May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.
  May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key 
released (translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.

  
  these messages are generated approximately each 200 msec. If the former is 
not related to stuck key problem, please, ignore.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 24 09:45:39 2016
  DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2013-11-17 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 2191
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN55WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 24 08:57:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Touch-packages] [Bug 1165313] Re: Right arrow, comma and circumflex keys don't work anymore

2016-08-17 Thread Launchpad Bug Tracker
[Expired for xkeyboard-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1165313

Title:
  Right arrow, comma and circumflex keys don't work anymore

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04

  keyboard layout as given by parameters is : "French (Alternative)"

  After todays updates several keys including "Right Arrow Key" "Comma
  Key" and "Circumflex" don't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1165313/+subscriptions

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


[Touch-packages] [Bug 1498732] Re: keyboard layout setup

2016-08-17 Thread Launchpad Bug Tracker
[Expired for xkeyboard-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1498732

Title:
  keyboard layout setup

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  Keyboard layout in Ubuntu 15 setup doesn't seem to work.  When
  selecting "Dvorak" manually in the F3 menu or using the automatic
  layout detection, which correctly detects Dvorak, the layout isn't
  actually set.  For instance a couple screens later when asking for the
  hostname the keyboard layout is ASCII and when the machine boots
  asking for the username/password it's ASCII.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1498732/+subscriptions

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


[Touch-packages] [Bug 1613352] Re: Test timeout: MesaDisplayConfigurationTest.reads_updated_subpixel_information

2016-08-17 Thread Daniel van Vugt
** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1613352

Title:
  Test timeout:
  MesaDisplayConfigurationTest.reads_updated_subpixel_information

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  MesaDisplayConfigurationTest.reads_updated_subpixel_information
  will timeout under load.

  06:17:37 28: [--] 8 tests from MesaDisplayConfigurationTest
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.configuration_is_read_correctly
  06:17:37 28: [ OK ] 
MesaDisplayConfigurationTest.configuration_is_read_correctly (196 ms)
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.reads_subpixel_information_correctly
  06:17:37 28: [ OK ] 
MesaDisplayConfigurationTest.reads_subpixel_information_correctly (264 ms)
  06:17:37 28: [ RUN ] 
MesaDisplayConfigurationTest.reads_updated_subpixel_information
  08:47:37 make[2]: *** [test] Terminated
  08:47:37 make: *** [build] Terminated
  08:47:37 make[1]: *** wait: No child processes.  Stop.
  08:47:37 make[1]: *** Waiting for unfinished jobs
  08:47:37 make[1]: *** wait: No child processes.  Stop.
  08:47:37 Makefile:85: recipe for target 'test' failed
  08:47:37 debian/rules:13: recipe for target 'build' failed
  08:47:37 E: Caught signal ���Terminated���: terminating immediately
  08:47:37 Build killed with signal TERM after 150 minutes of inactivity
  08:47:37 

  First seen here:
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/1811/consoleFull
  and reproduced under load locally with lp:mir.

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

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


[Touch-packages] [Bug 1613816] Re: Autopilot tests fail

2016-08-17 Thread Arthur Mello
** Branch linked: lp:~artmello/gallery-app/gallery-app-fix_1613816

** Changed in: gallery-app (Ubuntu)
   Status: New => In Progress

** Changed in: gallery-app (Ubuntu)
 Assignee: (unassigned) => Arthur Mello (artmello)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1613816

Title:
  Autopilot tests fail

Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Somewhere between 03.10 and 04.10 the autopilot tests of the gallery
  application has suffered a major regression.

  During that periond the 1289..1290 revisions were released.

  The tests fail with this backtrace.

  
  Traceback (most recent call last):
  File "/home/phablet/autopilot/gallery_app/tests/test_events_view.py", line 
119, in test_share_single_photo
  self.events_view.select_photo(self.sample_jpg_files[3])
  File "/home/phablet/autopilot/gallery_app/emulators/events_view.py", line 
106, in select_photo
  photo = self._get_item_in_event_view(photo_name, event_index_num)
  File "/home/phablet/autopilot/gallery_app/emulators/events_view.py", line 90, 
in _get_item_in_event_view
  'Photo with image name {} could not be found'.format(image_name))
  gallery_app.emulators.gallery_utils.GalleryAppException: Photo with image 
name /home/phablet/Pictures/sample01.jpg could not be found

  
  Full logs are available here -> 
http://people.canonical.com/~bzoltan/ap-2016-04-10-VIVID-SILO16-MAKO/ap-2016_04_09-19_41_12-gallery_app-1-archive.tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1613816/+subscriptions

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


[Touch-packages] [Bug 1614328] [NEW] Ubuntu 16.04 graphics

2016-08-17 Thread Daniel
Public bug reported:

Graphics not working properly. Screen flashes and render very slow.
Intermitterend black screen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Aug 18 04:25:45 2016
DistUpgraded: 2016-07-02 05:10:08,328 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 nvidia-364, 364.19, 4.4.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 12) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:1722]
InstallationDate: Installed on 2015-07-21 (394 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP ProBook 6440b
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=a5182374-ace4-48ce-aa22-0fde8fe63540 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-07-02 (46 days ago)
dmi.bios.date: 03/28/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDD Ver. F.21
dmi.board.name: 1722
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 29.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDDVer.F.21:bd03/28/2012:svnHewlett-Packard:pnHPProBook6440b:pvr:rvnHewlett-Packard:rn1722:rvrKBCVersion29.37:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6440b
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Aug 15 18:41:40 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id6460 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614328

Title:
  Ubuntu 16.04 graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Graphics not working properly. Screen flashes and render very slow.
  Intermitterend black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug 18 04:25:45 2016
  DistUpgraded: 2016-07-02 05:10:08,328 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   nvidia-364, 364.19, 4.4.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:1722]
  InstallationDate: Installed on 2015-07-21 (394 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP ProBook 6440b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=a5182374-ace4-48ce-aa22-0fde8fe63540 ro quiet splash vt.handoff=7
  

[Touch-packages] [Bug 1370008] Re: URL Dispatcher Should Prompt on Bad URL

2016-08-17 Thread Ted Gould
** Branch linked: lp:~ted/url-dispatcher/bad-url-prompt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  Confirmed
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1588915] Re: ifup does not block for interface to be up with static addresses

2016-08-17 Thread Iskren Ivov Chernev
I'm also affected by this issue.

So network-online.target and network.target are a good catch all that
should work, but also there should be a way to wait on a particular
(especially statically configured) interface to be up. I would think
ifup@XXX.service would finish only after XXX is up, but that is not the
case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1588915

Title:
  ifup does not block for interface to be up with static addresses

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 16.04 LTS (server)
  Release:16.04

  systemd:
Installed: 229-4ubuntu6
Candidate: 229-4ubuntu6
Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This issue is more about systemd integration then an issue with
  systemd package itself.  The general problem is the distinction
  between the network being configured and the network being up and what
  that means for services that depend on the network.

  upstream systemd has network.target (network is configured) and
  network-online.target (network is up), however xenial server (dunno
  about desktop) doesn't seem to use network-online.target.  The result
  of which is, as soon as the network is configured both network.target
  and network-online.target are considered complete.  At which point
  services dependent on either of those will get started.  However this
  can lead to problems if the services in question are actually
  dependent on the network (ie dns lookups) when they are starting up.

  Here's an example of what I mean.  If you install openntpd and add the
  -s option there is a race on boot if it will or wont be able to do the
  initial sync.

  Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network.
  Jun 02 16:58:02 xenial64 systemd[1]: Starting OpenNTPd Network Time 
Protocol...
  Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network is Online.
  Jun 02 16:58:02 xenial64 ntpd[920]: constraint certificate verification 
turned off
  Jun 02 16:58:02 xenial64 ntpd[928]: ntp engine ready
  Jun 02 16:58:02 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is down
  Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is up at 1000 
Mbps, full duplex
  Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Flow control is on 
for TX and on for RX
  Jun 02 16:58:05 xenial64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link 
becomes ready
  Jun 02 16:58:17 xenial64 ntpd[920]: no reply received in time, skipping 
initial time setting

  openntpd was started 3 seconds before the interface even got link.

  I believe this issue is only going to effect physical servers with
  static ips.  vm's interfaces will instantly have link when they are
  brought up and dhcp, the interface will already be up or else they
  wouldn't have been able to get an ip.

  thanks
  jim

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

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


[Touch-packages] [Bug 1562634] Re: package initramfs-tools 0.103ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-17 Thread nila...@nilandsplace.com
** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1562634

Title:
  package initramfs-tools 0.103ubuntu4.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  too complex too many options you sort it out please

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.3
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Mar 28 00:05:57 2016
  DuplicateSignature: package:initramfs-tools:0.103ubuntu4.3:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-08 (19 days ago)
  InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1562634/+subscriptions

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


[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

2016-08-17 Thread pjd
@janl
in my case, apt was unable to use the _apt user due to misconfiguration. it did 
report (some) failure, which to ignore would be my choice and responsibility 
then - there is no way of making apt resolve the _apt user issue in a way that 
would lead to consistently increasing system security.

hence this is not a security bug, but rather just a request for
increasing verbosity in error messages - in order to ease debugging
OTHER bugs.


please verify that you did indeed have the same issue with the following steps:
1. run apt, preserving the /tmp/apt.(data|sig).+ downloads (e.g. by 
*temporarily* chattr+a-ing your /tmp directory)
2. run the apt-key command on the exact same files from a root command line and 
compare output
3. run the apt-key command on the exact same files from a _apt command line and 
compare output

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1577926

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
  W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
  [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
  [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
  [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
  [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
  [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
  [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Víctor R . Ruiz
Yes, my SIM was locked.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

2016-08-17 Thread janl
It should be noted that since this totally prevents updating of the
machine this is also a security bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1577926

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
  W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
  [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
  [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
  [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
  [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
  [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
  [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

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


[Touch-packages] [Bug 1614299] [NEW] install failure on python 3.5

2016-08-17 Thread Reece
Public bug reported:

Related to expired issue: https://answers.launchpad.net/ubuntu/+source
/python-apt/+question/285522


snafu$ cd /tmp

snafu$ pyvenv apt

snafu$ source apt/bin/activate

(apt) snafu$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial
Linux snafu 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

(apt) snafu$ pip install python-apt
Collecting python-apt
  Using cached python-apt-0.7.8.tar.bz2
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-build-l1pt_xe2/python-apt/setup.py", line 6, in 
from DistUtilsExtra.command import *
ImportError: No module named 'DistUtilsExtra'


Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-l1pt_xe2/python-apt/
You are using pip version 8.1.1, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1614299

Title:
  install failure on python 3.5

Status in python-apt package in Ubuntu:
  New

Bug description:
  Related to expired issue: https://answers.launchpad.net/ubuntu/+source
  /python-apt/+question/285522

  
  snafu$ cd /tmp

  snafu$ pyvenv apt

  snafu$ source apt/bin/activate

  (apt) snafu$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  Linux snafu 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  (apt) snafu$ pip install python-apt
  Collecting python-apt
Using cached python-apt-0.7.8.tar.bz2
  Complete output from command python setup.py egg_info:
  Traceback (most recent call last):
File "", line 1, in 
File "/tmp/pip-build-l1pt_xe2/python-apt/setup.py", line 6, in 
  from DistUtilsExtra.command import *
  ImportError: No module named 'DistUtilsExtra'
  
  
  Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-l1pt_xe2/python-apt/
  You are using pip version 8.1.1, however version 8.1.2 is available.
  You should consider upgrading via the 'pip install --upgrade pip' command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1614299/+subscriptions

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


[Touch-packages] [Bug 1380364] Re: lightdm writes XDISPLAY instead of tty device name to utmp record

2016-08-17 Thread Mathew Hodson
** Branch linked: lp:~seb128/unity-control-center/lightdm-login-history

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1380364

Title:
  lightdm writes XDISPLAY instead of tty device name to utmp record

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  Until now, I've been using good old gdm-2.20.11 and wanted to switch
  to lightdm-1.12.1. If you list users logged in via the 'w' or 'who'
  command, it shows you who is logged in and what they are doing.
  Especially, on which tty. Example:

  USER TTYLOGIN@   IDLE   JCPU   PCPU WHAT
  usertty9  03Oct14 16days  1:52m  0.01s /bin/sh /etc/xdg/xfce4/xinitrc 
-- /etc/X11/xinit/xserverrc

  Also, 'who' gives this information:
  usertty9 Oct  3 22:34 (:20)

  However, lightdm does not follow that tradition. Instead, it prints :0
  instead of the actual tty, and something weird for other values (like
  ?xdm? instead of the idle value etc.)

  'w':
  USER TTYLOGIN@   IDLE   JCPU   PCPU WHAT
  user:019:50   ?xdm?  23.82s  0.01s /bin/sh /etc/xdg/xfce4/xinitrc 
-- /etc/X11/xinit/xserverrc

  Note: :0 is not tty, it is DISPLAY env.

  'who':
  user:0   2014-10-12 19:50 (:0)

  The same for this one. I wonder, is this a bug (to me it seems so,
  because for every other program the correct values are reported)?

  It is a problem for me, because I have written scripts for automation
  etc. that parse w and who output to determine which tty is in use by
  which DISPLAY.

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

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


[Touch-packages] [Bug 1614254] Re: Help

2016-08-17 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Please also change the bug title to something more meaningful.

Thanks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614254

Title:
  Help

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  no clue Not familiar

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 13:43:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
  InstallationDate: Installed on 2016-07-30 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/dash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80E6
  dmi.board.vendor: HP
  dmi.board.version: 87.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/04/2016:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80E6:rvr87.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug 16 19:07:42 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-08-17 Thread John Johansen
could you try reproducing with the kernel in

http://people.canonical.com/~jj/linux+jj/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135

Title:
  kernel BUG on snap disconnect from within a snap

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

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

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


[Touch-packages] [Bug 1614254] [NEW] Help

2016-08-17 Thread Matt
Public bug reported:

no clue Not familiar

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Aug 17 13:43:55 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
InstallationDate: Installed on 2016-07-30 (17 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP ENVY m7 Notebook
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/dash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80E6
dmi.board.vendor: HP
dmi.board.version: 87.60
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/04/2016:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80E6:rvr87.60:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY m7 Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 16 19:07:42 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614254

Title:
  Help

Status in xorg package in Ubuntu:
  New

Bug description:
  no clue Not familiar

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 13:43:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
  

[Touch-packages] [Bug 1614223] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-17 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  The version of update-initramfs that you likely have
installed is unable to work on a persistent usb stick.  You can resolve
this issue by upgrading the version of casper on your system. This can
be done via the commands:

sudo apt-get update; sudo apt-get install casper

Then performing the software update or installation that you were
originally trying.  If this does not resolve your bug please set its
status back to New.  Thanks in advance!

** Tags added: needs-new-casper

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1614223

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Only updating a new instalation of Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Wed Aug 17 18:54:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1614223/+subscriptions

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


[Touch-packages] [Bug 1612316] Re: Browser is out of date

2016-08-17 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1599146 ***
https://bugs.launchpad.net/bugs/1599146

** This bug has been marked a duplicate of bug 1599146
   captcha's don't work on Ubuntu browser

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1612316

Title:
  Browser is out of date

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Captcha verification doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1612316/+subscriptions

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


[Touch-packages] [Bug 1614234] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2016-08-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1482008 ***
https://bugs.launchpad.net/bugs/1482008

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1482008

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1614234

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: udev 231-1
  Uname: Linux 4.8.0-040800rc2-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 17 16:21:26 2016
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-07-26 (388 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-040800rc2-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

2016-08-17 Thread Mathew Hodson
** Changed in: sudo (Ubuntu)
   Importance: Undecided => High

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1595558

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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


[Touch-packages] [Bug 1614232] [NEW] python-lxc attach_wait prevents further keyboard input

2016-08-17 Thread Larry Price
Public bug reported:

I previously reported this bug on Github
(https://github.com/lxc/lxc/issues/1137), but am duplicating the report
here for completeness.

I've found that my python scripts stop responding to keyboard input
after running an lxc attach_wait command in python3-lxc
(2.0.4-0ubuntu2).

I wrote a small script to quickly reproduce the issue. With the script,
one can see that using Ctrl+C before running the lxc command causes a
KeyboardInterrupt, but using Ctrl+C after the lxc command finishes is no
longer caught.

#!/usr/bin/env python3

import lxc
import time
import os

CONTAINER_NAME='xenial'
CONTAINER_PATH='%s/.cache/libertine-container' % os.environ["HOME"]

def lxc_work():
container = lxc.Container(CONTAINER_NAME, CONTAINER_PATH)
container.start()
container.attach_wait(lxc.attach_run_command, ['ls'])

print("Ctrl+C will attempt to stop the script during the next ~5 seconds")
time.sleep(5)

print("Running lxc command 'ls' in container '%s', please wait..." % 
CONTAINER_NAME)
lxc_work()

print("Ctrl+C should attempt to stop the script in the next ~5 seconds, but 
doesn't")
time.sleep(5)

Also see:
https://gist.github.com/larryprice/f562f838ff84929c1619978a6404b8b6

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1614232

Title:
  python-lxc attach_wait prevents further keyboard input

Status in lxc package in Ubuntu:
  New

Bug description:
  I previously reported this bug on Github
  (https://github.com/lxc/lxc/issues/1137), but am duplicating the
  report here for completeness.

  I've found that my python scripts stop responding to keyboard input
  after running an lxc attach_wait command in python3-lxc
  (2.0.4-0ubuntu2).

  I wrote a small script to quickly reproduce the issue. With the
  script, one can see that using Ctrl+C before running the lxc command
  causes a KeyboardInterrupt, but using Ctrl+C after the lxc command
  finishes is no longer caught.

  #!/usr/bin/env python3

  import lxc
  import time
  import os
  
  CONTAINER_NAME='xenial'
  CONTAINER_PATH='%s/.cache/libertine-container' % os.environ["HOME"]
  
  def lxc_work():
  container = lxc.Container(CONTAINER_NAME, CONTAINER_PATH)
  container.start()
  container.attach_wait(lxc.attach_run_command, ['ls'])
  
  print("Ctrl+C will attempt to stop the script during the next ~5 seconds")
  time.sleep(5)
  
  print("Running lxc command 'ls' in container '%s', please wait..." % 
CONTAINER_NAME)
  lxc_work()
  
  print("Ctrl+C should attempt to stop the script in the next ~5 seconds, 
but doesn't")
  time.sleep(5)

  Also see:
  https://gist.github.com/larryprice/f562f838ff84929c1619978a6404b8b6

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

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


[Touch-packages] [Bug 1612316] Re: Browser is out of date

2016-08-17 Thread Tyler Hicks
** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1612316

Title:
  Browser is out of date

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Captcha verification doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1612316/+subscriptions

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


[Touch-packages] [Bug 1614226] [NEW] package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

2016-08-17 Thread abduladim rihan
Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk-3-bin 3.18.9-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 16 09:49:41 2016
ErrorMessage: subprocess new pre-installation script returned error exit status 
2
InstallationDate: Installed on 2016-08-10 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: gtk+3.0
Title: package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1614226

Title:
  package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 2

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-bin 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Aug 16 09:49:41 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2016-08-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: gtk+3.0
  Title: package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1614226/+subscriptions

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


[Touch-packages] [Bug 1614223] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-17 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1614223

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Only updating a new instalation of Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Wed Aug 17 18:54:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1614223/+subscriptions

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


[Touch-packages] [Bug 1614223] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-17 Thread Luiz Scott
Public bug reported:

Only updating a new instalation of Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
Date: Wed Aug 17 18:54:42 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
LiveMediaBuild: It
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1614223

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Only updating a new instalation of Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Wed Aug 17 18:54:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1614223/+subscriptions

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


[Touch-packages] [Bug 1613638] Re: [MIR] unity8

2016-08-17 Thread Michael Terry
- This lintian warning indicates something that could cause a problem
later if we want to co-install multiarch unity8-fake-env packages.
Could we move that binary?  "unity8-fake-env: arch-dependent-file-not-
in-arch-specific-directory usr/bin/unity-mock-indicator-service"  Not
really a blocker, but should be done.  Bug 1614219.

- There are a million bugs, but since this MIR is in service of slowly
building u8 up to be ready, rather than an immediate switch, that's
fine.

Otherwise packaging seemed fine.  Team is subscribed to bugs.  Tests are
run during build and in autopkg.  It is clearly actively maintained.

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1613638

Title:
  [MIR] unity8

Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is planned for inclusion in main for 16.10

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   The whole list of dependencies being MIR'ed is being tracked by 
https://trello.com/b/mab4G8UQ/unity-8-in-16-10
   * indicator-network [bug #1612619]
   * libusermetrics [bug #1612259]
   * pay-service [https://trello.com/c/hgcmUB7z]
   * qmenumodel [bug #1612363]
   * qtmir [bug #1612358]
   * qtsystems-opensource-src [bug #1552860]
   * thumbnailer [bug #1613561]
   * ubuntu-settings-components [bug #1613640]
   * ubuntu-system-settings [bug #1612280]
   * unity-notifications [bug #1613678]
   * unity-scopes-api [bug #1612461]
   * unity-scopes-shell [bug #1612460]
   * unity-system-compositor [bug #1613601]
   Recommends:
   * unity-scope-click [https://trello.com/c/GD6LuwNl]
   * unity-scope-mediascanner [bug #1218409]
   Potential to skip:
   * biometryd [https://trello.com/c/oP4UmB9t]
   * telephony-service [bug #1613490]

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

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


[Touch-packages] [Bug 1614219] [NEW] Move unity-mock-indicator-service to a multiarch path

2016-08-17 Thread Michael Terry
Public bug reported:

/usr/bin/unity-mock-indicator-service is currently in unity8-fake-env,
which is Multi-Arch: same.

Which means if you tried to install unity8-fake-env:i386 and unity8
-fake-env:amd64, you'll get an error, because the path would conflict
and the contents would be different.

So we need to either move it into /usr/lib/XXX/unity8/ or move it into a
package that is Multi-Arch: foreign.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614219

Title:
  Move unity-mock-indicator-service to a multiarch path

Status in unity8 package in Ubuntu:
  New

Bug description:
  /usr/bin/unity-mock-indicator-service is currently in unity8-fake-env,
  which is Multi-Arch: same.

  Which means if you tried to install unity8-fake-env:i386 and unity8
  -fake-env:amd64, you'll get an error, because the path would conflict
  and the contents would be different.

  So we need to either move it into /usr/lib/XXX/unity8/ or move it into
  a package that is Multi-Arch: foreign.

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

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


[Touch-packages] [Bug 1612339] Re: package libc6:i386 2.19-0ubuntu6.9 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/li

2016-08-17 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1612339

Title:
  package libc6:i386 2.19-0ubuntu6.9 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright
  usr/share/lintian/overrides/libc6] failed to install/upgrade: package
  libc6:i386 2.19-0ubuntu6.9 cannot be configured because libc6:amd64 is
  at a different version (2.23-0ubuntu3)

Status in eglibc package in Ubuntu:
  New

Bug description:
  I don't even understand Geek Language you are asking me about...WHAT
  is eglibc??? what does it mean???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libc6:i386 2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6]
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Aug 11 09:22:29 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.23-0ubuntu3
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DuplicateSignature: package:libc6:i386:2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6]:package libc6:i386 2.19-0ubuntu6.9 cannot be 
configured because libc6:amd64 is at a different version (2.23-0ubuntu3)
  ErrorMessage: package libc6:i386 2.19-0ubuntu6.9 cannot be configured because 
libc6:amd64 is at a different version (2.23-0ubuntu3)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: eglibc
  Title: package libc6:i386 2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6] failed to install/upgrade: package 
libc6:i386 2.19-0ubuntu6.9 cannot be configured because libc6:amd64 is at a 
different version (2.23-0ubuntu3)
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (0 days ago)

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

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


[Touch-packages] [Bug 1612339] Re: package libc6:i386 2.19-0ubuntu6.9 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/li

2016-08-17 Thread Tyler Hicks
** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1612339

Title:
  package libc6:i386 2.19-0ubuntu6.9 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright
  usr/share/lintian/overrides/libc6] failed to install/upgrade: package
  libc6:i386 2.19-0ubuntu6.9 cannot be configured because libc6:amd64 is
  at a different version (2.23-0ubuntu3)

Status in eglibc package in Ubuntu:
  New

Bug description:
  I don't even understand Geek Language you are asking me about...WHAT
  is eglibc??? what does it mean???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libc6:i386 2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6]
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Aug 11 09:22:29 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.23-0ubuntu3
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DuplicateSignature: package:libc6:i386:2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6]:package libc6:i386 2.19-0ubuntu6.9 cannot be 
configured because libc6:amd64 is at a different version (2.23-0ubuntu3)
  ErrorMessage: package libc6:i386 2.19-0ubuntu6.9 cannot be configured because 
libc6:amd64 is at a different version (2.23-0ubuntu3)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: eglibc
  Title: package libc6:i386 2.19-0ubuntu6.9 [modified: 
usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright 
usr/share/lintian/overrides/libc6] failed to install/upgrade: package 
libc6:i386 2.19-0ubuntu6.9 cannot be configured because libc6:amd64 is at a 
different version (2.23-0ubuntu3)
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (0 days ago)

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

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


[Touch-packages] [Bug 1613043] Re: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

2016-08-17 Thread Tyler Hicks
** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1613043

Title:
  package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: подпроцесс установлен сценарий pre-removal возвратил
  код ошибки 1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 13 13:53:39 2016
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2015-08-12 (367 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код 
ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1613043/+subscriptions

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


[Touch-packages] [Bug 1614215] [NEW] "md5sums differ" message seems to indicate an install problem

2016-08-17 Thread Mike Robinson
Public bug reported:

Upon applying the latest Ubuntu routine-update, I observed these
messages:

Setting up apparmor (2.10.95-0ubuntu2.2) ...
Installing new version of config file 
/etc/apparmor.d/abstractions/dbus-session-strict ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Files /var/lib/dpkg/info/apparmor.md5sums and 
/var/lib/apparmor/profiles/.apparmor.md5sums differ

"The reason why I am filing a bug report" is the LAST line.  I presume
that if md5sums do not agree, something was probably done improperly in
preparing this particular software-update blast.

However, in-passing, I would also point out line #3, about "start and
stop actions no longer supported." That seems to me to be something (of
much less importance, obviously) that might have been overlooked.  (I've
seen =that= message for some time now.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Aug 17 14:22:55 2016
InstallationDate: Installed on 2016-03-02 (168 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/hostname--vg-root ro
SourcePackage: apparmor
Syslog:
 Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is 
enabled
 Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is 
enabled
 Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is 
enabled
 Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is 
enabled
UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1614215

Title:
  "md5sums differ" message seems to indicate an install problem

Status in apparmor package in Ubuntu:
  New

Bug description:
  Upon applying the latest Ubuntu routine-update, I observed these
  messages:

  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/dbus-session-strict ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Files /var/lib/dpkg/info/apparmor.md5sums and 
/var/lib/apparmor/profiles/.apparmor.md5sums differ

  "The reason why I am filing a bug report" is the LAST line.  I presume
  that if md5sums do not agree, something was probably done improperly
  in preparing this particular software-update blast.

  However, in-passing, I would also point out line #3, about "start and
  stop actions no longer supported." That seems to me to be something
  (of much less importance, obviously) that might have been overlooked.
  (I've seen =that= message for some time now.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug 17 14:22:55 2016
  InstallationDate: Installed on 2016-03-02 (168 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: apparmor
  Syslog:
   Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

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

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


Re: [Touch-packages] [Bug 1614158] Re: Don't get up by starting

2016-08-17 Thread modaell
Hi

you are right, English is not my nativ lanuage... and Computerprogramms 
also not. But I try to explaine again:

I don't refferring to some programs , I referring to the startup of my 
computer with the new version of ubuntu. I downloadedthis version ca. 
week ago and till this time the start up of ubuntu don't get fast and it 
ist sometimes complicat

Thanks for your help


Am 17.08.2016 um 18:50 schrieb Paul White:
> Hi modaell,
>
> You say: "I have to wait lontimes till the programm start up. Sometimes
> i close cold and try again. Then I make esc and take the programm ubuntu
> and then it works better"
>
> I appreciate that English may not be your native language but which
> programs are you referring to? Please gives us some examples.
>
> You have reported a bug against the xorg package. Was that your
> intention?
>
> Are you referring to the startup of your PC or the startup of individual
> applications that you have installed?
>
> Please clarify, thanks.
>
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614158

Title:
  Don't get up by starting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have to wait lontimes till the programm start up. Sometimes i close
  cold and try again. Then I make esc and take the programm ubuntu and
  then it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 18:07:07 2016
  DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
  InstallationDate: Installed on 2015-04-29 (476 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6475b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=9d20e8cc-fbe8-4310-8a57-2061e2a6c8bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (13 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68RTU Ver. F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 180F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 47.19
  dmi.chassis.asset.tag: CNU3329NSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68RTUVer.F.46:bd10/07/2013:svnHewlett-Packard:pnHPProBook6475b:pvrA1029D1103:rvnHewlett-Packard:rn180F:rvrKBCVersion47.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6475b
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 17 18:05:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1614210] [NEW] Remove incomplete fips in openssl in xenial.

2016-08-17 Thread Joy Latten
Public bug reported:

Package: openssl-1.0.2g-1ubuntu4.1
Distro: xenial

The openssl contains incomplete fips patches. In light that the fips is
incomplete and will not be completed in the main archive and they are
impacting customers, they should be withdrawn. See lp bugs 1593953,
1591797, 1594748, 1588524, 1613658. Removal of these fips patches will
remove these fips-related issues.

[Test case]
1. Problem in 1594748
Note: this problem was reported in upstream openssl and testcase posted there 
also.
https://rt.openssl.org/Ticket/Display.html?id=4559

CRYPTO_set_mem_functions() always returns 0 because library
initialization within fips code already calls CRYPTO_malloc() and
disables it.

This testcase should cause openssl to abort, but instead it returns a
context.

#include 
#include 
#include 
void * my_alloc(size_t n) { abort(); }
void my_free(void *p) { abort(); }
void * my_realloc(void *p, size_t n) { abort(); }
int main(int argc, const char **argv)
{
  const SSL_METHOD *method;
  SSL_CTX *ctx;
  CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
  SSL_library_init();
  method = SSLv23_client_method();
  ctx = SSL_CTX_new(method);
  printf("Got ctx %p\n", ctx);
  return 0;
}

2. Problem in 1593953
EC key generation allows user to generate keys using EC curves that the EC sign 
and verify
do not support when OPENSSL_FIPS is defined.
Testcase taken from lp #1593953

openssl ecparam -genkey -name Oakley-EC2N-4

will fail when OPENSSL_FIPS is defined since it causes a fips key-pair 
consistency check to be done.
Otherwise, without OPENSSL_FIPS defined, the check is not done.

3. Problem reported in 1588524
Error code being skipped...

Testcase taken from lp #1588524

#include 
#include 

int main() {
int rc;
unsigned long fips_err;
SSL_library_init();
SSL_load_error_strings();
ERR_load_crypto_strings();
OpenSSL_add_all_algorithms();
rc = FIPS_mode_set(1);
fips_err = ERR_peek_last_error();

// FIPS_mode_set will return 0 on failure, which is expected if
// the FIPS module is not compiled. In this case, we should then
// be able to get the error code
// CRYPTO_R_FIPS_MODE_NOT_SUPPORTED (0xf06d065)
// https://wiki.openssl.org/index.php/FIPS_mode_set%28%29
printf("%d %lu\n", rc, fips_err);
ERR_print_errors_fp(stdout);

ERR_free_strings();
return 0;
}

Should report an error message.

[ Regression potential ]
Removing the fips patches should decrease regression potential of openssl in 
the main archive.

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

** Description changed:

+ openssl-1.0.2g-1ubuntu4.1 in xenial.
+ 
  The openssl contains incomplete fips patches. In light that the fips is
  incomplete and will not be completed in the main archive and they are
  impacting customers, they should be withdrawn. See lp bugs 1593953,
  1591797, 1594748, 1588524, 1613658. Removal of these fips patches will
  remove these fips-related issues.
  
  [Test case]
- 1. Problem in 1594748 
+ 1. Problem in 1594748
  Note: this problem was reported in upstream openssl and testcase posted there 
also.
  https://rt.openssl.org/Ticket/Display.html?id=4559
  
  CRYPTO_set_mem_functions() always returns 0 because library
  initialization within fips code already calls CRYPTO_malloc() and
  disables it.
  
  This testcase should cause openssl to abort, but instead it returns a
  context.
  
  #include 
  #include 
  #include 
  void * my_alloc(size_t n) { abort(); }
  void my_free(void *p) { abort(); }
  void * my_realloc(void *p, size_t n) { abort(); }
  int main(int argc, const char **argv)
  {
-   const SSL_METHOD *method;
-   SSL_CTX *ctx;
-   CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
-   SSL_library_init();
-   method = SSLv23_client_method();
-   ctx = SSL_CTX_new(method);
-   printf("Got ctx %p\n", ctx);
-   return 0;
+   const SSL_METHOD *method;
+   SSL_CTX *ctx;
+   CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
+   SSL_library_init();
+   method = SSLv23_client_method();
+   ctx = SSL_CTX_new(method);
+   printf("Got ctx %p\n", ctx);
+   return 0;
  }
  
  2. Problem in 1593953
  EC key generation allows user to generate keys using EC curves that the EC 
sign and verify
  do not support when OPENSSL_FIPS is defined.
  Testcase taken from lp #1593953
  
  openssl ecparam -genkey -name Oakley-EC2N-4
  
  will fail when OPENSSL_FIPS is defined since it causes a fips key-pair 
consistency check to be done.
  Otherwise, without OPENSSL_FIPS defined, the check is not done.
  
  3. Problem reported in 1588524
  Error code being skipped...
  
  Testcase taken from lp #1588524
  
  #include 
  #include 
  
  int main() {
- int rc;
- unsigned long fips_err;
- SSL_library_init();
- SSL_load_error_strings();
- ERR_load_crypto_strings();
- OpenSSL_add_all_algorithms();
- rc = FIPS_mode_set(1);
- fips_err = ERR_peek_last_error();
+ int rc;
+ unsigned long 

[Touch-packages] [Bug 1612942] Re: Underlined word doesn't get submitted in some apps such ass Talaan

2016-08-17 Thread Anupam
According to the developer of Talaan (comment #7 of bug #1559940), this
happens when one has "word suggestions" (dictionary) on. As a workaround
one has to either put one extra space after the last word or select the
desired (last) word from the list of suggestions after typing all the
time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1612942

Title:
  Underlined word doesn't get submitted in some apps such ass Talaan

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  In Talaan:

  
  1. Create new TODO item
  2. Type a few words, don't type a space after the last word. This word stays 
underlined.
  3. Press the "+" to add the TODO item

  Expected result: the complete sentence is submitted

  Actual result: The last word isn't submitted.

  When pressing space after the last word, the word stops being
  underlined. If you press the + then, the whole sentence gets
  submitted.

  
  I have experienced the same behavior in other apps such as facebook messenger.

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

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


[Touch-packages] [Bug 1614204] [NEW] Unicode 9.0 emojis not showing

2016-08-17 Thread Anupam
Public bug reported:

Someone sent me a Unicode 9.0 "ROFL" emoji 
(http://emojipedia.org/rolling-on-the-floor-laughing/), but it showed up as a 
blank box.
Device: E5, OTA-12, stable channel

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Unicode 9.0 emojis are not showing
+ Unicode 9.0 emojis not showing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1614204

Title:
  Unicode 9.0 emojis not showing

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Someone sent me a Unicode 9.0 "ROFL" emoji 
(http://emojipedia.org/rolling-on-the-floor-laughing/), but it showed up as a 
blank box.
  Device: E5, OTA-12, stable channel

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

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


[Touch-packages] [Bug 1612942] Re: Underlined word doesn't get submitted in some apps such ass Talaan

2016-08-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1612942

Title:
  Underlined word doesn't get submitted in some apps such ass Talaan

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  In Talaan:

  
  1. Create new TODO item
  2. Type a few words, don't type a space after the last word. This word stays 
underlined.
  3. Press the "+" to add the TODO item

  Expected result: the complete sentence is submitted

  Actual result: The last word isn't submitted.

  When pressing space after the last word, the word stops being
  underlined. If you press the + then, the whole sentence gets
  submitted.

  
  I have experienced the same behavior in other apps such as facebook messenger.

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

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


[Touch-packages] [Bug 1613601] Re: [MIR] unity-system-compositor

2016-08-17 Thread Michael Terry
- android-properties should be a Build-Dep in arm64, right?

- Is ubuntu-desktop-mir needed anymore?

- This builds its autopilot package with python2...  Didn't we switch to
python3 for all autopilot usage?  I'd think it should build-dep on dh-
python, drop the python2 build-deps, and use --with python3 instead of
--with python2 (and switch python:Depends to python3:Depends, depend on
python3-autopilot instead of python-autopilot, etc).

- Can we subscribe phablet-team, ubuntu-phonedations-bugs, or unity-api-
team to LP bugs?  Whichever you think is most appropriate.  We just want
a standard team on the hook for bugs.

- Does anyone know if we can drop the "sleep .1" from the wrapper
script?  I worry the answer is no, and that we will never drop it.

- It seems like there are an awful lot of crashers in the bug list.  But
since this MIR is clearing the way to slowly experiment with phasing
this onto Desktops instead of an immediate switch, we can get those down
over time.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1613601

Title:
  [MIR] unity-system-compositor

Status in unity-system-compositor package in Ubuntu:
  Incomplete

Bug description:
  Note that a much older version of unity-system-compositor had been previously 
accepted into main:
  https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588

  [Availability]
  * Available in universe

  [Rationale]
  * This package is the system compositor for our convergence effort
  * Used by default on phablet images and in the Unity8 session on the desktop

  [Security]
  * No known security issues at this time
  * A security review is recommended. The package had been reviewed in the past 
by the security team for use on the phone, but it has changed significantly 
since then.

  [Quality assurance]
  * This package has unit and integration tests that run with each package build
  * CI is used during development

  [Dependencies]
  * All dependencies are in main
  * It 'Suggests' repowerd which already has a MIR:
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585

  [Standards compliance]
  * Follows FHS and Debian Policy.
  * This package uses cmake.

  [Maintenance]
  * This package is maintained by Canonical and actively in use on the phone 
images
  * mir-development-team/unity-system-compositor-team are subscribed to project 
and ubuntu package bugs respectively (The unity-system-compositor developers 
are the Mir developers)

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

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


[Touch-packages] [Bug 1605868] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name org.debian.apt was not pro

2016-08-17 Thread Jeremy Bicha
This bug is fixed by making sure aptdaemon is installed.

I encourage you not to have -proposed updates enabled when using a
development release of Ubuntu. See http://askubuntu.com/q/785414/1579

** Package changed: software-properties (Ubuntu) => aptdaemon (Ubuntu)

** Changed in: aptdaemon (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1605868

Title:
  software-properties-gtk crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.debian.apt was not provided by any .service files

Status in aptdaemon package in Ubuntu:
  Fix Committed

Bug description:
  software-properties-gtk crashed after deleted repository and when
  close it

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.4.0-32.51-generic 4.4.15
  Uname: Linux 4.4.0-32-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 23 16:11:45 2016
  DbusErrorAnalysis: no service file providing org.debian.apt
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.debian.apt was not provided by any .service files
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1581990] Re: Profile reload leads to kernel NULL pointer dereference

2016-08-17 Thread Tyler Hicks
Bug #1579135 looks to be the same kernel trace.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1581990

Title:
  Profile reload leads to kernel NULL pointer dereference

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS
  Linux zeus 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
  Apparmor packages 2.10.95-0ubuntu2.

  When I do a "apparmor_parser -r /etc/apparmor.d/usr.lib.dovecot.anvil"
  followed by a "apparmor_parser -r
  /etc/apparmor.d/usr.lib.dovecot.auth" it hangs and the kernel
  complains:

  audit: type=1400 audit(1463327049.301:13641): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/lib/dovecot/anvil" 
pid=13236 comm="apparmor_parser"
  [ cut here ]
  WARNING: CPU: 3 PID: 13236 at 
/build/linux-UbQGH5/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
  AppArmor WARN profile_cmp: ((!b)): 
  Modules linked in:
   ebtable_filter ebtables bridge stp llc rc_technisat_ts35 tda10023 tda10021 
intel_rapl x86_pkg_temp_thermal intel_powerclamp mantis coretemp mantis_core 
dvb_core serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic rc_core input_leds mei_me lpc_ich snd_hda_intel shpchp 
snd_hda_codec mei snd_soc_rt5640 snd_soc_ssm4567 snd_soc_rl6231 snd_soc_core 
snd_hda_core snd_hwdep snd_compress snd_seq_midi ac97_bus snd_seq_midi_event 
snd_pcm_dmaengine 8250_fintek snd_rawmidi snd_pcm snd_seq elan_i2c 
snd_seq_device dw_dmac dw_dmac_core snd_timer snd_soc_sst_acpi snd 8250_dw 
i2c_designware_platform tpm_infineon soundcore spi_pxa2xx_platform 
i2c_designware_core acpi_pad mac_hid kvm_intel kvm irqbypass nf_log_ipv6 xt_hl 
ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6
   xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_tcpudp xt_limit 
xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT 
nf_reject_ipv4 ip6table_filter ip6_tables nf_nat_ftp nf_nat nf_conntrack_ftp 
nf_conntrack iptable_filter ip_tables x_tables autofs4 drbg ansi_cprng 
algif_skcipher af_alg hid_generic usbhid dm_crypt i915 crct10dif_pclmul 
crc32_pclmul i2c_algo_bit drm_kms_helper e1000e syscopyarea aesni_intel 
aes_x86_64 ptp lrw uas gf128mul sysfillrect sysimgblt ahci glue_helper 
fb_sys_fops ablk_helper sdhci_acpi libahci cryptd pps_core drm usb_storage 
video i2c_hid sdhci hid fjes
  CPU: 3 PID: 13236 Comm: apparmor_parser Not tainted 4.4.0-22-generic 
#39-Ubuntu
  Hardware name: Gigabyte Technology Co., Ltd. H97-D3H/H97-D3H-CF, BIOS F3 MX 
05/26/2014
   0086 0171a3d1 880211cb3c00 813e9c53
   880211cb3c48 81cec6e0 880211cb3c38 81080fb2
   880213608400  0008 
  Call Trace:
   [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? u32_swap+0x10/0x10
   [] profile_cmp+0xed/0x180
   [] aa_vec_unique+0x163/0x240
   [] __aa_labelset_update_subtree+0x687/0x820
   [] aa_replace_profiles+0x59b/0xb70
   [] ? __kmalloc+0x22e/0x250
   [] policy_update+0x9f/0x1f0
   [] profile_replace+0x13/0x20
   [] __vfs_write+0x18/0x40
   [] vfs_write+0xa9/0x1a0
   [] ? do_sys_open+0x1bf/0x2a0
   [] SyS_write+0x55/0xc0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 4507a2efab029c8e ]---
  BUG: unable to handle kernel NULL pointer dereference at 0038
  IP: [] profile_cmp+0x2f/0x180
  PGD 20dd58067 PUD 21236c067 PMD 0 
  Oops:  [#1] SMP 
  Modules linked in: ebtable_filter ebtables bridge stp llc rc_technisat_ts35 
tda10023 tda10021 intel_rapl x86_pkg_temp_thermal intel_powerclamp mantis 
coretemp mantis_core dvb_core serio_raw snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic rc_core input_leds mei_me lpc_ich 
snd_hda_intel shpchp snd_hda_codec mei snd_soc_rt5640 snd_soc_ssm4567 
snd_soc_rl6231 snd_soc_core snd_hda_core snd_hwdep snd_compress snd_seq_midi 
ac97_bus snd_seq_midi_event snd_pcm_dmaengine 8250_fintek snd_rawmidi snd_pcm 
snd_seq elan_i2c snd_seq_device dw_dmac dw_dmac_core snd_timer snd_soc_sst_acpi 
snd 8250_dw i2c_designware_platform tpm_infineon soundcore spi_pxa2xx_platform 
i2c_designware_core acpi_pad mac_hid kvm_intel kvm irqbypass nf_log_ipv6 xt_hl 
ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT
   nf_reject_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_multiport 
xt_tcpudp xt_limit xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ipt_REJECT nf_reject_ipv4 ip6table_filter ip6_tables nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables autofs4 drbg 
ansi_cprng algif_skcipher af_alg hid_generic usbhid dm_crypt i915 
crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper e1000e syscopyarea 
aesni_intel aes_x86_64 ptp lrw uas gf128mul sysfillrect 

[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-08-17 Thread Tyler Hicks
Bug #1581990 looks to be the same kernel trace.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135

Title:
  kernel BUG on snap disconnect from within a snap

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

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

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


[Touch-packages] [Bug 1613563] Re: [MIR] unity-api

2016-08-17 Thread Michael Terry
Sure, subbing unity-api-team is fine.  I'm working to get that added to
the package-subscribers list (instead of unity-api-bugs).

Sub them and we're good here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-api in Ubuntu.
https://bugs.launchpad.net/bugs/1613563

Title:
  [MIR] unity-api

Status in unity-api package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch components, such as the 
Unity shell, unity-scopes-api, and others.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   I believe that all the dependencies are part of Ubuntu Touch already.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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


[Touch-packages] [Bug 1614158] Re: Don't get up by starting

2016-08-17 Thread Paul White
Hi modaell,

You say: "I have to wait lontimes till the programm start up. Sometimes
i close cold and try again. Then I make esc and take the programm ubuntu
and then it works better"

I appreciate that English may not be your native language but which
programs are you referring to? Please gives us some examples.

You have reported a bug against the xorg package. Was that your
intention?

Are you referring to the startup of your PC or the startup of individual
applications that you have installed?

Please clarify, thanks.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614158

Title:
  Don't get up by starting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have to wait lontimes till the programm start up. Sometimes i close
  cold and try again. Then I make esc and take the programm ubuntu and
  then it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 18:07:07 2016
  DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
  InstallationDate: Installed on 2015-04-29 (476 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6475b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=9d20e8cc-fbe8-4310-8a57-2061e2a6c8bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (13 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68RTU Ver. F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 180F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 47.19
  dmi.chassis.asset.tag: CNU3329NSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68RTUVer.F.46:bd10/07/2013:svnHewlett-Packard:pnHPProBook6475b:pvrA1029D1103:rvnHewlett-Packard:rn180F:rvrKBCVersion47.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6475b
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 17 18:05:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1605868] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name org.debian.apt was not pro

2016-08-17 Thread Jeremy Bicha
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1605868

Title:
  software-properties-gtk crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.debian.apt was not provided by any .service files

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk crashed after deleted repository and when
  close it

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.4.0-32.51-generic 4.4.15
  Uname: Linux 4.4.0-32-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 23 16:11:45 2016
  DbusErrorAnalysis: no service file providing org.debian.apt
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.debian.apt was not provided by any .service files
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1605868/+subscriptions

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


[Touch-packages] [Bug 1605868] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name org.debian.apt was not pro

2016-08-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1605868

Title:
  software-properties-gtk crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.debian.apt was not provided by any .service files

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk crashed after deleted repository and when
  close it

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.1
  ProcVersionSignature: Ubuntu 4.4.0-32.51-generic 4.4.15
  Uname: Linux 4.4.0-32-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 23 16:11:45 2016
  DbusErrorAnalysis: no service file providing org.debian.apt
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.debian.apt was not provided by any .service files
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1605868/+subscriptions

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


[Touch-packages] [Bug 1614163] Re: unity8 stops processing touch input events after shaking the phone

2016-08-17 Thread Dave Morley
Confirmed for me it opened the section I clicked on but it took an age

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614163

Title:
  unity8 stops processing touch input events after shaking the phone

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 403
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Test Case:
  1. Boot the phone and unlock it
  2. Shake it (I'm on apps scope by default if it matters)
  3. Scroll the page up and down

  Expected result
  Scrolling works as expected, page goes up/down

  Actual result
  The dash is like frozen. A right edge swipe works and clears the problem up.

  The following records are logged in unity8.log

  [...]
  [2016-08-17:18:18:37.829] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:18:37.832] qtmir.sensor: Screen::customEvent - new orientation 
8 handled
  [2016-08-17:18:18:39.119] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:18:39.122] qtmir.sensor: Screen::customEvent - new orientation 
1 handled
  [2016-08-17:18:18:54.957] qtmir.surfaces: MirSurfaceItem(unity8-dash) - Got a 
QEvent::TouchBegin while there's still an active/unfinished touch sequence.
  [2016-08-17:18:20:42.033] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:20:42.036] qtmir.sensor: Screen::customEvent - new orientation 
8 handled
  [2016-08-17:18:20:42.849] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:20:42.853] qtmir.sensor: Screen::customEvent - new orientation 
1 handled

  

  [2016-08-17:18:20:45.100] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() unfocused
  [2016-08-17:18:20:45.217] [PERFORMANCE]: Last frame took 89 ms to render.
  [2016-08-17:18:20:45.295] [PERFORMANCE]: Last frame took 35 ms to render.
  [2016-08-17:18:20:46.037] [PERFORMANCE]: Last frame took 88 ms to render.
  [2016-08-17:18:20:46.271] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() focused
  [2016-08-17:18:20:46.298] qtmir.clipboard: D-Bus GetContents - returning 0 
bytes

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614163/+subscriptions

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


[Touch-packages] [Bug 1614166] [NEW] custome ringtone screen got frozen while "Transfer in progress" window appears

2016-08-17 Thread Victor gonzalez
Public bug reported:

Enviroment:

current build number: 170
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-08-17 14:00:59
version version: 170
version ubuntu: 20160817
version device: 20160809.0
version custom: 20160805--42-20-vivid

Product: BQ M10 FHD

Steps to reproduce:

1º Go to system settings/sound/Ringtone and select a custom ringtone
2º Transfer in progress window appears
3º Check if the window gets stucked

Current result: Transfer in progress window does not disappear, gets
stucked and you can only swipe it to close

Expected result: Device should not get stucked on transfer in progress
window

Add info: I reproduced two times 16:33 \\ 18:29. Logs attached and video

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

** Attachment added: "video+logs.zip"
   
https://bugs.launchpad.net/bugs/1614166/+attachment/4722731/+files/video+logs.zip

** Summary changed:

- custome ringtone screen got frozen while "Transfer in progress"
+ custome ringtone screen got frozen while "Transfer in progress" window appears

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614166

Title:
  custome ringtone screen got frozen while "Transfer in progress" window
  appears

Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment:

  current build number: 170
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-17 14:00:59
  version version: 170
  version ubuntu: 20160817
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Go to system settings/sound/Ringtone and select a custom ringtone
  2º Transfer in progress window appears
  3º Check if the window gets stucked

  Current result: Transfer in progress window does not disappear, gets
  stucked and you can only swipe it to close

  Expected result: Device should not get stucked on transfer in progress
  window

  Add info: I reproduced two times 16:33 \\ 18:29. Logs attached and
  video

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

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


[Touch-packages] [Bug 1614166] Re: custome ringtone screen got frozen while "Transfer in progress" window appears

2016-08-17 Thread Victor gonzalez
2nd time reproduced at 18:29

** Attachment added: "time stamp 18:29.zip"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1614166/+attachment/4722740/+files/time%20stamp%2018%3A29.zip

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614166

Title:
  custome ringtone screen got frozen while "Transfer in progress" window
  appears

Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment:

  current build number: 170
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-17 14:00:59
  version version: 170
  version ubuntu: 20160817
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Go to system settings/sound/Ringtone and select a custom ringtone
  2º Transfer in progress window appears
  3º Check if the window gets stucked

  Current result: Transfer in progress window does not disappear, gets
  stucked and you can only swipe it to close

  Expected result: Device should not get stucked on transfer in progress
  window

  Add info: I reproduced two times 16:33 \\ 18:29. Logs attached and
  video

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

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


[Touch-packages] [Bug 1613852] Re: My system is trying to assassinate me using sound

2016-08-17 Thread Shahar Or
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1613852

Title:
  My system is trying to assassinate me using sound

Status in pulseaudio package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  New

Bug description:
  Most modern video formats that I find on the interwebs, when I try to
  play them with VLC, the sound is such a loud white noise, that I
  thought maybe it is an assassination attempt on my life.

  Totem refuses to play, claiming an error loading supporting library.

  Attached is a recording of what it sounds like.

  This started happening some one month ago or so.

  Until then, I've been enjoying all kinds of videos and their audio
  without issues.

  Likely not a VLC issue, although it would be nice if players could
  protect me from such atrocities.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc-nox 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 16 21:51:33 2016
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2010-10-12 (2135 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago)

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

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


[Touch-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

2016-08-17 Thread Devid Antonio Filoni
** Changed in: band-aids-uphone
   Status: New => In Progress

** Changed in: band-aids-uphone
 Assignee: (unassigned) => Devid Antonio Filoni (d.filoni)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1364647

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1583981.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1364647/+subscriptions

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


[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20

2016-08-17 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-mate-artwork - 16.10.6

---
ubuntu-mate-artwork (16.10.6) yakkety; urgency=medium

  * Update Ubuntu MATE themes to support GTK 3.20. (LP: #1593048)

 -- Martin Wimpress   Wed, 17 Aug 2016 13:10:02 +0100

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1593048

Title:
  ubuntu-themes should support GTK 3.20

Status in arc-theme package in Ubuntu:
  Fix Released
Status in breeze-gtk package in Ubuntu:
  Fix Committed
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in mate-themes package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntukylin-theme package in Ubuntu:
  In Progress

Bug description:
  This is a tracking bug. ubuntu-themes needs to be updated to support
  GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu.

  Some initial work has been done at
  https://code.launchpad.net/~laney/ubuntu-themes/gtk320

  If you would like to help, please contact the Ubuntu Desktop Team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1593048/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Jean-Baptiste Lallement
My SIM is locked

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1614163] [NEW] unity8 stops processing touch input events after shaking the phone

2016-08-17 Thread Jean-Baptiste Lallement
Public bug reported:

current build number: 403
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

Test Case:
1. Boot the phone and unlock it
2. Shake it (I'm on apps scope by default if it matters)
3. Scroll the page up and down

Expected result
Scrolling works as expected, page goes up/down

Actual result
The dash is like frozen. A right edge swipe works and clears the problem up.

The following records are logged in unity8.log

[...]
[2016-08-17:18:18:37.829] qtmir.sensor: Screen::onOrientationReadingChanged
[2016-08-17:18:18:37.832] qtmir.sensor: Screen::customEvent - new orientation 8 
handled
[2016-08-17:18:18:39.119] qtmir.sensor: Screen::onOrientationReadingChanged
[2016-08-17:18:18:39.122] qtmir.sensor: Screen::customEvent - new orientation 1 
handled
[2016-08-17:18:18:54.957] qtmir.surfaces: MirSurfaceItem(unity8-dash) - Got a 
QEvent::TouchBegin while there's still an active/unfinished touch sequence.
[2016-08-17:18:20:42.033] qtmir.sensor: Screen::onOrientationReadingChanged
[2016-08-17:18:20:42.036] qtmir.sensor: Screen::customEvent - new orientation 8 
handled
[2016-08-17:18:20:42.849] qtmir.sensor: Screen::onOrientationReadingChanged
[2016-08-17:18:20:42.853] qtmir.sensor: Screen::customEvent - new orientation 1 
handled



[2016-08-17:18:20:45.100] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() unfocused
[2016-08-17:18:20:45.217] [PERFORMANCE]: Last frame took 89 ms to render.
[2016-08-17:18:20:45.295] [PERFORMANCE]: Last frame took 35 ms to render.
[2016-08-17:18:20:46.037] [PERFORMANCE]: Last frame took 88 ms to render.
[2016-08-17:18:20:46.271] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() focused
[2016-08-17:18:20:46.298] qtmir.clipboard: D-Bus GetContents - returning 0 bytes

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

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


** Tags: regression-proposed

** Attachment added: "unity8.log"
   https://bugs.launchpad.net/bugs/1614163/+attachment/4722729/+files/unity8.log

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614163

Title:
  unity8 stops processing touch input events after shaking the phone

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 403
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Test Case:
  1. Boot the phone and unlock it
  2. Shake it (I'm on apps scope by default if it matters)
  3. Scroll the page up and down

  Expected result
  Scrolling works as expected, page goes up/down

  Actual result
  The dash is like frozen. A right edge swipe works and clears the problem up.

  The following records are logged in unity8.log

  [...]
  [2016-08-17:18:18:37.829] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:18:37.832] qtmir.sensor: Screen::customEvent - new orientation 
8 handled
  [2016-08-17:18:18:39.119] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:18:39.122] qtmir.sensor: Screen::customEvent - new orientation 
1 handled
  [2016-08-17:18:18:54.957] qtmir.surfaces: MirSurfaceItem(unity8-dash) - Got a 
QEvent::TouchBegin while there's still an active/unfinished touch sequence.
  [2016-08-17:18:20:42.033] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:20:42.036] qtmir.sensor: Screen::customEvent - new orientation 
8 handled
  [2016-08-17:18:20:42.849] qtmir.sensor: Screen::onOrientationReadingChanged
  [2016-08-17:18:20:42.853] qtmir.sensor: Screen::customEvent - new orientation 
1 handled

  

  [2016-08-17:18:20:45.100] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() unfocused
  [2016-08-17:18:20:45.217] [PERFORMANCE]: Last frame took 89 ms to render.
  [2016-08-17:18:20:45.295] [PERFORMANCE]: Last frame took 35 ms to render.
  [2016-08-17:18:20:46.037] [PERFORMANCE]: Last frame took 88 ms to render.
  [2016-08-17:18:20:46.271] qtmir.surfaces: 
MirSurface[0x1670f10,"unity8-dash"]::updateActiveFocus() focused
  [2016-08-17:18:20:46.298] qtmir.clipboard: D-Bus GetContents - returning 0 
bytes

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614163/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Dave Morley
Potentially yes I have a locked sim as far as I am aware jibel does too
and possibly Victor

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Lukáš Tinkl
I suspect yes, so here's a tentative patch:

http://paste.ubuntu.com/23065053/

(sorry I'm on vacation with very limited connectivity)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1614158] Re: Don't get up by starting

2016-08-17 Thread modaell
thanks to help me, I don't understand a lot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614158

Title:
  Don't get up by starting

Status in xorg package in Ubuntu:
  New

Bug description:
  I have to wait lontimes till the programm start up. Sometimes i close
  cold and try again. Then I make esc and take the programm ubuntu and
  then it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 18:07:07 2016
  DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
  InstallationDate: Installed on 2015-04-29 (476 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6475b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=9d20e8cc-fbe8-4310-8a57-2061e2a6c8bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (13 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68RTU Ver. F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 180F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 47.19
  dmi.chassis.asset.tag: CNU3329NSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68RTUVer.F.46:bd10/07/2013:svnHewlett-Packard:pnHPProBook6475b:pvrA1029D1103:rvnHewlett-Packard:rn180F:rvrKBCVersion47.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6475b
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 17 18:05:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1613803] Re: indicator-power does not show brightness options

2016-08-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  indicator-power does not show brightness options

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Enviroment:

  Distributor ID: Ubuntu
  Description: Ubuntu Yakkety Yak (development branch)
  Release: 16.10
  Codename: yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Steps to reproduce:

  1º Open unity8 session
  2º Click the indicator-power in upper bar
  3º Check that no brightness options are available

  Current result: No brightness options(brightness bar & Adjust
  brightness automatically toggle) available on indicator-power running
  unity8 on a laptop

  Expected result: Brightness options should appear in indicator-power
  running unity8 on a laptop

  Add info: picture attached

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

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


[Touch-packages] [Bug 1614158] [NEW] Don't get up by starting

2016-08-17 Thread modaell
Public bug reported:

I have to wait lontimes till the programm start up. Sometimes i close
cold and try again. Then I make esc and take the programm ubuntu and
then it works better

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Aug 17 18:07:07 2016
DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
InstallationDate: Installed on 2015-04-29 (476 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ProBook 6475b
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=9d20e8cc-fbe8-4310-8a57-2061e2a6c8bf ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-04 (13 days ago)
dmi.bios.date: 10/07/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68RTU Ver. F.46
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 180F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 47.19
dmi.chassis.asset.tag: CNU3329NSY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68RTUVer.F.46:bd10/07/2013:svnHewlett-Packard:pnHPProBook6475b:pvrA1029D1103:rvnHewlett-Packard:rn180F:rvrKBCVersion47.19:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6475b
dmi.product.version: A1029D1103
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Aug 17 18:05:07 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1614158

Title:
  Don't get up by starting

Status in xorg package in Ubuntu:
  New

Bug description:
  I have to wait lontimes till the programm start up. Sometimes i close
  cold and try again. Then I make esc and take the programm ubuntu and
  then it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 18:07:07 2016
  DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
  InstallationDate: Installed on 2015-04-29 (476 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6475b
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Lukáš Tinkl
Just curious, is the difference between a working rotation (Albert) and
non-working (jibel & dave) a SIM PIN locked phone?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-08-17 Thread Jim Hodapp
@Alfonso, @Pat: that's the issue I mentioned yesterday. Sounds like
something that might be a hole in QA testing that we should bring up
with that team.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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


[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-08-17 Thread Alfonso Sanchez-Beato
@Pat, @Jim, I have sent an e-mail about this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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


[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-08-17 Thread Pat McGowan
@alfonso does that come from the device tarball? certainly works on other 
devices
anything else missing there?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Jean-Baptiste Lallement
I confirm what Dave found. My arale running latest rc-proposed rotation
stopped working after a reboot, then suddenly a moment later without any
apparent reason it was back and working as expected. It is very
reproducible and systematically doesn't work after a reboot. Although
starting telegram seems to clear it up.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-08-17 Thread Alfonso Sanchez-Beato
Hmm, it looks like the screenshot issue is happening because file

"/system/media/audio/ui/camera_click.ogg"

does not exist. So it is a different bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Albert Astals Cid
been trying to reproduce for over an hour, works every single
reboot/reflash i make :/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1594748] Re: CRYPTO_set_mem_functions() is broken

2016-08-17 Thread Dave Chiluk
This needs to be resolved in Xenial as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1594748

Title:
  CRYPTO_set_mem_functions() is broken

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
   *** 1.0.2g-1ubuntu4.1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization already calls CRYPTO_malloc() and disables it:

  #0  CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c 
"fips_drbg_lib.c",
  line=line@entry=106) at mem.c:329
  #1  0x770596df in FIPS_drbg_new (type=type@entry=0, 
flags=flags@entry=0)
  at fips_drbg_lib.c:106
  #2  0x7705aeb9 in FIPS_drbg_health_check (
  dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
  #3  0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960 
,
  type=, flags=) at fips_drbg_lib.c:94
  #4  0x76fe38f3 in RAND_init_fips () at rand_lib.c:287
  #5  0x76f26f7a in OPENSSL_init_library () at o_init.c:119
  #6  0x77de74ea in call_init (l=, argc=argc@entry=1,
  argv=argv@entry=0x7fffe5e8, env=env@entry=0x7fffe5f8) at 
dl-init.c:72
  #7  0x77de75fb in call_init (env=0x7fffe5f8, argv=0x7fffe5e8, 
argc=1,
  l=) at dl-init.c:30
  #8  _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffe5e8,
  env=0x7fffe5f8) at dl-init.c:120

  This doesn't happen in upstream OpenSSL or in Debian's OpenSSL.
  Looking at the patches, this is caused by FIPS_drbg_init() in
  openssl-1.0.2g-fips.patch:

  +if (!(dctx->xflags & DRBG_FLAG_TEST)) {
  +if (!FIPS_drbg_health_check(dctx)) {
  +FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE);
  +return 0;
  +}
  +}

  I don't want any FIPS mode enabled though, so does it really even need
  to call RAND_init_fips() then?

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

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


[Touch-packages] [Bug 1590776] Re: hide selection handle when start typing

2016-08-17 Thread Olivier Tilloy
Oxide 1.16.8 is in silo 34 and being tested now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1590776

Title:
  hide selection handle when start typing

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Released
Status in Oxide 1.16 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  we are showing the selection handle (in addition to the cursor)
  whenever entering a text field that already has text in it. For
  example, if you are replying to a Gmail message, you have an annoying
  blue selection handle blinking where you are trying to type and you
  can't turn it off. Or on a form, focusing on a field to append text
  will also show the selection handle. Or a multi line text area, adding
  a new line and typing at the beginning.

  Tested Chrome on Android and it behaves differently, and think we should do 
similar:
   1. Show the selection handle initially, but have it disappear when you press 
any key (space, character, etc.)
   2. Tapping anywhere in the field will cause handle to be shown again
   3. Also, can we put the selection handle on the bottom of the cursor instead 
of the top? This is the behavior on Chrome for Android and the rest of our 
non-html platform in Ubuntu touch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+subscriptions

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


[Touch-packages] [Bug 1593919] Re: Bluetooth not working with Meizu Pro 5

2016-08-17 Thread Alexandre Payet
*** This bug is a duplicate of bug 1590844 ***
https://bugs.launchpad.net/bugs/1590844

** This bug has been marked a duplicate of bug 1590844
   Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1593919

Title:
  Bluetooth not working with Meizu Pro 5

Status in turbo:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have problems with bluetooth. When I connect my Jabra Supreme
  headset, or connect with my car (Ford Fiesta), I only hear a lot of
  noise. This is both when I make a call, or receive an incoming call. I
  can hear music via bluetooth without problems on both headset, and in
  the car.

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

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


[Touch-packages] [Bug 1614108] Re: QStandardPaths::RuntimeLocation returns empty string under pbuilder

2016-08-17 Thread Alberto Mardegan
I investigated this bug, and it happens because QFileInfo::ownerId()
returns -2 while inspecting the runtime directory. The documentation
says:

On Windows and on systems where files do not have owners this
function returns ((uint) -2).

It's not clear though, why would this be returning -2 under pbuilder,
given that the filesystem seems to support ownership.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1614108

Title:
  QStandardPaths::RuntimeLocation returns empty string under pbuilder

Status in webapps-sprint:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The unit tests for ubuntu-system-settings-online-accounts are failing
  when run under pbuilder:

  ==
  task-0: * Start testing of UiProxyTest *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 
20160519)
  task-0: PASS : UiProxyTest::initTestCase()
  task-0: PASS : UiProxyTest::testInit()
  task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
  task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
  task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
  task-0: Loc: [tst_ui_proxy.cpp(319)]
  ==

  I've debugged the issue, and I've verified that
  QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
  returning an empty string. Although it's documented that in some
  systems that function can return NULL, it would be better if it didn't
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1614108/+subscriptions

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


[Touch-packages] [Bug 1598181] Re: No network showing from the dialer app even though phone calls are possible

2016-08-17 Thread Jim Hodapp
** Changed in: ofono (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: dialer-app (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1598181

Title:
  No network showing from the dialer app even though phone calls are
  possible

Status in Canonical System Image:
  In Progress
Status in turbo:
  New
Status in dialer-app package in Ubuntu:
  Invalid
Status in indicator-network package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Committed

Bug description:
  I noticed that I am seeing "No network" being displayed in the upper
  right hand corner of the dialer app even though I am able to make
  phone calls. This is on turbo and using the smaller SIM slot (#2) with
  T-Mobile in the US.

  Build version info:

  current build number: 116
  device name: turbo
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-07-01 09:38:31
  version version: 116
  version ubuntu: 20160701
  version device: 20160617-82a5c0d
  version custom: 20160701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+subscriptions

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


[Touch-packages] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

2016-08-17 Thread Timo Aaltonen
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1577735

Title:
  Add missing SKL/BXT PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Trusty:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Some GPU PCI-ID's are missing from libdrm (SKL, BXT) & mesa (BXT),
  these need to be added.

  [Test case]

  own such hw, run a desktop session and check that it's using native
  drivers

  [Regression potential]

  none

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

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


[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

2016-08-17 Thread Chris J Arges
Hello Talat, or anyone else affected,

Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.6 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Wily:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

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


[Touch-packages] [Bug 1614108] [NEW] QStandardPaths::RuntimeLocation returns empty string under pbuilder

2016-08-17 Thread Alberto Mardegan
Public bug reported:

The unit tests for ubuntu-system-settings-online-accounts are failing
when run under pbuilder:

==
task-0: * Start testing of UiProxyTest *
task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160519)
task-0: PASS : UiProxyTest::initTestCase()
task-0: PASS : UiProxyTest::testInit()
task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
task-0: Loc: [tst_ui_proxy.cpp(319)]
==

I've debugged the issue, and I've verified that
QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
returning an empty string. Although it's documented that in some systems
that function can return NULL, it would be better if it didn't :-)

** Affects: webapps-sprint
 Importance: High
 Assignee: Alberto Mardegan (mardy)
 Status: In Progress

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Critical
 Assignee: Alberto Mardegan (mardy)
 Status: In Progress

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided => Critical

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
   Status: New => In Progress

** Changed in: webapps-sprint
   Importance: Undecided => High

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
Milestone: None => sprint-26

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1614108

Title:
  QStandardPaths::RuntimeLocation returns empty string under pbuilder

Status in webapps-sprint:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The unit tests for ubuntu-system-settings-online-accounts are failing
  when run under pbuilder:

  ==
  task-0: * Start testing of UiProxyTest *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 
20160519)
  task-0: PASS : UiProxyTest::initTestCase()
  task-0: PASS : UiProxyTest::testInit()
  task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
  task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
  task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
  task-0: Loc: [tst_ui_proxy.cpp(319)]
  ==

  I've debugged the issue, and I've verified that
  QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
  returning an empty string. Although it's documented that in some
  systems that function can return NULL, it would be better if it didn't
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1614108/+subscriptions

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


[Touch-packages] [Bug 1380662] Re: legacy apps re-set their notification status on reboot

2016-08-17 Thread Jonas G. Drange
** Changed in: ubuntu-push (Ubuntu)
   Status: In Progress => Fix Released

** No longer affects: ubuntu-system-settings (Ubuntu)

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
   Status: In Progress => New

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
 Assignee: John Lenton (chipaca) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-ubuntu-touch-
schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1380662

Title:
  legacy apps re-set their notification status on reboot

Status in Canonical System Image:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu RTM:
  Fix Released

Bug description:
  when un-setting the notification defaults for "external drives" this
  setting is respected fine until i reboot my phone, after which the
  setting is auto-enabled again, regardless of what i chose before the
  reboot.

  the same seems to be true for the "system-settings" option in the
  notifications panel. something like gmail or facebook persits fine

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380662/+subscriptions

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


[Touch-packages] [Bug 1582803] Re: [SRU]bug report script uses invalid nm options

2016-08-17 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.2.2-0ubuntu7

---
network-manager (1.2.2-0ubuntu7) yakkety; urgency=medium

  [ Martin Pitt ]
  * debian/NetworkManager.conf: Re-Drop "dns=dnsmasq" option again, resolved
now does DNS requests on port 53 so that chrome and other NSS deniers
work.
  * debian/network-manager.postinst: Fix conf.d path with mkdir.
  * Make /run/NetworkManager/conf.d/* files override corresponding ones in
/usr/lib/. (LP: #1614043)
  * Move libgnutls-dev build dependency (which does not exist any more) to
libgnutls28-dev.

  [ Aron Xu ]
  * Fix invalid nmcli options in bug report script (LP: #1582803)

 -- Martin Pitt   Wed, 17 Aug 2016 12:55:29
+0200

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1582803

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582803/+subscriptions

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


[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

2016-08-17 Thread Jean-Baptiste Lallement
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

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

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

** Tags added: regression-proposed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Tags added: lt-blocker

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1614070

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image (403 on arale)
  2. Once in the system rotate the device 

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614070/+subscriptions

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


[Touch-packages] [Bug 1614043] Re: /run/NetworkManager/conf.d/ files do not override files in /usr/lib/NetworkManager/conf.d

2016-08-17 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.2.2-0ubuntu7

---
network-manager (1.2.2-0ubuntu7) yakkety; urgency=medium

  [ Martin Pitt ]
  * debian/NetworkManager.conf: Re-Drop "dns=dnsmasq" option again, resolved
now does DNS requests on port 53 so that chrome and other NSS deniers
work.
  * debian/network-manager.postinst: Fix conf.d path with mkdir.
  * Make /run/NetworkManager/conf.d/* files override corresponding ones in
/usr/lib/. (LP: #1614043)
  * Move libgnutls-dev build dependency (which does not exist any more) to
libgnutls28-dev.

  [ Aron Xu ]
  * Fix invalid nmcli options in bug report script (LP: #1582803)

 -- Martin Pitt   Wed, 17 Aug 2016 12:55:29
+0200

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1614043

Title:
  /run/NetworkManager/conf.d/ files do not override files in
  /usr/lib/NetworkManager/conf.d

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  On upgrades, network-manager creates an empty
  /etc/NetworkManager/conf.d/10-globally-managed-devices.conf which
  shadows the one in /usr/lib:

  $ strace -fvvs1024 /usr/sbin/NetworkManager --print-config 2>&1|grep 
10-globally
  access("/etc/NetworkManager/conf.d/10-globally-managed-devices.conf", F_OK) = 0
  open("/etc/NetworkManager/conf.d/10-globally-managed-devices.conf", O_RDONLY) 
= 5
  write(1, "# NetworkManager configuration: 
/etc/NetworkManager/NetworkManager.conf (etc: 10-globally-managed-devices.conf, 
default-wifi-powersave-on.conf)\n\n[main]\nplugins=ifupdown,keyfile,ofono\ndns=dnsmasq\n\n[ifupdown]\nmanaged=false\n\n[connection]\nwifi.powersave=3\n",
 252# NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf 
(etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf)

  However, the same does not work for /run:

  sudo rm /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
  sudo touch /run/NetworkManager/conf.d/10-globally-managed-devices.conf

  $ strace -fvvs1024 /usr/sbin/NetworkManager --print-config 2>&1|grep 
10-globally
  access("/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf", 
F_OK) = 0
  open("/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf", 
O_RDONLY) = 5
  access("/var/run/NetworkManager/conf.d/10-globally-managed-devices.conf", 
F_OK) = 0
  open("/var/run/NetworkManager/conf.d/10-globally-managed-devices.conf", 
O_RDONLY) = 5
  write(1, "# NetworkManager configuration: 
/etc/NetworkManager/NetworkManager.conf (lib: 10-globally-managed-devices.conf) 
(etc: 
default-wifi-powersave-on.conf)\n\n[main]\nplugins=ifupdown,keyfile,ofono\ndns=dnsmasq\n\n[keyfile]\nunmanaged-devices=*,except:type:wifi,except:type:wwan\n\n[ifupdown]\nmanaged=false\n\n[connection]\nwifi.powersave=3\n",
 323# NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf 
(lib: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)

  Thus "unmanaged-devices" is still excluding eveyrthing but wifi/wwan,
  i. e. per the original /usr/lib/ config.

  network-manager version 1.2.2-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1614043/+subscriptions

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


[Touch-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-17 Thread Łukasz Zemczak
** Branch linked: lp:~sil2100/ubuntu-touch-
session/fix_bootability_on_xenial

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
   Status: New => Invalid

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

** Changed in: canonical-devices-system-image
 Assignee: Michał Sawicz (saviq) => Łukasz Zemczak (sil2100)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-ubuntu-touch-
schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1604421

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  In Progress
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Invalid
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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


[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager

2016-08-17 Thread Michael Sheldon
I'm taking a look at the crasher mentioned in this now, then will review
the other items to see if anything else is still outstanding

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1488425

Title:
  [MIR] ubuntu-download-manager

Status in Canonical System Image:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  webbrowser-app (in main) currently has a non-explicit runtime dependency on 
ubuntu-download-manager, which is in universe.
  This has been working until now because the desktop version of the app 
doesn’t make use of the QML API for the download manager, only the version for 
touch devices does (and ubuntu-download-manager is part of the touch seed).
  With convergence in mind, the desktop version needs to start using that QML 
API, so the runtime dependency needs to be made explicit. Hence the need for 
ubuntu-download-manager to be included in main.
  It is likely that other applications will have the same kind of requirements 
in the near future too.

  ubuntu-download-manager is actively being developed and maintained,
  upstream tracks their bugs at
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/.

  All its build and runtime dependencies are already in main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488425/+subscriptions

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


[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

2016-08-17 Thread Chris J Arges
Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.67-1ubuntu0.16.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libdrm (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1600124

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

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

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


[Touch-packages] [Bug 1614100] [NEW] Upload dialog in Firefox does not have an address bar any more for entering pathes

2016-08-17 Thread Karl Kastner
Public bug reported:

Since recently, the upload menu in Firefox allows only for browsing.
Thus, instead of simply entering the directory on the keyboard or
copying the pwd from the command line, I have to click myself through
the directory tree like a monkey.

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

** Package changed: poppler (Ubuntu) => firefox (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1614100

Title:
  Upload dialog in Firefox does not have an address bar any more for
  entering pathes

Status in firefox package in Ubuntu:
  New

Bug description:
  Since recently, the upload menu in Firefox allows only for browsing.
  Thus, instead of simply entering the directory on the keyboard or
  copying the pwd from the command line, I have to click myself through
  the directory tree like a monkey.

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

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


[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

2016-08-17 Thread Louis Bouchard
Hello,

Looking at the history for this case, the SRU got rejected by pitti
(Comment #29) because of a v-failed on the fix for LP: #1568485 which is
also included in this SRU.

Since then, LP: #1568485 has been verified and is now fix-released.
There is no longer any reason to hold on the trusty SRU for this bug.
The delta between this SRU and trusty-updates is now only the patch that
resolves this issue.

There should no longer be any roadblock for this SRU so I am re-
uploading the 12.6 package. I am also unsubscribing ubuntu-sponsors

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

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


[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

2016-08-17 Thread Chris J Arges
Hello Kyle, or anyone else affected,

Accepted sudo into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: sudo (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1595558

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-08-17 Thread Philippe Vaucher
** Package changed: ubuntu => bash (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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


[Touch-packages] [Bug 1566205] Re: Flaky test tst_mouseFilterTest::testCase_forwardedDblClickToTransparentMouseArea

2016-08-17 Thread Tim Peeters
** Tags added: flaky-test

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1566205

Title:
  Flaky test
  tst_mouseFilterTest::testCase_forwardedDblClickToTransparentMouseArea

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-stable/612/console

  --
  tst_mousefilters: FAIL!  : 
tst_mouseFilterTest::testCase_forwardedDblClickToTransparentMouseArea() 
Compared values are not the same
  tst_mousefilters:Actual   (doubleClicked.count()): 0
  tst_mousefilters:Expected (1): 1
  tst_mousefilters:Loc: [tst_mousefilterstest.cpp(788)]
  --

  The MP in question adds only a non-used bzr commit hook, so the test
  is flaky.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1566205/+subscriptions

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


[Touch-packages] [Bug 1506612] Re: pdfimages extracts black rectangles instead of the images

2016-08-17 Thread Karl Kastner
I can reproduce this for certain files in xenial. Most of these files
are pdf files that were converted from ps format.

** Attachment added: "77-321.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1506612/+attachment/4722623/+files/77-321.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1506612

Title:
  pdfimages extracts black rectangles instead of the images

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images,
  two of which are black rectangles.

  If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that
  looks correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: poppler-utils 0.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 15 12:36:10 2015
  InstallationDate: Installed on 2013-05-02 (896 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: poppler
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1506612] Re: pdfimages extracts black rectangles instead of the images

2016-08-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1506612

Title:
  pdfimages extracts black rectangles instead of the images

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images,
  two of which are black rectangles.

  If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that
  looks correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: poppler-utils 0.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 15 12:36:10 2015
  InstallationDate: Installed on 2013-05-02 (896 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: poppler
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1541386] Re: Failing tests with GLES on i386/amd64 in tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml

2016-08-17 Thread Tim Peeters
** Tags added: flaky-test

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1541386

Title:
  Failing tests with GLES on i386/amd64 in
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  We have a failing unit test with gles on i386 and amd64:

  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Started with PID: 18869
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: * Start testing of 
components *
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Config: Using QtTest library 
5.4.1, Qt 5.4.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by 
GCC 4.9.2)
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::initTestCase()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: XFAIL  : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel() 
Array changes are not detected by repeaters
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(176)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: XFAIL  : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel() 
Array changes are not detected by repeaters
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(178)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: FAIL!  : 
components::TabsWithRepeaterDeprecatedToolbar::test_tabOrder_bug1253804() Tab 
titles after shuffling don't match for index 0
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Actual   (): tab 0
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Expected (): tab 3
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(138)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_twinRepeaters()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_twoRepeaters()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::cleanupTestCase()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Totals: 6 passed, 1 failed, 0 
skipped, 0 blacklisted
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: * Finished testing of 
components *
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Exited with status 256
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Shutting down
  DBus daemon: Shutdown
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml exited with 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1541386/+subscriptions

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


[Touch-packages] [Bug 1541386] Re: Failing tests with GLES on i386/amd64 in tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml

2016-08-17 Thread Timo Jyrinki
Also:

FAIL!  :
components::TabsWithRepeaterNewHeader::test_tabOrder_bug1253804() Tab
titles after shuffling don't match for index 0

https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-i386
-gles-stable/1004/console

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1541386

Title:
  Failing tests with GLES on i386/amd64 in
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  We have a failing unit test with gles on i386 and amd64:

  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Started with PID: 18869
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: * Start testing of 
components *
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Config: Using QtTest library 
5.4.1, Qt 5.4.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by 
GCC 4.9.2)
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::initTestCase()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: XFAIL  : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel() 
Array changes are not detected by repeaters
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(176)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: XFAIL  : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel() 
Array changes are not detected by repeaters
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(178)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_repeaterTabs_arrayAsModel()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: FAIL!  : 
components::TabsWithRepeaterDeprecatedToolbar::test_tabOrder_bug1253804() Tab 
titles after shuffling don't match for index 0
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Actual   (): tab 0
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Expected (): tab 3
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml:Loc: 
[/«BUILDDIR»/ubuntu-ui-toolkit-gles-1.3.1829+15.04.20160203/tests/unit_x11/tst_components/tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml(138)]
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_twinRepeaters()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::test_twoRepeaters()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: PASS   : 
components::TabsWithRepeaterDeprecatedToolbar::cleanupTestCase()
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Totals: 6 passed, 1 failed, 0 
skipped, 0 blacklisted
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: * Finished testing of 
components *
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Exited with status 256
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml: Shutting down
  DBus daemon: Shutdown
  tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml exited with 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1541386/+subscriptions

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


[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20

2016-08-17 Thread Martin Wimpress
** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1593048

Title:
  ubuntu-themes should support GTK 3.20

Status in arc-theme package in Ubuntu:
  Fix Released
Status in breeze-gtk package in Ubuntu:
  Fix Committed
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in mate-themes package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntukylin-theme package in Ubuntu:
  In Progress

Bug description:
  This is a tracking bug. ubuntu-themes needs to be updated to support
  GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu.

  Some initial work has been done at
  https://code.launchpad.net/~laney/ubuntu-themes/gtk320

  If you would like to help, please contact the Ubuntu Desktop Team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1593048/+subscriptions

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


[Touch-packages] [Bug 1614080] [NEW] PATH contains dot when PATH is unset before running bash

2016-08-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
adds '.' to PATH:

philippe@pv-desktop:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
philippe@pv-desktop:~$ unset PATH
philippe@pv-desktop:~$ /bin/bash
philippe@pv-desktop:~$ echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

Even when testing in a virtual machine / docker, and erasing
/root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
still happens.

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


** Tags: bot-comment
-- 
PATH contains dot when PATH is unset before running bash
https://bugs.launchpad.net/bugs/1614080
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bash in Ubuntu.

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


[Touch-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.

2016-08-17 Thread Launchpad Bug Tracker
This bug was fixed in the package frame -
2.5.0daily13.06.05+16.04.20160809-0ubuntu1

---
frame (2.5.0daily13.06.05+16.04.20160809-0ubuntu1) xenial; urgency=medium

  * device: don't use asserts to get properties on failures, to avoid
crashes (LP: #1350523)

 -- Marco Trevisan (Treviño)   Tue, 09 Aug 2016 19:14:39
+

** Changed in: frame (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to frame in Ubuntu.
https://bugs.launchpad.net/bugs/1350523

Title:
  compiz assert failure: compiz: device.cpp:147: float
  frame_device_get_window_resolution_x(UFDevice): Assertion `status ==
  UFStatusSuccess' failed.

Status in frame:
  In Progress
Status in compiz package in Ubuntu:
  Won't Fix
Status in frame package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Invalid
Status in frame source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Unity might crash on systems with touch screen or multi-gesture
  supporting touchpads.

  [Test case]

  The crash is pretty random, it happens in some cases where unity is
  locked and after a suspension. Without having to touch any input.

  [Regression Potential]

  Regression potential: fix is very safe. We're just removing asserts in
  code, returning safe values and printing errors instead.

  
  Not sure if the cause is running autopilot tests.

  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  .tmp.unity.support.test.1:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  AssertionMessage: compiz: device.cpp:147: float 
frame_device_get_window_resolution_x(UFDevice): Assertion `status == 
UFStatusSuccess' failed.
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jul 30 21:46:07 2014
  DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2014-02-13 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  MachineType: System manufacturer System Product Name
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7
  Signal: 6SourcePackage: compiz
  StacktraceTop:
   __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == 
UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", 
line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float 
frame_device_get_window_resolution_x(UFDevice)") at assert.c:92
   __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", 
file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float 
frame_device_get_window_resolution_x(UFDevice)") at assert.c:101
   frame_device_get_window_resolution_x () from 
/usr/lib/x86_64-linux-gnu/libframe.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
  Title: compiz assert failure: compiz: device.cpp:147: float 
frame_device_get_window_resolution_x(UFDevice): Assertion `status == 
UFStatusSuccess' failed.
  UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  

  1   2   >