[Touch-packages] [Bug 1923553] Re: software-properties-qt python exception on selecting "other" package source

2021-04-12 Thread elguavas
** Description changed:

  on hirsute (21.04) software-properties-qt (software-properties-
  qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
  python exception when a package download source of "other" is selected.
+ the same error occurs when using software-properties-gtk.
  
  this python traceback appears in the console:
  
  Traceback (most recent call last):
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
- dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
55, in __init__
- self.country_info = CountryInformation()
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
- it = et.getiterator('iso_3166_entry')
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
+ dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
55, in __init__
+ self.country_info = CountryInformation()
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
+ it = et.getiterator('iso_3166_entry')
  AttributeError: 'ElementTree' object has no attribute 'getiterator'
  
  i assume the underlying python code being called is using the long
  deprecated and now removed "getiterator" method in ElementTree to
  generate the list of "other" download sources.

** Summary changed:

- software-properties-qt python exception on selecting "other" package source
+ software-properties python exception on selecting "other" package source

** Summary changed:

- software-properties python exception on selecting "other" package source
+ software-properties gui python exception on selecting "other" package source

** Description changed:

  on hirsute (21.04) software-properties-qt (software-properties-
  qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
  python exception when a package download source of "other" is selected.
- the same error occurs when using software-properties-gtk.
+ the same error occurs when using software-properties-gtk (software-
+ properties-gtk/hirsute 0.99.8).
  
  this python traceback appears in the console:
  
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
  dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
55, in __init__
  self.country_info = CountryInformation()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
  it = et.getiterator('iso_3166_entry')
  AttributeError: 'ElementTree' object has no attribute 'getiterator'
  
  i assume the underlying python code being called is using the long
  deprecated and now removed "getiterator" method in ElementTree to
  generate the list of "other" download sources.

** Description changed:

  on hirsute (21.04) software-properties-qt (software-properties-
  qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
  python exception when a package download source of "other" is selected.
- the same error occurs when using software-properties-gtk (software-
- properties-gtk/hirsute 0.99.8).
+ the same underlying error occurs when using software-properties-gtk
+ (software-properties-gtk/hirsute 0.99.8).
  
- this python traceback appears in the console:
+ this python traceback appears in the console for the qt gui:
  
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
  dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
55, in __init__
  self.country_info = CountryInformation()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
  it = et.getiterator('iso_3166_entry')
  AttributeError: 'ElementTree' object has no attribute 'getiterator'
  
- i assume the underlying python code being called is using the long
- deprecated and now removed "getiterator" method in ElementTree to
- generate the list of "other" download sources.
+ and this appears for the gtk gui:
+ 
+ Traceback (most recent call last):
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 661, in on_combobox_server_changed
+ dialog = 

[Touch-packages] [Bug 1923553] [NEW] software-properties-qt python exception on selecting "other" package source

2021-04-12 Thread elguavas
Public bug reported:

on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.

this python traceback appears in the console:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
  File "/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", 
line 55, in __init__
self.country_info = CountryInformation()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'

i assume the underlying python code being called is using the long
deprecated and now removed "getiterator" method in ElementTree to
generate the list of "other" download sources.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  software-properties-qt python exception on selecting "other" package
  source

Status in software-properties package in Ubuntu:
  New

Bug description:
  on hirsute (21.04) software-properties-qt (software-properties-
  qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
  python exception when a package download source of "other" is
  selected.

  this python traceback appears in the console:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 454, in on_combobox_server_changed
  dialogue = DialogMirror(self.userinterface, self.datadir, self.distro, 
self.custom_mirrors)
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
55, in __init__
  self.country_info = CountryInformation()
File 
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line 
34, in __init__
  it = et.getiterator('iso_3166_entry')
  AttributeError: 'ElementTree' object has no attribute 'getiterator'

  i assume the underlying python code being called is using the long
  deprecated and now removed "getiterator" method in ElementTree to
  generate the list of "other" download sources.

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

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


[Touch-packages] [Bug 1908818] Re: pure packaging of libnss3

2021-04-12 Thread Christian Ehrhardt 
And finally after some fixups in the builders (thanks cjwatson!) 
https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1 also has built 
riscv64.
All ready now

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

Title:
  pure packaging of libnss3

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Groovy:
  Fix Committed
Status in nss source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * A packaging error in the current version has led library symlinks
 to be broken and in the wrong place.

   * Fix by applying the later change to Groovy as well

  [Test Plan]

   * install libnss3
   * check (path depends on the architecture) the lib links
 $ dpkg -L libnss3 | grep MULTIARCH
 # ^^ should be empty
 $ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
 # vv should look like that:

  lrwxrwxrwx 1 root root 17 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
  root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
  lrwxrwxrwx 1 root root 18 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
  lrwxrwxrwx 1 root root 17 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
  lrwxrwxrwx 1 root root 22 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
  lrwxrwxrwx 1 root root 21 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  [Where problems could occur]

   * I first was afraid, that no matter how bad the paths would
 have been we'd need to retain them for anyone using them
 already. But the existing links go into nowhere since they
 are relative therefore the regression risk should be minimal

  root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
  lrwxrwxrwx 1 root root 18 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
  lrwxrwxrwx 1 root root 17 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
  lrwxrwxrwx 1 root root 22 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
  lrwxrwxrwx 1 root root 21 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so

   * never the less, to be clear - if problems occur they would be in 
 loading these libraries. E.g. a user could have had this package
 and a self built nss on his system, after the change it might load the 
 packaged one.

  [Other Info]
   
   * n/a

  ---

  
  dpkg -L libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnss3
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/libnss3
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk

  as we can see soft links to libraries do nor resolve
  ${DEB_HOST_MULTIARCH} to x86_64-linux-gnu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec 20 14:36:10 2020
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

2021-04-12 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  Failed to start Load/Save RF Kill Switch Status

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  systemd-rfkill fails when running under kernel 5.10 or later due to
  change in the kernel/userspace api

  [test case]

  on a system with kernel 5.10 or later, check systemd-rfkill status or
  journal output, see comment 3 for specific failure text

  [regression]

  any regression would almost certainly cause problems with the systemd-
  rfkill service and/or systemd-rfkill binary

  [scope]

  this is needed for focal

  this was fixed upstream in commit
  a71c09685021cbcecb7566a00342421f635cc002 which was backported to h in
  version 247.3-3ubuntu3.

  since this only occurs with kernel 5.10 or later, no releases earlier
  than f are affected because they will never receive kernel 5.10.

  since the HWE kernel in f will be updated to 5.10 once 21.04 is
  released, this is needed for f. Since a user could upgrade to the 5.10
  HWE kernel in f, and then do-release-upgrade to g before it EOL, this
  is also needed in g.

  [original description]

  
  When I boot the system I get these lög messages
  - Failed to start Load/Save RF Kill Switch Statu
  - A start job for unit systemd-rfkill.service has failed
  and with sender systemd-rfkil
  Read event structure of invalid size

  Also happens on an Ubuntu system on the same computer.

  System details

  p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
  System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: 
     Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804
     date: 02/02/2021
  CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB
     Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798
     8: 2239 9: 2238 10: 2233 11: 2236 12: 2234
  Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu
     v: kernel
     Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa
     resolution: 2560x1440~60Hz
     OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1
  Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel
     Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel
     Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo
     Sound Server: ALSA v: k5.11.0-11-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
     IF: wlp6s0 state: down mac: 
     Device-2: Realtek RTL8125 2.5GbE driver: r8169
     IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: 
     IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
     IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
  Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb
     Report: ID: hci0 state: up running pscan bt-v: 3.0 address: 

  Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%)
     ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB
     ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 
465.76 GiB
     ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 
465.76 GiB
  Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2
     ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile
  Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 
40.0 C
     Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0
  Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB 
(12.1%) Shell: Bash inxi: 3.3.01
  p-i@pi-tuf-b550m-wifi:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Mar 29 10:12:21 2021
  

[Touch-packages] [Bug 1923542] [NEW] "Failed to restart network-manager.service: Unit network-manager.service not found." during package update

2021-04-12 Thread Thomas Bechtold
Public bug reported:

I updated network-manger on hirsute:

network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over
(1.30.0-1ubuntu2)

During the postinst run, I get:

Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ...
Failed to restart network-manager.service: Unit network-manager.service not 
found.
invoke-rc.d: initscript network-manager, action "force-reload" failed.

The reason seems to be that there is no network-manager.service . it's
called NetworkManager.service .

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 06:15:31 2021
InstallationDate: Installed on 2020-12-08 (125 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
RebootRequiredPkgs: network-manager
SourcePackage: network-manager
UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  "Failed to restart network-manager.service: Unit network-
  manager.service not found." during package update

Status in network-manager package in Ubuntu:
  New

Bug description:
  I updated network-manger on hirsute:

  network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over
  (1.30.0-1ubuntu2)

  During the postinst run, I get:

  Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ...
  Failed to restart network-manager.service: Unit network-manager.service not 
found.
  invoke-rc.d: initscript network-manager, action "force-reload" failed.

  The reason seems to be that there is no network-manager.service . it's
  called NetworkManager.service .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 13 06:15:31 2021
  InstallationDate: Installed on 2020-12-08 (125 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RebootRequiredPkgs: network-manager
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   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/1923542/+subscriptions

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


[Touch-packages] [Bug 1915386] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2021-04-12 Thread Launchpad Bug Tracker
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  erreur logiciel lors ouverture session ou pour upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6
  ProcVersionSignature: Ubuntu 4.4.0-201.233-generic 4.4.247
  Uname: Linux 4.4.0-201-generic i686
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: i386
  Date: Wed Feb 10 23:01:24 2021
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2021-02-10 (0 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32ubuntu0.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2020-02-17T19:03:38

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

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


[Touch-packages] [Bug 1923541] [NEW] /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

2021-04-12 Thread Thomas Bechtold
Public bug reported:

Currently running 21.04, apport version is 2.20.11-0ubuntu62 .

When I try to fill a bug, I see:

$ ubuntu-bug  network-manager
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
apport.hookutils.attach_casper_md5check(report,
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in 
attach_casper_md5check
del report['CasperMD5json']
  File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__
del self.data[key]
KeyError: 'CasperMD5json'


It's not crashing the bug reporting itself, but it looks wrong to have a 
stacktrace on the command line.

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

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

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  New

Bug description:
  Currently running 21.04, apport version is 2.20.11-0ubuntu62 .

  When I try to fill a bug, I see:

  $ ubuntu-bug  network-manager
  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
  apport.hookutils.attach_casper_md5check(report,
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in 
attach_casper_md5check
  del report['CasperMD5json']
File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__
  del self.data[key]
  KeyError: 'CasperMD5json'

  
  It's not crashing the bug reporting itself, but it looks wrong to have a 
stacktrace on the command line.

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

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


[Touch-packages] [Bug 1923513] Re: xrandr --panning problem

2021-04-12 Thread Daniel van Vugt
** Tags added: focal

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  xrandr --panning problem

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Dear community 
  Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux 
Mint 20 

  Distribution: 
  cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

  Netbook is with small screen 
  1024x600
  To get bigger virtual screen I use xrandr like:

  xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

  To return to normal screen I use

  xrandr --fb 1024x600

  What is expected:
  when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

  What is in reality:

  With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
  When I move mouse down below the original 600 pixels,
  first 768-600=168 strings are shown like a background image.
  Or 
  new virtual 601 string is the copy of the old 1
  602 string is the copy of the old 2
  ...
  768 string is the copy of the old 168
   
  It looks like an index shift in the array:
  The string which "disappears" from the top is moved to the bottom   

  This "background" image can be overwritten by the real application window.
  For example, if I move the terminal window it appears on the top of this 
"background"   
  But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
  the shifted copy of the top part of the screen appears at the bottom 
according the 
  1->601 
  2->602 etc logic.

  After playing a lot with xrandr parameters I had found a workaround:
  One has to specify the first parameter in --fb bigger than the first 
parameter in --panning

  For example:
  xrandr --fb 1025x768 --output LVDS1 --panning 1024x768

  Here 1025>1024

  I had checked this bug  with two different laptops, so it is not related with 
the hardware.
  More information:
  xrandr -v
  xrandr program version   1.5.0
  Server reports RandR version 1.6

  The working configuration:
  xrandr
  Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis

  Wrongly working configuration:
   
  xrandr
  Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  Hope you can reproduce this bug.

  Best regards, Dmitry

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

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


[Touch-packages] [Bug 1923512] Re: Simple Scan

2021-04-12 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => simple-scan (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/1923512

Title:
  Simple Scan

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Non si avvia

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompositorRunning: None
  Date: Mon Apr 12 23:52:06 2021
  DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2019-10-24 (536 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic 
root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago)
  dmi.bios.date: 06/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0416
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QPL-AM
  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.:bvr0416:bd06/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  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 Mar  8 18:21:30 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputYSTEK USB Mouse  MOUSE, id 8
   inputMicrosoft® LifeCam VX-2000: Mi KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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


[Touch-packages] [Bug 1923437] Re: can't set 2560x1440 resolution after installing nvidia drivers

2021-04-12 Thread Daniel van Vugt
It appears 2560x1440 was a fake mode created by the open source driver.
It's not a mode that is officially supported by the monitor itself,
whose data I have decoded below:

EDID version: 1.4
Manufacturer: GSM Model 23305 Serial Number 181370
Made in week 5 of 2016
Digital display
10 bits per primary color channel
DisplayPort interface
Maximum image size: 60 cm x 34 cm
Gamma: 2.20
DPMS levels: Standby
Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing includes the native pixel format and preferred refresh 
rate
Color Characteristics
  Red:   0.6523, 0.3349
  Green: 0.3046, 0.6367
  Blue:  0.1484, 0.0615
  White: 0.3134, 0.3291
Established Timings I & II
640x48059.940 Hz   4:331.469 kHz  25.175 MHz (DMT)
800x60060.317 Hz   4:337.879 kHz  40.000 MHz (DMT)
   1024x76860.004 Hz   4:348.363 kHz  65.000 MHz (DMT)
Standard Timings
   1152x86459.959 Hz   4:353.783 kHz  81.750 MHz (EDID 1.4 source: CVT)
   1152x86460.000 Hz   4:353.700 kHz  81.624 MHz (EDID 1.3 source: GTF)
   1280x1024   60.020 Hz   5:463.981 kHz 108.000 MHz (DMT)
   1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (DMT)
   1600x90060.000 Hz  16:960.000 kHz 108.000 MHz (DMT, RB)
   1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (DMT)
   1280x80059.810 Hz  16:10   49.702 kHz  83.500 MHz (DMT)
Detailed mode: Clock 533.280 MHz, 600 mm x 340 mm
   3840 3848 3992 4000 (  8 144   8)
   2160 2214 2219  ( 54   5   3)
   +hsync -vsync
   VertFreq: 60.000 Hz, HorFreq: 133.320 kHz
Detailed mode: Clock 266.640 MHz, 600 mm x 340 mm
   3840 3848 3992 4000 (  8 144   8)
   2160 2214 2219  ( 54   5   3)
   +hsync -vsync
   VertFreq: 30.000 Hz, HorFreq: 66.660 kHz
Display Range Limits
  Monitor ranges (GTF): 56-61 Hz V, 30-135 kHz H, max dotclock 560 MHz
Display Product Name: LG Ultra HD
Has 1 extension block
Checksum: 0x11



CTA-861 Extension Block Revision 3
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
13 bytes of CTA data blocks
  Video Data Block
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4)
  720x48059.940 Hz  16:931.469 kHz  27.000 MHz (VIC   3)
  640x48059.940 Hz   4:331.469 kHz  25.175 MHz (VIC   1)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
Detailed mode: Clock 148.500 MHz, 600 mm x 340 mm
   1920 2008 2052 2200 ( 88  44 148)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Checksum: 0x41


** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu)

** Summary changed:

- can't set 2560x1440 resolution after installing nvidia drivers 
+ Can't add custom mode 2560x1440 after installing nvidia drivers

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

Title:
  Can't add custom mode 2560x1440 after installing nvidia drivers

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  Hello !

  I have 2 monitors 
  1) one is 4K 
  2) another one is FULLHD, 
  when I installed lubuntu I had 4k monitor work at maximum 4k and another at 
fullhd , I want to change that 4k monitor to 2560x1440(2k). 

  after install nvidia drivers there is no 2560x1440 resolution in
  "monitor settings" resolutions tab like it was before installing
  drivers. when trying to add it manually from xrandr, at some point it
  gives me that error:

  X Error of failed request:  BadName (named color or font does not exist)
Major opcode of failed request:  140 (RANDR)
Minor opcode of failed request:  16 (RRCreateMode)
Serial number of failed request:  35
Current serial number in output stream:  35

  in short , I can't set monitor to 2560x1440. what it might be ?

  --

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Unable to locate package pkgname

  3) What you expected to happen

  have 2560x1440 resolution option after installing nvidia driver

  4) What happened instead

  have no 2560x1440 listed in "monitor settings" and can't even create
  it manually from xrandr commands

  Best 

[Touch-packages] [Bug 1922536] Re: bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth

2021-04-12 Thread Daniel van Vugt
There was a suggestion in bug 1912940 that the latest hirsute updates
have fixed the problem. Please run:

  sudo apt update
  sudo apt full-upgrade

and tell us if the problem persists.

** This bug is no longer a duplicate of bug 1912940
   Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth 
(ideapad_bluetooth) disabled every time on startup

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

** Summary changed:

- bluetooth not working in gnome settings after reboot and requires systemctl 
restart bluetooth
+ Bluetooth (ideapad_bluetooth) not working in gnome settings after reboot and 
requires systemctl restart bluetooth

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

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

Title:
  Bluetooth (ideapad_bluetooth) not working in gnome settings after
  reboot and requires systemctl restart bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Selected logs:
  https://paste.ubuntu.com/p/gMbk2ntQyz/
  https://paste.ubuntu.com/p/F8n72kCbJJ/
  lshw:
  https://paste.ubuntu.com/p/3Z9jwBdyVt/

  If I try and use the bluetooth toggle in gnome settings upon boot it
  won't do anything. If I have the bluetooth settings window open in
  gnome settings and manually restart the bluetooth service with: "sudo
  systemctl restart bluetooth" then it starts searching for devices and
  I was able to pair Samsung Galaxy Earbuds after multiple service
  restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 00:35:34 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 81Q9
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D8:3B:BF:4D:22:D0  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:302871 acl:36 sco:0 events:10305 errors:0
TX bytes:822111 acl:36 sco:0 commands:5384 errors:0

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

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


[Touch-packages] [Bug 1923513] Re: xrandr --panning problem

2021-04-12 Thread Chris Guiver
Thank you for the time & effort shown in researching the issue you've
experienced.

Before the bug can really be accepted & worked on by Ubuntu, it'll need
to be confirmed that Linux Mint run-time adjustments are not-at-play,
ie. confirmation on a pure Ubuntu system (with logs provided).

Your logic & effort at finding your issue is noticed & appreciated.

FYI: For best results, it's best to work on the current development
release (so extra SRU steps aren't required, which currently are
required for hirsute, so it'll be likely mean the next i-cycle).

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

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

Title:
  xrandr --panning problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear community 
  Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux 
Mint 20 

  Distribution: 
  cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

  Netbook is with small screen 
  1024x600
  To get bigger virtual screen I use xrandr like:

  xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

  To return to normal screen I use

  xrandr --fb 1024x600

  What is expected:
  when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

  What is in reality:

  With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
  When I move mouse down below the original 600 pixels,
  first 768-600=168 strings are shown like a background image.
  Or 
  new virtual 601 string is the copy of the old 1
  602 string is the copy of the old 2
  ...
  768 string is the copy of the old 168
   
  It looks like an index shift in the array:
  The string which "disappears" from the top is moved to the bottom   

  This "background" image can be overwritten by the real application window.
  For example, if I move the terminal window it appears on the top of this 
"background"   
  But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
  the shifted copy of the top part of the screen appears at the bottom 
according the 
  1->601 
  2->602 etc logic.

  After playing a lot with xrandr parameters I had found a workaround:
  One has to specify the first parameter in --fb bigger than the first 
parameter in --panning

  For example:
  xrandr --fb 1025x768 --output LVDS1 --panning 1024x768

  Here 1025>1024

  I had checked this bug  with two different laptops, so it is not related with 
the hardware.
  More information:
  xrandr -v
  xrandr program version   1.5.0
  Server reports RandR version 1.6

  The working configuration:
  xrandr
  Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis

  Wrongly working configuration:
   
  xrandr
  Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  Hope you can reproduce this bug.

  Best regards, Dmitry

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

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


[Touch-packages] [Bug 1923513] Re: xrandr --panning problem

2021-04-12 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 1923513

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.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.

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

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

Title:
  xrandr --panning problem

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Dear community 
  Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux 
Mint 20 

  Distribution: 
  cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

  Netbook is with small screen 
  1024x600
  To get bigger virtual screen I use xrandr like:

  xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

  To return to normal screen I use

  xrandr --fb 1024x600

  What is expected:
  when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

  What is in reality:

  With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
  When I move mouse down below the original 600 pixels,
  first 768-600=168 strings are shown like a background image.
  Or 
  new virtual 601 string is the copy of the old 1
  602 string is the copy of the old 2
  ...
  768 string is the copy of the old 168
   
  It looks like an index shift in the array:
  The string which "disappears" from the top is moved to the bottom   

  This "background" image can be overwritten by the real application window.
  For example, if I move the terminal window it appears on the top of this 
"background"   
  But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
  the shifted copy of the top part of the screen appears at the bottom 
according the 
  1->601 
  2->602 etc logic.

  After playing a lot with xrandr parameters I had found a workaround:
  One has to specify the first parameter in --fb bigger than the first 
parameter in --panning

  For example:
  xrandr --fb 1025x768 --output LVDS1 --panning 1024x768

  Here 1025>1024

  I had checked this bug  with two different laptops, so it is not related with 
the hardware.
  More information:
  xrandr -v
  xrandr program version   1.5.0
  Server reports RandR version 1.6

  The working configuration:
  xrandr
  Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis

  Wrongly working configuration:
   
  xrandr
  Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
  LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 220mm x 130mm panning 1024x768+0+0
 1024x600  60.19*+
 1024x576  59.9059.82  
 960x540   59.6359.82  
 800x600   60.3256.25  
 864x486   59.9259.57  
 640x480   59.94  
 720x405   59.5158.99  
 640x360   59.8459.32  
 512x300   60.00  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  Hope you can reproduce this bug.

  Best regards, Dmitry

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

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


[Touch-packages] [Bug 1923273] Re: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff

2021-04-12 Thread xiao huang
Issues have been assigned numbers CVE-2021-30498、CVE-2021-30499

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30498

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30499

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

Title:
  buffer-overflow on libcaca-0.99.beta20/export.c export_tga,
  export_troff

Status in libcaca package in Ubuntu:
  New

Bug description:
  Hello Ubuntu Security Team
  I use libfuzzer to test libcaca api .I found two crash

  - https://github.com/cacalabs/libcaca/issues/53

  - https://github.com/cacalabs/libcaca/issues/54

  
  ## Vendor of Product
  https://github.com/cacalabs/libcaca

  
  ## Affected Product Code Base
  libcaca e4968ba
  
  ## Affected Component
  affected component:libcaca.so
  
  ## Affected source code file
  affected source code file(As call stack):

 ->caca_export_canvas_to_memory()  in
  libcaca/caca/codec/export.c

 ->caca_export_memory()in
  libcaca/caca/codec/export.c

 -> export_tga()in  
libcaca/caca/codec/export.c

-> export_troff()   in  
libcaca/caca/codec/export.c

   
  ## Attack Type
  Context-dependent

  
  ## Impact Denial of Service
  true

  
  ## Reference
  https://github.com/cacalabs/libcaca

  
  ## Discoverer
  fdgnneig

  
  ## Verification process and POC

  ### Verification steps:

  1.Get the source code of libcaca:

  2.Compile the libcaca.so library:

  ```shell
  $ cd libcaca
  $ apt-get install automake libtool pkg-config -y
  $ ./bootstrap
  $ ./configure
  $ make

  3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc

  4.Run POC

  
  POC.sh
  ```
  cat << EOF > poc_troff.cc
  #include "config.h"
  #include "caca.h"
  //#include "common-image.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"troff",);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;

  }

  
  int main(int args,char* argv[]){

 size_t  len = 0;
 unsigned char buffer[] = 
{0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
 printf("%d\n",sizeof(buffer)/sizeof(unsigned char));

 return 0;

  }
  EOF

  clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address
  -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o
  poc_troff

  
  cat << EOF > poc_tga.cc
  #include "config.h"
  #include "caca.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"tga",);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;
 return 0;
  }

  int main(int args,char* argv[]){

 size_t  len = 0;
 unsigned char buffer[] = 
{0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 

[Touch-packages] [Bug 1923517] Re: tracker-store crashed with signal 5

2021-04-12 Thread Apport retracing service
** Tags removed: need-amd64-retrace

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

Title:
  tracker-store crashed with signal 5

Status in tracker package in Ubuntu:
  New

Bug description:
  This happens with g_listenv

  jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> 
  addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
  g_listenv
  ??:?

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 12 18:16:39 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-04-07 (5 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: libc6
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
  Title: tracker-store crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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


[Touch-packages] [Bug 1923517] [NEW] tracker-store crashed with signal 5

2021-04-12 Thread Joshua Peisach
Public bug reported:

This happens with g_listenv

jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> 
addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
g_listenv
??:?

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
Date: Mon Apr 12 18:16:39 2021
ExecutablePath: /usr/libexec/tracker-store
InstallationDate: Installed on 2021-04-07 (5 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407)
ProcCmdline: /usr/libexec/tracker-store
RebootRequiredPkgs: libc6
Signal: 5
SourcePackage: tracker
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
Title: tracker-store crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

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


** Tags: amd64 apport-crash hirsute need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  tracker-store crashed with signal 5

Status in tracker package in Ubuntu:
  New

Bug description:
  This happens with g_listenv

  jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> 
  addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
  g_listenv
  ??:?

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 12 18:16:39 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-04-07 (5 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: libc6
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
  Title: tracker-store crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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


[Touch-packages] [Bug 1923512] [NEW] Simple Scan

2021-04-12 Thread Luigi Di Virgilio
Public bug reported:

Non si avvia

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
CompositorRunning: None
Date: Mon Apr 12 23:52:06 2021
DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
InstallationDate: Installed on 2019-10-24 (536 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic 
root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago)
dmi.bios.date: 06/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0416
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QPL-AM
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.:bvr0416:bd06/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
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 Mar  8 18:21:30 2020
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputYSTEK USB Mouse  MOUSE, id 8
 inputMicrosoft® LifeCam VX-2000: Mi KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.4

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


** Tags: apport-bug bionic i386 third-party-packages ubuntu

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

Title:
  Simple Scan

Status in xorg package in Ubuntu:
  New

Bug description:
  Non si avvia

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompositorRunning: None
  Date: Mon Apr 12 23:52:06 2021
  DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2019-10-24 (536 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic 
root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago)
  dmi.bios.date: 06/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0416
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QPL-AM
  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: 

[Touch-packages] [Bug 1923513] [NEW] xrandr --panning problem

2021-04-12 Thread dmitry eshchenko
Public bug reported:

Dear community 
Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 
20 

Distribution: 
cat /etc/upstream-release/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

Netbook is with small screen 
1024x600
To get bigger virtual screen I use xrandr like:

xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

To return to normal screen I use

xrandr --fb 1024x600

What is expected:
when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

What is in reality:

With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
When I move mouse down below the original 600 pixels,
first 768-600=168 strings are shown like a background image.
Or 
new virtual 601 string is the copy of the old 1
602 string is the copy of the old 2
...
768 string is the copy of the old 168
 
It looks like an index shift in the array:
The string which "disappears" from the top is moved to the bottom   

This "background" image can be overwritten by the real application window.
For example, if I move the terminal window it appears on the top of this 
"background"   
But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
the shifted copy of the top part of the screen appears at the bottom according 
the 
1->601 
2->602 etc logic.

After playing a lot with xrandr parameters I had found a workaround:
One has to specify the first parameter in --fb bigger than the first parameter 
in --panning

For example:
xrandr --fb 1025x768 --output LVDS1 --panning 1024x768

Here 1025>1024

I had checked this bug  with two different laptops, so it is not related with 
the hardware.
More information:
xrandr -v
xrandr program version   1.5.0
Server reports RandR version 1.6

The working configuration:
xrandr
Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
220mm x 130mm panning 1024x768+0+0
   1024x600  60.19*+
   1024x576  59.9059.82  
   960x540   59.6359.82  
   800x600   60.3256.25  
   864x486   59.9259.57  
   640x480   59.94  
   720x405   59.5158.99  
   640x360   59.8459.32  
   512x300   60.00  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis

Wrongly working configuration:
 
xrandr
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
220mm x 130mm panning 1024x768+0+0
   1024x600  60.19*+
   1024x576  59.9059.82  
   960x540   59.6359.82  
   800x600   60.3256.25  
   864x486   59.9259.57  
   640x480   59.94  
   720x405   59.5158.99  
   640x360   59.8459.32  
   512x300   60.00  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Hope you can reproduce this bug.

Best regards, Dmitry

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

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

Title:
  xrandr --panning problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear community 
  Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux 
Mint 20 

  Distribution: 
  cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

  Netbook is with small screen 
  1024x600
  To get bigger virtual screen I use xrandr like:

  xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

  To return to normal screen I use

  xrandr --fb 1024x600

  What is expected:
  when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

  What is in reality:

  With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
  When I move mouse down below the original 600 pixels,
  first 768-600=168 strings are shown like a background image.
  Or 
  new virtual 601 string is the copy of the old 1
  602 string is the copy of the old 2
  ...
  768 string is the copy of the old 168
   
  It looks like an index shift in the array:
  The string which "disappears" from the top is moved to the bottom   

  This "background" image can be overwritten by the real application window.
  For example, if I move the terminal window it appears on the top of this 
"background"   
  But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
  the shifted copy of the top part of the screen appears at 

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-04-12 Thread Tessa
just tried to use netplan on a public facing server, discovered there's
no `ucarp` integration, and discovered this bug.

is there any ETA on these outstanding items? network HA is a nightmare
without CARP, this feels like essential server functionality.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-12 Thread William Wilson
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836

Apparently I had not created the bug report correctly the first time.

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

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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


[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64

2021-04-12 Thread Tommy Thorn
couldN’T, grr

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

Title:
  Recent update broke qemu-system-riscv64

Status in binutils package in Ubuntu:
  New
Status in gcc-10 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days
  ago broke it.  Now when I launch it, it hits an assertion:



  OpenSBI v0.6  

 _  _ 
/ __ \  / |  _ \_   _|  

   | |  | |_ __   ___ _ __ | (___ | |_) || |

   | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |

   
   | |__| | |_) |  __/ | | |) | |_) || |_   

   
\/| .__/ \___|_| |_|_/|/_|  

  | |   

   
  |_|   



  ...
  Found /boot/extlinux/extlinux.conf

   
  Retrieving file: /boot/extlinux/extlinux.conf 

   
  618 bytes read in 2 ms (301.8 KiB/s)  

  RISC-V Qemu Boot Options  

  1:  Linux kernel-5.5.0-dirty 
  2:  Linux kernel-5.5.0-dirty (recovery mode)
  Enter choice: 1:Linux kernel-5.5.0-dirty  

  Retrieving file: /boot/initrd.img-5.5.0-dirty 

   
  qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: 
Assertion `qemu_coroutine_self() == pool->main_co' failed.  
 
  ./run.sh: line 31:  1604 Aborted (core dumped) 
qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin 
-device virtio-blk-devi
  ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-device,rng=rng0 -drive 
file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi
  ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports


  Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04
  (fully updated).

  
  Think you have everything already, but just in case:

  $ lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  $ uname -a
  Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  (note this is a VM running on macOS/M1)

  $ apt-cache policy qemu
  qemu:
Installed: 1:5.2+dfsg-9ubuntu1
Candidate: 1:5.2+dfsg-9ubuntu1
Version table:
   *** 1:5.2+dfsg-9ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu 1:5.2+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic aarch64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Mon Mar 29 02:33:25 2021
  Dependencies:
   
  KvmCmdLine: COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
  Lspci-vt:
   -[:00]-+-00.0  Apple Inc. Device f020
  +-01.0  Red Hat, Inc. Virtio network device
  +-05.0  Red Hat, Inc. Virtio console
  +-06.0  Red Hat, Inc. Virtio block device
  \-07.0  Red Hat, Inc. Virtio RNG
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
 

[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64

2021-04-12 Thread Tommy Thorn
That would explain why I could reproduce with personal builds.  Glibc
looks very relevant here.

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

Title:
  Recent update broke qemu-system-riscv64

Status in binutils package in Ubuntu:
  New
Status in gcc-10 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days
  ago broke it.  Now when I launch it, it hits an assertion:



  OpenSBI v0.6  

 _  _ 
/ __ \  / |  _ \_   _|  

   | |  | |_ __   ___ _ __ | (___ | |_) || |

   | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |

   
   | |__| | |_) |  __/ | | |) | |_) || |_   

   
\/| .__/ \___|_| |_|_/|/_|  

  | |   

   
  |_|   



  ...
  Found /boot/extlinux/extlinux.conf

   
  Retrieving file: /boot/extlinux/extlinux.conf 

   
  618 bytes read in 2 ms (301.8 KiB/s)  

  RISC-V Qemu Boot Options  

  1:  Linux kernel-5.5.0-dirty 
  2:  Linux kernel-5.5.0-dirty (recovery mode)
  Enter choice: 1:Linux kernel-5.5.0-dirty  

  Retrieving file: /boot/initrd.img-5.5.0-dirty 

   
  qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: 
Assertion `qemu_coroutine_self() == pool->main_co' failed.  
 
  ./run.sh: line 31:  1604 Aborted (core dumped) 
qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin 
-device virtio-blk-devi
  ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-device,rng=rng0 -drive 
file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi
  ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports


  Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04
  (fully updated).

  
  Think you have everything already, but just in case:

  $ lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  $ uname -a
  Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  (note this is a VM running on macOS/M1)

  $ apt-cache policy qemu
  qemu:
Installed: 1:5.2+dfsg-9ubuntu1
Candidate: 1:5.2+dfsg-9ubuntu1
Version table:
   *** 1:5.2+dfsg-9ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu 1:5.2+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic aarch64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Mon Mar 29 02:33:25 2021
  Dependencies:
   
  KvmCmdLine: COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
  Lspci-vt:
   -[:00]-+-00.0  Apple Inc. Device f020
  +-01.0  Red Hat, Inc. Virtio network device
  +-05.0  Red Hat, Inc. Virtio console
  +-06.0  Red Hat, Inc. Virtio block device
  \-07.0  

[Touch-packages] [Bug 1895839] Re: CVE-2020-24977

2021-04-12 Thread Steve Beattie
Please note that upstream has indicated that this issue only affects the
xmllint binary, and not the shared library.

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  Fix Released
Status in libxml2 source package in Hirsute:
  Fix Released
Status in libxml2 package in Debian:
  Fix Released

Bug description:
  GNOME project libxml2 v2.9.10 and earlier have a global buffer over-
  read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch: 
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2

  Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

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

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


[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64

2021-04-12 Thread Christian Ehrhardt 
>From my test PPAs the version "1:5.2+dfsg-9ubuntu2~hirsuteppa3" which is
a no-change rebuild of the formerly working "1:5.2+dfsg-9ubuntu1" did in
three tries fail three times.

So we are not looking at anything that is in the qemu source or the 
Ubuntu/Debian Delta applied to it. But at something in the build environment 
that now creates binaries behaving badly, which built on 2021-03-23 worked fine.
Since I have no idea yet where exactly to look at I'll add "the usual suspects" 
of glibc, gcc-10 and binutils - also Doko/Rbalint (who look after those 
packages) have seen a lot might have an idea about what might be going on here.

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

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

** Also affects: gcc-10 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Recent update broke qemu-system-riscv64

Status in binutils package in Ubuntu:
  New
Status in gcc-10 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days
  ago broke it.  Now when I launch it, it hits an assertion:



  OpenSBI v0.6  

 _  _ 
/ __ \  / |  _ \_   _|  

   | |  | |_ __   ___ _ __ | (___ | |_) || |

   | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |

   
   | |__| | |_) |  __/ | | |) | |_) || |_   

   
\/| .__/ \___|_| |_|_/|/_|  

  | |   

   
  |_|   



  ...
  Found /boot/extlinux/extlinux.conf

   
  Retrieving file: /boot/extlinux/extlinux.conf 

   
  618 bytes read in 2 ms (301.8 KiB/s)  

  RISC-V Qemu Boot Options  

  1:  Linux kernel-5.5.0-dirty 
  2:  Linux kernel-5.5.0-dirty (recovery mode)
  Enter choice: 1:Linux kernel-5.5.0-dirty  

  Retrieving file: /boot/initrd.img-5.5.0-dirty 

   
  qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: 
Assertion `qemu_coroutine_self() == pool->main_co' failed.  
 
  ./run.sh: line 31:  1604 Aborted (core dumped) 
qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin 
-device virtio-blk-devi
  ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-device,rng=rng0 -drive 
file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi
  ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports


  Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04
  (fully updated).

  
  Think you have everything already, but just in case:

  $ lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  $ uname -a
  Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  (note this is a VM running on macOS/M1)

  $ apt-cache policy qemu
  qemu:
Installed: 1:5.2+dfsg-9ubuntu1
Candidate: 1:5.2+dfsg-9ubuntu1
Version table:
   *** 1:5.2+dfsg-9ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu 1:5.2+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic aarch64
  

[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

2021-04-12 Thread Dan Streetman
** Also affects: systemd via
   https://github.com/systemd/systemd/issues/18677
   Importance: Unknown
   Status: Unknown

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

Title:
  Failed to start Load/Save RF Kill Switch Status

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  systemd-rfkill fails when running under kernel 5.10 or later due to
  change in the kernel/userspace api

  [test case]

  on a system with kernel 5.10 or later, check systemd-rfkill status or
  journal output, see comment 3 for specific failure text

  [regression]

  any regression would almost certainly cause problems with the systemd-
  rfkill service and/or systemd-rfkill binary

  [scope]

  this is needed for focal

  this was fixed upstream in commit
  a71c09685021cbcecb7566a00342421f635cc002 which was backported to h in
  version 247.3-3ubuntu3.

  since this only occurs with kernel 5.10 or later, no releases earlier
  than f are affected because they will never receive kernel 5.10.

  since the HWE kernel in f will be updated to 5.10 once 21.04 is
  released, this is needed for f. Since a user could upgrade to the 5.10
  HWE kernel in f, and then do-release-upgrade to g before it EOL, this
  is also needed in g.

  [original description]

  
  When I boot the system I get these lög messages
  - Failed to start Load/Save RF Kill Switch Statu
  - A start job for unit systemd-rfkill.service has failed
  and with sender systemd-rfkil
  Read event structure of invalid size

  Also happens on an Ubuntu system on the same computer.

  System details

  p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
  System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: 
     Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804
     date: 02/02/2021
  CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB
     Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798
     8: 2239 9: 2238 10: 2233 11: 2236 12: 2234
  Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu
     v: kernel
     Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa
     resolution: 2560x1440~60Hz
     OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1
  Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel
     Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel
     Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo
     Sound Server: ALSA v: k5.11.0-11-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
     IF: wlp6s0 state: down mac: 
     Device-2: Realtek RTL8125 2.5GbE driver: r8169
     IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: 
     IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
     IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
  Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb
     Report: ID: hci0 state: up running pscan bt-v: 3.0 address: 

  Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%)
     ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB
     ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 
465.76 GiB
     ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 
465.76 GiB
  Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2
     ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile
  Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 
40.0 C
     Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0
  Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB 
(12.1%) Shell: Bash inxi: 3.3.01
  p-i@pi-tuf-b550m-wifi:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: 

[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-12 Thread Gunnar Hjalmarsson
** Description changed:

+ [Impact]
+ 
+ If you enable the guest session feature on e.g. Ubuntu MATE, you are met
+ by an error message when trying to enter a guest session:
+ 
+ "Could not update file ICEauthority file /run/user/XXX/ICEauthority"
+ 
+ Even if it's not always a fatal error (the login may succeed after a few
+ minutes), the user experience is really bad, and you are inclined to
+ conclude that you are completely blocked from using the feature.
+ 
+ The proposed fix adds a rule to the lightdm-guest-session AppArmor
+ profile and prevents the error from happening.
+ 
+ [Test Plan]
+ 
+ On an updated Ubuntu MATE installation:
+ 
+ * Enable guest session
+ 
+   sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
+ >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
+ 
+ * Install lightdm from {focal,groovy}-proposed
+ 
+ * Reboot
+ 
+ You should now be able to enter a guest session without being stopped by
+ the ICEauthority error.
+ 
+ [Where problems could occur]
+ 
+ This one-liner is a harmless change.
+ 
+ The guest session is run in an unconfined mode since Ubuntu 16.10.
+ That's why the feature is disabled by default.
+ 
+ So if the additional rule would be wrong somehow (which I have no reason
+ to believe), it wouldn't break the AppArmor security layer for the
+ simple reason that it's already broken to begin with.
+ 
+ [Original description]
+ 
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).
  
  ## How to reproduce:
-  - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
-  - enable guest user session
-  - try to login as guest user
+  - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
+  - enable guest user session
+  - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
- ``` 
+ ```
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
- Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
+ Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this:
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
-   owner /run/user/[0-9]*/ICEauthority-? l,`
+   owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

** Changed in: lightdm (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: lightdm (Ubuntu Focal)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.

[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2021-04-12 Thread Dan Streetman
I'm marking this invalid for systemd (the patch there was reverted) and
fix released for plymouth, with the assumption this was fixed with the
patch for bug 1817738.

If anyone is able to reproduce the problem please add a comment.

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
A security update will be issue in next days to fix it on Ubuntu
releases.

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
issued*

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
There are no CVEs for this issues so far.

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

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] [NEW] out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
Public bug reported:

An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

affects Exiv2 in ubuntu releases

** Affects: exiv2 (Ubuntu)
 Importance: Undecided
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

** Changed in: exiv2 (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2021-04-12 Thread Dan Streetman
Unfortunately I can't reproduce this bug, even with the
0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for
sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2.

Also note that the [test case] in the description is wrong, that would
be correct with the systemd change made earlier, but that change was
reverted upstream and in ubuntu, so the test case steps aren't an
accurate indication that the bug is fixed or not.

Anyone on this bug able to reproduce the main problem, of key output
(e.g. passwords) being printed on the console and visible between login
sessions, and/or during shutdown? If not, I think we should consider
this bug fixed.

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

** Changed in: plymouth (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1923472] Re: xdm fails to start on Sundays

2021-04-12 Thread Balint Reczey
** Package changed: systemd (Ubuntu) => xdm (Ubuntu)

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

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

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

Title:
  xdm fails to start on Sundays

Status in xdm package in Ubuntu:
  New
Status in xdm package in Debian:
  Unknown

Bug description:
  On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start
  on Ubuntu 20.04.

  More correctly, it does start, but exits almost immediately on signal
  12. It leaves /var/run/xdm.pid behind, and also a running X server
  with no clients. This makes it hard to restart, for one needs to kill
  the X server and remove the pid file first.

  The cause is logrotate running during startup and killing xdm before
  xdm installs a handler for SIGUSR2. The issue is more fully described
  upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346

  In passing I would comment that running logrotate so early during
  startup seems strange to me. Startup would surely be faster if these
  sort of "cron" jobs were left until it had finished?

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

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


[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Andrea Righi
New debdiff that contains a proper reference to the upstream patch.
Thanks!

** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486963/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

2021-04-12 Thread Dan Streetman
** Description changed:

+ [impact]
+ 
+ systemd-rfkill fails when running under kernel 5.10 or later due to
+ change in the kernel/userspace api
+ 
+ [test case]
+ 
+ on a system with kernel 5.10 or later, check systemd-rfkill status or
+ journal output, see comment 3 for specific failure text
+ 
+ [regression]
+ 
+ any regression would almost certainly cause problems with the systemd-
+ rfkill service and/or systemd-rfkill binary
+ 
+ [scope]
+ 
+ this is needed for focal
+ 
+ this was fixed upstream in commit
+ a71c09685021cbcecb7566a00342421f635cc002 which was backported to h in
+ version 247.3-3ubuntu3.
+ 
+ since this only occurs with kernel 5.10 or later, no releases earlier
+ than f are affected because they will never receive kernel 5.10.
+ 
+ since the HWE kernel in f will be updated to 5.10 once 21.04 is
+ released, this is needed for f. Since a user could upgrade to the 5.10
+ HWE kernel in f, and then do-release-upgrade to g before it EOL, this is
+ also needed in g.
+ 
+ [original description]
+ 
+ 
  When I boot the system I get these lög messages
  - Failed to start Load/Save RF Kill Switch Statu
  - A start job for unit systemd-rfkill.service has failed
  and with sender systemd-rfkil
  Read event structure of invalid size
  
  Also happens on an Ubuntu system on the same computer.
  
  System details
  
  p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
- System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
- Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
-Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804 
-date: 02/02/2021 
- CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB 
-Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 
-8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 
- Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
-v: kernel 
-Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa 
-resolution: 2560x1440~60Hz 
-OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 
- Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
-Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
-Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
-Sound Server: ALSA v: k5.11.0-11-generic 
- Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
-IF: wlp6s0 state: down mac:  
-Device-2: Realtek RTL8125 2.5GbE driver: r8169 
-IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:  
-IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
 
-IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
 
- Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb 
-Report: ID: hci0 state: up running pscan bt-v: 3.0 address: 
 
- Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) 
-ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB 
-ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 
465.76 GiB 
-ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 
465.76 GiB 
- Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2 
-ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1 
- Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile 
- Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 
40.0 C 
-Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0 
- Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB 
(12.1%) Shell: Bash inxi: 3.3.01 
+ System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo)
+ Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: 
+    Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804
+    date: 02/02/2021
+ CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB
+    Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798
+    8: 2239 9: 2238 10: 2233 11: 2236 12: 2234
+ Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu
+    v: kernel
+    Display: x11 server: X.Org 1.20.10 

[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window

2021-04-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Confirmed
Status in orca package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions

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


[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window

2021-04-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Confirmed
Status in orca package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions

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


[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window

2021-04-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: at-spi2-core (Ubuntu)
   Status: New => Confirmed

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Confirmed
Status in orca package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions

-- 
Mailing list: https://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 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Steve Beattie
On Mon, Apr 12, 2021 at 03:07:45PM -, Andrea Righi wrote:
> @sbeattie sorry I didn't notice your comment, I can post another debdiff
> that includes the proper upstream commit.

Probably would be for the best for when we do a merge in the I
cycle, to make identifying which patches can be dropped that much
easier. Thanks.

-- 
Steve Beattie


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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1854772] Re: /var/lib/dpkg/status has faulty entries

2021-04-12 Thread Julian Andres Klode
The status file seems fine, apt is happy with it, this is either a bug
in apt-listchanges or a specific FS corruption, but haven't seen that
before.

** Package changed: apt (Ubuntu) => apt-listchanges (Ubuntu)

** Changed in: apt-listchanges (Ubuntu)
   Status: New => Triaged

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

Title:
  /var/lib/dpkg/status has faulty entries

Status in apt-listchanges package in Ubuntu:
  Triaged
Status in dpkg package in Ubuntu:
  New

Bug description:
  Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
  Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
  self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in 
  self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
  field, value = line.split(':', 1)
  ValueError: not enough values to unpack (expected 2, got 1)

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in 
  main(config)
File "/usr/bin/apt-listchanges", line 83, in main
  status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
  {'what': file, 'errmsg': str(ex)}) from ex
  RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough 
values to unpack (expected 2, got 1)
  (Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit 
installiert.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apt 1.9.4
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Dec  2 16:00:56 2019
  InstallationDate: Installed on 2019-09-09 (83 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-12 Thread Jonas Wiegert
** Changed in: lightdm (Ubuntu Groovy)
   Status: Triaged => 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/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Focal:
  Triaged
Status in lightdm source package in Groovy:
  Incomplete
Status in lightdm source package in Hirsute:
  Fix Released

Bug description:
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ``` 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

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

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


[Touch-packages] [Bug 1923472] [NEW] xdm fails to start on Sundays

2021-04-12 Thread Michael Rutter
Public bug reported:

On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on
Ubuntu 20.04.

More correctly, it does start, but exits almost immediately on signal
12. It leaves /var/run/xdm.pid behind, and also a running X server with
no clients. This makes it hard to restart, for one needs to kill the X
server and remove the pid file first.

The cause is logrotate running during startup and killing xdm before xdm
installs a handler for SIGUSR2. The issue is more fully described
upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346

In passing I would comment that running logrotate so early during
startup seems strange to me. Startup would surely be faster if these
sort of "cron" jobs were left until it had finished?

** 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/1923472

Title:
  xdm fails to start on Sundays

Status in systemd package in Ubuntu:
  New

Bug description:
  On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start
  on Ubuntu 20.04.

  More correctly, it does start, but exits almost immediately on signal
  12. It leaves /var/run/xdm.pid behind, and also a running X server
  with no clients. This makes it hard to restart, for one needs to kill
  the X server and remove the pid file first.

  The cause is logrotate running during startup and killing xdm before
  xdm installs a handler for SIGUSR2. The issue is more fully described
  upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346

  In passing I would comment that running logrotate so early during
  startup seems strange to me. Startup would surely be faster if these
  sort of "cron" jobs were left until it had finished?

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

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


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-12 Thread Launchpad Bug Tracker
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4

---
lightdm (1.30.0-0ubuntu4) hirsute; urgency=medium

  * debian/patches/fix-guest-session-ICEauthority-error.patch:
- Fixes AppArmor issue which prevented access to the guest session
  feature in e.g. MATE (LP: #1921655). Thanks to Jonas Wiegert for
  the solution!
  * debian/patches/Glibc-2.33-fix.patch:
- Cherry picked from upstream to prevent FTBFS
  * debian/patches/dont-turn-format-warnings-into-errors.patch:
- Works around FTBFS on s390x with gcc versions higher than gcc-9.

 -- Gunnar Hjalmarsson   Sun, 11 Apr 2021 00:18:06
+0200

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

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

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Focal:
  Triaged
Status in lightdm source package in Groovy:
  Triaged
Status in lightdm source package in Hirsute:
  Fix Released

Bug description:
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ``` 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

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

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


[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

2021-04-12 Thread Dan Streetman
** Also affects: systemd (Ubuntu Focal)
   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/1921696

Title:
  Failed to start Load/Save RF Kill Switch Status

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

Bug description:
  When I boot the system I get these lög messages
  - Failed to start Load/Save RF Kill Switch Statu
  - A start job for unit systemd-rfkill.service has failed
  and with sender systemd-rfkil
  Read event structure of invalid size

  Also happens on an Ubuntu system on the same computer.

  System details

  p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
  System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
 Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804 
 date: 02/02/2021 
  CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB 
 Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 
 8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 
  Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
 v: kernel 
 Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa 
 resolution: 2560x1440~60Hz 
 OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 
  Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
 Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
 Sound Server: ALSA v: k5.11.0-11-generic 
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
 IF: wlp6s0 state: down mac:  
 Device-2: Realtek RTL8125 2.5GbE driver: r8169 
 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:  
 IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
 
 IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
 
  Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb 
 Report: ID: hci0 state: up running pscan bt-v: 3.0 address: 
 
  Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) 
 ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB 
 ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 
465.76 GiB 
 ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 
465.76 GiB 
  Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1 
  Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile 
  Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 
40.0 C 
 Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0 
  Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB 
(12.1%) Shell: Bash inxi: 3.3.01 
  p-i@pi-tuf-b550m-wifi:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Mar 29 10:12:21 2021
  InstallationDate: Installed on 2021-02-05 (51 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=d37b6e75-43a0-4e56-85c1-4a6ef8e1ffc9 ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  

[Touch-packages] [Bug 1918930] Re: Unexpected file size of one package interrupts update process for all packages and leaves system vulnerable

2021-04-12 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Unexpected file size of one package interrupts update process for all
  packages and leaves system vulnerable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  An unexpected file size error of *one* package interrupts the whole
  update process for *all* packages and this can leave the system in a
  vulnerable state - this is not a constructed situation, but very real
  right now, look at the following console output - sublime has some
  problems with its package size, but then important ssh updates are not
  executed. Bad.

  The following packages will be upgraded:
brave-browser git git-man libpython2.7-minimal libpython2.7-stdlib 
linux-firmware openssh-client openssh-server openssh-sftp-server python2.7 
python2.7-minimal python3-pil sublime-merge
  13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 4.548 kB/199 MB of archives.
  After this operation, 1.744 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 https://download.sublimetext.com apt/stable/ sublime-merge 2049 [4.548 
kB]
  Err:1 https://download.sublimetext.com apt/stable/ sublime-merge 2049
File has unexpected size (4542548 != 4548032). Mirror sync in progress? 
[IP: 104.236.0.104 443]
Hashes of expected file:
 - 
SHA512:f65ce3ca80ff0877da48826a0151036cd8e0bdf28b03d225a03f202262ca1278accdac8e7eb46a22904203750ccf06e3abe496a44f7a4b0c3363076501f72369
 - SHA256:e71fcf37e9d934a60b5112a7b79c819f03f55d331371ec0e9b02378c6234478c
 - SHA1:7fe54a9f7ea5383dbdfc0aae39310e2902c6d7f5 [weak]
 - MD5Sum:fd78a3b986bd7da8b2ebd1f659f5938c [weak]
 - Filesize:4548032 [weak]
  E: Failed to fetch 
https://download.sublimetext.com/files/sublime-merge_build-2049_amd64.deb  File 
has unexpected size (4542548 != 4548032). Mirror sync in progress? [IP: 
104.236.0.104 443]
 Hashes of expected file:
  - 
SHA512:f65ce3ca80ff0877da48826a0151036cd8e0bdf28b03d225a03f202262ca1278accdac8e7eb46a22904203750ccf06e3abe496a44f7a4b0c3363076501f72369
  - SHA256:e71fcf37e9d934a60b5112a7b79c819f03f55d331371ec0e9b02378c6234478c
  - SHA1:7fe54a9f7ea5383dbdfc0aae39310e2902c6d7f5 [weak]
  - MD5Sum:fd78a3b986bd7da8b2ebd1f659f5938c [weak]
  - Filesize:4548032 [weak]
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Note: This issue is not about the package size error in a third party
  repo - I do not blame Ubuntu for problems with that. This is about
  breaking the whole process of updating the system because one single
  sub-task fails.

  Why not make the basic tools really robust and reliable?

  BTW - here are s many free pixels on this screen - why not add two
  or three small sentences about text formatting syntax available in
  this extremely primitive text input box? Is there any text formatting
  at all? Why not put just a little bit of love to the user perspective
  and experience? Just two little senteces about formatting would make
  it so much more user friendly to type here. It feels so quick-and-
  dirty, it hurts. Very sad.

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

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


[Touch-packages] [Bug 1918920] Re: Harden test for no new acquires after transaction abort

2021-04-12 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Harden test for no new acquires after transaction abort

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less 
flaky. No end user impact as it's a test-only change.

  [Test plan]
  Running autopkgtest, which runs our extensive integration test suite which 
includes the changed test.

  [Where problems could occur]
  No end user regression potential on its own, but might slightly change 
regression potential for future pdiff changes:

  Test approach is slightly different now. It still catches that updates
  fail correctly, but tests more concretely that a transaction was
  aborted rather than that no worker received work (which was not
  guaranteed, the work could be scheduled before it was aborted).

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

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


[Touch-packages] [Bug 1918928] Re: APT 2021/03 SRU release scheduling

2021-04-12 Thread Julian Andres Klode
All the SRUs were released the same day, block tags were ignored :-(

** Changed in: apt (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  APT 2021/03 SRU release scheduling

Status in apt package in Ubuntu:
  Invalid

Bug description:
  We want to release the APT SRUs from Mar 2021 in a staggered manner,
  such that we have 2-3 days between each release to get more chance to
  discover regressions before rolling out to older releases.

  Hence this bug, which we tag block-proposed-{bionic,focal} and then
  untag once the delay has passed.

  For groovy, we just want the normal aging :-)

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

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


[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

2021-04-12 Thread Julian Andres Klode
We set Acquire::Retries to 10 on autopkgtest.

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

** Changed in: auto-package-testing
   Status: Triaged => Fix Released

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Fix Released
Status in apt package in Ubuntu:
  Invalid

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_octave-interval_20210319_151509_8348f.gz
 

[Touch-packages] [Bug 1922786] Re: Apt install of local deb files shows a notification causing confusion

2021-04-12 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  Apt install of local deb files shows a notification causing confusion

Status in apt package in Ubuntu:
  Triaged

Bug description:
  
  Installation for a local deb file shows a notification message that causes a 
lot of confusion whether the package has been successfully installed or not.

  Steps to reproduce
  =
  - Download a package file (xxx.deb)
  - Install the package file from command line "sudo apt install ./xxx.deb"
  - A notification messages shows up at the end of the installation saying:
   "Download is performed unsandboxed as root as file 
'/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"

  -> Expected no notification or warnings if installation finished
  successfully.

  It seems that this is only "Notifcation message" BUT it causes a lot
  of confusion whether the package has been installed or not. The
  package seems to be installed correctly from what I understand.

  $ apt --version
  apt 2.2.2 (amd64)

  $ lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  Full log:
  ==
  $ sudo apt install ./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'nrf-command-line-tools' instead of 
'./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
  The following NEW packages will be installed:
nrf-command-line-tools
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  After this operation, 22,6 MB of additional disk space will be used.
  Get:1 
/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb
 nrf-command-line-tools amd64 10.12.1 [3 406 kB]
  Selecting previously unselected package nrf-command-line-tools.
  (Reading database ... 149444 files and directories currently installed.)
  Preparing to unpack .../nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb ...
  Unpacking nrf-command-line-tools (10.12.1) ...
  Setting up nrf-command-line-tools (10.12.1) ...
  N: Download is performed unsandboxed as root as file 
'/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

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

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


[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Andrea Righi
@sbeattie sorry I didn't notice your comment, I can post another debdiff
that includes the proper upstream commit.

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Andrea Righi
** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486955/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

2021-04-12 Thread Till Kamppeter
Please report on the new GitHub of CUPS on OpenPrinting:

https://github.com/OpenPrinting/cups/issues

On Apple the CUPS project is dead and bug reports probably not read any
more.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-12 Thread pkaeding
** Bug watch added: Red Hat Bugzilla #1858866
   https://bugzilla.redhat.com/show_bug.cgi?id=1858866

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-12 Thread Alexander Scheel
** Changed in: shadow (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

-- 
Mailing list: https://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 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-12 Thread pkaeding
For some additional context, here is a related bug report for redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1858866 (they decided to
wont-fix, indicating the flaw is with the CIS benchmark).

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-12 Thread Alexander Scheel
I largely agree but I'd like to point out a little bit of nuance. Even
on modern (e.g., 20.04) systems using shadow by default, global
read/write access to /etc/passwd{,-} _can_ (in some scenarios) still
problematic. A system will still function fine even if /etc/passwd has
000 permissions (+/- some quirks you mentioned, John, about ls and other
utilities not working and the user having no display name when logging
in to their shell).

However, you can still add non-shadowed entries into /etc/passwd{,-} and
have the resulting entries work:

loser:$6$7RrPcCmNJddmS6RK$wHog/STwlVx42Y/jrVMBol9AUHGxywkr7oa4w4gH72Tm0WpCx2nVhmmaIL5JmxJfHLf9ZaoUi/i2RRUp1t8gO.:1001:1000:user:/home/loser:/bin/bash

(with no entry in /etc/shadow -- password is 'user' before you try
cracking it ;-)


IMO, with access to the backup file, there's two risks:

 - Modification (which CIS defends against) -- if admin ever reverts a backup 
file corrupted by an attacker, we could hit the above scenario or:
 - Brute-force (which CIS also defends against though as you pointed out, is a 
bit overkill).

What do I mean by the latter? CIS benchmark has a x-day password
rotation window with some complexity arguments on quality. If
/etc/passwd has any non-shadowed entries in it (e.g., from a _really_
old system that was fully upgraded or was manually added for whatever
reason), /etc/passwd- could be a source of leaking (potentially) old
passwords for these accounts and (if they're reused across the org or
indicative of a pattern by the owner) provide an attack vector for other
systems in the organization.

Regardless... that probably isn't a threat on a well-admin'd machine. :)


CIS has also relaxed this in later versions of the guide:

https://workbench.cisecurity.org/community/1/discussions/2821
https://workbench.cisecurity.org/tickets/5218
https://workbench.cisecurity.org/benchmarks/6800/tickets/5158



This is already addressed in CIS benchmark for Ubuntu 20.04 v1.0.0.

It is also corrected in the future (unreleased) version of 18.04 guidance:
https://workbench.cisecurity.org/sections/772680/recommendations/1262266

Until such benchmark is released, we can't switch to using that
guidance.

But it is coming :)

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923464] [NEW] ideally should boot rootfs from a matching hard drive

2021-04-12 Thread Dimitri John Ledkov
Public bug reported:

Ideally we should strive to boot rootfs from a matching hard drive.

I.e. if we are booting rootfs by UUID, we should try to find the one
that came from the same drive as where ESP (UEFI) came from, or u-boot
spl / u-boot got loaded from (loader1/loader2).

Such that for example, when booted from external usb stick, rootfs from
there is mounted.

Or when booted from internal drive whilst a dd backup is attached over
usb, rootfs is loaded from the internal drive not from the usb attached
backup.

This would need:

* u-boot to export the drive it loaded extlinux.conf / bootscript from,
and pass it on kernel command line

* grub to export the device UUID it got loaded from (from the
BootServices EFI table) and pass it on the kernel command line or via
runtime EFI variable

* sdboot already does that I believe, but not sure if initramfs-tools
consumes the sdboot provided information

* initramfs-tools to consume above and sort the discovered devices based
on that, when deciding what to mount as rootfs

** Affects: cloud-images
 Importance: Undecided
 Status: New

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

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

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

** Affects: u-boot (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: u-boot-menu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rls-ii-incoming

** Description changed:

  Ideally we should strive to boot rootfs from a matching hard drive.
  
  I.e. if we are booting rootfs by UUID, we should try to find the one
  that came from the same drive as where ESP (UEFI) came from, or u-boot
  spl / u-boot got loaded from (loader1/loader2).
  
  Such that for example, when booted from external usb stick, rootfs from
  there is mounted.
  
  Or when booted from internal drive whilst a dd backup is attached over
  usb, rootfs is loaded from the internal drive not from the usb attached
  backup.
  
  This would need:
  
  * u-boot to export the drive it loaded extlinux.conf / bootscript from,
  and pass it on kernel command line
  
  * grub to export the device UUID it got loaded from (from the
  BootServices EFI table) and pass it on the kernel command line or via
  runtime EFI variable
  
+ * sdboot already does that I believe, but not sure if initramfs-tools
+ consumes the sdboot provided information
+ 
  * initramfs-tools to consume above and sort the discovered devices based
  on that, when deciding what to mount as rootfs

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

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

** Also affects: u-boot (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: u-boot-menu (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Tags added: rls-ii-incoming

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

Title:
  ideally should boot rootfs from a matching hard drive

Status in cloud-images:
  New
Status in grub2 package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in u-boot package in Ubuntu:
  New
Status in u-boot-menu package in Ubuntu:
  New

Bug description:
  Ideally we should strive to boot rootfs from a matching hard drive.

  I.e. if we are booting rootfs by UUID, we should try to find the one
  that came from the same drive as where ESP (UEFI) came from, or u-boot
  spl / u-boot got loaded from (loader1/loader2).

  Such that for example, when booted from external usb stick, rootfs
  from there is mounted.

  Or when booted from internal drive whilst a dd backup is attached over
  usb, rootfs is loaded from the internal drive not from the usb
  attached backup.

  This would need:

  * u-boot to export the drive it loaded extlinux.conf / bootscript
  from, and pass it on kernel command line

  * grub to export the device UUID it got loaded from (from the
  BootServices EFI table) and pass it on the kernel command line or via
  runtime EFI variable

  * sdboot already does that I believe, but not sure if initramfs-tools
  consumes the sdboot provided information

  * initramfs-tools to consume above and sort the discovered devices
  based on that, when deciding what to mount as rootfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1923464/+subscriptions

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


[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2021-04-12 Thread andrea
Nothing to do for me. Ubuntu 20.10 HP spectre x360. 5.11.22 Kernel (no
microphone)

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

-- 
Mailing list: https://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 1923432] [NEW] apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Steve Beattie
This is https://gitlab.com/apparmor/apparmor/-/merge_requests/656
upstream, and was addressed in
https://gitlab.com/apparmor/apparmor/-/merge_requests/656/diffs?commit_id=2c2dbdc3a3012ce06371edc1e9be6f58711d8565
on the master branch and was cherrypicked to the apparmor 3.0 branch in
https://gitlab.com/apparmor/apparmor/-/commit/80efc15e18a6bb0d0abd2821cb03bf6be51cc517
This should be safe to cherrypick for hirsute.

(Similar cherrypicks occurred for prior AppArmor branches.)

-- 
Steve Beattie


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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-04-12 Thread Pierre-Antoine Champin
@Sebastien Sorry for the late reply.

I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.

How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file ./system/apt-daily.timer,
ensuring that it contained the RandomizedDelaySec directive.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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


[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

2021-04-12 Thread Alejandro
Hi Sebastian,

the patch set the job state to backend error.

I don't think openprinting is the right error here. The problem is in
the backend (the USB backend) when it's not possible to communicate with
a USB printer. This usually means that the printer is not connected.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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


[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

2021-04-12 Thread Sebastien Bacher
What's the status of the patch upstream? The cups reports mentioned
earlier got close asking to report to openprinting instead, did you do
that?

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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


[Touch-packages] [Bug 1922909] Re: Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820 X-series

2021-04-12 Thread Kai-Heng Feng
** Package changed: linux (Ubuntu) => e2fsprogs (Ubuntu)

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

Title:
  Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820
  X-series

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  Hi Team,

  Please be note Ubuntu ISO 18.04.5 not detecting the samsung PM981a SSD
  drive upon installation

  #nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev
    
 - -- 
 
  /dev/nvme0n1   S4UFNF0NC01090 PM981a NVMe SAMSUNG 2048GB  
 1 165.28  GB /   2.05  TB512   B +  0 B   15302229

  Please provide a fix in the next 18.05.6 ISO.

  Please note there is no uissue detecting in Ubuntu 20.04.2 ISO

  Thanks

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

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


[Touch-packages] [Bug 1923377] Re: Automatically installed systemd:i386 makes graphical boot hang

2021-04-12 Thread Dan Streetman
Sorry, providing a couple lines from the apt update history log isn't
enough for anyone to be able to analyze anything.

You can try attaching your full journal logs, and the full apt and dpkg
logs would help as well, but even the logs may not help and more
complete system configuration data may be needed.

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

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

Title:
  Automatically installed systemd:i386 makes graphical boot hang

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  2)
  systemd:i386 (245.4-4ubuntu3.6, automatic)
  systemd:amd64 (245.4-4ubuntu3.6, automatic)
  3)
  I expected that letting the system install/upgrade packages it suggested 
would cause no harm.
  4)
  Harm was caused. Graphical boot got stuck after the grub menu. But I could 
access virtual console be pressing alt-F1.

  I accepted the upgrade on Saturday, on Sunday, when tried to boot the
  machine, the machine hung up. I suspect that one of the problematic
  packages was systemd:i386. I have no idea why a 32bit version of this
  got installed, and other 32bit versions as well. I attached an excerpt
  from /var/log/apt/history.log showing the problematic upgrade.

  One of the results was that the binaries /usr/bin/systemctl and
  /lib/systemd/systemd were 32bit executables, and they could not load
  appropriate the pam modules (which were still 64bit). But as I could
  log in from the virtual terminal just fine, this showed that pam
  itself was working, systemd was the problem.

  After long struggle I managed to fix this by reinstalling systemd,
  which overwrote the above binaries with their 64bit versions. Removing
  systemd:i386 would have deleted systemd altogether. After that I
  purged various 32bit packages I suspected were causing problems. And I
  installed the packages removed by the upgrade on Saturday, such as
  snapd. Now the system boots up in graphical mode just fine.

  But why did the 32bit versions of systemd etc got installed
  automatically?

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

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


[Touch-packages] [Bug 1922909] [NEW] Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820 X-series

2021-04-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi Team,

Please be note Ubuntu ISO 18.04.5 not detecting the samsung PM981a SSD
drive upon installation

#nvme list
Node SN   Model
Namespace Usage  Format   FW Rev
   
- --  
/dev/nvme0n1   S4UFNF0NC01090 PM981a NVMe SAMSUNG 2048GB   
1 165.28  GB /   2.05  TB512   B +  0 B   15302229

Please provide a fix in the next 18.05.6 ISO.

Please note there is no uissue detecting in Ubuntu 20.04.2 ISO

Thanks

** Affects: e2fsprogs (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bionic
-- 
Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820 X-series
https://bugs.launchpad.net/bugs/1922909
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to e2fsprogs 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 1923437] [NEW] can't set 2560x1440 resolution after installing nvidia drivers

2021-04-12 Thread nikola
Public bug reported:

Hello !

I have 2 monitors 
1) one is 4K 
2) another one is FULLHD, 
when I installed lubuntu I had 4k monitor work at maximum 4k and another at 
fullhd , I want to change that 4k monitor to 2560x1440(2k). 

after install nvidia drivers there is no 2560x1440 resolution in
"monitor settings" resolutions tab like it was before installing
drivers. when trying to add it manually from xrandr, at some point it
gives me that error:

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  35
  Current serial number in output stream:  35

in short , I can't set monitor to 2560x1440. what it might be ?

--

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

Unable to locate package pkgname

3) What you expected to happen

have 2560x1440 resolution option after installing nvidia driver

4) What happened instead

have no 2560x1440 listed in "monitor settings" and can't even create it
manually from xrandr commands

Best Regard !

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.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  460.67  Thu Mar 11 00:11:45 
UTC 2021
 GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: LXQt
Date: Mon Apr 12 14:07:34 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150]
InstallationDate: Installed on 2021-04-12 (0 days ago)
InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-13-generic 
root=UUID=acd8d9c8-3bd0-4c68-9a02-19818e4cf3c3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2017
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: X99-DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd09/05/2017:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
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.10-3ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute resolution 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/1923437

Title:
  can't set 2560x1440 resolution after installing nvidia drivers

Status in xorg package in Ubuntu:
  New

Bug description:
 

[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

2021-04-12 Thread Per-Inge
Didn't get the log message about rfkill after boot this morning.
After update today I have systemd 247.3-3ubuntu3 installed.

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

Title:
  Failed to start Load/Save RF Kill Switch Status

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  When I boot the system I get these lög messages
  - Failed to start Load/Save RF Kill Switch Statu
  - A start job for unit systemd-rfkill.service has failed
  and with sender systemd-rfkil
  Read event structure of invalid size

  Also happens on an Ubuntu system on the same computer.

  System details

  p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
  System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
 Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804 
 date: 02/02/2021 
  CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB 
 Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 
2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 
 8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 
  Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
 v: kernel 
 Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa 
 resolution: 2560x1440~60Hz 
 OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 
  Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
 Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
 Sound Server: ALSA v: k5.11.0-11-generic 
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
 IF: wlp6s0 state: down mac:  
 Device-2: Realtek RTL8125 2.5GbE driver: r8169 
 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:  
 IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
 
 IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
 
  Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb 
 Report: ID: hci0 state: up running pscan bt-v: 3.0 address: 
 
  Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) 
 ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB 
 ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 
465.76 GiB 
 ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 
465.76 GiB 
  Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1 
  Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile 
  Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 
40.0 C 
 Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0 
  Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB 
(12.1%) Shell: Bash inxi: 3.3.01 
  p-i@pi-tuf-b550m-wifi:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Mar 29 10:12:21 2021
  InstallationDate: Installed on 2021-02-05 (51 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=d37b6e75-43a0-4e56-85c1-4a6ef8e1ffc9 ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  

[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2021-04-12 Thread jeremyszu
Although comment#2 is merged, this issue still needs PA corresponding
(https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290).

Therefore, we will deliver a special alsa-ucm-conf on our oem-archive as
short-term solution and leave it be replaced after this ticket gets the
merge.

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions

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


[Touch-packages] [Bug 1923432] [NEW] apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

2021-04-12 Thread Andrea Righi
Public bug reported:

It looks like /etc/apparmor/severity.db is missing the new capability
CAP_CHECKPOINT_RESTORE.

This causes the following regression test failure:

  ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
  make: *** [Makefile:81: check_severity_db] Error 1

This new capability is correctly supported by the parser already (see
d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
probably need to update severity.db as well.

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

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

** Also affects: apparmor (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Hirsute:
  New

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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


[Touch-packages] [Bug 1923406] Re: sslh 1.18-1 high CPU load -> Fix available

2021-04-12 Thread Balint Reczey
** Package changed: systemd (Ubuntu) => sslh (Ubuntu)

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

Title:
  sslh 1.18-1 high CPU load -> Fix available

Status in sslh package in Ubuntu:
  New

Bug description:
  System: Ubuntu 18.04 LTS 
  Software: sslh v1.18-1

  The Problem is that the sslh-daemon causes 100% load after a while.
  The bug seems to be reported and fixed in december 2020 at the the 
ssl-project.

  Should be fixed in v1.21b or newer. So please backport/update the
  package accordingly to fix the problem for everyone.

  See:
  https://github.com/yrutschle/sslh/issues/284

  And for the fix in code:
  
https://github.com/yrutschle/sslh/commit/1e33455fe76078d97ea4ce1c8b856df2dea64c71

  
  Workaround: We put a cronjob that kills/restarts sslhd every 3hours and after 
that we tried to update the binaries from source ourselves.

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

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


[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

2021-04-12 Thread Launchpad Bug Tracker
This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1~20.04.1

---
libseccomp (2.5.1-1ubuntu1~20.04.1) focal; urgency=medium

  * Updated to new upstream 2.5.1 version for updated syscalls support
(LP: #1891810)
   - Removed the following patches that are now included in the new version:
 + d/p/cython3.patch
 + d/p/riscv64_support.patch
 + d/p/fix-aarch64-syscalls.patch
 + d/p/db-consolidate-some-of-the-code-which-adds-rules.patch
 + d/p/db-add-shadow-transactions.patch
   - Deleted the patch to add a local copy of architecture specific header
 files from linux-libc-dev/focal as this is not needed anymore
 + d/p/add-5.4-local-syscall-headers.patch
   - debian/control: Added gperf to Build-Depends as this is now required
 by upstream
   - debian/libseccomp2.symbols: Added new symbols
  * Add system call headers for powerpc required for backport to xenial
- d/p/add-5.8-powerpc-syscall-headers.patch

 -- Alex Murray   Mon, 01 Mar 2021 13:47:46
+1030

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

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in libseccomp source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

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

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


[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

2021-04-12 Thread Łukasz Zemczak
For bionic there's a few ADT regressions for libseccomp - I re-ran them,
let's see if they pass now.

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in libseccomp source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-12 Thread Sebastien Bacher
@William, thanks, could you share the Debian bug url? I browsed
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=bluez
but I'm not finding it...

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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


[Touch-packages] [Bug 1923421] [NEW] Can't change ImageMagick as a default application for opening PDF

2021-04-12 Thread Wiktor Nizio
Public bug reported:

I have ImageMagick set as the default application for opening PDF. I am
trying to change the setting, but it doesn't work.

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

Title:
  Can't change ImageMagick as a default application for opening PDF

Status in Ubuntu:
  New

Bug description:
  I have ImageMagick set as the default application for opening PDF. I
  am trying to change the setting, but it doesn't work.

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

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


[Touch-packages] [Bug 1923406] [NEW] sslh 1.18-1 high CPU load -> Fix available

2021-04-12 Thread muelmanu
Public bug reported:

System: Ubuntu 18.04 LTS 
Software: sslh v1.18-1

The Problem is that the sslh-daemon causes 100% load after a while.
The bug seems to be reported and fixed in december 2020 at the the ssl-project.

Should be fixed in v1.21b or newer. So please backport/update the
package accordingly to fix the problem for everyone.

See:
https://github.com/yrutschle/sslh/issues/284

And for the fix in code:
https://github.com/yrutschle/sslh/commit/1e33455fe76078d97ea4ce1c8b856df2dea64c71


Workaround: We put a cronjob that kills/restarts sslhd every 3hours and after 
that we tried to update the binaries from source ourselves.

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


** Tags: bug cpuload fixed sslh

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

Title:
  sslh 1.18-1 high CPU load -> Fix available

Status in systemd package in Ubuntu:
  New

Bug description:
  System: Ubuntu 18.04 LTS 
  Software: sslh v1.18-1

  The Problem is that the sslh-daemon causes 100% load after a while.
  The bug seems to be reported and fixed in december 2020 at the the 
ssl-project.

  Should be fixed in v1.21b or newer. So please backport/update the
  package accordingly to fix the problem for everyone.

  See:
  https://github.com/yrutschle/sslh/issues/284

  And for the fix in code:
  
https://github.com/yrutschle/sslh/commit/1e33455fe76078d97ea4ce1c8b856df2dea64c71

  
  Workaround: We put a cronjob that kills/restarts sslhd every 3hours and after 
that we tried to update the binaries from source ourselves.

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

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


[Touch-packages] [Bug 1923167] Re: Screen flickering- QHD Benq

2021-04-12 Thread Daniel van Vugt
Please try a different cable. If that doesn't solve the problem then
please run these commands:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt
  xrandr --verbose > xrandr.txt

and attach the resulting text files here.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Incomplete

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

Title:
  Screen flickering- QHD Benq

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  The Display continuously flickers when we are using the Displayport 
connection with QHD (2560x1440) Benq-Monitors.
  The affected Hardware is:
  Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx)

  Using a DP to HDMI-Adapter solves the problem with the given resolution. 
  This error occurs in both Ubuntu Releases 18.04 and 20.10.

  This is what we see in the Logs:

  [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795
  [27.144] (II) AMDGPU(0): Using hsync ranges from config file
  [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file
  [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
  [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 
2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 
2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056 
 600 601 605 628 +hsync +vsync (37.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152 
 624 625 628 667 -hsync -vsync (49.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056 
 600 601 604 625 +hsync +vsync (46.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 
1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 
1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
  [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked
  [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923167/+subscriptions

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

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

2021-04-12 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When I login into Gnome or Plasma, the screen is soon freezed (it
  seems that Linux keeps doing something, however). Gnome Wayland is not
  affected.

  This is after I moved my system to a new computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  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: Mon Apr 12 07:37:00 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415]
  InstallationDate: Installed on 2018-06-23 (1023 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
   |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
  MachineType: Acer TravelMate P215-52
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog:
   
  dmi.bios.date: 07/29/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BassDrum_CM
  dmi.board.vendor: CML
  dmi.board.version: V1.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: TravelMate P2
  dmi.product.name: TravelMate P215-52
  dmi.product.sku: 
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend

2021-04-12 Thread Daniel van Vugt
Thanks for the bug report. I can see two immediate problems.

The first problem isn't really related to this bug but you should fix it
anyway. Your log is being flooded by crashes in 'onedrive'. If you don't
need 'onedrive' then consider uninstalling it.

The second problem is these messages in your Xorg logs which might be
related to this bug:

[ 87005.338] [dix] EventToCore: Not implemented yet 
[ 87131.437] [dix] EventToCore: Not implemented yet 
[ 87283.009] [dix] EventToCore: Not implemented yet 

Next we would like to see a system log of the problem happening so
please:

1. Reproduce the bug again such that the machine is unresponsive.

2. Wait 30 seconds.

3. Do a "hard reboot".

4. Run:

   journalctl -b-1 > prevboot.txt

5. Attach the resulting text file here.

6. Follow these instructions to check for crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Summary changed:

- regression: no display when waking from suspend
+ [Lenovo ThinkPad T450s] regression: no display when waking from suspend

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: multimonitor

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

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

Title:
  [Lenovo ThinkPad T450s] regression: no display when waking from
  suspend

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have two Lenovo T450s laptops running Ubuntu 20.10.
  A few weeks ago, suspend stopped working properly: with an external monitor, 
the external monitor no longer registers the connection when waking from 
suspend.
  Without, the laptop screen is black and the machine unresponsive until 
hard-rebooted, when waking from suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 11 17:53:01 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (808 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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-server/+bug/1923381/+subscriptions

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

[Touch-packages] [Bug 1923333] Re: Benq G610HDA not being detected

2021-04-12 Thread Daniel van Vugt
Thanks for the bug report. It appears the Nvidia Xorg driver has not
been installed properly so any display plugged into the Nvidia GPU won't
be detected. Please try uninstalling and then reinstalling the Nvidia
driver using the 'Additional Drivers' app.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Incomplete

** Description changed:

- My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable,
+ My monitor Benq G610HDA is not being detected by Ubuntu. Good VGA Cable,
  still Unknown display
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04: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  460.39  Thu Jan 21 21:54:06 
UTC 2021
-  GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
+  GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 11 13:13:18 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
-  nvidia, 460.39, 5.8.0-48-generic, x86_64: installed
-  v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed
-  v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
+  nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
+  nvidia, 460.39, 5.8.0-48-generic, x86_64: installed
+  v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed
+  v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d]
-Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d]
+    Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d]
  InstallationDate: Installed on 2021-02-08 (61 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  MachineType: ASUSTeK COMPUTER INC. X455LB
  ProcEnviron:
-  LANGUAGE=en_PH:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_PH.UTF-8
-  SHELL=/bin/zsh
+  LANGUAGE=en_PH:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_PH.UTF-8
+  SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=def1bb03-4353-441e-b107-29aaf5b72e17 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LB.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX455LB.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X455LB
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: 

[Touch-packages] [Bug 1923318] Re: Ubuntu does not detect video output devices

2021-04-12 Thread Daniel van Vugt
Please also run these commands:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt
  xrandr --verbose > xrandr.txt
  grep . /sys/class/drm/*/status > kernelconn.txt
  grep . /sys/class/drm/*/modes > kernelmodes.txt

and attach the resulting text files here.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Ubuntu does not detect video output devices

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Firstly I'd like to apologize as I am a novice Ubuntu user and I am
  unsure as to which information I should include within this report.

  That being said,

  I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu:
  radeon rx6800.

  Ubuntu is detecting default display at correct resolution, which is
  connected via DisplayPort on rx6800 gpu. However, my second monitor,
  LGCX 4k OLED connected via HDMI is not detected in display properties
  window.

  xrandr does not detect outputs other than default display.

  I have run apt-get update and apt-get upgrade, restarted, unplugged
  and plugged displays back in, tried installing amd-gpu drivers
  separately which were downloaded from official website, i have tried
  updating kernal, along with many other troubleshooting strategies.

  I believe this to be some sort of software issue.

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

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


[Touch-packages] [Bug 1923233] Re: Computer is very slow

2021-04-12 Thread Daniel van Vugt
Thanks for the bug report. I can't see anything broken so can you
explain exactly what is slow (and what isn't)?

Please also open a Terminal window and run 'top'. How much CPU is used
while the computer is slow?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Computer is very slow

Status in Ubuntu:
  Incomplete

Bug description:
  Lap Top Computer is very slow

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   [  OK  ] Started Manage, Install and Generate Color 
Profiles.
   [  OK  ] Started GNOME Display Manager.
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr  9 12:49:55 2021
  DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
  InstallationDate: Installed on 2018-02-18 (1145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP Laptop 15-bw0xx
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago)
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8330
  dmi.board.vendor: HP
  dmi.board.version: 27.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bw0xx
  dmi.product.sku: 1GR30LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Tue Nov 20 10:27:42 2018
  xserver.configfile: default
  xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: amdgpu

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

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