[Touch-packages] [Bug 1837174] [NEW] auto compress if save filename ends with .gz

[Yuan-Chen Cheng]

Public bug reported:

email plain text file will be likely cause problem. gzip the save file
could help lots of back and forth.

Proposed to gzip the file if filename ends with ".gz".

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

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

Title:
  auto compress if save filename ends with .gz

Status in apport package in Ubuntu:
  New

Bug description:
  email plain text file will be likely cause problem. gzip the save file
  could help lots of back and forth.

  Proposed to gzip the file if filename ends with ".gz".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837174/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Bryan Quigley]

I just built a package that just reverts it for Bionic and Disco :
https://launchpad.net/~bryanquigley/+archive/ubuntu/1796501

Will confirm results tomorrow but so far with DNSSEC=yes:

Bionic with DVE-2018-0001 patch: Can't resolve europa.eu
Bionic with patch reverted: Can resolve europa.eu

Disco with DVE-2018-0001 patch: Can't resolve people.com.cn, search.yahoo.com, 
news.yahoo.com
Disco with patch reverted:  Can resolve those three domains.

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1837173] Re: shall allow local save even it's neither ubuntu nor native.

[Yuan-Chen Cheng]

patch attached for ubuntu/devel branch.

** Patch added: "allow-local-save-more-aggressively.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837173/+attachment/5277979/+files/allow-local-save-more-aggressively.patch

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

Title:
  shall allow local save even it's neither ubuntu nor native.

Status in apport package in Ubuntu:
  New

Bug description:
  For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is
  a local test one, it won't save the log.

  Let's skip package check if --save option is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837173/+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 1837173] [NEW] shall allow local save even it's neither ubuntu nor native.

[Yuan-Chen Cheng]

Public bug reported:

For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is a
local test one, it won't save the log.

Let's skip package check if --save option is used.

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

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

Title:
  shall allow local save even it's neither ubuntu nor native.

Status in apport package in Ubuntu:
  New

Bug description:
  For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is
  a local test one, it won't save the log.

  Let's skip package check if --save option is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837173/+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 859060] Re: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a()

[Launchpad Bug Tracker]

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

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

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

Title:
  totem-plugin-viewer crashed with SIGSEGV in
  g_type_check_instance_is_a()

Status in gstreamer0.10 package in Ubuntu:
  Expired
Status in totem package in Ubuntu:
  Expired

Bug description:
  Totem crashed when clicking the small play button to preview a sound
  file in the itunes store preview thingy... more specifically this
  address http://itunes.apple.com/us/album/nine-oclock-
  single/id465976129?ls=1

  Description:  Ubuntu oneiric (development branch)
  Release:  11.10
  libgstreamer0.10-0:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-good:
Installed: 0.10.30-1ubuntu7
Candidate: 0.10.30-1ubuntu7
Version table:
   *** 0.10.30-1ubuntu7 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-alsa:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-audiosink:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-plugins-bad:
Installed: 0.10.22-2ubuntu4
Candidate: 0.10.22-2ubuntu4
Version table:
   *** 0.10.22-2ubuntu4 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-ugly:
Installed: 0.10.18-3ubuntu1
Candidate: 0.10.18-3ubuntu1
Version table:
   *** 0.10.18-3ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-ffmpeg:
Installed: 0.10.12-1ubuntu1
Candidate: 0.10.12-1ubuntu1
Version table:
   *** 0.10.12-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-pulse:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-gconf:
Installed: 0.10.30-1ubuntu7
Candidate: 0.10.30-1ubuntu7
Version table:
   *** 0.10.30-1ubuntu7 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-tools:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-audiosource:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-doc:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  libgstreamer0.10-dev:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-videosink:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-videosource:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-gnonlin:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-gnonlin-dbg:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-gnonlin-doc:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-nice:
Installed: 0.1.0-2ubuntu1
Candidate: 0.1.0-2ubuntu1
Version table:
   *** 0.1.0-2ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base-apps:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base-dbg:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   0.10.35-1 0
   

[Touch-packages] [Bug 859060] Re: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a()

[Launchpad Bug Tracker]

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

** Changed in: gstreamer0.10 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  totem-plugin-viewer crashed with SIGSEGV in
  g_type_check_instance_is_a()

Status in gstreamer0.10 package in Ubuntu:
  Expired
Status in totem package in Ubuntu:
  Expired

Bug description:
  Totem crashed when clicking the small play button to preview a sound
  file in the itunes store preview thingy... more specifically this
  address http://itunes.apple.com/us/album/nine-oclock-
  single/id465976129?ls=1

  Description:  Ubuntu oneiric (development branch)
  Release:  11.10
  libgstreamer0.10-0:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-good:
Installed: 0.10.30-1ubuntu7
Candidate: 0.10.30-1ubuntu7
Version table:
   *** 0.10.30-1ubuntu7 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-alsa:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-audiosink:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-plugins-bad:
Installed: 0.10.22-2ubuntu4
Candidate: 0.10.22-2ubuntu4
Version table:
   *** 0.10.22-2ubuntu4 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-ugly:
Installed: 0.10.18-3ubuntu1
Candidate: 0.10.18-3ubuntu1
Version table:
   *** 0.10.18-3ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-ffmpeg:
Installed: 0.10.12-1ubuntu1
Candidate: 0.10.12-1ubuntu1
Version table:
   *** 0.10.12-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 
Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-pulse:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-gconf:
Installed: 0.10.30-1ubuntu7
Candidate: 0.10.30-1ubuntu7
Version table:
   *** 0.10.30-1ubuntu7 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-tools:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-audiosource:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-doc:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  libgstreamer0.10-dev:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-videosink:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-videosource:
Installed: (none)
Candidate: (none)
Version table:
  gstreamer0.10-gnonlin:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-gnonlin-dbg:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-gnonlin-doc:
Installed: (none)
Candidate: 0.10.17-2
Version table:
   0.10.17-2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  gstreamer0.10-nice:
Installed: 0.1.0-2ubuntu1
Candidate: 0.1.0-2ubuntu1
Version table:
   *** 0.1.0-2ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base-apps:
Installed: 0.10.35-1
Candidate: 0.10.35-1
Version table:
   *** 0.10.35-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status
  gstreamer0.10-plugins-base-dbg:
Installed: (none)
Candidate: 0.10.35-1
Version table:
   

[Touch-packages] [Bug 1061554] Re: assertion failure `trap != NULL' displayed by all GTK3 software

[ALinuxUser]

I have this problem on Linux Mint 19.1, which is based on Ubuntu 18.04.1
(although admittedly I am running the alpha of Mint 19.2).

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

Title:
  assertion failure `trap != NULL' displayed by all GTK3 software

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  All GTK3/GNOME3 software I tried (gedit, evince, evolution, ...)
  display the following error message:

  $ gedit

  (gedit:5387): Gdk-CRITICAL **: gdk_error_trap_pop_internal: assertion
  `trap != NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libgtk-3-0 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.15-lowlatency 3.5.4
  Uname: Linux 3.5.0-16-lowlatency i686
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  Date: Thu Oct  4 13:56:41 2012
  EcryptfsInUse: Yes
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1061554/+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 1837170] [NEW] Kodi package crash after the update of libdrm-amdgpu1

[Tom Lake]

Public bug reported:

Greetings,

The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
it to crash after loading any video or reproduce a black image.

Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

  libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06 +0300


Kodi gives this error:

#3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

Repeated several times

#3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
#4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

Team-Kodi stated these errors are in relation to 'Not supported GPU
drivers', when Kodi can't find these files.


I've found the cause, and a temporary solution:

This bug was caused after an update for the latest version of libdrm-
amdgpu1 2.4.97-1ubuntu1~18.04.1

So I grabbed the previous version from 
https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

and now Kodi returns.


I created a bug report, the problem affects multiple users.

https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828


We have a PointRelease coming soon, would we have time to fix this package?

Thank you for your assistance.

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

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in libdrm package in Ubuntu:
  New

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

[Daniel van Vugt]

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

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about 

[Touch-packages] [Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >=

[Daniel van Vugt]

** Summary changed:

- /usr/bin/gnome-shell:gnome-shell: 
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: 
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.
+ gnome-shell crashed with assertion failure 
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: 
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.

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

** Tags added: radeon

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

Title:
  gnome-shell crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.4-0ubuntu18.04.1, the problem page at 
https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837087/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

[Tina Russell]

** Description changed:

- I’m not exactly sure if this belongs here, libva, mesa, or upstream
- somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program
- is.
+ Buggy as Kodi is, this seems to be a problem specifically with mesa-va-
+ drivers.
  
  Kodi has worked just fine on my system, as recently as July 6th of this
  year, but yesterday (July 16) I tried Kodi again: I got a blank screen
  and a pause for a few moments, followed by an unceremonious crash-to-
  desktop. This happens every time I start Kodi, now.
  
  If I run it through the command-line, I get this:
  
  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)
  
  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
- XBMC PPA) since its release in June, but in between July 7th and 16th, I
- did upgrade Nouveau:
- 
- 2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
- 2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1
- 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386 
2.4.95-1~18.04.1
- 2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
- 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
- 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386 
2.4.95-1~18.04.1
- 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1
- 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386 
2.4.95-1~18.04.1
- 2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386 
2.4.95-1~18.04.1
- 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
- 
- 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 

- 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 

- 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
- 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
- 
- (Another reason I’m guessing this is a Nouveau problem is because I
- later tried switching to the official NVidia drivers, didn’t get this
- bug, and then later encountered a distinct yet worse bug that locks up
- the whole system. So, now I’m back to using Nouveau.)
+ XBMC PPA) since its release in June, but in between July 6th and 16th, I
+ did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2
+ 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package
+ to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic
+ repository), however, Kodi works again, without even requiring me to
+ restart my machine. So, this is likely a problem with “mesa-va-drivers”.
  
  I tried looking in Xorg.0.log:
  
  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)
  
  …that’s all that appears in the log when I try to load Kodi and a crash
  happens.
  
  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I hope
  this bug can get fixed, soon. Thanks!

** No longer affects: xserver-xorg-video-nouveau (Ubuntu)

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  New

Bug description:
  Buggy as Kodi is, this seems to be a problem specifically with mesa-
  va-drivers.

  Kodi has worked just 

[Touch-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

[Tina Russell]

Sweet mother of the Muses, I just downgraded the mesa-va-drivers package
to 18.0.0~rc5-1ubuntu1 (since that’s the one from the non-updates Bionic
repository) and Kodi works again! Then, this is a problem specifically
with the mesa-va-drivers package. I’ll have to update the description
accordingly.

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  New

Bug description:
  Buggy as Kodi is, this seems to be a problem specifically with mesa-
  va-drivers.

  Kodi has worked just fine on my system, as recently as July 6th of
  this year, but yesterday (July 16) I tried Kodi again: I got a blank
  screen and a pause for a few moments, followed by an unceremonious
  crash-to-desktop. This happens every time I start Kodi, now.

  If I run it through the command-line, I get this:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)

  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
  XBMC PPA) since its release in June, but in between July 6th and 16th,
  I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2
  19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers”
  package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates
  Bionic repository), however, Kodi works again, without even requiring
  me to restart my machine. So, this is likely a problem with “mesa-va-
  drivers”.

  I tried looking in Xorg.0.log:

  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

  …that’s all that appears in the log when I try to load Kodi and a
  crash happens.

  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I
  hope this bug can get fixed, soon. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1828663] Re: policykit failures due to internal user id mismatch

[Launchpad Bug Tracker]

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

** Changed in: polkit-qt-1 (Ubuntu)
   Status: New => Confirmed

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

Title:
  policykit failures due to internal user id mismatch

Status in PolicyKit:
  New
Status in lubuntu-meta package in Ubuntu:
  Invalid
Status in lxqt-policykit package in Ubuntu:
  Invalid
Status in policykit-1 package in Ubuntu:
  Confirmed
Status in polkit-qt-1 package in Ubuntu:
  Confirmed

Bug description:
  After adding a second user to the sudo group any authentication in the
  QT applications menu fails, till I manually remove the second user
  from the sudo group by issuing deluser chiara sudo in terminal window.

  Lubuntu 19.04
  (fresh install, in italian)
  1)open the preferences/LXQt settins/user and groups menu from the application 
menu
  2)add new user, before saving add it to sudo group; save (password asked for 
user currently logged on, as expected - then new user password asked, user 
created -all ok)
  3)restart system
  4) log in as newly created user; open the same interface preferences/LXQt 
settins/user and groups; try changing the full name field  (properties of your 
own user): logged user password asked (and... why? User two is changing 
himself) 
  5)popup showed: "Error executing command as another user: Not authorized" & 
user unchanged.
  6)if you exit session, reenter with the first user, also him is now unable to 
use interface ti change users via interface
  7)using terminal, delete second user from sudo group
  8)restart system
  9)athenticated interface working again.

  It happened me both at home on a phisical laptop and on a virtual
  machine at office, where I could do it all twice.

  By the way, also plasma-discover tells me I haven't the right to
  update/install when I have two sudoers (tried at home to remove second
  sudoer to fix it, and it worked)

  So it seems that the authentication mechanism of the QT graphical interface 
fails when there are more then one sudoer on the system - but only for 
applications started from the application menu.
  Launching the same application via terminal (sudo plasma-discovery) works.

  commands issued by the interface (which lead to "unauthorized" error:

  --change user
  pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco 
marcop 

  --plasma-discover
  polkit-agent-helper-1 marcop

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1828663/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

[Tina Russell]

There was an update to Mesa over in the Ubuntu-X-Swat PPA today (by
which I mean the “Updates” one), from 19.0.2-1ubuntu1.1~18.04.1 to
19.0.8-0ubuntu0~18.04.1. …Sadly, as I discovered—after installing the
updates, then restarting and trying Kodi again—this bug is still present
and still works exactly the same.

(While I’m here, does anyone know how I would file a bug with the
nvidia-340 package? I mean, I don’t know how much we can do about that
driver, given its proprietary nature, but I want to try, at least. I
just want one of my graphics drivers working so I can use my media
player again… (sigh))

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

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  I’m not exactly sure if this belongs here, libva, mesa, or upstream
  somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that
  program is.

  Kodi has worked just fine on my system, as recently as July 6th of
  this year, but yesterday (July 16) I tried Kodi again: I got a blank
  screen and a pause for a few moments, followed by an unceremonious
  crash-to-desktop. This happens every time I start Kodi, now.

  If I run it through the command-line, I get this:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)

  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
  XBMC PPA) since its release in June, but in between July 7th and 16th,
  I did upgrade Nouveau:

  2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
  2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1
  2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386 
2.4.95-1~18.04.1
  2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
  2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64 
2.4.95-1~18.04.1
  2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386 
2.4.95-1~18.04.1
  2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1
  2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386 
2.4.95-1~18.04.1
  2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386 
2.4.95-1~18.04.1
  2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1

  2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 

  2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 

  2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
  2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1

  (Another reason I’m guessing this is a Nouveau problem is because I
  later tried switching to the official NVidia drivers, didn’t get this
  bug, and then later encountered a distinct yet worse bug that locks up
  the whole system. So, now I’m back to using Nouveau.)

  I tried looking in Xorg.0.log:

  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

  …that’s all that appears in the log when I try to load Kodi and a
  crash happens.

  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I
  hope this bug can get fixed, 

[Touch-packages] [Bug 1835297] Re: Precision 7730 smart card reader does not work out of box

[Jill Manfield]

The link is not working.  Skip that.  I have the following commands in case it 
helps:
  *-usb
   description: Mass storage device
   product: DataTraveler 3.0
   vendor: Kingston
   physical id: 1
   bus info: usb@2:1
   logical name: scsi0
   version: 0.01
   serial: 0026186871D2F02178471906
   capabilities: usb-3.00 scsi emulated scsi-host
   configuration: driver=usb-storage maxpower=296mA speed=5000Mbit/s
 *-disk
  description: SCSI Disk
  product: DataTraveler 3.0
  vendor: Kingston
  physical id: 0.0.0
  bus info: scsi@0:0.0.0
  logical name: /dev/sda
  serial: 0
  size: 7377MiB (7736MB)
  capabilities: removable
  configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
*-medium
 physical id: 0
 logical name: /dev/sda
 size: 7377MiB (7736MB)
 capabilities: partitioned partitioned:dos
 configuration: signature=06593661
  *-storage
   description: Non-Volatile memory controller
   product: Toshiba America Info Systems
   vendor: Toshiba America Info Systems
   physical id: 0
   bus info: pci@:02:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: storage pciexpress pm msi msix nvm_express bus_master 
cap_list
   configuration: driver=nvme latency=0
   resources: irq:16 memory:b050-b0503fff

Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0025 Intel Corp. 
Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e94
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10)
00:14.0 USB controller: Intel Corporation Device a36d (rev 10)
00:14.2 RAM memory: Intel Corporation Device a36f (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
00:16.0 Communication controller: Intel Corporation Device a360 (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device a33d (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Device a348 (rev 10)
00:1f.4 SMBus: Intel Corporation Device a323 (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM 
(rev 10)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Polaris10]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon 
RX 580]
02:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0116
6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 
(rev 01)
6f:00.0 Network controller: Intel Corporation Device 2526 (rev 29)


Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x0951 Kingston Technology
  idProduct  0x1666 DataTraveler G4
  bcdDevice0.01
  iManufacturer   1 Kingston
  iProduct2 DataTraveler 3.0
  iSerial 3 0026186871D2F02178471906
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   44
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower   74mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5

[Touch-packages] [Bug 1829968] Re: motd [on at least some instances] does not auto-update daily

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu7.1

---
base-files (10.1ubuntu7.1) cosmic; urgency=medium

  * debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)

 -- Brian Murray   Mon, 08 Jul 2019 11:37:37 -0700

** Changed in: base-files (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  motd [on at least some instances] does not auto-update daily

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Cosmic:
  Fix Released
Status in base-files source package in Disco:
  Fix Released
Status in base-files source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  motd-news timer is not properly configured and may not run regularly so long 
running systems will not get an updated motd

  [Test Case]
  The motd-news.timer is known to be incorrectly configured because 
motd-news.services is a one shot service which will not become active. 
Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not 
work reliably. However, because it can work some of the time it is difficult to 
find a case where the timer always fails so test case will involve only 
confirming that the new timer is correct.

  1) On a system with curl installed, install the new version of base-files
  2) Run 'systemctl list-timers motd* --all
  3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because 
we don't want people to miss important messages)
  4) Wait until "NEXT" is reached
  5) Confirm that there is another "NEXT" and that the time stamp of 
/var/cache/motd-news was updated

  [Regression Potential]
  I can't think of any on the client side as the job wasn't working as it was 
intended but it may cause extra load on the motd server.

  Original Description
  
  I have a VM running on AWS. It was launched on May 9th:

    $ uptime
     05:26:21 up 12 days,  6:34,  1 user,  load average: 0.00, 0.00, 0.00
    $ date
    Wed May 22 05:26:24 UTC 2019

  I touched none of the system defaults, and yet the motd has not
  updated automatically.

    $ ls -l /var/cache/motd-news
    -rw-r--r-- 1 root root 0 May  9 22:53 /var/cache/motd-news

  The systemd timer unit looks like this:

    $ systemctl status motd-news.timer
    ● motd-news.timer - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor 
preset: enabled)
   Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 
days ago
  Trigger: n/a

    May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the
  Day.

  If I run /etc/update-motd.d/50-motd-news --force manually, the file
  does update correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1637800] Re: add a motd script for news

[Brian Murray]

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

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

[Jill Manfield]

Following https://help.ubuntu.com/community/CommonAccessCard
Does not work to get the smartcard reader working.
pcsc_scan returns
'Waiting for first reader'

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

[Jill Manfield]

The information Nick previously provided was how they got around the
issue using the Kali opensource drivers.  Would you like us to follow
https://pcsclite.alioth.debian.org/ccid.html#support to get you that
information.

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) => xorg-server (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/1837081

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg-server package in Ubuntu:
  New
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

[Jill Manfield]

Does this cert indicate only Realtek is certified?

The lsusb output is:
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x0a5c Broadcom Corp.
  idProduct  0x5832 
  bcdDevice1.01
  iManufacturer   1 Broadcom Corp
  iProduct2 5880
  iSerial 3 0123456789ABCD
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  139
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   254 Application Specific Interface
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  4 Broadcom USH
  ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass11 Chip/SmartCard
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  5 Contacted SmartCard
  ChipCard Interface Descriptor:
bLength54
bDescriptorType33
bcdCCID  1.00
nMaxSlotIndex   0
bVoltageSupport 7  5.0V 3.0V 1.8V 
dwProtocols 3  T=0 T=1
dwDefaultClock   4000
dwMaxiumumClock  4000
bNumClockSupported  0
dwDataRate   9600 bps
dwMaxDataRate  25 bps
bNumDataRatesSupp.  0
dwMaxIFSD 247
dwSyncProtocols   
dwMechanical  
dwFeatures   000102BA
  Auto configuration based on ATR
  Auto voltage selection
  Auto clock change
  Auto baud rate change
  Auto PPS made by CCID
  NAD value other than 0x00 accepted
  TPDU level exchange
dwMaxCCIDMsgLen   271
bClassGetResponse  00
bClassEnvelope 00
wlcdLayout   none
bPINSupport 0 
bMaxCCIDBusySlots   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86  EP 6 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes

[Touch-packages] [Bug 1637800] Re: add a motd script for news

[Brian Murray]

I installed the version of base-files from Ubuntu 18.04's proposed
repository and after installation of the package not timer was running
for motd-news. I rebooted to see if that would active the timer and it
did not.

bdmurray@clean-xenial-amd64:~$ ls -lh /var/cache/motd-news 
-rw-r--r-- 1 root root 0 Jul 18 12:32 /var/cache/motd-news
bdmurray@clean-xenial-amd64:~$ systemctl list-timers --all
NEXT LEFT LAST PASSED  
UNIT ACTIVATES
Thu 2019-07-18 21:33:41 PDT  8h left  Thu 2019-07-18 12:20:38 PDT  1h 8min ago 
apt-daily.timer  apt-daily.service
Fri 2019-07-19 06:01:14 PDT  16h left Thu 2019-07-18 12:20:38 PDT  1h 8min ago 
apt-daily-upgrade.timer  apt-daily-upgrade.service
Fri 2019-07-19 12:47:35 PDT  23h left Thu 2019-07-18 12:47:35 PDT  41min ago   
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
n/a  n/a  n/a  n/a 
snapd.refresh.timer 
n/a  n/a  n/a  n/a 
snapd.snap-repair.timer  snapd.snap-repair.service
n/a  n/a  n/a  n/a 
ureadahead-stop.timerureadahead-stop.service

6 timers listed.
bdmurray@clean-xenial-amd64:~$ uptime
 13:29:32 up 57 min,  1 user,  load average: 0.00, 0.00, 0.00
bdmurray@clean-xenial-amd64:~$ apt-cache policy base-files
base-files:
  Installed: 9.4ubuntu4.10
  Candidate: 9.4ubuntu4.10
  Version table:
 *** 9.4ubuntu4.10 100
100 /var/lib/dpkg/status
 9.4ubuntu4.8 500
500 https://ubuntu.osuosl.org/ubuntu xenial-updates/main amd64 Packages
 9.4ubuntu4 500
500 https://ubuntu.osuosl.org/ubuntu xenial/main amd64 Packages

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+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 1828102] Re: Regression in ModemManager

[Dan Streetman]

> I've sponsored this for disco

lol, looks like we collided :)

since our uploads are identical (I assume) it shouldn't matter which the
ubuntu-sru team approves.

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in modemmanager source package in Cosmic:
  Won't Fix
Status in modemmanager source package in Disco:
  In Progress
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

[Jill Manfield]

To add to this the following URL suggests the support and drivers should be 
bundled:
https://certification.ubuntu.com/hardware/201803-26164/

The Dell OEM image does not house the drivers, nor does the Canonical
image.  Is this expected?  Should there be documentation on how to get
this working without using opensource drivers since it is certified?

What does the certification mean?

Is there anything we need to do at Dell to get canonical and Dell to
work on getting the Kati.org pcscd* drivers bundled?

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835922] Re: missing gl* symbols in version 19.0.2

[Kan Li]

Tested 19.0.8 from ppa:ubuntu-x-swat/updates locally and the fix works.
Any idea when the fix will be available in the ubuntu repo for Bionic
release? I haven't found any way to install from ppa on Heroku.

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

Title:
  missing gl* symbols in version 19.0.2

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New
Status in mesa source package in Disco:
  New

Bug description:
  Linking with libosmesa6-dev version 19.0.2 will fail because all the
  gl* symbols are missing:

  ```
  [100%] Linking CXX executable bin/minko-converter
  
../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o):
 In function `jas_stream_tmpfile':
  jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better 
use `mkstemp'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::clear(unsigned int, float, 
float, float, float, float, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask'
  OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth'
  OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor'
  OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
unsigned int, int)':
  OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
int)':
  OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned 
int)':
  OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, 
unsigned int, unsigned int, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x559): undefined reference to 
`glVertexAttribPointer'
  OpenGLES2Context.cpp:(.text+0x59a): undefined reference to 
`glDisableVertexAttribArray'
  OpenGLES2Context.cpp:(.text+0x61e): undefined reference to 
`glEnableVertexAttribArray'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::createVertexAttributeArray()':
  OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function 
`minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to 
`glDeleteVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned 
int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned 
int, void*)':
  OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture'
  OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

I have checked the gtk+3.0 SRU in bionic-proposed now and could
reproduce the bug before updating and encountered correct behavior after
the update. So I am marking this SRU as verified.

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

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file (in /etc/cups/ppd/) removing the paper size 
you have selected for your job in the PageSize, PageRegion, PaperDimension, and 
ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 

[Touch-packages] [Bug 1828102] Re: Regression in ModemManager

[Ken VanDine]

I've sponsored this for disco

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in modemmanager source package in Cosmic:
  Won't Fix
Status in modemmanager source package in Disco:
  In Progress
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1828102] Re: Regression in ModemManager

[Dan Streetman]

Cosmic has reached EOL, today:
https://lists.ubuntu.com/archives/ubuntu-announce/2019-July/000246.html

However, I uploaded this for disco.

Note to sru reviewers, this patch was applied to bionic already in bug
1819615

** Also affects: modemmanager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: modemmanager (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in modemmanager source package in Cosmic:
  Won't Fix
Status in modemmanager source package in Disco:
  In Progress
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1837098] Re: Can't print in monochrome, only in colour

[Will Cooke]

To add a bit of clarity, I can't *choose* to print in monochrome from
and of the UI.  The system print dialog shows no options to select
monochrome.

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  New

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] [NEW] Can't print in monochrome, only in colour

[Will Cooke]

Public bug reported:

Printer is a Samsung C430W connected over wifi and using driverless
printing.  Everything is discovered and I can print in colour just fine.

In Bionic I was able to toggle in to monochrome, but in Disco I am not.
I now have to print everything in colour.

$ lpoptions -l
PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
ColorModel/Print Color Mode: *RGB
cupsPrintQuality/Print Quality: *4
print-scaling/Print Scaling: *auto auto-fit fill fit none

I have also attached the output of ipptool.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New

** Attachment added: "out.txt"
   https://bugs.launchpad.net/bugs/1837098/+attachment/5277893/+files/out.txt

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  New

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

Jason, the message you mention has nothing to do with the bug reported
here, it is from the color management daemon and in no case prevents a
job from printing. The bug reported here is about a problem of the
GTK/GNOME print dialog not handling printer driver updates correctly. It
only happens when a printer driver gets updated (can happen during a
general system update or an upgrade to a new Ubuntu version). We need
your error_log (in debug mode, see "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems) to judge whether you
are suffering this bug or something else.

** Description changed:

  [Impact]
  
  The problem occurs when the printer's driver package is updated and with
  this the PPD is replaced and one of the default settings of the queue is
  not available any more in the new PPD file. Then the setting is prefixed
  with "Custom." and with this the jobs fail.
  
  See comment #15 for more info.
  
  [Test Case]
  
  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
- - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
+ - Stop CUPS, edit the PPD file (in /etc/cups/ppd/) removing the paper size 
you have selected for your job in the PageSize, PageRegion, PaperDimension, and 
ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".
  
  With the fixed package installed the job will print.
  
  [Regression Potential]
  
  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job failure
  though.
  
  [Other Info]
  
  Complete info about the bug and the fix in comment #15,
  
  Original bug description:
  
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:
  
  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  
  Note the un-reaped gs process.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: 

[Touch-packages] [Bug 1829805] Re: update-initramfs -k all -c does not create initrd images anymore

[Brian Murray]

** Summary changed:

- Lubuntu Eoan Daily Image fails to boot after install on KVM
+ update-initramfs -k all -c does not create initrd images anymore

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

Title:
  update-initramfs -k all -c does not create initrd images anymore

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Context: The live environment appears to function properly and install
  proceeds as expected with no noticeable errors.

  Expected results: After a system reboot the virtual machine enters the
  graphical environment

  Actual Results: After rebooting the virtual machine a kernel panic
  error screen appears. I will attempt to attach the screenshot after
  submitting this bug report.

  The collected data is from the live environment as the installed
  environment will not boot.

  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  lubuntu@lubuntu:~$ apt-cache policy grub2
  grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
   2.02+dfsg1-12ubuntu2 500
  500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) 
eoan/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Tue May 21 00:30:39 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+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 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM

[Brian Murray]

There was some discussion regarding this particular bug in #ubuntu-
release on 20190620 - https://irclogs.ubuntu.com/2019/06/20/%23ubuntu-
release.html. I will not summarize the conversation here but only
capture what I understand the bug in initramfs-tools to be.

update-initramfs no longer uses what is in /var/lib/initramfs-tools as a
source of knowledge about kernel versions so using "-k all" will not
bring a deleted initrd. This behavior does not match the documentation
and is a regression. Some choice quotes follow:

"[20:52]  That appears to completely ignore STATEDIR now.
[20:59]  Anyhow, the behaviour change above is that it switched from 
checking STATEDIR to stating the initrd.
[20:59]  So, instead of "statedir knows what we've done in the past", 
we have "in you have no initrd, you can't have a new one either".
[20:59]  s/in you/if you/
[21:02]  
https://salsa.debian.org/kernel-team/initramfs-tools/commit/f39625afd6ba6c1aa2027286dc3ef1c933da14e0
[21:03]  vorlon: That would be the offending commit.  I think the 
obvious way to get both old and new behaviour combined would just be to add the 
statedir bit to the list (and sort -u the mess)."

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Triaged

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

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

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

Title:
  Lubuntu Eoan Daily Image fails to boot after install on KVM

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Context: The live environment appears to function properly and install
  proceeds as expected with no noticeable errors.

  Expected results: After a system reboot the virtual machine enters the
  graphical environment

  Actual Results: After rebooting the virtual machine a kernel panic
  error screen appears. I will attempt to attach the screenshot after
  submitting this bug report.

  The collected data is from the live environment as the installed
  environment will not boot.

  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  lubuntu@lubuntu:~$ apt-cache policy grub2
  grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
   2.02+dfsg1-12ubuntu2 500
  500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) 
eoan/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Tue May 21 00:30:39 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+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 1837080] Re: Recent update causes boot failure

[paranioid factoid]

Oh, you moved it to the initramfs-tools package maintenance group. My
apologies. I thought you closed the bug report.

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

Title:
  Recent update causes boot failure

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Ubuntu Studio 19.04 (also experienced with Ubuntu-18.04.2LTS with
  Studio Upgrade). Latest kernel 5.0.0-20 can't build an initialramfs
  due to problems finding fonts or Plymouth objects. On reboot, system
  can't start a display server. It loads, flashes, and then crashes,
  cycling endlessly. Can't get into the system with a pseudotty due to
  the display server cycling.

  It seems to be a support package and not the kernel directly. I
  downgrades the kernel to 5.0.0-13 by launching an installer USB and
  mounting the root filesystem that way. chroot to the mount point and
  use apt to purge the offending kernel directly. But the problem
  persisted.

  I re-installed with Ubuntu Studio 19.04 and during install system
  updates left the installer unable to write a boot record (because it
  couldn't create an initialramfs).

  Hardware:

  AMD 1950x Threadripper
  AMD VEGA FE
  Samsung nvme boot disk
  simple usb stick as install media.

  I don't have log output or screen output as I couldn't cut and paste
  or otherwise save it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1837080/+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 1837080] Re: Recent update causes boot failure

[paranioid factoid]

Yes it does. I'm running an unpatched Ubuntu Studio 19.04 because when I
install updates the system crashes on next reboot. There's a serious
problem here.

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

Title:
  Recent update causes boot failure

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Ubuntu Studio 19.04 (also experienced with Ubuntu-18.04.2LTS with
  Studio Upgrade). Latest kernel 5.0.0-20 can't build an initialramfs
  due to problems finding fonts or Plymouth objects. On reboot, system
  can't start a display server. It loads, flashes, and then crashes,
  cycling endlessly. Can't get into the system with a pseudotty due to
  the display server cycling.

  It seems to be a support package and not the kernel directly. I
  downgrades the kernel to 5.0.0-13 by launching an installer USB and
  mounting the root filesystem that way. chroot to the mount point and
  use apt to purge the offending kernel directly. But the problem
  persisted.

  I re-installed with Ubuntu Studio 19.04 and during install system
  updates left the installer unable to write a boot record (because it
  couldn't create an initialramfs).

  Hardware:

  AMD 1950x Threadripper
  AMD VEGA FE
  Samsung nvme boot disk
  simple usb stick as install media.

  I don't have log output or screen output as I couldn't cut and paste
  or otherwise save it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1837080/+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 1792643] Re: apport does not upload wayland or gnome-shell crash data

[Tom Reynolds]

This issue seems to have occurred to me today (and several times
previously) - when I returned to my computer after a while (the screen
had entered power saving mode), the gnome-shell process (on XWayland)
failed.

Neither after logging in to gnome-shell / Xwayland nor after logging out
and back into gnome-shell / Xorg was I prompted to submit a bug report
about it, even though there was /var/crash/_usr_bin_gnome-
shell.1000.crash. Killing and restarting whoopsie and update-notifier
did not change it. Manually generating and submitting the report using
apport-cli /var/crash/_usr_bin_gnome-shell.1000.crashdid succeed for
me, however (however the automation to do so failed).

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

Title:
  apport does not upload wayland or gnome-shell crash data

Status in apport package in Ubuntu:
  Confirmed

Bug description:
   uname -a

  Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

   lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  In trying to upload .crash data for bug 1789962 "gnome-shell segfaults
  in Wayland when display is turned off while Kodi running" I determined
  that apport-cli and friends were never able to upload the .crash
  files. The URL where they should appear is:
  
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  Earlier, I did upload the .crash files directly and was told by the
  defect reviewer that:

  _usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols)
  _usr_bin_gnome-shell.1000.crash: Stack trace is missing

  
   You can see the other bug for details, here is the last comment that I added 
(so far):

  I deleted all entries in /var/crash and /var/lib/whoopsie.
  I recreated the problem

  ls -l /var/crash

  total 92136
  -rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 
_usr_bin_gnome-shell.1000.crash
  -rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 
_usr_bin_Xwayland.1000.crash
  -rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 
_usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash

  fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash

  *** Error: Invalid problem report

  No such file or directory

  Press any key to continue...

  fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (40.6 MB)
E: Examine locally
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/E/V/K/I/C):
  S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  < Deleted lots and lots of ellipsis >
  

  echo $?
  0
  total 4
  ls -l /var/lib/whoopsie
  -rw--- 1 root root 128 Sep 13 18:39 whoopsie-id

  sudo cat /var/lib/whoopsie/whoopsie-id

  
39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  Checked the URL:
  
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  No entries since 08/11. None for wayland, gnome-shell or Kodi.
  I checked for over 5 minutes.


  So perhaps something is going bad on my end, but I just don't know
  what or how to  debug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1792643/+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 1837080] Re: Recent update causes boot failure

[Erich Eickmeyer]

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

** No longer affects: ubuntustudio

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

Title:
  Recent update causes boot failure

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Ubuntu Studio 19.04 (also experienced with Ubuntu-18.04.2LTS with
  Studio Upgrade). Latest kernel 5.0.0-20 can't build an initialramfs
  due to problems finding fonts or Plymouth objects. On reboot, system
  can't start a display server. It loads, flashes, and then crashes,
  cycling endlessly. Can't get into the system with a pseudotty due to
  the display server cycling.

  It seems to be a support package and not the kernel directly. I
  downgrades the kernel to 5.0.0-13 by launching an installer USB and
  mounting the root filesystem that way. chroot to the mount point and
  use apt to purge the offending kernel directly. But the problem
  persisted.

  I re-installed with Ubuntu Studio 19.04 and during install system
  updates left the installer unable to write a boot record (because it
  couldn't create an initialramfs).

  Hardware:

  AMD 1950x Threadripper
  AMD VEGA FE
  Samsung nvme boot disk
  simple usb stick as install media.

  I don't have log output or screen output as I couldn't cut and paste
  or otherwise save it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1837080/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Jason Currie]

I am experiencing this same problem in Linux Mint 19.1. After creating a
print job, there is no response from the printer (it doesn't wake up or
anything), there is no printing, but the only message in the error log
is "CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id \'MaisonLaser-
Gray..\' already exists"

I was able to resolve this on another machine by removing Gutenprint and
doing something else, but it was a while ago and I didn't keep notes.

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1828102] Re: Regression in ModemManager

[Till Kamppeter]

Added description changes from comment #5.

Please could someone with appropriate rights sponsor the uploads of the
attached debdiffs (SRUs)? Thanks.

It would be great if at least the SRU for Disco could get uploaded and
rolled out. Cosmic is very close before EOL, so it can easily happen
that the SRU does not get published in time, so Disco is much more
important.

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Cosmic:
  In Progress
Status in modemmanager source package in Disco:
  In Progress
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1792643] Re: apport does not upload wayland or gnome-shell crash data

[Launchpad Bug Tracker]

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

Title:
  apport does not upload wayland or gnome-shell crash data

Status in apport package in Ubuntu:
  Confirmed

Bug description:
   uname -a

  Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

   lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  In trying to upload .crash data for bug 1789962 "gnome-shell segfaults
  in Wayland when display is turned off while Kodi running" I determined
  that apport-cli and friends were never able to upload the .crash
  files. The URL where they should appear is:
  
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  Earlier, I did upload the .crash files directly and was told by the
  defect reviewer that:

  _usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols)
  _usr_bin_gnome-shell.1000.crash: Stack trace is missing

  
   You can see the other bug for details, here is the last comment that I added 
(so far):

  I deleted all entries in /var/crash and /var/lib/whoopsie.
  I recreated the problem

  ls -l /var/crash

  total 92136
  -rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 
_usr_bin_gnome-shell.1000.crash
  -rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 
_usr_bin_Xwayland.1000.crash
  -rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 
_usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash

  fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash

  *** Error: Invalid problem report

  No such file or directory

  Press any key to continue...

  fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (40.6 MB)
E: Examine locally
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/E/V/K/I/C):
  S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  < Deleted lots and lots of ellipsis >
  

  echo $?
  0
  total 4
  ls -l /var/lib/whoopsie
  -rw--- 1 root root 128 Sep 13 18:39 whoopsie-id

  sudo cat /var/lib/whoopsie/whoopsie-id

  
39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  Checked the URL:
  
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

  No entries since 08/11. None for wayland, gnome-shell or Kodi.
  I checked for over 5 minutes.


  So perhaps something is going bad on my end, but I just don't know
  what or how to  debug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1792643/+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 1828102] Re: Regression in ModemManager

[Till Kamppeter]

** Description changed:

  [Impact]
  
+ ModemManager disconnects from CDMA modem after 30 sec failing to check
+ signal status due to incorrect error handling
+ 
  [Test case]
+ 
+ connect to a cdma device without an extra AT channel (Eg. Samsung
+ brightside phone) and modemmanager will terminate the connection
  
  [Regression potential]
  
  The patch is tiny, fixing an obvious overlook, and it only affects CDMA
  broadband modems, so the risk of a regression is very low.
  
  [Original description]
  
  ModemManager disconnects after ~30 sec
  
  caused by a typo in 1.8
  
  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details
  
  needs a SRU for cosmic and dingo
  
  patch attached
  
  yechiel

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Cosmic:
  In Progress
Status in modemmanager source package in Disco:
  In Progress
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

[Alexander E. Patrakov]

https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate

** Bug watch added: Red Hat Bugzilla #1652274
   https://bugzilla.redhat.com/show_bug.cgi?id=1652274

** Also affects: xorg (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1652274
   Importance: Unknown
   Status: Unknown

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

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg package in Ubuntu:
  New
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+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 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

[Alexander E. Patrakov]

Public bug reported:

I have recently files this bug:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided
to test if it affects Ubuntu 19.04.

Just to remind you, this was about xorg crashing in a virtual machine
that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU
is Intel Core i7 4770S (Haswell).

Well, xorg crashes on 19.04, too, but with a different backtrace, and
adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
separate bug.

Disabling virgl on qemu command line helps, but I would rather have it
enabled.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Thu Jul 18 21:09:46 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco third-party-packages 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/1837081

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg package in Ubuntu:
  New

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  

[Touch-packages] [Bug 1837076] [NEW] RepeatedMsgReduction should be off by default

[Msd]

Public bug reported:

Maintainers explains that this option should be off :
https://www.rsyslog.com/doc/master/configuration/action/rsconf1_repeatedmsgreduction.html

> This parameter models old sysklogd legacy. Note that many people, including 
> the rsyslog authors, consider this to be a misfeature. [...]
> - While turning this feature on can save some space in logs, most log 
> analysis tools need to see the repeated messages, they can’t handle the “last 
> message repeated” format.
> - This is a feature that worked decades ago when logs were small and reviewed 
> by a human, it fails badly on high volume logs processed by tools. [...]
> This turns on repeated message reduction (not recommended):
> `$RepeatedMsgReduction on# do not log repeated messages`

So I think this option should be off by default in Ubuntu.

This option is Off in Debian 10.

Is there a reason why this is option is on on Ubuntu ?

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

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

Title:
  RepeatedMsgReduction should be off by default

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Maintainers explains that this option should be off :
  
https://www.rsyslog.com/doc/master/configuration/action/rsconf1_repeatedmsgreduction.html

  > This parameter models old sysklogd legacy. Note that many people, including 
the rsyslog authors, consider this to be a misfeature. [...]
  > - While turning this feature on can save some space in logs, most log 
analysis tools need to see the repeated messages, they can’t handle the “last 
message repeated” format.
  > - This is a feature that worked decades ago when logs were small and 
reviewed by a human, it fails badly on high volume logs processed by tools. 
[...]
  > This turns on repeated message reduction (not recommended):
  > `$RepeatedMsgReduction on# do not log repeated messages`

  So I think this option should be off by default in Ubuntu.

  This option is Off in Debian 10.

  Is there a reason why this is option is on on Ubuntu ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1837076/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

[Brian Murray]

** Tags removed: rls-dd-incoming rls-ee-incoming

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests

[Sebastien Bacher]

Could you try if the followup SRU made a difference there?
https://bugs.launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.3

** Tags added: regression-update

** Tags added: rls-bb-incoming

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

Title:
  libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests

Status in nginx package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  New

Bug description:
  Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but
  fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2.

  Repro steps:
  1. Create control Dockerfile:
  ==
  FROM ubuntu:18.04

  RUN apt-get update -y && \
apt-get upgrade -y && \
apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 
libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 
libssl1.1=1.1.0g-2ubuntu4.3

  RUN git clone https://github.com/nginx/nginx-tests.git
  WORKDIR /nginx-tests

  ENV TEST_NGINX_BINARY=/usr/sbin/nginx
  ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules

  USER www-data

  ENTRYPOINT ["prove", "."]
  ==

  2. Run the command in a directory with only the Dockerfile:
  docker build -t nginx_image . && docker run --rm -it nginx_image

  3. See output:
  ==
  Test Summary Report
  ---
  ./grpc_request_buffering.t   (Wstat: 512 Tests: 14 Failed: 2)
Failed tests:  11-12
Non-zero exit status: 2
  ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6)
Failed tests:  1-2, 7-8, 10-11
Non-zero exit status: 6
  ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output
  Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr  0.78 sys + 35.84 cusr 
16.99 csys = 55.48 CPU) 

  Result: FAIL
  ==

  4. Create new Dockerfile (only difference is updating libssl1.1):
  ==
  FROM ubuntu:18.04

  RUN apt-get update -y && \
apt-get upgrade -y && \
apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 
libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 
libssl1.1=1.1.1-1ubuntu2.1~18.04.2

  RUN git clone https://github.com/nginx/nginx-tests.git
  WORKDIR /nginx-tests

  ENV TEST_NGINX_BINARY=/usr/sbin/nginx
  ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules

  USER www-data

  ENTRYPOINT ["prove", "."]
  ==

  5. See output
  ==
  Test Summary Report
  ---
  ./grpc_request_buffering.t   (Wstat: 512 Tests: 14 Failed: 2)
Failed tests:  11-12
Non-zero exit status: 2
  ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6)
Failed tests:  1-2, 7-8, 10-11
Non-zero exit status: 6
  ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3)
Failed tests:  3, 5-6
Non-zero exit status: 3
  ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2)
Failed tests:  4-5
Non-zero exit status: 2
  ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2)
Failed tests:  4-5
Non-zero exit status: 2
  ./stream_ssl.t   (Wstat: 768 Tests: 9 Failed: 3)
Failed tests:  2, 4-5
Non-zero exit status: 3
  ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3)
Failed tests:  4-5, 9
Non-zero exit status: 3
  ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output
  ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3)
Failed tests:  4-5, 9
Non-zero exit status: 3
  Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr  0.73 sys + 36.49 cusr 
16.91 csys = 56.13 CPU)
  Result: FAIL
  ==

  New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t,
  stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM

[Steve Langasek]

** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing

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

Title:
  Lubuntu Eoan Daily Image fails to boot after install on KVM

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Context: The live environment appears to function properly and install
  proceeds as expected with no noticeable errors.

  Expected results: After a system reboot the virtual machine enters the
  graphical environment

  Actual Results: After rebooting the virtual machine a kernel panic
  error screen appears. I will attempt to attach the screenshot after
  submitting this bug report.

  The collected data is from the live environment as the installed
  environment will not boot.

  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  lubuntu@lubuntu:~$ apt-cache policy grub2
  grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
   2.02+dfsg1-12ubuntu2 500
  500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) 
eoan/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Tue May 21 00:30:39 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+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 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

[Brian Murray]

** Tags removed: rls-ee-incoming

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

Title:
  update-notifier doesn't respect "automatically check for updates:
  Never"

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Eoan:
  Confirmed

Bug description:
  This has been a long-standing problem with various ubuntu
  installations, and I'm sensing some reticence in doing anything about
  it. This attitude also seems to be purposeful to try to cajole updates
  on people who make bad choices due to confusion/fud/paranoia.

  apt install fails due to:

  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  A great deal of networking is taking place despite setting automatic
  upgrades to "never". Cycling this doesn't seem to do anything. This
  action is hostile to programmers and the setting should be respected.

  Wisdom on threads is to let it update until it's out of updates, and
  then it supposedly respects the "never" flag, but the experience I'm
  having is much more non-deterministic. have been using 19.04 for weeks
  now and still get the background notifier using data and getting in
  the way of aptitude package installations. I prefer manual update &&
  upgrade once my code is ready to push.

  Is there another way around this or are people just living with it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+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 1829968] Re: motd [on at least some instances] does not auto-update daily

[Brian Murray]

And the verification for Ubuntu 18.10 (cosmic) has also passed:

bdmurray@clean-cosmic-amd64:~$ apt-cache policy base-files
base-files:
  Installed: 10.1ubuntu7.1
  Candidate: 10.1ubuntu7.1
  Version table:
 *** 10.1ubuntu7.1 100
100 /var/lib/dpkg/status
 10.1ubuntu7 500
500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages
bdmurray@clean-cosmic-amd64:~$ systemctl list-timers motd* --all
NEXT LEFT LAST PASSED   
UNITACTIVATES
Wed 2019-07-17 22:01:58 PDT  13h left Wed 2019-07-17 08:02:02 PDT  1min 35s ago 
motd-news.timer motd-news.service

1 timers listed.
bdmurray@clean-cosmic-amd64:~$ systemctl list-timers motd* --all
NEXT LEFTLAST PASSED  
UNITACTIVATES
Wed 2019-07-17 22:01:58 PDT  8h left Wed 2019-07-17 08:02:02 PDT  5h 2min ago 
motd-news.timer motd-news.service

1 timers listed.
bdmurray@clean-cosmic-amd64:~$ systemctl list-timers motd* --all
NEXT LEFT  LAST PASSED 
UNITACTIVATES
Thu 2019-07-18 10:10:54 PDT  2h 17min left Wed 2019-07-17 22:02:39 PDT  9h ago 
motd-news.timer motd-news.service

1 timers listed.
bdmurray@clean-cosmic-amd64:~$ ls -lh /var/cache/motd-news
-rw-r--r-- 1 root root 0 Jul 17 22:02 /var/cache/motd-news


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

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

Title:
  motd [on at least some instances] does not auto-update daily

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Cosmic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Released
Status in base-files source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  motd-news timer is not properly configured and may not run regularly so long 
running systems will not get an updated motd

  [Test Case]
  The motd-news.timer is known to be incorrectly configured because 
motd-news.services is a one shot service which will not become active. 
Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not 
work reliably. However, because it can work some of the time it is difficult to 
find a case where the timer always fails so test case will involve only 
confirming that the new timer is correct.

  1) On a system with curl installed, install the new version of base-files
  2) Run 'systemctl list-timers motd* --all
  3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because 
we don't want people to miss important messages)
  4) Wait until "NEXT" is reached
  5) Confirm that there is another "NEXT" and that the time stamp of 
/var/cache/motd-news was updated

  [Regression Potential]
  I can't think of any on the client side as the job wasn't working as it was 
intended but it may cause extra load on the motd server.

  Original Description
  
  I have a VM running on AWS. It was launched on May 9th:

    $ uptime
     05:26:21 up 12 days,  6:34,  1 user,  load average: 0.00, 0.00, 0.00
    $ date
    Wed May 22 05:26:24 UTC 2019

  I touched none of the system defaults, and yet the motd has not
  updated automatically.

    $ ls -l /var/cache/motd-news
    -rw-r--r-- 1 root root 0 May  9 22:53 /var/cache/motd-news

  The systemd timer unit looks like this:

    $ systemctl status motd-news.timer
    ● motd-news.timer - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor 
preset: enabled)
   Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 
days ago
  Trigger: n/a

    May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the
  Day.

  If I run /etc/update-motd.d/50-motd-news --force manually, the file
  does update correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Sebastien Bacher]

** Changed in: mesa (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1835622] Re: Cannot start desktop session with compositor enabled

[Timo Aaltonen]

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

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

Title:
  Cannot start desktop session with compositor enabled

Status in Xfwm4:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xfwm4 package in Ubuntu:
  Invalid

Bug description:
  I cannot login to the Xfce desktop session anymore. in ~/.xsession-
  errors there's the message:

  xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285:
  intel_miptree_match_image: Assertion `image->TexObject->Target ==
  mt->target' failed.

  Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0.

  I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA
  with xfwm4 4.13.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1835622] Re: Cannot start desktop session with compositor enabled

[Timo Aaltonen]

well, perhaps not a dupe but would be nice to know if the new upstream
bugfix version helps

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

Title:
  Cannot start desktop session with compositor enabled

Status in Xfwm4:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xfwm4 package in Ubuntu:
  New

Bug description:
  I cannot login to the Xfce desktop session anymore. in ~/.xsession-
  errors there's the message:

  xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285:
  intel_miptree_match_image: Assertion `image->TexObject->Target ==
  mt->target' failed.

  Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0.

  I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA
  with xfwm4 4.13.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1835622] Re: Cannot start desktop session with compositor enabled

[Timo Aaltonen]

please test ppa:ubuntu-x-swat/updates

seems to be a duplicate of bug 1836721

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

Title:
  Cannot start desktop session with compositor enabled

Status in Xfwm4:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xfwm4 package in Ubuntu:
  New

Bug description:
  I cannot login to the Xfce desktop session anymore. in ~/.xsession-
  errors there's the message:

  xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285:
  intel_miptree_match_image: Assertion `image->TexObject->Target ==
  mt->target' failed.

  Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0.

  I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA
  with xfwm4 4.13.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1836738] Re: avahi-daemon takes 100% cpu over many minutes

[Angela]

18th July repeated 100% CPU use for over 5 minutes. Eventually cleared.

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

Title:
  avahi-daemon takes 100% cpu over many minutes

Status in avahi package in Ubuntu:
  New

Bug description:
  Rarely the processor locks onto avahi-deamon processes and doesn't
  release. This can happen when the PC is not being used. Only the high
  fan speed alerts me. I cannot repeat it will but it repeats itself
  naturally.

  I find in syslog lots of withdrawing and then registering IPv6 address
  records

  ul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:a165:d30c:a46d:fb67 on wlp2s0.*.
  Jul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:a165:d30c:a46d:fb67 on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for fd00::1:4a28:976d:1601:df6b on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 kernel: [21448.679978] IPv6: 
ipv6_create_tempaddr: retry temporary address regeneration
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:4a28:976d:1601:df6b on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.*.
  Jul 16 13:49:16 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:a5b6:b0b2:d3ab:cf92 on wlp2s0.*.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: avahi-daemon 0.7-4ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 13:36:05 2019
  InstallationDate: Installed on 2019-05-08 (68 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1836738/+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 1832050] Re: chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)

[Rafael David Tinoco]

Dimitri,

We fixed chrony's autopkgtest issue by allowing stderr during the test.
This case is still "on" as the dhclient hooks were the ones causing
stderr to chrony's tests (fyio). I have marked LP: #1832053 as a
duplicate of this and marked affecting systemd only.

Thanks!

** No longer affects: chrony (Ubuntu)

** No longer affects: chrony (Ubuntu Eoan)

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

Title:
  chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces
  stderr)

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  iproute2 fix in -proposed
  (https://launchpad.net/ubuntu/+source/iproute2/4.18.0-1ubuntu3) has
  showed regressions in chrony autopkgtest (object of this bug report).

  From autopkgtest output:

  """
  Generating /etc/default/isc-dhcp-server...
  Created symlink 
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server.service → 
/lib/systemd/system/isc-dhcp-server.service.
  Created symlink 
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server6.service → 
/lib/systemd/system/isc-dhcp-server6.service.
  Setting up autopkgtest-satdep (0) ...
  Processing triggers for systemd (240-6ubuntu9) ...
  Processing triggers for man-db (2.8.5-2) ...
  Processing triggers for libc-bin (2.29-0ubuntu2) ...
  (Reading database ... 62774 files and directories currently installed.)
  Removing autopkgtest-satdep (0) ...
  autopkgtest [20:50:33]: test time-sources-from-dhcp-servers: 
[---
  Preparing the dummy network interface and dhcpd configuration…
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or 
directory
  Done!

  Check if the NTP server is made available to chronyd…
  SUCCESS!

  Release the current lease and check if the NTP server has been correctly 
removed…
  SUCCESS!
  """

  It is likely that the stdout from md5sum coming out of the dhclient
  command caused the "regression".

  I have reproduced the issue by hand doing:

  $ apt-get install isc-dhcp-server
  $ modprobe dummy

  $ ip link add name dummy0 type dummy
  $ ip address add 192.168.1.1/24 dev dummy0
  $ ip link set dev dummy0 up

  cat < /etc/dhcp/dhcpd.conf
  default-lease-time 600;
  max-lease-time 7200;
  authorative;

  subnet 192.168.1.0 netmask 255.255.255.0 {
  option subnet-mask  255.255.255.0;
  option broadcast-address192.168.1.255;
  option ntp-servers  192.168.1.50;
  range 192.168.1.42 192.168.1.100;
  }
  EOF

  $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc-
  dhcp-server

  and

  $ systemctl restart isc-dhcp-server

  $ dhclient dummy0 <- problem happens here

  It could be a "isc-dhcp-client"problem, but I'll keep this bug linked
  to another bug if that is the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832050/+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 1832053] Re: systemd dhclient hook is causing md5sum cmds in inexistent files

[Rafael David Tinoco]

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

** No longer affects: ubuntu

** No longer affects: chrony (Ubuntu)

** No longer affects: chrony (Ubuntu Eoan)

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

Title:
  systemd dhclient hook is causing md5sum cmds in inexistent files

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  I have discovered this issue by doing investigation for the BUG:

  https://bugs.launchpad.net/ubuntu/+bug/1832050

  """
  I have reproduced the issue by hand doing:

  $ apt-get install isc-dhcp-server
  $ modprobe dummy

  $ ip link add name dummy0 type dummy
  $ ip address add 192.168.1.1/24 dev dummy0
  $ ip link set dev dummy0 up

  cat < /etc/dhcp/dhcpd.conf
  default-lease-time 600;
  max-lease-time 7200;
  authorative;

  subnet 192.168.1.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.1.255;
  option ntp-servers 192.168.1.50;
  range 192.168.1.42 192.168.1.100;
  }
  EOF

  $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc-
  dhcp-server

  and

  $ systemctl restart isc-dhcp-server

  $ dhclient dummy0 <- problem happens here
  """

  When trying a simple dhclient running on a bridge called "teste":

  (c)inaddy@eoanchrony:~/work/sources/ubuntu/chrony/debian/tests$ sudo dhclient 
teste
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or 
directory

  The problem is caused by the hook script:

  /etc/dhcp/dhclient-enter-hooks.d/resolved

  In the following line:

  md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-
  dhcp-v6-$interface.conf &> $oldstate

  I believe commit

  +systemd (240-6ubuntu9) eoan; urgency=medium

  caused this issue with a patch to file "debian/extra/dhclient-enter-
  resolved-hook"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832053/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Net User]

Have the same issue in Ubuntu 18.04.2 LTS.
In pavucontrol or in blueman-applet:
If select A2DP sound works;
If select HSP/HFP sound/mic do not work.

bluetoothctl output:
Name: Jabra Elite 65t   


Alias: Jabra Elite 65t  


Class: 0x00240404   


Icon: audio-card


Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v0067p247Ed020E

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1832050] Re: chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)

[Rafael David Tinoco]

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

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

** No longer affects: ubuntu

** No longer affects: Ubuntu Eoan

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

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

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

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

Title:
  chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces
  stderr)

Status in chrony package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in chrony source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  iproute2 fix in -proposed
  (https://launchpad.net/ubuntu/+source/iproute2/4.18.0-1ubuntu3) has
  showed regressions in chrony autopkgtest (object of this bug report).

  From autopkgtest output:

  """
  Generating /etc/default/isc-dhcp-server...
  Created symlink 
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server.service → 
/lib/systemd/system/isc-dhcp-server.service.
  Created symlink 
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server6.service → 
/lib/systemd/system/isc-dhcp-server6.service.
  Setting up autopkgtest-satdep (0) ...
  Processing triggers for systemd (240-6ubuntu9) ...
  Processing triggers for man-db (2.8.5-2) ...
  Processing triggers for libc-bin (2.29-0ubuntu2) ...
  (Reading database ... 62774 files and directories currently installed.)
  Removing autopkgtest-satdep (0) ...
  autopkgtest [20:50:33]: test time-sources-from-dhcp-servers: 
[---
  Preparing the dummy network interface and dhcpd configuration…
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or 
directory
  Done!

  Check if the NTP server is made available to chronyd…
  SUCCESS!

  Release the current lease and check if the NTP server has been correctly 
removed…
  SUCCESS!
  """

  It is likely that the stdout from md5sum coming out of the dhclient
  command caused the "regression".

  I have reproduced the issue by hand doing:

  $ apt-get install isc-dhcp-server
  $ modprobe dummy

  $ ip link add name dummy0 type dummy
  $ ip address add 192.168.1.1/24 dev dummy0
  $ ip link set dev dummy0 up

  cat < /etc/dhcp/dhcpd.conf
  default-lease-time 600;
  max-lease-time 7200;
  authorative;

  subnet 192.168.1.0 netmask 255.255.255.0 {
  option subnet-mask  255.255.255.0;
  option broadcast-address192.168.1.255;
  option ntp-servers  192.168.1.50;
  range 192.168.1.42 192.168.1.100;
  }
  EOF

  $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc-
  dhcp-server

  and

  $ systemctl restart isc-dhcp-server

  $ dhclient dummy0 <- problem happens here

  It could be a "isc-dhcp-client"problem, but I'll keep this bug linked
  to another bug if that is the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1832050/+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 1832053] Re: systemd dhclient hook is causing md5sum cmds in inexistent files

[Rafael David Tinoco]

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

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

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

** No longer affects: Ubuntu Eoan

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

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

** This bug has been marked a duplicate of bug 1832050
   chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)

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

Title:
  systemd dhclient hook is causing md5sum cmds in inexistent files

Status in Ubuntu:
  Confirmed
Status in chrony package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in chrony source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  I have discovered this issue by doing investigation for the BUG:

  https://bugs.launchpad.net/ubuntu/+bug/1832050

  """
  I have reproduced the issue by hand doing:

  $ apt-get install isc-dhcp-server
  $ modprobe dummy

  $ ip link add name dummy0 type dummy
  $ ip address add 192.168.1.1/24 dev dummy0
  $ ip link set dev dummy0 up

  cat < /etc/dhcp/dhcpd.conf
  default-lease-time 600;
  max-lease-time 7200;
  authorative;

  subnet 192.168.1.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.1.255;
  option ntp-servers 192.168.1.50;
  range 192.168.1.42 192.168.1.100;
  }
  EOF

  $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc-
  dhcp-server

  and

  $ systemctl restart isc-dhcp-server

  $ dhclient dummy0 <- problem happens here
  """

  When trying a simple dhclient running on a bridge called "teste":

  (c)inaddy@eoanchrony:~/work/sources/ubuntu/chrony/debian/tests$ sudo dhclient 
teste
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or 
directory
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or 
directory

  The problem is caused by the hook script:

  /etc/dhcp/dhclient-enter-hooks.d/resolved

  In the following line:

  md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-
  dhcp-v6-$interface.conf &> $oldstate

  I believe commit

  +systemd (240-6ubuntu9) eoan; urgency=medium

  caused this issue with a patch to file "debian/extra/dhclient-enter-
  resolved-hook"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1832053/+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 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

[Dmitry Shachnev]

Thanks for confirming, adjusting the bug status accordingly.

** No longer affects: twinkle (Ubuntu)

** Also affects: qtdeclarative-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

** Changed in: qtdeclarative-opensource-src (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src source package in Bionic:
  Won't Fix

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Timo Aaltonen]

cool, the fix is on the SRU queue now, waiting for review

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu Xenial)
   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/1754671

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound

[João Ornelas]

Exactly the same issue on 18.04. Why was this closed?

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

Title:
  [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Have checked under windows (same computer in dual-boot & same
  headset), and the sound is crystal clear, so 99% sure this is not a
  hardware problem.

  Motherboard is ASUS Crosshair Hero 6.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  paul   2587 F pulseaudio
   /dev/snd/controlC0:  paul   2587 F pulseaudio
   /dev/snd/controlC1:  paul   2587 F pulseaudio
   /dev/snd/controlC2:  paul   2587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 11:48:05 2017
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, 
dropouts or crackling sound
  UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago)
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated from ppa:ubuntu-x-swat/updates, now everything is
fine on i386 Ubuntu 18.04

~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
  Installed: 19.0.8-0ubuntu0~18.04.1
  Candidate: 19.0.8-0ubuntu0~18.04.1
  Version table:
 *** 19.0.8-0ubuntu0~18.04.1 500
500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu bionic/main 
i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

[Timo Aaltonen]

excellent, that version is on the SRU queue already, waiting for review

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  

[Touch-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

[Alexander E. Patrakov]

It works.

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2

[Timo Aaltonen]

please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built

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

Title:
  missing gl* symbols in version 19.0.2

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New
Status in mesa source package in Disco:
  New

Bug description:
  Linking with libosmesa6-dev version 19.0.2 will fail because all the
  gl* symbols are missing:

  ```
  [100%] Linking CXX executable bin/minko-converter
  
../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o):
 In function `jas_stream_tmpfile':
  jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better 
use `mkstemp'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::clear(unsigned int, float, 
float, float, float, float, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask'
  OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth'
  OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor'
  OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
unsigned int, int)':
  OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
int)':
  OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned 
int)':
  OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, 
unsigned int, unsigned int, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x559): undefined reference to 
`glVertexAttribPointer'
  OpenGLES2Context.cpp:(.text+0x59a): undefined reference to 
`glDisableVertexAttribArray'
  OpenGLES2Context.cpp:(.text+0x61e): undefined reference to 
`glEnableVertexAttribArray'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::createVertexAttributeArray()':
  OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function 
`minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to 
`glDeleteVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned 
int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned 
int, void*)':
  OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture'
  OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned 
int, unsigned int, unsigned int, unsigned int, void*)':
  

[Touch-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Timo Aaltonen]

please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

[Timo Aaltonen]

please test 19.0.8 from ppa:ubuntu-x-swat/updates

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

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Timo Aaltonen]

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

** Summary changed:

- Black screen on skylake after 18.0 => 18.2 update
+ [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Timo Aaltonen]

okay, adding the revert again.. this should've been fixed in the kernel
after 18.04.2 but that didn't happen

since we don't support 32bit installs in newer releases, bionic is the
only one that will get this

** Also affects: mesa (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu)
   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/1836721

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1835922] Re: missing gl* symbols in version 19.0.2

[Timo Aaltonen]

fixed upstream in 19.0.5

** Bug watch added: freedesktop.org Bugzilla #109659
   https://bugs.freedesktop.org/show_bug.cgi?id=109659

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=109659
   Importance: Unknown
   Status: Unknown

** Also affects: mesa (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  missing gl* symbols in version 19.0.2

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New
Status in mesa source package in Disco:
  New

Bug description:
  Linking with libosmesa6-dev version 19.0.2 will fail because all the
  gl* symbols are missing:

  ```
  [100%] Linking CXX executable bin/minko-converter
  
../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o):
 In function `jas_stream_tmpfile':
  jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better 
use `mkstemp'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::clear(unsigned int, float, 
float, float, float, float, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask'
  OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth'
  OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor'
  OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
unsigned int, int)':
  OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
int)':
  OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
  OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned 
int)':
  OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData'
  OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, 
unsigned int, unsigned int, unsigned int, unsigned int)':
  OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer'
  OpenGLES2Context.cpp:(.text+0x559): undefined reference to 
`glVertexAttribPointer'
  OpenGLES2Context.cpp:(.text+0x59a): undefined reference to 
`glDisableVertexAttribArray'
  OpenGLES2Context.cpp:(.text+0x61e): undefined reference to 
`glEnableVertexAttribArray'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::createVertexAttributeArray()':
  OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function 
`minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)':
  OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to 
`glDeleteVertexArrays'
  
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned 
int, minko::render::CubeTexture::Face, 

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

> That's weird, do you understand why? The update was deleted so you should be 
> back to initial 
> situation, we had no change to the previous package build

Other package changes? Certainly systemd-resolver although we don't use
that (because of a previous VPN DNS leak problem) we use dnsmasq.

My original thought was that it was the VPN config change that we'd made
to cope with the new NM, but testing seems to show it isn't that.

Now we have a failure mode which some people had *occasionally* reported
before, where even VPN lookups which *must* go to the VPN, for the
company domain, are not. This was just occasional before; now it seems
to happen all the time. I haven't done a thorough investigation since
just putting the updated NM back has been enough 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/1754671

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Till Kamppeter]

seb128, it seems that dwmw2 NEEDS this SRU, without he does not get his
environment working correctly, with SRU he gets it at least working
setting the parameters he mentioned. I asked the posters of the
regressions whether they get their situation fixed when using this SRU,
the systemd SRU and dwmw2's settings, but no one answered.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Sebastien Bacher]

> Then the NM update was pulled, and new installations aren't working at
all, even if we don't set the DNS config as described.

That's weird, do you understand why? The update was deleted so you
should be back to initial situation, we had no change to the previous
package build

Also Till is still trying to understand what the regressions reported
are about and what we should do about those

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1798313] Re: traceoute6 gives error sendto: Invalid argument

[Launchpad Bug Tracker]

This bug was fixed in the package iputils - 3:20161105-1ubuntu3

---
iputils (3:20161105-1ubuntu3) bionic; urgency=medium

  * debian/patches/git_after_free.patch,
debian/patches/git_routing_ipv6.patch:
- backport fixes for ipv6 routing commands not working (lp: #1798313)

 -- Sebastien Bacher   Fri, 28 Jun 2019 13:05:23
+0200

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

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Bionic:
  Fix Released
Status in iputils package in Debian:
  Fix Released

Bug description:
  * Impact
  Using IPv6 the routing command returns Invalid argument errors

  * Test case
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument

  * Regression potential
  Check that the command behave correclty on IPv4 and IP6 Ips

  --

  
  This seems like a regression of Debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1757375] Re: Desktop unable to Suspend when Inactive

[Sebastien Bacher]

it's also weird because
/usr/share/polkit-1/actions/org.freedesktop.login1.policy has


...

auth_admin_keep
auth_admin_keep
yes



Which means the active session should be allowed

Is you user an admin one?

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1798313] Update Released

[Łukasz Zemczak]

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Bionic:
  Fix Committed
Status in iputils package in Debian:
  Fix Released

Bug description:
  * Impact
  Using IPv6 the routing command returns Invalid argument errors

  * Test case
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument

  * Regression potential
  Check that the command behave correclty on IPv4 and IP6 Ips

  --

  
  This seems like a regression of Debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1829968] Re: motd [on at least some instances] does not auto-update daily

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu9.1

---
base-files (10.1ubuntu9.1) disco; urgency=medium

  * debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)

 -- Brian Murray   Mon, 08 Jul 2019 11:15:53 -0700

** Changed in: base-files (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  motd [on at least some instances] does not auto-update daily

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Cosmic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Released
Status in base-files source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  motd-news timer is not properly configured and may not run regularly so long 
running systems will not get an updated motd

  [Test Case]
  The motd-news.timer is known to be incorrectly configured because 
motd-news.services is a one shot service which will not become active. 
Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not 
work reliably. However, because it can work some of the time it is difficult to 
find a case where the timer always fails so test case will involve only 
confirming that the new timer is correct.

  1) On a system with curl installed, install the new version of base-files
  2) Run 'systemctl list-timers motd* --all
  3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because 
we don't want people to miss important messages)
  4) Wait until "NEXT" is reached
  5) Confirm that there is another "NEXT" and that the time stamp of 
/var/cache/motd-news was updated

  [Regression Potential]
  I can't think of any on the client side as the job wasn't working as it was 
intended but it may cause extra load on the motd server.

  Original Description
  
  I have a VM running on AWS. It was launched on May 9th:

    $ uptime
     05:26:21 up 12 days,  6:34,  1 user,  load average: 0.00, 0.00, 0.00
    $ date
    Wed May 22 05:26:24 UTC 2019

  I touched none of the system defaults, and yet the motd has not
  updated automatically.

    $ ls -l /var/cache/motd-news
    -rw-r--r-- 1 root root 0 May  9 22:53 /var/cache/motd-news

  The systemd timer unit looks like this:

    $ systemctl status motd-news.timer
    ● motd-news.timer - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor 
preset: enabled)
   Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 
days ago
  Trigger: n/a

    May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the
  Day.

  If I run /etc/update-motd.d/50-motd-news --force manually, the file
  does update correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1829968] Re: motd [on at least some instances] does not auto-update daily

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu2.5

---
base-files (10.1ubuntu2.5) bionic; urgency=medium

  * debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)

 -- Brian Murray   Mon, 08 Jul 2019 11:43:29 -0700

** Changed in: base-files (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  motd [on at least some instances] does not auto-update daily

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Cosmic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Released
Status in base-files source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  motd-news timer is not properly configured and may not run regularly so long 
running systems will not get an updated motd

  [Test Case]
  The motd-news.timer is known to be incorrectly configured because 
motd-news.services is a one shot service which will not become active. 
Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not 
work reliably. However, because it can work some of the time it is difficult to 
find a case where the timer always fails so test case will involve only 
confirming that the new timer is correct.

  1) On a system with curl installed, install the new version of base-files
  2) Run 'systemctl list-timers motd* --all
  3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because 
we don't want people to miss important messages)
  4) Wait until "NEXT" is reached
  5) Confirm that there is another "NEXT" and that the time stamp of 
/var/cache/motd-news was updated

  [Regression Potential]
  I can't think of any on the client side as the job wasn't working as it was 
intended but it may cause extra load on the motd server.

  Original Description
  
  I have a VM running on AWS. It was launched on May 9th:

    $ uptime
     05:26:21 up 12 days,  6:34,  1 user,  load average: 0.00, 0.00, 0.00
    $ date
    Wed May 22 05:26:24 UTC 2019

  I touched none of the system defaults, and yet the motd has not
  updated automatically.

    $ ls -l /var/cache/motd-news
    -rw-r--r-- 1 root root 0 May  9 22:53 /var/cache/motd-news

  The systemd timer unit looks like this:

    $ systemctl status motd-news.timer
    ● motd-news.timer - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor 
preset: enabled)
   Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 
days ago
  Trigger: n/a

    May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the
  Day.

  If I run /etc/update-motd.d/50-motd-news --force manually, the file
  does update correctly.

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

[Łukasz Zemczak]

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

Title:
  motd [on at least some instances] does not auto-update daily

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Cosmic:
  Fix Committed
Status in base-files source package in Disco:
  Fix Released
Status in base-files source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  motd-news timer is not properly configured and may not run regularly so long 
running systems will not get an updated motd

  [Test Case]
  The motd-news.timer is known to be incorrectly configured because 
motd-news.services is a one shot service which will not become active. 
Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not 
work reliably. However, because it can work some of the time it is difficult to 
find a case where the timer always fails so test case will involve only 
confirming that the new timer is correct.

  1) On a system with curl installed, install the new version of base-files
  2) Run 'systemctl list-timers motd* --all
  3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because 
we don't want people to miss important messages)
  4) Wait until "NEXT" is reached
  5) Confirm that there is another "NEXT" and that the time stamp of 
/var/cache/motd-news was updated

  [Regression Potential]
  I can't think of any on the client side as the job wasn't working as it was 
intended but it may cause extra load on the motd server.

  Original Description
  
  I have a VM running on AWS. It was launched on May 9th:

    $ uptime
     05:26:21 up 12 days,  6:34,  1 user,  load average: 0.00, 0.00, 0.00
    $ date
    Wed May 22 05:26:24 UTC 2019

  I touched none of the system defaults, and yet the motd has not
  updated automatically.

    $ ls -l /var/cache/motd-news
    -rw-r--r-- 1 root root 0 May  9 22:53 /var/cache/motd-news

  The systemd timer unit looks like this:

    $ systemctl status motd-news.timer
    ● motd-news.timer - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor 
preset: enabled)
   Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 
days ago
  Trigger: n/a

    May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the
  Day.

  If I run /etc/update-motd.d/50-motd-news --force manually, the file
  does update correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1757375] Re: Desktop unable to Suspend when Inactive

[Sebastien Bacher]

It's not ignored but the bug is about a 3 years old version of Ubuntu
and it got only one report in that time with 2 affect users, that makes
it a pretty low priority issue.

Also suspend on idle does work under Unity so maybe the issue is not the
with the permission but with the action xfce is using?

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

Do we have any idea when this will be fixed? Most of my users used to
get away with the DNS leakage and it was "only" a security problem but
stuff actually worked. Then the NM and other updates were shipped, we
set ipv4.dns-priority=-1 and ipv4.dns-search=~. and it all worked fine.
Then the NM update was pulled, and new installations aren't working at
all, even if we don't set the DNS config as described. There's nothing
that works for us except "dig out the package that has now been
unpublished, and install that".

An ETA for having this properly working again would be very much
appreciated.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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