Re: [Touch-packages] [ext] [Bug 1953720] Re: OSError: [Errno 30] Read-only file system: '/var/crash/...

[Ralf Hildebrandt]

* Benjamin Drung <1953...@bugs.launchpad.net>:
> I still fail to understand what went wrong there. /var/crash has correct
> permission to write to. In case of permission errors, the error should
> say PermissionError (errno 13 IIRC), but the failure message says "Read-
> only file system".
> 
> Can you paste the content of /proc/mounts?

# cat /proc/mounts 
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs
rw,nosuid,noexec,relatime,size=32868660k,nr_inodes=8217165,mode=755,inode64
0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs
rw,nosuid,nodev,noexec,relatime,size=6577308k,mode=755,inode64 0 0
/dev/sda1 / ext4 rw,relatime,errors=remount-ro,stripe=64 0 0
securityfs /sys/kernel/security securityfs
rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,inode64 0 0
tmpfs /run/lock tmpfs
rw,nosuid,nodev,noexec,relatime,size=5120k,inode64 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755,inode64 0 0
cgroup2 /sys/fs/cgroup/unified cgroup2
rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup
rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
none /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
cgroup /sys/fs/cgroup/cpuset cgroup
rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/freezer cgroup
rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/perf_event cgroup
rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/memory cgroup
rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup
rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/blkio cgroup
rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma
0 0
cgroup /sys/fs/cgroup/hugetlb cgroup
rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/misc cgroup rw,nosuid,nodev,noexec,relatime,misc
0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids
0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs
rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22944
0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/debug/tracing tracefs
rw,nosuid,nodev,noexec,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl
rw,nosuid,nodev,noexec,relatime 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /run/user/0 tmpfs
rw,nosuid,nodev,relatime,size=6577304k,mode=700,inode64 0 0

> What happens if you try to create a file in /var/crash? E.g. run
> 
> touch /var/crash/testcase.crash
> 
> I would expect that to work.

# touch /var/crash/testcase.crash
# ls -l /var/crash/testcase.crash
-rw-r--r-- 1 root root 0 Jul 27 08:21 /var/crash/testcase.crash

-- 
Ralf Hildebrandt
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netzwerk

Campus Benjamin Franklin (CBF)
Haus I | 1. OG | Raum 105
Hindenburgdamm 30 | D-12203 Berlin

Tel. +49 30 450 570 155
ralf.hildebra...@charite.de
https://www.charite.de

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

Title:
  OSError: [Errno 30] Read-only file system: '/var/crash/...

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call 
last):
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
408, in 
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: main()
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
152, in main
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, 
servers, config):
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
239, in check
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, 
mock_runner, servers)
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
262, in send_digest
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, 
servers[0], digested)
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
253, in _send_digest
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, 
(digested, server))
  Dec  6 12:02:3

[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

[Timothy Quinn]

Confirmed with Ubuntu desktop 20.04.1, fully updated. Now seeing if this
can be resolved by upgrading to newer version of nginx using:
https://www.linuxbabe.com/security/modsecurity-nginx-debian-ubuntu

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

Title:
  libperl.so.5.30.0 causes nginx to segfault

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]

  1) launch a focal container
  $ lxc launch images:ubuntu/focal focal-1897561
  2) enter the container
  $ lxc shell focal-1897561
  3) install libnginx-mod-http-perl
  # apt-get install -y nginx-core libnginx-mod-http-perl
  4) check nginx journal
  # journalctl -fu nginx &
  5) reload nginx 2-3 times
  # systemctl reload nginx

  Eventually you will see this from the journal:

  Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web 
server and a reverse proxy server.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 
'core-dump'.

  [Workaround]

  If libnginx-mod-http-perl is not needed, purging it and restarting
  nginx sidesteps the problem.

  [Original bug description]

  Ubuntu 20.04 LTS

  Looks that Perl 5.30 has bug that causes nginx to die, usually occurs
  after "service nginx reload"

  This looks like nginx, but it really is perl issue:
  https://github.com/Perl/perl5/issues/17154

  Fix done in 5.32 (Perl5 commit bf0) and people are asking backport
  to 5.30 to get fix also to nginx.

  Error:
  Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 
ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in 
libperl.so.5.30.0[7fbf321a5000+166000]

  Symptom: Nginx terminates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: perl 5.30.0-9build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal uec-images
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Lenin]

it appears the phased updates only get installed if sources.list also
has proposed repos, without them, it's all fine. sorry for the noise

** Changed in: apt (Ubuntu)
   Status: Incomplete => 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/1981672

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

** Description changed:

  [Impact]
  
-  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
-  * The GIF loader runs out of memory with specifically crafted files
+  * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer limit.
  
-  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.
  
-  * Or, in other ways, bad gif files in other applications can open the
+  * Or, in other ways, bad gif files in other applications can open the
  door for exploits.
  
-  * Any app using gdk-pixbuf is affected, mainly file managers and image
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
  viewers.
  
  [Test Plan]
  
-  * Take the POC's - they can be found in the issue in the GNOME repo
+  * Take the POC's - they can be found in the issue in the GNOME repo
  
-  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
-  - Nautilus, GNOME's file manager
-  - Nemo, Cinnamon's file manager
-  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
-  - PCManFM, LXDE's file manager which straight up crashes
-  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
+  - Eye of GNOME (eog) triggers the segfault in syslog
  
-  * If you or the system couldn't tell something is wrong, cat
+  * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.
  
  [Where problems could occur]
  
-  * The patch itself is simple, but since gdk-pixbuf is often used with
+  * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.
  
-  * It is possible, and has happened in the past (which has been patched)
+  * It is possible, and has happened in the past (which has been patched)
  that other bad GIFs can cause other crashes.
  
-  * That patch is essentially overflow checks -  changes with GLib
+  * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems
  
-  * Other failures to properly handle GIFs and broken or intentionally
+  * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs
  
  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.
  
  [Other Info]
-  
-  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
-  * Files attached are examples or crashes
-  * Again, all apps using gdk-pixbuf are affected
-  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
-  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
+ 
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

** Description changed:

- There is a buffer overwrite in gdk-pixbuf. I will eventually create a
- whole SRU document with how to reproduce and all, but I'll just say it
- is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
- causes the entire system to run out of memory. (With firefox, 1612/3922
- MB - which says something.)
+ [Impact]
  
- It may be possible all apps using gdk-pixbuf can have a problem handling
- files like the PoC.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
- https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
+  * The GIF loader runs out of memory with specifically crafted files
+ with bad frame data (and images with its sizes) over the integer limit.
+ 
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+ RAM systems like my old iMac, the system can completely run out of
+ memory.
+ 
+  * Or, in other ways, bad gif files in other applications can open the
+ door for exploits.
+ 
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
+ viewers.
+ 
+ [Test Plan]
+ 
+  * Take the POC's - they can be found in the issue in the GNOME repo
+ 
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+ 
+  * If you or the system couldn't tell something is wrong, cat
+ /var/log/syslog and enjoy the segfaults or out of memory warnings or
+ even kernel spam.
+ 
+ [Where problems could occur]
+ 
+  * The patch itself is simple, but since gdk-pixbuf is often used with
+ GTK apps a mistake here could be problematic.
+ 
+  * It is possible, and has happened in the past (which has been patched)
+ that other bad GIFs can cause other crashes.
+ 
+  * That patch is essentially overflow checks -  changes with GLib
+ (GNOME's, not to be confused with glibc) and the functions used in not
+ only the patch but all of gdk-pixbuf can cause problems
+ 
+  * Other failures to properly handle GIFs and broken or intentionally
+ tampered GIFs can continue and always will open the door for security
+ holes for other bugs
+ 
+ * Again, overall a simple patch but as long as the GIFs remain handled
+ properly, and no changes to the GLib functions are made and to other
+ apps that use gdk-pixbuf (and assuming are not affected by the change
+ and still work), the patch does not have much regression potential.
+ 
+ [Other Info]
+  
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

Here's proposal focal patch - I noticed some whitespaces but those are
in the code and not introduced by me.

** Patch added: "Proposed focal patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605438/+files/gdk-pixbuf_2.40.0+dfsg-3ubuntu0.3.debdiff

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => In Progress

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

PCManFM crashed to this.

that's my last POC - I'm going to create the patch

** Attachment added: "pcmanfmcrash.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605437/+files/pcmanfmcrash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

Thunar, which uses tumbler for thumbnailing, produced a crash.

** Attachment added: "Tumbler (xfce thumbnailer crash)"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605436/+files/libgdkpixbufloader-gif-crash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

Here is what it did to my iMac.

** Attachment added: "OldiMacSyslog"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605435/+files/OldiMacSyslog

** Changed in: gdk-pixbuf (Ubuntu)
 Assignee: (unassigned) => Joshua Peisach (itzswirlz)

** Tags removed: jammy
** Tags added: bionic xenial

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] [NEW] CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Joshua Peisach]

*** This bug is a security vulnerability ***

Public security bug reported:

There is a buffer overwrite in gdk-pixbuf. I will eventually create a
whole SRU document with how to reproduce and all, but I'll just say it
is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
causes the entire system to run out of memory. (With firefox, 1612/3922
MB - which says something.)

It may be possible all apps using gdk-pixbuf can have a problem handling
files like the PoC.

https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Tue Jul 26 19:33:41 2022
InstallationDate: Installed on 2021-11-24 (244 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
SourcePackage: gdk-pixbuf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Assignee: Joshua Peisach (itzswirlz)
 Status: New


** Tags: amd64 apport-bug bionic focal xenial

** Information type changed from Private Security to Public Security

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

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[Robie Basak]

> ...it has basically no impact on our own applications...

Just because you and I can't find a case that would break doesn't mean
there isn't one. So there's risk. And I think the consequences, because
of the nature of this package, could be quite large.

> I'm not particularly keen on doing this SRU just for the sake of 1/,
and 2/ can be fixed in that package, but do we want to break things for
3/ ?

We'll have to break it at some point, right? Otherwise the configuration
file format in /etc could never move on. A new release would be the
appropriate time, as has happened in Jammy. So now seems a good a time
as any, given that it's already happened, and it requires effort and
risk to reverse it.

Upstream NodeJS should be able to release a fixed version themselves. In
fact I believe it's the norm for external software sources to have to
adjust themselves for new distribution releases anyway. Is there any
reason this isn't acceptable to them?

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:

[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU

[sefs]

I have been monitoring the same issue for months. But have not been able to 
identify the root cause.
Worst yet it not only affects my system but also my router.

The dnsmasq goes to 100%cpu and somehow forces my pfsense to also begin to 
consume 100%cpu
if i kill dnsmasq then the router comes back to normal.

Please send help.

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

Title:
  dnsmasq often using 100% of CPU

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Release:  22.04
  Codename: jammy
  Kernel: Linux 5.15.0-40-generic x86_64

  ⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1

  dnsmasq is caught in a loop after every dns request, resulting in 100%
  CPU usage for several minutes each time.  This leads to a hot and
  lethargic computer.  During this time thousands of the following
  messages (see below) are printed from strace.

  The loop tends to obsess on denied connections, but there are so many
  I'm not 100% sure.

  systemd-resolved is _not_ running, some bugs refer to that.

  ⏵ head /etc/dnsmasq.d/foo.conf

  address=/#/127.0.0.2
  port=53
  resolv-file=/var/run/NetworkManager/resolv.conf

  ⏵ sudo strace -p 3519  (dnsmasq)

  poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
  events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
  events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
  events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])

  recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
  sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
  msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
  client\10ser"..., iov_len=4096}], msg_iovlen=1,
  msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
  cmsg_data={ipi_ifindex=if_nametoindex("lo"),
  ipi_spec_dst=inet_addr("127.0.0.53"),
  ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
  0) = 54

  ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0

  sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
  54, 0, {sa_family=AF_INET, sin_port=htons(53),
  sin_addr=inet_addr("127.0.0.53")}, 16) = 54

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


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

[Touch-packages] [Bug 1958019]

[baipush]

Hello everybody

I can confirm it works for me too (thx Gervasio for pushing forward on
me :) ).

How do we get the patches for all these different Lenovo models that
have been touched in this thread into the original Kernel so that
everybody can have them by default when installing their favorite
distro?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1925348] Re: stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

[Jeffrey Hawkins]

What is the status of this CVE with Ubuntu Jammy?  This was fixed in the
upstream in January/February 2022,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99935#c11

** Bug watch added: GCC Bugzilla #99935
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99935

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

Title:
  stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  stack-overflowon GNU libiberty/rust-demangle.c:664 demangle_path when
  we run ./cxxfilt ./crashs/poc

  ./crash/poc:�@}@�^_RB_RB999IRB�RBRB

  ==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 
(pc 0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0)
  #0 0x6a3330 in demangle_path rust-demangle.c:664
  #1 0x6a3bd1 in demangle_path rust-demangle.c:774
  #2 0x6a3bd1 in demangle_path rust-demangle.c:774
  #3 0x6a3bd1 in demangle_path rust-demangle.c:774
  #4 0x6a3bd1 in demangle_path rust-demangle.c:774
  #5 0x6a3bd1 in demangle_path rust-demangle.c:774
  #6 0x6a3bd1 in demangle_path rust-demangle.c:774
  #7 0x6a3bd1 in demangle_path rust-demangle.c:774
  #8 0x6a3bd1 in demangle_path rust-demangle.c:774
  #9 0x6a3bd1 in demangle_path rust-demangle.c:774
  #10 0x6a3bd1 in demangle_path rust-demangle.c:774
  #11 0x6a3bd1 in demangle_path rust-demangle.c:774
  #12 0x6a3bd1 in demangle_path rust-demangle.c:774
  #13 0x6a3bd1 in demangle_path rust-demangle.c:774
  #14 0x6a3bd1 in demangle_path rust-demangle.c:774
  #15 0x6a3bd1 in demangle_path rust-demangle.c:774
  #16 0x6a3bd1 in demangle_path rust-demangle.c:774
  #17 0x6a3bd1 in demangle_path rust-demangle.c:774
  #18 0x6a3bd1 in demangle_path rust-demangle.c:774
  #19 0x6a3bd1 in demangle_path rust-demangle.c:774
  #20 0x6a3bd1 in demangle_path rust-demangle.c:774
  #21 0x6a3bd1 in demangle_path rust-demangle.c:774
  #22 0x6a3bd1 in demangle_path rust-demangle.c:774
  #23 0x6a3bd1 in demangle_path rust-demangle.c:774
  #24 0x6a3bd1 in demangle_path rust-demangle.c:774
  #25 0x6a3bd1 in demangle_path rust-demangle.c:774
  #26 0x6a3bd1 in demangle_path rust-demangle.c:774
  #27 0x6a3bd1 in demangle_path rust-demangle.c:774
  #28 0x6a3bd1 in demangle_path rust-demangle.c:774
  #29 0x6a3bd1 in demangle_path rust-demangle.c:774
  #30 0x6a3bd1 in demangle_path rust-demangle.c:774
  #31 0x6a3bd1 in demangle_path rust-demangle.c:774
  #32 0x6a3bd1 in demangle_path rust-demangle.c:774
  #33 0x6a3bd1 in demangle_path rust-demangle.c:774
  #34 0x6a3bd1 in demangle_path rust-demangle.c:774
  #35 0x6a3bd1 in demangle_path rust-demangle.c:774
  #36 0x6a3bd1 in demangle_path rust-demangle.c:774
  #37 0x6a3bd1 in demangle_path rust-demangle.c:774
  #38 0x6a3bd1 in demangle_path rust-demangle.c:774
  #39 0x6a3bd1 in demangle_path rust-demangle.c:774
  #40 0x6a3bd1 in demangle_path rust-demangle.c:774
  #41 0x6a3bd1 in demangle_path rust-demangle.c:774
  #42 0x6a3bd1 in demangle_path rust-demangle.c:774
  #43 0x6a3bd1 in demangle_path rust-demangle.c:774
  #44 0x6a3bd1 in demangle_path rust-demangle.c:774
  #45 0x6a3bd1 in demangle_path rust-demangle.c:774
  #46 0x6a3bd1 in demangle_path rust-demangle.c:774
  #47 0x6a3bd1 in demangle_path rust-demangle.c:774
  #48 0x6a3bd1 in demangle_path rust-demangle.c:774
  #49 0x6a3bd1 in demangle_path rust-demangle.c:774
  #50 0x6a3bd1 in demangle_path rust-demangle.c:774
  #51 0x6a3bd1 in demangle_path rust-demangle.c:774
  #52 0x6a3bd1 in demangle_path rust-demangle.c:774
  #53 0x6a3bd1 in demangle_path rust-demangle.c:774
  #54 0x6a3bd1 in demangle_path rust-demangle.c:774
  #55 0x6a3bd1 in demangle_path rust-demangle.c:774
  #56 0x6a3bd1 in demangle_path rust-demangle.c:774
  #57 0x6a3bd1 in demangle_path rust-demangle.c:774
  #58 0x6a3bd1 in demangle_path rust-demangle.c:774
  #59 0x6a3bd1 in demangle_path rust-demangle.c:774
  #60 0x6a3bd1 in demangle_path rust-demangle.c:774
  #61 0x6a3bd1 in demangle_path rust-demangle.c:774
  #62 0x6a3bd1 in demangle_path rust-demangle.c:774
  #63 0x6a3bd1 in demangle_path rust-demangle.c:774
  #64 0x6a3bd1 in demangle_path rust-demangle.c:774
  #65 0x6a3bd1 in demangle_path rust-demangle.c:774
  #66 0x6a3bd1 in demangle_path rust-demangle.c:774
  #67 0x6a3bd1 in demangle_path rust-demangle.c:774
  #68 0x6a3bd1 in demangle_path rust-demangle.c:774
  #69 0x6a3bd1 in demangle_path rust-demangle.c:774
  #70 0x6a3bd1 in demangle_path rust-demangle.c:774
  #71 0x6a3bd1 in demangle_path rust-demangle.c:774
  #72 0x6a3bd1 in demangle_path rust-demangle.c:774
  #73 0x6a3bd1 in demangle_path rust-demangl

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/openssh/+git/openssh/+merge/427460

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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

[Touch-packages] [Bug 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory

[Andreas Hasenack]

I tried the same set of patches on jammy's cyrus-sasl (2.1.27). They
applied, but I couldn't get gssapi + ldaps to work against AD 2016. It
kept complaining that the channel binding token was not there. Weird. I
then tried fedora 36, and centos 9, which I thought were the "benchmark"
for this, but they also do not work against this AD 2016 server. Just
kinetic with the patched 2.1.28 cyrus-sasl2. Maybe just proper RHEL
works?

I'm confused.

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

Title:
  Missing channel binding prevents authentication to ActiveDirectory

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  > Are you uncertain if your issue is really a bug?
  Effect is an authentication error. Root case is a "missing feature" (see 
below) and requires updating dependencies, downporting.

  > If you are certain this is a bug please include the source package the bug 
is in.
  It's in the interaction between three libraries: openldap, cyrus-sasl, krb5

  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Broken in 18.04 and also in 20.10 (I guess it's also broken in anything 
inbetween)

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

  libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1
  ldap-utils: 2.4.53+dfsg-1ubuntu1.2
  libgssapi-krb5-2: 1.17-10ubuntu0.1

  > 3) What you expected to happen
  # kinit
  $ export LDAPSASL_CBINDING=tls-endpoint
  $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps://
  SASL/GSSAPI authentication started
  SASL username: 
  SASL SSF: 0
  u:

  > 4) What happened instead
  SASL/GSSAPI authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-0C090597, comment: 
AcceptSecurityContext error, data 80090346, v4563

  
  ---

  
  Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends 
activating this as a required feature. See 
https://access.redhat.com/articles/4661861
  Authentication to any AD DC which has mandatory channel binding fails.

  Channel binding requires at least an update to cyrus-sasl, which is
  not in any release as far as I can see:

  https://github.com/cyrusimap/cyrus-
  sasl/commit/975edbb69070eba6b035f08776de771a129cfb57

  
  It also needs this commit in openldap:

  
https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6

  Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5).

  
  RH also mentions it needs up-to-date krb5 libraries, but I can't tell what 
minimum version this needs.

  
  I can build all libraries from source, current master (except for krb5 where 
I've used 1.18.3) and can confirm that channel binding works when using those 
libraries.

  
  I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I 
would guess by extension also SSSD and realmd.

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


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

[Touch-packages] [Bug 1977710] Re: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

[Bug Watch Updater]

** Changed in: adduser (Debian)
   Status: New => Fix Released

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

Title:
  /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

Status in adduser package in Ubuntu:
  Triaged
Status in adduser package in Debian:
  Fix Released

Bug description:
  Since version 3.121ubuntu1 adduser's postinst script creates
  /etc/adduser.conf.dpkg-save file on debootstrap's root filesystem,
  that is, even when /etc/adduser.conf doesn't exist prior to package
  installation.

  Because of the change below the postinst script changes packaged
  /etc/adduser.conf and creates /etc/adduser.conf.dpkg-save as a backup:

- Enable private home directories by default (LP: #48734)
  + Set DIR_MODE=0750 in the default adduser.conf
  + Change the description and default value to select private home
directories by default in debconf template
  + Change the DIR_MODE when private home directories is configured via
debconf from 0751 to 0750 to ensure files are truly private

  The .dpkg-save file shouldn't be present on debootstrapped system.

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


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

[Touch-packages] [Bug 1982885] [NEW] Firefox does not scroll with touch input

[Matthew Lovibond]

Public bug reported:

Firefox does not scroll with the usual touch gesture of swiping up or
down on the screen. This action just selects text on the page as though
the left mouse button was depressed and the cursor moved across the
page.

lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

Snapstore version 103.0-1 latest stable

Possibly related to being packaged as a snap (have noticed this
behaviour on Fedora using the firefox snap).

It's still possible to scroll by dragging the scrollbar but this
essentially breaks firefox on touch systems

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

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

** No longer affects: systemd (Ubuntu)

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

Title:
  Firefox does not scroll with touch input

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox does not scroll with the usual touch gesture of swiping up or
  down on the screen. This action just selects text on the page as
  though the left mouse button was depressed and the cursor moved across
  the page.

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Snapstore version 103.0-1 latest stable

  Possibly related to being packaged as a snap (have noticed this
  behaviour on Fedora using the firefox snap).

  It's still possible to scroll by dragging the scrollbar but this
  essentially breaks firefox on touch systems

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Launchpad Bug Tracker]

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

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

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/openssh/+git/openssh/+merge/427455

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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

[Touch-packages] [Bug 1973032] Re: Can't report a bug anymore

[Johannes Mages]

Hi Benjamin!

Sorry I forgot to close this case. The issue is gone. The main repo was
accidentally kicked out and Ubuntu hadn't update properly. After I re-
checked the main repo it's gone. Thank you!

** Changed in: apport (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: apport (Ubuntu)
   Status: Opinion => Incomplete

** Changed in: apport (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Can't report a bug anymore

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Hi guy's!

  I got some GPU lock-ups or freezes today an last weekend and want to
  report it (x-org). But every time I go through ubuntu-bug it says at
  the end, that the bug can't be reported because it isn't a official
  release and I have to uninstall all 3rd party packages first.

  I have no idea what's wrong. I'm using Ubuntu 20.04.3 LTS with Kernel
  5.4.0-97-generic and the latest Nvidia 510.60.02 GPU driver.

  If you need some more informations please tell me.

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/openssh/+git/openssh/+merge/427453

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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

[Touch-packages] [Bug 1981697] Re: KDC: weak crypto in default settings

[Andreas Hasenack]

** Tags added: bitesize server-todo

** Also affects: krb5 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  KDC: weak crypto in default settings

Status in krb5 package in Ubuntu:
  Confirmed
Status in krb5 source package in Jammy:
  Triaged
Status in krb5 package in Debian:
  Fix Released

Bug description:
  Default setting in /etc/krb5kdc/kdc.conf, as installed from krb5-kdc in 
Ubuntu 22.04 Server:
  master_key_type = des3-hmac-sha1

  3DES was deprecated by NIST in 2017, i.e. give years ago! Reference:
  https://csrc.nist.gov/News/2017/Update-to-Current-Use-and-Deprecation-
  of-TDEA . This should not be a default since a very long time, and
  particularly not for new installations. If a compatibility with out-
  of-date installations is necessary, this should be explicitly made be
  the administrator.

  SHA-1 was deprecated as well, in 2011, i.e. eleven years ago!
  Reference:
  https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-131a.pdf
  .

  A reasonable default would probably be:
  master_key_type = aes256-cts-hmac-sha384-192

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: krb5-kdc 1.19.2-2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 14 12:34:22 2022
  InstallationDate: Installed on 2022-05-30 (45 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: krb5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

[Sami Pietila]

I found an old printer certificate from /etc/cups/ssl/ folder. Deleting
the certificate made cups to download the new one from printer and now
printing seems to work. Perhaps cups does not update the certificates.

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[Manfred Hampl]

I tested the updated package on my system and I can confirm that the new
version now correctly shows the apt keys. Other actions in software-
properties-gtk like changing the repository server and disabling
-proposed still work as before.

For the autopkgtest regression that has been reported in comment #21:
This seems to be caused by a transient network hickup, see relevant output from 
the log below:

Ign:1 http://ddebs.ubuntu.com jammy-updates/main arm64 
linux-image-unsigned-5.15.0-41-generic-dbgsym arm64 5.15.0-41.44
Err:1 http://ddebs.ubuntu.com jammy-updates/main arm64 
linux-image-unsigned-5.15.0-41-generic-dbgsym arm64 5.15.0-41.44
  Error reading from server. Remote end closed connection [IP: 185.125.190.18 
80]
Fetched 17.3 kB in 25min 53s (11 B/s)
E: Failed to fetch 
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-unsigned-5.15.0-41-generic-dbgsym_5.15.0-41.44_arm64.ddeb
  Error reading from server. Remote end closed connection [IP: 185.125.190.18 
80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
autopkgtest [14:56:44]: test live: ---]
live FAIL non-zero exit status 100

I assume that re-running the autopkgtest will show that this is no regression 
in the package.
In my opinion verification has succeeded, but due to the autopkgtest failure 
report I do not dare to change the tags accordingly.

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[Simon Chopin]

** Description changed:

- [Impact] 
- While the default configuration works fine for every package that uses the 
system libssl3, any software that uses libssl1.1, either separately packaged 
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive) 
will fail to load the configuration as they don't have any notion of providers.
+ [Impact]
+ While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.
+ 
+ Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
+ Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.
  
  If the provider section isn't present in the configuration, libssl3 will
  load the default provider, which means that commenting out the section
  won't impact the behavior of standard libssl3 users.
  
  [Test Plan]
  
  On a system with a pristine openssl configuration:
  
  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }
  
  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:
  
  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  
  
  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).
  
  Would it be possible to get this Debian sid change ported to jammy?

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will l

[Touch-packages] [Bug 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[Simon Chopin]

Many thanks for raising this :)

I was prepared to argue for this change as (if working as intended) it
has basically no impact on our own applications and could help quite a
few unsuspecting users, but since you asked for evidence I did a little
digging, and was somewhat surprised by what I found. While it is true
that there are quite a bit of software out there that embeds older
versions of OpenSSL, NodeJS are the outliers in pointing to /etc/ssl as
their OPENSSLDIR. In fact, even our own package points to /usr/lib/ssl,
with symlinks to /etc for the config file and the certificates.

I erroneously thought that the OpenSSL upstream default was also
/etc/ssl, but as it turns out they're using the more sensible
/usr/local/ssl as a default.

This limits the impact to

1/ third-party packages depending on our old libssl1.1,
2/ our nodejs package
3/ upstream NodeJS builds

I'm not particularly keen on doing this SRU just for the sake of 1/, and
2/ can be fixed in that package, but do we want to break things for 3/ ?

I don't know much about the JS ecosystem. My first Google result for
`installing nodejs on Ubuntu` was pretty quick to point me towards `nvm`
to "easily install different versions of Node", and that tool seems to
download upstream binaries directly.

I'm OK either way, and I've already started working on extending the
test case as per your requests.

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact] 
  While the default configuration works fine for every package that uses the 
system libssl3, any software that uses libssl1.1, either separately packaged 
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive) 
will fail to load the configuration as they don't have any notion of providers.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, 

[Touch-packages] [Bug 1970449] Autopkgtest regression report (software-properties/0.99.22.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted software-properties (0.99.22.3) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

crash/8.0.0-1ubuntu1 (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#software-properties

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

Thank you!

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

[Tired Sysadmin]

I should also have mentioned that 'ubuntu-server' has a hard dependency
on 'motd-news-config', so anybody wanting a standard server-type
installation will automatically get the advert updater and
/etc/default/motd-news.

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the Day
  After=network-online.target
  Documentation=man:update-motd(8)

  [Service]
  Type=oneshot
  ExecStart=/etc/update-motd.d/50-motd-news --force

  
  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
    Installed: 10.1ubuntu2.3
    Candidate: 10.1ubuntu2.3
    Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

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


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

[Touch-packages] [Bug 1982859] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@518:parse_arguments:print_usage:_print_message

[Benjamin Drung]

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

** This bug has been marked a duplicate of bug 1979211
   
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@518:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

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

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


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

[Touch-packages] [Bug 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

[Benjamin Drung]

This apport bug happens very often on Ubuntu 18.04 (bionic): 87
occurrences in the past day making it on rank 4. So we should fix it in
bionic.

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

** Changed in: apport (Ubuntu Bionic)
   Importance: Undecided => High

** Tags added: rls-bb-incoming

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:AssertionError:/usr/share/apport/whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New

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

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


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

[Touch-packages] [Bug 1980561] Re: apport-gtk: ImportError: cannot import name '_gi' from partially initialized module 'gi'

[Benjamin Drung]

13 occurrences in the last day making it on rank 9.

** Changed in: apport (Ubuntu)
   Importance: Low => High

** Changed in: apport
   Importance: Low => High

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

Title:
  apport-gtk: ImportError: cannot import name '_gi' from partially
  initialized module 'gi'

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 16, in 
  import gi
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in 
  from . import _gi
  ImportError: cannot import name '_gi' from partially initialized module 'gi' 
(most likely due to a circular import) 
(/usr/lib/python3/dist-packages/gi/__init__.py)

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

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


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

[Touch-packages] [Bug 1982859] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@518:parse_arguments:print_usage:_print_message

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

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


** Tags: bionic focal

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@518:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

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

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


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

[Touch-packages] [Bug 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report

[Benjamin Drung]

** Changed in: apport (Ubuntu Focal)
   Importance: Undecided => High

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:/usr/share/apport/whoopsie-upload-
  all@170:collect_info:process_report

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

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

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


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

[Touch-packages] [Bug 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r

[Benjamin Drung]

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:zlib.error:/usr/share/apport/whoopsie-upload-
  
all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Won't Fix
Status in apport source package in Jammy:
  Fix Released

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

  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 196, in 
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 146, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 103, in process_report
  r.add_gdb_info()
    File "/usr/lib/python3/dist-packages/apport/report.py", line 786, in 
add_gdb_info
  gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1706, in 
gdb_command
  self['CoreDump'].write(f)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 75, in write
  block = gz.read(1048576)
    File "/usr/lib/python3.9/gzip.py", line 300, in read
  return self._buffer.read(size)
    File "/usr/lib/python3.9/_compression.py", line 68, in readinto
  data = self.read(len(byte_view))
    File "/usr/lib/python3.9/gzip.py", line 495, in read
  uncompress = self._decompressor.decompress(buf, size)
  zlib.error: Error -3 while decompressing data: invalid code lengths set

  Report for 20.04 (focal):
  https://errors.ubuntu.com/problem/fff3109d511a7db05ec5526679b8d8608a143932

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


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

[Touch-packages] [Bug 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

[Tired Sysadmin]

Simon Déziel (sdeziel) wrote:
> IIRC, `chmod -x` snippets from /etc/update-motd.d/ was the way to go a
> few releases ago when it was consumed by run-parts.

In 22.04 it's still handled by run-parts, and the man page documents it
as such.  Specifically by

$ strings /lib/x86_64-linux-gnu/security/pam_motd.so | grep run-parts
/usr/bin/env -i 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin run-parts 
--lsbsysinit /etc/update-motd.d > /run/motd.dynamic.new

in its primary use case.  The "fetch new ads on boot" motd-news.service
for this bug report runs one of the scripts directly, but the directory
is still a run-parts input.

We could disable scripts by renaming them to something that won't be
found by the '--lsbsysinit' file patterns, but that would only solve the
problem for "at login" updates, not the "at boot" updates through
systemd.


> It's merely to avoid harmless surprise and keep the old sysadmins happy,

Service errors is hardly a "surprise", and you don't need to be
condescending about it.


wontfix (wontfix) wrote:
> and that is to set ENABLED=0 in /etc/default/motd-news."
> 
> This file no longer exists by default in Ubuntu 22.04 Jammy.

$ grep VERSION /etc/os-release
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
$ dpkg -S /etc/default/motd-news
motd-news-config: /etc/default/motd-news
$ apt show motd-news-config
Package: motd-news-config
Priority: optional
Source: base-files
Task: cloud-image, ubuntu-wsl, server, ubuntu-server-raspi
APT-Manual-Installed: no
[several header elided]

It certainly existed by default from the beginning of the server
installation I'm working with.  However, it's "priority: optional" so
perhaps that's what you mean by "not default"; it likely wouldn't be
there for a standard desktop installation.

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the Day
  After=network-online.target
  Documentation=man:update-motd(8)

  [Service]
  Type=oneshot
  ExecStart=/etc/update-motd.d/50-motd-news --force

  
  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
    Installed: 10.1ubuntu2.3
    Candidate: 10.1ubuntu2.3
    Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

Both Hirsute and Impish are End of Life. 
So there is no possibility to fix these ones. 

Change will be SRUd to Focal for sure.

** Changed in: openssh (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

** Changed in: openssh (Ubuntu Impish)
   Status: Triaged => Won't Fix

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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

[Touch-packages] [Bug 1982800] Re: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Simple attempted apt update/upgrade on Ubuntu 22.04 Desktop kernel
  version 5.15.0-40-generic with systemd-boot as boot loader, failed.

  The error was returned on running 'apt autoremove' concerning kernel
  version 39 files.

  Most likely a failure of sd-boot's kernel-update functionality due in
  part to its absence of hooks for Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   unattended-upgrades:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   2293 F pulseaudio
   /dev/snd/controlC1:  eric   2293 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Jul 25 20:36:10 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-06-08 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: 
initrd=\8e50061eea1a489d8622f7be6f5b5945\5.15.0-40-generic\initrd 
root=PARTUUID=9d1de6a4-452c-42d2-bf18-acee90032326 rw
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1704
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79-E WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1704:bd05/08/2015:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79-EWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 1661209] Re: apport-unpack crashes with ValueError: ['ProcEnviron', UserGroups'] has no binary content

[Benjamin Drung]

I can reproduce it with the attached _usr_sbin_avahi-daemon.0.crash

Can you submit the crash by running "apport-bug
/var/crash/_usr_sbin_avahi-daemon.0.crash"?

** Summary changed:

- crashes when trying to upload avahi report from #1661205
+ apport-unpack crashes with ValueError: ['ProcEnviron', UserGroups'] has no 
binary content

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

** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
   Status: New => Triaged

** Changed in: apport
   Importance: Undecided => Medium

** Changed in: apport
Milestone: None => 2.23.0

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

Title:
  apport-unpack crashes with ValueError: ['ProcEnviron', UserGroups']
  has no binary content

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  In bug #1661205 avahi-dameon repeatedly crashes, and causes apport to
  go into an infinite loop.

  However I suspect this is a problem with apport, because when I
  manually unpack the .crash I get:

  # apport-unpack /var/crash/_usr_sbin_avahi-daemon.0.crash /home/redacted/foo
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['ProcEnviron', 'UserGroups'] has no binary content

  Please find attached /var/crash/_usr_sbin_avahi-daemon.0.crash

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu8.2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashReports:
   640:0:122:14612:2017-02-02 10:48:08.638081761 +:2017-02-02 
10:48:08.638081761 +:/var/crash/_usr_bin_apport-unpack.0.crash
   640:0:122:1355374:2017-02-02 10:42:53.922800121 +:2017-02-02 
10:48:08.582079751 +:/var/crash/_usr_sbin_avahi-daemon.0.crash
  CurrentDesktop: Unity
  Date: Thu Feb  2 10:51:34 2017
  InstallationDate: Installed on 2016-10-31 (93 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.99.25

---
software-properties (0.99.25) kinetic; urgency=medium

  * Fix GPG keys are not shown in Software and Updates (LP: #1970449)
  * Remove trailing spaces
  * Drop obsolete imports from __future__
  * Remove duplicate keys in desktop files
  * d/copyright: Use https URLs instead of http
  * d/copyright: Correct path to add-apt-repository.1
  * Drop obsolete Conflicts & Replaces
  * Fix spelling mistake of repository
  * Set Rules-Requires-Root: no
  * Bump Standards-Version to 4.6.1
  * Add Vcs-Browser

 -- Benjamin Drung   Tue, 26 Jul 2022 13:03:28 +0200

** Changed in: software-properties (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1962135] Re: [SRU] gstreamer 1.16.3 series

[Ashton Nelson]

I tested a variety of audio/video formats (x264, x265, MP4, MKV, flac,
MP3, etc.) as well as streaming audio/video and everything seems to work
as intended with no issues.

Tested on a Focal VM with the latest updates including this patch.

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

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

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-base1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-good1.0 source package in Focal:
  Fix Committed
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+subscriptions


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

[Touch-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox

[Benjamin Drung]

There are two possible reasons:
1. Firefox or no other browser is installed
2. Firefox or another browser is installed, but xdg-open fails to open it.

Assuming it is point 2, I re-assign this ticket to xdg-utils which
provides /usr/bin/xdg-open.

** Package changed: apport (Ubuntu) => xdg-utils (Ubuntu)

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

Title:
  apport-collect & ubuntu-bug failing to switch to firefox

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  In attempting to file a bug report on Lubuntu jammy ISO 
  (QA-test installed yesterday using ISO 2020-04-15)

  --
  guiverc@dc7700-2re:~$ apport-collect 1969290
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION'
  ---

  On attempting to file using `ubuntu-bug apport`

  ---
  guiverc@dc7700-2re:~$ ubuntu-bug apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  . 

   


   
  *** Send problem report to the developers?

   


   
  After the problem report has been sent, please fill out the form in the   

   
  automatically opened web browser. 

   


   
  What would you like to do? Your options are:  

   
S: Send report (5.0 KB) 

   
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  96%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?'
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sun Apr 17 12:34:57 2022
  InstallationDate: Installed on 2022-04-16 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220415)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: http

[Touch-packages] [Bug 1979211] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message

[Benjamin Drung]

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

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

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Won't Fix
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  Test Case
  -

  There should be no instances of
  https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
  for the fixed version.

  Original Description
  

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

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 531, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 463, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.10/argparse.py", line 2562, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.10/argparse.py", line 2573, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

  This bug can be reproduced by configuring the previously supported
  parameters to Apport and then let a process crash (e.g. call divide-
  by-zero):

  ```
  echo "|/usr/share/apport/apport %p %s %c %d %P %E" | sudo tee 
/proc/sys/kernel/core_pattern
  ```

  So this bug is a regression of commit c320e910a516 ("Switch to using
  non-positional arguments") which is a fix for CVE-2022-28658 and
  CVE-2021-3899.

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


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

[Touch-packages] [Bug 1973032] Re: Can't report a bug anymore

[Benjamin Drung]

Can you run following command and attach the resulting Packages.txt file
to this bug report?

dpkg-query -W > Packages.txt

Then we can check the exact package versions. Did you installed all
available package updates?

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

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

Title:
  Can't report a bug anymore

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hi guy's!

  I got some GPU lock-ups or freezes today an last weekend and want to
  report it (x-org). But every time I go through ubuntu-bug it says at
  the end, that the bug can't be reported because it isn't a official
  release and I have to uninstall all 3rd party packages first.

  I have no idea what's wrong. I'm using Ubuntu 20.04.3 LTS with Kernel
  5.4.0-97-generic and the latest Nvidia 510.60.02 GPU driver.

  If you need some more informations please tell me.

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


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

[Touch-packages] [Bug 1982684] Re: ubuntu-bug launches chromium instead of my default browser

[Benjamin Drung]

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

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

Title:
  ubuntu-bug launches chromium instead of my default browser

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  graingert@conscientious:~$ gconftool --get 
/desktop/gnome/url-handlers/http/command
  No value set for `/desktop/gnome/url-handlers/http/command'
  graingert@conscientious:~$ cat ~/.local/share/applications/mimeapps.list
  cat: /home/graingert/.local/share/applications/mimeapps.list: No such file or 
directory

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 09:56:49 2022
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1980238] Re: apport-gtk: AssertionError when importing Gdk

[Benjamin Drung]

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

** Changed in: apport
   Importance: Medium => High

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

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

Title:
  apport-gtk: AssertionError when importing Gdk

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Latest occurrence on Ubuntu 22.04 with apport 2.20.11-0ubuntu82.1

  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 19, in 
  from gi.repository import GLib, Wnck, GdkX11, Gdk
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in 
load_module
  importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in 
load_module
  importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 146, in 
load_module
  dynamic_module = load_overrides(introspection_module)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 118, 
in load_overrides
  override_mod = importlib.import_module(override_package_name)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "/usr/lib/python3/dist-packages/gi/overrides/Gdk.py", line 83, in 

  Color = override(Color)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 195, 
in override
  assert g_type != TYPE_NONE
  AssertionError

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

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


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

[Touch-packages] [Bug 1980553] Re: /usr/share/apport/apport-kde:NameError:/usr/share/apport/apport-kde@19:/usr/share/apport/apport-kde@58

[Benjamin Drung]

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

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

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

Title:
  /usr/share/apport/apport-kde:NameError:/usr/share/apport/apport-
  kde@19:/usr/share/apport/apport-kde@58

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 19, in 
  import sip
  ModuleNotFoundError: No module named 'sip'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 58, in 
  apport.fatal(
  NameError: name 'apport' is not defined

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

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


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

[Touch-packages] [Bug 1953720] Re: OSError: [Errno 30] Read-only file system: '/var/crash/...

[Benjamin Drung]

I still fail to understand what went wrong there. /var/crash has correct
permission to write to. In case of permission errors, the error should
say PermissionError (errno 13 IIRC), but the failure message says "Read-
only file system".

Can you paste the content of /proc/mounts?

What happens if you try to create a file in /var/crash? E.g. run

touch /var/crash/testcase.crash

I would expect that to work.

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

Title:
  OSError: [Errno 30] Read-only file system: '/var/crash/...

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call 
last):
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
408, in 
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: main()
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
152, in main
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, 
servers, config):
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
239, in check
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, 
mock_runner, servers)
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
262, in send_digest
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, 
servers[0], digested)
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 
253, in _send_digest
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, 
(digested, server))
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: response = 
self.routine(*args, **kwargs)
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: msg = (b"Code: %s\nDiag: 
OK\nPV: %s\nThread: 1024\nCount: 0\n"
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: TypeError: %b requires a 
bytes-like object, or an object that implements __bytes__, not 'int'
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Error in sys.excepthook:
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call 
last):
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in 
apport_excepthook
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: with 
os.fdopen(os.open(pr_filename,
  Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: OSError: [Errno 30] Read-only 
file system: '/var/crash/_usr_bin_pyzor.122.crash'

  1) due to an encoding error, pyzor is throwing an exception.
  2) /usr/lib/python3/dist-packages/apport_python_hook.py is the exception 
handler invoked (belonging to the python3-apport package)
  3) This exception handler tries to write to 
/var/crash/_usr_bin_pyzor.122.crash, which fails

  I checked the permissions:

  # ls -l /var/crash
  total 0

  # ls -ld /var/crash
  drwxrwxrwt 2 root root 4096 Dec  8 16:45 /var/crash

  # ls -ld /var/
  drwxr-xr-x 18 root root 4096 Jun 23  2020 /var/

  # ls -ld /
  drwxr-xr-x 24 root root 4096 Nov 30 06:19 /

  /var/crash is sticky, so why can't it write?

  # cat /proc/mounts  |fgrep crash
  #

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3-apport 2.20.11-0ubuntu27.21
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Dec  9 09:39:40 2021
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2021-04-07 (245 days ago)

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

** Changed in: openssh (Ubuntu Focal)
 Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)

** Changed in: openssh (Ubuntu Hirsute)
 Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)

** Changed in: openssh (Ubuntu Impish)
 Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Triaged
Status in openssh source package in Impish:
  Triaged

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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

[Touch-packages] [Bug 1981638] Re: apport-unpack crashed with ValueError in extract_keys(): ['separator'] has no binary content

[Benjamin Drung]

Can you attach /var/crash/_usr_bin_gnome-shell.1000.crash to this bug
report? Then this should be fairly easy to fix.

** Information type changed from Private to Public

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

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

Title:
  apport-unpack crashed with ValueError in extract_keys(): ['separator']
  has no binary content

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  (I am reporting this from the host: I tried to report this bug 6 times
  in the VM and it always logged me out.)

  When unpacking a crash report (specifically that of bug #1981613),
  apport-unpack extracts most or all of the files correctly and then
  raises the following exception:

   Traceback (most recent call last):
 File "/usr/bin/apport-unpack", line 81, in 
   pr.extract_keys(f, bin_keys, dir)
 File "/usr/lib/python3/dist-packages/problem_report.py", line 244, in 
extract_keys
   raise ValueError(
   ValueError: ['separator'] has no binary content

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: apport 2.22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:20883:2022-07-13 21:18:51.655054330 +0100:2022-07-13 
21:18:52.655054330 +0100:/var/crash/_usr_bin_apport-unpack.1000.crash
   600:117:124:37:2022-07-13 21:15:31.220157021 +0100:2022-07-13 
21:15:31.216156906 +0100:/var/crash/_usr_bin_gnome-shell.1000.uploaded
   640:1000:124:50223405:2022-07-13 21:14:56.558673858 +0100:2022-07-13 
21:14:57.558673858 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash
   664:1000:124:0:2022-07-13 21:15:22.259870444 +0100:2022-07-13 
21:15:22.259870444 +0100:/var/crash/_usr_bin_gnome-shell.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 13 21:18:52 2022
  ExecutablePath: /usr/bin/apport-unpack
  ExecutableTimestamp: 1657219442
  InstallationDate: Installed on 2022-06-26 (17 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220624)
  InterpreterPath: /usr/bin/python3.10
  JournalErrors:
   Jul 13 21:18:43 testing-vm-2210 tracker-extract[8225]: Could not connect to 
filesystem miner endpoint: Timeout was reached
   Jul 13 21:18:43 testing-vm-2210 systemd[783]: tracker-extract-3.service: 
Failed with result 'exit-code'.
   Jul 13 21:18:43 testing-vm-2210 systemd[783]: Failed to start Tracker 
metadata extractor.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-unpack 
/var/crash/_usr_bin_gnome-shell.1000.crash gnome-shell-segv
  ProcCwd: /home/user
  Python3Details: /usr/bin/python3.10, Python 3.10.5, python3-minimal, 
3.10.4-0ubuntu2
  PythonArgs: ['/usr/bin/apport-unpack', 
'/var/crash/_usr_bin_gnome-shell.1000.crash', 'gnome-shell-segv']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-unpack crashed with ValueError in extract_keys(): ['separator'] 
has no binary content
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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


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

[Touch-packages] [Bug 1790155] Re: package_hook crashed with FileNotFoundError in makedirs(): [Errno 2] No such file or directory: '//var/cache/apt/archives/partial'

[Benjamin Drung]

Apport calls: apt.Cache(progress, rootdir='/')

This call should not crash that way. The library is provided by
python3-apt. Therefore reassigning to it.

** Description changed:

- ??
+ Traceback (most recent call last):
+   File "/usr/share/apport/package_hook", line 47, in 
+ pr.add_package(options.package)
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 297, in 
add_package
+ version = packaging.get_version(package)
+   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 133, 
in get_version
+ pkg = self._apt_pkg(package)
+   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 126, 
in _apt_pkg
+ return self._cache()[package]
+   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 91, in 
_cache
+ self._apt_cache = apt.Cache(progress, rootdir='/')
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 134, in __init__
+ self._check_and_create_required_dirs(rootdir)
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 167, in 
_check_and_create_required_dirs
+ os.makedirs(rootdir + d)
+   File "/usr/lib/python3.6/os.py", line 220, in makedirs
+ mkdir(name, mode)
+ FileNotFoundError: [Errno 2] No such file or directory: 
'//var/cache/apt/archives/partial'
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu9
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CrashReports:
-  600:0:117:477532:2018-08-30 21:37:16.894364432 +0530:2018-08-30 
22:00:45.845285436 +0530:/var/crash/autofs.0.crash
-  640:0:117:20449:2018-08-30 21:37:16.574347496 +0530:2018-08-30 
21:37:17.574347496 +0530:/var/crash/_usr_share_apport_package_hook.0.crash
-  600:0:117:211775:2018-08-30 22:02:54.401198146 +0530:2018-08-30 
22:04:08.651412758 +0530:/var/crash/ttf-mscorefonts-installer.0.crash
-  640:1000:117:2161231:2018-08-31 19:00:33.207204658 +0530:2018-08-31 
19:00:30.443132877 +0530:/var/crash/_usr_bin_Xwayland.1000.crash
+  600:0:117:477532:2018-08-30 21:37:16.894364432 +0530:2018-08-30 
22:00:45.845285436 +0530:/var/crash/autofs.0.crash
+  640:0:117:20449:2018-08-30 21:37:16.574347496 +0530:2018-08-30 
21:37:17.574347496 +0530:/var/crash/_usr_share_apport_package_hook.0.crash
+  600:0:117:211775:2018-08-30 22:02:54.401198146 +0530:2018-08-30 
22:04:08.651412758 +0530:/var/crash/ttf-mscorefonts-installer.0.crash
+  640:1000:117:2161231:2018-08-31 19:00:33.207204658 +0530:2018-08-31 
19:00:30.443132877 +0530:/var/crash/_usr_bin_Xwayland.1000.crash
  Date: Thu Aug 30 21:37:17 2018
  ExecutablePath: /usr/share/apport/package_hook
  InstallationDate: Installed on 2018-04-28 (125 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/package_hook -p 522-autofs 
--tags dist-upgrade -l /var/log/dist-upgrade/apt.log -l 
/var/log/dist-upgrade/apt-term.log -l 
/var/log/dist-upgrade/apt-clone_system_state.tar.gz -l 
/var/log/dist-upgrade/history.log -l /var/log/dist-upgrade/lspci.txt -l 
/var/log/dist-upgrade/main.log -l /var/log/dist-upgrade/term.log -l 
/var/log/dist-upgrade/screenlog.0 -l /var/log/dist-upgrade/xorg_fixup.log
  ProcEnviron:
-  TERM=screen.xterm-256color
-  SHELL=/bin/bash
-  LANG=en_IN
-  PATH=(custom, user)
+  TERM=screen.xterm-256color
+  SHELL=/bin/bash
+  LANG=en_IN
+  PATH=(custom, user)
  Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
  PythonArgs: ['/usr/share/apport/package_hook', '-p', '522-autofs', '--tags', 
'dist-upgrade', '-l', '/var/log/dist-upgrade/apt.log', '-l', 
'/var/log/dist-upgrade/apt-term.log', '-l', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz', '-l', 
'/var/log/dist-upgrade/history.log', '-l', '/var/log/dist-upgrade/lspci.txt', 
'-l', '/var/log/dist-upgrade/main.log', '-l', '/var/log/dist-upgrade/term.log', 
'-l', '/var/log/dist-upgrade/screenlog.0', '-l', 
'/var/log/dist-upgrade/xorg_fixup.log']
  PythonDetails: N/A
  SourcePackage: apport
  Title: package_hook crashed with FileNotFoundError in makedirs(): [Errno 2] 
No such file or directory: '//var/cache/apt/archives/partial'
  UpgradeStatus: Upgraded to cosmic on 2018-08-30 (0 days ago)
  UserGroups:

** Information type changed from Private to Public

** Package changed: apport (Ubuntu) => python-apt (Ubuntu)

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

Title:
  package_hook crashed with FileNotFoundError in makedirs(): [Errno 2]
  No such file or directory: '//var/cache/apt/archives/partial'

Status in python-apt package in Ubuntu:
  New

Bug description:
  Traceback (most recent call last):
File "/usr/share/apport/package_hook", line 47, in 
  pr.add_package(optio

[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04

[Philipp Wendler]

Somebody else has reported this upstream
(https://github.com/systemd/systemd/issues/24120) and a fix is being
developed as https://github.com/systemd/systemd/pull/24122.

** Bug watch added: github.com/systemd/systemd/issues #24120
   https://github.com/systemd/systemd/issues/24120

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/24120
   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/1979952

Title:
  Bind mount to NFS mount fails on Ubuntu 22.04

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  I have the following setup:
  - /data is an NFS mount.
  - /home is a bind mount to /data/home.

  Configured in /etc/fstab with these lines:

  $FILE_SERVER:/data /data nfs defaults 0 0
  /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0

  This has worked with the same configuration for me on at least Ubuntu 18.04 
and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted 
by systemd.
  So not only is /home not mounted after boot, but also when I run "sudo 
systemctl start home.mount", it fails.

  The journal entries are this:

  sudo[1316]:  wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; 
COMMAND=/usr/bin/systemctl start home.mount
  sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by 
wendler(uid=1000)
  systemd[1]: home.mount: Directory /home to mount over is not empty, mounting 
anyway.
  systemd[1]: home.mount: Failed to make bind mount source '/data/home': 
Permission denied
  systemd[1]: home.mount: Failed to run 'mount' task: Permission denied
  systemd[1]: home.mount: Failed with result 'resources'.
  systemd[1]: Failed to mount /home.

  However, when I run "sudo mount /home" it works.

  Now the weird thing is that after I have mounted /home manually once
  and unmounted it again, then "sudo systemctl start home.mount"
  suddenly also works! But of course only until the next reboot.

  And even if I just do "ls /data" once (either as root or as my user),
  it also makes "sudo systemctl start home.mount" start working!

  To be fully clear:

  - Booting the system (/home fails to mount)
  - sudo systemctl start home.mount  # fails
  - sudo ls /data  # shows correct output
  - sudo systemctl start home.mount  # works!

  
  Additional information:

  The NFS export for /data has root_squash set and if I remove this
  option, the bind mount of /home works as it should. However, both
  /data and /data/home have mode rwxr-xr-x, so root is able to enter and
  read these directories even despite root_squash.

  It is not a network or mount-order problem. Not only is the bind mount
  to /home correctly attempted after /data is mounted during boot,
  remember that the bind mount also fails when I try it with "sudo
  systemctl start home.mount" minutes afterwards.

  Versions (system is a recent installation with all updates applied):
  - Ubuntu 22.04
  - Linux 5.15.0-40-generic
  - systemd 249.11-0ubuntu3.3
  - util-linux 2.37.2-4ubuntu3

  This appears on both Ubuntu 22.04 machines that I have (a hardware
  machine and a VM).

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


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

[Touch-packages] [Bug 1844682] Re: ubuntu-bug _usr_bin_sudo.crash yields AttributeError

[Benjamin Drung]

yesno returns None. The API says that this can be the case:

```
def yesno(self, text):
"""Show a yes/no question.

Return True if the user selected "Yes", False if selected "No" or
"None" on cancel/dialog closing.
"""
```

So the culprit is /usr/share/apport/package-hooks/source_sudo.py which
is provided by the sudo package. So adjust the package accordingly.

** Package changed: apport (Ubuntu) => sudo (Ubuntu)

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

Title:
  ubuntu-bug _usr_bin_sudo.crash yields AttributeError

Status in sudo package in Ubuntu:
  New

Bug description:
  While digging through /var/crash folder I've realized that I do have a
  few crashes involving sudo. To be exact, couple of files names
  _usr_bin_sudo.N.crash

  Logically, I've tried uploading those to Ubuntu error tracker using
  following:

  ubuntu-bug  /var/crash/_usr_bin_sudo.0.crash

  It failed mumbling about permissions. So, stupid but common next step:
  sudo ubuntu-bug  /var/crash/_usr_bin_sudo.0.crash

  yielded me the following Python Traceback:

  ** (apport-gtk:6825): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-ILURWtYdgA: Connection refused
  ERROR: hook /usr/share/apport/package-hooks/source_sudo.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_sudo.py", line 20, in add_info
  response = ui.yesno("The contents of your /etc/sudoers file may help 
developers diagnose your bug more quickly, however, it may contain sensitive 
information.  Do you want to include it in your bug report?")
  AttributeError: 'NoneType' object has no attribute 'yesno'

  It seems that in the end, something got uploaded to the server, but it
  didn't make any indication of successful upload what-so-ever.
  Repeating the same sequence of actions does not yield the same Python
  Traceback and exits gracefully.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.19
  ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Thu Sep 19 17:09:29 2019
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1784116] Re: ubuntu-bug reports the package from other arch as not installed

[Benjamin Drung]

I can confirm it and reproduce on Ubuntu 22.04. Install libnss-nis:i386
(but not libnss-nis:amd64). Then run:

ubuntu-bug /lib/i386-linux-gnu/libnss_nis.so.2.0.0

Then the problem report says:

Package: libnss-nis (not installed)

** Summary changed:

- ubuntu-bug reports the package as not installed.
+ ubuntu-bug reports the package from other arch as not installed

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

** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
   Status: New => Triaged

** Changed in: apport
   Importance: Undecided => Medium

** Changed in: apport
Milestone: None => 2.23.0

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

Title:
  ubuntu-bug reports the package from other arch as not installed

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1 Minimal (+++)

  ubuntu-bug steam returns package not installed:

  -steam/bionic,now 1:1.0.0.54+repack-5ubuntu1 i386 [installed]
  -se attachment.

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


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

[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

[Brian Murray]

** Changed in: ubuntu-download-manager (Ubuntu Vivid)
   Status: New => Won't Fix

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in Canonical System Image:
  Fix Released
Status in Click Package Index:
  Fix Released
Status in Software Center Agent:
  Fix Released
Status in click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager source package in Vivid:
  Won't Fix

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+subscriptions


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

[Touch-packages] [Bug 1925478] Re: python3-apport will crash if current directory has been unlinked

[Benjamin Drung]

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

Thanks for reporting this bug. I stumbled over the same bug and reported
it as bug #1979637 (since I didn't noticed your bug report). This bug is
fixed in Ubuntu 22.10 (kinetic) and will be backported to Ubuntu 22.04
(jammy). If you want to have it backported to older releases, please
commit in #1979637.

** This bug has been marked a duplicate of bug 1979637
   apport_python_hook: FileNotFoundError if cwd was deleted

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

Title:
  python3-apport will crash if current directory has been unlinked

Status in apport package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  I have also checked the code for Ubuntu 20 and the specific code looks
  identical to me.

  
  From package:python3-apport
  file: /usr/lib/python3/dist-packages/apport_python_hook.py

  The follwing code will crash if current directory has been removed, 
os.getcwd() does not like that directory is gone:
  # apport will look up the package from the executable path.   

 
  try:
  binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
  except (TypeError, AttributeError, IndexError):
  # the module has mutated sys.argv, plan B 

 
  try:
  binary = os.readlink('/proc/%i/exe' % os.getpid())
  except OSError:
  return

  
  FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmp_6ehbyrh'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in 
apport_excepthook
  binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
  FileNotFoundError: [Errno 2] No such file or directory

  
  The try-except condition above maybe should also contain FileNotFoundError to 
handle this error.

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


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

[Touch-packages] [Bug 1979637] Re: apport_python_hook: FileNotFoundError if cwd was deleted

[Launchpad Bug Tracker]

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

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

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

Title:
  apport_python_hook: FileNotFoundError if cwd was deleted

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Confirmed

Bug description:
  Test Case
  -

  Run following shell script:

  ```sh
  echo "raise ValueError()" > /tmp/failure.py
  mkdir /tmp/foo
  cd /tmp/foo/
  rmdir /tmp/foo/
  python3 ../failure.py
  ```

  It should only print following stacktrace:

  ```
  Traceback (most recent call last):
File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  ```

  Regression Potential
  

  There might be a regression that causes capturing Python exception
  fail. Then reporting them as bugs to Launchpad or the error tracker
  would not be possible.

  Original Description
  

  The script should only show a ValueError, but apport_python_hook.py
  crashes:

  ```
  Traceback (most recent call last):
    File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "", line 1372, in 
_path_importer_cache
  KeyError: '..'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 55, in 
apport_excepthook
  import apt_pkg
    File "", line 1027, in _find_and_load
    File "", line 1002, in _find_and_load_unlocked
    File "", line 945, in _find_spec
    File "", line 1439, in find_spec
    File "", line 1408, in _get_spec
    File "", line 1374, in 
_path_importer_cache
    File "", line 1350, in _path_hooks
    File "", line 1632, in 
path_hook_for_FileFinder
    File "", line 1505, in __init__
  FileNotFoundError: [Errno 2] No such file or directory

  Original exception was:
  Traceback (most recent call last):
    File "../failure.py", line 1, in 
  raise ValueError()
  ValueError
  ```

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


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

[Touch-packages] [Bug 1982684] Re: ubuntu-bug launches chromium instead of my default browser

[Benjamin Drung]

What happens when you run following command:

xdg-open https://launchpad.net

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

Title:
  ubuntu-bug launches chromium instead of my default browser

Status in apport package in Ubuntu:
  New

Bug description:
  graingert@conscientious:~$ gconftool --get 
/desktop/gnome/url-handlers/http/command
  No value set for `/desktop/gnome/url-handlers/http/command'
  graingert@conscientious:~$ cat ~/.local/share/applications/mimeapps.list
  cat: /home/graingert/.local/share/applications/mimeapps.list: No such file or 
directory

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 09:56:49 2022
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[Łukasz Zemczak]

Hello MadhuSoodanan, or anyone else affected,

Accepted software-properties into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.22.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1970449

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[Benjamin Drung]

** Changed in: software-properties (Ubuntu Kinetic)
   Status: Confirmed => Fix Committed

** Changed in: software-properties (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Description changed:

+ [Impact]
+ 
  software-properties-gtk does not show the registered apt gpg keys in the
  "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.
+ 
+ [Test Plan]
+ 
+ 1. Launch software-properties-gtk
+ 2. Click on the "Authentication" tab
+ 3. At least one key should be listed
+ 
+ [Where problems could occur]
+ 
+ I fail to come up with possible problems. The failures was a regression
+ and the fixed version has a test case.
+ 
+ [Other Infos]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

** Patch added: "software-properties_0.99.22.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+attachment/5605384/+files/software-properties_0.99.22.3.debdiff

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

[Benjamin Drung]

subprocess.run is nicer that subprocess.Popen since you do not have to
close the opened process. The underlying problem is that
subprocess.Popen gave you the output line by line, but stdout from
subprocess.run is the complete output. To iterate over the lines you
have to call splitlines() first. Otherwise only the first line is taken
into account and all following lines will be ignored.

I added a test case and fixed the code (besides some packaging clean-
up). Thanks H. Hösch for the analysis and for finding the culprit.

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Jammy:
  Confirmed
Status in software-properties source package in Kinetic:
  Confirmed

Bug description:
  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Lenin]

I partly agree, the problem seems it is a phased update? Can you confirm or not?
Because other 22.04 machines don't get that version (90% of the other 22.04 
machines).

Thus I wish to have a way to not take part of phased updates, especially since 
we disable
auto bug reporting (which seems to be crucial part of phased updates roll out 
increment or roll back/discard)

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Julian Andres Klode]

In your libmysqlclient21 example everything seems to be working
correctly so I don't understand why you post that.

- you are eligible for 8.0.29-0ubuntu0.22.04.3
- you force downgrade to 8.0.29-0ubuntu0.22.04.2
- you upgrade once again to 8.0.29-0ubuntu0.22.04.3
- no higher version available in final dist-upgrade run

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Lenin]

a downgrade is possible:

hostname:~# apt policy libmysqlclient21
libmysqlclient21:
  Installed: 8.0.29-0ubuntu0.22.04.3
  Candidate: 8.0.29-0ubuntu0.22.04.3
  Version table:
 *** 8.0.29-0ubuntu0.22.04.3 500 (phased 10%)
500 http://ubuntu.ethz.ch/ubuntu jammy-updates/main amd64 Packages
500 http://ubuntu.ethz.ch/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 8.0.29-0ubuntu0.22.04.2 500
500 http://ubuntu.ethz.ch/ubuntu jammy-security/main amd64 Packages
 8.0.28-0ubuntu4 500
500 http://ubuntu.ethz.ch/ubuntu jammy/main amd64 Packages
hostname:~# apt install libmysqlclient21=8.0.29-0ubuntu0.22.04.2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libaom-dev libarmadillo-dev libarpack2-dev libavformat-dev libblosc-dev 
libcharls-dev libdav1d-dev
  libde265-dev libdouble-conversion-dev libfreexl-dev libfyba-dev libgeos-dev 
libgeotiff-dev libgl2ps-dev
  libglew-dev libheif-dev libjson-c-dev libjsoncpp-dev libkml-dev 
libkmlconvenience1 libkmlregionator1
  libkmlxsd1 liblapack-dev libnetcdf-c++4 libnetcdf-cxx-legacy-dev libogdi-dev 
libopenjp2-7-dev libopenni2-0
  libopenni2-dev libpcl-apps1.12 libpcl-common1.12 libpcl-features1.12 
libpcl-filters1.12 libpcl-io1.12
  libpcl-kdtree1.12 libpcl-keypoints1.12 libpcl-ml1.12 libpcl-octree1.12 
libpcl-outofcore1.12 libpcl-people1.12
  libpcl-recognition1.12 libpcl-registration1.12 libpcl-sample-consensus1.12 
libpcl-search1.12
  libpcl-segmentation1.12 libpcl-stereo1.12 libpcl-surface1.12 
libpcl-tracking1.12 libpcl-visualization1.12
  libpoppler-dev libpoppler-private-dev libproj-dev librttopo-dev 
libspatialite-dev libsuperlu-dev
  libswscale-dev libtheora-dev liburiparser-dev libusb-1.0-0-dev libutfcpp-dev 
libvtk9-java libvtk9.1-qt
  libx265-dev libzstd-dev python3-vtk9 qttools5-private-dev tcl-dev tcl8.6-dev 
tk-dev tk8.6-dev vtk9
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  default-libmysqlclient-dev libgdal-dev libmysqlclient-dev libpcl-dev 
libvtk9-dev libvtk9-qt-dev
The following packages will be DOWNGRADED:
  libmysqlclient21
0 upgraded, 0 newly installed, 1 downgraded, 6 to remove and 0 not upgraded.
Need to get 1,273 kB of archives.
After this operation, 102 MB disk space will be freed.
Do you want to continue? [Y/n] 

hostname:~# apt install libmysqlclient21
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libaom-dev libarmadillo-dev libarpack2-dev libavformat-dev libblosc-dev 
libcharls-dev libdav1d-dev
  libde265-dev libdouble-conversion-dev libfreexl-dev libfyba-dev libgeos-dev 
libgeotiff-dev libgl2ps-dev
  libglew-dev libheif-dev libjson-c-dev libjsoncpp-dev libkml-dev 
libkmlconvenience1 libkmlregionator1
  libkmlxsd1 liblapack-dev libnetcdf-c++4 libnetcdf-cxx-legacy-dev libogdi-dev 
libopenjp2-7-dev libopenni2-0
  libopenni2-dev libpcl-apps1.12 libpcl-common1.12 libpcl-features1.12 
libpcl-filters1.12 libpcl-io1.12
  libpcl-kdtree1.12 libpcl-keypoints1.12 libpcl-ml1.12 libpcl-octree1.12 
libpcl-outofcore1.12 libpcl-people1.12
  libpcl-recognition1.12 libpcl-registration1.12 libpcl-sample-consensus1.12 
libpcl-search1.12
  libpcl-segmentation1.12 libpcl-stereo1.12 libpcl-surface1.12 
libpcl-tracking1.12 libpcl-visualization1.12
  libpoppler-dev libpoppler-private-dev libproj-dev librttopo-dev 
libspatialite-dev libsuperlu-dev
  libswscale-dev libtheora-dev liburiparser-dev libusb-1.0-0-dev libutfcpp-dev 
libvtk9-java libvtk9.1-qt
  libx265-dev libzstd-dev python3-vtk9 qttools5-private-dev tcl-dev tcl8.6-dev 
tk-dev tk8.6-dev vtk9
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  libmysqlclient21
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,273 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ubuntu.ethz.ch/ubuntu jammy-updates/main amd64 libmysqlclient21 
amd64 8.0.29-0ubuntu0.22.04.3 [1,273 kB]
Fetched 1,273 kB in 0s (16.9 MB/s) 
(Reading database ... 750292 files and directories currently installed.)
Preparing to unpack .../libmysqlclient21_8.0.29-0ubuntu0.22.04.3_amd64.deb ...
Unpacking libmysqlclient21:amd64 (8.0.29-0ubuntu0.22.04.3) over 
(8.0.29-0ubuntu0.22.04.2) ...
Setting up libmysqlclient21:amd64 (8.0.29-0ubuntu0.22.04.3) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
/sbin/ldconfig.real: /lib/libXp.so.6 is not a symbolic link

/sbin/ldconfig.real: /lib/libgfortran.so.3 is not a symbolic link

Scanning processes...   
 
Scanning candidates...  
 
Scanning processor microcode...   

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Lenin]

I wasn't expecting different behaviour of apt, apt-get, aptitude, and
here's proof they're all linked against same libapt, same version:

hostname:~# ldd $(which apt-get) |grep apt
libapt-private.so.0.0 => /lib/x86_64-linux-gnu/libapt-private.so.0.0 
(0x7fe7c1c68000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fe7c1aa6000)
hostname:~# ldd $(which apt) |grep apt
libapt-private.so.0.0 => /lib/x86_64-linux-gnu/libapt-private.so.0.0 
(0x7fd3023a5000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fd3021e3000)
hostname:~# ldd $(which aptitude) |grep apt
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fa63a117000)

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

[Touch-packages] [Bug 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

[Pedro Serrano]

Folks,

I get the Same error.

lightdm --test-mode 
Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate 
permissions?

It's been a few years without activity...  Thanks for your attention.

Regards

Pedro

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

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


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

[Touch-packages] [Bug 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

[Pedro Serrano]

BTW..
root@###:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy
root@###:~# apt list lightdm --installed
Listing... Done
lightdm/jammy,now 1.30.0-0ubuntu5 amd64 [installed,automatic]

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

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


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

[Touch-packages] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

[Daniel van Vugt]

Only fixed in Mesa 23 right now but I would expect to see it in 22.x

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

Title:
  gnome-shell crashed with SIGSEGV in crocus_begin_query() from
  crocus_begin_query() from crocus_end_query() from crocus_end_query()
  from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed

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

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


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

[Touch-packages] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

[Daniel van Vugt]

Upstream says the crash is caused by a leak and reviewing the Mesa code
seems to support that theory. The fix is:

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17731

** Tags added: gnome-shell-leak

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

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

** Tags added: fixed-in-23 fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in crocus_begin_query() from
  crocus_begin_query() from crocus_end_query() from crocus_end_query()
  from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed

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

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


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

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

[Bug Watch Updater]

** Changed in: nettle (Debian)
   Status: Unknown => New

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress
Status in nettle package in Debian:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Lukas Märdian]

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

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable

[Lukas Märdian]

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

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

Title:
  /etc/localtime symlink not correctly handled when using /etc/writable

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Jammy:
  New
Status in systemd source package in Kinetic:
  Fix Committed

Bug description:
  When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a
  symlink to /etc/writable/localtime (which in itself if a symlink).
  Systemd doesn't handle this correctly when doing firstboot or using
  inotify to watch for changed to localtime.

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


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

[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail

[Lukas Märdian]

** Changed in: systemd (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

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

Title:
  Some modprobe loading services requested by the pstore service fail

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  It has been detected that some modprobe services fail on UC22 after
  the jammy upgrade  249.11-0ubuntu3.4:

  $ systemctl --system --no-ask-password --no-pager list-units --state=failed
  Failed units:
UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module 
chromeos_pstore
  ● modprobe@efi_pstore.service  loaded failed failed Load Kernel Module 
efi_pstore
  ● modprobe@mtdpstore.service   loaded failed failed Load Kernel Module 
mtdpstore
  ● modprobe@pstore_blk.service  loaded failed failed Load Kernel Module 
pstore_blk
  ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module 
pstore_zone
  ● modprobe@ramoops.service loaded failed failed Load Kernel Module 
ramoops

  This happens because of some changes to systemd-pstore.service that
  now has:

  After=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service
  Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service

  This causes too many tries of the modprobe services, that fail in the
  end with

  Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service:
  Start request repeated too quickly.

  Although we have seen this only on UC22, it potentially can affect
  classic systems as well, as systemd-pstore.service is re-tried there a
  few times too. See https://github.com/snapcore/core-base/issues/72 for
  more details.

  A fix for this is available upstream:
  
https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1

  [Test Plan]

  Start the device and check that there is no modprobe-pstore related
  failed service. This is racy, so a few tries will be needed to make
  sure things are fine.

  [Where problems could occur]

  The modprobe services are usually dependencies from other services, so
  it should be fine if the retry behavior is controlled by those other
  services. Risk should be small. If something goes wrong we might see a
  lot of restarts for these services.

  [Other Info]

  Testing should happen on UC22 too.

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


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

[Touch-packages] [Bug 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect

[Lukas Märdian]

The fix is already included in upstream v251 (Kinetic+)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1975667

Title:
  systemd-resolved does not reset DNS server and search domain list
  properly after VPN disconnect

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Networking components such as VPNs that rely on systemd-resolved's API
  to configure search domains may inadvertently leave the network
  configuration in a bad state. This is a result of a broken systemd-
  resolved API.

  [Test Plan]
  * On a jammy host, configure a couple search domains with resolvectl:

  $ resolvectl domain  search1.internal search2.internal
  $ resolvectl domain 

  * In any case, both domains should be displayed. Then, attempt to
  clear the configured domains:

  $ resolvectl domain  ""
  $ resolvectl domain 

  * On a patched system, the two domains should no longer be displayed.
  On an un-patched system, one of the domains will still be configured.

  [Where problems could occur]
  This patch touches the logic that configures search domains in 
systemd-resolved. If the patch caused regressions, it would be related to the 
set of configured search domains.

  [Original Description]

  Hi,
  in Ubuntu 21.10 I am facing a problem with DNS server list and search domain 
list is not properly reset back to the previous values after a VPN is 
disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded 
from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is 
not an "upgrade issue".

  I use this resolv.conf symlink:
  /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

  Actual behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS 
server and search domain entries left there, so it is not reset back properly.

  Desired behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected DNS servers and search domain list 
is restored to exactly the same state as was prior to the VPN connection.

  Steps for reproducing:
  1. Before VPN is connected this is the DNS server and search domain list in 
/etc/resolv.conf:

  nameserver 192.168.122.1
  search .

  2. Once the VPN is connected, we see there were VPN's DNS server and
  serach domain list entries added:

  nameserver 2xx.xx.xx.x0
  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain1.local domain2.internal domain3.internal

  3. After VPN disconnection, we see the DNS server and search domain
  list in /etc/resolv.conf is not restored to the state at point (1.)
  and some entries from VPN is being kept there:

  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain2.internal domain3.internal

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 06:06:05 2022
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.14.0-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.cha

[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail

[Lukas Märdian]

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

Title:
  Some modprobe loading services requested by the pstore service fail

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  In Progress

Bug description:
  [Impact]

  It has been detected that some modprobe services fail on UC22 after
  the jammy upgrade  249.11-0ubuntu3.4:

  $ systemctl --system --no-ask-password --no-pager list-units --state=failed
  Failed units:
UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module 
chromeos_pstore
  ● modprobe@efi_pstore.service  loaded failed failed Load Kernel Module 
efi_pstore
  ● modprobe@mtdpstore.service   loaded failed failed Load Kernel Module 
mtdpstore
  ● modprobe@pstore_blk.service  loaded failed failed Load Kernel Module 
pstore_blk
  ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module 
pstore_zone
  ● modprobe@ramoops.service loaded failed failed Load Kernel Module 
ramoops

  This happens because of some changes to systemd-pstore.service that
  now has:

  After=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service
  Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service

  This causes too many tries of the modprobe services, that fail in the
  end with

  Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service:
  Start request repeated too quickly.

  Although we have seen this only on UC22, it potentially can affect
  classic systems as well, as systemd-pstore.service is re-tried there a
  few times too. See https://github.com/snapcore/core-base/issues/72 for
  more details.

  A fix for this is available upstream:
  
https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1

  [Test Plan]

  Start the device and check that there is no modprobe-pstore related
  failed service. This is racy, so a few tries will be needed to make
  sure things are fine.

  [Where problems could occur]

  The modprobe services are usually dependencies from other services, so
  it should be fine if the retry behavior is controlled by those other
  services. Risk should be small. If something goes wrong we might see a
  lot of restarts for these services.

  [Other Info]

  Testing should happen on UC22 too.

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


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

[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

[Luís Cunha dos Reis Infante da Câmara]

Fixed in https://gitlab.com/ubports/development/core/lomiri-download-
manager/-/commit/df3665685da5cfb559a06016d4e0339c29b903e1 (2015), that
first appeared in version 0.9+15.10.20150723.2-0ubuntu1.

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

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in Canonical System Image:
  Fix Released
Status in Click Package Index:
  Fix Released
Status in Software Center Agent:
  Fix Released
Status in click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager source package in Vivid:
  New

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+subscriptions


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

[Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Lenin]

also we noticed that while the status page lags: 
https://people.canonical.com/~ubuntu-archive/phased-updates.html we already get 
phased updates that are not listed: 
Packages not installed from apt repositories (1):
   libmysqlclient21:amd64 (8.0.29-0ubuntu0.22.04.3)

reported by xymon monitoring system, hobbit plugins, apt plugin
specifically.

apt policy confirms it is part of phased updates.

this problem exists with apt 2.4.6 as well as 2.5.1 on Ubuntu 22.04

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

Title:
  apt phased out broken code, missing documentation to opt out

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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