[Touch-packages] [Bug 1879019] Re: bad mime type for bmp

[pqwoerituytrueiwoq]

Steps to reproduce:

~$ wget 
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242/+attachment/5107204/+files/180408141636.BMP
~$ file --mime-type 180408141636.BMP

Expected Output
180408141636.BMP:   image/x-ms-bmp

Unexpected Output
180408141636.BMP:   application/octet-stream

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

Title:
  bad mime type for bmp

Status in file package in Ubuntu:
  New

Bug description:
  Sample BMP file attached to this related bug:
  https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242

  Note the attached screenshot here, this is a regression

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmagic1 1:5.38-4
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 15 23:28:26 2020
  InstallationDate: Installed on 2018-04-29 (747 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1879019] [NEW] bad mime type for bmp

[pqwoerituytrueiwoq]

Public bug reported:

Sample BMP file attached to this related bug:
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242

Note the attached screenshot here, this is a regression

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libmagic1 1:5.38-4
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri May 15 23:28:26 2020
InstallationDate: Installed on 2018-04-29 (747 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: file
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot_2020-05-15_23-27-08.png"
   
https://bugs.launchpad.net/bugs/1879019/+attachment/5372432/+files/Screenshot_2020-05-15_23-27-08.png

** Description changed:

  Sample BMP file attached to this related bug:
  https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242
+ 
+ Note the attached screenshot here, this is a regression
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmagic1 1:5.38-4
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 15 23:28:26 2020
  InstallationDate: Installed on 2018-04-29 (747 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  bad mime type for bmp

Status in file package in Ubuntu:
  New

Bug description:
  Sample BMP file attached to this related bug:
  https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242

  Note the attached screenshot here, this is a regression

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmagic1 1:5.38-4
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 15 23:28:26 2020
  InstallationDate: Installed on 2018-04-29 (747 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Hooman]

I have the same problem. I see packets being received by Ubuntu through
the WiFi iface, but they don't seem to be delivered.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   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.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1879015] Re: Autologin doesn't work (Lubuntu 18.04)

[Gunnar Hjalmarsson]

Please show what exactly the config file looks like.

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

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

Title:
  Autologin doesn't work (Lubuntu 18.04)

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I tried everything.

  3) I expected a working autologin once I set autologin-user=myusername in 
/etc/lightdm/lightdm.conf. Also I tried to change default session option. After 
I set "Do not ask password" in Users and Groups GUI autologin didn't work 
either. I needed to press "Login" button anyway. I don't know where the problem 
is. The only way to make autologin work I know is to set "Autologin" option 
while system installation. I don't want to reinstall to change just one option.
  Currently I use slim desktop manager. It's simpler and works. I have all 
possible options in /etc/slim.conf, I just need to uncomment something and 
edit. No need of reading docs and forums to just know what it can do. I hope 
someday lightdm will be changed in the same KISS way as slim.

  4) For some reason autologin doesn't work. Looks like lightdm just
  ignores its config files. It either shouldn't ignore these files or
  should provide a tool for configuring. The GUI tools I found doesn't
  provide an autologin option.

  (lightdm-autologin-greeter package doesn't help (I've edited
  /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly),
  lightdm package doesn't have /etc/lightdm/lightdm.conf file)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May 16 04:05:25 2020
  InstallationDate: Installed on 2020-05-09 (6 days ago)
  InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 
(20200203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1879015] Re: Autologin doesn't work (Lubuntu 18.04)

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

For Lubuntu specific support links, please go to
https://lubuntu.me/links/

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

Title:
  Autologin doesn't work (Lubuntu 18.04)

Status in lightdm package in Ubuntu:
  New

Bug description:
  I tried everything.

  3) I expected a working autologin once I set autologin-user=myusername in 
/etc/lightdm/lightdm.conf. Also I tried to change default session option. After 
I set "Do not ask password" in Users and Groups GUI autologin didn't work 
either. I needed to press "Login" button anyway. I don't know where the problem 
is. The only way to make autologin work I know is to set "Autologin" option 
while system installation. I don't want to reinstall to change just one option.
  Currently I use slim desktop manager. It's simpler and works. I have all 
possible options in /etc/slim.conf, I just need to uncomment something and 
edit. No need of reading docs and forums to just know what it can do. I hope 
someday lightdm will be changed in the same KISS way as slim.

  4) For some reason autologin doesn't work. Looks like lightdm just
  ignores its config files. It either shouldn't ignore these files or
  should provide a tool for configuring. The GUI tools I found doesn't
  provide an autologin option.

  (lightdm-autologin-greeter package doesn't help (I've edited
  /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly),
  lightdm package doesn't have /etc/lightdm/lightdm.conf file)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May 16 04:05:25 2020
  InstallationDate: Installed on 2020-05-09 (6 days ago)
  InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 
(20200203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1879015] [NEW] Autologin doesn't work (Lubuntu 18.04)

[Dima]

Public bug reported:

I tried everything.

3) I expected a working autologin once I set autologin-user=myusername in 
/etc/lightdm/lightdm.conf. Also I tried to change default session option. After 
I set "Do not ask password" in Users and Groups GUI autologin didn't work 
either. I needed to press "Login" button anyway. I don't know where the problem 
is. The only way to make autologin work I know is to set "Autologin" option 
while system installation. I don't want to reinstall to change just one option.
Currently I use slim desktop manager. It's simpler and works. I have all 
possible options in /etc/slim.conf, I just need to uncomment something and 
edit. No need of reading docs and forums to just know what it can do. I hope 
someday lightdm will be changed in the same KISS way as slim.

4) For some reason autologin doesn't work. Looks like lightdm just
ignores its config files. It either shouldn't ignore these files or
should provide a tool for configuring. The GUI tools I found doesn't
provide an autologin option.

(lightdm-autologin-greeter package doesn't help (I've edited
/etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly),
lightdm package doesn't have /etc/lightdm/lightdm.conf file)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic i686
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: i386
CurrentDesktop: LXDE
Date: Sat May 16 04:05:25 2020
InstallationDate: Installed on 2020-05-09 (6 days ago)
InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 (20200203)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic i386

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

Title:
  Autologin doesn't work (Lubuntu 18.04)

Status in lightdm package in Ubuntu:
  New

Bug description:
  I tried everything.

  3) I expected a working autologin once I set autologin-user=myusername in 
/etc/lightdm/lightdm.conf. Also I tried to change default session option. After 
I set "Do not ask password" in Users and Groups GUI autologin didn't work 
either. I needed to press "Login" button anyway. I don't know where the problem 
is. The only way to make autologin work I know is to set "Autologin" option 
while system installation. I don't want to reinstall to change just one option.
  Currently I use slim desktop manager. It's simpler and works. I have all 
possible options in /etc/slim.conf, I just need to uncomment something and 
edit. No need of reading docs and forums to just know what it can do. I hope 
someday lightdm will be changed in the same KISS way as slim.

  4) For some reason autologin doesn't work. Looks like lightdm just
  ignores its config files. It either shouldn't ignore these files or
  should provide a tool for configuring. The GUI tools I found doesn't
  provide an autologin option.

  (lightdm-autologin-greeter package doesn't help (I've edited
  /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly),
  lightdm package doesn't have /etc/lightdm/lightdm.conf file)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May 16 04:05:25 2020
  InstallationDate: Installed on 2020-05-09 (6 days ago)
  InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 
(20200203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1807514] Re: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Rolf Leggewie]

systemd-shim is a xenial package.  Your distro information is bionic.
Am I right to assume that this happened while you were trying to upgrade
a xenial system to bionic?  I have to admit I just ran into this myself.

** Changed in: systemd-shim (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd-shim package in Ubuntu:
  Incomplete

Bug description:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec  8 17:13:53 2018
  DistUpgraded: 2018-12-08 17:07:42,953 DEBUG /openCache(), new cache size 61306
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1682:3030]
  InstallationDate: Installed on 2014-02-15 (1757 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MachineType: Dell Inc. Dell DXP051
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=e3337e9d-4116-4f99-b96f-8019182e5c07 ro
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago)
  dmi.bios.date: 01/08/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0YC523
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0YC523:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell DXP051
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~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: Sun Nov  4 10:33:25 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Touch-packages] [Bug 1879007] Re: Xorg freeze

[Paramvir Singh]

Adding prevboot.txt

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879007/+attachment/5372371/+files/prevboot.txt

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When I first did a clean install of Ubuntu 20.04. The system got frequently 
frozen at random times 4-5 times a day and mostly every time when it was on 
charging and I tried to boot. I was using the nouveau display driver instead of 
the Nvidia driver. I did a clean install again and the same thing happened. I 
upgraded to Nvidia drivers with Intel GPU PRIME profile (earlier I hadn't 
performed key management so I guess they were not being used properly, but this 
time I did). The system didn't freeze for 2 days. This time too it was plugged 
into power and I was watching a video when it just froze. Mouse and keyboard 
became irresponsive(like before). I couldn't perform any magic sysreq so  I had 
to force reboot by pressing the power key. It has been happening every 2-3 days 
since that. My kdump crash logs are empty. Everytime the system froze the 
system has been plugged into power(or I couldn't recall if the system froze 
otherwise). It gets very irritating. Please help.
  Release : Ubuntu 20.04 LTS
  Xorg Package version : 1:7.7+19ubuntu14

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 03:40:43 2020
  DistUpgraded: 2020-04-26 15:14:05,561 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0923]
 Subsystem: Dell GP107M [GeForce GTX 1050 3 GB Max-Q] [1028:0923]
  InstallationDate: Installed on 2020-04-26 (19 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 002: ID 0c45:671b Microdia Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7591
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c933ad76-6d7d-4174-97aa-0c543f666e94 ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-26 (19 days ago)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0K1VDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7591
  dmi.product.sku: 0923
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1879010] [NEW] Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink

[Chris S.]

Public bug reported:

This seems identical to this bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was
suggested to open a new bug as the other one was closed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 16:13:24 2020
InstallationDate: Installed on 2020-05-06 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9300
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.7
dmi.board.name: 077Y9N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 54:8D:5A:D8:BA:43  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1126282 acl:178 sco:0 events:156624 errors:0
TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth speaker defaults to lower quality (HSP/HFP) instead of
  higher quality (A2DP) sink

Status in bluez package in Ubuntu:
  New

Bug description:
  This seems identical to this bug:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was
  suggested to open a new bug as the other one was closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 16:13:24 2020
  InstallationDate: Installed on 2020-05-06 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:8D:5A:D8:BA:43  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1126282 acl:178 sco:0 events:156624 errors:0
TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0

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

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

[Touch-packages] [Bug 269441] Re: Trash always full

[Endriux]

Linux Mint 19.3 Cinnamon - This issue has plagued me since I decided to share 
an entire volume over my home network with samba.
One day, I noticed the sharing emblem on the volume's .Trash-1000 icon.
Thus I right-clicked on it -> Properties -> Share tab, I switched off sharing 
of .Trash-1000 folder and BOOM! The issue disappeared.
Strangely, the sharing emblem was just on .Trash-1000 icon.
Just for the record, the "indicted" volume is formatted to ntfs.

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

Title:
  Trash always full

Status in Ubuntu MATE:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+subscriptions

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

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Toni]

Year 2020 and we still looking for a solution. Bug confirmed with Canyon
and JBL headphones 2 days ago by me.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Touch-packages] [Bug 1879007] [NEW] Xorg freeze

[Paramvir Singh]

Public bug reported:

When I first did a clean install of Ubuntu 20.04. The system got frequently 
frozen at random times 4-5 times a day and mostly every time when it was on 
charging and I tried to boot. I was using the nouveau display driver instead of 
the Nvidia driver. I did a clean install again and the same thing happened. I 
upgraded to Nvidia drivers with Intel GPU PRIME profile (earlier I hadn't 
performed key management so I guess they were not being used properly, but this 
time I did). The system didn't freeze for 2 days. This time too it was plugged 
into power and I was watching a video when it just froze. Mouse and keyboard 
became irresponsive(like before). I couldn't perform any magic sysreq so  I had 
to force reboot by pressing the power key. It has been happening every 2-3 days 
since that. My kdump crash logs are empty. Everytime the system froze the 
system has been plugged into power(or I couldn't recall if the system froze 
otherwise). It gets very irritating. Please help.
Release : Ubuntu 20.04 LTS
Xorg Package version : 1:7.7+19ubuntu14

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 03:40:43 2020
DistUpgraded: 2020-04-26 15:14:05,561 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0923]
   Subsystem: Dell GP107M [GeForce GTX 1050 3 GB Max-Q] [1028:0923]
InstallationDate: Installed on 2020-04-26 (19 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
 Bus 001 Device 002: ID 0c45:671b Microdia Integrated_Webcam_HD
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7591
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c933ad76-6d7d-4174-97aa-0c543f666e94 ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (19 days ago)
dmi.bios.date: 07/22/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0K1VDX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7591
dmi.product.sku: 0923
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze 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/1879007

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When I first did a clean install of Ubuntu 20.04. The system got frequently 
frozen at random times 4-5 times a day and mostly every time when it was on 
charging and I tried to boot. I was using the nouveau display driver instead of 
the Nvidia driver. I did a clean install again and the same thing happened. I 
upgraded to Nvidia drivers with Intel GPU PRIME profile (earlier I hadn't 
performed key management so I guess they were not being used properly, but this 
time I did). The system didn't freeze for 2 days. This time too it was plugged 
into power and I was watching a video when it just froze. Mouse and keyboard 
became irresponsive(like before). I couldn't perform any magic sysreq so  I had 
to force reboot by pressing the 

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Chris Newcomer]

FYI, version 0.11-4ubuntu2.5 was recently released. If you are still
experiencing this issue, the following steps will correct it:

1. Remove the postinst file from the affected package (version 0.11-4ubuntu2.1):
sudo rm /var/lib/dpkg/info/libjson-c2\:amd64.postinst

2. Re-run the package configure step to correct its half-installed status:
sudo dpkg --configure -a

3. Update the package list from the repository:
sudo apt update

4. Upgrade the affected package to the latest version:
sudo apt install libjson-c2

5. Reboot to activate the new package:
sudo reboot

Any user running a version of the libjson-c2 package not equal to
0.11-4ubuntu2.1 will not have to go through these steps and updating the
package to the new version will be done the normal way; either through
unattended-updates or manual apt upgrade.

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

Re: [Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1

[Jacson Syncler Silva de Assis]

It's ok. I'm sorry, I'm wrong. I think it would be a security bug. Thanks, 
again sorry   Em sexta-feira, 15 de maio de 2020 13:01:02 BRT, Marc Deslauriers 
 escreveu:  
 
 Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1877895

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  New

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
  dpkg 1.19.7ubuntu3
  apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  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.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE15125CBW
  dmi.product.sku: 54508549
  dmi.product.version: C800EQPLK
  dmi.sys.vendor: Sony Corporation

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

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  New

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  dmi.board.asset.tag: N/A
  

[Touch-packages] [Bug 1878782] Re: Bluetooth is on but scanned devices are not showing.

[Sebastien Bacher]

** Package changed: alsa-driver (Ubuntu) => bluez (Ubuntu)

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

Title:
  Bluetooth is on but scanned devices are not showing.

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth in spite of being switched on, shows the same image as when
  it is off in the paired devices menu. I cannot access my paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 13:48:16 2020
  InstallationDate: Installed on 2020-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1TCN27WW(V2.08)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
  dmi.product.family: ideapad 110-15ISK
  dmi.product.name: 80UD
  dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
  dmi.product.version: Lenovo ideapad 110-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1878241] Re: On every boot, a message appears that my wireless printer has been added

[Sebastien Bacher]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1725955, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1725955
   "Printer added" notification

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

Title:
  On every boot, a message appears that my wireless printer has been
  added

Status in cups package in Ubuntu:
  New

Bug description:
  I have a Brother HL 3170CDW printer on my wifi network.  Every time I
  boot Ubuntu, a notification appears at the top of the login screen
  saying that "The printer Brother_HL_3170CDW_series has been added".  I
  would expect this to happen only one time.

  This is a nuisance/cosmetic issue only -- the printer is not actually
  added multiple times.  It only appears once in the Printers section of
  Settings.

  To be clear, I have not installed any drivers or printer-related
  software other than what is supplied in the default Focal 20.04
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 09:17:34 2020
  InstallationDate: Installed on 2020-05-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for Brother_HL_3170CDW_series: 
implicitclass://Brother_HL_3170CDW_series/
  MachineType: Razer Blade
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_HL_3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Brother_HL_3170CDW_series.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2019
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.05
  dmi.board.name: Razer CH20
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.05:bd05/16/2019:svnRazer:pnBlade:pvr2.04:rvnRazer:rnRazerCH20:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582002 Razer Blade
  dmi.product.name: Blade
  dmi.product.sku: RZ09-02888E92
  dmi.product.version: 2.04
  dmi.sys.vendor: Razer

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

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

[Touch-packages] [Bug 1878707] Re: Openconnect provided DNS servers are not read by NetworkManager

[Sebastien Bacher]

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

  apport-collect 1878707

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10

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

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

[Touch-packages] [Bug 1878215] Re: ibus crash

[Sebastien Bacher]

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

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

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

Thanks!

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  ibus crash

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue May 12 16:59:54 2020
  InstallationDate: Installed on 2017-12-13 (880 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-04-21 (21 days ago)

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

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

[Touch-packages] [Bug 1878814] Re: apparmor stays active even when the service is disabled

[Jamie Strandboge]

I'm not familiar with mysql-workbench-community, but looking at the logs
I see:

May 14 17:44:33 owen-AOD255 kernel: [  181.312508] audit: type=1400
audit(1589474673.710:1024): apparmor="DENIED" operation="connect"
profile="snap.mysql-workbench-community.mysql-workbench-community"
name="/run/uuidd/request" pid=3579 comm="mysql-workbench"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0

This issue was fixed in a recent commit to snapd, but it hasn't reached
the stable channel yet (it should be in snapd 2.45). You can either:

* 'sudo snap install --devmode mysql-workbench-community' to work around the 
issue and put apparmor into complain mode
* 'sudo snap refresh snapd --edge' to pull in the edge build of snapd which has 
the fix

If choosing the former, when 'snap version' reports 2.45, you can
install the snap in strict mode (omit --devmode). If the latter, when
'snap info snapd' reports that 2.45 is in the stable channel, run 'sudo
snap refresh snapd --stable' to start tracking stable again.

This is not a bug in apparmor, but instead snapd. Triaging the bug as
such.

** Package changed: apparmor (Ubuntu) => snapd (Ubuntu)

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

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

** Changed in: snapd (Ubuntu)
Milestone: None => focal-updates

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

Title:
  apparmor stays active even when the service is disabled

Status in snapd package in Ubuntu:
  In Progress

Bug description:
  Trying to access a fresh install of MySQL, what a complete pain that
  is!! I installed mysql-workbench-community from the app store.
  Attempts to access the database with user root were rebuffed by an
  AppArmor error about permissions.

  Running aa-status I could see the app in the enforce category, so I
  made many attempts to move it to complain, but this failed and I'll
  file a bug report about that as well.

  I decided to disable both the apparmor and ufw service.

  However, the AppArmor permissions error dialog continue to appear and
  it's not possible to access the database.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 09:40:01 2020
  InstallationDate: Installed on 2020-03-10 (65 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1870995] Re: i8042: Warning: Keylock active

[Sebastien Bacher]

Thank you for your bug report, the warning is from the kernel,
reassigning

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  i8042: Warning: Keylock active

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I see "i8042: Warning: Keylock active" in my dmesg.  Since this is a
  warning, I get, ergo, warned.  Well, about what do I get warned?  I
  feel warned, but I don't know what's wrong and what do I have to avoid
  doing so that I don't get into trouble.  Is there an issue there that
  needs to be solved?

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

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

[Touch-packages] [Bug 1847651] Re: NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved

[Sebastien Bacher]

Closing if that's fixed in the current version

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NetworkManager isn't pushing DNS server for openvpn connection to
  systemd-resolved

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I imported an openvpn configuration with `nmcli c import type openvpn file 
config.ovpn`.
  After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off 
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
  I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains:

  [main]
  # We need to specify "dns=systemd-resolved" as for the time being our
  # /etc/resolv.conf points to resolvconf's generated file instead of
  # systemd-resolved's, so the auto-detection does not work.
  dns=systemd-resolved

  Given all this, what I believe _should_ happen is when I start the
  VPN, /run/NetworkManager/no-stub-resolv.conf should be updated to list
  the DNS server I've specified first, AND NetworkManager should tell
  systemd-resolved to associate that DNS server with the tun0 network
  interface created for the VPN.

  The former happens, i.e., no-stub-resolv.conf is updated, but the
  latter doesn't, i.e., systemd-reoslve --status and resolvectl status
  both do not show the DNS server I've specified in the VPN settings.

  As a result, my DNS server is not getting used.

  I've hacked this all over the place and I can't figure out _any_ way,
  when using systemd-resolved mode in NetworkManager, to get it to use
  my VPN's DNS server when I enable the VPN.

  Surely this behavior is not expected?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 14:19:17 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (28 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 10.204.0.1 dev wlp0s20f3 proto dhcp metric 600 
   10.204.0.0/21 dev wlp0s20f3 proto kernel scope link src 10.204.3.73 metric 
600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (20 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1862080] Re: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

[Sebastien Bacher]

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  If I use xserver-xorg-video-nouveau/focal,now 1:1.0.16-1 amd64
  there is no sound on Display port.
  My graphic card is GTX 1650. 

  Please see bug 1859096. It work with 440 nvidia driver 
  but I want to use Nouveau driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Feb  5 23:50:39 2020
  InstallationDate: Installed on 2020-01-05 (31 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200104)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B51
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1878862] Re: AppArmor - Cannot move snap packages from enforce to complain

[Jamie Strandboge]

snapd manages the security policies for snaps (and it will rewrite the
profiles at some point if you modify them yourself). You may install a
snap in devmode which puts apparmor in complain. Eg:

sudo snap install --devmode mysql-workbench-community

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

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

Title:
  AppArmor - Cannot move snap packages from enforce to complain

Status in apparmor package in Ubuntu:
  Invalid

Bug description:
  I installed mysql-workbench-community from the app store but it is
  unable to actually access the local database due to AppArmor
  intervention.

  All attempts to move the app in to complain results in error messages.

  ~# aa-status 
  apparmor module is loaded.
  10 profiles are loaded.
  10 profiles are in enforce mode.
  .
 snap.mysql-workbench-community.mysql-workbench-community
  .
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  ~# aa-complain /snap/bin/mysql-workbench-community
  Profile for /usr/bin/snap not found, skipping

  ~# aa-complain snap.mysql-workbench-community
  Can't find snap.mysql-workbench-community in the system path list. If the 
name of the application
  is correct, please run 'which snap.mysql-workbench-community' as a user with 
correct PATH
  environment set up in order to find the fully-qualified path and
  use the full path as parameter.

  ~# aa-complain snap.mysql-workbench-community.mysql-workbench-community
  Can't find snap.mysql-workbench-community.mysql-workbench-community in the 
system path list. If the name of the application
  is correct, please run 'which 
snap.mysql-workbench-community.mysql-workbench-community' as a user with 
correct PATH
  environment set up in order to find the fully-qualified path and
  use the full path as parameter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 15 09:47:56 2020
  InstallationDate: Installed on 2020-03-10 (65 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721704] Re: Printer settings stuck on loading drivers database

[Sebastien Bacher]

Thank you for your bug report, could you take a screenshot of the dialog
showing the issue and add a 'journalctl -b 0' log from the session after
getting the bug?

** Package changed: ubuntu-settings (Ubuntu) => system-config-printer
(Ubuntu)

** Changed in: system-config-printer (Ubuntu)
   Importance: Undecided => Low

** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Printer settings stuck on loading drivers database

Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

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

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

[Touch-packages] [Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow

[Jarno Suni]

Well, I think it is not a problem, if we do not need depcache here :)

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

Title:
  'apt-mark showauto' and 'apt show' is slow

Status in apt package in Ubuntu:
  Triaged

Bug description:
  $ time apt-mark showauto >/dev/null

  real  0m0.587s
  user  0m0.552s
  sys   0m0.016s

  When I run the command first time, it is even much slower.

  I could do the job in fraction of a time using awk in POSIX shell
  script:

  auto_file='/var/lib/apt/extended_states'
  eval $(apt-config shell auto_file Dir::State::extended_states/f)
  awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
  }' "$auto_file" | CL_ALL=C sort -u

  real  0m0.019s
  user  0m0.008s
  sys   0m0.000s

  That prints architecture for every package and shows entries in
  slightly different order, though. And the file could be out of date
  showing packages that are not installed?!?

  Similarly

  apt show 

  is slow. (It also shows whether a package is manually or automatically
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.17
  ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 26 12:59:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1070 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apt: [modified]
  modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
  mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
  mtime.conffile..etc.kernel.postinst.d.apt.auto.removal: 
2017-06-01T14:39:39.236080

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

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

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Ricardo Ortega]

Using ubuntu-20.04-live-server-amd64.iso I created an USB and did fresh
install, after fresh install I ran apt get update followed by apt get
upgrade, I then removed the existing yaml in /etc/netplan and added
99_config.yaml:

labuser@lab:~$ sudo nano /etc/netplan/99_config.yaml
labuser@lab:~$ sudo cat /etc/netplan/99_config.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
enp0s25:
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp0s25]
  dhcp4: no
  addresses: [10.59.2.57/24]
  gateway4: 10.59.2.1
  nameservers:
  search: [mydomain, otherdomain]
  addresses: [209.18.47.61, 209.18.47.62]
labuser@lab:~$ sudo shutdown -r
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet6 fe80::ac4c::fe1b:21b7/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ sudo net apply
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet 10.59.2.57/24 brd 10.59.2.255 scope global br0
   valid_lft forever preferred_lft forever
inet6 fe80::ac4c::fe1b:21b7/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ dpkg -l systemd
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)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  systemd245.4-4ubuntu3 amd64system and service manager
labuser@lab:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
labuser@lab:~$ sudo nano /etc/apt/sources.list
labuser@lab:~$ sudo cat /etc/apt/sources.list | grep proposed
deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse 
universe 
labuser@lab:~$ sudo apt update
labuser@lab:~$ sudo apt install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd-sysv systemd-timesyncd
Suggested packages:
  systemd-container
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
  systemd-timesyncd
6 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 4385 kB of archives.
After this operation, 9216 B of additional disk space will be used.
Do you want to continue? [Y/n]
labuser@lab:~$ sudo shutdown -r
labuser@lab:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s25:  mtu 1500 qdisc fq_codel master 
br0 state UP group default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether 3c:d9:2b:4f:01:80 brd ff:ff:ff:ff:ff:ff
inet 10.59.2.57/24 brd 10.59.2.255 scope global br0
   valid_lft forever preferred_lft forever
inet6 fe80::84eb:bdff:feb1:f4e2/64 scope link
   valid_lft forever preferred_lft forever
labuser@lab:~$ dpkg -l systemd
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)
||/ Name   Version  Architecture Description
+++-==---==>
ii  

[Touch-packages] [Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

[RNZ]

Also if apt purge lightdm and remove /var/lib/lightdm, after install
this directory not created and lightmd can't start.

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

Title:
  lightdm: PAM unable to dlopen(pam_kwallet.so):
  /lib/security/pam_kwallet.so: cannot open shared object file: No such
  file or directory

Status in One Hundred Papercuts:
  Confirmed
Status in Light Display Manager:
  Confirmed
Status in systemd:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  auth.log complaints:

  Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
  Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
  Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened 
for user lightdm by (uid=0)
  Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user 
ingroup nopasswdlogin" not met by user "oem"
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for 
user oem by (uid=0)

  
  As per lp:1309535 #18 comment such 'warnings' should be silenced (as they 
scared unawared users about the both needs of pam's gnome/kde)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Dec 19 10:47:07 2014
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

[RNZ]

I have same issue

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

Title:
  lightdm: PAM unable to dlopen(pam_kwallet.so):
  /lib/security/pam_kwallet.so: cannot open shared object file: No such
  file or directory

Status in One Hundred Papercuts:
  Confirmed
Status in Light Display Manager:
  Confirmed
Status in systemd:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  auth.log complaints:

  Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
  Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
  Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened 
for user lightdm by (uid=0)
  Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user 
ingroup nopasswdlogin" not met by user "oem"
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for 
user oem by (uid=0)

  
  As per lp:1309535 #18 comment such 'warnings' should be silenced (as they 
scared unawared users about the both needs of pam's gnome/kde)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Dec 19 10:47:07 2014
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs

[Dimitri John Ledkov]

https://github.com/systemd/systemd/pull/15827

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Dan Streetman]

> Just want to give a heads up that manual unpack followed by apt
install -f still crashes

as stated in comment 15, you MUST reboot between dpkg --unpack and apt
install -f.

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878970] [NEW] Ubuntu 20.04 - AOC HDMI Monitor

[Danilo Buzar]

Public bug reported:

This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590.

I've just bought a monitor AOC 22B1H and I'm using as a second monitor
plugged in HDMI.

For 3 times the system crashed and I had to do a hard reboot for no
reason apparently.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 15:02:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:0957]
   Subsystem: Dell GP108M [GeForce MX250] [1028:0957]
InstallationDate: Installed on 2020-05-04 (11 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 5590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=1a490b05-de14-4d4f-8795-c0fe269ac8cb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 0XRXN9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/15/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5590
dmi.product.sku: 0957
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze 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/1878970

Title:
  Ubuntu 20.04 - AOC HDMI Monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590.

  I've just bought a monitor AOC 22B1H and I'm using as a second monitor
  plugged in HDMI.

  For 3 times the system crashed and I had to do a hard reboot for no
  reason apparently.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 15:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:0957]
 Subsystem: Dell GP108M [GeForce MX250] [1028:0957]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1878969] [NEW] time-epoch never changes in SRUs

[Dimitri John Ledkov]

Public bug reported:

[Impact]

 * Systems without hwclock come up with a fixed time epoch which is not updated 
in SRUs
 * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

[Test Case]

 * Boot without network NTP or hwclock
 * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
 * Boot newer update of systemd, observe that the time epoch is at least 2020

[Regression Potential]

 * Bad epoch, may result in unable to perform TLS connections, validated
GPG signatures, and snapd assertions. Changing epoch to be more recent
is desired. Some machines may rely on the fact that "bionic" without
hwclock always comes up in year 2018. But in practice that is incorrect
thing to do.

[Other Info]
 
 * By default

option('time-epoch', type : 'integer', value : '-1',
   description : 'time epoch for time clients')

in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to
be compliant with the https://reproducible-builds.org/docs/timestamps/
specification.

** Affects: ubuntu-core-initramfs
 Importance: Undecided
 Status: New

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

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

** Affects: systemd (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: ubuntu-core-initramfs
   Importance: Undecided
   Status: New

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

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

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

[Touch-packages] [Bug 1878967] Re: [USB-Audio - Audinst HUD-mx1, playback] No sound at all.

[Vidvuds]

** Description changed:

- Description:  Ubuntu 20.04 LTS
- Release:  20.04
- 
  I can't seem to get Ubuntu to route sound out to my USB connected external 
audio interface or my integrated soundcard (MSI Mortar B450M).
  I have options to select either as output devices in the Sound section of the 
Settings app, however, clicking any of those seems to result in the sound being 
routed out to either my HDMI connected TV, or DisplayPort connected monitor - 
whichever was last chosen from the list.
  The list seems to get populated correctly though, and even correctly reflects 
headphones being plugged into and unplugged from the front panel
  The ubuntu-bug test app was able to successfully play the test tones via both 
interfaces without problem.
- I also notice in the Settings app's Sound section that, when switching 
between my 2 audio-enabled display devices and clicking Test, the selection in 
the list will revert to the 2nd item on the list (which in my case is neither 
of the display devices), but the afore chosen display device will still play 
back the sound.
+ I also notice in the Settings app's Sound section that, when switching 
between my 2 audio-enabled display devices and clicking Test, for some reason 
the Output Device selection gets set to the "Analog Output - Audinst HUD-mx1" 
option no matter where it is on the list, but the afore chosen display device 
will still play back the sound.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  vidis  1815 F pulseaudio
-  /dev/snd/controlC1:  vidis  1815 F pulseaudio
-  /dev/snd/pcmC1D0c:   vidis  1815 F...m pulseaudio
-  /dev/snd/controlC2:  vidis  1815 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  vidis  1815 F pulseaudio
+  /dev/snd/controlC1:  vidis  1815 F pulseaudio
+  /dev/snd/pcmC1D0c:   vidis  1815 F...m pulseaudio
+  /dev/snd/controlC2:  vidis  1815 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 20:01:18 2020
  InstallationDate: Installed on 2020-03-14 (61 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HUDmx1 successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - Audinst HUD-mx1, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-11 (3 days ago)
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.D0:bd01/06/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTAR(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

Title:
  [USB-Audio - Audinst HUD-mx1, playback] No sound at all.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can't seem to get Ubuntu to route sound out to my USB connected external 
audio interface or my integrated soundcard (MSI Mortar B450M).
  I have options to select either as output devices in the Sound section of the 
Settings app, however, clicking any of those seems to result in the sound being 
routed out to either my HDMI connected TV, or DisplayPort connected monitor - 
whichever was last chosen from the list.
  The list seems to get populated correctly though, and even correctly reflects 
headphones being plugged into and unplugged from the front panel
  The ubuntu-bug test app was able to successfully play the test tones via both 
interfaces without problem.
  I also notice in the Settings app's Sound section that, when switching 
between my 2 audio-enabled display devices and clicking Test, for some reason 
the Output Device selection gets set to the 

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Chris Newcomer]

@cekkent: Did you reboot between the "dpkg --unpack..." and "sudo apt
install -f" steps?

That reboot is incredibly important since it switches out the init
process from the faulty one in 2.1 to the one in the 2.2 package.

The "apt install -f" is intended to run the pre/post install scripts for
the package to get it out if the half-installed state.

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack

[kisak]

Hello Mr. Aaltonen, Mr. Zemczak,

Per the distro packaging guidelines for Intel/Iris [1], please add
libepoxy 1.5.4-1 to the set of packages to backport to bionic in this
set and build the xorg packages against it instead of the older
libepoxy. This is to avoid a mixed i965+iris driver situation that is
not recommended.

Alternatively, mesa's debian/rules can be adjusted by adding
`confflags_GALLIUM += -Dprefer-iris=false` immediately after
`GALLIUM_DRIVERS += iris,` to avoid the dependency bump and retain i965
as the default OpenGL driver for all Intel hardware like previous mesa
builds for 18.04.

[1] https://lists.freedesktop.org/archives/mesa-
dev/2020-January/224027.html

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

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

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

[Touch-packages] [Bug 1878967] [NEW] [USB-Audio - Audinst HUD-mx1, playback] No sound at all.

[Vidvuds]

Public bug reported:

Description:Ubuntu 20.04 LTS
Release:20.04

I can't seem to get Ubuntu to route sound out to my USB connected external 
audio interface or my integrated soundcard (MSI Mortar B450M).
I have options to select either as output devices in the Sound section of the 
Settings app, however, clicking any of those seems to result in the sound being 
routed out to either my HDMI connected TV, or DisplayPort connected monitor - 
whichever was last chosen from the list.
The list seems to get populated correctly though, and even correctly reflects 
headphones being plugged into and unplugged from the front panel
The ubuntu-bug test app was able to successfully play the test tones via both 
interfaces without problem.
I also notice in the Settings app's Sound section that, when switching between 
my 2 audio-enabled display devices and clicking Test, the selection in the list 
will revert to the 2nd item on the list (which in my case is neither of the 
display devices), but the afore chosen display device will still play back the 
sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vidis  1815 F pulseaudio
 /dev/snd/controlC1:  vidis  1815 F pulseaudio
 /dev/snd/pcmC1D0c:   vidis  1815 F...m pulseaudio
 /dev/snd/controlC2:  vidis  1815 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 20:01:18 2020
InstallationDate: Installed on 2020-03-14 (61 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HUDmx1 successful
Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [USB-Audio - Audinst HUD-mx1, playback] No sound at all
UpgradeStatus: Upgraded to focal on 2020-05-11 (3 days ago)
dmi.bios.date: 01/06/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.D0:bd01/06/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTAR(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [USB-Audio - Audinst HUD-mx1, playback] No sound at all.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I can't seem to get Ubuntu to route sound out to my USB connected external 
audio interface or my integrated soundcard (MSI Mortar B450M).
  I have options to select either as output devices in the Sound section of the 
Settings app, however, clicking any of those seems to result in the sound being 
routed out to either my HDMI connected TV, or DisplayPort connected monitor - 
whichever was last chosen from the list.
  The list seems to get populated correctly though, and even correctly reflects 
headphones being plugged into and unplugged from the front panel
  The ubuntu-bug test app was able to successfully play the test tones via both 
interfaces without problem.
  I also notice in the Settings app's Sound section that, when switching 
between my 2 audio-enabled display devices and clicking Test, the selection in 
the list will revert to the 2nd item on the list (which in my case is neither 
of the display devices), but the afore chosen display device will still play 
back the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vidis  1815 F pulseaudio
   

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Damian harouff]

Just want to give a heads up that manual unpack followed by apt install
-f still crashes, however the VM automatically rebooted this time
(instead of remaining dead) and I was able to proceed with usual apt
update afterwards with no further issues.

root@web1:~# curl -LO 
https://launchpad.net/ubuntu/+archive/primary/+files/libjson-c2_0.11-4ubuntu2.2_amd64.deb
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 21858  100 218580 0  10273  0  0:00:02  0:00:02 --:--:--  164k
root@web1:~# dpkg --unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb
(Reading database ... 39096 files and directories currently installed.)
Preparing to unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ...
Unpacking libjson-c2:amd64 (0.11-4ubuntu2.2) over (0.11-4ubuntu2.2) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
root@web1:~# reboot
root@web1:~# logout
[root@redacted ~]# vzctl enter 040199a0-e959-4428-87e6-76dd3b26262e
entered into CT
root@web1:/# apt install -f
Reading package lists... Done
Building dependency tree... 50%
[1]+  Stopped apt install -f
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up libjson-c2:amd64 (0.11-4ubuntu2.2) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Got signal 9
[root@redacted ~]#

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878693] Re: apt upgrade of libjson-c2 causes upstart to crash

[John Edwards]

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

** Also affects: json-c (Ubuntu)
   Importance: Undecided
   Status: New

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

** This bug has been marked a duplicate of bug 1878723
   Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

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

Title:
  apt upgrade of libjson-c2 causes upstart to crash

Status in json-c package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in json-c package in Ubuntu Linaro Evaluation Build:
  New

Bug description:
  On Ubuntu 16.04 machines which are still running upstart for init the
  apt upgrade of libjson-c2 to 0.11-4ubuntu2.1 causes upstart to crash
  and leave the machine unusable until rebooted.

  This has occurred on 5 virtual machines running on QEMU/KVM.

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

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

[Touch-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package 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: libdrm (Ubuntu Bionic)
   Status: New => 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 libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1876882

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

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

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

[Touch-packages] [Bug 1789950] Re: [Bluetooth speaker BSP08WBT, playback] No bluetooth playback possible after resuming from suspend

[indigocat]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [Bluetooth speaker BSP08WBT, playback] No bluetooth playback possible
  after resuming from suspend

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  # What happens:
  After resuming from suspend, audio playback to bluetooth speaker isn't 
possible, only the machine's internal speakers work.

  Bluetooth speaker is a selectable option as output, but audio is not
  routed to bluetooth speaker, playback defaults to internal speakers
  even if bluetooth speaker is selected.

  #What should happen:
  When choosing the bluetooth speaker as audio output device, audio should be 
immediately routed to bluetooth speaker.

  #Troubleshoting:
  Already tried `pulseaudio --kill; pulseaudio --start`, `sudo hciconfig hci0 
reset`, and `sudo service udev restart`. Problem persists.

  I'm using kernel 4.4.0-134-generic.
  Cannot use kernel 4.15+ on this machine (older Lenovo T410s), as performance 
drops impressively, due to sub-optimal disk i/o in comparison to 4.4, at least 
on this machine.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dmayr 13648 F pulseaudio
   /dev/snd/controlC0:  dmayr 13648 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Thu Aug 30 13:36:38 2018
  InstallationDate: Installed on 2017-09-24 (340 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: BSP08WBT
  Symptom_Type: None of the above
  Title: [BSP08WBT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924BV6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924BV6:pvrThinkPadT410s:rvnLENOVO:rn2924BV6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2924BV6
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Dan Streetman]

> Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the
same lockup which can only be recovered with a hard reboot.

The 2.2 version includes only a revert of the patch, so for any system
affected by this, the currently-running init still contains the faulty
code, and the fixed package's post-install script calls telinit on the
currently-running init, which triggers the problem.  Work is in progress
to produce a new version that also adjusts the package's post-install
script to detect the problematic version and avoid calling telinit.


For impacted systems, you can follow this process to upgrade to the 
0.11-4ubuntu2.2_amd64.deb package version:

- Obtain the latest package:
```
$ curl -LO 
https://launchpad.net/ubuntu/+archive/primary/+files/libjson-c2_0.11-4ubuntu2.2_amd64.deb
```

- Unpack (install without configuring) the package:
```
$ dpkg --unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb
```

- Reboot; this is mandatory in order to proceed:
```
$ sudo reboot
```

- Configure the package:
```
$ sudo apt install -f
```

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1529152] Autopkgtest regression report (systemd/237-3ubuntu10.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.41) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

python-dbusmock/unknown (armhf)
policykit-1/unknown (armhf)
multipath-tools/unknown (armhf)
debci/unknown (ppc64el)
netplan.io/0.99-0ubuntu3~18.04.1 (i386)
pdns-recursor/unknown (armhf)
umockdev/0.11.1-1 (armhf)
sssd/unknown (armhf)
linux-raspi2-5.3/unknown (armhf)
suricata/unknown (armhf)
lxc/unknown (armhf)
casync/2+61.20180112-1 (s390x)
openssh/1:7.6p1-4ubuntu0.3 (arm64, s390x, amd64, i386, ppc64el, armhf)
python-systemd/unknown (armhf)
puppet/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
postgresql-10/unknown (armhf)
polkit-qt-1/unknown (armhf)
munin/unknown (armhf)
systemd/237-3ubuntu10.41 (armhf)
pulseaudio/unknown (armhf)
php7.2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  slow completion for systemd units

Status in systemd:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in bash-completion source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Won't Fix
Status in bash-completion source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  systemctl tab completion is annoyingly slow.

  [test case]

  on a bionic system:

  $ systemctl status systemd-

  any unit can be used, or even  before specifying any unit name
  chars.

  That will hang for sometimes a few seconds.

  [regression potential]

  this updates systemctl bash completion, so any regression would likely
  result in systemctl command misbehaving; most likely, failure to tab-
  complete.

  [scope]

  This is needed for Bionic and Xenial, however I am not currently
  planning to fix this for Xenial.

  This is fixed by upstream commit
  f28255e2d5695b0d060558ff8cbb2b526fc94cc0 and a few other previous
  commits, which are all included starting in v240, so this is fixed
  already in Eoan and later.

  [original description]

  Pressing Tab after entering `sudo systemctl status
  [existing service name without .service suffix]` into console it takes
  up to 5 seconds until the auto-completion completes. Until then the
  cursor can't be moved.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bash-completion 1:2.1-4.1ubuntu2
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 21:04:41 2015
  InstallationDate: Installed on 2015-04-20 (248 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago)

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

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

[Touch-packages] [Bug 1094235] Re: package libc6 2.15-0ubuntu10.2 failed to install/upgrade: './usr/share/doc/libc6/changelog.Debian.gz' is different from the same file on the system

[indigocat]

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

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

Title:
  package libc6 2.15-0ubuntu10.2 failed to install/upgrade:
  './usr/share/doc/libc6/changelog.Debian.gz' is different from the same
  file on the system

Status in eglibc package in Ubuntu:
  Invalid

Bug description:
  apt-get install -f

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libc6 2.15-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15.1
  Architecture: amd64
  Date: Fri Dec 28 08:24:20 2012
  DpkgTerminalLog:
   Preparando para reemplazar libc6 2.15-0ubuntu10.2 (usando 
.../libc6_2.15-0ubuntu10.3_amd64.deb) ...
   Desempaquetando el reemplazo de libc6 ...
   dpkg: error al procesar 
/var/cache/apt/archives/libc6_2.15-0ubuntu10.3_amd64.deb (--unpack):
'./usr/share/doc/libc6/changelog.Debian.gz' is different from the same file 
on the system
  ErrorMessage: './usr/share/doc/libc6/changelog.Debian.gz' is different from 
the same file on the system
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.15-0ubuntu10.2 failed to install/upgrade: 
'./usr/share/doc/libc6/changelog.Debian.gz' is different from the same file on 
the system
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1867375] Autopkgtest regression report (systemd/237-3ubuntu10.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.41) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

python-dbusmock/unknown (armhf)
policykit-1/unknown (armhf)
multipath-tools/unknown (armhf)
debci/unknown (ppc64el)
netplan.io/0.99-0ubuntu3~18.04.1 (i386)
pdns-recursor/unknown (armhf)
umockdev/0.11.1-1 (armhf)
sssd/unknown (armhf)
linux-raspi2-5.3/unknown (armhf)
suricata/unknown (armhf)
lxc/unknown (armhf)
casync/2+61.20180112-1 (s390x)
openssh/1:7.6p1-4ubuntu0.3 (arm64, s390x, amd64, i386, ppc64el, armhf)
python-systemd/unknown (armhf)
puppet/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
postgresql-10/unknown (armhf)
polkit-qt-1/unknown (armhf)
munin/unknown (armhf)
systemd/237-3ubuntu10.41 (armhf)
pulseaudio/unknown (armhf)
php7.2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Committed
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Committed
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  

[Touch-packages] [Bug 1873607] Autopkgtest regression report (systemd/237-3ubuntu10.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.41) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

python-dbusmock/unknown (armhf)
policykit-1/unknown (armhf)
multipath-tools/unknown (armhf)
debci/unknown (ppc64el)
netplan.io/0.99-0ubuntu3~18.04.1 (i386)
pdns-recursor/unknown (armhf)
umockdev/0.11.1-1 (armhf)
sssd/unknown (armhf)
linux-raspi2-5.3/unknown (armhf)
suricata/unknown (armhf)
lxc/unknown (armhf)
casync/2+61.20180112-1 (s390x)
openssh/1:7.6p1-4ubuntu0.3 (arm64, s390x, amd64, i386, ppc64el, armhf)
python-systemd/unknown (armhf)
puppet/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
postgresql-10/unknown (armhf)
polkit-qt-1/unknown (armhf)
munin/unknown (armhf)
systemd/237-3ubuntu10.41 (armhf)
pulseaudio/unknown (armhf)
php7.2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as 

[Touch-packages] [Bug 1876600] Autopkgtest regression report (systemd/237-3ubuntu10.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.41) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

python-dbusmock/unknown (armhf)
policykit-1/unknown (armhf)
multipath-tools/unknown (armhf)
debci/unknown (ppc64el)
netplan.io/0.99-0ubuntu3~18.04.1 (i386)
pdns-recursor/unknown (armhf)
umockdev/0.11.1-1 (armhf)
sssd/unknown (armhf)
linux-raspi2-5.3/unknown (armhf)
suricata/unknown (armhf)
lxc/unknown (armhf)
casync/2+61.20180112-1 (s390x)
openssh/1:7.6p1-4ubuntu0.3 (arm64, s390x, amd64, i386, ppc64el, armhf)
python-systemd/unknown (armhf)
puppet/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
postgresql-10/unknown (armhf)
polkit-qt-1/unknown (armhf)
munin/unknown (armhf)
systemd/237-3ubuntu10.41 (armhf)
pulseaudio/unknown (armhf)
php7.2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001reply-cookie: 0x0001

  Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
  38  r = sd_bus_message_new_method_call(bus, ,
  $1 = 0x1
  $2 = 0xff00
  Call failed: Operation not supported
  Sleeping and retrying...
  Call failed: Invalid argument
  Assertion 'm->n_ref > 0' failed at 
../src/libsystemd/sd-bus/bus-message.c:934, function sd_bus_message_unref(). 
Aborting.

  Program received signal 

[Touch-packages] [Bug 1877159] Autopkgtest regression report (systemd/237-3ubuntu10.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.41) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

python-dbusmock/unknown (armhf)
policykit-1/unknown (armhf)
multipath-tools/unknown (armhf)
debci/unknown (ppc64el)
netplan.io/0.99-0ubuntu3~18.04.1 (i386)
pdns-recursor/unknown (armhf)
umockdev/0.11.1-1 (armhf)
sssd/unknown (armhf)
linux-raspi2-5.3/unknown (armhf)
suricata/unknown (armhf)
lxc/unknown (armhf)
casync/2+61.20180112-1 (s390x)
openssh/1:7.6p1-4ubuntu0.3 (arm64, s390x, amd64, i386, ppc64el, armhf)
python-systemd/unknown (armhf)
puppet/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
postgresql-10/unknown (armhf)
polkit-qt-1/unknown (armhf)
munin/unknown (armhf)
systemd/237-3ubuntu10.41 (armhf)
pulseaudio/unknown (armhf)
php7.2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  

[Touch-packages] [Bug 1878955] [NEW] resolved dhclient-enter-hook complains about an empty file

[Craig Francis]

Public bug reported:

When starting/using `dhclient`, it will often return an error such as:

cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
hooks.d/resolved"

Because the $oldstate file can be empty, or different, it should use
`cmp --quiet`

This happens when "/run/systemd/resolved.conf.d/isc-
dhcp-v*-$interface.conf" files do not exist, or when the content
changes.

This is very loosely related to
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

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

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

Title:
  resolved dhclient-enter-hook complains about an empty file

Status in systemd package in Ubuntu:
  New

Bug description:
  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

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

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

[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"

[Slater]

This bug affects programs such as GIMP. I could not launch it and I
found this issue by searching "lh_table_new: calloc failed". Reverting
back to libjson-c3 version 0.12.1-1.3 fixes the issue.

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

Title:
  program abort  by "lh_table_new: calloc failed"

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  I wrote small sample program which abort by lh_table_new calloc failed.
  see this.
  https://gist.github.com/735eec6fd0869df1facb08da5baa402c

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

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

[Touch-packages] [Bug 1878953] [NEW] Display settings is lost when switching between modes with Super+P

[Frank Blah]

Public bug reported:

When switching between modes (built-in only, joint, ...) with Super+P,
the display settings are lost. That even occurs when selecting already
selected mode (selecting "joint" while being in "joint" mode).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 18:12:11 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
InstallationDate: Installed on 2020-05-11 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ZBook 15 G6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2019
dmi.bios.vendor: HP
dmi.bios.version: R92 Ver. 01.02.01
dmi.board.name: 860F
dmi.board.vendor: HP
dmi.board.version: KBC Version 65.23.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook 15
dmi.product.name: HP ZBook 15 G6
dmi.product.sku: 6CJ09AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1878953

Title:
  Display settings is lost when switching between modes with Super+P

Status in xorg package in Ubuntu:
  New

Bug description:
  When switching between modes (built-in only, joint, ...) with Super+P,
  the display settings are lost. That even occurs when selecting already
  selected mode (selecting "joint" while being in "joint" mode).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 18:12:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
  InstallationDate: Installed on 2020-05-11 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  

[Touch-packages] [Bug 1878951] [NEW] External monitor won't reconnect after reattaching HDMI cable

[Frank Blah]

Public bug reported:

Steps to reproduce:
1. Successfully connect AOC u2879vf external display by attaching HDMI cable
2. Remove the cable, output switches to the built-in display and external 
display goes black
3. Reconnect the HDMI cable again

What is expected:
The external screen should display the image (as in step 1)

What happened instead:
The system thinks the display is connected (see the xrandr output), but the 
external display is still black (no signal). The clumsy workaround is to use 
Super+P to switch to "built-in display only" and then back to "joint". After 
that, the external monitor comes back.

xrandr outputs:

Step 1
Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 621mm x 341mm
   3840x2160 60.00*+  59.9450.0029.9829.9725.0023.98  
   1920x2160 59.99  
   1920x1080 60.0059.9450.00  
   1680x1050 59.95  
   1440x900  59.89  
   1280x1024 75.0260.02  
   1280x960  60.00  
   1280x720  60.0059.9450.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.3256.25  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0072.8159.9459.93  
DP-1 connected 1920x1080+909+2160 (normal left inverted right x axis y axis) 
344mm x 193mm
   1920x1080 60.03*+  40.02  
DP-2 disconnected (normal left inverted right x axis y axis)

Step 2
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 
344mm x 193mm
   1920x1080 60.03*+  40.02  
DP-2 disconnected (normal left inverted right x axis y axis)

Step 3
Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 621mm x 341mm
   3840x2160 60.00*+  59.9450.0029.9829.9725.0023.98  
   1920x2160 59.99  
   1920x1080 60.0059.9450.00  
   1680x1050 59.95  
   1440x900  59.89  
   1280x1024 75.0260.02  
   1280x960  60.00  
   1280x720  60.0059.9450.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.3256.25  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0072.8159.9459.93  
DP-1 connected 1920x1080+1097+2160 (normal left inverted right x axis y axis) 
344mm x 193mm
   1920x1080 60.03*+  40.02  
DP-2 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 17:43:16 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
InstallationDate: Installed on 2020-05-11 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ZBook 15 G6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2019
dmi.bios.vendor: HP
dmi.bios.version: R92 Ver. 01.02.01
dmi.board.name: 860F
dmi.board.vendor: HP
dmi.board.version: KBC Version 65.23.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook 15
dmi.product.name: HP ZBook 15 G6
dmi.product.sku: 6CJ09AV
dmi.sys.vendor: HP
version.compiz: compiz N/A

[Touch-packages] [Bug 1878752] Related fix proposed to charm-ceph-osd (master)

[OpenStack Infra]

Related fix proposed to branch: master
Review: https://review.opendev.org/728488

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

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

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

[Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso
  instalado, do pacote udev, o script post-installation retornou erro do
  status de saída 1

Status in systemd package in Ubuntu:
  New

Bug description:
  after updating from 18.04 to 20.04, appears errors constantly

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Sat May  9 10:24:26 2020
  ErrorMessage: o subprocesso instalado, do pacote udev, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVE15125CBW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso 
instalado, do pacote udev, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0170D5
  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.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE15125CBW
  dmi.product.sku: 54508549
  dmi.product.version: C800EQPLK
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1878945] Re: crash slapd after update

[John]

** Description changed:

  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;
  
  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and get:
  
  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)
  
  journalctl -xe
  
  -- Unit slapd.service has finished starting up.
- -- 
+ --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit apt-daily.service has finished starting up.
- -- 
+ --
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit slapd.service has begun shutting down.
  May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
  May 15 18:28:14 srv slapd[4020]:...fail!
  May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
  May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit slapd.service has finished shutting down.
  May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
  May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
  May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit slapd.service has begun starting up.
  May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
  May 15 18:28:15 srv slapd[4029]:...done.
  May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
+ --
  -- Unit slapd.service has finished starting up.
- -- 
+ --
  -- The start-up result is done.
  
+ OS: Ubuntu 16.04.6 LTS
+ 
  help, please!

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  New

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:27:32 srv 

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Colin Ian King]

This appears not to be a kernel issue per-se, so any idea of an ETA for
a fix with udev for this?

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

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

Title:
  gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index ->
  g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.1-1ubuntu1~19.04.1, the problem page at 
https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 
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/accountsservice/+bug/1832865/+subscriptions

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1878945] [NEW] crash slapd after update

[John]

Public bug reported:

hi,
after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and get:

5ebeb45f hdb_db_open: database "dc=myBase": db_open(/var/lib/ldap/id2entry.bdb) 
failed: No such file or directory (2).
5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open failed! 
(2)
slap_startup failed (test would succeed using the -u switch)

journalctl -xe

-- Unit slapd.service has finished starting up.
-- 
-- The start-up result is done.
May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
-- Subject: Unit apt-daily.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit apt-daily.service has begun starting up.
May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit apt-daily.service has finished starting up.
-- 
-- The start-up result is done.
May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
-- Subject: Unit slapd.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit slapd.service has begun shutting down.
May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
May 15 18:28:14 srv slapd[4020]:...fail!
May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
-- Subject: Unit slapd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit slapd.service has finished shutting down.
May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
-- Subject: Unit slapd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit slapd.service has begun starting up.
May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
May 15 18:28:15 srv slapd[4029]:...done.
May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
-- Subject: Unit slapd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit slapd.service has finished starting up.
-- 
-- The start-up result is done.

help, please!

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


** Tags: ldap openldap slapd

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  New

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  -- 
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit apt-daily.service has finished starting up.
  -- 
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping 

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Marc Deslauriers]

Also see https://github.com/json-c/json-c/pull/610/

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878770] Re: Ubuntu 18.04 crashes app after updating to libjson-c3:amd64 0.12.1-1.3ubuntu0.1

[Daniel Manrique]

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

** Project changed: canonical-identity-provider => json-c (Ubuntu)

** This bug has been marked a duplicate of bug 1878738
   program abort  by "lh_table_new: calloc failed"

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

Title:
  Ubuntu 18.04 crashes app after updating to libjson-c3:amd64
  0.12.1-1.3ubuntu0.1

Status in json-c package in Ubuntu:
  New

Bug description:
  Hi
  I've founded critcal bug

  App linked with libjson-c3:amd64 0.12.1-1.3ubuntu0.1 crashes
  with information:

  lh_table_new: calloc failed

  Example:
  https://gist.github.com/yusukemihara/735eec6fd0869df1facb08da5baa402c

  Version 0.12.1-1.3 worked fine, problem appear with
  0.12.1-1.3ubuntu0.1

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

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

[Touch-packages] [Bug 1878770] [NEW] Ubuntu 18.04 crashes app after updating to libjson-c3:amd64 0.12.1-1.3ubuntu0.1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi
I've founded critcal bug

App linked with libjson-c3:amd64 0.12.1-1.3ubuntu0.1 crashes
with information:

lh_table_new: calloc failed

Example:
https://gist.github.com/yusukemihara/735eec6fd0869df1facb08da5baa402c

Version 0.12.1-1.3 worked fine, problem appear with 0.12.1-1.3ubuntu0.1

** Affects: json-c (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: critical
-- 
Ubuntu 18.04 crashes app after updating to libjson-c3:amd64 0.12.1-1.3ubuntu0.1 
https://bugs.launchpad.net/bugs/1878770
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to json-c 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 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Leonard Boyce]

Sorry, I posted too soon.

Post reboot:


root@HMPBgZ:~# apt-get update

Fetched 51.5 kB in 1s (46.4 kB/s)
Reading package lists... Done
root@HMPBgZ:~# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct 
the problem. 
root@HMPBgZ:~# dpkg -s libjson-c2
Package: libjson-c2
Status: install ok half-configured
Priority: extra
Section: libs
Installed-Size: 67
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: same
Source: json-c
Version: 0.11-4ubuntu2.2
Config-Version: 0.11-4ubuntu2
Depends: libc6 (>= 2.14)
Description: JSON manipulation library - shared library
 This library allows you to easily construct JSON objects in C,
 output them as JSON formatted strings and parse JSON formatted
 strings back into the C representation of JSON objects.
Homepage: https://github.com/json-c/json-c/wiki
Original-Maintainer: fabien boucher 

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

[Matthias Klumpp]

** Changed in: gnome-software (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Confirmed
Status in ubuntu-meta source package in Focal:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Leonard Boyce]

This is not fixed with the updated package.

Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the
same lockup which can only be recovered with a hard reboot.

root@HMPBgZ:~# dpkg -i libjson-c2_0.11-4ubuntu2.2_amd64.deb 
(Reading database ... 154353 files and directories currently installed.)
Preparing to unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ...
Unpacking libjson-c2:amd64 (0.11-4ubuntu2.2) over (0.11-4ubuntu2.1) ...
Setting up libjson-c2:amd64 (0.11-4ubuntu2.2) ...
packet_write_wait: Connection to xx.xx.xx.xx port 22: Broken pipe

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices

[James Page]

** Attachment added: "lib-udev.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1878752/+attachment/5372124/+files/lib-udev.tar.gz

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

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

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

[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices

[James Page]

** Attachment added: "etc-udev.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1878752/+attachment/5372125/+files/etc-udev.tar.gz

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

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

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

[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices

[Dimitri John Ledkov]

"dropping unrelated symlinks" sounds a lot like "udev drops bcache/by-
uuid names, when didn't ask for it".

I wonder if this issue is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941

CC rharper somehow.

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

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

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

[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

[Launchpad Bug Tracker]

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

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

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Confirmed
Status in ubuntu-meta source package in Focal:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions

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

[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices

[Dmitrii Shcherbakov]

For context: focal kernels seem to contain raharper's patch for bcache
that fixed LP: #1729145.

https://paste.ubuntu.com/p/VkfPDBzqyt/
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=67553dcd79051be43ef73207309bee4cb72e5189

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

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Eric Desrochers]

** Changed in: json-c (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Launchpad Bug Tracker]

This bug was fixed in the package json-c - 0.12.1-1.3ubuntu0.2

---
json-c (0.12.1-1.3ubuntu0.2) bionic-security; urgency=medium

  * Revert the security fixes and rebuild the old version (LP: #1878723)

 -- Chris Coulson   Fri, 15 May 2020
12:33:56 +0100

** Changed in: json-c (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Launchpad Bug Tracker]

This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2

---
json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium

  * Revert the security fixes and rebuild the old version (LP: #1878723)

 -- Chris Coulson   Fri, 15 May 2020
12:33:18 +0100

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Launchpad Bug Tracker]

This bug was fixed in the package json-c - 0.11-4ubuntu2.2

---
json-c (0.11-4ubuntu2.2) xenial-security; urgency=medium

  * Revert the security fixes and rebuild the old version (LP: #1878723)

 -- Chris Coulson   Fri, 15 May 2020
12:11:57 +0100

** Changed in: json-c (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: json-c (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Francis Ginther]

** Tags added: id-5ebd60b9e10a724ad7cbaffe

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in pam package in Debian:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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

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

[Touch-packages] [Bug 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'

[Francis Ginther]

** Tags added: id-5ebd660bfd7e0a67b3d68ea4

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

Title:
  Consider making '-o Acquire::Retries=3' the default for 'apt-get
  update/install/dist-upgrade'

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Groovy:
  Confirmed

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Francis Ginther]

** Tags added: id-5ebe6d95d5ae066b83cac917

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Chris Coulson]

The updated packages just revert the security fixes which resolves this
immediate issue. Keeping the bug open though because we still want to
resolve the underlying issue so that we can republish an update with the
security fixes in it

** Changed in: json-c (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Launchpad Bug Tracker]

This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2

---
json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium

  * Revert the security fixes and rebuild the old version (LP: #1878723)

 -- Chris Coulson   Fri, 15 May 2020
12:33:18 +0100

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Launchpad Bug Tracker]

This bug was fixed in the package json-c - 0.13.1+dfsg-7ubuntu0.2

---
json-c (0.13.1+dfsg-7ubuntu0.2) focal-security; urgency=medium

  * Revert the security fixes and rebuild the old version (LP: #1878723)

 -- Chris Coulson   Fri, 15 May 2020
12:31:48 +0100

** Changed in: json-c (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: json-c (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Jack Howarth]

My experience with focal-proposed and accountsservice
0.6.55-0ubuntu12~20.04.1 has been that the update causes the currently
executing 'sudo apt-get update' to prematurely abort when the gnome
shell crashes. In my case, this left the linux-kerrnel packages only
half configured. My understanding is that 'sudo apt-get update' doesn't
fully run as a background process when executed from a Gnome Terminal
window. So when the gnome shell crashes back to gdm, the current update
is stopped at that point.

I believe the proper way to test this package is on a machine currently
on focal-updates that is then switched to focal-proposed so that the
update occurs against a real-world set of packages and not just the
accountsservice packages alone.

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Andy Whitcroft]

Removed the broken version from the archive, and copied back the
previous version.

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[Paride Legovini]

** Changed in: json-c (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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

[Touch-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

[Jani Uusitalo]

After doing manual dconf cleanup, I've been unable to reproduce the
issue. That's since posting the previous comment, so a few days now. So
I think I'll hold off on reporting this upstream for the time being, but
I'll go ahead and do that if the problem still manifests itself.

Thanks again, Daniel.

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  

[Touch-packages] [Bug 1878884] Re: Fractional scaling results in black screen

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1873403, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1873403
   [nvidia] Screen turns off when trying to set some fractional scaling values

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

Title:
  Fractional scaling results in black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  ==

  1. Open display settings
  2. Enable fractional scaling
  3. Set particular scale for external and internal monitor

  
  What is expected
  

  Working displays

  
  What happened instead
  =

  Experiencing a black screen. I can get the output back by switching to
  another display output with Super+P, which resets the scaling
  fraction.

  
  Additional info
  ===

  Screencast in the attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 11:19:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
  InstallationDate: Installed on 2020-05-11 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ZBook 15 G6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.02.01
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 15
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6CJ09AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1860926] Autopkgtest regression report (systemd/242-7ubuntu3.9)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (242-7ubuntu3.9) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

nghttp2/unknown (armhf)
pulseaudio/unknown (armhf)
docker.io/unknown (armhf)
csync2/unknown (armhf)
network-manager/unknown (armhf)
dovecot/unknown (armhf)
open-iscsi/unknown (armhf)
netplan.io/unknown (armhf)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tinyssh/unknown (armhf)
puppet/unknown (armhf)
corosync/unknown (armhf)
python-uinput/unknown (armhf)
nextepc/unknown (armhf)
debci/unknown (armhf)
pyudev/unknown (armhf)
cups/unknown (armhf)
umockdev/0.13.2-1 (armhf)
cockpit/unknown (ppc64el)
network-manager/1.20.4-2ubuntu2.2 (arm64)
nftables/unknown (armhf)
prometheus/unknown (armhf)
corosync-qdevice/unknown (armhf)
prometheus-bind-exporter/unknown (armhf)
python-systemd/unknown (armhf)
prometheus-alertmanager/unknown (armhf)
ndctl/unknown (armhf)
prometheus-apache-exporter/unknown (armhf)
dpdk/unknown (armhf)
nextepc/0.3.10+nods-3ubuntu1 (ppc64el)
dbus/unknown (armhf)
openssh/1:8.0p1-6build1 (armhf, amd64, i386, ppc64el, arm64, s390x)
openrazer/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
snapd/2.42.1+19.10 (i386)
prometheus-node-exporter/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
python-dbusmock/unknown (armhf)
systemd/242-7ubuntu3.9 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, 

[Touch-packages] [Bug 1873607] Autopkgtest regression report (systemd/242-7ubuntu3.9)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (242-7ubuntu3.9) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

nghttp2/unknown (armhf)
pulseaudio/unknown (armhf)
docker.io/unknown (armhf)
csync2/unknown (armhf)
network-manager/unknown (armhf)
dovecot/unknown (armhf)
open-iscsi/unknown (armhf)
netplan.io/unknown (armhf)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tinyssh/unknown (armhf)
puppet/unknown (armhf)
corosync/unknown (armhf)
python-uinput/unknown (armhf)
nextepc/unknown (armhf)
debci/unknown (armhf)
pyudev/unknown (armhf)
cups/unknown (armhf)
umockdev/0.13.2-1 (armhf)
cockpit/unknown (ppc64el)
network-manager/1.20.4-2ubuntu2.2 (arm64)
nftables/unknown (armhf)
prometheus/unknown (armhf)
corosync-qdevice/unknown (armhf)
prometheus-bind-exporter/unknown (armhf)
python-systemd/unknown (armhf)
prometheus-alertmanager/unknown (armhf)
ndctl/unknown (armhf)
prometheus-apache-exporter/unknown (armhf)
dpdk/unknown (armhf)
nextepc/0.3.10+nods-3ubuntu1 (ppc64el)
dbus/unknown (armhf)
openssh/1:8.0p1-6build1 (armhf, amd64, i386, ppc64el, arm64, s390x)
openrazer/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
snapd/2.42.1+19.10 (i386)
prometheus-node-exporter/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
python-dbusmock/unknown (armhf)
systemd/242-7ubuntu3.9 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 

[Touch-packages] [Bug 1867375] Autopkgtest regression report (systemd/242-7ubuntu3.9)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (242-7ubuntu3.9) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

nghttp2/unknown (armhf)
pulseaudio/unknown (armhf)
docker.io/unknown (armhf)
csync2/unknown (armhf)
network-manager/unknown (armhf)
dovecot/unknown (armhf)
open-iscsi/unknown (armhf)
netplan.io/unknown (armhf)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tinyssh/unknown (armhf)
puppet/unknown (armhf)
corosync/unknown (armhf)
python-uinput/unknown (armhf)
nextepc/unknown (armhf)
debci/unknown (armhf)
pyudev/unknown (armhf)
cups/unknown (armhf)
umockdev/0.13.2-1 (armhf)
cockpit/unknown (ppc64el)
network-manager/1.20.4-2ubuntu2.2 (arm64)
nftables/unknown (armhf)
prometheus/unknown (armhf)
corosync-qdevice/unknown (armhf)
prometheus-bind-exporter/unknown (armhf)
python-systemd/unknown (armhf)
prometheus-alertmanager/unknown (armhf)
ndctl/unknown (armhf)
prometheus-apache-exporter/unknown (armhf)
dpdk/unknown (armhf)
nextepc/0.3.10+nods-3ubuntu1 (ppc64el)
dbus/unknown (armhf)
openssh/1:8.0p1-6build1 (armhf, amd64, i386, ppc64el, arm64, s390x)
openrazer/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
snapd/2.42.1+19.10 (i386)
prometheus-node-exporter/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
python-dbusmock/unknown (armhf)
systemd/242-7ubuntu3.9 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Committed
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Committed
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by 

[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types

[Sebastien Bacher]

Thank you for your bug report. Could you add an example of a such file to the 
bug?
How do you want to open the files? If it's from e.g nautilus then mime-support 
isn't the right place where the mimetype needs to be defined but rather 
shared-mime-info

** Changed in: mime-support (Ubuntu)
   Status: New => Incomplete

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  Incomplete

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

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

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

[Touch-packages] [Bug 1877271] Autopkgtest regression report (systemd/242-7ubuntu3.9)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (242-7ubuntu3.9) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

nghttp2/unknown (armhf)
pulseaudio/unknown (armhf)
docker.io/unknown (armhf)
csync2/unknown (armhf)
network-manager/unknown (armhf)
dovecot/unknown (armhf)
open-iscsi/unknown (armhf)
netplan.io/unknown (armhf)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tinyssh/unknown (armhf)
puppet/unknown (armhf)
corosync/unknown (armhf)
python-uinput/unknown (armhf)
nextepc/unknown (armhf)
debci/unknown (armhf)
pyudev/unknown (armhf)
cups/unknown (armhf)
umockdev/0.13.2-1 (armhf)
cockpit/unknown (ppc64el)
network-manager/1.20.4-2ubuntu2.2 (arm64)
nftables/unknown (armhf)
prometheus/unknown (armhf)
corosync-qdevice/unknown (armhf)
prometheus-bind-exporter/unknown (armhf)
python-systemd/unknown (armhf)
prometheus-alertmanager/unknown (armhf)
ndctl/unknown (armhf)
prometheus-apache-exporter/unknown (armhf)
dpdk/unknown (armhf)
nextepc/0.3.10+nods-3ubuntu1 (ppc64el)
dbus/unknown (armhf)
openssh/1:8.0p1-6build1 (armhf, amd64, i386, ppc64el, arm64, s390x)
openrazer/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
snapd/2.42.1+19.10 (i386)
prometheus-node-exporter/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
python-dbusmock/unknown (armhf)
systemd/242-7ubuntu3.9 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  networkd does not enable ipv6 when requested

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  if networkd is configured with ipv6 address but the 'disable_ipv6'
  sysctl is enabled, networkd does not enable it and set the ipv6
  configuration.

  [test case]

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  [regression potential]

  any regression would likely result in failure to configure ipv6
  addresses/routes.

  [scope]

  this is needed only for Eoan.

  this is fixed by commit 57ad76074670d4859e808a6aabd69fd6e58514c5,
  which is included starting in v243, so this is fixed in Focal and
  later.

  this bug was introduced by a series of patches starting at
  54a1a535bd60f13964bbddd8f381601e33e8e56f, which is included starting
  in v243, but was also pulled into Debian v242-4, and so included in
  Eoan.  This bug is not present in earlier versions so is not needed in
  Xenial or Bionic.

  [other info]

  this is a follow on for the fix in bug 1859862.

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

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

[Touch-packages] [Bug 1878884] [NEW] Fractional scaling results in black screen

[Frank Blah]

Public bug reported:

Steps to reproduce
==

1. Open display settings
2. Enable fractional scaling
3. Set particular scale for external and internal monitor


What is expected


Working displays


What happened instead
=

Experiencing a black screen. I can get the output back by switching to
another display output with Super+P, which resets the scaling fraction.


Additional info
===

Screencast in the attachment.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 11:19:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
InstallationDate: Installed on 2020-05-11 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ZBook 15 G6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2019
dmi.bios.vendor: HP
dmi.bios.version: R92 Ver. 01.02.01
dmi.board.name: 860F
dmi.board.vendor: HP
dmi.board.version: KBC Version 65.23.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook 15
dmi.product.name: HP ZBook 15 G6
dmi.product.sku: 6CJ09AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Screencast from 2020-05-15 11:20:05.webm"
   
https://bugs.launchpad.net/bugs/1878884/+attachment/5371962/+files/Screencast%20from%202020-05-15%2011%3A20%3A05.webm

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

Title:
  Fractional scaling results in black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  ==

  1. Open display settings
  2. Enable fractional scaling
  3. Set particular scale for external and internal monitor

  
  What is expected
  

  Working displays

  
  What happened instead
  =

  Experiencing a black screen. I can get the output back by switching to
  another display output with Super+P, which resets the scaling
  fraction.

  
  Additional info
  ===

  Screencast in the attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission 

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Chih-Hsyuan Ho]

@Daniel, when can we expect the this fix in pulseaudio will show up in
-updates channel for Bionic?  Thanks.

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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

[Touch-packages] [Bug 1878838] Re: Black screen (switched to wrong VT) upon login

[Daniel van Vugt]

Although the workaround is simple, this is a pretty serious bug for
users who don't figure it out.

** Summary changed:

- Black screen after Login
+ Black screen (switched to wrong VT) upon login

** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Black screen (switched to wrong VT) upon login
+ [nvidia] Black screen (switched to wrong VT) upon login

** Summary changed:

- [nvidia] Black screen (switched to wrong VT) upon login
+ [nvidia] Black screen (wrong VT) upon login

** Tags added: black-screen nvidia

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [nvidia] Black screen (wrong VT) upon login

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  OS: Fresh install of ubuntu 20.04

  Steps:

  1. Enter password to login (Black screen is shown)

  Workaround:

  2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with 
login prompt)
  3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen 
is gone)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 14:08:29 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-04-28 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022

[Dan Streetman]

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

** Also affects: gnome-terminal (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-terminal (Ubuntu Bionic)
   Status: New => Invalid

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

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  New

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1878814] [NEW] apparmor stays active even when the service is disabled

[Owen]

Public bug reported:

Trying to access a fresh install of MySQL, what a complete pain that
is!! I installed mysql-workbench-community from the app store. Attempts
to access the database with user root were rebuffed by an AppArmor error
about permissions.

Running aa-status I could see the app in the enforce category, so I made
many attempts to move it to complain, but this failed and I'll file a
bug report about that as well.

I decided to disable both the apparmor and ufw service.

However, the AppArmor permissions error dialog continue to appear and
it's not possible to access the database.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apparmor 2.13.3-7ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 09:40:01 2020
InstallationDate: Installed on 2020-03-10 (65 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] 
AppArmor D-Bus mediation is enabled
 May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] 
AppArmor D-Bus mediation is enabled
 May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] 
AppArmor D-Bus mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  apparmor stays active even when the service is disabled

Status in apparmor package in Ubuntu:
  New

Bug description:
  Trying to access a fresh install of MySQL, what a complete pain that
  is!! I installed mysql-workbench-community from the app store.
  Attempts to access the database with user root were rebuffed by an
  AppArmor error about permissions.

  Running aa-status I could see the app in the enforce category, so I
  made many attempts to move it to complain, but this failed and I'll
  file a bug report about that as well.

  I decided to disable both the apparmor and ufw service.

  However, the AppArmor permissions error dialog continue to appear and
  it's not possible to access the database.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 09:40:01 2020
  InstallationDate: Installed on 2020-03-10 (65 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] 
AppArmor D-Bus mediation is enabled
   May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1878838] [NEW] Black screen after Login

[Aakash]

Public bug reported:

OS: Fresh install of ubuntu 20.04

Steps:

1. Enter password to login (Black screen is shown)

Workaround:

2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with 
login prompt)
3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen 
is gone)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 14:08:29 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
InstallationDate: Installed on 2020-04-28 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1878838

Title:
  Black screen after Login

Status in xorg package in Ubuntu:
  New

Bug description:
  OS: Fresh install of ubuntu 20.04

  Steps:

  1. Enter password to login (Black screen is shown)

  Workaround:

  2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with 
login prompt)
  3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen 
is gone)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 14:08:29 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 

[Touch-packages] [Bug 1878862] [NEW] AppArmor - Cannot move snap packages from enforce to complain

[Owen]

Public bug reported:

I installed mysql-workbench-community from the app store but it is
unable to actually access the local database due to AppArmor
intervention.

All attempts to move the app in to complain results in error messages.

~# aa-status 
apparmor module is loaded.
10 profiles are loaded.
10 profiles are in enforce mode.
.
   snap.mysql-workbench-community.mysql-workbench-community
.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

~# aa-complain /snap/bin/mysql-workbench-community
Profile for /usr/bin/snap not found, skipping

~# aa-complain snap.mysql-workbench-community
Can't find snap.mysql-workbench-community in the system path list. If the name 
of the application
is correct, please run 'which snap.mysql-workbench-community' as a user with 
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.

~# aa-complain snap.mysql-workbench-community.mysql-workbench-community
Can't find snap.mysql-workbench-community.mysql-workbench-community in the 
system path list. If the name of the application
is correct, please run 'which 
snap.mysql-workbench-community.mysql-workbench-community' as a user with 
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apparmor 2.13.3-7ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 15 09:47:56 2020
InstallationDate: Installed on 2020-03-10 (65 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] 
AppArmor D-Bus mediation is enabled
 May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] 
AppArmor D-Bus mediation is enabled
 May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] 
AppArmor D-Bus mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  AppArmor - Cannot move snap packages from enforce to complain

Status in apparmor package in Ubuntu:
  New

Bug description:
  I installed mysql-workbench-community from the app store but it is
  unable to actually access the local database due to AppArmor
  intervention.

  All attempts to move the app in to complain results in error messages.

  ~# aa-status 
  apparmor module is loaded.
  10 profiles are loaded.
  10 profiles are in enforce mode.
  .
 snap.mysql-workbench-community.mysql-workbench-community
  .
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  ~# aa-complain /snap/bin/mysql-workbench-community
  Profile for /usr/bin/snap not found, skipping

  ~# aa-complain snap.mysql-workbench-community
  Can't find snap.mysql-workbench-community in the system path list. If the 
name of the application
  is correct, please run 'which snap.mysql-workbench-community' as a user with 
correct PATH
  environment set up in order to find the fully-qualified path and
  use the full path as parameter.

  ~# aa-complain snap.mysql-workbench-community.mysql-workbench-community
  Can't find snap.mysql-workbench-community.mysql-workbench-community in the 
system path list. If the name of the application
  is correct, please run 'which 
snap.mysql-workbench-community.mysql-workbench-community' as a user with 
correct PATH
  environment set up in order to find the fully-qualified path and
  use the full path as parameter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 15 09:47:56 2020
  InstallationDate: Installed on 2020-03-10 (65 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   

[Touch-packages] [Bug 1878782] [NEW] Bluetooth is on but scanned devices are not showing.

[Nimit Khandelwal]

Public bug reported:

Bluetooth in spite of being switched on, shows the same image as when it
is off in the paired devices menu. I cannot access my paired devices.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 13:48:16 2020
InstallationDate: Installed on 2020-05-12 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 1TCN27WW(V2.08)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 110-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
dmi.product.family: ideapad 110-15ISK
dmi.product.name: 80UD
dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
dmi.product.version: Lenovo ideapad 110-15ISK
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "The attachment demonstrates the bug."
   
https://bugs.launchpad.net/bugs/1878782/+attachment/5371904/+files/Bug_Report.png

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

Title:
  Bluetooth is on but scanned devices are not showing.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bluetooth in spite of being switched on, shows the same image as when
  it is off in the paired devices menu. I cannot access my paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 13:48:16 2020
  InstallationDate: Installed on 2020-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1TCN27WW(V2.08)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
  dmi.product.family: ideapad 110-15ISK
  dmi.product.name: 80UD
  dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
  dmi.product.version: Lenovo ideapad 110-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Iain Lane]

Right. It's in the library. Programs will remain using the versions of
the libraries that were on the system when they started, so that means
that you need to upgrade, reboot, and *then* try the restart. I should
update the QA steps to make that more clear, will do.

** Description changed:

  [ Description ]
  
  When accountsservice's daemon is restarted - particularly when there is
  a user configured for auto login - it can cause code using its library
  to crash. This is bad because gnome-shell is one of those users which
  crashes.
  
  [ QA ]
  
  Configure a user for automatic login in gnome-shell.
+ 
+ Update to this SRU, and then *restart your system*. The crash is in the
+ library part, and so you will still see it if programs loaded the buggy
+ version. Restarting is the easiest way to make sure you're not on it.
  
  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.
  
  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.
  
  ---
  
  Test that fast user switching still works properly.
  
  ---
  
  Take a look at the error reports listed below and hopefully see them not
  occurring (barring the usual noise) with the SRU.
  
  [ Regression potential ]
  
  We think this is safe - it tells clients that the daemon is away when it
  quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when they
  weren't before now, so that could cause problems. Watch out for errors
  creeping up with this SRU.
  
  We wondered upstream whether some more protections might be needed. I'm
  thinking that those should be *additional* safety rails around this fix,
  but it could actually be that more is needed and this fix isn't
  complete.
  
  [ Original report ]
  
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it 

[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types

[Charles Plessy]

Hello,

You can add `application/vnd.apple.pages pages` in `/etc/mime.types` on
your system, and I will do it in a future update of the `mime-support`
package, but it will not effect the output of the `file` command, which
uses a different database.

You can open a bug on the `file` package to request it, but please have
a look if you can at 
before: as you will see, unless you can provide a “magic number” for
that format (a proprietary format from a proprietary software, if I may
comment), it may not be possible to detect it.

You can also have a look at the `shared-mime-info` package for another
way to associate the `.pages` file suffix to the
`application/vnd.apple.pages` media type.

Have a nice day,

Charles Plessy

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

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

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

[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Iain Lane]

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

It's not a regression. It is in fact the same bug happening one last
time. I just explained it in the other bug, hope that's clear.

(If I'm not understanding right, please un-dupe and re-open this bug.)

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

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

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

Status in accountsservice package in Ubuntu:
  New

Bug description:
  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
  point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

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

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