date:20170807

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Expired

Bug description:
  I was doing a normal upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 10:14:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-14 (110 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 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/openssh/+bug/1695900/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2017-08-07 Thread lizehao

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => lizehao (lllwonder)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1709225] [NEW] gtk test regressions with pango 1.40.8

2017-08-07 Thread Jeremy Bicha

Public bug reported:

See the upstream bug.

Ubuntu's gtk+3 fails to build from source because of test failures.

It looks like pango 1.40.8 is to blame.

Setting block-proposed as a pointer to explain the libgtk2-perl
autopkgtest is failing with pango 1.40.8

** Affects: pango
 Importance: Unknown
 Status: Unknown

** Affects: pango1.0 (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: artful block-proposed ftbfs

** Bug watch added: GNOME Bug Tracker #785978
   https://bugzilla.gnome.org/show_bug.cgi?id=785978

** Also affects: pango via
   https://bugzilla.gnome.org/show_bug.cgi?id=785978
   Importance: Unknown
   Status: Unknown

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

Title:
  gtk test regressions with pango 1.40.8

Status in Pango:
  Unknown
Status in pango1.0 package in Ubuntu:
  Confirmed

Bug description:
  See the upstream bug.

  Ubuntu's gtk+3 fails to build from source because of test failures.

  It looks like pango 1.40.8 is to blame.

  Setting block-proposed as a pointer to explain the libgtk2-perl
  autopkgtest is failing with pango 1.40.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1709225/+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 1709221] [NEW] package base-files 9.6ubuntu13 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

2017-08-07 Thread Iordan

Public bug reported:

Não consigo instalar e nem atualizar meu sistema UBUNTU

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: base-files 9.6ubuntu13
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Aug  7 23:07:27 2017
DpkgTerminalLog:
 dpkg: erro ao processar o pacote base-files (--configure):
  O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: base-files
Title: package base-files 9.6ubuntu13 failed to install/upgrade: O pacote está 
num mau estado de inconsistência; deve  reinstala-lo antes de tentar 
configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package base-files 9.6ubuntu13 failed to install/upgrade: O pacote
  está num mau estado de inconsistência; deve  reinstala-lo antes de
  tentar configura-lo.

Status in base-files package in Ubuntu:
  New

Bug description:
  Não consigo instalar e nem atualizar meu sistema UBUNTU

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug  7 23:07:27 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote base-files (--configure):
O pacote está num mau estado de inconsistência; deve
reinstala-lo antes de tentar configura-lo.
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: base-files
  Title: package base-files 9.6ubuntu13 failed to install/upgrade: O pacote 
está num mau estado de inconsistência; deve  reinstala-lo antes de tentar 
configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1709221/+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 1694628] Re: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to install/upgrade: package zlib1g:amd64 cannot be configured because zlib1g:i386 is not ready (current status 'h

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to
  install/upgrade: package zlib1g:amd64 cannot be configured because
  zlib1g:i386 is not ready (current status 'half-installed')

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  The error occured whlile installing the epson xp205 printer driver on
  ubuntu mate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May 31 10:10:22 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:zlib1g:amd64:1:1.2.8.dfsg-2ubuntu4.1
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package zlib1g:amd64 (--configure):
package zlib1g:amd64 cannot be configured because zlib1g:i386 is not ready 
(current status 'half-installed')
  ErrorMessage: package zlib1g:amd64 cannot be configured because zlib1g:i386 
is not ready (current status 'half-installed')
  InstallationDate: Installed on 2017-05-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to 
install/upgrade: package zlib1g:amd64 cannot be configured because zlib1g:i386 
is not ready (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1694628/+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 1709055] Re: Drop support for Android (Ubuntu Touch patches)

I don't know anything about the details. I just kept what appeared to be
required by snappy support (wouldn't build without it). Also, this patch
is what I have been testing for the past week, so if there's more that
can be removed I suggest we do that separately. To change the patch now
would impact its theoretical maturity and set us back a week.

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

Title:
  Drop support for Android (Ubuntu Touch patches)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Drop support for Android (Ubuntu Touch patches)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+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 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1709163

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

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

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

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

** Changed in: mir
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2017-08-07 Thread Daniel Axtens

Hi Marzog,

What commit has been committed to Linux? I cannot find it.

Regards,
Daniel

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2017-08-07 Thread Marzog

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

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-07 Thread Chris Halse Rogers

Already have done: https://github.com/karelzak/util-linux/pull/492 ☺

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1708635/+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 1709207] [NEW] package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente

2017-08-07 Thread FranciscoLima

Public bug reported:

Simple scan application. Error installing driver

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.24 5.24.1-7ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Aug  7 20:35:44 2017
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.24:i386
InstallationDate: Installed on 2017-07-30 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: perl
Title: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.24:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a
  tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Simple scan application. Error installing driver

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.24 5.24.1-7ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Aug  7 20:35:44 2017
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.24/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.24:i386
  InstallationDate: Installed on 2017-07-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-7ubuntu1 failed to install/upgrade: a 
tentar sobreescrever '/usr/share/doc/libperl5.24/changelog.Debian.gz' 
partilhado, que é diferente de outras instâncias do pacote libperl5.24:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1709207/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-08-07 Thread FFab

Upstream kernel test - kernel 4.13-rc4

Installation updated 2017-08-07.
Results just like 4.13-rc3 test.

** Tags removed: kernel-bug-exists-upstream-4.13-rc3
** Tags added: kernel-bug-exists-upstream-4.13-rc4

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  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.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+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 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts

2017-08-07 Thread Michael Terry

Right, good suggestion.  That reveals the error:

GoaBackend-WARNING **: Did not find emails.account in JSON data

I signed up for a Live account using my own email, not a MS one.  So
maybe that's causing an issue somewhere?

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

Title:
  Can't add a Microsoft account to GNOME Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  In artful:

  1) Open Settings->Online Accounts
  2) Click on "Microsoft" under "Add an account"
  3) See an authorization window pop up, enter my user/password for Microsoft 
Live
  4) Click next, see it ask whether it's OK to give GNOME various permissions
  5) Click yes, see the window disappear

  But at this point, no Microsoft account appears in the active-accounts
  section.  It just seems to have closed the window and done nothing.

  Is there a way to get better logging for this and try again?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-online-accounts 3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  6 10:03:55 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (1669 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1709175] Re: remove init.d and upstart files

2017-08-07 Thread Seth Arnold

Please note
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1503762 -- it's
not obvious what the systemd unit file for apparmor ought to look like.

Thanks

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

Title:
  remove init.d and upstart files

Status in apparmor package in Ubuntu:
  New

Bug description:
  remove init.d and upstart files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1709175/+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 1700964] Re: package python-psycopg2 2.6.1-1build2 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1

2017-08-07 Thread Scott Kitterman

** Package changed: psycopg2 (Ubuntu) => python-defaults (Ubuntu)

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

Title:
  package python-psycopg2 2.6.1-1build2 failed to install/upgrade: sub-
  processo script pre-removal instalado retornou estado de saída de erro
  1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  Updated from python version 2.7 to 3.5 and removed the former from the
  alternatives list.  It broke python-psycopg2 package so that I could
  not either finish installation or remove the package, and I got
  warnings every time I installed other packages through apt or updated
  apt sources, and various crashes reports on startup.

  Adding python 2.7 to alternatives again, with priority set to  2 ($
  sudo update-alternatives --install /usr/bin/python python
  /usr/bin/python2.7 2) restored normal behavior, but it took me a bit
  to understand what to do.

  Maybe there could be a better warning or error message that pointed
  the user to the right direction.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-psycopg2 2.6.1-1build2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 27 15:46:57 2017
  ErrorMessage: sub-processo script pre-removal instalado retornou estado de 
saída de erro 1
  InstallationDate: Installed on 2016-12-06 (203 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: psycopg2
  Title: package python-psycopg2 2.6.1-1build2 failed to install/upgrade: 
sub-processo script pre-removal instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1700964/+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 1709175] [NEW] remove init.d and upstart files

2017-08-07 Thread Dimitri John Ledkov

Public bug reported:

remove init.d and upstart files

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


** Tags: block-proposed

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

Title:
  remove init.d and upstart files

Status in apparmor package in Ubuntu:
  New

Bug description:
  remove init.d and upstart files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1709175/+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 1700964] [NEW] package python-psycopg2 2.6.1-1build2 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1

You have been subscribed to a public bug:

Updated from python version 2.7 to 3.5 and removed the former from the
alternatives list.  It broke python-psycopg2 package so that I could not
either finish installation or remove the package, and I got warnings
every time I installed other packages through apt or updated apt
sources, and various crashes reports on startup.

Adding python 2.7 to alternatives again, with priority set to  2 ($ sudo
update-alternatives --install /usr/bin/python python /usr/bin/python2.7
2) restored normal behavior, but it took me a bit to understand what to
do.

Maybe there could be a better warning or error message that pointed the
user to the right direction.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-psycopg2 2.6.1-1build2
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 27 15:46:57 2017
ErrorMessage: sub-processo script pre-removal instalado retornou estado de 
saída de erro 1
InstallationDate: Installed on 2016-12-06 (203 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: psycopg2
Title: package python-psycopg2 2.6.1-1build2 failed to install/upgrade: 
sub-processo script pre-removal instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial
-- 
package python-psycopg2 2.6.1-1build2 failed to install/upgrade: sub-processo 
script pre-removal instalado retornou estado de saída de erro 1
https://bugs.launchpad.net/bugs/1700964
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to python-defaults 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 1645631] Re: Sending files fails because obex not loaded

This bug was fixed in the package bluez - 5.45-0ubuntu4

---
bluez (5.45-0ubuntu4) artful; urgency=medium

  * Drop deprecated rfcomm.conf and upstart config. (LP: #1674680)

 -- Dariusz Gadomski   Mon, 07 Aug 2017
13:29:41 +0200

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Sending files fails because obex not loaded

Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  If I run bluetooth-sendto from command line and try to send the file,
  it quits after selecting the target device with following command line
  output:

  "Acquiring proxy failed: Error calling StartServiceByName for
  org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit
  dbus-org.bluez.obex.service not found."

  After I run "systemctl --user start obex", it proceeds to send the
  file. Even then it for some reason gets stuck, but I do not know what
  causes it and it is probably a different problem.

  This system is upgraded from xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-bluetooth 3.20.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Nov 29 11:04:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (77 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=fi
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1708375] Re: Add support for purple-telegram (telepathy-haze)

2017-08-07 Thread Khurshid Alam

Updated

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Status: New => Confirmed

** Patch added: "telepathy-purple.patch"
   
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/4928529/+files/telepathy-purple.patch

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+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 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

This bug was fixed in the package bluez - 5.45-0ubuntu4

---
bluez (5.45-0ubuntu4) artful; urgency=medium

  * Drop deprecated rfcomm.conf and upstart config. (LP: #1674680)

 -- Dariusz Gadomski   Mon, 07 Aug 2017
13:29:41 +0200

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

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  Fix Released
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

2017-08-07 Thread kenjo

** Attachment added: "fail"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+attachment/4928526/+files/ps_f1.txt

** Description changed:

So if I have sound output selected to be the intel sound on the
mainboard and turn off one of my two displays the audio out is changed
to HDMI. YES OFF it's not a typo.

The Display I turn off is connected to displayport and do not even have
HDMI. The audio is switched over to the still active display.

If I then turn the display back it's still hdmi. If I then turn off the
display that has HDMI out connected. the audio is still connected to
- that display. since its actually of I hear no sound but pulseaudio still
- connect to it.
+ that display. since its actually off I hear no sound but pulseaudio
+ still connect to it.

I have to manually open the GUI tool and change back to the correct
- ouput when the display is turned of or when the display is blanked. or
+ output when the display is turned of or when the display is blanked. or
suspend/resume.

- I attache the output of "pacmd list-cards && pacmd list-sinks"
+ I attache the output of "pacmd list-cards && pacmd list-sinks"
ok -> ps_w1.txt
fail -> ps_f1.txt

** Description changed:

So if I have sound output selected to be the intel sound on the
mainboard and turn off one of my two displays the audio out is changed
to HDMI. YES OFF it's not a typo.

The Display I turn off is connected to displayport and do not even have
HDMI. The audio is switched over to the still active display.

If I then turn the display back it's still hdmi. If I then turn off the
display that has HDMI out connected. the audio is still connected to
that display. since its actually off I hear no sound but pulseaudio
still connect to it.

I have to manually open the GUI tool and change back to the correct
- output when the display is turned of or when the display is blanked. or
+ output when the display is turned off or when the display is blanked. or
suspend/resume.

I attache the output of "pacmd list-cards && pacmd list-sinks"
ok -> ps_w1.txt
fail -> ps_f1.txt

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

Title:
default output changes from intel builtin to hdmi when display is
turned off. yes off not on

Status in pulseaudio package in Ubuntu:
New

Bug description:
So if I have sound output selected to be the intel sound on the
mainboard and turn off one of my two displays the audio out is changed
to HDMI. YES OFF it's not a typo.

The Display I turn off is connected to displayport and do not even
have HDMI. The audio is switched over to the still active display.

If I then turn the display back it's still hdmi. If I then turn off
the display that has HDMI out connected. the audio is still connected
to that display. since its actually off I hear no sound but pulseaudio
still connect to it.

I have to manually open the GUI tool and change back to the correct
output when the display is turned off or when the display is blanked.
or suspend/resume.

I attache the output of "pacmd list-cards && pacmd list-sinks"
ok -> ps_w1.txt
fail -> ps_f1.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1709135] Re: add bond primary parameter

2017-08-07 Thread Mathieu Trudel-Lapierre

Sounds like we'd need to add a key under parameters: for the bond
device, as per the original description (but the device needs to be
listed in 'interfaces', and exist in the list of interfaces defined in
netplan:

ethernets:
  version: 2
  ethernets:
eth0:
  match:
driver: virtio
ens4:
  match:
driver: e1000
  bonds:
bond0:
  interfaces: [ eth0, ens4 ]
  parameters:
mode: active-backup
mii-monitor-interval: 100
primary: ens4
  dhcp4: true

This will require backporting the feature from systemd to the releases
where we need this (to xenial).

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

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

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

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

** Also affects: nplan (Ubuntu Artful)
   Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: Triaged

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

** Also affects: nplan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: nplan (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: nplan (Ubuntu Zesty)
   Status: New => Triaged

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

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

** Changed in: nplan (Ubuntu Zesty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: nplan (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  Fix Released
Status in nplan source package in Artful:
  Triaged
Status in systemd source package in Artful:
  Fix Released

Bug description:
  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml 
  ethernets:
version: 2
ethernets:
  eth0:
match:
  driver: virtio
  ens4:
match:
  driver: e1000
bonds:
  bond0:
parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
dhcp4: true

  % ./generate -r `pwd`/target 
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+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 1709163] [NEW] default output changes from intel builtin to hdmi when display is turned off. yes off not on

2017-08-07 Thread kenjo

Public bug reported:

So if I have sound output selected to be the intel sound on the
mainboard and turn off one of my two displays the audio out is changed
to HDMI. YES OFF it's not a typo.

The Display I turn off is connected to displayport and do not even have
HDMI. The audio is switched over to the still active display.

If I then turn the display back it's still hdmi. If I then turn off the
display that has HDMI out connected. the audio is still connected to
that display. since its actually off I hear no sound but pulseaudio
still connect to it.

I have to manually open the GUI tool and change back to the correct
output when the display is turned off or when the display is blanked. or
suspend/resume.

I attache the output of "pacmd list-cards  && pacmd list-sinks"
ok   -> ps_w1.txt
fail -> ps_f1.txt

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

** Patch added: "working aoudio"
   https://bugs.launchpad.net/bugs/1709163/+attachment/4928525/+files/ps_w1.txt

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

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

2017-08-07 Thread Jamie Strandboge

@intrigeri - you're right. I'll fix this in the citrain branch and in
2.11.0-2ubuntu14.

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Released
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1598759/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-08-07 Thread Eugene Jones

I can't believe all it took was to do:

sudo apt purge dbus-user-session

Thanks to whoever discovered this!

Sidenote: My Yandex browser now launches instantaneously rather than
taking atleast half a minute to open up.

This fix was definitely a good find

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1706848] Re: This error message appears at startup

2017-08-07 Thread Anoop Naik

I get the same error some times while shutting down. And sometimes
shutdown hangs. This is happening very often these days.

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

Title:
  This error message appears at startup

Status in xorg package in Ubuntu:
  New

Bug description:
  [   2.235485] nouveau :01:00.0: bus: MMIO read of 
  FAULT at 3e6684 [IBUS]

  Even after the xorg update the error continues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Thu Jul 27 00:59:38 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753]
  InstallationDate: Installed on 2017-07-21 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jul 27 00:56:08 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 8
   inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1706848/+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 1693226] Re: Break the conflicts with click the optparser

2017-08-07 Thread the_dark_knight

I get the following error for sudo apt-get -f install

Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ...
Traceback (most recent call last):
  File "/usr/bin/click", line 37, in 
import click
ImportError: No module named 'click'
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/bin/click", line 37, in 
import click
ImportError: No module named 'click'
dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Job for click-system-hooks.service failed because the control process exited 
with error code.
See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
click-system-hooks.service couldn't start.
Errors were encountered while processing:
 /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I installed python click with sudo pip3 install click and tried running
sudo apt-get -f install

Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ...
Traceback (most recent call last):
  File "/usr/bin/click", line 55, in 
from click import commands
ImportError: cannot import name 'commands'
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/bin/click", line 55, in 
from click import commands
ImportError: cannot import name 'commands'
dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Job for click-system-hooks.service failed because the control process exited 
with error code.
See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
click-system-hooks.service couldn't start.
Errors were encountered while processing:
 /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1707833] Re: erros de atualização e erros internos

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

Title:
  erros de atualização e erros  internos

Status in xorg package in Ubuntu:
  New

Bug description:
  Falha ao atualizar o Sistema pela Internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76
  Uname: Linux 4.4.0-88-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Tue Aug  1 01:16:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-07-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-88-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul 31 20:58:11 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1707833/+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 1708916] Re: Gong show...

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

Title:
  Gong show...

Status in xorg package in Ubuntu:
  New

Bug description:
  I am exhausted and just can't do it anymore...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Sun Aug  6 04:01:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2017-08-02 (4 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K54C
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54C.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54C
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54C.207:bd04/18/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54C
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Aug  6 02:37:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708916/+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 1708915] Re: Gong show...

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

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

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

Title:
  Gong show...

Status in xorg package in Ubuntu:
  New

Bug description:
  I am exhausted and just can't do it anymore...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Sun Aug  6 04:01:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2017-08-02 (4 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K54C
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54C.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54C
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54C.207:bd04/18/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54C
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Aug  6 02:37:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708915/+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 1708983] Re: frozen screen

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

Title:
  frozen screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Random freezing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Sun Aug  6 16:51:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[1028:0667]
  InstallationDate: Installed on 2017-08-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0c45:64ad Microdia 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3531
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=53de4d80-8cca-40f7-a458-af49bc522162 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 00FTTX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/30/2014:svnDellInc.:pnInspiron3531:pvrA03:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron 3531
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708983/+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 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

2017-08-07 Thread Dave Chiluk

Sponsored artful.

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1708882] Re: package libfftw3-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/info/fftw3.info.gz', which is also in package imgcnv 1.66

2017-08-07 Thread Hans Joachim Desserud

** Tags added: package-conflict

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

Title:
  package libfftw3-doc (not installed) failed to install/upgrade: trying
  to overwrite '/usr/share/info/fftw3.info.gz', which is also in package
  imgcnv 1.66

Status in fftw3 package in Ubuntu:
  New

Bug description:
  apparent conflict with package 'imgcnv' - no idea who's right.

  $ sudo apt install libfftw3-3 libfftw3-dev libfftw3-doc
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libfftw3-3 is already the newest version (3.3.5-3).
  libfftw3-3 set to manually installed.
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.10.0-26 linux-headers-4.10.0-26-generic
linux-image-4.10.0-26-generic linux-image-extra-4.10.0-26-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libfftw3-bin libfftw3-quad3
  The following NEW packages will be installed:
libfftw3-bin libfftw3-dev libfftw3-doc libfftw3-quad3
  0 upgraded, 4 newly installed, 0 to remove and 14 not upgraded.
  Need to get 2,877 kB of archives.
  After this operation, 19.3 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 libfftw3-quad3 
amd64 3.3.5-3 [549 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 libfftw3-bin amd64 
3.3.5-3 [31.8 kB]
  Get:3 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 libfftw3-dev amd64 
3.3.5-3 [2,123 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 libfftw3-doc all 
3.3.5-3 [173 kB]
  Fetched 2,877 kB in 1s (2,326 kB/s)   
  Selecting previously unselected package libfftw3-quad3:amd64.
  (Reading database ... 423617 files and directories currently installed.)
  Preparing to unpack .../libfftw3-quad3_3.3.5-3_amd64.deb ...
  Unpacking libfftw3-quad3:amd64 (3.3.5-3) ...
  Selecting previously unselected package libfftw3-bin.
  Preparing to unpack .../libfftw3-bin_3.3.5-3_amd64.deb ...
  Unpacking libfftw3-bin (3.3.5-3) ...
  Selecting previously unselected package libfftw3-dev:amd64.
  Preparing to unpack .../libfftw3-dev_3.3.5-3_amd64.deb ...
  Unpacking libfftw3-dev:amd64 (3.3.5-3) ...
  Selecting previously unselected package libfftw3-doc.
  Preparing to unpack .../libfftw3-doc_3.3.5-3_all.deb ...
  Unpacking libfftw3-doc (3.3.5-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfftw3-doc_3.3.5-3_all.deb (--unpack):
   trying to overwrite '/usr/share/info/fftw3.info.gz', which is also in 
package imgcnv 1.66
  Errors were encountered while processing:
   /var/cache/apt/archives/libfftw3-doc_3.3.5-3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libfftw3-doc (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libfftw3-quad3:amd64: Install
   libfftw3-bin:amd64: Install
   libfftw3-dev:amd64: Install
   libfftw3-doc:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Aug  5 16:57:23 2017
  ErrorMessage: trying to overwrite '/usr/share/info/fftw3.info.gz', which is 
also in package imgcnv 1.66
  InstallationDate: Installed on 2017-04-08 (119 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: fftw3
  Title: package libfftw3-doc (not installed) failed to install/upgrade: trying 
to overwrite '/usr/share/info/fftw3.info.gz', which is also in package imgcnv 
1.66
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (103 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1708882/+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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

Two more fails today:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/4876/consoleFull

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/4879/consoleFull

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1132212] Re: [gnome-fallback] No icon for menu "Kids"

2017-08-07 Thread Joshua Bayfield

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

** This bug has been marked a duplicate of bug 508020
   Icon for games > kids missing

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

Title:
  [gnome-fallback] No icon for menu "Kids"

Status in edubuntu-artwork package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I have installed on VirtualBox, Edubuntu amd64
  (eefd0c1c57a31a1f91ebe159b0a2a1c4 *raring-dvd-amd64.iso 20130223.1).

  On the session "gnome-fallback", menu "Applications">"Games">"Kids":
  No icon for menu "Kids".

  Thanks.

  Gianni

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: edubuntu-artwork 13.02.2
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Sat Feb 23 19:50:36 2013
  InstallationDate: Installed on 2013-02-23 (0 days ago)
  InstallationMedia: Edubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: edubuntu-artwork
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/1132212/+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 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts

2017-08-07 Thread Joshua Bayfield

I cannot reproduce this bug with gnome-online-accounts 3.24.1-0ubuntu1
on artful, which is the same version that you are running.

I think by running "G_MESSAGES_DEBUG=all gnome-control-center" and then
trying to add your account as usual may print any log messages of any
use to the terminal.

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

Title:
  Can't add a Microsoft account to GNOME Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  In artful:

  1) Open Settings->Online Accounts
  2) Click on "Microsoft" under "Add an account"
  3) See an authorization window pop up, enter my user/password for Microsoft 
Live
  4) Click next, see it ask whether it's OK to give GNOME various permissions
  5) Click yes, see the window disappear

  But at this point, no Microsoft account appears in the active-accounts
  section.  It just seems to have closed the window and done nothing.

  Is there a way to get better logging for this and try again?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-online-accounts 3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  6 10:03:55 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (1669 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1686344] Update Released

2017-08-07 Thread Łukasz Zemczak

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1686344] Re: Mesa 17.0.x stable release

This bug was fixed in the package mesa - 17.0.7-0ubuntu0.17.04.1

---
mesa (17.0.7-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream bugfix release.
  * d/p/vulkan-mir.patch: Refreshed.

mesa (17.0.5-0ubuntu1) artful; urgency=medium

  * New upstream bugfix release. (LP: #1686344)

mesa (17.0.4-1ubuntu1) artful; urgency=medium

  * Merge from Debian.

mesa (17.0.4-1) experimental; urgency=medium

  * New upstrem release.

 -- Timo Aaltonen   Thu, 08 Jun 2017 10:54:05 +0300

** Changed in: mesa (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

2017-08-07 Thread Dariusz Gadomski

Patch proposal for Artful.

** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928420/+files/artful_bluez_5.45-0ubuntu3.debdiff

** Patch removed: "artful_bluez_5.45-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928336/+files/artful_bluez_5.45-0ubuntu3.debdiff

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

2017-08-07 Thread Dave Chiluk

** Also affects: bluez (Ubuntu Artful)
   Importance: Low
   Status: New

** Tags removed: sts-sponsor-chiluk

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-07 Thread Dimitri John Ledkov

Hi,

Please provide minimal example of how to reproduce this. Ideally without
the CI - as I see it tries to setup ccache / clang etc. And I'm not sure
if all of that is relevant.

You mention an older kernel, what kernel is that? I would have thought a
reasonable kernel to test on, is latest xenial-security kernel.

Instead of uploading fixes to util-linux, ideally an upstream bug report
/ pull request is open about the issue with as much details as possible.

Regards,

Dimitri.

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1708635/+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 1709097] Re: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-08-07 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 click in Ubuntu.
https://bugs.launchpad.net/bugs/1709097

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  New

Bug description:
  update problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.9
  AptOrdering:
   click: Install
   click: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Aug  1 12:45:52 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-01  12:45:43
   Commandline: apt-get install -f
   Requested-By: razavi (1000)
   Upgrade: click:amd64 (0.4.43+16.04.20160203-0ubuntu2, 
0.4.43+16.04.20170613-0ubuntu1)
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-25 (346 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: subprocess new pre-removal 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/click/+bug/1709097/+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 1709097] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-08-07 Thread Seyed Naser RAZAVI

Public bug reported:

update problem

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: click 0.4.43+16.04.20160203-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.9
AptOrdering:
 click: Install
 click: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Aug  1 12:45:52 2017
DpkgHistoryLog:
 Start-Date: 2017-08-01  12:45:43
 Commandline: apt-get install -f
 Requested-By: razavi (1000)
 Upgrade: click:amd64 (0.4.43+16.04.20160203-0ubuntu2, 
0.4.43+16.04.20170613-0ubuntu1)
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-08-25 (346 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: click
Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: click (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 click in Ubuntu.
https://bugs.launchpad.net/bugs/1709097

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  New

Bug description:
  update problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.9
  AptOrdering:
   click: Install
   click: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Aug  1 12:45:52 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-01  12:45:43
   Commandline: apt-get install -f
   Requested-By: razavi (1000)
   Upgrade: click:amd64 (0.4.43+16.04.20160203-0ubuntu2, 
0.4.43+16.04.20170613-0ubuntu1)
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-25 (346 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: subprocess new pre-removal 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/click/+bug/1709097/+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 1629226] Re: Bash exits after a few failed fork()-s

2017-08-07 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
   Status: New => Invalid

** Tags added: triage-g

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

Title:
  Bash exits after a few failed fork()-s

Status in The Ubuntu-power-systems project:
  Invalid
Status in bash package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  ===
  I write a simple systemd service which will fork child processes fiercely. 
But quickly the service failed:

  % sudo systemctl status reproducer.service
  ? reproducer.service - Reproducer of systemd services killed by ips
 Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2016-03-18 06:58:37 CDT; 2min 
43s ago
Process: 5103 ExecStart=/home/hpt/reproducer/reproducer.sh (code=exited, 
status=0/SUCCESS)
   Main PID: 5105 (code=exited, status=254)

  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Main process exited, 
code=exited, status=254/n/a
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Unit entered failed 
state.
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Failed with result 
'exit-code'.

  The default task limit of systemd services is 512. Looks like the
  service is terminated by the kernel's ips cgroup controller. I think
  this isn't correct. Child processes cannot be forked shouldn't cause
  parent to die.

  
  % cat /etc/systemd/system/reproducer.service 
  [Unit]
  Description=Reproducer of systemd services killed by ips
  After=multi-user.target

  [Service]
  ExecStart=/home/hpt/reproducer/reproducer.sh
  Type=forking

  [Install]
  WantedBy=multi-user.target

  % cat /home/hpt/reproducer/reproducer.sh
  #!/bin/bash

  foo()
  {
  #exec sh -c "echo $1: \$\$;sleep 60"
  echo $1: 
  sleep 60
  }

  bar()
  {
  c=1
  while true
  do
  for ((i=1;i<=2048;i++))
  do
  foo $c &
  ((c++))
  done

  wait
  c=1
  done
  }

  # main
  bar &

  disown -a

  exit 0

  
  ---uname output---
  Linux pinelp3 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8408-E8E,lpar 

  Steps to Reproduce
  
  1. install the simple service in "Problem description"
  2. sudo systemctl start reproducer.service
  3. wait 2~3 minutes
   
  == Comment: #3 - Vaishnavi Bhat  - 2016-03-22 11:21:55 ==
  From the machine,
  root@pinelp3:~# ulimit -a
  core file size  (blocks, -c) 0
  data seg size   (kbytes, -d) unlimited
  scheduling priority (-e) 0
  file size   (blocks, -f) unlimited
  pending signals (-i) 48192
  max locked memory   (kbytes, -l) 64
  max memory size (kbytes, -m) unlimited
  open files  (-n) 1024
  pipe size(512 bytes, -p) 8
  POSIX message queues (bytes, -q) 819200
  real-time priority  (-r) 0
  stack size  (kbytes, -s) 8192
  cpu time   (seconds, -t) unlimited
  max user processes  (-u) 48192
  virtual memory  (kbytes, -v) unlimited
  file locks  (-x) unlimited

  root@pinelp3:~# ps aux | wc -l  ->While the service is 
running 
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l-->While the service is not 
running. 
  572

  root@pinelp3:~# free -m   --> While service is running
totalusedfree  shared  buff/cache   
available
  Mem:  12117 628 459  22

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

2017-08-07 Thread Henk Terhell

> GTK_THEME=Abiword solves the problem, no more flickering

Also for me it did not solve the problem on Lubuntu Artful 17.10.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+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 1429285] Re: feature request: apt-get update --if-necessary

2017-08-07 Thread Robie Basak

> IMHO, in the use case for "apt install", "apt update" should be
considered an implementation detail and the user shouldn't need to call
it directly. "apt install" should just do the right thing.

Here's basically the same opinion with some commentary from others:
https://twitter.com/chr1sa/status/894048628284604416

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

Title:
  feature request: apt-get update --if-necessary

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  In many cases (juju, lxc containers .. ) we find ourselves in the
  position of not knowing if the apt-cache has been udpated recently.
  So, you either risk not doing it, or do it and it takes some time and
  generates load.

  so long story short, you always run 'apt-get update' which is quite often
  unnecessary.

  Would it be possible to add (or is there now) something like
  '--if-necessary' or '--if-necessary=5m'.  I could imagine that that would
  look at /var/lib/apt/lists and check timestamps on files for each url that
  /etc/apt/sources.list[.d/*] would hit.  If nothing was needed and
  reasonably recent, then it would not do the update.

  There exist other solutions to this like:

https://coderwall.com/p/0xtstw/doing-an-apt-get-update-in-ansible-only-if-a-condition-is-met

https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/

  
  It'd be nice if we had a sane way to say:
update if you need to, otherwise don't waste time and resources

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  6 17:06:22 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-02 (63 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150101)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/+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 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-07 Thread ChristianEhrhardt

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

** This bug is no longer a duplicate of bug 1594902
   Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
** This bug has been marked a duplicate of bug 1707400
   libvirt-bin doesn't regenerate apparmor cache in postinst

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

Title:
  package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  upgrade 15.10 -> 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu10
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon Apr 25 12:44:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-06 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2016-04-14T14:20:45.067249

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574566/+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 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit

2017-08-07 Thread ChristianEhrhardt

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

We think we finally found the issue behind this and in hindsight the 
explanation why this was so bad to reproduce is that it seems to depend on 
apparmor profile caching.
Dupping on the bug that will SRU a fix.

** This bug has been marked a duplicate of bug 1707400
   libvirt-bin doesn't regenerate apparmor cache in postinst

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

Title:
  Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04
  64-bit

Status in apparmor package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  Output from 'apt-get upgrade':
  Setting up libvirt-bin (1.3.1-1ubuntu10.1) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  Job for libvirt-bin.service failed because the control process exited with 
error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript libvirt-bin, action "restart" failed.
  dpkg: error processing package libvirt-bin (--configure):
   subprocess installed post-installation script returned error exit status 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Output from 'systemctl status libvirt-bin.service':
  ● libvirt-bin.service - Virtualization daemon
 Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 
BST; 4min 52s ago
   Docs: man:libvirtd(8)
 http://libvirt.org
Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, 
status=6)
   Main PID: 2984 (code=exited, status=6)

  Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon.
  Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed 
state.
  Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 
'exit-code'.
  Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time 
over, scheduling restart.
  Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon.
  Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated 
too quickly.
  Jun 21 17:55:16 lydia systemd[1]: Failed to start Virtualization daemon.

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

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

[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

2017-08-07 Thread ChristianEhrhardt

@Robie - IIRC Paul wants to use it as "remote ntp check" which actually
should be done via sntp but that binary was unavailable until artful and
the fix doesn't fit an SRU (bug 1604010).

@Josh - just a day after your report the SRU completed that took out the old 
locking and the silly unconditional restart from the ifup hooks. I'd hope 
things should be much better for you now - could you please verify if that is 
true for your scenario as well?
If not we have to search where the remaining issue comes from as the new 
behavior should have ntp preferred to ntpdate and ntpdate being the one 
rejected as ntp already has the port used.
If there is a window e.g. due to the many interfaces that you described - that 
inverts that with ntpdate blocking ntp still that would have to be fixed.


** Changed in: ntp (Ubuntu Xenial)
   Status: Triaged => Incomplete

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Incomplete
Status in ntp package in Debian:
  Fix Released

Bug description:
  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  
  System Information:

   lsb_release -rd:
 Description:Ubuntu 16.04.2 LTS
 Release:16.04

  
   apt-cache policy ntpdate:

 ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

   apt-cache policy ntp:

 ntp:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+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 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell

2017-08-07 Thread Jeremy Bicha

Fedora includes a symbolic Firefox icon in their Firefox distro packaging:
http://pkgs.fedoraproject.org/rpms/firefox/blob/master/f/firefox-symbolic.svg

I think we should do the same and see about pushing that icon upstream.

I think it's up to the app developers to provide the symbolic icons not
the icon theme.

Personally, the icon in the top bar is so small that a symbolic simpler
monochrome icon is a bit more clear than a regular color icon.

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

Title:
  Humanity should provide symbolic versions of custom icons for GNOME
  Shell

Status in Ubuntu theme:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The app icon in top panel next to application menu entry is the
  default adwaita icons and don't match the current theming.

  It's either:
  - the fact that we don't provide the correct icon size in our themes, and so, 
the icons are defaulted
  - a bug in G-S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell

2017-08-07 Thread Didier Roche

For now, let's use in the ubuntu session non symbolic icons:
- our theme doesn't support them and there are few changes we'll have app 
symbolic icons for our default applications in 17.10.
- for coherence reasons: most of branded apps outside of GNOME (firefox, 
chrome, thunderbird) don't have symbolic icons, and so, will appear colorized. 
Shipping two different experiences in the same session is weird. Let's ensure 
the ubuntu session don't use them by default thus.

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

Title:
  Humanity should provide symbolic versions of custom icons for GNOME
  Shell

Status in Ubuntu theme:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The app icon in top panel next to application menu entry is the
  default adwaita icons and don't match the current theming.

  It's either:
  - the fact that we don't provide the correct icon size in our themes, and so, 
the icons are defaulted
  - a bug in G-S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

2017-08-07 Thread Frode Nordahl

@cyphermox Thank you!

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

2017-08-07 Thread Frode Nordahl

@slashd Thank you! I will start work on debdiffs for the SRU's ASAP.

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

2017-08-07 Thread Dariusz Gadomski

Artful patch proposal.

** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928336/+files/artful_bluez_5.45-0ubuntu3.debdiff

** Patch removed: "zesty_bluez_5.43-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4841667/+files/zesty_bluez_5.43-0ubuntu2.debdiff

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1709055] Re: Drop support for Android (Ubuntu Touch patches)

2017-08-07 Thread Sebastien Bacher

Thanks for working on that. Before I look more at it/sponsor, is there
any reason you didn't drop the trust store support? Some of the changes
are required by the snappy patch but that doesn't require the module so
we could at least remove the corresponding deb from debian/control
right?

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

Title:
  Drop support for Android (Ubuntu Touch patches)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Drop support for Android (Ubuntu Touch patches)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+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 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

2017-08-07 Thread Robie Basak

Why does the ntp charm use ntpdate on Xenial, or need to use it?

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp package in Debian:
  Fix Released

Bug description:
  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  
  System Information:

   lsb_release -rd:
 Description:Ubuntu 16.04.2 LTS
 Release:16.04

  
   apt-cache policy ntpdate:

 ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

   apt-cache policy ntp:

 ntp:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
 100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+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 1709055] Re: Drop support for Android (Ubuntu Touch patches)

Here's the patch

** Patch added: "pulseaudio_10.0-2ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+attachment/4928322/+files/pulseaudio_10.0-2ubuntu2.debdiff

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

Title:
  Drop support for Android (Ubuntu Touch patches)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Drop support for Android (Ubuntu Touch patches)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+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 1709055] [NEW] Drop support for Android (Ubuntu Touch patches)

Public bug reported:

Drop support for Android (Ubuntu Touch patches)

** Affects: pulseaudio (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: pulseaudio (Ubuntu)
   Status: New => In Progress

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

Title:
  Drop support for Android (Ubuntu Touch patches)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Drop support for Android (Ubuntu Touch patches)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+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 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

** Branch linked: lp:~mir-team/mir/fix-1672960

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+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 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

** Changed in: mir
Milestone: None => 0.28.0

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+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 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

Looking at src/server/frontend/protobuf_message_processor.cpp LL105..154

This looks like an issue with the "response_callback" supplied to
SelfDeletingCallback throwing: in which case the "callback" has self
destructed before the catch block is entered.

** Changed in: mir
   Status: Confirmed => In Progress

** Changed in: mir
 Assignee: (unassigned) => Alan Griffiths (alan-griffiths)

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2017-08-07 Thread Aleksey

Would love to see similar feature in Gnome as it will be default desktop
for Ubuntu soon.

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

** Changed in: miral
   Status: Incomplete => Invalid

** Changed in: miral (Ubuntu)
   Status: Confirmed => 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/1672012

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1708137] Re: application crashes due to rival protobuffers versions

Thanks.

This is an old issue. It used to cause problems with Unity8 too (see bug
1535297).

A proper fix needs to come from protobuf itself, but the bug could also
be avoided if Mir or your app were willing and able to change protobuf
versions.

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: Incomplete => New

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

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

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

** Summary changed:

- application crashes due to rival protobuffers versions
+ Application crashes due to rival protobuf versions

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Invalid

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

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

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

Title:
  Application crashes due to rival protobuf versions

Status in Mir:
  New
Status in gstreamer-vaapi package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  New
Status in protobuf package in Ubuntu:
  New

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1708137/+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 1708137] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928282/+files/ProcInterrupts.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928281/+files/ProcEnviron.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1708137/+attachment/4928277/+files/Lsusb.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928287/+files/XorgLogOld.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1708137/+attachment/4928276/+files/Lspci.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928289/+files/xdpyinfo.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1708137/+attachment/4928288/+files/Xrandr.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928286/+files/XorgLog.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] UnitySupportTest.txt

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928285/+files/UnitySupportTest.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1708137/+attachment/4928284/+files/UdevDb.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928283/+files/ProcModules.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928280/+files/ProcCpuinfoMinimal.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] MonitorsUser.xml.txt

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928278/+files/MonitorsUser.xml.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928279/+files/ProcCpuinfo.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928274/+files/DpkgLog.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928275/+files/JournalErrors.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928273/+files/CurrentDmesg.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  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:21fa]
  InstallationDate: Installed on 2016-09-23 (317 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2325A95
  Package: mir
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET90WW (2.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A95
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 000H014363
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325A95
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708137] Re: application crashes due to rival protobuffers versions

apport information

** Tags added: apport-collected compiz-0.9 ubuntu xenial

** Description changed:

  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're going
  to deal with that.
  
  Best,
  Henning
+ --- 
+ .tmp.unity_support_test.0:
+  
+ ApportVersion: 2.20.1-0ubuntu2.10
+ 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
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: ubuntu
+ 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:21fa]
+ InstallationDate: Installed on 2016-09-23 (317 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: LENOVO 2325A95
+ Package: mir
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=454b2c55-2a2b-41ca-a3bd-65b0d601658b ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
+ Tags:  xenial ubuntu compiz-0.9
+ Uname: Linux 4.4.0-89-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 12/20/2012
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G2ET90WW (2.50 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 2325A95
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: 000H014363
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn2325A95:pvrThinkPadX230:rvnLENOVO:rn2325A95:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.name: 2325A95
+ dmi.product.version: ThinkPad X230
+ dmi.sys.vendor: LENOVO
+ version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1708137/+attachment/4928272/+files/BootLog.txt

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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

[Touch-packages] [Bug 1709028] [NEW] ubuntu after install

2017-08-07 Thread mike loudermilk

Public bug reported:

I know it is beta but it keeps crashing (shutting down) it will install
1 or 2 apps then crash

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm 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  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
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
Date: Mon Aug  7 03:10:31 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-30-generic, x86_64: installed
 nvidia-375, 375.66, 4.10.0-30-generic, x86_64: installed
 virtualbox, 5.1.22, 4.10.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:361c]
InstallationDate: Installed on 2017-07-15 (22 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=d40eff84-0e39-42dc-ace7-e8f4c66aae07 ro nopat vesafb.invalid=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Aug  7 03:07:35 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSteelSeries SteelSeries Apex Raw Gaming Keyboard KEYBOARD, id 8
 inputSteelSeries SteelSeries Apex Raw Gaming Keyboard KEYBOARD, id 9
 inputKensington  Kensington USB/PS2 Orbit MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1~16.04.1

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


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

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

Title:
  ubuntu after install

Status in xorg package in Ubuntu:
  New

Bug description:
  I know it is beta but it keeps crashing (shutting down) it will
  install 1 or 2 apps then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm 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: ""

[Touch-packages] [Bug 447136] Re: package iputils-tracepath 3:20071127-1build1 failed to install/upgrade: underprocess installerade post-installation-skript gav felkod 2

2017-08-07 Thread Daniel Croona

I thought it was closed already, and now I moved it to "Invalid". Is
that OK?

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

Title:
  package iputils-tracepath 3:20071127-1build1 failed to
  install/upgrade: underprocess installerade post-installation-skript
  gav felkod 2

Status in iputils package in Ubuntu:
  Invalid

Bug description:
  error occured during upgrade from ubuntu 9.04 to 9.10

  ProblemType: Package
  Architecture: i386
  Date: Fri Oct  9 12:40:48 2009
  DistroRelease: Ubuntu 9.10
  ErrorMessage: underprocess installerade post-installation-skript gav felkod 2
  Package: iputils-tracepath 3:20071127-1build1
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: iputils
  Title: package iputils-tracepath 3:20071127-1build1 failed to 
install/upgrade: underprocess installerade post-installation-skript gav felkod 2
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/447136/+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 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell

Oh, sorry. This bug is about app icons. I was talking about indicators.

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

Title:
  Humanity should provide symbolic versions of custom icons for GNOME
  Shell

Status in Ubuntu theme:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The app icon in top panel next to application menu entry is the
  default adwaita icons and don't match the current theming.

  It's either:
  - the fact that we don't provide the correct icon size in our themes, and so, 
the icons are defaulted
  - a bug in G-S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 901622] Re: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) )

2017-08-07 Thread Brinstar

Not sure if this is the same bug but I'm having problems with an ext4
USB drive being recognised in Ubuntu 16.04.3 after waking from suspend

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

Title:
  Resume after pm-suspend with read-only ext4 root file system on USB
  disk (ext4 journal commit I/O error) )

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to Oneiric resume from pm-suspend no longer works, might be 
connected to change of kernel from 2.6.38 to 3.0.0... Issue also reported for 
Arch Linux and kernel 2.6.39 here: 
https://bbs.archlinux.org/viewtopic.php?pid=1008743
  See attached dmesg output for details

  This is for kernel 3.0.0-14-server x86_64 (but also occured on 3.0.0-13) and 
a NAS booting from a USB stick.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  Package: pm-utils 1.4.1-8ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (51 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd 
lpadmin netdev plugdev powerdev sambashare scanner tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/901622/+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 1292763] Re: ld-2.19.so crashed with SIGSEGV in in in ??()

2017-08-07 Thread Bug Watch Updater

** Changed in: eglibc (Debian)
   Status: Unknown => New

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

Title:
  ld-2.19.so crashed with SIGSEGV in  in  in
  ??()

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  New

Bug description:
  This happened when I was running `update-manager', when it was
  configuring packages at the end.

  In the kernel log, I find:

  [146936.255567] traps: ld-linux-x32.so[26237] general protection ip:f7715ced 
sp:ff8372a8 error:0 in ld-2.19.so[f76ff000+2]
  [146936.617914] traps: ld-linux-x32.so[26247] general protection ip:f778aced 
sp:ffd435c8 error:0 in ld-2.19.so[f7774000+2]
  [146936.794923] traps: ld-linux-x32.so[26257] general protection ip:f776eced 
sp:ffd19978 error:0 in ld-2.19.so[f7758000+2]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libc6-x32 2.19-0ubuntu2
  Uname: Linux 3.13.6 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 14 13:51:30 2014
  Dependencies:
   gcc-4.9-base 4.9-20140303-0ubuntu3
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140303-0ubuntu3
   multiarch-support 2.19-0ubuntu2
  Disassembly: value is not available
  ExecutablePath: /libx32/ld-2.19.so
  InstallationDate: Installed on 2011-02-28 (1110 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /libx32/ld-linux-x32.so.2
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcMaps:
   f772c000-f772d000 r-xp  00:00 0  
[vdso]
   f772d000-f774d000 r-xp  08:01 22151174   
/libx32/ld-2.19.so
   f794c000-f794e000 rw-p 0001f000 08:01 22151174   
/libx32/ld-2.19.so
   ffc0d000-ffc2e000 rw-p  00:00 0  
[stack]
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: eglibc
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 13235):
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  Title: ld-2.19.so crashed with SIGSEGV in  in ??()
  UpgradeStatus: Upgraded to trusty on 2014-03-13 (2 days ago)
  UserGroups: pkcs11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1292763/+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 1292763] Re: ld-2.19.so crashed with SIGSEGV in in in ??()

I intend to close this ticket as fix released soon (based on bug 1302903
comment 1).  Please speak up if you still experience this.

** Bug watch added: Debian Bug tracker #722348
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722348

** Also affects: eglibc (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722348
   Importance: Unknown
   Status: Unknown

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

Title:
  ld-2.19.so crashed with SIGSEGV in  in  in
  ??()

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  Unknown

Bug description:
  This happened when I was running `update-manager', when it was
  configuring packages at the end.

  In the kernel log, I find:

  [146936.255567] traps: ld-linux-x32.so[26237] general protection ip:f7715ced 
sp:ff8372a8 error:0 in ld-2.19.so[f76ff000+2]
  [146936.617914] traps: ld-linux-x32.so[26247] general protection ip:f778aced 
sp:ffd435c8 error:0 in ld-2.19.so[f7774000+2]
  [146936.794923] traps: ld-linux-x32.so[26257] general protection ip:f776eced 
sp:ffd19978 error:0 in ld-2.19.so[f7758000+2]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libc6-x32 2.19-0ubuntu2
  Uname: Linux 3.13.6 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 14 13:51:30 2014
  Dependencies:
   gcc-4.9-base 4.9-20140303-0ubuntu3
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140303-0ubuntu3
   multiarch-support 2.19-0ubuntu2
  Disassembly: value is not available
  ExecutablePath: /libx32/ld-2.19.so
  InstallationDate: Installed on 2011-02-28 (1110 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /libx32/ld-linux-x32.so.2
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcMaps:
   f772c000-f772d000 r-xp  00:00 0  
[vdso]
   f772d000-f774d000 r-xp  08:01 22151174   
/libx32/ld-2.19.so
   f794c000-f794e000 rw-p 0001f000 08:01 22151174   
/libx32/ld-2.19.so
   ffc0d000-ffc2e000 rw-p  00:00 0  
[stack]
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: eglibc
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 13235):
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  Title: ld-2.19.so crashed with SIGSEGV in  in ??()
  UpgradeStatus: Upgraded to trusty on 2014-03-13 (2 days ago)
  UserGroups: pkcs11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1292763/+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 1302903] Re: traps: ld-linux-x32.so[10206] general protection ip:f7786e8d sp:ffd7ae08 error:0 in ld-2.17.so[f7770000+21000]

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

** This bug has been marked a duplicate of bug 1292763
   ld-2.19.so crashed with SIGSEGV in  in  in ??()

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

Title:
  traps: ld-linux-x32.so[10206] general protection ip:f7786e8d
  sp:ffd7ae08 error:0 in ld-2.17.so[f777+21000]

Status in eglibc package in Ubuntu:
  Incomplete
Status in eglibc package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/722348:

  Package: libc6-x32
  Version: 2.17-92+b1
  Severity: important

  Dear Maintainer,
  *** Please consider answering these questions, where appropriate ***
  > What led up to the situation?
  Don't know. Mostly when upgrading the packages a lot of these errors will be
  logged in /var/log/messages.

  > What exactly did you do (or not do) that was effective (or ineffective)?
  No, idea. Just apt-get upgrade the system.

  > What was the outcome of this action?
  Many error messages logged in the /var/log/message file:
  ---
  Sep 10 20:51:16 xx kernel: [  496.550568] traps: ld-linux-x32.so[9186]
  general protection ip:f7709e8d sp:fffb7998 error:0 in
  ld-2.17.so[f76f3000+21000]
  Sep 10 20:51:22 xx kernel: [  502.001278] do_general_protection: 34
  callbacks suppressed
  Sep 10 20:51:22 xx kernel: [  502.001289] traps: ld-linux-x32.so[9997]
  general protection ip:f774ee8d sp:ffa91478 error:0 in
  ld-2.17.so[f7738000+21000]
  Sep 10 20:51:22 xx kernel: [  502.085832] traps: ld-linux-x32.so[10011]
  general protection ip:f77cae8d sp:ffc98ac8 error:0 in
  ld-2.17.so[f77b4000+21000]
  Sep 10 20:51:22 xx kernel: [  502.132180] traps: ld-linux-x32.so[10027]
  general protection ip:f770ee8d sp:ff9a6048 error:0 in
  ld-2.17.so[f76f8000+21000]
  Sep 10 20:51:22 xx kernel: [  502.202541] traps: ld-linux-x32.so[10041]
  general protection ip:f7782e8d sp:ffe4d8a8 error:0 in
  ld-2.17.so[f776c000+21000]
  Sep 10 20:51:22 xx kernel: [  502.256817] traps: ld-linux-x32.so[10055]
  general protection ip:f77e7e8d sp:ff80e4f8 error:0 in
  ld-2.17.so[f77d1000+21000]
  Sep 10 20:51:22 xx kernel: [  502.314973] traps: ld-linux-x32.so[10069]
  general protection ip:f77afe8d sp:ffd43cd8 error:0 in
  ld-2.17.so[f7799000+21000]
  Sep 10 20:51:23 xx kernel: [  502.836815] traps: ld-linux-x32.so[10123]
  general protection ip:f7751e8d sp:ff8605f8 error:0 in
  ld-2.17.so[f773b000+21000]
  Sep 10 20:51:23 xx kernel: [  503.396900] traps: ld-linux-x32.so[10178]
  general protection ip:f779ce8d sp:ffc0ae38 error:0 in
  ld-2.17.so[f7786000+21000]
  Sep 10 20:51:23 xx kernel: [  503.452558] traps: ld-linux-x32.so[10192]
  general protection ip:f77abe8d sp:ff8e8368 error:0 in
  ld-2.17.so[f7795000+21000]
  Sep 10 20:51:23 xx kernel: [  503.497275] traps: ld-linux-x32.so[10206]
  general protection ip:f7786e8d sp:ffd7ae08 error:0 in
  ld-2.17.so[f777+21000]
  ---

  > What outcome did you expect instead?
  No errors.

  *** End of the template - remove these lines ***

  May I know how to debug this issue? Please let me know if anything I can help,
  thanks!


  -- System Information:
  Debian Release: jessie/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
  Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
  Shell: /bin/sh linked to /bin/bash

  Versions of packages libc6-x32 depends on:
  ii  libc6  2.17-92+b1

  libc6-x32 recommends no packages.

  libc6-x32 suggests no packages.

  -- no debconf information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1302903/+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 1292763] Re: ld-2.19.so crashed with SIGSEGV in in in ??()

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ld-2.19.so crashed with SIGSEGV in  in  in
  ??()

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  Unknown

Bug description:
  This happened when I was running `update-manager', when it was
  configuring packages at the end.

  In the kernel log, I find:

  [146936.255567] traps: ld-linux-x32.so[26237] general protection ip:f7715ced 
sp:ff8372a8 error:0 in ld-2.19.so[f76ff000+2]
  [146936.617914] traps: ld-linux-x32.so[26247] general protection ip:f778aced 
sp:ffd435c8 error:0 in ld-2.19.so[f7774000+2]
  [146936.794923] traps: ld-linux-x32.so[26257] general protection ip:f776eced 
sp:ffd19978 error:0 in ld-2.19.so[f7758000+2]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libc6-x32 2.19-0ubuntu2
  Uname: Linux 3.13.6 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 14 13:51:30 2014
  Dependencies:
   gcc-4.9-base 4.9-20140303-0ubuntu3
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140303-0ubuntu3
   multiarch-support 2.19-0ubuntu2
  Disassembly: value is not available
  ExecutablePath: /libx32/ld-2.19.so
  InstallationDate: Installed on 2011-02-28 (1110 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /libx32/ld-linux-x32.so.2
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcMaps:
   f772c000-f772d000 r-xp  00:00 0  
[vdso]
   f772d000-f774d000 r-xp  08:01 22151174   
/libx32/ld-2.19.so
   f794c000-f794e000 rw-p 0001f000 08:01 22151174   
/libx32/ld-2.19.so
   ffc0d000-ffc2e000 rw-p  00:00 0  
[stack]
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: eglibc
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 13235):
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  Title: ld-2.19.so crashed with SIGSEGV in  in ??()
  UpgradeStatus: Upgraded to trusty on 2014-03-13 (2 days ago)
  UserGroups: pkcs11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1292763/+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 1292763] Re: ld-2.19.so crashed with SIGSEGV in in in ??()

This seems to occur only in libc-x32.  Reports so far are only for
14.04/trusty.  Can anybody reproduce this on a later release?

** This bug is no longer a duplicate of private bug 1297993

** Changed in: eglibc (Ubuntu)
 Assignee: (unassigned) => Rolf Leggewie (r0lf)

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

Title:
  ld-2.19.so crashed with SIGSEGV in  in  in
  ??()

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  Unknown

Bug description:
  This happened when I was running `update-manager', when it was
  configuring packages at the end.

  In the kernel log, I find:

  [146936.255567] traps: ld-linux-x32.so[26237] general protection ip:f7715ced 
sp:ff8372a8 error:0 in ld-2.19.so[f76ff000+2]
  [146936.617914] traps: ld-linux-x32.so[26247] general protection ip:f778aced 
sp:ffd435c8 error:0 in ld-2.19.so[f7774000+2]
  [146936.794923] traps: ld-linux-x32.so[26257] general protection ip:f776eced 
sp:ffd19978 error:0 in ld-2.19.so[f7758000+2]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libc6-x32 2.19-0ubuntu2
  Uname: Linux 3.13.6 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 14 13:51:30 2014
  Dependencies:
   gcc-4.9-base 4.9-20140303-0ubuntu3
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140303-0ubuntu3
   multiarch-support 2.19-0ubuntu2
  Disassembly: value is not available
  ExecutablePath: /libx32/ld-2.19.so
  InstallationDate: Installed on 2011-02-28 (1110 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: /libx32/ld-linux-x32.so.2
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcMaps:
   f772c000-f772d000 r-xp  00:00 0  
[vdso]
   f772d000-f774d000 r-xp  08:01 22151174   
/libx32/ld-2.19.so
   f794c000-f794e000 rw-p 0001f000 08:01 22151174   
/libx32/ld-2.19.so
   ffc0d000-ffc2e000 rw-p  00:00 0  
[stack]
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: eglibc
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 13235):
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  Title: ld-2.19.so crashed with SIGSEGV in  in ??()
  UpgradeStatus: Upgraded to trusty on 2014-03-13 (2 days ago)
  UserGroups: pkcs11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1292763/+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 447136] Re: package iputils-tracepath 3:20071127-1build1 failed to install/upgrade: underprocess installerade post-installation-skript gav felkod 2

2017-08-07 Thread Daniel Croona

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

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

Title:
  package iputils-tracepath 3:20071127-1build1 failed to
  install/upgrade: underprocess installerade post-installation-skript
  gav felkod 2

Status in iputils package in Ubuntu:
  Invalid

Bug description:
  error occured during upgrade from ubuntu 9.04 to 9.10

  ProblemType: Package
  Architecture: i386
  Date: Fri Oct  9 12:40:48 2009
  DistroRelease: Ubuntu 9.10
  ErrorMessage: underprocess installerade post-installation-skript gav felkod 2
  Package: iputils-tracepath 3:20071127-1build1
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: iputils
  Title: package iputils-tracepath 3:20071127-1build1 failed to 
install/upgrade: underprocess installerade post-installation-skript gav felkod 2
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/447136/+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 1292763] Re: ld-2.19.so crashed with SIGSEGV in in in ??()