[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Mathew Hodson]

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

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

** No longer affects: network-manager (Ubuntu)

** No longer affects: resolvconf (Ubuntu)

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

Title:
  No dns resolution after closing a vpn/pptp connection

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

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Mathew Hodson]

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Wishlist => Low

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Wishlist => Low

** Tags removed: verification-needed verification-needed-xenial
** Tags added: upgrade-software-version verification-done

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport this is an overview of all LP bugs the upload
  fixes:

  - most important bugs (feel free to add more)
     + LP: #1615381 : apt-get autoremove may remove current kernel

  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246 could use SRU template but seems straightforward
     + LP: #1260041 SRU template ok
     + LP: #1396787 SRU template ok
     + LP: #1446552 SRU template ok
     + LP: #1455097 SRU template ok
     + LP: #1458204 could use SRU template but seems straightforward
     + LP: #1577215 could use SRU template but seems straightforward
     + LP: #1602536 SRU template ok
     + LP: #1615381 could use SRU template but seems straightforward
     + LP: #1624644 SRU template ok
     + LP: #1649709 not affecting xenial
     + LP: #1654070 could use SRU template but seems straightforward
     + LP: #1654600 SRU template ok
     + LP: #1675079 SRU template ok
     + LP: #1680599 could use SRU template but seems straightforward
     + LP: #1686470 SRU template ok
     + LP: #1690980 SRU template ok
     + LP: #1698159 SRU template ok
     + LP: #1702793 this bug
     + LP: #1714019 just a merge request
     + LP: #1718419 just a merge request
     + LP: #1719630 SRU template ok
     + LP: #1722426 just a merge request
     + LP: #1737442 SRU template ok
     + LP: #1737635 SRU template ok
     + LP: #1737637 SRU template ok
     + LP: #1737717 SRU template ok
     + LP: #1741579 SRU template ok
     + LP: #1764797 just a merge request
     + LP: #1773033 SRU template ok
     + LP: #1775292 SRU template ok
     + LP: #1775307 SRU template ok
     + LP: #1778219 SRU template ok
     + LP: #1778800 SRU template ok
     + LP: #1779157 SRU template ok
     + LP: #1781176 SRU template ok
     + LP: #1781183 SRU template ok
     + LP: #1781446 SRU template ok
     + LP: #1781586 SRU template ok
     + LP: #1785093 SRU template ok
     + LP: #1789637 SRU template ok
     + LP: #1803749 SRU template ok

  [Regression Potential]

  * Due to this update covering the full backport unattended-upgrades
  can regress in any imaginable way including failing to install,
  upgrade, run, or removing essential packages from the system. Those
  are unlikely.* There are open bugs about u-u being slower than in the
  past, thus this may be a likely regression but IMO the pending speed
  optimizations should not be blocking the backport because the
  reliability issues are more important to fix and speed optimizations
  can be cherry-picked later.

  [Other Info]

  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html

  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.

  [Original Bug Text]

  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

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

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

[Touch-packages] [Bug 1815267] Re: package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 2

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Trying to upgrade in WSL.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.12.6-0ubuntu2
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Feb  8 22:33:57 2019
  Dmesg:
   [0.007816]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
   [0.249297] <3>init: (1) ERROR: ConfigMountDrvfsVolumes:1713: mount O: 
/mnt/o with options "uid=1000,gid=100
   [0.249308] " failed: 22
  DuplicateSignature:
   package:fontconfig-config:2.12.6-0ubuntu2
   Unpacking gtk-update-icon-cache (3.24.1-1ubuntu2) over (3.22.30-1ubuntu1) ...
   dpkg-deb: error: tar subprocess was killed by signal (Segmentation fault), 
core dumped
   dpkg: error processing archive 
/tmp/apt-dpkg-install-5wk29P/014-fontconfig-config_2.13.0-5ubuntu3_all.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (0 days ago)

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

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

[Touch-packages] [Bug 1815267] [NEW] package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Nick]

Public bug reported:

Trying to upgrade in WSL.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: fontconfig-config 2.12.6-0ubuntu2
ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
Uname: Linux 4.4.0-17763-Microsoft x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Feb  8 22:33:57 2019
Dmesg:
 [0.007816]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
 [0.249297] <3>init: (1) ERROR: ConfigMountDrvfsVolumes:1713: mount O: 
/mnt/o with options "uid=1000,gid=100
 [0.249308] " failed: 22
DuplicateSignature:
 package:fontconfig-config:2.12.6-0ubuntu2
 Unpacking gtk-update-icon-cache (3.24.1-1ubuntu2) over (3.22.30-1ubuntu1) ...
 dpkg-deb: error: tar subprocess was killed by signal (Segmentation fault), 
core dumped
 dpkg: error processing archive 
/tmp/apt-dpkg-install-5wk29P/014-fontconfig-config_2.13.0-5ubuntu3_all.deb 
(--unpack):
  dpkg-deb --control subprocess returned error exit status 2
ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.2
SourcePackage: fontconfig
Title: package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
UpgradeStatus: Upgraded to cosmic on 2019-02-09 (0 days ago)

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


** Tags: amd64 apport-package cosmic uec-images

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

Title:
  package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 2

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Trying to upgrade in WSL.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.12.6-0ubuntu2
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Feb  8 22:33:57 2019
  Dmesg:
   [0.007816]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
   [0.249297] <3>init: (1) ERROR: ConfigMountDrvfsVolumes:1713: mount O: 
/mnt/o with options "uid=1000,gid=100
   [0.249308] " failed: 22
  DuplicateSignature:
   package:fontconfig-config:2.12.6-0ubuntu2
   Unpacking gtk-update-icon-cache (3.24.1-1ubuntu2) over (3.22.30-1ubuntu1) ...
   dpkg-deb: error: tar subprocess was killed by signal (Segmentation fault), 
core dumped
   dpkg: error processing archive 
/tmp/apt-dpkg-install-5wk29P/014-fontconfig-config_2.13.0-5ubuntu3_all.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.12.6-0ubuntu2 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (0 days ago)

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

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

[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window

[jimav]

xdg-open http://bugs.launchpad.net opens the page in Firefox.

I use zdg-open routinely.

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

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

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

[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window

[jimav]

x not z

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Taylor Raack]

I can also confirm that the network-manager package version
1.10.14-0ubuntu1 from bionic-proposed fixes the issue.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

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

  Configure the system to send all the traffic to a VPN, do a name
  resolution, the request should not go to the public DNS server (to be
  checked by capturing the traffic by example with wireshark)

  
  * 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 1807437] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Launchpad Bug Tracker]

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

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

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Expired

Bug description:
  On startuo I got an error message,three consecutive times now, saying
  system failed to load package. Weirdly, another message appears saying
  my software is up to date. When I 'x' it. I'm left with the option of
  reporting the bug failure, which I'm doing now.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   usbmuxd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec  7 19:01:57 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-07-29 (861 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config line 13: Deprecated option UsePrivilegeSeparation
   /etc/ssh/sshd_config line 16: Deprecated option KeyRegenerationInterval
   /etc/ssh/sshd_config line 17: Deprecated option ServerKeyBits
   /etc/ssh/sshd_config line 30: Bad SSH2 mac spec 
'hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com'.
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (205 days ago)

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

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

[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release

[Nataraj]

Tested mesa 18.2.8 from bionic-proposed and the fix worked for the
problem I was having with vlc.

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

Title:
  Mesa 18.2.8 stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point 
release of the series. This will also be backported to 18.04 as part of the HWE 
stack update.

  Upstream changes:

  18.2.3
  - Different patches for the DirectX9 and DRI state trackers.
  - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza 
and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky.
  - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, 
anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in
  Radeonsi.
  - State Trackers also get different fixes and corrections.
  - Finally, fixes for GLSL and NIR are also in this queue.

  18.2.4
  - Different fixes for different drivers: freedreno, radeonsi, swr, anv and 
radv.
  - Also there are fixes for ac, gallium, spirv and blorp.

  18.2.5
  - A patch for nine state tracker that fixes several crashes using nine's
  thread_submit feature. There are other patches to other state trackers.
  - A couple of patches for Meson build system, as well as for autotools.
  - In the drivers side, there are a couple of fixes for RADV, one regarding
  subgroups and another regarding conditional rendering. There are also fixes 
for virgl, r600, and i965.
  - Finally, the queue contains a couple of fixes for NIR, Wayland, and other
  components.

  18.2.6
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.7
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.8
  - Several fixes in Meson build system.
  - Also several fixes for st/nine subcomponent.
  - Patch for RADV driver that fixes a hang in Yakuza using DXVK.
  - There are also fixes for Virgl driver.
  - Added PCI IDs for VegaM, Vega20 and Vega10.

  
  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems, this is the last of the 
series so should be safe to update to.

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

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

[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running

[Brian Murray]

** Changed in: apport (Ubuntu)
 Assignee: alaaabdo (alaaabdo201222) => Brian Murray (brian-murray)

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

Title:
  apport-autoreport.service fails if whoopsie isn't running

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  If automatic crash reporting is enabled and apport-autoreport.service starts 
before whoopsie on boot then crash reports that happened during shutdown or 
start up will not be automatically uploaded to the error tracker.

  Test Case
  -
  1) install apport-noui
  2) sudo service apport stop
  3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating 
the situation where whoopsie isn't running. I did this by copying lines 159,160 
to 161,162 and unindenting them. N.B. this isn't necessary if you are on a 
system where whoopsie is starting after apport.
  4) touch /var/crash/my.crash
  5) reboot
  5) run 'systemctl status apport-autoreport.service' and observe it failed 
because whoopsie isn't running

  When testing the proposed version of apport you'll want to revert the
  changes you made to whoopsie-upload-all. With the version of apport
  from -proposed you should no longer see the failure message for the
  apport-autoreport.service. The best test case is just having an
  affected system test the package from -proposed though.

  Regression Potential
  
  We are clearly fixing something that was a mistake in the original service so 
there is little chance for regression.

  

  ProblemType: BugDistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

[El jinete sin cabeza]

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

** Description changed:

+ https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
+ 
+ ---
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
  
  ---
  
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
- I'm not sure, but this happened after updating to gstreamer 1.15.1
+ I'm not sure, but this happened after updating to gstreamer 1.15.1.  The
+ problem occurs when I maximize totem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

- https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
- 
- ---
- 
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1.  The
  problem occurs when I maximize totem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-l

[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running

[alaaabdo]

** Changed in: apport (Ubuntu)
 Assignee: Brian Murray (brian-murray) => alaaabdo (alaaabdo201222)

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

Title:
  apport-autoreport.service fails if whoopsie isn't running

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  If automatic crash reporting is enabled and apport-autoreport.service starts 
before whoopsie on boot then crash reports that happened during shutdown or 
start up will not be automatically uploaded to the error tracker.

  Test Case
  -
  1) install apport-noui
  2) sudo service apport stop
  3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating 
the situation where whoopsie isn't running. I did this by copying lines 159,160 
to 161,162 and unindenting them. N.B. this isn't necessary if you are on a 
system where whoopsie is starting after apport.
  4) touch /var/crash/my.crash
  5) reboot
  5) run 'systemctl status apport-autoreport.service' and observe it failed 
because whoopsie isn't running

  When testing the proposed version of apport you'll want to revert the
  changes you made to whoopsie-upload-all. With the version of apport
  from -proposed you should no longer see the failure message for the
  apport-autoreport.service. The best test case is just having an
  affected system test the package from -proposed though.

  Regression Potential
  
  We are clearly fixing something that was a mistake in the original service so 
there is little chance for regression.

  

  ProblemType: BugDistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 799585] Re: cannot change "open with" option to non-standard program

[Sebastien Bacher]

The dialog comes from gtk, upstream already stated that programs need to
provide a .desktop and it's not the filemanager/selector job to create
those. They don't plan to add that feature to gtk itself but it's easy
enough to create a such entry

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  cannot change "open with" option to non-standard program

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  Won't Fix

Bug description:
  In Oneiric, you cannot change the program used to open a file to a 
non-standard program.
  I use the daily build of Libreoffice, which is loaded in the /opt/ folder.
  There is no way I can get to the program from the oeneric interface other 
than by calling the program up in a terminal.
  This is incredibly inconvenient.

  TEST CASE:
  1. Launch Nautilus (Launcher -> Files)
  2. Right-click on a file
  3. On the contextual menu select "Open With / Other Application ..." or "Open 
with other application..."
  4. On the untitled dialog click on "Show other applications"

  Result:
  There is a list of "Recommended Applications" and "Other Applications" but no 
way to select/add an application other than those being on the list.

  Expected:
  Ability to add an application to the list from the UI

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
  Uname: Linux 3.0-1-generic x86_64
  Architecture: amd64
  Date: Sun Jun 19 22:42:27 2011
  InstallationMedia: Ubuntu-Studio 11.04 "Natty Narwhal" - Release amd64 
(20110426.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Steve Langasek]

This SRU claims for regression-potential:

> Low. The quirk uses strict DMI to match affected systems.

This doesn't appear to be true for the changes to upower, which include
no DMI quirking whatsoever.  Please clarify this.

** Changed in: upower (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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

[Touch-packages] [Bug 799585] [NEW] cannot change "open with" option to non-standard program

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Oneiric, you cannot change the program used to open a file to a non-standard 
program.
I use the daily build of Libreoffice, which is loaded in the /opt/ folder.
There is no way I can get to the program from the oeneric interface other than 
by calling the program up in a terminal.
This is incredibly inconvenient.

TEST CASE:
1. Launch Nautilus (Launcher -> Files)
2. Right-click on a file
3. On the contextual menu select "Open With / Other Application ..." or "Open 
with other application..."
4. On the untitled dialog click on "Show other applications"

Result:
There is a list of "Recommended Applications" and "Other Applications" but no 
way to select/add an application other than those being on the list.

Expected:
Ability to add an application to the list from the UI

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubuntu-desktop (not installed)
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic x86_64
Architecture: amd64
Date: Sun Jun 19 22:42:27 2011
InstallationMedia: Ubuntu-Studio 11.04 "Natty Narwhal" - Release amd64 
(20110426.1)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nautilus
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Won't Fix


** Tags: amd64 apport-bug oneiric precise running-unity testcase
-- 
cannot change "open with" option to non-standard program
https://bugs.launchpad.net/bugs/799585
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Steve Langasek]

Hello Bryan, or anyone else affected,

Accepted busybox into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/busybox/1:1.27.2-2ubuntu3.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: busybox (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Fix Released
Status in debirf package in Ubuntu:
  Confirmed
Status in busybox source package in Bionic:
  Fix Committed
Status in debirf source package in Bionic:
  Confirmed
Status in busybox source package in Cosmic:
  Fix Released
Status in debirf source package in Cosmic:
  Confirmed

Bug description:
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-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/1807719

Title:
  Some emoji in emoji chooser are black & white

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:
  Fix Committed

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

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

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

[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-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/1807721

Title:
  Fix variant selection in emoji chooser

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:
  Fix Committed

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

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

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

[Touch-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

[El jinete sin cabeza]

** Description changed:

+ https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)

  ---

  https://gitlab.gnome.org/GNOME/totem/issues/297

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Seth Arnold]

Hi Michael, probably "new bug report" would have been the better choice.

See if this will show you more details:
journalctl -eu ssh

Thanks

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

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

Status in openssh package in Ubuntu:
  Expired

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

[El jinete sin cabeza]

https://gitlab.gnome.org/GNOME/totem/issues/297#note_432608

Bastien Nocera:
"Looks like a crash inside the application side intel driver inside Mesa. It's 
going to be a driver problem rather than something that totem can deal with."

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

** Also affects: xserver-xorg-video-intel (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/1815236

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/297

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Michael Terranova]

and here's the output of ps fauxw

** Attachment added: "output-of_ps-fauxw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713435/+attachment/5237108/+files/output-of_ps-fauxw.txt

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

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

Status in openssh package in Ubuntu:
  Expired

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Michael Terranova]

Sorry I'm a noob. Don't know much about this other than I'd bet that if it 
happened to me during this recent update maybe others are affected as well
I see someone was asked earlier for this:

~$ sudo systemctl status ssh.service

● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab
   Active: failed (Result: start-limit-hit) since Fri 2019-02-08 16:25:20 EST; 2
  Process: 21889 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Unit entered failed state.
Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Service hold-off time over, sched
Feb 08 16:25:20 ayumu systemd[1]: Stopped OpenBSD Secure Shell server.
Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Start request repeated too quickl
Feb 08 16:25:20 ayumu systemd[1]: Failed to start OpenBSD Secure Shell server.
Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Unit entered failed state.
Feb 08 16:25:20 ayumu systemd[1]: ssh.service: Failed with result 'start-limit-h
lines 1-13/13 (END)

I will try to attach the other two previously-requested things

** Attachment added: "sudo netstat -anp"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713435/+attachment/5237107/+files/output-of-netstat-anp.txt

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

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

Status in openssh package in Ubuntu:
  Expired

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815172] Update Released

[Adam Conrad]

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.2

---
mesa (18.2.2-0ubuntu1~18.04.2) bionic; urgency=medium

  * i965-revert-enabling-softpin.diff: Don't enable softpin, causes
issues on 32bit installs. (LP: #1815172)

 -- Timo Aaltonen   Fri, 08 Feb 2019 19:12:58 +0200

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

[Brian Murray]

** Tags added: bionic disco rls-dd-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/1814072

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

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

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

[Touch-packages] [Bug 1800559] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Package changed: adduser (Ubuntu) => initramfs-tools (Ubuntu)

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-free-space

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

Title:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  randy@randy-Inspiron-518:~$ sudo apt-get updates
  [sudo] password for randy: 
  E: Invalid operation updates
  randy@randy-Inspiron-518:~$ sudo apt-get update
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
 
  Hit:2 http://archive.canonical.com/ubuntu xenial InRelease
 
  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
 
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]   
 
  Fetched 216 kB in 1s (147 kB/s)   
 
  Reading package lists... Done
  randy@randy-Inspiron-518:~$ sudo apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
linux-generic linux-headers-generic linux-image-generic
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  4 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.122ubuntu8.13) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-image-extra-4.4.0-137-generic (4.4.0-137.163) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.4.0-137-generic /boot/vmlinuz-4.4.0-137-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-4.4.0-137-generic 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-extra-4.4.0-137-generic; however:
Package linux-image-extra-4.4.0-137-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-image-generic (= 4.4.0.137.143); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for initramfs-tools (0.122ubuntu8.13) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
No apport report written because the error message 
indicates its a followup error from a previous failure.
  update-initramfs: 
Generating /boot/initrd.img-4.4.0-137-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-4.4.0-137-generic
   linux-image-generic
   linux-generic
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  randy@randy-Inspiron-518:~$ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  4 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up initramfs-tools (0.122ubuntu8.13) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-image-extra-4.4.0

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Alkis Georgopoulos]

I verify that the bionic-proposed package addresses the issue.

Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 
[8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel driver in use: i915


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

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Till Kamppeter]

Attached is the debdiff with the proposed fix of comment #19 applied.
Someone with appropriate upload rights to Disco, please upload it.

I could not actually test it as I have no access to a Microsoft VPN,

I do not see any regression though. I can access Canonical's VPNs and
while having activated one and also after deactivating it I always have
DNS correctly working.

To the original poster: As soon as this is in Disco (or building the
fixed package by yourself) please test whether this helps. If the fixed
package does not solve your problem, we will try the proposed "cp -a
..." fixes.

** Patch added: "ppp_2.4.7-2+4ubuntu3_2.4.7-2+4ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+attachment/5237098/+files/ppp_2.4.7-2+4ubuntu3_2.4.7-2+4ubuntu4.debdiff

** Tags added: patch

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Invalid
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1814933] Re: Ambiance/Radiance: path-bar is broken with nautilus > 3.30

[Adolfo Jayme]

** Description changed:

  Nautilus 3.30 has new path-bar. And hence it doesn't look good with
  current design.
  
  I had several ideas to solve the problem. Hence opened a discussion
- thread in community hub to get opinions from developers and users.
+ thread in community hub [1] to get opinions from developers and users.
  
  See:
  
  I will open a merge once this gets finalized.
+ 
+ [1]: https://discourse.ubuntu.com/t/ambiance-radiance-path-bar-redesign-
+ for-nautilus-3-30/9706

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

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

Title:
  Ambiance/Radiance: path-bar is broken with nautilus > 3.30

Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Nautilus 3.30 has new path-bar. And hence it doesn't look good with
  current design.

  I had several ideas to solve the problem. Hence opened a discussion
  thread in community hub [1] to get opinions from developers and users.

  See:

  I will open a merge once this gets finalized.

  [1]: https://discourse.ubuntu.com/t/ambiance-radiance-path-bar-
  redesign-for-nautilus-3-30/9706

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

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

[Touch-packages] [Bug 1814818] Re: Skip enslaved devices during boot

[Adam Conrad]

Hello Marcelo, or anyone else affected,

Accepted initramfs-tools into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.131ubuntu15.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: initramfs-tools (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

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

Title:
  Skip enslaved devices during boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  In some scenarios, we need to skip enslaved network devices from being
  brought up in initrd.

  In order to avoid regressions for other users, the new behaviour is
  being conditioned to the configuration variable NETWORK_SKIP_ENSLAVED.
  This mechanism enable us to use it only for the required kernels. The
  target kernel should be responsible to include the configuration via
  an initramfs-tools hook.

  [Test Case]

  Enslaved network devices shouldn't be brought up when the
  configuration is set by certain kernels. For any other scenario, such
  as the generic Ubuntu kernel, the behaviour should not be changed.

  [Regression Potential]

  The potential for regressions was vastly reduced by conditioning the
  new behaviour.

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

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

[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.4-0ubuntu1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 3.24.3 releases.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
  font you have installed: currently, that's fonts-symbola which we no
  longer install by default). Previously, it was ❙/○ for most languages
  but ON/OFF for English (because English has short words that could fit
  on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.5 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

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

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

[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.4-0ubuntu1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

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

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

[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

[Steve Langasek]

Hello Jeremy, or anyone else affected,

Accepted gtk+3.0 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.4-0ubuntu1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

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

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

[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.5.0+19.04.20190208-0ubuntu1

---
unity (7.5.0+19.04.20190208-0ubuntu1) disco; urgency=medium

  [ Alberts Muktupāvels ]
  * Install compiz configuration files.

  [ Khurshid Alam ]
  * Recommend nemo for unity. (LP: #1814506)

 -- Dmitry Shachnev   Fri, 08 Feb 2019 11:46:59
+

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

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

Title:
  Use nemo-desktop to draw desktop icons under Unity (Disco)

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have
  the desktop any more. The alternate options are to use caja-desktop or
  nemo-desktop keeping nautilus default file manger for now. Since nemo-
  desktop does not require any extensive patching it is easy to use
  under unity.

  Nemo-desktop will only draw the icons, not the background. In absence of
  nautilus unity-settings-daemon draws the background, so nothing to do in 
u-s-d.

  There are few small patches (nemo action files) required from nemo. 
@fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship 
  these action files ourselves as recommended by upstream. Budgie is doing the 
same.
  
https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions

  
  Since nautilus still be default file-manager we disable auto-mount with nemo 
and various other cinnamon/nemo option in ubuntu-settings.gsettings-override

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

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

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Brad Figg]

** Tags added: bjf-tracking

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1815228] Re: packagekitd crashed with SIGABRT

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1814885
   packagekitd crashed with SIGABRT in std::terminate()

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  its a been a while since i got this bug. my version shows 19.04 but
  using disco 19.10

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: packagekit 1.1.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Feb  8 13:43:02 2019
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2016-10-05 (856 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/sh
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2018-12-06 (64 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

[onli]

I forgot to link the upstream issue:
https://gitlab.gnome.org/GNOME/mutter/issues/204

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

Title:
  [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When Wayland is activated in GDM, nothing happens when selecting an
  account with the keyboard or typing in the password. I have to type,
  then wait, then move the mouse around for the characters to appears.

  Because I wouldn't believe this report, I made a video of the problem:
  https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf-
  f2a74f952ca5

  Moving from Wayland to X makes the issue disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 18:39:19 2018
  InstallationDate: Installed on 2018-06-17 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184

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

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

[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Adam Conrad]

Hello Timo, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Touch-packages] [Bug 1811225] Please test proposed package

[Adam Conrad]

Hello Timo, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Mesa 18.2.8 stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point 
release of the series. This will also be backported to 18.04 as part of the HWE 
stack update.

  Upstream changes:

  18.2.3
  - Different patches for the DirectX9 and DRI state trackers.
  - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza 
and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky.
  - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, 
anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in
  Radeonsi.
  - State Trackers also get different fixes and corrections.
  - Finally, fixes for GLSL and NIR are also in this queue.

  18.2.4
  - Different fixes for different drivers: freedreno, radeonsi, swr, anv and 
radv.
  - Also there are fixes for ac, gallium, spirv and blorp.

  18.2.5
  - A patch for nine state tracker that fixes several crashes using nine's
  thread_submit feature. There are other patches to other state trackers.
  - A couple of patches for Meson build system, as well as for autotools.
  - In the drivers side, there are a couple of fixes for RADV, one regarding
  subgroups and another regarding conditional rendering. There are also fixes 
for virgl, r600, and i965.
  - Finally, the queue contains a couple of fixes for NIR, Wayland, and other
  components.

  18.2.6
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.7
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.8
  - Several fixes in Meson build system.
  - Also several fixes for st/nine subcomponent.
  - Patch for RADV driver that fixes a hang in Yakuza using DXVK.
  - There are also fixes for Virgl driver.
  - Added PCI IDs for VegaM, Vega20 and Vega10.

  
  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems, this is the last of the 
series so should be safe to update to.

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

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

[Touch-packages] [Bug 1815172] Please test proposed package

[Adam Conrad]

Hello Alkis, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Adam Conrad]

Hello Alkis, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

** Tags added: verification-needed-cosmic

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  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

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 1815227] [NEW] I don't know

[andrea]

Public bug reported:

The computer is very slow

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  8 19:22:14 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller 
[104d:90c3]
InstallationDate: Installed on 2017-11-08 (457 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Sony Corporation SVF14N2J2ES
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7882e147-2858-4dbd-ad0b-e8eedad25132 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1130DD
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1130DD:bd04/22/2014:svnSonyCorporation:pnSVF14N2J2ES:pvrC10KKKAB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: SVF14N2
dmi.product.name: SVF14N2J2ES
dmi.product.version: C10KKKAB
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Tue Jan 15 18:04:54 2019
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic 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/1815227

Title:
  I don't know

Status in xorg package in Ubuntu:
  New

Bug description:
  The computer is very slow

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  8 19:22:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller 
[104d:90c3]
  InstallationDate: Installed on 2017-11-08 (457 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Sony Corporation SVF14N2J2ES
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7882e147-2858-4dbd-ad0b-e8eedad25132 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1130DD
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1130DD:bd04/22/2014:svnSonyCorporation:pnSVF14N2J2ES:pvrC10KKKAB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: SVF14N2
  dmi.product.name: SVF14N2J2ES
  dmi.product.ver

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[Ads20000]

This is an upstream GNOME bug (though you might want to make the case that 
Ubuntu should deviate from the default GNOME behaviour for this issue, in which 
case please open a new bug since I don't think standard practice is to re-open 
old bugs like this when it has been fixed in an Ubuntu release? I think you 
could reasonably tag the new bug as a regression. If you do make a new bug for 
this issue in newer Ubuntu releases then please link to it from here), please 
+1 (use the thumbs up button on the original Issue and comments that you agree 
with, don't comment a +1) the following issues to indicate your support for a 
restoration of type-ahead. On unlocked Issues you can also comment specific 
use-cases which a lack of type-ahead breaks and which the optimizations 
mentioned in https://gitlab.gnome.org/GNOME/nautilus/issues/246 and 
https://gitlab.gnome.org/GNOME/nautilus/issues/247 don't fix (if you think 
those optimizations would help your use-case then please +1 them). Specific 
use-cases where you absolutely NEED type-ahead search may change the 
developers' minds, if you don't have specific use-cases then just +1 comments 
on GNOME GitLab that you agree with, but we're unlikely to see much change in 
that case, we NEED specific use-cases:
https://gitlab.gnome.org/GNOME/nautilus/issues/8 (unlocked)
https://gitlab.gnome.org/GNOME/nautilus/issues/244 (locked)
https://gitlab.gnome.org/GNOME/nautilus/issues/466 (unlocked)
https://gitlab.gnome.org/GNOME/nautilus/issues/590 (unlocked)

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Justin Bull]

Hi Daniel,

I reported the bug
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551 which had
its status changed to Confirmed yesterday.

Thanks for getting back to me.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Daniel Holbert]

Hi Justin! Original reporter here -- I've been running Ubuntu 18.10
since release, and I've never once been able to reproduce this issue on
that version.

I have the same gnome-shell version as you, and I tested Firefox 65
(official version from Ubuntu repos) and am still unable to reproduce.

I'd suggest you file a new bug and link it from here.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Timo Aaltonen]

this is caused by enabling softpin in mesa, which is supported in kernel
4.5 and up but is still somewhat buggy as seen here.. we need these
commits backported to the kernel:

9125963a9494253fa5a29cc1b4169885d2be7042 drm/i915: Mark up GTT sizes as u64
6fc4e48f9ed46e9adff236a0c350074aafa3b7fa drm/i915: Compare user's 64b GTT 
offset even on 32b

but since 18.04.2 is about to be released, it's best to revert enabling
softpin in mesa, and enable it again for 18.04.3.

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  New

Bug description:
  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

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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Dimitri John Ledkov]

I'm afraid it just missed it, i think. But we can try.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  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:
  Fix Released

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=

[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

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

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

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

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

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 47958] Re: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

[Benjamin Buch]

This bug is still present the latest Ubuntu 18.04.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

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

Bug description:
  Since /usr/bin/ssh-agent is setgid ssh, it unsets LD_LIBRARY_PATH.
  This made it impossible to set this variable in my dotfiles
  (.gnomerc).

  My solution was to write a wrapper script that prefixes the command with 
/usr/bin/env VAR=val ... for each variable that gets unset:


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

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

[Touch-packages] [Bug 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades

[ITEAS]

Sorry for the late reply ;( I've not tested it on xenial, but on bionic
it is working perfectly. Thanks a lot. Great work.

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The confusing text on shutdown is, well, can confuse users.
   * This fix itself is minor and would not warrant a backport but it is 
backported as part of fully backporting Bionic's u-u version to Xenial.

  [Test Case]

   * Check that the status text is less confusing than it was previously
  either by configuring unattended-upgrades to run at shutdown and
  waiting for the text to appear or check that the text is changed in
  unattended-upgrades-shutdown:

  $ grep -B1 please /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
  msg = _("Unattended-upgrade in progress during shutdown, "
  "please don't turn off the computer")

* The former way or the verification may not be easy since with the fix for 
LP: #1803137 the shutdown screen does not show up when u-u-shutdown starts 
running, see the bug for the details.
* Also checking unatttended-upgrades-shutdown for the changed text does not 
ensure that the translation is ready, too.

  [Regression Potential]

   * The updated text should not cause major issues, but until it is
  translated to each language it is shown in English, possibly confusing
  users in a different way.

  [Original Bug Text]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion.
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

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

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

[Touch-packages] [Bug 1774443] Re: wireless hardblocked and wireless enable button not functional

[Kai-Heng Feng]

Does this still happen on latest mainline kernel?

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

Title:
  wireless hardblocked and wireless enable button not functional

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and
  ubuntu. In Windows, system boots with wireless disabled and then
  pressing the wireless enable button twice enables WiFi.

  In ubuntu, system boots with wireless disabled and wireless enable
  button has no functionality either directly or in combination with the
  fn-key.

  Module hp_wmi may be the culprit? But disabling this has no effect on
  hardblock.

  reference forum post for more detailed info:
  https://ubuntuforums.org/showthread.php?t=2392934&p=13772159#post13772159

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 31 10:32:38 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-19 (11 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 172.16.96.1 dev eno1  proto static  metric 100 
   169.254.0.0/16 dev eno1  scope link  metric 1000 
   172.16.96.0/19 dev eno1  proto kernel  scope link  src 172.16.119.109  
metric 100 
   192.17.90.180 via 172.16.96.1 dev eno1  proto dhcp  metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  802-3-ethernet  
1527780471  Thu 31 May 2018 10:27:51 AM CDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp8s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  naww   1928 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-19 (32 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u3  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u3  scope link  metric 1000 
   192.168.42.0/24 dev enp0s20u3  proto kernel  scope link  src 192.168.42.168  
metric 100
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

[Bug Watch Updater]

** Changed in: apt (Debian)
   Status: Unknown => Fix Released

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic   | source, ...
   apt | 1.7.0   | cosmic   | source, ...
   apt | 1.8.0~rc2   | disco| source, ...

  [Test Case]
  1) Deploy a Trusty (14.04 LTS) vm w/ 128M
  2) Fetch latest stress-ng src code
   2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
   2.2) cd stress-ng
   2.3) make clean
   2.4) make
  3) Stress the mmap() with stress-ng
   3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
  4) Disable swap (if any)
   4.1) swapoff -a
  5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
  ...
  vsftpd:
Installed: (none)
Candidate: 3.0.2-1ubuntu2.14.04.1
Version table:
   3.0.2-1ubuntu2.14.04.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   3.0.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  ...

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

[Julian Andres Klode]

FWIW, you should also be able to turn off overcommitting in the kernel
and/or set a ulimit -v to make things easier to reproduce.

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic   | source, ...
   apt | 1.7.0   | cosmic   | source, ...
   apt | 1.8.0~rc2   | disco| source, ...

  [Test Case]
  1) Deploy a Trusty (14.04 LTS) vm w/ 128M
  2) Fetch latest stress-ng src code
   2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
   2.2) cd stress-ng
   2.3) make clean
   2.4) make
  3) Stress the mmap() with stress-ng
   3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
  4) Disable swap (if any)
   4.1) swapoff -a
  5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
  ...
  vsftpd:
Installed: (none)
Candidate: 3.0.2-1ubuntu2.14.04.1
Version table:
   3.0.2-1ubuntu2.14.04.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   3.0.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  Segmentation fault (core dumped)
  ...

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1737442] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1706:main:__init__:__init__:open

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:

The crash does not seem to be occurring even in different form:
https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=unattended-upgrades&period=year&version=1.1ubuntu1.18.04.7~16.04.1


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

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

Title:
  /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
  upgrade@1706:main:__init__:__init__:open

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades crashes when initializing the cache preventing 
security updates to be applied.
   * The fix prints an error message then exits

  [Test Case]

   * Observe
  https://errors.ubuntu.com/problem/cb12eff1497c73b95a2a51f4213bc3f30f2ac4d5
  not happening in fixed releases

  [Regression Potential]

   * The fix is simply catching the error and exiting, there is little
  room for regressions. In the worst case u-u crashes differently when
  printing the error.

  [Original Bug Text]

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/933de54e4841d617eb5c73ab02bb2d3be522a6ff 
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/unattended-upgrades/+bug/1737442/+subscriptions

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:

root@x-uu-ref:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# grep dpkg-dev /var/lib/dpkg/info/unattended-upgrades.* ; echo 
$?
1


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

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades may fail to install due to missing dpkg-vendor command.
   * The fix is using lsb_release which is provided by dependencies.

  [Test Case]

   * Install unattended-upgrades, then check the maintainer scripts to not have 
reference to dpkg-dev:
  $ grep dpkg-dev /var/lib/dpkg/info/unattended-upgrades.* ; echo $?
  1

  [Regression Potential]

   * lsb_release may fail but that would be a different, bigger issue affecting 
many other programs. This is unlikely.
   * Changed maintainer scripts may fail due to errors introduced with the fix. 
Since those scripts had extensive testing in later releases by now it looks 
like unlikely to occur, too.

  [Original Bug Text]

  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

[Heitor R. Alves de Siqueira]

** Description changed:

  [Impact]
  apt crashes (core dump) during cache creation
  
  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.
  
  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1
  
  $ git describe --contains 6789e01e9370
  1.1_exp16~5
  
  $ rmadison apt
-  apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
-  apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
-  apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
-  apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
-  apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
-  apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
-  apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x
- 
+  apt | 1.0.1ubuntu2| trusty   | source, ...
+  apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
+  apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
+  apt | 1.2.10ubuntu1   | xenial   | source, ...
+  apt | 1.6.1   | bionic   | source, ...
+  apt | 1.7.0   | cosmic   | source, ...
+  apt | 1.8.0~rc2   | disco| source, ...
  
  [Test Case]
- Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.
+ 1) Deploy a Trusty (14.04 LTS) vm w/ 128M
+ 2) Fetch latest stress-ng src code
+  2.1) git clone git://kernel.ubuntu.com/cking/stress-ng
+  2.2) cd stress-ng
+  2.3) make clean
+  2.4) make
+ 3) Stress the mmap() with stress-ng
+  3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90%
+ 4) Disable swap (if any)
+  4.1) swapoff -a
+ 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done
+ ...
+ vsftpd:
+   Installed: (none)
+   Candidate: 3.0.2-1ubuntu2.14.04.1
+   Version table:
+  3.0.2-1ubuntu2.14.04.1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
+  3.0.2-1ubuntu2 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
+ ...
  
  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, ...
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, ...
   apt | 1.2.10ubuntu1   | xenial   | source, ...
   apt | 1.6.1   | bionic 

[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I'm pretty sure you need to adjust the "chat mix" knob on your headset
as the audio will now be playing through a separate audio device on the
headset.  Basically previously it was using the mono "chat"/mono output
on the headphones.  Now with the ppa it's primarily using the
"game"/stereo output.  AFAIU the knob adjusts the mix between the two
outputs on the headphones themselves.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1737635] Re: Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:

The crash does not seem to be occurring even in different form:
https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=unattended-upgrades&period=year&version=1.1ubuntu1.18.04.7~16.04.1

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

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

Title:
  Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades crashes at the end of its run before sending
  out upgrade report email when dpkg's log contains invalid UTF-8
  characters.

  
  [Test Case]

   * Observe
  https://errors.ubuntu.com/problem/4617feba656f6ec216996b0f1f662ae13904b9f8
  not occurring again

  [Regression Potential]

   * The fix is minimal, only replacing invalid characters with �.
  Regressions in u-u are unlikely but tools may break consuming
  unattended-upgrades output in case they can't handle the replacement
  marker.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa 
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/.

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1706, in 
  main(options)
    File "/usr/bin/unattended-upgrade", line 1619, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
    File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content
  for line in fp.readlines():
    File "/usr/lib/python3.6/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: 
invalid continuation byte

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

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

[Touch-packages] [Bug 1803749] Re: apt.Cache.clear() may set apt.Package.is_auto_removable to False

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:

$ sudo chroot x-test-1803749/
root@MacBookAir-test:/# apt install unattended-upgrades zsh
Reading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
  iso-codes python-apt-common python3-apt xz-utils zsh-common
Suggested packages:
  isoquery python3-apt-dbg python-apt-doc bsd-mailx mail-transport-agent zsh-doc
The following NEW packages will be installed:
  iso-codes python-apt-common python3-apt unattended-upgrades xz-utils zsh 
zsh-common
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 6354 kB of archives.
After this operation, 32.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 zsh-common all 
5.1.1-1ubuntu2 [3170 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 zsh amd64 
5.1.1-1ubuntu2 [651 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 iso-codes all 3.65-1 
[2268 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/main amd64 python-apt-common all 
1.1.0~beta1build1 [17.3 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 python3-apt amd64 
1.1.0~beta1build1 [137 kB]
Get:6 http://archive.ubuntu.com/ubuntu xenial/main amd64 xz-utils amd64 
5.1.1alpha+20120614-2ubuntu2 [78.8 kB]
Get:7 http://archive.ubuntu.com/ubuntu xenial/main amd64 unattended-upgrades 
all 0.90 [31.6 kB]
Fetched 6354 kB in 6s (1024 kB/s)   
  
Preconfiguring packages ...
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package zsh-common.
(Reading database ... 10444 files and directories currently installed.)
Preparing to unpack .../zsh-common_5.1.1-1ubuntu2_all.deb ...
Unpacking zsh-common (5.1.1-1ubuntu2) ...
Selecting previously unselected package zsh.
Preparing to unpack .../zsh_5.1.1-1ubuntu2_amd64.deb ...
Unpacking zsh (5.1.1-1ubuntu2) ...
Selecting previously unselected package iso-codes.
Preparing to unpack .../iso-codes_3.65-1_all.deb ...
Unpacking iso-codes (3.65-1) ...
Selecting previously unselected package python-apt-common.
Preparing to unpack .../python-apt-common_1.1.0~beta1build1_all.deb ...
Unpacking python-apt-common (1.1.0~beta1build1) ...
Selecting previously unselected package python3-apt.
Preparing to unpack .../python3-apt_1.1.0~beta1build1_amd64.deb ...
Unpacking python3-apt (1.1.0~beta1build1) ...
Selecting previously unselected package xz-utils.
Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2ubuntu2_amd64.deb ...
Unpacking xz-utils (5.1.1alpha+20120614-2ubuntu2) ...
Selecting previously unselected package unattended-upgrades.
Preparing to unpack .../unattended-upgrades_0.90_all.deb ...
Unpacking unattended-upgrades (0.90) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Setting up zsh-common (5.1.1-1ubuntu2) ...
Setting up zsh (5.1.1-1ubuntu2) ...
update-alternatives: using /bin/zsh5 to provide /bin/zsh (zsh) in auto mode
update-alternatives: using /bin/zsh5 to provide /bin/rzsh (rzsh) in auto mode
Setting up iso-codes (3.65-1) ...
Setting up python-apt-common (1.1.0~beta1build1) ...
Setting up python3-apt (1.1.0~beta1build1) ...
Setting up xz-utils (5.1.1alpha+20120614-2ubuntu2) ...
update-alternatives: using /usr/bin/xz to provide /usr/bin/lzma (lzma) in auto 
mode
Setting up unattended-upgrades (0.90) ...

Creating config file /etc/apt/apt.conf.d/20auto-upgrades with new
version

Creating config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
root@MacBookAir-test:/# apt-mark auto zsh
zsh set to automatically installed.
root@MacBookAir-test:/# echo "Unattended-Upgrade::Package-Blacklist {"libs";}" 
> /etc/apt/apt.conf.d/51unattended-upgrades
root@MacBookAir-test:/# echo "deb http://archive.ubuntu.com/ubuntu 
xenial-security main" >> /etc/apt/sources.list
root@MacBookAir-test:/#  echo "deb http://archive.ubuntu.com/ubuntu 
xenial-updates main" >> /etc/apt/sources.list
root@MacBookAir-test:/# apt update -qq
105 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@MacBookAir-test:/#  unattended-upgrades --dry-run --verbose --debug
Initial blacklisted packages: libs
Initial whitelisted packages: 
Starting unattended upgrades script
...
adjusting candidate version: 'libkmod2=22-1ubuntu5'
adjusting candidate version: 'libstdc++6=5.4.0-6ubuntu1~16.04.10'
adjusting candidate version: 'sudo=1.8.16-0ubuntu1.4'
marking zsh-common for remove
marking zsh for remove
Packages that are auto removed: 'zsh zsh-common'
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
/usr/bin/dpkg --status-fd 197 --force-depends --force-remov

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[beta-tester]

just tried http://cdimage.ubuntu.com/daily-live/pending/disco-desktop-amd64.iso 
from 2019-02-08 without the workaround and it pxe boots just fine.
thank you very much!!!

will the Ubuntu 18.04 LTS (Bionic Beaver) receive that fix in the next
point release as well?

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  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:
  Fix Released

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-

[Touch-packages] [Bug 1413283] Re: "Set as default" is absent from "Open with.." context menu

[Sebastien Bacher]

That's a gtk widget, reassigning

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "Set as default" is absent from "Open with.." context menu

Status in One Hundred Papercuts:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Question http://askubuntu.com/questions/90214/how-to-set-default-
  program gets 35k+ views. I suspect much of it is because there is no
  intuitive way to set a file association. See the comment under
  accepted answer:

  Right-click -> open with -> other application DOES NOT show "Set as 
default"...
  Right-click -> Properties -> Open With DOES show "Set as default"

  I was looking for "Set as default" in "Open with.." menu myself .

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

[Eric Desrochers]

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

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

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
   apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x


  [Test Case]
  Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1413283] [NEW] "Set as default" is absent from "Open with.." context menu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Question http://askubuntu.com/questions/90214/how-to-set-default-program
gets 35k+ views. I suspect much of it is because there is no intuitive
way to set a file association. See the comment under accepted answer:

Right-click -> open with -> other application DOES NOT show "Set as 
default"...
Right-click -> Properties -> Open With DOES show "Set as default"

I was looking for "Set as default" in "Open with.." menu myself .

** Affects: hundredpapercuts
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Confirmed

-- 
"Set as default" is absent from "Open with.." context menu
https://bugs.launchpad.net/bugs/1413283
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Ricardo Ribalda Delgado]

This workaround works for me:
https://gist.github.com/hxss/a3eadb0cc52e58ce7743dff71b92b297

Have only tried it twice now

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

Title:
  Bluetooth headphones only use A2DP when connected manually

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

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

[Edson José dos Santos]

** Attachment added: "Captura de tela de 2019-02-08 11-14-16.png"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+attachment/5236984/+files/Captura%20de%20tela%20de%202019-02-08%2011-14-16.png

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

[Edson José dos Santos]

Hi, Sebastien Bacher

I executed the command informed in the indicated page to reset the
tracker as below:

edson@edson-p6540br:~$ tracker reset --hard
CAUTION: This process can irreversibly delete data.
Although most of the content indexed by Tracker can safely be reindexed, it can 
not be guaranteed that it will be so for all data. Be aware that you can go 
through a data loss situation at your own risk.

Tem certeza que deseja prosseguir? [s|N]: s
Found 4 PIDs…
  Processo 2397 morto — “tracker-miner-fs”
  Processo 2408 morto — “tracker-miner-apps”
  Processo 2415 morto — “tracker-store”
  Processo 27688 morto — “tracker-extract”
Setting database locations
Checking database directories exist
Checking database version
Checking whether database files exist
Removing all database/storage files
  Removing database:'/home/edson/.cache/tracker/meta.db'
  Removing db-locale file:'/home/edson/.cache/tracker/db-locale.txt'
  Removing journal:'/home/edson/.local/share/tracker/data/tracker-store.journal'
  Removing db-version file:'/home/edson/.cache/tracker/db-version.txt'


NOTE> At startup I gave a F1 and I could see that the system still looks for 
system assemblies in HDs that I removed and there were other linux systems 
installed as test, being fedora among others.

Initially the HD went live on for less time. Then I opened the terminal
and executed the commands below

sudo apt update  
sudo apt full-upgrade -y

Both above all okay

In sudo update-grub the system found only the existing HD with Windows
10 and when checking the tracker everything came back to almost 100%
CPU.

If you have another suggestion, I'm grateful.

See attached pictures

Edson Santos


** Attachment added: "Captura de tela de 2019-02-08 11-10-37.png"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+attachment/5236983/+files/Captura%20de%20tela%20de%202019-02-08%2011-10-37.png

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1737717] Re: unattended-upgrade-shutdown crashes with apt_pkg.Error: E:Syntax error /etc/apt/apt.conf:2: Extra junk at end of file

[Balint Reczey]

The crash was first found and fixed in LP: #1737717 but the fix LP:
#1778219 introduced it in a slightly different way on start-up.

With the fix for LP: #1737717 u-u.service can gracefully stop u-u when
the APT configuration became broken _after_ starting the u-u.service but
the service still throws an unhandled exception when it starts with an
already broken APT configuration.

Since the original behaviour was crashing on u-u.service stopping i'm
marking this but as verified on 1.1ubuntu1.18.04.7~16.04.1.

root@x-uu-ref:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~#  echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades
root@dd-uu-ref:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
   Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Fri 2019-02-08 08:59:58 UTC; 3h 42min ago
 Docs: man:unattended-upgrade(8)
 Main PID: 259 (unattended-upgr)
Tasks: 2 (limit: 4915)
   Memory: 12.4M
   CGroup: /system.slice/unattended-upgrades.service
   └─259 /usr/bin/python3 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal

Feb 08 08:59:58 dd-uu-ref systemd[1]: Started Unattended Upgrades Shutdown.
root@dd-uu-ref:~# service unattended-upgrades stop
root@dd-uu-ref:~# cat 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log 
2019-02-07 16:08:14,675 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgrades only if it is running
2019-02-08 12:42:43,640 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgrades only if it is running


** Description changed:

  [Impact]
  
-  * Unattended-upgrades-shutdown service fails to start printing a crash
-  * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.
+  * Unattended-upgrades-shutdown service fails to stop printing a crash
+  * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.
  
  [Test Case]
  
-  * Buggy version:
- root@x2:~#  echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades 
- root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
- Traceback (most recent call last):
-   File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
- apt_pkg.init_config()
- SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: 
Extra junk at end of file
- root@x2:~# 
+  * Buggy version:
+ root@x-uu-1702793:~#  echo extra-junk >> 
/etc/apt/apt.conf.d/50unattended-upgrades
+ root@x-uu-1702793:~# service unattended-upgrades status
+ ● unattended-upgrades.service - Unattended Upgrades Shutdown
+Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
vendor preset: enabled)
+Active: active (exited) since Fri 2019-02-08 12:55:16 UTC; 39s ago
+  Docs: man:unattended-upgrade(8)
+ Tasks: 0
+Memory: 0B
+   CPU: 0
  
-  * Fixed version:
- # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $?
- 1
- root@bb-lp-1806076:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log 
- 2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting
- 2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error 
/etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file'
+ Feb 08 12:55:16 x-uu-1702793 systemd[1]: Started Unattended Upgrades Shutdown.
+ root@x-uu-1702793:~# service unattended-upgrades stop  
+ root@x-uu-1702793:~# service unattended-upgrades status
+ ● unattended-upgrades.service - Unattended Upgrades Shutdown
+Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
vendor preset: enabled)
+Active: failed (Result: exit-code) since Fri 2019-02-08 12:56:02 UTC; 2s 
ago
+  Docs: man:unattended-upgrade(8)
+   Process: 602 
ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown 
(code=exited, status=1/FAILURE)
+ 
+ Feb 08 12:55:16 x-uu-1702793 systemd[1]: Started Unattended Upgrades Shutdown.
+ Feb 08 12:56:02 x-uu-1702793 systemd[1]: Stopping Unattended Upgrades 
Shutdown...
+ Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: Traceback 
(most recent call last):
+ Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]:   File 
"/usr/share/unattended-upgrades/unattended-up
+ Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: 
apt_pkg.init_config()
+ Feb 08 12:56:02 x-uu-1702793 

[Touch-packages] [Bug 1699783] Re: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente de outras instâ

[Skylure Ken]

It prevents me from installing PHPMyAdmin, MySQL, and and MySQL
Workbench on Kali-Linux...-_-'

dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.50-2+deb8u3_amd64.deb (--unpack):
 unable to install new version of '/usr/lib/x86_64-linux-gnu/libpng12.so.0': No 
such file or directory

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

Title:
  package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é
  diferente de outras instâncias do pacote libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.50-2+deb8u3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 22 09:47:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  ErrorMessage: a tentar sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' 
partilhado, que é diferente de outras instâncias do pacote libpng12-0:amd64
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libpng
  Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libpng12-0/ANNOUNCE' partilhado, que é diferente 
de outras instâncias do pacote libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815189] Re: /usr/share/unattended-upgrades/unattended-upgrade-shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@399:main

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Unattended-upgrades-shutdown service fails to start printing a crash
-  * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.
+  * Unattended-upgrades-shutdown service fails to start printing a crash
+  * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.
  
  [Test Case]
  
-  * Buggy version:
+  * Buggy version:
  root@x2:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades
  root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  Traceback (most recent call last):
-   File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
- apt_pkg.init_config()
+   File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
+ apt_pkg.init_config()
  SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: 
Extra junk at end of file
  root@x2:~#
  
-  * Fixed version:
+  * Fixed version:
  # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $?
  1
  root@bb-lp-1806076:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting
  2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error 
/etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file'
  
  [Regression Potential]
  
-  * U-u-s used to exit crashing, now it exits with an error code, just logging 
the error. There is little chance for regressing here, but users may have 
harder time to figure out why u-u-s exited, they need to check the log file.
-  * There is also an enhancement request tracked to start u-u-s with a default 
config when parsing the config fails to be able to act on shutdown:
+  * U-u-s used to exit crashing, now it exits with an error code, just logging 
the error. There is little chance for regressing here, but users may have 
harder time to figure out why u-u-s exited, they need to check the log file.
+  * There is also an enhancement request tracked to start u-u-s with a default 
config when parsing the config fails to be able to act on shutdown:
  https://github.com/mvo5/unattended-upgrades/issues/161
  
  [Original Bug Text]
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/.
+ 
+ The crash was first found and fixed in LP: #1737717 but the fix LP: #1778219 
introduced it in a slightly different way.
+ With the fix for LP: #1737717 u-u.service can gracefully stop u-u when the 
APT configuration became broken _after_ starting the u-u.service but the 
service still throws an unhandled exception when it starts with an already 
broken APT configuration.

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

Title:
  /usr/share/unattended-upgrades/unattended-upgrade-
  shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-
  upgrade-shutdown@399:main

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades-shutdown service fails to start printing a crash
   * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.

  [Test Case]

   * Buggy version:
  root@x2:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades
  root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  Traceback (most recent call last):
    File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
  apt_pkg.init_config()
  SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: 
Extra junk at end of file
  root@x2:~#

   * Fixed version:
  # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $?
  1
  root@bb-lp-1806076:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting
  2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error 
/etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file'

  [Regression Potential]

   * U-u-s used to exit crashing, now it exits with an error code, just logging 
the error. There is little chance for regressing here, but users may have 
harder time to figure out why u-u-s exited, they need to check the log file.
   * There is also an enhancement request tracked to start u

[Touch-packages] [Bug 1815189] Re: /usr/share/unattended-upgrades/unattended-upgrade-shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@399:main

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Unattended-upgrades-shutdown service fails to start printing a crash
+  * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.
+ 
+ [Test Case]
+ 
+  * Buggy version:
+ root@x2:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades
+ root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown
+ Traceback (most recent call last):
+   File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
+ apt_pkg.init_config()
+ SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: 
Extra junk at end of file
+ root@x2:~#
+ 
+  * Fixed version:
+ # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $?
+ 1
+ root@bb-lp-1806076:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
+ 2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting
+ 2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error 
/etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file'
+ 
+ [Regression Potential]
+ 
+  * U-u-s used to exit crashing, now it exits with an error code, just logging 
the error. There is little chance for regressing here, but users may have 
harder time to figure out why u-u-s exited, they need to check the log file.
+  * There is also an enhancement request tracked to start u-u-s with a default 
config when parsing the config fails to be able to act on shutdown:
+ https://github.com/mvo5/unattended-upgrades/issues/161
+ 
+ [Original Bug Text]
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/.

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

Title:
  /usr/share/unattended-upgrades/unattended-upgrade-
  shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-
  upgrade-shutdown@399:main

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades-shutdown service fails to start printing a crash
   * The fix would not warrant an SRU itself but it is part of the full 
backport SRU tracked in LP: #1702793.

  [Test Case]

   * Buggy version:
  root@x2:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades
  root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  Traceback (most recent call last):
File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 
119, in 
  apt_pkg.init_config()
  SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: 
Extra junk at end of file
  root@x2:~#

   * Fixed version:
  # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $?
  1
  root@bb-lp-1806076:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
  2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting
  2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error 
/etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file'

  [Regression Potential]

   * U-u-s used to exit crashing, now it exits with an error code, just logging 
the error. There is little chance for regressing here, but users may have 
harder time to figure out why u-u-s exited, they need to check the log file.
   * There is also an enhancement request tracked to start u-u-s with a default 
config when parsing the config fails to be able to act on shutdown:
  https://github.com/mvo5/unattended-upgrades/issues/161

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/unattended-upgrades/+bug/1815189/+subscriptions

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

[Touch-packages] [Bug 1815189] Re: /usr/share/unattended-upgrades/unattended-upgrade-shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@399:main

[Balint Reczey]

** This bug is no longer a duplicate of bug 1737717
   unattended-upgrade-shutdown crashes with apt_pkg.Error: E:Syntax error 
/etc/apt/apt.conf:2: Extra junk at end of file

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

Title:
  /usr/share/unattended-upgrades/unattended-upgrade-
  shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-
  upgrade-shutdown@399:main

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/unattended-upgrades/+bug/1815189/+subscriptions

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

[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

[Sebastien Bacher]

Could you provide the debug informations?

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+subscriptions

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

[Touch-packages] [Bug 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades

[Balint Reczey]

** Tags removed: verification-don
** Tags added: verification-done

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The confusing text on shutdown is, well, can confuse users.
   * This fix itself is minor and would not warrant a backport but it is 
backported as part of fully backporting Bionic's u-u version to Xenial.

  [Test Case]

   * Check that the status text is less confusing than it was previously
  either by configuring unattended-upgrades to run at shutdown and
  waiting for the text to appear or check that the text is changed in
  unattended-upgrades-shutdown:

  $ grep -B1 please /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
  msg = _("Unattended-upgrade in progress during shutdown, "
  "please don't turn off the computer")

* The former way or the verification may not be easy since with the fix for 
LP: #1803137 the shutdown screen does not show up when u-u-shutdown starts 
running, see the bug for the details.
* Also checking unatttended-upgrades-shutdown for the changed text does not 
ensure that the translation is ready, too.

  [Regression Potential]

   * The updated text should not cause major issues, but until it is
  translated to each language it is shown in English, possibly confusing
  users in a different way.

  [Original Bug Text]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion.
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

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

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

[Touch-packages] [Bug 1815189] Re: /usr/share/unattended-upgrades/unattended-upgrade-shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@399:main

[Balint Reczey]

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

** This bug has been marked a duplicate of bug 1737717
   unattended-upgrade-shutdown crashes with apt_pkg.Error: E:Syntax error 
/etc/apt/apt.conf:2: Extra junk at end of file

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

Title:
  /usr/share/unattended-upgrades/unattended-upgrade-
  shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-
  upgrade-shutdown@399:main

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/unattended-upgrades/+bug/1815189/+subscriptions

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

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

[Sebastien Bacher]

It could be https://gitlab.gnome.org/GNOME/tracker/merge_requests/35 ,
does 'tracker reset --hard' resolves the issue?

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1815189] [NEW] /usr/share/unattended-upgrades/unattended-upgrade-shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@399:main

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic cosmic

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

Title:
  /usr/share/unattended-upgrades/unattended-upgrade-
  shutdown:apt_pkg.Error:/usr/share/unattended-upgrades/unattended-
  upgrade-shutdown@399:main

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/994a64ac5b092229a3b9f45045daa8e51371085b 
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/unattended-upgrades/+bug/1815189/+subscriptions

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

[Touch-packages] [Bug 1815188] Re: Fix crash when opening DepCache before Cache

[Colin Watson]

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

** This bug has been marked a duplicate of bug 1815187
   Fix crash when opening DepCache before Cache

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

Title:
  Fix crash when opening DepCache before Cache

Status in apt package in Ubuntu:
  New

Bug description:
  [Impact]
  apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

  [Test case]
  TODO, some apt search -o RootDir= foobar

  [Regression potential]
  There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

[Touch-packages] [Bug 1773033] Re: unattended upgrade no longer actions on shutdown

[Balint Reczey]

Then without AC power:

root@x-uu-ref:~# cat > /etc/apt/apt.conf.d/51unattended-upgrades-on-battery
 Unattended-Upgrade::OnlyOnACPower "false";
root@x-uu-ref:~# unattended-upgrade --dry-run --verbose 
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
No packages found that can be upgraded unattended and no pending auto-removals
root@x-uu-ref:~# on_ac_power ; echo $?
1
root@x-uu-ref:~# 


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

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

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades does not install upgrades when it is configured
  to install updates on shutdown and when it the system is started on
  battery, but installs updates on battery in other cases.

   * This behaviour is unintended and confuses users, moreover
  installing updates on battery risks the system to be shut down in the
  middle of an upgrade due to depleting the battery.

   * This upload changes u-u to skip updates or gracefully stop when the
  system is switching to batter-powered state by default minimizing the
  risk of breaking the system.

  [Test Case]

   * Run "unattended-upgrade --dry-run --verbose" on battery and on AC
  power

   * With default configuration u-u should stop with the following message on 
battery:
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  System is on battery power, stopping

   * On AC power it should continue:
  $ sudo ./unattended-upgrade --dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

   * Add the following configuration file and check u-u continuing even on 
battery:
  $ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery 
  Unattended-Upgrade::OnlyOnACPower "false";
  rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade 
--dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

  
  [Regression Potential] 

   * Unattended-upgrades may fail to install updates even on AC power,
  but this is unlikely to happen due to the code changed being fairly
  simple. on_ac_power may return 255 (false) Power status could not be
  determined, but this is mapped to being on AC power and installing the
  updates, only subprocess.call("on_ac_power") == 1 makes u-u skip
  updates.

  [Original Bug Text]

  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESM:${distro_codename}";
  "${distro_id}:${distro_codename}-updates";
  //  "${distro_id}:${distro_codename}-proposed"

[Touch-packages] [Bug 1773033] Re: unattended upgrade no longer actions on shutdown

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:
root@x-uu-ref:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# unattended-upgrade --dry-run --verbose 
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
System is on battery power, stopping
root@x-uu-ref:~# unattended-upgrade --dry-run --verbose 
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
No packages found that can be upgraded unattended and no pending auto-removals

(Between the two runs I plugged the laptop in again.)

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

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades does not install upgrades when it is configured
  to install updates on shutdown and when it the system is started on
  battery, but installs updates on battery in other cases.

   * This behaviour is unintended and confuses users, moreover
  installing updates on battery risks the system to be shut down in the
  middle of an upgrade due to depleting the battery.

   * This upload changes u-u to skip updates or gracefully stop when the
  system is switching to batter-powered state by default minimizing the
  risk of breaking the system.

  [Test Case]

   * Run "unattended-upgrade --dry-run --verbose" on battery and on AC
  power

   * With default configuration u-u should stop with the following message on 
battery:
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  System is on battery power, stopping

   * On AC power it should continue:
  $ sudo ./unattended-upgrade --dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

   * Add the following configuration file and check u-u continuing even on 
battery:
  $ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery 
  Unattended-Upgrade::OnlyOnACPower "false";
  rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade 
--dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

  
  [Regression Potential] 

   * Unattended-upgrades may fail to install updates even on AC power,
  but this is unlikely to happen due to the code changed being fairly
  simple. on_ac_power may return 255 (false) Power status could not be
  determined, but this is mapped to being on AC power and installing the
  updates, only subprocess.call("on_ac_power") == 1 makes u-u skip
  updates.

  [Original Bug Text]

  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Un

[Touch-packages] [Bug 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades

[Balint Reczey]

Tested with 1.1ubuntu1.18.04.7~16.04.1:

root@x-uu-ref:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# grep -B1 please 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
msg = _("Unattended-upgrade in progress during shutdown, "
"please don't turn off the computer")
--
_("To enable monitoring the PrepareForShutdown() signal "
  "instead of polling please install the python3-gi package"))
root@x-uu-ref:~# 


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

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The confusing text on shutdown is, well, can confuse users.
   * This fix itself is minor and would not warrant a backport but it is 
backported as part of fully backporting Bionic's u-u version to Xenial.

  [Test Case]

   * Check that the status text is less confusing than it was previously
  either by configuring unattended-upgrades to run at shutdown and
  waiting for the text to appear or check that the text is changed in
  unattended-upgrades-shutdown:

  $ grep -B1 please /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
  msg = _("Unattended-upgrade in progress during shutdown, "
  "please don't turn off the computer")

* The former way or the verification may not be easy since with the fix for 
LP: #1803137 the shutdown screen does not show up when u-u-shutdown starts 
running, see the bug for the details.
* Also checking unatttended-upgrades-shutdown for the changed text does not 
ensure that the translation is ready, too.

  [Regression Potential]

   * The updated text should not cause major issues, but until it is
  translated to each language it is shown in English, possibly confusing
  users in a different way.

  [Original Bug Text]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion.
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

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

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

[Touch-packages] [Bug 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version

[Balint Reczey]

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

** Tags removed: verification-don
** Tags added: verification-done

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

Title:
  Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1
  version

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades fails to install updates when adjusting
  candidates is needed.

  [Test Case]

  Note that only 1.2ubuntu1 is affected. Earlier releases either did not
  crash or did not adjust candidates due to LP: #1775292. To reproduce
  the crash Cosmic's u-u 1.2ubuntu1 needs to be installed.

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " or a crash with buggy 
u-u versions
  ...
  adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
  adjusting candidate version: zfs-test=0.7.5-1ubuntu15
  adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
  adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1928, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1554, in main
  allowed_origins=allowed_origins)
File "/usr/bin/unattended-upgrade", line 122, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 152, in open
  self.adjust_candidates()
File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
  for pkgname, candidate in self._get_candidates_to_adjust():
  ValueError: too many values to unpack (expected 2) * Install fixed u-u version

   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: " and no crash

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

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

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

[Touch-packages] [Bug 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1

[Balint Reczey]

Tested 1.1ubuntu1.18.04.7~16.04.1. Candidates are adjusted:

root@x-uu-ref:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# grep invoke /var/lib/dpkg/info/unattended-upgrades.prerm
root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
Using 
(^linux-image.*4.19.0-12-generic|^linux-headers.*4.19.0-12-generic|^linux-image-extra.*4.19.0-12-generic|^linux-modules.*4.19.0-12-generic|^linux-modules-extra.*4.19.0-12-generic|^linux-signed-image.*4.19.0-12-generic|^kfreebsd-image.*4.19.0-12-generic|^kfreebsd-headers.*4.19.0-12-generic|^gnumach-image.*4.19.0-12-generic|4.19.0-12-generic.*-modules|4.19.0-12-generic.*-kernel|^linux-backports-modules-.*.*4.19.0-12-generic|^linux-modules-.*.*4.19.0-12-generic|^linux-tools.*4.19.0-12-generic|^linux-cloud-tools.*4.19.0-12-generic)
 regexp to find running kernel packages
Checking: cloud-init ([])
adjusting candidate version: cloud-init=0.7.7~bzr1212-0ubuntu1
Checking: kmod ([])
adjusting candidate version: kmod=22-1ubuntu5
Checking: libc-bin ([])
adjusting candidate version: libc-bin=2.23-0ubuntu10
Checking: libc6 ([])
adjusting candidate version: libc6=2.23-0ubuntu10
Checking: libkmod2 ([])
adjusting candidate version: libkmod2=22-1ubuntu5
Checking: locales ([])
adjusting candidate version: locales=2.23-0ubuntu10
Checking: multiarch-support ([])
adjusting candidate version: multiarch-support=2.23-0ubuntu10
Checking: python-apt-common ([])
adjusting candidate version: python-apt-common=1.1.0~beta1build1
Checking: snapd ([])
adjusting candidate version: snapd=2.0.2
Checking: ubuntu-core-launcher ([])
adjusting candidate version: ubuntu-core-launcher=1.0.27.1
pkgs that look like they should be upgraded: 
Fetched 0 B in 0s (0 B/s)   
  
fetch.run() result: 0
blacklist: []
whitelist: []
No packages found that can be upgraded unattended and no pending auto-removals
root@x-uu-ref:~# 


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

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

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

Title:
  Unattended-upgrades stopped adjusting candidates in 1.1

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades may fail to install an update when the highest
  version of a package to be updated exists in an origin u-u is not
  allowed to pull packages from.

  [Test Case]

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " with buggy u-u version
   * Install fixed u-u version
   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: "

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

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

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

[Touch-packages] [Bug 1815188] [NEW] Fix crash when opening DepCache before Cache

[Julian Andres Klode]

Public bug reported:

[Impact]
apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

[Test case]
TODO, some apt search -o RootDir= foobar

[Regression potential]
There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

Title:
  Fix crash when opening DepCache before Cache

Status in apt package in Ubuntu:
  New

Bug description:
  [Impact]
  apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

  [Test case]
  TODO, some apt search -o RootDir= foobar

  [Regression potential]
  There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

[Touch-packages] [Bug 1815187] [NEW] Fix crash when opening DepCache before Cache

[Julian Andres Klode]

Public bug reported:

[Impact]
apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

[Test case]
TODO, some apt search -o RootDir= foobar

[Regression potential]
There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

Title:
  Fix crash when opening DepCache before Cache

Status in apt package in Ubuntu:
  New

Bug description:
  [Impact]
  apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

  [Test case]
  TODO, some apt search -o RootDir= foobar

  [Regression potential]
  There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

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

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

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Bug Watch Updater]

Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=109583.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-02-08T08:04:22+00:00 Alkis Georgopoulos wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/0


On 2019-02-08T08:59:14+00:00 Denys-kostin wrote:

Hello Alkis, thank you for the report.
Do you know, what kernel version was used on those machines? It might be 
helpful also.

I have HD 520 graphic card, quite close to mentioned by you, so can try
to reproduce

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/2


On 2019-02-08T09:04:12+00:00 Alkis Georgopoulos wrote:

Thank you Denis,

I tried with the following Ubuntu-built kernels, all having the issue:
4.15.0-45, 4.15.0-44, 4.15.0-20.

It happens on both 32bit and 64bit installations.

The failed units logs are:
systemctl status gpu-manager: https://termbin.com/kkix
systemctl status lightdm: https://termbin.com/ybev
lightdm.log: https://termbin.com/ssrb

The weird part is that I don't see xorg segfaults or /var/crash/*
reports or anything, the only error I got was that xinit line that I
mentioned, "i965: Failed to submit batchbuffer: Invalid argument"

I have the `lspci` results from 4 schools so far, they're all 8086:1912
(HD Graphics 530), although from different vendors, ASUS, Dell etc.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/3


On 2019-02-08T09:10:38+00:00 Alkis Georgopoulos wrote:

The Ubuntu folks uploaded 18.3.3 in their ppa:ubuntu-x-swat/updates PPA
for me to test with, and it has the exact same issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/4


On 2019-02-08T09:21:41+00:00 Chris Wilson wrote:

Can you please:

$ echo 0xf > /sys/modules/drm/parameters/debug
$ xinit
$ echo 0 > /sys/modules/drm/parameters/debug
$ dmesg > dmesg.txt # and upload

Hopefully we remembered to tag the EINVAL.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/5


On 2019-02-08T09:32:05+00:00 Alkis Georgopoulos wrote:

I used "/sys/module" instead of "/sys/modules":

$ echo 0xf /sys/module/drm/parameters/debug
$ xinit
i965: Failed to submit batchbuffer: Invalid argument
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

$ echo 0 /sys/module/drm/parameters/debug
$ dmesg | nc termbin.com 

https://termbin.com/fb2m

I don't see any additional messages though...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/6


On 2019-02-08T09:33:24+00:00 Alkis Georgopoulos wrote:

Sorry, I forgot the >

Here's the correct log:
https://termbin.com/6n12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/7


On 2019-02-08T09:48:56+00:00 Chris Wilson wrote:

(In reply to Chris Wilson from comment #4)
> Hopefully we remembered to tag the EINVAL.

[ 1494.995482] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, 
DRM_IOCTL_MODE_CREATE_DUMB
[ 1494.995493] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, 
DRM_IOCTL_MODE_CREATE_DUMB
[ 1494.995584] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, 
I915_GEM_EXECBUFFER2_WR
[ 1494.995595] [drm:drm_ioctl [drm]] ret = -22

That'll be no then.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/8


** Changed in: mesa
   Status: Unknown => Confirmed

** Changed in: mesa
   Importance:

[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

[vinay teki]

I'm facing the exact same issue.
Did you find a solution @sundhar shrestha.
please let me know.

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing all files in
  /var/lib/apt/lists and update again" but it doesn't work. Don't know
  how to resolve it.

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

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

[Christian Ehrhardt ]

I opened a MP [1] for review by different parties:
- you (@xantares) as the original author if you are fine with my polishing
- security to get their ack on it
- server-team to spot silly errors that I might have missed or done

[1]:
https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/362906

** Tags added: server-next

** Changed in: libseccomp (Ubuntu Bionic)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Triaged
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Some newer workloads fail due to libseccomp as in Bionic lacking
  statx support

   * This backports the syscall definitions for statx to Bionic to allow
  to manage those

  [Test Case]

  # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
  $ sudo apt install docker.io
  $ sudo usermod -a -G docker ubuntu
  $ cat > test-statx/Dockerfile << EOF
  FROM ubuntu:18.04
  RUN apt-get update && apt-get install -y wget gcc
  WORKDIR /tmp
  RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
  RUN gcc test-statx.c -o test-statx
  RUN touch test-file
  RUN chmod +x ./test-statx
  RUN ./test-statx test-file
  EOF
  $ docker build test-statx

  With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic
  that yields

  [...]
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in 6e60a82409e6
  test-file: Operation not permitted
  statx(test-file) = -1
  The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1

  With the fix applied it would work and look like:
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in a83bc043e7bd
  statx(test-file) = 0
  results=fff
Size: 0   Blocks: 0  IO Block: 4096regular file
  Device: 00:32   Inode: 261994  Links: 1
  Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
  Access: 2019-02-08 07:57:42.0+
  Modify: 2019-02-08 07:57:42.0+
  Change: 2019-02-08 07:57:43.076507007+
   Birth: 2019-02-08 07:57:43.076507007+
  Attributes:  (     
 -... .---.-..)
  Removing intermediate container a83bc043e7bd
   ---> d428d14cbc57
  Successfully built d428d14cbc57

  
  [Regression Potential] 

   * This "only" defines a new syscall number for all the architectures.
  It does not make any other changes, thereby it should be rather safe.
  If anything software could now manage statx through libseccomp and
  behavior that was formerly failing (like the reported docker case)
  would not succeed and due to that be a change in behavior - but I
  think it is a wanted change.

  [Other Info]
   
   * n/a

  ---

  
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/362906

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Triaged
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Some newer workloads fail due to libseccomp as in Bionic lacking
  statx support

   * This backports the syscall definitions for statx to Bionic to allow
  to manage those

  [Test Case]

  # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
  $ sudo apt install docker.io
  $ sudo usermod -a -G docker ubuntu
  $ cat > test-statx/Dockerfile << EOF
  FROM ubuntu:18.04
  RUN apt-get update && apt-get install -y wget gcc
  WORKDIR /tmp
  RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
  RUN gcc test-statx.c -o test-statx
  RUN touch test-file
  RUN chmod +x ./test-statx
  RUN ./test-statx test-file
  EOF
  $ docker build test-statx

  With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic
  that yields

  [...]
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in 6e60a82409e6
  test-file: Operation not permitted
  statx(test-file) = -1
  The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1

  With the fix applied it would work and look like:
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in a83bc043e7bd
  statx(test-file) = 0
  results=fff
Size: 0   Blocks: 0  IO Block: 4096regular file
  Device: 00:32   Inode: 261994  Links: 1
  Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
  Access: 2019-02-08 07:57:42.0+
  Modify: 2019-02-08 07:57:42.0+
  Change: 2019-02-08 07:57:43.076507007+
   Birth: 2019-02-08 07:57:43.076507007+
  Attributes:  (     
 -... .---.-..)
  Removing intermediate container a83bc043e7bd
   ---> d428d14cbc57
  Successfully built d428d14cbc57

  
  [Regression Potential] 

   * This "only" defines a new syscall number for all the architectures.
  It does not make any other changes, thereby it should be rather safe.
  If anything software could now manage statx through libseccomp and
  behavior that was formerly failing (like the reported docker case)
  would not succeed and due to that be a change in behavior - but I
  think it is a wanted change.

  [Other Info]
   
   * n/a

  ---

  
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

[Christian Ehrhardt ]

Ok, tests worked fine for me - I added all I had as SRU template in the
bug description.

** Description changed:

+ [Impact]
+ 
+  * Some newer workloads fail due to libseccomp as in Bionic lacking
+ statx support
+ 
+  * This backports the syscall definitions for statx to Bionic to allow
+ to manage those
+ 
+ [Test Case]
+ 
+ # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
+ $ sudo apt install docker.io
+ $ sudo usermod -a -G docker ubuntu
+ $ cat > test-statx/Dockerfile << EOF
+ FROM ubuntu:18.04
+ RUN apt-get update && apt-get install -y wget gcc
+ WORKDIR /tmp
+ RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
+ RUN gcc test-statx.c -o test-statx
+ RUN touch test-file
+ RUN chmod +x ./test-statx
+ RUN ./test-statx test-file
+ EOF
+ $ docker build test-statx
+ 
+ With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic that
+ yields
+ 
+ [...]
+ Step 8/8 : RUN ./test-statx test-file
+  ---> Running in 6e60a82409e6
+ test-file: Operation not permitted
+ statx(test-file) = -1
+ The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1
+ 
+ With the fix applied it would work and look like:
+ Step 8/8 : RUN ./test-statx test-file
+  ---> Running in a83bc043e7bd
+ statx(test-file) = 0
+ results=fff
+   Size: 0   Blocks: 0  IO Block: 4096regular file
+ Device: 00:32   Inode: 261994  Links: 1
+ Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
+ Access: 2019-02-08 07:57:42.0+
+ Modify: 2019-02-08 07:57:42.0+
+ Change: 2019-02-08 07:57:43.076507007+
+  Birth: 2019-02-08 07:57:43.076507007+
+ Attributes:  (     
 -... .---.-..)
+ Removing intermediate container a83bc043e7bd
+  ---> d428d14cbc57
+ Successfully built d428d14cbc57
+ 
+ 
+ [Regression Potential] 
+ 
+  * This "only" defines a new syscall number for all the architectures.
+ It does not make any other changes, thereby it should be rather safe. If
+ anything software could now manage statx through libseccomp and behavior
+ that was formerly failing (like the reported docker case) would not
+ succeed and due to that be a change in behavior - but I think it is a
+ wanted change.
+ 
+ [Other Info]
+  
+  * n/a
+ 
+ ---
+ 
+ 
  Hello maintainer,
  
  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859
  
  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417
  
  regards,
  xan.

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Triaged
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Some newer workloads fail due to libseccomp as in Bionic lacking
  statx support

   * This backports the syscall definitions for statx to Bionic to allow
  to manage those

  [Test Case]

  # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
  $ sudo apt install docker.io
  $ sudo usermod -a -G docker ubuntu
  $ cat > test-statx/Dockerfile << EOF
  FROM ubuntu:18.04
  RUN apt-get update && apt-get install -y wget gcc
  WORKDIR /tmp
  RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
  RUN gcc test-statx.c -o test-statx
  RUN touch test-file
  RUN chmod +x ./test-statx
  RUN ./test-statx test-file
  EOF
  $ docker build test-statx

  With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic
  that yields

  [...]
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in 6e60a82409e6
  test-file: Operation not permitted
  statx(test-file) = -1
  The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1

  With the fix applied it would work and look like:
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in a83bc043e7bd
  statx(test-file) = 0
  results=fff
Size: 0   Blocks: 0  IO Block: 4096regular file
  Device: 00:32   Inode: 261994  Links: 1
  Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
  Access: 2019-02-08 07:57:42.0+
  Modify: 2019-02-08 07:57:42.0+
  Change: 2019-02-08 07:57:43.076507007+
   Birth: 2019-02-08 07:57:43.076507007+
  Attributes:  (     
 -... .--

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

[Christian Ehrhardt ]

Hi I polished your patch a bit and I'm currently testing it in PPA [1].
If you can give it a try as well.

I have created an SRU Teamplate and more detailed test steps and will
add them once they hopefully succeed on the prepare PPA. Otherwise I'll
ping here for you to revisit the change.

[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3640

** Also affects: libseccomp (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: docker.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: libseccomp (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: docker.io (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: docker.io (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: docker.io (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Triaged
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

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

[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Timo Aaltonen]

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

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

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Cosmic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in mesa source package in Cosmic:
  New

Bug description:
  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

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 1815172] [NEW] Black screen on skylake after 18.0 => 18.2 update

[Alkis Georgopoulos]

Public bug reported:

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

** Affects: mesa
 Importance: Unknown
 Status: Unknown

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

** Affects: mesa (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: mesa (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Bug watch added: freedesktop.org Bugzilla #109583
   https://bugs.freedesktop.org/show_bug.cgi?id=109583

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=109583
   Importance: Unknown
   Status: Unknown

-- 
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:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in mesa source package in Cosmic:
  New

Bug description:
  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

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