date:20171121

Hello Lawrence, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed-xenial

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in wayland-protocols source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727390] Re: New bugfix release 17.2.4

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed-xenial

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1647069] Re: package rfkill 0.5-1ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

This bug was fixed in the package rfkill - 0.5-2ubuntu1

---
rfkill (0.5-2ubuntu1) bionic; urgency=low

  * Sync from Debian unstable; all previous changes dropped as obsolete,
the minimum required systemd version shipped in xenial and the upstart
jobs can now be dropped.  LP: #1732795.
- Fixes problem of rfkill being configured while udev is not configured.
  LP: #1647069.
  * debian/rfkill.maintscript: handle removal of obsolete upstart jobs on
upgrade.  This change can be dropped after 18.04 LTS.

rfkill (0.5-2) unstable; urgency=medium

  * QA upload.
  * Set Debian QA Group as maintainer. (see #881513)
  * Migrations:
  - debian/control to format 1.0.
  - debian/rules to simplified format.
  - DH level to 10.
  * debian/control:
  - Bumped Standards-Version to 4.1.1.
  - Removed no longer needed build dependency dpkg-dev.
  - Updated VCS fields.
  * debian/patches/:
  - debian-changes:
  ~ Renamed to 10_fix-manpage.patch.
  ~ Added a specific header.
  - 20_add-GCC-hardening.patch: created to use GCC hardening.
  * debian/rules:
  - Do not use Debian revision as version for final binary.
  - Use build architecture compiler to avoid a FTCBFS. Thanks to
Helmut Grohne . (Closes: #839798)
  * debian/source/:
  - options: removed. This file was pushing all patches to a single file.
  - patch-header: removed. It was creating a "default" header.
  * debian/watch:
  - Bumped to version 4.
  - Updated.

 -- Steve Langasek   Tue, 21 Nov 2017
15:41:16 -0800

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

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

Title:
  package rfkill 0.5-1ubuntu3 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in rfkill package in Ubuntu:
  Fix Released

Bug description:
  The rfkill package call udevadm see https://bugs.launchpad.net/ubuntu-
  packaging-guide/+bug/1646557/

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rfkill 0.5-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec  1 12:32:46 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: rfkill
  Title: package rfkill 0.5-1ubuntu3 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.rfkill-restore.override: manual
  upstart.rfkill-store.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1647069/+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 1732795] Re: Sync rfkill 0.5-2 (main) from Debian unstable (main)

This bug was fixed in the package rfkill - 0.5-2ubuntu1

---
rfkill (0.5-2ubuntu1) bionic; urgency=low

  * Sync from Debian unstable; all previous changes dropped as obsolete,
the minimum required systemd version shipped in xenial and the upstart
jobs can now be dropped.  LP: #1732795.
- Fixes problem of rfkill being configured while udev is not configured.
  LP: #1647069.
  * debian/rfkill.maintscript: handle removal of obsolete upstart jobs on
upgrade.  This change can be dropped after 18.04 LTS.

rfkill (0.5-2) unstable; urgency=medium

  * QA upload.
  * Set Debian QA Group as maintainer. (see #881513)
  * Migrations:
  - debian/control to format 1.0.
  - debian/rules to simplified format.
  - DH level to 10.
  * debian/control:
  - Bumped Standards-Version to 4.1.1.
  - Removed no longer needed build dependency dpkg-dev.
  - Updated VCS fields.
  * debian/patches/:
  - debian-changes:
  ~ Renamed to 10_fix-manpage.patch.
  ~ Added a specific header.
  - 20_add-GCC-hardening.patch: created to use GCC hardening.
  * debian/rules:
  - Do not use Debian revision as version for final binary.
  - Use build architecture compiler to avoid a FTCBFS. Thanks to
Helmut Grohne . (Closes: #839798)
  * debian/source/:
  - options: removed. This file was pushing all patches to a single file.
  - patch-header: removed. It was creating a "default" header.
  * debian/watch:
  - Bumped to version 4.
  - Updated.

 -- Steve Langasek   Tue, 21 Nov 2017
15:41:16 -0800

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

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

Title:
  Sync rfkill 0.5-2 (main) from Debian unstable (main)

Status in rfkill package in Ubuntu:
  Fix Released

Bug description:
  Please sync rfkill 0.5-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian.  Remaining changes:
  - Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
state across reboots.

  Per the changelog the only remaining changes is to create the upstart jobs in 
/etc/init. 
  That's no longer needed and no longer has any effect with upstart no longer 
used - in fact
  some of upstart has already been removed from this package, see:
* Drop obsolete and no-op dh_installinit --upstart-only option.
  (LP: #1519228)

  
  Changelog entries since current bionic version 0.5-1ubuntu4:

  rfkill (0.5-2) unstable; urgency=medium

* QA upload.
* Set Debian QA Group as maintainer. (see #881513)
* Migrations:
- debian/control to format 1.0.
- debian/rules to simplified format.
- DH level to 10.
* debian/control:
- Bumped Standards-Version to 4.1.1.
- Removed no longer needed build dependency dpkg-dev.
- Updated VCS fields.
* debian/patches/:
- debian-changes:
~ Renamed to 10_fix-manpage.patch.
~ Added a specific header.
- 20_add-GCC-hardening.patch: created to use GCC hardening.
* debian/rules:
- Do not use Debian revision as version for final binary.
- Use build architecture compiler to avoid a FTCBFS. Thanks to
  Helmut Grohne . (Closes: #839798)
* debian/source/:
- options: removed. This file was pushing all patches to a single file.
- patch-header: removed. It was creating a "default" header.
* debian/watch:
- Bumped to version 4.
- Updated.

   -- Joao Eriberto Mota Filho   Mon, 13 Nov 2017
  18:17:03 -0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1732795/+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 1732795] Re: Sync rfkill 0.5-2 (main) from Debian unstable (main)

2017-11-21 Thread dino99

rfkill (0.5-2ubuntu1) bionic; urgency=low

  * Sync from Debian unstable; all previous changes dropped as obsolete,
the minimum required systemd version shipped in xenial and the upstart
jobs can now be dropped.  LP: #1732795.
- Fixes problem of rfkill being configured while udev is not configured.
  LP: #1647069.
  * debian/rfkill.maintscript: handle removal of obsolete upstart jobs on
upgrade.  This change can be dropped after 18.04 LTS.

 -- Steve Langasek   Tue, 21 Nov 2017
15:41:16 -0800

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

Title:
  Sync rfkill 0.5-2 (main) from Debian unstable (main)

Status in rfkill package in Ubuntu:
  New

Bug description:
  Please sync rfkill 0.5-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian.  Remaining changes:
  - Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
state across reboots.

  Per the changelog the only remaining changes is to create the upstart jobs in 
/etc/init. 
  That's no longer needed and no longer has any effect with upstart no longer 
used - in fact
  some of upstart has already been removed from this package, see:
* Drop obsolete and no-op dh_installinit --upstart-only option.
  (LP: #1519228)

  
  Changelog entries since current bionic version 0.5-1ubuntu4:

  rfkill (0.5-2) unstable; urgency=medium

* QA upload.
* Set Debian QA Group as maintainer. (see #881513)
* Migrations:
- debian/control to format 1.0.
- debian/rules to simplified format.
- DH level to 10.
* debian/control:
- Bumped Standards-Version to 4.1.1.
- Removed no longer needed build dependency dpkg-dev.
- Updated VCS fields.
* debian/patches/:
- debian-changes:
~ Renamed to 10_fix-manpage.patch.
~ Added a specific header.
- 20_add-GCC-hardening.patch: created to use GCC hardening.
* debian/rules:
- Do not use Debian revision as version for final binary.
- Use build architecture compiler to avoid a FTCBFS. Thanks to
  Helmut Grohne . (Closes: #839798)
* debian/source/:
- options: removed. This file was pushing all patches to a single file.
- patch-header: removed. It was creating a "default" header.
* debian/watch:
- Bumped to version 4.
- Updated.

   -- Joao Eriberto Mota Filho   Mon, 13 Nov 2017
  18:17:03 -0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1732795/+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 1731910] Re: gnome-shell-calendar-server assert failure: * Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 *

This bug was fixed in the package evolution-data-server -
3.26.2.1-1ubuntu1

---
evolution-data-server (3.26.2.1-1ubuntu1) bionic; urgency=medium

  * Sync with Debian (LP: #1731910). Remaining change:
- Add transitional evolution-data-server-online-accounts package.
  This can be dropped after Ubuntu 18.04 LTS.

evolution-data-server (3.26.2.1-1) unstable; urgency=medium

  * New upstream release
  * Add new symbol

 -- Jeremy Bicha   Tue, 14 Nov 2017 10:38:45 -0500

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell-calendar-server assert failure: *** Error in `/usr/lib
  /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer:
  0x559ef762f960 ***

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  no idea how to reproduce.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:13:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   e_cal_component_free_datetime () at 
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1731910/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

This bug was fixed in the package mesa - 17.2.4-0ubuntu2

---
mesa (17.2.4-0ubuntu2) bionic; urgency=medium

  * Import changes from 17.2.2-0ubuntu2
  * Make mesa-va-drivers enhance libva2 rather than libva1.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP: #1720890)

 -- Timo Aaltonen   Wed, 08 Nov 2017 16:29:58 +0200

** Changed in: mesa (Ubuntu)
   Status: In Progress => 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/1720890

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1727390] Re: New bugfix release 17.2.4

This bug was fixed in the package mesa - 17.2.4-0ubuntu2

---
mesa (17.2.4-0ubuntu2) bionic; urgency=medium

  * Import changes from 17.2.2-0ubuntu2
  * Make mesa-va-drivers enhance libva2 rather than libva1.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP: #1720890)

 -- Timo Aaltonen   Wed, 08 Nov 2017 16:29:58 +0200

** Changed in: mesa (Ubuntu)
   Status: In Progress => 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/1727390

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

This bug was fixed in the package mesa - 17.2.4-0ubuntu2

---
mesa (17.2.4-0ubuntu2) bionic; urgency=medium

  * Import changes from 17.2.2-0ubuntu2
  * Make mesa-va-drivers enhance libva2 rather than libva1.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP: #1720890)

 -- Timo Aaltonen   Wed, 08 Nov 2017 16:29:58 +0200

** Changed in: mesa (Ubuntu)
   Status: New => 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/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

Stephan Fabel, while I wouldn't say this is fully root caused, due to
how debugging GUI stuff is not my focus, I'll mark this Triaged for now.
However, given Ubuntu is moving away from Unity going forward as per
https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-
rather-than-phone-and-convergence/ you may want to use a GNOME based
session going forward to avoid this problem.

** Changed in: xorg (Ubuntu)
   Importance: Medium => Low

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

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: Use GNOME Flashback (Metacity) session.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

--

[Touch-packages] [Bug 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

** Description changed:

  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4
  
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.
  
  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or animation,
  the mouse pointer remains static and drawn.
  
  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor
  
  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.
  
  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.
  
  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.
  
  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713
+ 
+ WORKAROUND: Use GNOME Flashback (Metacity) session.
  
  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse

[Touch-packages] [Bug 1733733] [NEW] portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estad

2017-11-21 Thread Guilherme Soares Lima

Public bug reported:

I installed orbital apps then it crashed, i changed to unity environment then 
tried to install again. I'm in need for portable apps for ubuntu.
Description:Ubuntu 17.10
Release:17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: gconf2-common 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Tue Nov 21 21:44:08 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 128
InstallationDate: Installed on 2017-09-05 (77 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: gconf
Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 128
UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago)

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

Title:
  portable apps crash while installing package gconf2-common
  3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-
  installation instalado retornou estado de saída de erro 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I installed orbital apps then it crashed, i changed to unity environment then 
tried to install again. I'm in need for portable apps for ubuntu.
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gconf2-common 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 21 21:44:08 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 128
  InstallationDate: Installed on 2017-09-05 (77 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 128
  UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1733733/+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 1535048] Re: i915 driver seems to cause system crash at random

2017-11-21 Thread Tyson Tan

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

On my system:
1) the problem doesn't seem to be related to i915 firmware (which the archlinux 
report I mentioned)
2) the problem seems to be triggered by a spike in CPU/GPU stress, it can be 
triggered by two kinds of actions in particular: disk partitioning / OpenGl 
accelerated applications
3) the problem is fixed when a realtime Linux kernel is being used

I highly suspect this to be a bug in Linux power management for Skylake.

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
  VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y 
axis) 338mm x 270mm
 1280x1024 60.02*+ 75.02
 1152x864 75.00
 1024x768 75.08 70.07 60.00
 832x624 74.55
 800x600 72.19 75.00 60.32 56.25
 640x480 75.00 72.81 66.67 60.00
 720x400 70.08
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  The program 'fglrxinfo' can be found in the following packages:
   * fglrx
   * fglrx-updates
  Try: sudo apt-get install 
  The program 'nvidia-settings' is currently not installed. You can install it 
by typing:
  sudo apt-get install nvidia-settings
  H/W path Device Class Description

[Touch-packages] [Bug 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

2017-11-21 Thread David Glasser

I got some advice on mistakes in my update to changelog. This version
should be better.

** Patch added: "Second version with fixed changelog entries"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+attachment/5012529/+files/Fix-journald-rate-limit-with-low-disk-space.debdiff

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

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

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

2017-11-21 Thread Evan Broder

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

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

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

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

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-artful

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727390] Re: New bugfix release 17.2.4

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-artful

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

Hello Lawrence, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage

2017-11-21 Thread Anders Hall

The problem went away in 17.10. Cheers.

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM

2017-11-21 Thread Anders Hall

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

The problem went away in 17.10. Cheers.


** This bug has been marked a duplicate of bug 774071
   Indicator-datetime-service renders 100% CPU usage

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2017-11-21 Thread Stephan Fabel

I can confirm that the issue is gone completely using the "GNOME
Flashback (Metacity)" session.

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 346386] Re: [MASTER] Update fails with invalid package files with "Encountered a section with no Package: header"

2017-11-21 Thread Julian Andres Klode

** Changed in: apt (Ubuntu)
 Assignee: Pavel muhlheim (procomp26) => (unassigned)

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

Title:
  [MASTER] Update fails with invalid package files with "Encountered a
  section with no Package: header"

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Natty:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  Binary package hint: adept-updater

  Pertinent data printed when attempting to run Updater as follows:

  An unresolvable problem occurred while initializing the package
  information.

  Please report this bug against the 'update-manager' package and
  include the following error message:

  'E:Encountered a section with no Package: header, E:Problem with
  MergeList /var/lib/apt/lists/us.archive.ubuntu
  .com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The
  package lists or status file could not be parsed or opened.'

  WORKAROUND:
  Remove problematic files from /var/lib/apt/lists/ and rerun apt-get update.

  In the event that one is connected to a network with a proxy server
  that returns html pages (like a web page requesting you to login) and
  not package list files.   Those html files will get downloaded to
  /var/lib/apt/lists/ and prevent someone from using a package manager
  until the problem html pages are removed.

  TEST CASE:
  1) download the dummy-proxy attachment from this bug report
  2) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a 
proxy that is not allowing access to archive.ubuntu.com and gives you   garbage 
html instead)
  2.5) Execute 'sudo -i' in a terminal
  3) Execute 'http_proxy=http://localhost:8080 apt-get update' in same terminal
  4) Observe the following error messages in your terminal:
  W: GPG error: http://archive.ubuntu.com precise InRelease: File 
/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease 
doesn't  start with a clearsigned message
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index  No Hash 
entry in Release file /var/lib/apt/lists/partial/
archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index
  W: Failed to fetch 
gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources
 Encountered a section with noPackage: header
  5) Stop dummy-proxy
  6) Execute 'sudo apt-get update' in a terminal
  7) Observe the following error message:
  Reading package lists... Done
  W: GPG error: http://archive.ubuntu.com precise Release: The following 
signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic  
Signing Key 
  8) Remove the problematic files in /var/lib/apt/lists (sudo rm 
/var/lib/apt/lists/*)

  Install apt from -proposed
  1) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a 
proxy that is not allowing access to archive.ubuntu.com and gives you   
garbarge html instead)
  1.5) Execute 'sudo -i' in a terminal
  2) Execute 'http_proxy=http://localhost:8080 apt-get update' in same terminal
  3) Observe the following error messages in your terminal:
  W: A error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: http://
archive.ubuntu.com precise Release: The following signatures were invalid: 
NODATA 1 NODATA 2
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/Release
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.
  4) Stop dummy-proxy
  5) Execute 'sudo apt-get update' in a terminal
  6) Observe the update succeed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+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 1548057] Re: rfkill state is not restored on reboot

2017-11-21 Thread Steve Langasek

This is now handled by the systemd package (/lib/systemd/systemd-rfkill;
/lib/systemd/system/rfkill.service).  And yes, it is buggy from what I
can see.

** Package changed: rfkill (Ubuntu) => systemd (Ubuntu)

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

Title:
  rfkill state is not restored on reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  For fun having

  rfkill block bluetooth

  in rc.local does not work either

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rfkill 0.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 21 13:37:39 2016
  InstallationDate: Installed on 2013-05-17 (1010 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: rfkill
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1548057/+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 1732795] Re: Sync rfkill 0.5-2 (main) from Debian unstable (main)

2017-11-21 Thread Steve Langasek

This must not be a sync because the old Ubuntu version ships upstart
jobs as conffiles which must be cleaned up on upgrade.

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

Title:
  Sync rfkill 0.5-2 (main) from Debian unstable (main)

Status in rfkill package in Ubuntu:
  New

Bug description:
  Please sync rfkill 0.5-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian.  Remaining changes:
  - Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
state across reboots.

  Per the changelog the only remaining changes is to create the upstart jobs in 
/etc/init. 
  That's no longer needed and no longer has any effect with upstart no longer 
used - in fact
  some of upstart has already been removed from this package, see:
* Drop obsolete and no-op dh_installinit --upstart-only option.
  (LP: #1519228)

  
  Changelog entries since current bionic version 0.5-1ubuntu4:

  rfkill (0.5-2) unstable; urgency=medium

* QA upload.
* Set Debian QA Group as maintainer. (see #881513)
* Migrations:
- debian/control to format 1.0.
- debian/rules to simplified format.
- DH level to 10.
* debian/control:
- Bumped Standards-Version to 4.1.1.
- Removed no longer needed build dependency dpkg-dev.
- Updated VCS fields.
* debian/patches/:
- debian-changes:
~ Renamed to 10_fix-manpage.patch.
~ Added a specific header.
- 20_add-GCC-hardening.patch: created to use GCC hardening.
* debian/rules:
- Do not use Debian revision as version for final binary.
- Use build architecture compiler to avoid a FTCBFS. Thanks to
  Helmut Grohne . (Closes: #839798)
* debian/source/:
- options: removed. This file was pushing all patches to a single file.
- patch-header: removed. It was creating a "default" header.
* debian/watch:
- Bumped to version 4.
- Updated.

   -- Joao Eriberto Mota Filho   Mon, 13 Nov 2017
  18:17:03 -0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1732795/+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 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

This bug was fixed in the package dnsmasq - 2.75-1ubuntu0.16.04.4

---
dnsmasq (2.75-1ubuntu0.16.04.4) xenial; urgency=medium

  * Fix replying prematurely if one of many servers replies REFUSED
(LP: #1726017) by adding two upstream patches.
- 2.76: 4ace25c5d6: Treat REFUSED (not SERVFAIL) as an unsuccessful
  upstream response
- 2.77: 68f6312d4b: Stop treating SERVFAIL as a successful response from
  upstream servers.

 -- Christian Ehrhardt   Mon, 23 Oct
2017 08:32:22 +0200

** Changed in: dnsmasq (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Released
Status in dnsmasq source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * DNS name resolution fails in certain network configurations, where
     different DNS servers are responsible for different domains and one or
     more servers reply REFUSED to queries that regard other domains than
     their own. Without the patch, dnsmasq returns a negative reply to
     if only one such negative answer is received from a forwarder, even
     if other forwarders return valid responses.

     This breaks
     the resolver and practically all internet connectivity, including web
     browsing, email, and receiving updates.

   * This should be backported to stable to fix internet connectivity
     for users.

   * The patch fixes the problem by querying all servers and only returning
     a negative reply to the requestor only if *all* forwarders return negative
     responses.

  [Test Case]

   * It should be possible to test this in a virtual network. One DNS server
     should be responsible for queries to the outside world, and the other one
     could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
     IP addresses and names. It's important that at least one of these servers
     return REFUSED to queries that don't belong into its realm (assuming the
     domain name is "my.net", the server for "my.net" would reply REFUSED to
     "ubuntu.com" and every other domain. I am not sure if this is normally the
     case, all I can say is that my Linux-based ASUS router does it.

     Connect an Ubuntu VM to this network.

     To aggravate the problem, the DHCP server would put the internal DNS
     server first in the nameservers field. If that's the case, the problem
     would also occur if the client used "strict-order" in dnsmasq.conf.

  [Regression Potential]

   * I don't see any. Would there be networks where admins rely upon getting
     NXDOMAIN back if just one server fails for a DNS query? I don't know.

   * [racb] As the behaviour in the area of REFUSED and SERVFAIL is
  being changed, it's probably worth checking during SRU verification
  that dnsmasq correctly passes back successful, REFUSED, SERVFAIL,
  zero-answer and 1+ answer responses in the simple, single upstream DNS
  server case. If there is a regression introduced by these patches, it
  is likely to be in the area of handling SERVFAIL, REFUSED and
  successful replies.

  [Other Info]

  Original bug description follows.

  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.

  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local
  network, and 192.168.1.4 is the forwarder in my DSL Router,
  responsible to answer queries about the outside world. THe DHCP server
  returns these in the order 192.168.1.4,192.168.1.1. The internal
  server replies REFUSED to queries about external domains.

  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as
  various other OSes.

  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.

  I believe this is fixed in dnsmasq 2.76 and related to

  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2016q1/010263.html

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e
  http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6

  According to these sources, the bug was introduced with
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b

  In my local setup at least, I can work around the problem by using the
  "strict-order" option to dnsmasq.

  echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf

  But

[Touch-packages] [Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

This bug was fixed in the package dnsmasq - 2.76-5ubuntu0.2

---
dnsmasq (2.76-5ubuntu0.2) zesty; urgency=medium

  * Fix replying prematurely if one of many servers replies REFUSED
(LP: #1726017) by adding an upstream patche.
- 2.77: 68f6312d4b: Stop treating SERVFAIL as a successful response from
  upstream servers.

 -- Christian Ehrhardt   Mon, 23 Oct
2017 08:48:44 +0200

** Changed in: dnsmasq (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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Released
Status in dnsmasq source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * DNS name resolution fails in certain network configurations, where
     different DNS servers are responsible for different domains and one or
     more servers reply REFUSED to queries that regard other domains than
     their own. Without the patch, dnsmasq returns a negative reply to
     if only one such negative answer is received from a forwarder, even
     if other forwarders return valid responses.

     This breaks
     the resolver and practically all internet connectivity, including web
     browsing, email, and receiving updates.

   * This should be backported to stable to fix internet connectivity
     for users.

   * The patch fixes the problem by querying all servers and only returning
     a negative reply to the requestor only if *all* forwarders return negative
     responses.

  [Test Case]

   * It should be possible to test this in a virtual network. One DNS server
     should be responsible for queries to the outside world, and the other one
     could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
     IP addresses and names. It's important that at least one of these servers
     return REFUSED to queries that don't belong into its realm (assuming the
     domain name is "my.net", the server for "my.net" would reply REFUSED to
     "ubuntu.com" and every other domain. I am not sure if this is normally the
     case, all I can say is that my Linux-based ASUS router does it.

     Connect an Ubuntu VM to this network.

     To aggravate the problem, the DHCP server would put the internal DNS
     server first in the nameservers field. If that's the case, the problem
     would also occur if the client used "strict-order" in dnsmasq.conf.

  [Regression Potential]

   * I don't see any. Would there be networks where admins rely upon getting
     NXDOMAIN back if just one server fails for a DNS query? I don't know.

   * [racb] As the behaviour in the area of REFUSED and SERVFAIL is
  being changed, it's probably worth checking during SRU verification
  that dnsmasq correctly passes back successful, REFUSED, SERVFAIL,
  zero-answer and 1+ answer responses in the simple, single upstream DNS
  server case. If there is a regression introduced by these patches, it
  is likely to be in the area of handling SERVFAIL, REFUSED and
  successful replies.

  [Other Info]

  Original bug description follows.

  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.

  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local
  network, and 192.168.1.4 is the forwarder in my DSL Router,
  responsible to answer queries about the outside world. THe DHCP server
  returns these in the order 192.168.1.4,192.168.1.1. The internal
  server replies REFUSED to queries about external domains.

  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as
  various other OSes.

  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.

  I believe this is fixed in dnsmasq 2.76 and related to

  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2016q1/010263.html

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e
  http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6

  According to these sources, the bug was introduced with
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b

  In my local setup at least, I can work around the problem by using the
  "strict-order" option to dnsmasq.

  echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf

  But that's not a general solution. If dnsmasq has several forwarders,
  and some return SERVFAIL or REFUSED and

[Touch-packages] [Bug 1726017] Update Released

The verification of the Stable Release Update for dnsmasq 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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Released
Status in dnsmasq source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * DNS name resolution fails in certain network configurations, where
     different DNS servers are responsible for different domains and one or
     more servers reply REFUSED to queries that regard other domains than
     their own. Without the patch, dnsmasq returns a negative reply to
     if only one such negative answer is received from a forwarder, even
     if other forwarders return valid responses.

     This breaks
     the resolver and practically all internet connectivity, including web
     browsing, email, and receiving updates.

   * This should be backported to stable to fix internet connectivity
     for users.

   * The patch fixes the problem by querying all servers and only returning
     a negative reply to the requestor only if *all* forwarders return negative
     responses.

  [Test Case]

   * It should be possible to test this in a virtual network. One DNS server
     should be responsible for queries to the outside world, and the other one
     could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
     IP addresses and names. It's important that at least one of these servers
     return REFUSED to queries that don't belong into its realm (assuming the
     domain name is "my.net", the server for "my.net" would reply REFUSED to
     "ubuntu.com" and every other domain. I am not sure if this is normally the
     case, all I can say is that my Linux-based ASUS router does it.

     Connect an Ubuntu VM to this network.

     To aggravate the problem, the DHCP server would put the internal DNS
     server first in the nameservers field. If that's the case, the problem
     would also occur if the client used "strict-order" in dnsmasq.conf.

  [Regression Potential]

   * I don't see any. Would there be networks where admins rely upon getting
     NXDOMAIN back if just one server fails for a DNS query? I don't know.

   * [racb] As the behaviour in the area of REFUSED and SERVFAIL is
  being changed, it's probably worth checking during SRU verification
  that dnsmasq correctly passes back successful, REFUSED, SERVFAIL,
  zero-answer and 1+ answer responses in the simple, single upstream DNS
  server case. If there is a regression introduced by these patches, it
  is likely to be in the area of handling SERVFAIL, REFUSED and
  successful replies.

  [Other Info]

  Original bug description follows.

  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.

  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local
  network, and 192.168.1.4 is the forwarder in my DSL Router,
  responsible to answer queries about the outside world. THe DHCP server
  returns these in the order 192.168.1.4,192.168.1.1. The internal
  server replies REFUSED to queries about external domains.

  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as
  various other OSes.

  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.

  I believe this is fixed in dnsmasq 2.76 and related to

  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2016q1/010263.html

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e
  http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6

  According to these sources, the bug was introduced with
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b

  In my local setup at least, I can work around the problem by using the
  "strict-order" option to dnsmasq.

  echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf

  But that's not a general solution. If dnsmasq has several forwarders,
  and some return SERVFAIL or REFUSED and others return SUCCESS, the
  successful answer should be

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-11-21 Thread Mathieu Trudel-Lapierre

Verification done for isc-dhcp 4.3.5-3ubuntu1.1 as well:

If you manually enable using dhclient for ipv4 networking in the
initramfs, the system behaves as expected and correctly writes
DOMAINSEARCH in the /run/net-*.conf files. Ipv4 is not handled by
dhclient by default (but uses klibc instead) hence the need to modify
scripts.

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1699759] Re: LXC Alpine template broken on ppc64le

2017-11-21 Thread Stéphane Graber

It's in 17.10

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

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

Title:
  LXC Alpine template broken on ppc64le

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-14 07:36:33 ==
  LXC Alpine template is broken on Ubuntu 17.10, since it does not support 
ppc64le.

  It shows the following message:

  # Unknown architecture.

  == Comment: #1 - Breno Leitao  - 2017-06-14 07:37:50 ==
  Patch sent to upstream and accepted already:

  https://github.com/lxc/lxc/pull/1621#issuecomment-307887344

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+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 1699759] Re: LXC Alpine template broken on ppc64le

2017-11-21 Thread David Britton

** Changed in: lxc (Ubuntu)
 Assignee: David Britton (davidpbritton) => Stéphane Graber (stgraber)

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

Title:
  LXC Alpine template broken on ppc64le

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-14 07:36:33 ==
  LXC Alpine template is broken on Ubuntu 17.10, since it does not support 
ppc64le.

  It shows the following message:

  # Unknown architecture.

  == Comment: #1 - Breno Leitao  - 2017-06-14 07:37:50 ==
  Patch sent to upstream and accepted already:

  https://github.com/lxc/lxc/pull/1621#issuecomment-307887344

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

Stephan Fabel, to further root cause, could you login to a "GNOME
Flashback (Metacity)" session (not a compiz-based or Unity session) via
https://launchpad.net/ubuntu/+source/gnome-flashback and advise if the
flickering persists?

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

** Description changed:

- When I connect my laptop to my DisplayLink based device with USB
- (Wavlink universal USB 3.0 docking station
- https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
- Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
+ When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
+ https://launchpadlibrarian.net/346625588/20171121_131417.mp4
+ 
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.
  
  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or animation,
  the mouse pointer remains static and drawn.
  
  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor
  
  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.
  
  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.
  
  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.
  
  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713
  
  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for

[Touch-packages] [Bug 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

Original reporter's video of the issue.

** Attachment added: "20171121_131417.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+attachment/5012481/+files/20171121_131417.mp4

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2017-11-21 Thread timor

I can confirm bug on ASUS Zenbook UX305CA. I have laptop-mode and pm-
utils installed.

Let me know how can I help you to fix it.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

This bug was fixed in the package klibc - 2.0.4-8ubuntu4.1

---
klibc (2.0.4-8ubuntu4.1) zesty; urgency=medium

  * Write DNS domain in place of DOMAINSEARCH if that wasn't provided by the
DHCP server. (LP: #1713747)
- 0001-Write-DNS-domain-from-DHCP-if-we-have-no-DOMAINSEARC.patch

 -- Mathieu Trudel-Lapierre   Fri, 10 Nov 2017
16:35:19 -0500

** Changed in: klibc (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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1713747

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1713747] Update Released

2017-11-21 Thread Brian Murray

The verification of the Stable Release Update for klibc 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1713747

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.4

---
klibc (2.0.4-8ubuntu1.16.04.4) xenial; urgency=medium

  * Write DNS domain in place of DOMAINSEARCH if that wasn't provided by the
DHCP server. (LP: #1713747)
- 0001-Write-DNS-domain-from-DHCP-if-we-have-no-DOMAINSEARC.patch

 -- Mathieu Trudel-Lapierre   Fri, 10 Nov 2017
16:31:40 -0500

** Changed in: klibc (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 19353] Re: Tools relying on /etc/debian_version get confused

2017-11-21 Thread themusicgod1

** Tags added: bionic

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

Title:
  Tools relying on /etc/debian_version get confused

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  /etc/debian_version appears to be carried unmodified from Debian on Ubuntu 
systems. 
  This means that things like reportbug that use the information there to 
identify the 
  version of Debian that they are running on will identify Unbuntu systems as a 
Debian 
  version.

  Another approach would be to modify all the tools like reportbug to add their 
own 
  information or read /etc/ubuntu_version and prefer that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/19353/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2017-11-21 Thread Stephan Fabel

Sure, here it is: https://photos.app.goo.gl/5J2X3gsqGnNi8qwv2

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-11-21 Thread Mathieu Trudel-Lapierre

Verification-done for xenial with klibc 2.0.4-8ubuntu1.16.04.4:

I verified that updating klibc-utils to the new version yields a /run
/net-ens3.conf file that contains the proper value at DOMAINSEARCH=.

As for the above test on zesty, this involved modifying
scripts/functions to allow breaking the boot at initramfs after
networking to validate the file contents early.

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

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

Stephan Fabel, regarding the screencast not working, could you please
provide a camera picture of the screen?

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

2017-11-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "ust_2.7.1-1ubuntu0.1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

** Description changed:

  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.
  
  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or animation,
  the mouse pointer remains static and drawn.
  
  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor
  
  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.
  
  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.
  
  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.
  
  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713
+ 
+ WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
+ Clockwise
+ Anti-clockwise
+ 180 degrees
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-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
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  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.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

** Tags removed: potential-workaround

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I

[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

2017-11-21 Thread Martin Rosenau

I run Ubuntu 17.10 but I use Xorg instead of Wayland by default.

When I play some MP4 videos using VLC the entire system seems to freeze
but I still can move the mouse cursor (only keys and mouse buttons have
no effect any more).

The key combination Ctrl+Alt+F1 however still works - using this
combination I can log in with a different user.

Logged in as the other user everything works.

The only possibility to get the first user running again is to kill the
Xorg X server.

(Even killing VLC won't work.)

For this reason I assume that a bug in the X server is the problem.

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

Debdiff for artful

** Patch added: "ust_2.9.1-1ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+attachment/5012436/+files/ust_2.9.1-1ubuntu0.1.debdiff

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

Debdiff for zesty

** Patch added: "ust_2.9.0-1ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+attachment/5012432/+files/ust_2.9.0-1ubuntu0.1.debdiff

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

This is the debdiff for xenial.

** Patch added: "ust_2.7.1-1ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+attachment/5012431/+files/ust_2.7.1-1ubuntu0.1.debdiff

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733398] Re: gunzip fails with message : not in gzip format

2017-11-21 Thread Clive Johnston

It has been working fine all along until this past week or so.  I
upgraded my machine to Bionic via the sed route and needed to patch a
symbols file with that buildlog, but it won't gunzip it.  As I said,
I've never had any issues uncompressing buildlogs until now.

cliv...@kubuntu.org:~ $  apt-cache policy gzip
gzip:
  Installed: 1.6-5ubuntu1
  Candidate: 1.6-5ubuntu1
  Version table:
 *** 1.6-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

I have just noticed that the auto complete is inserting a / into the
filename at the epoch.  I renamed the file to test.txt.gz but it still
fails.

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

Title:
  gunzip fails with message : not in gzip format

Status in gzip package in Ubuntu:
  Incomplete

Bug description:
  I use "gzip -d" or "gunzip" to extract build logs to update the
  symbols.  For example:

  wget https://launchpad.net/~kubuntu-
  ci/+archive/ubuntu/unstable/+build/13749931/+files/buildlog_ubuntu-
  bionic-
  amd64.kf5-messagelib_4%3A17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz

  gunzip buildlog_ubuntu-bionic-
  amd64.kf5-messagelib_4\:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz

  However, on Bionic this last command fails with:

  gzip: buildlog_ubuntu-bionic-
  amd64.kf5-messagelib_4:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz:
  not in gzip format

  
  The same file extracts on other systems, just not Bionic 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1733398/+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 1733683] [NEW] python3-lttngust tries to load unversionned agent library

Public bug reported:

The python3-lttngust package contains bindings that use ctypes to
interact with a dedicated library provided by the liblttng-ust-python-
agent0. The python code loads the library by name but it targets the un-
versioned ".so" which is part of the dev package.

This means that when installed without the dev package the bindings
won't work.

The fix is to load the library by name and use the SONAME version
".so.0".

I'll provide a debdiff for the affected versions.

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

** Affects: ust (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: ust (Ubuntu Zesty)
 Importance: Undecided
 Status: New

** Affects: ust (Ubuntu Artful)
 Importance: Undecided
 Status: New

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

2017-11-21 Thread Stéphane Graber

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

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

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

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  New
Status in ust source package in Zesty:
  New
Status in ust source package in Artful:
  New

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

2017-11-21 Thread David Glasser

This is my first attempt at a debdiff and an SRU. I'd love to know if
I've filed it properly!

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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 1727237] Re: systemd-resolved is not finding a domain

2017-11-21 Thread Seth Arnold

I thought I'd add the information from my favourite DNS debugging tool
while the data may still be close to useful:

dnsviz reports NXDOMAIN for securelogin.arubanetworks.com
http://dnsviz.net/d/securelogin.arubanetworks.com/dnssec/

dnsviz also currently reports three warnings:

- com to arubanetworks.com: Authoritative  records exist for 
dns5.arubanetworks.com, but there are no corresponding  glue records.
- com to arubanetworks.com: The following NS name(s) were found in the 
authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com 
zone): dns6.arubanetworks.com
- com to arubanetworks.com: The following NS name(s) were found in the 
delegation NS RRset (i.e., in the com zone), but not in the authoritative NS 
RRset: dns4.arubanetworks.com

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1733669] Re: bootloader problem

2017-11-21 Thread Rawa Omer

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

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

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

Title:
  bootloader problem

Status in xorg package in Ubuntu:
  New

Bug description:
  when installing ubuntu 16.04 an error will occur saying that the grub
  bootloader is missing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  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 Nov 21 21:13:55 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: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
 Subsystem: Lenovo GM108M [GeForce 840M] [17aa:380d]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: LENOVO 20354
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN91WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  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 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: Tue Nov 21 21:09:38 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  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/1733669/+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 1733669] Re: bootloader problem

2017-11-21 Thread Rawa Omer

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

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

Title:
  bootloader problem

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  when installing ubuntu 16.04 an error will occur saying that the grub
  bootloader is missing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  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 Nov 21 21:13:55 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: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
 Subsystem: Lenovo GM108M [GeForce 840M] [17aa:380d]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: LENOVO 20354
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN91WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  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 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: Tue Nov 21 21:09:38 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  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/1733669/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-11-21 Thread huerben

Install the ubuntu-artwork packages via synaptic do not change the file 
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc
I don now why. 

so i copy the file from Marco Trevisan manualy in the file., do restart,

no error message in the terminal, but kompozer still not start.

$ kompozer
xxx@x:~$

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1733669] [NEW] bootloader problem

2017-11-21 Thread Rawa Omer

Public bug reported:

when installing ubuntu 16.04 an error will occur saying that the grub
bootloader is missing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
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 Nov 21 21:13:55 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: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
   Subsystem: Lenovo GM108M [GeForce 840M] [17aa:380d]
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 20354
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash ---
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN91WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A5
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
dmi.product.name: 20354
dmi.product.version: Lenovo Z50-70
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 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: Tue Nov 21 21:09:38 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


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

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

Title:
  bootloader problem

Status in xorg package in Ubuntu:
  New

Bug description:
  when installing ubuntu 16.04 an error will occur saying that the grub
  bootloader is missing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  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 Nov 21 21:13:55 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: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
 Subsystem: Lenovo GM108M [GeForce 840M] [17aa:380d]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: LENOVO 20354
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-11-21 Thread huerben

@Marco Trevisan (Treviño) (3v1n0) 
Is there no lin30 in your file?? I don see it.

line 30 in my file is:
30 class "GtkScrollbar" style "murrine-scrollbar"

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1733667] [NEW] bluetooth service does not start on reboot

2017-11-21 Thread Wolf Rogner

Public bug reported:

$ uname -a
Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

Just updated to latest repo kernel.

After reboot, the bluetoothd gets started but not activated.

Restarting does not work (error msg in bluetooth panel: adapter not
found - it was there before the reboot).

Required several reboots to fix the issue (i.e. after a reboot I have to
reboot several times, click the mouse frantically during boot to get it
recognized somewhere during the bootup).

I remember this to have happened two kernels before so I think it is a
regression.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluez 5.46-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 21 18:58:04 2017
InstallationDate: Installed on 2017-10-20 (32 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:32:75:9F:91:1E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:28328 acl:854 sco:0 events:231 errors:0
TX bytes:6881 acl:65 sco:0 commands:121 errors:0

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  bluetooth service does not start on reboot

Status in bluez package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  Just updated to latest repo kernel.

  After reboot, the bluetoothd gets started but not activated.

  Restarting does not work (error msg in bluetooth panel: adapter not
  found - it was there before the reboot).

  Required several reboots to fix the issue (i.e. after a reboot I have
  to reboot several times, click the mouse frantically during boot to
  get it recognized somewhere during the bootup).

  I remember this to have happened two kernels before so I think it is a
  regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 18:58:04 2017
  InstallationDate: Installed on 2017-10-20 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias:

[Touch-packages] [Bug 1577215] Re: Origin pattern is unexpected on dpkg-reconfigure

2017-11-21 Thread Jan Claeys

Also, what about the other settings (e.g. package blacklist) in that
file?  Does/should it preserve those, warn about overwriting them, ...?

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

Title:
  Origin pattern is unexpected on dpkg-reconfigure

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  In testing out the new unattended-upgrades behaviour I was asked an
  unexpected question about the "unattended-upgrades Origin-Pattern".
  This is not a great experience, it doesn't match anything other than
  internal code patterns.

  For example, the default offered does NOT look like a sensible Ubuntu
  default for Ubuntu users:

"origin=Debian,codename=${distro_codename},label=Debian-
  Security";___

  Is that correct, or a mistake?

  What I would expect is simply this:

   Install security updates (Y/N)
   Install performance and reliability updates (Y/N)
   Install updates from unofficial archives (Y/N)

  The latter would map to all PPAs etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10

2017-11-21 Thread Segher

I did what Tim suggested on a fresh install of Ubuntu 17.10 nut it
doesn’t work on my laptop with GeForce GTX 1060. Still boots to a black
screen. Booting with HDMI cable connected however, does work fine.
Optimus is not available in NVIDIA settings. Is this a different bug?

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

Title:
  Black Screen after Upgrade from Kubuntu 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the
  same Result:

  After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'.
  This kernel does not work with the nvidia-grafic-card and lead to a black 
screen.

  After purging this kernel in a tty-session it booted up smothely.

  I think this can help many others.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Oct 20 09:57:26 2017
  DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] 
[1458:362d]
  InstallationDate: Installed on 2016-12-23 (300 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 062a:4102 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22d
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Gaming 3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 1732522] Re: [2.3] Ephemeral boot environment does not renew DHCP leases

2017-11-21 Thread Andres Rodriguez

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

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

Title:
  [2.3] Ephemeral boot environment does not renew DHCP leases

Status in cloud-init:
  New
Status in MAAS:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I started commissioning+hardware testing on a machine, and while the
  machine was testing (for 2hrs+) i noticed that the IP address had
  disappeared. The machine has the MAC of  00:25:90:4c:e7:9e and IP of
  192.168.0.211 from the dynamic range.

  Checking the MAAS server, I noticed that the IP/MAC was in the ARP
  table:

  andreserl@maas:/var/lib/maas/dhcp$ arp -a | grep 211
  192-168-9-211.maas (192.168.9.211) at 00:25:90:4c:e7:9e [ether] on bond-lan

  Checking the leases file has the following:
  http://pastebin.ubuntu.com/25969442/

  Then I checked a couple areas of MAAS:
   - Device discovery, the machine wasn't there.
   - Subnet details page, the machine wasn't there (e.g. as observed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1732522/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

2017-11-21 Thread Mikko Rantalainen

Should it be safe to install ligthdm package from zesty to xenial to
test if it fixes the issue? (https://packages.ubuntu.com/zesty/lightdm
version 1.22.0-0ubuntu2.1)

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

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del 
pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted 
system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from 
org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that "getting session list timeout", 
which is about a minute later than vt7, and does not have a password input 
field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/997483/+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 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

2017-11-21 Thread Manoj Iyer

** Changed in: apparmor (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
John Johansen (jjohansen)

** Changed in: ubuntu-power-systems
 Assignee: John Johansen (jjohansen) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  Incomplete
Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info :

[Touch-packages] [Bug 1732069] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  I can't update the any software in my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Nov 13 10:47:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-13  10:47:10
   Commandline: apt-get -f install
   Requested-By: mahima (1000)
   Upgrade: libtcmalloc-minimal4:amd64 (2.4-0ubuntu5, 2.4-0ubuntu5.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-22 (448 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1732069/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2017-11-21 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
 Assignee: David Britton (davidpbritton) => Canonical Server Team 
(canonical-server)

** Changed in: util-linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
David Britton (davidpbritton)

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080,

[Touch-packages] [Bug 1577215] Re: Origin pattern is unexpected on dpkg-reconfigure

2017-11-21 Thread Andreas Hasenack

Confirmed that in bionic it offers this Origins-Pattern in the
"Configuring unattended-upgrades" debconf question:

"origin=Debian,codename=${distro_codename},label=Debian-Security";

That should be Ubuntu, or ${distro_id} perhaps. That being said, it
doesn't seem to be used in the end, because my 50unattended-upgrades
file has no mention of Debian and uses ${distro_id} everywhere.

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

Title:
  Origin pattern is unexpected on dpkg-reconfigure

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  In testing out the new unattended-upgrades behaviour I was asked an
  unexpected question about the "unattended-upgrades Origin-Pattern".
  This is not a great experience, it doesn't match anything other than
  internal code patterns.

  For example, the default offered does NOT look like a sensible Ubuntu
  default for Ubuntu users:

"origin=Debian,codename=${distro_codename},label=Debian-
  Security";___

  Is that correct, or a mistake?

  What I would expect is simply this:

   Install security updates (Y/N)
   Install performance and reliability updates (Y/N)
   Install updates from unofficial archives (Y/N)

  The latter would map to all PPAs etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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 1733398] Re: gunzip fails with message : not in gzip format

2017-11-21 Thread Brian Murray

I was unable to recreate this in a bionic schroot.

(bionic-amd64)root@impulse:/tmp# apt-cache policy gzip  
   
gzip:
  Installed: 1.6-5ubuntu1
  Candidate: 1.6-5ubuntu1
  Version table:
 *** 1.6-5ubuntu1 500
500 http://192.168.10.7/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+build/13749931/+files/buildlog_ubuntu-bionic-amd64.kf5-messagelib_4%3A17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz
Resolving launchpad.net (launchpad.net)... 91.189.89.223, 91.189.89.222
Connecting to launchpad.net (launchpad.net)|91.189.89.223|:443... connected.
HTTP request sent, awaiting response... 303 See Other
Location: 
https://launchpadlibrarian.net/346383456/buildlog_ubuntu-bionic-amd64.kf5-messagelib_4%3A17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz
 [following]
--2017-11-21 16:48:57--  
https://launchpadlibrarian.net/346383456/buildlog_ubuntu-bionic-amd64.kf5-messagelib_4%3A17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz
Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 91.189.89.229, 
91.189.89.228
Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|91.189.89.229|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 162991 (159K) [text/plain]
Saving to: 
'buildlog_ubuntu-bionic-amd64.kf5-messagelib_4:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz'

buildlog_ubuntu-bionic-amd64.kf5-messag
100%[==>]
159.17K   319KB/sin 0.5s

2017-11-21 16:48:59 (319 KB/s) - 'buildlog_ubuntu-bionic-
amd64.kf5-messagelib_4:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz'
saved [162991/162991]

(bionic-amd64)root@impulse:/tmp# gunzip 
buildlog_ubuntu-bionic-amd64.kf5-messagelib_4\:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz
 
(bionic-amd64)root@impulse:/tmp# ls
buildlog_ubuntu-bionic-amd64.kf5-messagelib_4:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt

Could you double check or provide some more information on how I might
recreate this? Its also worth noting that the version of gunzip in
artful and bionic is the same one.

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

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

Title:
  gunzip fails with message : not in gzip format

Status in gzip package in Ubuntu:
  Incomplete

Bug description:
  I use "gzip -d" or "gunzip" to extract build logs to update the
  symbols.  For example:

  wget https://launchpad.net/~kubuntu-
  ci/+archive/ubuntu/unstable/+build/13749931/+files/buildlog_ubuntu-
  bionic-
  amd64.kf5-messagelib_4%3A17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz

  gunzip buildlog_ubuntu-bionic-
  amd64.kf5-messagelib_4\:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz

  However, on Bionic this last command fails with:

  gzip: buildlog_ubuntu-bionic-
  amd64.kf5-messagelib_4:17.11.80+p18.04+git20171119.2017-0_BUILDING.txt.gz:
  not in gzip format

  
  The same file extracts on other systems, just not Bionic 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1733398/+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 1733644] [NEW] Logging in while docked causes system to suspend

2017-11-21 Thread Nicholas Hollander

Public bug reported:

This issue is only present to the best of my knowledge on the Dell XPS
9560 while connected to a docking station, in this case the Dell WD-15.
When logging in to the computer from a cold boot, the computer will go
to sleep immediately after logging in.  This issue does not happen if
the lid of the laptop is open, or if the computer is waking from sleep.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.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  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 21 11:43:18 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2017-10-31 (20 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=301dbbe4-b5ce-48cc-b1fc-f59a051d8bdb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Logging in while docked causes system to suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  This issue is only present to the best of my knowledge on the Dell XPS
  9560 while connected to a docking station, in this case the Dell
  WD-15.  When logging in to the computer from a cold boot, the computer
  will go to sleep immediately after logging in.  This issue does not
  happen if the lid of the laptop is open, or if the computer is waking
  from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .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  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 11:43:18 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem:

[Touch-packages] [Bug 1732447] Re: rename no longer included in perl package, but still linked

2017-11-21 Thread Brian Murray

I was able to recreate this Ubuntu 17.10.

(artful-amd64)root@impulse:/home/bdmurray/source-trees/ubuntu-archive-tools/upstream#
 rename
The program 'rename' can be found in the following packages:
 * perl
 * rename
Try: apt install 
(artful-amd64)root@impulse:/home/bdmurray/source-trees/ubuntu-archive-tools/upstream#
 apt-cache policy perl
perl:
  Installed: 5.26.0-8ubuntu1
  Candidate: 5.26.0-8ubuntu1
  Version table:
 *** 5.26.0-8ubuntu1 500
500 http://192.168.10.7/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status


** Changed in: command-not-found (Ubuntu)
   Status: New => Triaged

** Changed in: command-not-found (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: artful

** Tags added: rls-bb-incoming

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

Title:
  rename no longer included in perl package, but still linked

Status in command-not-found package in Ubuntu:
  Triaged
Status in perl package in Ubuntu:
  Invalid

Bug description:
  typing "rename" in a terminal responds with...
   
  The program 'rename' can be found in the following packages:
   * perl
   * rename
  Ask your administrator to install one of them

  ...but perl is already installed.  Internet reports suggest this has
  started in 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: perl 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 15 16:24:29 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: perl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1732447/+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 1411487] Re: [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem random)

2017-11-21 Thread Bug Watch Updater

** Changed in: gnome-bluetooth
   Status: Incomplete => Expired

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

Title:
  [GNOME gnome-control-center] Not work AD2P in device HV-800 (problem
  random)

Status in GNOME Bluetooth:
  Expired
Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  Attach video.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 15 23:27:34 2015
  InstallationDate: Installed on 2014-09-25 (113 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw vt.handoff=7 init=/lib/systemd/systemd
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3923189 acl:28369 sco:67913 events:523 errors:0
TX bytes:3351604 acl:260 sco:65569 commands:111 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1411487/+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 1535048] Re: i915 driver seems to cause system crash at random

2017-11-21 Thread Tyson Tan

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

Here is the crach log and further discussion linked by the bug reporter on 
archlinux:
https://github.com/nisenbeck/ct-server-2016-jessie/issues/1

** Attachment added: "intel_crash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535048/+attachment/5012275/+files/intel_crash.txt

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
  VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y 
axis) 338mm x 270mm
 1280x1024 60.02*+ 75.02
 1152x864 75.00
 1024x768 75.08 70.07 60.00
 832x624 74.55
 800x600 72.19 75.00 60.32 56.25
 640x480 75.00 72.81 66.67 60.00
 720x400 70.08
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  The program 'fglrxinfo' can be found in the following packages:
   * fglrx
   * fglrx-updates
  Try: sudo apt-get install 
  The program 'nvidia-settings' is currently not installed. You can install it 
by typing:
  sudo apt-get install nvidia-settings
  H/W path Device Class Description
  ===
  system Computer
  /0 bus Motherboard
  /0/0 memory 1991MiB System memory
  /0/1 processor Intel(R) Pentium(R)

[Touch-packages] [Bug 1535048] Re: i915 driver seems to cause system crash at random

2017-11-21 Thread Tyson Tan

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

I have a machine with intel Skylake and it is suffering random reboot.
Although I'm not familiar with hardware side of things, please let me
know if there is anything I can help.

Meanwhile, the archlinux community has a similar report but they suspect i915 
firmware.
https://bugs.archlinux.org/task/53227

** Bug watch added: github.com/nisenbeck/ct-server-2016-jessie/issues #1
   https://github.com/nisenbeck/ct-server-2016-jessie/issues/1

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
  VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y 
axis) 338mm x 270mm
 1280x1024 60.02*+ 75.02
 1152x864 75.00
 1024x768 75.08 70.07 60.00
 832x624 74.55
 800x600 72.19 75.00 60.32 56.25
 640x480 75.00 72.81 66.67 60.00
 720x400 70.08
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  The program 'fglrxinfo' can be found in the following packages:
   * fglrx
   * fglrx-updates
  Try: sudo apt-get install 
  The program 'nvidia-settings' is currently not installed. You can install it 
by typing:
  sudo apt-get install nvidia-settings
  H/W path Device Class Description

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

2017-11-21 Thread Will Cooke

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

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

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-11-21 Thread Mathieu Trudel-Lapierre

Verification-done for zesty, with klibc-utils 2.0.4-8ubuntu4.1:

I updated klibc-utils and libklic; then modified the initramfs
scripts/functions to add "maybe-break networking" to the end of
configure_networking(); and rebooted with 'ip=dhcp break=networking'. I
could then verify the contents of /run/net-ens3.conf from the initramfs
environment; which checks out: DOMAINSEARCH shows the right value for
this network: "nat", same as DNSDOMAIN.

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

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1552792] Re: gnome software leaves dependencies installed

2017-11-21 Thread AsciiWolf

Slightly related issue: https://bugs.launchpad.net/ubuntu/+source/gnome-
software/+bug/1528028

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

Title:
  gnome software leaves dependencies installed

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software to install an application - removal of that
  package leaves behind dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  
  sudo apt-get autoremove 
  [sudo] password for wolf: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  
  After cleaning up and then reinstalling with gnome software, followed by the 
removal

  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1552792/+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 1733613] [NEW] package libqtcore4 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/xdg/Trolltech.conf », qui est différent d'autres instances du paq

2017-11-21 Thread Yannig Coulomb

Public bug reported:

impossible d'installé un logitiel ou de mettre à jour ubuntu

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libqtcore4 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 libqtcore4:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Nov 21 15:46:43 2017
DpkgHistoryLog:
 Start-Date: 2017-11-21  15:46:40
 Commandline: apt-get install -f
 Requested-By: utilisateur (1000)
 Install: libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1, automatic)
ErrorMessage: tentative de remplacement de « /etc/xdg/Trolltech.conf », qui est 
différent d'autres instances du paquet libqtcore4:amd64
InstallationDate: Installed on 2017-06-29 (144 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: qt4-x11
Title: package libqtcore4 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/xdg/Trolltech.conf », qui est différent d'autres 
instances du paquet libqtcore4:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade:
  tentative de remplacement de « /etc/xdg/Trolltech.conf », qui est
  différent d'autres instances du paquet libqtcore4:amd64

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  impossible d'installé un logitiel ou de mettre à jour ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libqtcore4:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Nov 21 15:46:43 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-21  15:46:40
   Commandline: apt-get install -f
   Requested-By: utilisateur (1000)
   Install: libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1, automatic)
  ErrorMessage: tentative de remplacement de « /etc/xdg/Trolltech.conf », qui 
est différent d'autres instances du paquet libqtcore4:amd64
  InstallationDate: Installed on 2017-06-29 (144 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: 
tentative de remplacement de « /etc/xdg/Trolltech.conf », qui est différent 
d'autres instances du paquet libqtcore4:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1733613/+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 1462723] RE

2017-11-21 Thread Tomas Van Verrewegen

Check 
[Bug 1462723] Re: lightdm quits at startup when beamer is connected

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

Title:
  lightdm quits at startup when beamer is connected

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  I have a beamer. Since installation of kubuntu-15.04 I can't log into
  my account if the beamer is connected. The kubuntu splash screen show
  up alright, but takes a bit longer to complete, then I am dropped into
  a black screen with a (movable) mouse pointer.

  If I disconnect the beamer during startup, I can login.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jun  7 10:15:33 2015
  InstallationDate: Installed on 2015-03-16 (82 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1462723/+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 1713508] Re: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: problemas de dependencias - se deja sin configurar

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

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

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

Title:
  package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  El sistema puso el aviso

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   640:0:116:142134:2017-08-28 11:02:42.357357740 -0300:2017-08-28 
11:02:45.133304945 -0300:/var/crash/apport.0.crash
   644:0:116:0:2017-08-28 11:02:45.133304945 -0300:2017-08-28 
11:02:45.133304945 -0300:/var/crash/apport.0.upload
   600:109:116:0:2017-08-28 11:02:48.793189539 -0300:2017-08-28 
11:02:48.793189539 -0300:/var/crash/apport.0.uploaded
   600:0:116:127426:2017-08-28 11:01:20.158540487 -0300:2017-08-28 
11:02:59.644799651 -0300:/var/crash/apport-gtk.0.crash
  Date: Mon Aug 28 11:01:21 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2015-08-11 (747 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (385 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1713508/+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 1733597] Re: "gio open" handles mailto: links wrong, putting /// at the start of the email address

2017-11-21 Thread Bug Watch Updater

** Changed in: glib
   Status: Unknown => Fix Released

** Changed in: glib
   Importance: Unknown => Medium

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

Title:
  "gio open" handles mailto: links wrong, putting /// at the start of
  the email address

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  "gio open mailto:user@host; results in gio executing "thunderbird
  mailto:///user@host;, which is wrong and causes the address that shows
  up in the thunderbird composition window to start with three slashes
  when it shouldn't.

  Proof, from "strace gio open mailto:user@host; output:

  16976 execve("/usr/bin/gio", ["gio", "open", "mailto:user@host;], [/* 76 vars 
*/]) = 0
  16980 execve("/usr/bin/thunderbird", ["thunderbird", "mailto:///user@host;], 
[/* 78 vars */] 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 08:39:42 2017
  InstallationDate: Installed on 2017-05-19 (185 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to artful on 2017-10-20 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1733597/+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 1733597] Re: "gio open" handles mailto: links wrong, putting /// at the start of the email address

2017-11-21 Thread Sebastien Bacher

Thanks, that was already reported upstream as
https://bugzilla.gnome.org/show_bug.cgi?id=779182 and is fixed in
upstream git

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Committed

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: glib
 Remote watch: GNOME Bug Tracker #790664 => GNOME Bug Tracker #779182

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

Title:
  "gio open" handles mailto: links wrong, putting /// at the start of
  the email address

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  "gio open mailto:user@host; results in gio executing "thunderbird
  mailto:///user@host;, which is wrong and causes the address that shows
  up in the thunderbird composition window to start with three slashes
  when it shouldn't.

  Proof, from "strace gio open mailto:user@host; output:

  16976 execve("/usr/bin/gio", ["gio", "open", "mailto:user@host;], [/* 76 vars 
*/]) = 0
  16980 execve("/usr/bin/thunderbird", ["thunderbird", "mailto:///user@host;], 
[/* 78 vars */] 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 08:39:42 2017
  InstallationDate: Installed on 2017-05-19 (185 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to artful on 2017-10-20 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1733597/+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 1732876] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-21 Thread Evgraphov Alexey

I found a solution. There was the printer driver earlier installed that
I downloaded from the supplier's website. Printer model Xerox wc3210.
After uninstalling the driver all work properly.

** Description changed:

  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:
  
  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)
  
  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
-  600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
-  640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
+  600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
+  640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.2
-  apt  1.2.24
+  dpkg 1.18.4ubuntu1.2
+  apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:

  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 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/apport/+bug/1732876/+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 1732876] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-21 Thread Evgraphov Alexey

I found a solution. There was the printer driver earlier installed that
I downloaded from the supplier's website. Printer model Xerox wc3210.
After uninstalling the driver all work properly.

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:

  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 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/apport/+bug/1732876/+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 1733597] [NEW] "gio open" handles mailto: links wrong, putting /// at the start of the email address

2017-11-21 Thread Jonathan Kamens

Public bug reported:

"gio open mailto:user@host; results in gio executing "thunderbird
mailto:///user@host;, which is wrong and causes the address that shows
up in the thunderbird composition window to start with three slashes
when it shouldn't.

Proof, from "strace gio open mailto:user@host; output:

16976 execve("/usr/bin/gio", ["gio", "open", "mailto:user@host;], [/* 76 vars 
*/]) = 0
16980 execve("/usr/bin/thunderbird", ["thunderbird", "mailto:///user@host;], 
[/* 78 vars */] 

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libglib2.0-bin 2.54.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 21 08:39:42 2017
InstallationDate: Installed on 2017-05-19 (185 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: glib2.0
UpgradeStatus: Upgraded to artful on 2017-10-20 (31 days ago)

** Affects: glib
 Importance: Unknown
 Status: Unknown

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

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

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

Title:
  "gio open" handles mailto: links wrong, putting /// at the start of
  the email address

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  "gio open mailto:user@host; results in gio executing "thunderbird
  mailto:///user@host;, which is wrong and causes the address that shows
  up in the thunderbird composition window to start with three slashes
  when it shouldn't.

  Proof, from "strace gio open mailto:user@host; output:

  16976 execve("/usr/bin/gio", ["gio", "open", "mailto:user@host;], [/* 76 vars 
*/]) = 0
  16980 execve("/usr/bin/thunderbird", ["thunderbird", "mailto:///user@host;], 
[/* 78 vars */] 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 08:39:42 2017
  InstallationDate: Installed on 2017-05-19 (185 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to artful on 2017-10-20 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1733597/+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 1727237] Re: systemd-resolved is not finding a domain

2017-11-21 Thread Rob Schultz

The issue is with systemd-resolvd not adding the captive portal DNS
after the logon. This worked fine with dnsmasq in 16.04 (and I assume
17.04).

For my laptop I have currently changed to 'unbound' for DNS resolution.
Note: If you are running Qemu/KVM you will want to keep dnsmasq-base
package.

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

2017-11-21 Thread Bug Watch Updater

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

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Won't Fix
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Hardware name: SATELLITE Z830
  [26932.384358] Modules linked in: sdhci_pci

[Touch-packages] [Bug 1731699] Re: Unable to transfer files via bluetooth to paired android phone

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

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

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+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 1733567] [NEW] apport fails to send crash reports

2017-11-21 Thread Rachel Greenham

Public bug reported:

There's an ongoing issue with gnome-shell crashing during or on exit
from screen lock. I am no longer able to report when this happens
because apport silently refuses to send the bug report.

If the automatic whoopsie dialog opens at all (it doesn't, often), and I
click to send the report, the window closes, and that's it. If I try to
use apport-cli to send a specific .crash file, it shows me the menu, I
type S to send the report, and apport-cli exits immediately, and again
there's no further action.

The crashes may be similar to those posted before, although this being
an ongoing and unfixed issue (eg: bug #1723620, bug #1723615), one would
expect to be able to send updated bug reports at least to show that, eg:
a newer version of the affected packages didn't fix it, or to add a new
observation (in this case that despite the crash my login session was
not ended by it, which is new). At the very least one would expect to
see either the list of possible duplicates, or at very *very* least, a
message saying that it's been submitted alreadyk or that my version of
the affected package is obsolete (it isn't, although I see apport itself
is getting an upgrade, but this problem has already persisted through a
few apport upgrades). But there's nothing, no feedback at all, it just
exits.

I wonder also if what's failed here is the ability to open a new browser
window, but if so it affects both google chrome and firefox, when each
is set to be the default browser. Also, *this* bug, initiated by typing
"ubuntu-bug apport", was submitted just fine, but this bug is not the
result of an actual *crash* (ie: resulting in a .crash file).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.4
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: called for pid 24462, 
signal 11, core limit 0, dump mode 1
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 7178) Tue Nov 21 11:06:06 2017: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 21 11:15:54 2017
InstallationDate: Installed on 2017-07-30 (113 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to artful on 2017-08-22 (90 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  apport fails to send crash reports

Status in apport package in Ubuntu:
  New

Bug description:
  There's an ongoing issue with gnome-shell crashing during or on exit
  from screen lock. I am no longer able to report when this happens
  because apport silently refuses to send the bug report.

  If the automatic whoopsie dialog opens at all (it doesn't, often), and
  I click to send the report, the window closes, and that's it. If I try
  to use apport-cli to send a specific .crash file, it shows me the
  menu, I type S to send the report, and apport-cli exits immediately,
  and again there's no further action.

  The crashes may be similar to those posted before, although this being
  an ongoing and unfixed issue (eg: bug #1723620, bug #1723615), one
  would expect to be able to send updated bug reports at least to show
  that, eg: a newer version of the affected packages didn't fix it, or
  to add a new observation (in this case that despite the crash my login
  session was not ended by it, which is new). At the very least one
  would expect to see either the list of possible duplicates, or at very
  *very* least, a message saying that it's been submitted alreadyk or
  that my version of the affected package is obsolete (it isn't,
  although I see apport itself is getting an upgrade, but this problem
  has already persisted through a few apport upgrades). But there's
  nothing, no feedback at all, it just exits.

  I wonder also if what's failed here is the ability to open a new
  browser window, but if so it affects both google chrome and firefox,
  when each is set to be the default browser. Also, *this* bug,
  initiated by typing "ubuntu-bug apport", was submitted just fine, but
  this bug is not the result of an actual *crash* (ie: resulting in a
  .crash file).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64

[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

2017-11-21 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: gnome-control-center (Ubuntu) => gnome-online-
accounts (Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Low

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

Title:
Google Online Account Two Factor with hardware key fails immediately

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

Bug description:
The hardware key authentication two factor fails immediately with a
web based retry dialogue when connecting a Google account to the
online accounts in settings using a hardware key second factor.

Steps to reproduce:
1. Set Google Account to default to a hardware security key like a Yubikey or
other FIDO standard key after having two factor authentication enabled on your
Google Account.
2. Open Online accounts
3. Add a Google Account
4. Enter google email address
5. Enter google password
6. (this is the login flow of two factor, if default is the hardware key the
error should appear).

Work around:
Choose use another method to authenticate: enter the authentication code and
you will proceed.

Expectations were:
The ability to use the hardware key to authenticate as the second factor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 17 16:01:11 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
ProcEnviron:
XDG_RUNTIME_DIR=
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1733002/+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 1599401] Re: mate-settings-daemon crashed with signal 5 in _XReply()

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  mate-settings-daemon crashed with signal 5 in _XReply()

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  polihron@polihron-K56CA:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mate-settings-daemon 1.14.0-1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Jul  6 10:50:49 2016
  ExecutablePath: /usr/bin/mate-settings-daemon
  InstallationDate: Installed on 2016-07-01 (4 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160629.1)
  ProcCmdline: /usr/bin/mate-settings-daemon
  Signal: 5
  SourcePackage: mate-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: mate-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1599401/+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 1733002] [NEW] Google Online Account Two Factor with hardware key fails immediately

You have been subscribed to a public bug:

The hardware key authentication two factor fails immediately with a web
based retry dialogue when connecting a Google account to the online
accounts in settings using a hardware key second factor.

Steps to reproduce:
1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
2. Open Online accounts
3. Add a Google Account
4. Enter google email address
5. Enter google password
6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

Work around:
Choose use another method to authenticate: enter the authentication code and 
you will proceed.

Expectations were:
The ability to use the hardware key to authenticate as the second factor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 17 16:01:11 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug artful third-party-packages
-- 
Google Online Account Two Factor with hardware key fails immediately
https://bugs.launchpad.net/bugs/1733002
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts 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 1680436] Re: notification-area-applet crashed with signal 5 in _XReply()

2017-11-21 Thread Vlad Orlov

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

** Package changed: mate-panel (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1599401
   mate-settings-daemon crashed with signal 5 in _XReply()

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

Title:
  notification-area-applet crashed with signal 5 in _XReply()

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-panel 1.18.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Apr  6 12:58:12 2017
  ExecutablePath: /usr/lib/mate-panel/notification-area-applet
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/mate-panel/notification-area-applet
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=pt:pt_BR:en
   LANG=pt_PT.UTF-8
  Signal: 5
  SourcePackage: mate-panel
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: notification-area-applet crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1680436/+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 1733557] [NEW] Login screen showing Authentication Failed Switch to greeter...

2017-11-21 Thread Andrew Neeson

Public bug reported:

When I lock my machine, the login screen shows my current user with the
message: "Authentication Failed"

..and in the position when the password normally exists, the option
"Switch to greeter..."

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Nov 21 10:28:47 2017
InstallationDate: Installed on 2017-04-17 (217 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

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


** Tags: amd64 apport-bug artful

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

** No longer affects: gnome-control-center (Ubuntu)

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

Title:
  Login screen showing Authentication Failed Switch to greeter...

Status in lightdm package in Ubuntu:
  New

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+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 1680436] [NEW] notification-area-applet crashed with signal 5 in _XReply()