[Touch-packages] [Bug 2064350] [NEW] pam_userdb.so is missing

[Thomas-Thomas]

Public bug reported:

The file is missing from libpam-modules.
This breaks, for example, existing vsftp configs if it is configured to use 
pam_userdb.so

Log:

vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: 
cannot open shared object file: No such file or directory
vsftpd: PAM adding faulty module: pam_userdb.so

Apparently there was a change which removed this in the past, and it
might be the removal has not been undone, while the package has been
released nevertheless.

http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog

  * For now remove libdb-dev so that libdb-dev can undergo time_t
transition.  That means this version of pam does not include
pam_userdb, which makes pam unsuitable for release.


$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

$ apt-cache policy libpam-modules
libpam-modules:
  Installed: 1.5.3-5ubuntu5
  Candidate: 1.5.3-5ubuntu5
  Version table:
 *** 1.5.3-5ubuntu5 500
500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

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

** Description changed:

  The file is missing from libpam-modules.
  This breaks, for example, existing vsftp configs if it is configured to use 
pam_userdb.so
  
  Log:
  
  vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: 
cannot open shared object file: No such file or directory
  vsftpd: PAM adding faulty module: pam_userdb.so
  
- 
- Apparently there was a change which removed this in the past, and it might be 
the removal has not been undone, while the package has been released 
nevertheless.
+ Apparently there was a change which removed this in the past, and it
+ might be the removal has not been undone, while the package has been
+ released nevertheless.
  
  
http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog
  
- 
-   * For now remove libdb-dev so that libdb-dev can undergo time_t
- transition.  That means this version of pam does not include
- pam_userdb, which makes pam unsuitable for release.
+   * For now remove libdb-dev so that libdb-dev can undergo time_t
+ transition.  That means this version of pam does not include
+ pam_userdb, which makes pam unsuitable for release.

** Description changed:

  The file is missing from libpam-modules.
  This breaks, for example, existing vsftp configs if it is configured to use 
pam_userdb.so
  
  Log:
  
  vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: 
cannot open shared object file: No such file or directory
  vsftpd: PAM adding faulty module: pam_userdb.so
  
  Apparently there was a change which removed this in the past, and it
  might be the removal has not been undone, while the package has been
  released nevertheless.
  
  
http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog
  
    * For now remove libdb-dev so that libdb-dev can undergo time_t
  transition.  That means this version of pam does not include
  pam_userdb, which makes pam unsuitable for release.
+ 
+ 
+ $ lsb_release -rd
+ No LSB modules are available.
+ Description:Ubuntu 24.04 LTS
+ Release:24.04
+ 
+ $ apt-cache policy libpam-modules
+ libpam-modules:
+   Installed: 1.5.3-5ubuntu5
+   Candidate: 1.5.3-5ubuntu5
+   Version table:
+  *** 1.5.3-5ubuntu5 500
+ 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  pam_userdb.so is missing

Status in pam package in Ubuntu:
  New

Bug description:
  The file is missing from libpam-modules.
  This breaks, for example, existing vsftp configs if it is configured to use 
pam_userdb.so

  Log:

  vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: 
cannot open shared object file: No such file or directory
  vsftpd: PAM adding faulty module: pam_userdb.so

  Apparently there was a change which removed this in the past, and it
  might be the removal has not been undone, while the package has been
  released nevertheless.

  
http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog

    * For now remove libdb-dev so that libdb-dev can undergo time_t
  transition.  That means this version of pam does not include
  pam_userdb, which makes pam unsuitable for release.


  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 24.04 LTS
  Release:24.04

  $ apt-cache policy libpam-modules
  libpam-modules:
Installed: 1.5.3-5ubuntu5
Candidate: 1.5.3-5ubuntu5
Version table:
   *** 1.5.3-5ubuntu5 500
  500 http://de.archive.ubuntu.com/ubuntu 

[Touch-packages] [Bug 2063078] [NEW] USB devices not detected

[Thomas Schweikle]

Public bug reported:

In some cases the kernel does detect a newly connected USB device, but
this device is never handled by systemd. The device handling shows up in
dmesg, but no device /dev/sd.. entries are created to access this newly
connected storage device.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Mon Apr 22 08:13:26 2024
InstallationDate: Installed on 2011-10-19 (4568 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic 
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
 --
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2019-04-27 (1822 days ago)
dmi.bios.date: 10/21/2013
dmi.bios.release: 2.15
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P643-M
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.ec.firmware.release: 1.19
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15:
dmi.product.family: TravelMate P643-M
dmi.product.name: TravelMate P643-M
dmi.product.sku: TravelMate P643-M_0681_2.15
dmi.product.version: V2.15
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug mantic

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

Title:
  USB devices not detected

Status in systemd package in Ubuntu:
  New

Bug description:
  In some cases the kernel does detect a newly connected USB device, but
  this device is never handled by systemd. The device handling shows up
  in dmesg, but no device /dev/sd.. entries are created to access this
  newly connected storage device.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Mon Apr 22 08:13:26 2024
  InstallationDate: Installed on 2011-10-19 (4568 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic 
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to mantic on 2019-04-27 (1822 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.release: 2.15
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go 

[Touch-packages] [Bug 2057927] Re: lxd vga console throws "Operation not permitted" error

[Thomas Parrott]

Please can you confirm if still an issue on lxd 5.21/stable as this is
the current supported version. Thanks

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

Title:
  lxd vga console throws "Operation not permitted" error

Status in apparmor package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Noble the lxd vga console doesn't work anymore. I
  am using the lxd latest/stable snap (5.20-f3dd836). When trying to
  attach a vga console to an lxd vm I get:

  unshare: write failed /proc/self/uid_map: Operation not permitted

  It seems to be related to apparmor, I can see a matching DENIAL
  message in dmesg:

  [ 4735.233989] audit: type=1400 audit(1710419600.517:300):
  apparmor="DENIED" operation="capable" class="cap"
  profile="unprivileged_userns" pid=13157 comm="unshare" capability=21
  capname="sys_admin"

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


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

[Touch-packages] [Bug 2060062] [NEW] libpam0g-dev cannot be installed

[Thomas Eyre]

Public bug reported:

When trying to install libpam0g-dev on noble numbat, I get the following
output:

The following packages have unmet dependencies:
 libpam0g-dev : Depends: libpam0g (= 1.5.2-9.1ubuntu3) but 1.5.3-5ubuntu3 is to 
be installed
E: Unable to correct problems, you have held broken packages.

I have a nightly build from a few days ago, but have been keeping it up
to date with the latest packages via apt full-upgrade.

LSB release output:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
Codename:   noble

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam0g-dev (not installed)
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  2 13:13:31 2024
InstallationDate: Installed on 2024-03-26 (7 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: pam
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  libpam0g-dev cannot be installed

Status in pam package in Ubuntu:
  New

Bug description:
  When trying to install libpam0g-dev on noble numbat, I get the
  following output:

  The following packages have unmet dependencies:
   libpam0g-dev : Depends: libpam0g (= 1.5.2-9.1ubuntu3) but 1.5.3-5ubuntu3 is 
to be installed
  E: Unable to correct problems, you have held broken packages.

  I have a nightly build from a few days ago, but have been keeping it
  up to date with the latest packages via apt full-upgrade.

  LSB release output:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04
  Codename: noble

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam0g-dev (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 13:13:31 2024
  InstallationDate: Installed on 2024-03-26 (7 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

** Project changed: coreutils => glibc

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in GLibC:
  New
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

** Bug watch added: Sourceware.org Bugzilla #31542
   https://sourceware.org/bugzilla/show_bug.cgi?id=31542

** Also affects: coreutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=31542
   Importance: Unknown
   Status: Unknown

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils:
  Unknown
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

Loading the test script output as text file in LibreOffice also shows
the same issue (screenshot attached). So, it is not a bug of Konsole or
XTerm. Probably, the 3-byte UTF-8 thousands separator character of the
locale is not useful. May be it should be a simple space, or a normal
UTF-8 non-breakable space (0xc2 0xa0, HTML "")?

** Attachment added: "Screenshot of the test script output loaded in 
LibreOffice"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+attachment/5758464/+files/Screenshot_20240322_222052.png

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

In a hexdump, printf seems to add a 3 characters for the thousands
separator:

#!/bin/sh
for l in de_DE en_US nb_NO nn_NO ; do
   echo "LC_NUMERIC=$l.UTF-8"
   for n in 1 100 1000 1 10 100 1000 ; do 
  LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'8d>" $n | hexdump -C
   done
done

Output:

LC_NUMERIC=nb_NO.UTF-8
  3c 20 20 20 20 20 20 20  31 3e|<   1>|
000a
  3c 20 20 20 20 20 31 30  30 3e|< 100>|
000a
  3c 20 31 e2 80 af 30 30  30 3e|< 1...000>|
000a
  3c 31 30 e2 80 af 30 30  30 3e|<10...000>|
000a
  3c 31 30 30 e2 80 af 30  30 30 3e |<100...000>|
000b
  3c 31 e2 80 af 30 30 30  e2 80 af 30 30 30 3e |<1...000...000>|
000f
  3c 31 30 e2 80 af 30 30  30 e2 80 af 30 30 30 3e  |<10...000...000>|
0010
LC_NUMERIC=nn_NO.UTF-8
  3c 20 20 20 20 20 20 20  31 3e|<   1>|
000a
  3c 20 20 20 20 20 31 30  30 3e|< 100>|
000a
  3c 20 31 e2 80 af 30 30  30 3e|< 1...000>|
000a
  3c 31 30 e2 80 af 30 30  30 3e|<10...000>|
000a
  3c 31 30 30 e2 80 af 30  30 30 3e |<100...000>|
000b
  3c 31 e2 80 af 30 30 30  e2 80 af 30 30 30 3e |<1...000...000>|
000f
  3c 31 30 e2 80 af 30 30  30 e2 80 af 30 30 30 3e  |<10...000...000>|
0010

However, both in Konsole as well as in XTerm, the issue occurs. So, the
bytes "0xe2 0x80 0xaf" inserted by printf for the thousands separator
seem to be incorrect? "0xe2 0x80 0xaf" is UTF-8 NARROW NO-BREAK SPACE ->
https://www.fileformat.info/info/ .unicode/char/202f/index.htm .

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

Launchpad suppresses the spaces, it seems. I attached a screenshot of
the terminal output to display the formatting issue.

** Attachment added: "Screenshot of the test script output"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+attachment/5758462/+files/Screenshot_20240322_213947.png

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2058775] [NEW] coreutils: printf formatting bug for nb_NO and nn_NO locales

[Thomas Dreibholz]

Public bug reported:

I just discovered a printf bug for at least the nb_NO and nn_NO locales
when printing numbers with thousands separator. To reproduce:

#!/bin/bash
for l in de_DE en_US nb_NO ; do
   echo "LC_NUMERIC=$l.UTF-8"
   for n in 1 100 1000 1 10 100 1000 ; do
  LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
   done
done

The expected output of "%'10d" is a right-formatted number string with
10 characters.

The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
and LC_NUMERIC=en_US.UTF-8:

LC_NUMERIC=de_DE.UTF-8
< 1>
<   100>
< 1.000>
<10.000>
<   100.000>
< 1.000.000>
<10.000.000>
LC_NUMERIC=en_US.UTF-8
< 1>
<   100>
< 1,000>
<10,000>
<   100,000>
< 1,000,000>
<10,000,000>

However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
formatting is wrong:

LC_NUMERIC=nb_NO.UTF-8
< 1>
<   100>
<   1 000>
<  10 000>
< 100 000>
<1 000 000>
<10 000 000>
LC_NUMERIC=nn_NO.UTF-8
< 1>
<   100>
<   1 000>
<  10 000>
< 100 000>
<1 000 000>
<10 000 000>

I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: coreutils 8.32-4.1ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Mar 22 21:33:13 2024
InstallationDate: Installed on 2022-11-29 (479 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Description changed:

  I just discovered a printf bug for at least the nb_NO and nn_NO locales
  when printing numbers with thousands separator. To reproduce:
  
  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
-echo "LC_NUMERIC=$l.UTF-8"
-for n in 1 100 1000 1 10 100 1000 ; do 
-   LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
-done
+    echo "LC_NUMERIC=$l.UTF-8"
+    for n in 1 100 1000 1 10 100 1000 ; do
+   LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
+    done
  done
  
  The expected output of "%'10d" is a right-formatted number string with
  10 characters.
  
  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:
  
  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>
  
  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:
  
  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  
  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  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 coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2058775

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  

[Touch-packages] [Bug 2056590] [NEW] No physical sound through speakers, settings show sound.

[Thomas Raes]

Public bug reported:

Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS.
Bluetooth headset does not give problems.
Microphone works, but bad quality.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 18:11:08 2024
InstallationDate: Installed on 2024-02-28 (9 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM3504DA.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM3504DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook 15 UM3504DA_UM3504DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698

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


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

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

Title:
  No physical sound through speakers, settings show sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS.
  Bluetooth headset does not give problems.
  Microphone works, but bad quality.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 18:11:08 2024
  InstallationDate: Installed on 2024-02-28 (9 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2023
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM3504DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM3504DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook 15 UM3504DA_UM3504DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698

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


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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Thomas Parrott]

I agree with Stéphane, it would be better to get the LXC_DEVEL issue
fixed quickly and then deal with the packaging refresh separately.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

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


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

[Touch-packages] [Bug 2049353] [NEW] wayland XWarpPointer backwards compability

[Thomas Enzenebner]

Public bug reported:

I'm not sure how to report this really as it's not a bug but still quite
severe. Bear with me as I'm a Unity dev mainly.

Unity uses function calls to X11 for setting mouse cursor positions.
Many games use this to lock the cursor to a certain position.

With no backwards compatibility to XWarpPointer these games will be broken in 
Wayland.
As there's little chance these games will be updated, the only possibility here 
is that Wayland supports this in some way.

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

** Information type changed from Private Security to Public

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

Title:
  wayland XWarpPointer backwards compability

Status in wayland package in Ubuntu:
  New

Bug description:
  I'm not sure how to report this really as it's not a bug but still
  quite severe. Bear with me as I'm a Unity dev mainly.

  Unity uses function calls to X11 for setting mouse cursor positions.
  Many games use this to lock the cursor to a certain position.

  With no backwards compatibility to XWarpPointer these games will be broken in 
Wayland.
  As there's little chance these games will be updated, the only possibility 
here is that Wayland supports this in some way.

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


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

[Touch-packages] [Bug 2047268] [NEW] package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1

[Sean Thomas Goul]

Public bug reported:

package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade:
installed systemd-boot package post-installation script subprocess
returned error exit status 1


upgraded stuff through sudo ap-get and it gave me this error, i was also 
copying music and browsing the web at the time

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: systemd-boot 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Dec 22 15:58:01 2023
DuplicateSignature:
 package:systemd-boot:253.5-1ubuntu6.1
 Setting up systemd-boot (253.5-1ubuntu6.1) ...
 dpkg: error processing package systemd-boot (--configure):
  installed systemd-boot package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed systemd-boot package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2023-12-20 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: systemd
Title: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: 
installed systemd-boot package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade:
  installed systemd-boot package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade:
  installed systemd-boot package post-installation script subprocess
  returned error exit status 1

  
  upgraded stuff through sudo ap-get and it gave me this error, i was also 
copying music and browsing the web at the time

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: systemd-boot 253.5-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Fri Dec 22 15:58:01 2023
  DuplicateSignature:
   package:systemd-boot:253.5-1ubuntu6.1
   Setting up systemd-boot (253.5-1ubuntu6.1) ...
   dpkg: error processing package systemd-boot (--configure):
installed systemd-boot package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed systemd-boot package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-12-20 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: systemd
  Title: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: 
installed systemd-boot package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

[Hywel Thomas]

Hello all,
I have been having the same problem (CUPS printer not showing/being available 
on Chromium), and seem to have fixed it as follows:-
 
Open CUPS administration page (localhost:631/admin)

under Server settings, enable 'Allow printing from the Internet'

   (I also have 'Allow remote administration' enabled, but I don't think
this matters)

   Click  'Change Settings'

The printer now appears in the Print dialog, under 'More...' options,
and can be selected (and, more importantly, will print!)

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

Title:
  Printer is not available in chromium snap

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer is not available in chromium. I had the same problem in firefox 
but fixed it with the following command:

sudo snap connect firefox:cups-control

  However this did not work with the chromium snap. I got the following
  error:

snap "chromium" has no plug named "cups-control"

  My printer is a network printer and is automatically detected by my
  Kubuntu install. It works out of the box with all native apps and
  flatpaks.

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


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

[Touch-packages] [Bug 2046650] [NEW] pcscd starts, then from applications all readers connected wont work

[Thomas Schweikle]

Public bug reported:

pcscd starts, then all readers connected are listed, but wont work.

starting pcsc_scan will never finish scanning, waiting on pcscd
returning data.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: pcscd 1.9.9-1ubuntu0.23.04.1
ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sun Dec 17 13:52:28 2023
InstallationDate: Installed on 2011-10-19 (4441 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pcsc-lite
UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar

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

Title:
  pcscd starts, then from applications all readers connected wont work

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  pcscd starts, then all readers connected are listed, but wont work.

  starting pcsc_scan will never finish scanning, waiting on pcscd
  returning data.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pcscd 1.9.9-1ubuntu0.23.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Dec 17 13:52:28 2023
  InstallationDate: Installed on 2011-10-19 (4441 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago)

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


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

[Touch-packages] [Bug 2046650] Re: pcscd starts, then from applications all readers connected wont work

[Thomas Schweikle]

# pcscd --foreground --info --color
 debuglog.c:386:DebugLogSetLevel() debug level=info
0040 pcscdaemon.c:356:main() Force colored logs
0381 pcscdaemon.c:666:main() pcsc-lite 1.9.9 daemon ready.
00013684 hotplug_libudev.c:421:HPAddDevice() Adding USB device: REINER SCT 
cyberJack wave
0068 readerfactory.c:1093:RFInitializeReader() Attempting startup of REINER 
SCT cyberJack wave (3428049512) 00 00 using 
/usr/lib/pcsc/drivers/libifd-cyberjack.bundle/Contents/Linux/libifd-cyberjack.so
CYBERJACK: Started
1582 readerfactory.c:968:RFBindFunctions() Loading IFD Handler 3.0

Same for some other readers. While pcscd ist starting they are reported,
but starting pcsc_scan just prints

$ pcsc_scan
PC/SC device scanner
V 1.6.2 (c) 2001-2022, Ludovic Rousseau 


then doing nothing more.

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

Title:
  pcscd starts, then from applications all readers connected wont work

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  pcscd starts, then all readers connected are listed, but wont work.

  starting pcsc_scan will never finish scanning, waiting on pcscd
  returning data.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pcscd 1.9.9-1ubuntu0.23.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Dec 17 13:52:28 2023
  InstallationDate: Installed on 2011-10-19 (4441 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago)

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


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

[Touch-packages] [Bug 2041491] Re: Provide an option to avoid the yaml NM backend

[Thomas]

I also would like to opt-out to the Netplan Backend in NM, without recomplie 
the whole stuff.
As already written on that page*, I dont like to be forced to that backend.

It could be such a easy job, if the original keyfile plugin would not be
patched that way it got - and if it could be compiled with a extra name
like keyfile-netplan or something.

So there could also be two plugin distibution packages, we can select to
install.

* https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
settings/32420/21

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

Title:
  Provide an option to avoid the yaml NM backend

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi, recently netplan added support for a yaml NM backend:

  https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
  settings/32420

  The rationale is that "the descriptive YAML layer is especially useful
  in cloud environments":

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556

  It's great that you care about that user group!
  Please also care for the rest of us that do not use cloud environments!

  For example, I routinely review, clone, backup or even directly edit
  the /etc/NetworkManager/system-connections files in my desktops and
  servers, in all distributions.

  Having an Ubuntu-specific way to do things will make things harder for
  me. I will have to learn a new Ubuntu-specific syntax, develop scripts
  and methods to convert my connections between distributions, I will
  need to discover and report bugs in the netplan <=> nm mapping etc...

  I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide 
a unified yaml-based experience for cloud-init etc.
  But Ubuntu is also great outside the cloud; please allow us to continue 
having a unified experience between distributions (i.e. directly using nm or 
systemd-networkd) without enforcing an Ubuntu-specific way of doing things 
(netplan) to us.

  For Ubuntu 24.04+, please provide an option to avoid the yaml NM
  backend, thank you very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+subscriptions


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

[Touch-packages] [Bug 2043753] [NEW] package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih1 whi

[Thomas Dunn]

Public bug reported:

was installing upgrade to ubuntu 20.04 and system reported crash.  no
visible signs other the message appeared.  Upgrade continued for a while
and then terminated.  I had libreoffice writer open at the time of the
error.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnih1 1.0.3-6ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252
Uname: Linux 5.4.0-166-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Nov 16 20:23:24 2023
DuplicateSignature:
 package:libnih1:1.0.3-6ubuntu2
 Unpacking libnetpbm10 (2:10.0-15.4) over (2:10.0-15.3build1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-eWw3bF/0718-libnih-dbus1_1.0.3-12build1_amd64.deb 
(--unpack):
  package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is 
not co-installable with libnih-dbus1 which has multiple installed instances
ErrorMessage: package libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: 
no' is not co-installable with libnih1 which has multiple installed instances
InstallationDate: Installed on 2014-04-03 (3514 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: libnih
Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not 
co-installable with libnih1 which has multiple installed instances
UpgradeStatus: Upgraded to jammy on 2023-11-17 (0 days ago)

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package
  libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-
  installable with libnih1 which has multiple installed instances

Status in libnih package in Ubuntu:
  New

Bug description:
  was installing upgrade to ubuntu 20.04 and system reported crash.  no
  visible signs other the message appeared.  Upgrade continued for a
  while and then terminated.  I had libreoffice writer open at the time
  of the error.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnih1 1.0.3-6ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252
  Uname: Linux 5.4.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 16 20:23:24 2023
  DuplicateSignature:
   package:libnih1:1.0.3-6ubuntu2
   Unpacking libnetpbm10 (2:10.0-15.4) over (2:10.0-15.3build1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eWw3bF/0718-libnih-dbus1_1.0.3-12build1_amd64.deb 
(--unpack):
package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is 
not co-installable with libnih-dbus1 which has multiple installed instances
  ErrorMessage: package libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: 
no' is not co-installable with libnih1 which has multiple installed instances
  InstallationDate: Installed on 2014-04-03 (3514 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: libnih
  Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not 
co-installable with libnih1 which has multiple installed instances
  UpgradeStatus: Upgraded to jammy on 2023-11-17 (0 days ago)

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


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

[Touch-packages] [Bug 2042749] [NEW] apt does not work with given convig files in new format

[Thomas Schweikle]

Public bug reported:

assume /etc/apt/sources.list.d/somerepo.list:

Types: deb
URIs: https://repo.vivaldi.com/stable/deb/
Suites: stable
Components: main
Architectures: amd64
Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg 
/etc/apt/trusted.gpg.d/4218647E.gpg


Then 'apt update' will produce:

# apt update
E: Type 'Types:' is not known on line 4 in source list 
/etc/apt/sources.list.d/vivaldi.list
E: The list of sources could not be read.

A new apt version is available. Would be nice to upgrade. At the moment
"man sources.list" does describe a file format not accepted by apt in
sources.list-files.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apt 2.7.3
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Nov  4 23:51:50 2023
InstallationDate: Installed on 2021-12-11 (693 days ago)
InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcEnviron:
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mantic

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

Title:
  apt does not work with given convig files in new format

Status in apt package in Ubuntu:
  New

Bug description:
  assume /etc/apt/sources.list.d/somerepo.list:

  Types: deb
  URIs: https://repo.vivaldi.com/stable/deb/
  Suites: stable
  Components: main
  Architectures: amd64
  Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg 
/etc/apt/trusted.gpg.d/4218647E.gpg

  
  Then 'apt update' will produce:

  # apt update
  E: Type 'Types:' is not known on line 4 in source list 
/etc/apt/sources.list.d/vivaldi.list
  E: The list of sources could not be read.

  A new apt version is available. Would be nice to upgrade. At the
  moment "man sources.list" does describe a file format not accepted by
  apt in sources.list-files.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Nov  4 23:51:50 2023
  InstallationDate: Installed on 2021-12-11 (693 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

@oibaf thanks, I reported it:

- https://gitlab.freedesktop.org/mesa/mesa/-/issues/1

(nice issue number by the way ☺️)

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/1

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

Title:
  OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
  with: *ERROR* Not enough memory for command submission!

Status in mesa package in Ubuntu:
  New

Bug description:
  I first thought the Radeon PRO W7600 was affected, in fact the
  affected GPU is the AMD FirePro S7150.

  See comment 3 and below:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3

  __

  When I run Unigine Superposition 1.1, it doesn't open any window and
  dmesg is filled with:

  ```
  [36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  ```

  printing new error log lines many time per second.

  Killing the Unigine Superposition process stops the log printing.

  There are more than one GPU in that system but the one used for
  rendering is a Radeon PRO W7600:

  ```
  Slot: 47:00.0
  Class:VGA compatible controller [0300]
  Vendor:   Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  Device:   Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
  SVendor:  Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  SDevice:  Device [0e0d]
  ProgIf:   00
  Driver:   amdgpu
  Module:   amdgpu
  IOMMUGroup:   58
  ```

  ```
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: AMD (0x1002)
  Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
  Version: 23.2.1
  Accelerated: yes
  Video memory: 8192MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.6
  Max compat profile version: 4.6
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  ```

  Other games like Unvanquished or Quake II RTX are working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libglapi-mesa 23.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Oct 14 14:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
   vhba/20211218, 6.2.0-33-generic, x86_64: installed
   vhba/20211218, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  dmi.bios.release: 5.23
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: WRX80SU8-F6
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: 

[Touch-packages] [Bug 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

I reproduce the bug with current Mesa
(d97427f41c1603db2f657b5d9c3f91a97f74b1c0) and LLVM 16.0.6. I don't know
if the bug is on drm side or on Mesa side.

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

Title:
  OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
  with: *ERROR* Not enough memory for command submission!

Status in mesa package in Ubuntu:
  New

Bug description:
  I first thought the Radeon PRO W7600 was affected, in fact the
  affected GPU is the AMD FirePro S7150.

  See comment 3 and below:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3

  __

  When I run Unigine Superposition 1.1, it doesn't open any window and
  dmesg is filled with:

  ```
  [36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  ```

  printing new error log lines many time per second.

  Killing the Unigine Superposition process stops the log printing.

  There are more than one GPU in that system but the one used for
  rendering is a Radeon PRO W7600:

  ```
  Slot: 47:00.0
  Class:VGA compatible controller [0300]
  Vendor:   Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  Device:   Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
  SVendor:  Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  SDevice:  Device [0e0d]
  ProgIf:   00
  Driver:   amdgpu
  Module:   amdgpu
  IOMMUGroup:   58
  ```

  ```
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: AMD (0x1002)
  Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
  Version: 23.2.1
  Accelerated: yes
  Video memory: 8192MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.6
  Max compat profile version: 4.6
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  ```

  Other games like Unvanquished or Quake II RTX are working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libglapi-mesa 23.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Oct 14 14:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
   vhba/20211218, 6.2.0-33-generic, x86_64: installed
   vhba/20211218, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  dmi.bios.release: 5.23
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: WRX80SU8-F6
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  

[Touch-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

I reproduce the same issue if I just do:

```
DRI_PRIME=1 glxinfo -B
name of display: :1
```

Which means the fault happens when using the AMD FirePro S7150, NOT the
AMD Radeon PRO W7600.

Maybe for some reasons Unigine Superposition tries to use all GPUs
available?

So, the bug is now easier to reproduce, it is affecting the AMD FirePro
S7150, and a glxinfo is enough.

** Summary changed:

- Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not 
enough memory for command submission!
+ OpenGL applications don't run on AMD FirePro S7150 and fills dmesg with: 
*ERROR* Not enough memory for command submission!

** Description changed:

+ I first thought the Radeon PRO W7600 was affected, in fact the affected
+ GPU is the AMD FirePro S7150.
+ 
+ See comment 3 and below:
+ https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
+ 
+ __
+ 
  When I run Unigine Superposition 1.1, it doesn't open any window and
  dmesg is filled with:
  
  ```
  [36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  ```
  
  printing new error log lines many time per second.
  
  Killing the Unigine Superposition process stops the log printing.
  
  There are more than one GPU in that system but the one used for
  rendering is a Radeon PRO W7600:
  
  ```
  Slot: 47:00.0
  Class:VGA compatible controller [0300]
  Vendor:   Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  Device:   Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
  SVendor:  Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  SDevice:  Device [0e0d]
  ProgIf:   00
  Driver:   amdgpu
  Module:   amdgpu
  IOMMUGroup:   58
  ```
  
  ```
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: AMD (0x1002)
  Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
  Version: 23.2.1
  Accelerated: yes
  Video memory: 8192MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.6
  Max compat profile version: 4.6
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  ```
  
  Other games like Unvanquished or Quake II RTX are working correctly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libglapi-mesa 23.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Oct 14 14:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
   vhba/20211218, 6.2.0-33-generic, x86_64: installed
   vhba/20211218, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  dmi.bios.release: 5.23
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: WRX80SU8-F6
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

** Description changed:

  When I run Unigine Superposition 1.1, it doesn't open any window and
  dmesg is filled with:
  
  ```
  [36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  ```
  
  printing new error log lines many time per second.
  
  Killing the Unigine Superposition process stops the log printing.
  
- There are more then one GPU in that system but the one used for
+ There are more than one GPU in that system but the one used for
  rendering is a Radeon PRO W7600:
  
  ```
  Slot: 47:00.0
  Class:VGA compatible controller [0300]
  Vendor:   Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  Device:   Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
  SVendor:  Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  SDevice:  Device [0e0d]
  ProgIf:   00
  Driver:   amdgpu
  Module:   amdgpu
  IOMMUGroup:   58
  ```
  
  ```
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: AMD (0x1002)
  Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
  Version: 23.2.1
  Accelerated: yes
  Video memory: 8192MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.6
  Max compat profile version: 4.6
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  ```
  
  Other games like Unvanquished or Quake II RTX are working correctly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libglapi-mesa 23.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Oct 14 14:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
   vhba/20211218, 6.2.0-33-generic, x86_64: installed
   vhba/20211218, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  dmi.bios.release: 5.23
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: WRX80SU8-F6
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  

[Touch-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

In the log file you may see notice of some amdgpu-pro OpenCL components
like ROCm ROCr OpenCL or Legacy Orca OpenCL, there is no amdgpu-pro
OpenGL or dkms module installed though. Removing entirely the amdgpu-pro
OpenCL packages produce the same bug anyway. The contrary would have
been surprising since I assume Superposition to be an OpenGL benchmark
and to not make use of OpenCL, but to be 100% sure I removed all those
amdgpu-pro packages and I get the same bug with stock Ubuntu anyway.

** Summary changed:

- Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough 
memory for command submission!
+ Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not 
enough memory for command submission!

** Description changed:

  When I run Unigine Superposition 1.1, it doesn't open any window and
  dmesg is filled with:
  
  ```
  [36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  [36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
  ```
  
  printing new error log lines many time per second.
  
  Killing the Unigine Superposition process stops the log printing.
  
- There is multiple GPU in that system but the one used for rendering is a
- Radeon PRO W7600:
- 
+ There are more then one GPU in that system but the one used for
+ rendering is a Radeon PRO W7600:
  
  ```
  Slot: 47:00.0
  Class:VGA compatible controller [0300]
  Vendor:   Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  Device:   Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
  SVendor:  Advanced Micro Devices, Inc. [AMD/ATI] [1002]
  SDevice:  Device [0e0d]
  ProgIf:   00
  Driver:   amdgpu
  Module:   amdgpu
  IOMMUGroup:   58
  ```
  
  ```
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
- Vendor: AMD (0x1002)
- Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
- Version: 23.2.1
- Accelerated: yes
- Video memory: 8192MB
- Unified memory: no
- Preferred profile: core (0x1)
- Max core profile version: 4.6
- Max compat profile version: 4.6
- Max GLES1 profile version: 1.1
- Max GLES[23] profile version: 3.2
+ Vendor: AMD (0x1002)
+ Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
+ Version: 23.2.1
+ Accelerated: yes
+ Video memory: 8192MB
+ Unified memory: no
+ Preferred profile: core (0x1)
+ Max core profile version: 4.6
+ Max compat profile version: 4.6
+ Max GLES1 profile version: 1.1
+ Max GLES[23] profile version: 3.2
  ```
  
  Other games like Unvanquished or Quake II RTX are working correctly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libglapi-mesa 23.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Oct 14 14:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
-  v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
-  vhba/20211218, 6.2.0-33-generic, x86_64: installed
-  vhba/20211218, 6.5.0-9-generic, x86_64: installed
+  v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
+  vhba/20211218, 6.2.0-33-generic, x86_64: installed
+  vhba/20211218, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  

[Touch-packages] [Bug 2039352] [NEW] Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!

[Thomas Debesse]

Public bug reported:

When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:

```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for 
command submission!
```

printing new error log lines many time per second.

Killing the Unigine Superposition process stops the log printing.

There is multiple GPU in that system but the one used for rendering is a
Radeon PRO W7600:


```
Slot:   47:00.0
Class:  VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor:Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice:Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```

```
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54, 
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```

Other games like Unvanquished or Quake II RTX are working correctly.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: 
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!)
 vhba/20211218, 6.2.0-33-generic, x86_64: installed
 vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

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

[Touch-packages] [Bug 2038892] [NEW] How To Contact +1(202-960-2084) McAfee Customer Service Number?

[Goodrich Thomas]

Private bug reported:

o contact McAfee Customer Service Phone Number, you can follow these
steps:

Visit the McAfee Website: Start by going to the official McAfee website.

Navigate to Support: Look for a “Support” or “Contact Us” link on the
website. This is typically found at the top or bottom of the homepage.

Choose Your Product: Select the McAfee product you need assistance with.
They offer various security solutions, so make sure to pick the right
one.

Access the Help Center: Many common issues can be resolved by searching
the McAfee Help Center. Try entering your problem or question in the
search bar.

Contact Options: If you can’t find a solution in the Help Center, look
for contact options. This may include phone numbers, live chat, or email
support. Click on the option that suits you best.

Provide Information: When contacting McAfee, be prepared to provide
information like your product key, account details, and a clear
description of your issue.

Follow Instructions: Follow the instructions provided by McAfee’s
customer support team. They may guide you through troubleshooting steps
or offer a solution tailored to your problem.

Record Reference Numbers: If you speak to a customer service
representative or open a support ticket, make sure to record any
reference numbers or case IDs for future reference.

Remember that McAfee’s contact options may vary depending on your
location and the specific product you’re using. Always verify the
contact details on their official website to ensure you’re reaching out
to legitimate customer support.

** Affects: null-and-void
 Importance: Undecided
 Status: Invalid

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

Title:
  How To Contact +1(202-960-2084) McAfee Customer Service Number?

Status in NULL Project:
  Invalid

Bug description:
  o contact McAfee Customer Service Phone Number, you can follow these
  steps:

  Visit the McAfee Website: Start by going to the official McAfee
  website.

  Navigate to Support: Look for a “Support” or “Contact Us” link on the
  website. This is typically found at the top or bottom of the homepage.

  Choose Your Product: Select the McAfee product you need assistance
  with. They offer various security solutions, so make sure to pick the
  right one.

  Access the Help Center: Many common issues can be resolved by
  searching the McAfee Help Center. Try entering your problem or
  question in the search bar.

  Contact Options: If you can’t find a solution in the Help Center, look
  for contact options. This may include phone numbers, live chat, or
  email support. Click on the option that suits you best.

  Provide Information: When contacting McAfee, be prepared to provide
  information like your product key, account details, and a clear
  description of your issue.

  Follow Instructions: Follow the instructions provided by McAfee’s
  customer support team. They may guide you through troubleshooting
  steps or offer a solution tailored to your problem.

  Record Reference Numbers: If you speak to a customer service
  representative or open a support ticket, make sure to record any
  reference numbers or case IDs for future reference.

  Remember that McAfee’s contact options may vary depending on your
  location and the specific product you’re using. Always verify the
  contact details on their official website to ensure you’re reaching
  out to legitimate customer support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/2038892/+subscriptions


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

[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again

[Thomas Bechtold]

Ok. Thanks for clarification. With that I think we can continue to get
https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-
rootfs-1/+merge/452352 merged.

But I still find this behavior confusing/buggy. I can still use
"debconf-show openssh-server" and see the password-authentication entry.
And that entry is out-of-sync with the real configuration. That's a bug
imo given that the behavior is not documented in README.Debian.gz .

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

Title:
  dpkg-reconfigure openssh-server doesn't ask questions again

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server does provide a couple of configuration options:

  [~]$ sudo debconf-get-selections |grep openssh-server
  openssh-serveropenssh-server/listenstream-may-failerror   
  openssh-serveropenssh-server/password-authentication  boolean true
  openssh-serveropenssh-server/permit-root-loginboolean true

  
  I want to change those options now interactively but nothing I tried worked 
and showed a dialog:

  [~]$ sudo dpkg-reconfigure -p low openssh-server  
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

  [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.


  But the documentation (https://manpages.debian.org/testing/debconf-
  doc/debconf.7.en.html#Reconfiguring_packages) does state that those
  commands should ask those questions again.

  
  p.s. also tried with a lxc debian-sid container and had the same problem 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.3p1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 10:35:33 2023
  InstallationDate: Installed on 2023-05-10 (142 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago)

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


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

[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again

[Thomas Bechtold]

looks like there's no db_input/db_go call in the openssh-server.config
file. Is that by intention?

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

Title:
  dpkg-reconfigure openssh-server doesn't ask questions again

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server does provide a couple of configuration options:

  [~]$ sudo debconf-get-selections |grep openssh-server
  openssh-serveropenssh-server/listenstream-may-failerror   
  openssh-serveropenssh-server/password-authentication  boolean true
  openssh-serveropenssh-server/permit-root-loginboolean true

  
  I want to change those options now interactively but nothing I tried worked 
and showed a dialog:

  [~]$ sudo dpkg-reconfigure -p low openssh-server  
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

  [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.


  But the documentation (https://manpages.debian.org/testing/debconf-
  doc/debconf.7.en.html#Reconfiguring_packages) does state that those
  commands should ask those questions again.

  
  p.s. also tried with a lxc debian-sid container and had the same problem 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.3p1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 10:35:33 2023
  InstallationDate: Installed on 2023-05-10 (142 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago)

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


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

[Touch-packages] [Bug 2037703] [NEW] dpkg-reconfigure openssh-server doesn't ask questions again

[Thomas Bechtold]

Public bug reported:

openssh-server does provide a couple of configuration options:

[~]$ sudo debconf-get-selections |grep openssh-server
openssh-server  openssh-server/listenstream-may-failerror   
openssh-server  openssh-server/password-authentication  boolean true
openssh-server  openssh-server/permit-root-loginboolean true


I want to change those options now interactively but nothing I tried worked and 
showed a dialog:

[~]$ sudo dpkg-reconfigure -p low openssh-server  
Warning: Stopping ssh.service, but it can still be activated by:
  ssh.socket
rescue-ssh.target is a disabled or a static unit not running, not starting it.

[~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
Warning: Stopping ssh.service, but it can still be activated by:
  ssh.socket
rescue-ssh.target is a disabled or a static unit not running, not starting it.


But the documentation (https://manpages.debian.org/testing/debconf-
doc/debconf.7.en.html#Reconfiguring_packages) does state that those
commands should ask those questions again.


p.s. also tried with a lxc debian-sid container and had the same problem there.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: openssh-server 1:9.3p1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 29 10:35:33 2023
InstallationDate: Installed on 2023-05-10 (142 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: openssh
UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago)

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


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

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

Title:
  dpkg-reconfigure openssh-server doesn't ask questions again

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server does provide a couple of configuration options:

  [~]$ sudo debconf-get-selections |grep openssh-server
  openssh-serveropenssh-server/listenstream-may-failerror   
  openssh-serveropenssh-server/password-authentication  boolean true
  openssh-serveropenssh-server/permit-root-loginboolean true

  
  I want to change those options now interactively but nothing I tried worked 
and showed a dialog:

  [~]$ sudo dpkg-reconfigure -p low openssh-server  
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.

  [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server
  Warning: Stopping ssh.service, but it can still be activated by:
ssh.socket
  rescue-ssh.target is a disabled or a static unit not running, not starting it.


  But the documentation (https://manpages.debian.org/testing/debconf-
  doc/debconf.7.en.html#Reconfiguring_packages) does state that those
  commands should ask those questions again.

  
  p.s. also tried with a lxc debian-sid container and had the same problem 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.3p1-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 10:35:33 2023
  InstallationDate: Installed on 2023-05-10 (142 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago)

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


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

[Touch-packages] [Bug 2037156] [NEW] initramfs-tools 0.142ubuntu12 fails on upgrade: wrong multiarch libdir Edit

[Thomas Schiex]

Public bug reported:

I just upgraded my system from Lunar to Mantic. initramfs is
systematically producing messages such as:

  E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.

Looking into the corresponding bash script shows that the penultimate
line produces an incorrect result:

  multiarch_dir=$(ldd /usr/sbin/dhcpcd | awk '/libc.so./ { print $3 }' |
cut -f3 -d/)

stores "lib" instead of x86_64-linux-gnu in my case.

the correct line (tested) should be:

  multiarch_dir=$(ldd /usr/sbin/dhcpcd | awk '/libc.so./ { print $3 }' |
cut -f4 -d/)


since ldd produces 

libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6
(0x7f5baec0)

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

** Attachment added: "Corrected /usr/share/initramfs-tools/hooks/dhcpcd file"
   https://bugs.launchpad.net/bugs/2037156/+attachment/5703688/+files/dhcpcd

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

Title:
  initramfs-tools 0.142ubuntu12 fails on upgrade: wrong multiarch libdir
  Edit

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I just upgraded my system from Lunar to Mantic. initramfs is
  systematically producing messages such as:

E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.

  Looking into the corresponding bash script shows that the penultimate
  line produces an incorrect result:

multiarch_dir=$(ldd /usr/sbin/dhcpcd | awk '/libc.so./ { print $3 }'
  | cut -f3 -d/)

  stores "lib" instead of x86_64-linux-gnu in my case.

  the correct line (tested) should be:

multiarch_dir=$(ldd /usr/sbin/dhcpcd | awk '/libc.so./ { print $3 }'
  | cut -f4 -d/)

  
  since ldd produces 

  libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6
  (0x7f5baec0)

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


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

[Touch-packages] [Bug 2033663] Re: iptables fails to parse "-i +" correctly

[Thomas Sthlm]

@oibaf
Bug now filed with netfilter:
https://bugzilla.netfilter.org/show_bug.cgi?id=1702

** Bug watch added: bugzilla.netfilter.org/ #1702
   http://bugzilla.netfilter.org/show_bug.cgi?id=1702

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

Title:
  iptables fails to parse "-i +" correctly

Status in iptables package in Ubuntu:
  New
Status in iptables-persistent package in Ubuntu:
  New

Bug description:
  I recently started to use Ubuntu 22.04 LTS on a server and created a simple 
ipables firewall for it.
  (For Ubuntu 20.04 that I have used before, the below seems fine.)

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  # apt-cache policy iptables-persistent
  iptables-persistent:
Installed: 1.0.16
Candidate: 1.0.16
Version table:
   *** 1.0.16 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy iptables
  iptables:
Installed: 1.8.7-1ubuntu5.1
Candidate: 1.8.7-1ubuntu5.1
Version table:
   *** 1.8.7-1ubuntu5.1 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.7-1ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  --
  ISSUE:
  If I enter a simple iptables rule that uses the "-i +" input interface 
wildcard thing in it, but note that I don't give any interface namestring 
"prefix" before the "+" - for example:
  iptables -A INPUT -i + -d 192.168.1.10 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.11 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.12 -j DROP 

  Then printouts of both iptables-save and iptables -L -n -v will show weird 
non-ascii/non-printable characters where the interfaces are supposed to be 
printed!
  The result for my rule example above shows as:
  -A INPUT -d 192.168.80.10/32 -i ˬP
  + -j DROP
  -A INPUT -d 192.168.80.11/32 -i À¨P�+ -j DROP
  -A INPUT -d 192.168.80.12/32 -i ˬP + -j DROP
  (The garbage chars are in hex \c0\a8\50\0a, \c0\a8\50\0b, \c0\a8\50\0c 
respectively. Note the \0a newline char breaking up the printout into two lines 
for the first rule.)

  The garbage characters makes 
  "iptables-save > /etc/iptables/rules.v4" 
  followed up with 
  "iptables-restore < /etc/iptables/rules.v4"
  to fail!

  I discovered that if the rule also includes some "protocol"
  constraints like "-p tcp -m tcp --dport 123" then iptables
  parses/prints the rule seemingly ok, but for "simpler" rules iptables
  gets confused.

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


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

[Touch-packages] [Bug 2033663] Re: iptables fails to parse "-i +" correctly

[Thomas Sthlm]

@oibaf
Thanx,

Didn't search super-much but I did find a somewhat similar issue:
https://bugzilla.netfilter.org/show_bug.cgi?id=1085

That bug was about letting through -i interface strings with typos/not
allowed characters when using the + wildcard, for example: iptables -A
INPUT -i "et h+" ...

They have apparently been into that code before to bugfix, but not
tested the case with + only / "null-string" interface name as prefix
before the + wildcard.

Guess that I will report it to netfilter's bugzilla.

** Bug watch added: bugzilla.netfilter.org/ #1085
   http://bugzilla.netfilter.org/show_bug.cgi?id=1085

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

Title:
  iptables fails to parse "-i +" correctly

Status in iptables package in Ubuntu:
  New
Status in iptables-persistent package in Ubuntu:
  New

Bug description:
  I recently started to use Ubuntu 22.04 LTS on a server and created a simple 
ipables firewall for it.
  (For Ubuntu 20.04 that I have used before, the below seems fine.)

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  # apt-cache policy iptables-persistent
  iptables-persistent:
Installed: 1.0.16
Candidate: 1.0.16
Version table:
   *** 1.0.16 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy iptables
  iptables:
Installed: 1.8.7-1ubuntu5.1
Candidate: 1.8.7-1ubuntu5.1
Version table:
   *** 1.8.7-1ubuntu5.1 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.7-1ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  --
  ISSUE:
  If I enter a simple iptables rule that uses the "-i +" input interface 
wildcard thing in it, but note that I don't give any interface namestring 
"prefix" before the "+" - for example:
  iptables -A INPUT -i + -d 192.168.1.10 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.11 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.12 -j DROP 

  Then printouts of both iptables-save and iptables -L -n -v will show weird 
non-ascii/non-printable characters where the interfaces are supposed to be 
printed!
  The result for my rule example above shows as:
  -A INPUT -d 192.168.80.10/32 -i ˬP
  + -j DROP
  -A INPUT -d 192.168.80.11/32 -i À¨P�+ -j DROP
  -A INPUT -d 192.168.80.12/32 -i ˬP + -j DROP
  (The garbage chars are in hex \c0\a8\50\0a, \c0\a8\50\0b, \c0\a8\50\0c 
respectively. Note the \0a newline char breaking up the printout into two lines 
for the first rule.)

  The garbage characters makes 
  "iptables-save > /etc/iptables/rules.v4" 
  followed up with 
  "iptables-restore < /etc/iptables/rules.v4"
  to fail!

  I discovered that if the rule also includes some "protocol"
  constraints like "-p tcp -m tcp --dport 123" then iptables
  parses/prints the rule seemingly ok, but for "simpler" rules iptables
  gets confused.

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


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

[Touch-packages] [Bug 2033663] Re: iptables fails to parse "-i +" correctly

[Thomas Sthlm]

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

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

Title:
  iptables fails to parse "-i +" correctly

Status in iptables package in Ubuntu:
  New
Status in iptables-persistent package in Ubuntu:
  New

Bug description:
  I recently started to use Ubuntu 22.04 LTS on a server and created a simple 
ipables firewall for it.
  (For Ubuntu 20.04 that I have used before, the below seems fine.)

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  # apt-cache policy iptables-persistent
  iptables-persistent:
Installed: 1.0.16
Candidate: 1.0.16
Version table:
   *** 1.0.16 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy iptables
  iptables:
Installed: 1.8.7-1ubuntu5.1
Candidate: 1.8.7-1ubuntu5.1
Version table:
   *** 1.8.7-1ubuntu5.1 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.7-1ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  --
  ISSUE:
  If I enter a simple iptables rule that uses the "-i +" input interface 
wildcard thing in it, but note that I don't give any interface namestring 
"prefix" before the "+" - for example:
  iptables -A INPUT -i + -d 192.168.1.10 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.11 -j DROP 
  iptables -A INPUT -i + -d 192.168.1.12 -j DROP 

  Then printouts of both iptables-save and iptables -L -n -v will show weird 
non-ascii/non-printable characters where the interfaces are supposed to be 
printed!
  The result for my rule example above shows as:
  -A INPUT -d 192.168.80.10/32 -i ˬP
  + -j DROP
  -A INPUT -d 192.168.80.11/32 -i À¨P�+ -j DROP
  -A INPUT -d 192.168.80.12/32 -i ˬP + -j DROP
  (The garbage chars are in hex \c0\a8\50\0a, \c0\a8\50\0b, \c0\a8\50\0c 
respectively. Note the \0a newline char breaking up the printout into two lines 
for the first rule.)

  The garbage characters makes 
  "iptables-save > /etc/iptables/rules.v4" 
  followed up with 
  "iptables-restore < /etc/iptables/rules.v4"
  to fail!

  I discovered that if the rule also includes some "protocol"
  constraints like "-p tcp -m tcp --dport 123" then iptables
  parses/prints the rule seemingly ok, but for "simpler" rules iptables
  gets confused.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[thomas]

Is there any progress on this issue? (Progress as in: works for end-
users as it did the last 20 years…)

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 2023463] [NEW] Cannot remove items from side panel

[Mark Thomas]

Public bug reported:

Only an annoying bug

I cannot remove the attached from my menu on the side panel.

Other items are removed ok.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 11 14:22:20 2023
DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c]
InstallationDate: Installed on 2023-02-08 (123 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Acer Aspire F5-572
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago)
dmi.bios.date: 05/25/2017
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Zoro_SL
dmi.board.vendor: Acer
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 2.70
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18:
dmi.product.family: SKL
dmi.product.name: Aspire F5-572
dmi.product.sku: Aspire F5-572_100C_1.18
dmi.product.version: V1.18
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kinetic ubuntu

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

Title:
  Cannot remove items from side panel

Status in xorg package in Ubuntu:
  New

Bug description:
  Only an annoying bug

  I cannot remove the attached from my menu on the side panel.

  Other items are removed ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 11 14:22:20 2023
  DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:100c]
  InstallationDate: Installed on 2023-02-08 (123 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Aspire F5-572
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago)
  dmi.bios.date: 05/25/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Zoro_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.70
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18:
  dmi.product.family: SKL
  dmi.product.name: Aspire F5-572
  dmi.product.sku: Aspire F5-572_100C_1.18
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer
  

[Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()

[Thomas Hoffmann]

Hello Adrien,

you are right. Carbon seemed to grab the python module from the pip
installation, not from the repository.

"pip remove pyOpenSSL" solved the issue.

The repo file /usr/lib/python3/dist-packages/OpenSSL/crypto.py has the same
reference to OpenSSL_add_all_algorithms but it doesn't seem to cause a problem.

@Simon: I also removed "cryptography" via pip because it was installed from the 
Repo and by pip.
Not sure which program caused it, but everything is fine now.

Thank you very much for your quick help!
Much appreciated!

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

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

Title:
  carbon-cache not starting because python3-openssl throws error
  _lib.OpenSSL_add_all_algorithms()

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  1) ubuntu release:
  We are using Ubuntu 22.04 LTS:
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2) packages:
  We have the following packages installed:
  graphite-carbon/jammy,jammy,now 1.1.7-1 all
  python3-openssl/jammy,jammy,now 21.0.0-1 all
  OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

  3) Expected result
  The carbon cache should start if all dependent packages are from the same 
repository.

  4) observed issue
  Since the last OpenSSL update this week via the ubuntu repository, the 
carbon-cache service is not starting any more.
  The error message is:

  Jun  7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache...
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call 
last):
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File "/usr/bin/carbon-cache", 
line 28, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import 
run_twistd_plugin  # noqa
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/lib/python3/dist-packages/carbon/util.py", line 19, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, 
SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: 
_lib.OpenSSL_add_all_algorithms()
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' 
has no attribute 'OpenSSL_add_all_algorithms'

  According to 
https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769
 the python module pyopenssl needs to be > 22.1.0
  Ubuntu 22.04 LTS ships with version 22.0.0.
  It seems, that the python3-openssl is not working well with the most recent 
openSSL version of Ubuntu 22.04.

  I could update pyopenssl with pip but this might break the update
  mechanism of apt.

  Any suggestions are appreciated, thanks!
  If I can provide further information, just let me know.

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


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

[Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()

[Thomas Hoffmann]

Short additional note:
It's similar to https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477
My expectance would be: If everything comes from the same ubuntu repository, I 
get a consistent set of tools which work together.
I am aware that this is not always possible but maybe there is a chance to 
backport the fix for this issue.

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

Title:
  carbon-cache not starting because python3-openssl throws error
  _lib.OpenSSL_add_all_algorithms()

Status in openssl package in Ubuntu:
  New

Bug description:
  1) ubuntu release:
  We are using Ubuntu 22.04 LTS:
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2) packages:
  We have the following packages installed:
  graphite-carbon/jammy,jammy,now 1.1.7-1 all
  python3-openssl/jammy,jammy,now 21.0.0-1 all
  OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

  3) Expected result
  The carbon cache should start if all dependent packages are from the same 
repository.

  4) observed issue
  Since the last OpenSSL update this week via the ubuntu repository, the 
carbon-cache service is not starting any more.
  The error message is:

  Jun  7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache...
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call 
last):
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File "/usr/bin/carbon-cache", 
line 28, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import 
run_twistd_plugin  # noqa
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/lib/python3/dist-packages/carbon/util.py", line 19, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, 
SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: 
_lib.OpenSSL_add_all_algorithms()
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' 
has no attribute 'OpenSSL_add_all_algorithms'

  According to 
https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769
 the python module pyopenssl needs to be > 22.1.0
  Ubuntu 22.04 LTS ships with version 22.0.0.
  It seems, that the python3-openssl is not working well with the most recent 
openSSL version of Ubuntu 22.04.

  I could update pyopenssl with pip but this might break the update
  mechanism of apt.

  Any suggestions are appreciated, thanks!
  If I can provide further information, just let me know.

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


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

[Touch-packages] [Bug 2023165] [NEW] carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()

[Thomas Hoffmann]

Public bug reported:

1) ubuntu release:
We are using Ubuntu 22.04 LTS:
Description:Ubuntu 22.04.2 LTS
Release:22.04

2) packages:
We have the following packages installed:
graphite-carbon/jammy,jammy,now 1.1.7-1 all
python3-openssl/jammy,jammy,now 21.0.0-1 all
OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

3) Expected result
The carbon cache should start if all dependent packages are from the same 
repository.

4) observed issue
Since the last OpenSSL update this week via the ubuntu repository, the 
carbon-cache service is not starting any more.
The error message is:

Jun  7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache...
Jun  7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last):
Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File "/usr/bin/carbon-cache", 
line 28, in 
Jun  7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import 
run_twistd_plugin  # noqa
Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/lib/python3/dist-packages/carbon/util.py", line 19, in 
Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL
Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in 

Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, 
SSL
Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in 

Jun  7 09:23:00 icinga2 carbon-cache[191566]: 
_lib.OpenSSL_add_all_algorithms()
Jun  7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has 
no attribute 'OpenSSL_add_all_algorithms'

According to 
https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769
 the python module pyopenssl needs to be > 22.1.0
Ubuntu 22.04 LTS ships with version 22.0.0.
It seems, that the python3-openssl is not working well with the most recent 
openSSL version of Ubuntu 22.04.

I could update pyopenssl with pip but this might break the update
mechanism of apt.

Any suggestions are appreciated, thanks!
If I can provide further information, just let me know.

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

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

Title:
  carbon-cache not starting because python3-openssl throws error
  _lib.OpenSSL_add_all_algorithms()

Status in openssl package in Ubuntu:
  New

Bug description:
  1) ubuntu release:
  We are using Ubuntu 22.04 LTS:
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2) packages:
  We have the following packages installed:
  graphite-carbon/jammy,jammy,now 1.1.7-1 all
  python3-openssl/jammy,jammy,now 21.0.0-1 all
  OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

  3) Expected result
  The carbon cache should start if all dependent packages are from the same 
repository.

  4) observed issue
  Since the last OpenSSL update this week via the ubuntu repository, the 
carbon-cache service is not starting any more.
  The error message is:

  Jun  7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache...
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call 
last):
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File "/usr/bin/carbon-cache", 
line 28, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import 
run_twistd_plugin  # noqa
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/lib/python3/dist-packages/carbon/util.py", line 19, in 
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, 
SSL
  Jun  7 09:23:00 icinga2 carbon-cache[191566]:   File 
"/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in 

  Jun  7 09:23:00 icinga2 carbon-cache[191566]: 
_lib.OpenSSL_add_all_algorithms()
  Jun  7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' 
has no attribute 'OpenSSL_add_all_algorithms'

  According to 
https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769
 the python module pyopenssl needs to be > 22.1.0
  Ubuntu 22.04 LTS ships with version 22.0.0.
  It seems, that the python3-openssl is not working well with the most recent 
openSSL version of Ubuntu 22.04.

  I could update pyopenssl with pip but this might break the update
  mechanism of apt.

  Any suggestions are appreciated, thanks!
  If I can provide further information, just let me know.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[thomas]

Is there any progress on this one? It completely disrupts workflows and
is the single most annoying bug in the Gnome shell since a few years.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[thomas]

Why is this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887 ?

It should definitely be the other way around, since it does not only
affect chromium but all programs using the Gnome shell file-save dialog.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 2018526] [NEW] Mesa Clover built with opaque pointers against LLVM built without opaque pointers

[Thomas Debesse]

Public bug reported:

This can be verified with any OpenCL application that actually tries to
compute something (clinfo may not be enough).

A very simple application to reproduce the bug is cl-mem:

```
git clone https://github.com/nerdralph/cl-mem.git
cd cl-mem
make
./cl-mem 
OpenCL build failed (-11). Build log follows:
fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': 
Opaque pointers are only supported in -opaque-pointers mode (Producer: 
'LLVM15.0.7' Reader: 'LLVM 15.0.7')
```

I may provide help to fix it, without guarantee. The migration of LLVM
to opaque pointers was not painless, some versions of Mesa may build and
run against some versions of LLVM 15 given that build option or that
patch is used, some not.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: mesa-opencl-icd 22.2.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.3
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu May  4 17:38:07 2023
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
MachineType: Default string Default string
ProcEnviron:
 LANGUAGE=fr_FR:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2022
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80PRO-F1
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80PRO-F1:bd08/04/2022:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kinetic third-party-packages ubuntu

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

Title:
  Mesa Clover built with opaque pointers against LLVM built without
  opaque pointers

Status in mesa package in Ubuntu:
  New

Bug description:
  This can be verified with any OpenCL application that actually tries
  to compute something (clinfo may not be enough).

  A very simple application to reproduce the bug is cl-mem:

  ```
  git clone https://github.com/nerdralph/cl-mem.git
  cd cl-mem
  make
  ./cl-mem 
  OpenCL build failed (-11). Build log follows:
  fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': 
Opaque pointers are only supported in -opaque-pointers mode (Producer: 
'LLVM15.0.7' Reader: 'LLVM 15.0.7')
  ```

  I may provide help to fix it, without guarantee. The migration of LLVM
  to opaque pointers was not painless, some versions of Mesa may build
  and run against some versions of LLVM 15 given that build option or
  that patch is used, some not.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: mesa-opencl-icd 22.2.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None

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

[Thomas Güttler]

I could help myself like this:

#check current linux version
uname -a

--> Linux p15 5.19.0-40-generic #41~22.04.1-Ubuntu


# list installed linux images
apt list --installed| grep linux-image

--> there were some older ones with version 5.15

# remove the old ones
apt remove linux-image-5.15.0-69-generic linux-image-5.15.0-70-generic
apt autoremove

# check states of /boot
df -h
--> /dev/nvme0n1p2 704M605M   48M   93% /boot


... hmm still not better.

rm /boot/*-5.15*


df -h /boot/

--> /dev/nvme0n1p2  704M288M  365M   45% /boot


Looks better now.


---

I can solve this on my own. But a normal human being (my mother, my
sister) can't do this.

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 27 07:47:41 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-10 (532 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago)

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


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

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

[Thomas Güttler]

The size of /boot was choosen by Ubuntu during the installation (not by
me).

I never touched a file in this directory by hand.

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 27 07:47:41 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-10 (532 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago)

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


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

[Touch-packages] [Bug 2017852] [NEW] package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Thomas Güttler]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Apr 27 07:47:41 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-11-10 (532 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago)

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


** Tags: amd64 apport-package jammy

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 27 07:47:41 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-10 (532 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago)

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


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

[Touch-packages] [Bug 2017792] [NEW] ifupdown on Ubuntu 22.04 fails to set DNS correctly -> DNS resolution does not work

[Thomas Dreibholz]

Public bug reported:

On a Ubuntu 22.04 system with /etc/network/interfaces configuration
(ifupdown) instead of Netplan, DNS is not set correctly. Therefore, DNS
resolution does not work.

This explains the issue:
https://unix.stackexchange.com/questions/714901/dns-broken-when-using-
ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0

Solution:

Fix in /etc/network/if-up.d/resolved:
Old: "$DNS"="$NEW_DNS"
New: $DNS="$NEW_DNS"

Old: "$DOMAINS"="$NEW_DOMAINS"
New: $DOMAINS="$NEW_DOMAINS"

/etc/network/if-up.d/resolved writes files
/run/network/ifupdown-- containing the DNS
configuration. The fix ensures that the files
/run/network/ifupdown-- contain the correct syntax
without quotes for the variable name.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ifupdown 0.8.36+nmu1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr 26 15:04:14 2023
InstallationDate: Installed on 2022-12-08 (139 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
ProcEnviron:
 LANGUAGE=nb:de:en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.network.if-up.d.resolved: 2023-04-26T14:36:08.277304

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  ifupdown on Ubuntu 22.04 fails to set DNS correctly -> DNS resolution
  does not work

Status in ifupdown package in Ubuntu:
  New

Bug description:
  On a Ubuntu 22.04 system with /etc/network/interfaces configuration
  (ifupdown) instead of Netplan, DNS is not set correctly. Therefore,
  DNS resolution does not work.

  This explains the issue:
  https://unix.stackexchange.com/questions/714901/dns-broken-when-using-
  ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0

  Solution:

  Fix in /etc/network/if-up.d/resolved:
  Old: "$DNS"="$NEW_DNS"
  New: $DNS="$NEW_DNS"

  Old: "$DOMAINS"="$NEW_DOMAINS"
  New: $DOMAINS="$NEW_DOMAINS"

  /etc/network/if-up.d/resolved writes files
  /run/network/ifupdown-- containing the DNS
  configuration. The fix ensures that the files
  /run/network/ifupdown-- contain the correct
  syntax without quotes for the variable name.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ifupdown 0.8.36+nmu1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr 26 15:04:14 2023
  InstallationDate: Installed on 2022-12-08 (139 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  ProcEnviron:
   LANGUAGE=nb:de:en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.network.if-up.d.resolved: 2023-04-26T14:36:08.277304

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


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

[Touch-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio]

[Thomas M Steenholdt]

I realize that the conflict is probably intended and my issue is that
vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate
bug, sorry.

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio]

[Thomas M Steenholdt]

I seem to hit the same dep issues on a freshly installed 23.04 system
when trying to install vanilla-gnome-desktop.

The following packages have unmet dependencies:
 pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
 pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2017083] [NEW] package linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Thomas Güttler]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Apr 20 08:26:01 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-11-10 (525 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2022-08-27 (235 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 20 08:26:01 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-10 (525 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-08-27 (235 days ago)

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


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

[Touch-packages] [Bug 2016141] Re: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21

[Thomas Faivre]

Hello,

thanks for the update!
I understand the reluctance to change something like that. But I still don't 
understand why the issue is not present when the version 245.4-4ubuntu3.19 is 
installed instead of 245.4-4ubuntu3.20.

> root@ubuntu2004:~# apt list --installed systemd
> Listing... Done
> systemd/now 245.4-4ubuntu3.19 amd64 [installed,upgradable to: 
> 245.4-4ubuntu3.21]
> root@ubuntu2004:~# apt install ./hello.deb 
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Note, selecting 'hello' instead of './hello.deb'
> The following additional packages will be installed:
>   chrony libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
> Suggested packages:
>   systemd-container policykit-1
> The following packages will be REMOVED:
>   systemd-timesyncd
> The following NEW packages will be installed:
>   chrony hello
> The following packages will be upgraded:
>   libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
> 5 upgraded, 2 newly installed, 1 to remove and 73 not upgraded.
> Need to get 4,591 kB/4,619 kB of archives.
> After this operation, 416 kB of additional disk space will be used.
> Do you want to continue? [Y/n] ^C

I would expect apt to not remove systemd-timesyncd according to what you are 
saying, since versions 245.4-4ubuntu3.20 and 245.4-4ubuntu3.21 are available.
Also, why can I install chrony manually in that case?

I feel like there is still something fishy somewhere...

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

Title:
  [focal] cannot resolve dependency when installing a package depending
  on 'chrony' since 245.4-4ubuntu3.21

Status in apt package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  Won't Fix
Status in systemd source package in Focal:
  Invalid

Bug description:
  Hello,

  Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot 
install our product.
  Our product depends on specifically chrony for the time-daemon, but apt 
cannot resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is 
installed.

  It might be specific to systemd-timesyncd, or an issue with apt itself
  but I am not sure.

  Reproduced using the "hello" package by modifying its dependencies:

  > root@ubuntu2004:~# apt download hello
  > Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B]
  > Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 
2.10-2ubuntu2 [28.2 kB]
  > Fetched 28.3 kB in 0s (95.6 kB/s)
  > W: Download is performed unsandboxed as root as file 
'/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  > root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello
  > root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control
  > root@ubuntu2004:~# dpkg -b hello/
  > dpkg-deb: building package 'hello' in 'hello.deb'.
  > root@ubuntu2004:~# apt -y install ./hello.deb
  > Reading package lists... Done
  > Building dependency tree   
  > Reading state information... Done
  > Note, selecting 'hello' instead of './hello.deb'
  > Some packages could not be installed. This may mean that you have
  > requested an impossible situation or if you are using the unstable
  > distribution that some required packages have not yet been created
  > or been moved out of Incoming.
  > The following information may help to resolve the situation:
  > 
  > The following packages have unmet dependencies:
  >  hello : Depends: chrony
  > E: Unable to correct problems, you have held broken packages.

  
  The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21:
  > root@ubuntu2004:~# apt -y install systemd
  [...]
  > Setting up systemd (245.4-4ubuntu3.21) ...
  > Setting up systemd-timesyncd (245.4-4ubuntu3.21) ...
  [...]
  > root@ubuntu2004:~# apt -y install ./hello.deb
  [...]
  > The following packages will be REMOVED:
  >   systemd-timesyncd
  > The following NEW packages will be installed:
  >   chrony hello
  [...]

  But that solution is a bit annoying as our customers might not want to
  upgrade systemd for some reason.

  OR by manually installing chrony:
  > root@ubuntu2004:~# apt -y install chrony
  [...]
  > The following packages will be REMOVED:
  >   systemd-timesyncd
  > The following NEW packages will be installed:
  >   chrony
  [...]
  > root@ubuntu2004:~# apt -y install ./hello.deb
  [...]
  > The following NEW packages will be installed:
  >   hello
  [...]


  Conflict with enabled debug logs:
  > root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb 
  > Reading package lists... Done
  > Building dependency tree   
  > Reading state information... Done
  > Note, selecting 'hello' instead of './hello.deb'
  > Starting pkgProblemResolver with 

[Touch-packages] [Bug 2016141] Re: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21

[Thomas Faivre]

Hello again,

New info on this issue.
I was trying to reproduce on ARM (and I did), but there is a but. And it's kind 
of an important one.

Our ARM VMs had version 245.4-4ubuntu3.19 installed, and the issue was
not seen. When upgrading to 245.4-4ubuntu3.20, the issue appears.

So it seems that the issue is upgrading *from* 245.4-4ubuntu3.20, and
not *to* 245.4-4ubuntu3.21.

I don't know what can be done then, maybe remove the version
245.4-4ubuntu3.20 from repositories? It might be a bit aggressive...

But I am still unsure why an available version upgrade of a package
creates a conflict...

Any suggestions?

Thanks!

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

Title:
  [focal] cannot resolve dependency when installing a package depending
  on 'chrony' since 245.4-4ubuntu3.21

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot 
install our product.
  Our product depends on specifically chrony for the time-daemon, but apt 
cannot resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is 
installed.

  It might be specific to systemd-timesyncd, or an issue with apt itself
  but I am not sure.

  Reproduced using the "hello" package by modifying its dependencies:

  > root@ubuntu2004:~# apt download hello
  > Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B]
  > Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 
2.10-2ubuntu2 [28.2 kB]
  > Fetched 28.3 kB in 0s (95.6 kB/s)
  > W: Download is performed unsandboxed as root as file 
'/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
  > root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello
  > root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control
  > root@ubuntu2004:~# dpkg -b hello/
  > dpkg-deb: building package 'hello' in 'hello.deb'.
  > root@ubuntu2004:~# apt -y install ./hello.deb
  > Reading package lists... Done
  > Building dependency tree   
  > Reading state information... Done
  > Note, selecting 'hello' instead of './hello.deb'
  > Some packages could not be installed. This may mean that you have
  > requested an impossible situation or if you are using the unstable
  > distribution that some required packages have not yet been created
  > or been moved out of Incoming.
  > The following information may help to resolve the situation:
  > 
  > The following packages have unmet dependencies:
  >  hello : Depends: chrony
  > E: Unable to correct problems, you have held broken packages.

  
  The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21:
  > root@ubuntu2004:~# apt -y install systemd
  [...]
  > Setting up systemd (245.4-4ubuntu3.21) ...
  > Setting up systemd-timesyncd (245.4-4ubuntu3.21) ...
  [...]
  > root@ubuntu2004:~# apt -y install ./hello.deb
  [...]
  > The following packages will be REMOVED:
  >   systemd-timesyncd
  > The following NEW packages will be installed:
  >   chrony hello
  [...]

  But that solution is a bit annoying as our customers might not want to
  upgrade systemd for some reason.

  OR by manually installing chrony:
  > root@ubuntu2004:~# apt -y install chrony
  [...]
  > The following packages will be REMOVED:
  >   systemd-timesyncd
  > The following NEW packages will be installed:
  >   chrony
  [...]
  > root@ubuntu2004:~# apt -y install ./hello.deb
  [...]
  > The following NEW packages will be installed:
  >   hello
  [...]


  Conflict with enabled debug logs:
  > root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb 
  > Reading package lists... Done
  > Building dependency tree   
  > Reading state information... Done
  > Note, selecting 'hello' instead of './hello.deb'
  > Starting pkgProblemResolver with broken count: 1
  > Starting 2 pkgProblemResolver with broken count: 1
  > Investigating (0) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib >
  > Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH >
  >   Considering chrony:amd64 1 as a solution to hello:amd64 
  >   Re-Instated chrony:amd64
  > Investigating (0) systemd-timesyncd:amd64 < 245.4-4ubuntu3.20 -> 
245.4-4ubuntu3.21 @ii umU Ib >
  > Broken systemd-timesyncd:amd64 Conflicts on time-daemon:amd64 < none @un H >
  >   Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 for 
ntp but that is not InstVer, ignoring
  >   Considering chrony:amd64 1 as a solution to systemd-timesyncd:amd64 14
  >   Added chrony:amd64 to the remove list
  >   Conflicts//Breaks against version 1:6.2p3-4 for openntpd but that is not 
InstVer, ignoring
  >   Conflicts//Breaks against version 1.1.8+dfsg1-4build1 for ntpsec but that 
is not InstVer, ignoring
  >   Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4 for ntp 

[Touch-packages] [Bug 2016141] [NEW] [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21

[Thomas Faivre]

Public bug reported:

Hello,

Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot 
install our product.
Our product depends on specifically chrony for the time-daemon, but apt cannot 
resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is installed.

It might be specific to systemd-timesyncd, or an issue with apt itself
but I am not sure.

Reproduced using the "hello" package by modifying its dependencies:

> root@ubuntu2004:~# apt download hello
> Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B]
> Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 
> 2.10-2ubuntu2 [28.2 kB]
> Fetched 28.3 kB in 0s (95.6 kB/s)
> W: Download is performed unsandboxed as root as file 
> '/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - 
> pkgAcquire::Run (13: Permission denied)
> root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello
> root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control
> root@ubuntu2004:~# dpkg -b hello/
> dpkg-deb: building package 'hello' in 'hello.deb'.
> root@ubuntu2004:~# apt -y install ./hello.deb
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Note, selecting 'hello' instead of './hello.deb'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  hello : Depends: chrony
> E: Unable to correct problems, you have held broken packages.


The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21:
> root@ubuntu2004:~# apt -y install systemd
[...]
> Setting up systemd (245.4-4ubuntu3.21) ...
> Setting up systemd-timesyncd (245.4-4ubuntu3.21) ...
[...]
> root@ubuntu2004:~# apt -y install ./hello.deb
[...]
> The following packages will be REMOVED:
>   systemd-timesyncd
> The following NEW packages will be installed:
>   chrony hello
[...]

But that solution is a bit annoying as our customers might not want to
upgrade systemd for some reason.

OR by manually installing chrony:
> root@ubuntu2004:~# apt -y install chrony
[...]
> The following packages will be REMOVED:
>   systemd-timesyncd
> The following NEW packages will be installed:
>   chrony
[...]
> root@ubuntu2004:~# apt -y install ./hello.deb
[...]
> The following NEW packages will be installed:
>   hello
[...]


Conflict with enabled debug logs:
> root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb 
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Note, selecting 'hello' instead of './hello.deb'
> Starting pkgProblemResolver with broken count: 1
> Starting 2 pkgProblemResolver with broken count: 1
> Investigating (0) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib >
> Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH >
>   Considering chrony:amd64 1 as a solution to hello:amd64 
>   Re-Instated chrony:amd64
> Investigating (0) systemd-timesyncd:amd64 < 245.4-4ubuntu3.20 -> 
> 245.4-4ubuntu3.21 @ii umU Ib >
> Broken systemd-timesyncd:amd64 Conflicts on time-daemon:amd64 < none @un H >
>   Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 for ntp 
> but that is not InstVer, ignoring
>   Considering chrony:amd64 1 as a solution to systemd-timesyncd:amd64 14
>   Added chrony:amd64 to the remove list
>   Conflicts//Breaks against version 1:6.2p3-4 for openntpd but that is not 
> InstVer, ignoring
>   Conflicts//Breaks against version 1.1.8+dfsg1-4build1 for ntpsec but that 
> is not InstVer, ignoring
>   Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4 for ntp but that 
> is not InstVer, ignoring
>   Conflicts//Breaks against version 3.5-6ubuntu6 for chrony but that is not 
> InstVer, ignoring
>   Fixing systemd-timesyncd:amd64 via keep of chrony:amd64
> Investigating (1) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib >
> Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH >
>   Considering chrony:amd64 1 as a solution to hello:amd64 
>   Considering chrony:amd64 1 as a solution to hello:amd64 
>   Considering maas:amd64 0 as a solution to hello:amd64 
>   Re-Instated apparmor:amd64
>   Re-Instated liblzo2-2:amd64
>   Re-Instated squashfs-tools:amd64
>   Re-Instated dbus-user-session:amd64
>   Re-Instated snapd:amd64
>   Re-Instated maas:amd64
> Investigating (1) maas:amd64 < none -> 1:0.7 @un uN Ib >
> Broken maas:amd64 Conflicts on isc-dhcp-server:amd64 < 
> 4.4.1-2.1ubuntu5.20.04.5 @ii mK >
>   Considering isc-dhcp-server:amd64 0 as a solution to maas:amd64 0
>   Holding Back maas:amd64 rather than change isc-dhcp-server:amd64
> Investigating (2) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib >
> Broken 

[Touch-packages] [Bug 2013135] [NEW] Dissapearing Mouse Cursor

[Thomas G.]

Public bug reported:

Touching the touch screen display removes the mouse cursor. It comes back after 
blindly navigating to the menu bar. This also happends randomly without 
touching the touchscreen. There doesn't appear to be a trigger for the random 
disappearances that is user input.
Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 18:19:00 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc]
   Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc]
InstallationDate: Installed on 2023-02-28 (28 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Dell Inc. Inspiron 7737
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=1322e8b8-bc4a-464a-89b8-6bc305451ff5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2013
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0H9X60
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 0.4
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd10/09/2013:br0.4:efr0.4:svnDellInc.:pnInspiron7737:pvr:rvnDellInc.:rn0H9X60:rvrA00:cvnDellInc.:ct8:cvr0.1:skuInspiron7737:
dmi.product.family: Shark Bay ULT
dmi.product.name: Inspiron 7737
dmi.product.sku: Inspiron 7737
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Dissapearing Mouse Cursor

Status in xorg package in Ubuntu:
  New

Bug description:
  Touching the touch screen display removes the mouse cursor. It comes back 
after blindly navigating to the menu bar. This also happends randomly without 
touching the touchscreen. There doesn't appear to be a trigger for the random 
disappearances that is user input.
  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 28 18:19:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc]
  InstallationDate: Installed on 2023-02-28 (28 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  

[Touch-packages] [Bug 2011751] Re: openbox crashed with SIGABRT

[Thomas Ward]

After discussion with the Security Team, we do not believe this is a
Security bug and that there currently is no need to keep it private as
there is other public discourse via other related bugs on other trackers
and here in Launchpad with other bugs (marked as dupes of this or such).

** Information type changed from Private Security to Public

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions


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

[Touch-packages] [Bug 2009706] Re: rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison 2.48.4-1ubuntu1 on Bionic

[Thomas S]

That appears to work around the problem, yes, changing them to.

copyprog = rsync -a -A -X --rsh=ssh --inplace --compress --old-args
copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress 
--old-args

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

Title:
  rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison
  2.48.4-1ubuntu1 on Bionic

Status in rsync package in Ubuntu:
  New
Status in unison package in Ubuntu:
  New

Bug description:
  Rsync 3.1.2-2.1ubuntu1.6, when used by Unison using the copyprog
  option in Unison, produces an error message and fails to sync files.
  Rsync 3.1.2-2.1ubuntu1 succeeds in syncing files. I believe Rsync
  3.1.2-2.1ubuntu1.5 succeeded but I no longer have the .deb file to
  test with.

  Steps to reproduce:

  Create a unison profile similar to the one given below, to sync a
  folder between a local machine and a remote ssh server. Both client
  and server need the same Ubuntu and Unison versions, and I used
  unpassphrased SSH keys for authentication. Place a test file in the
  folder to be synced, then run 'unison profilename'.

  Note that I have redacted domains in the below.

  Unison profile:

  label = Test Profile
  root = /root/unison-test
  root = ssh://fs2b.our.domain.org.uk//root/unison-test

  # run repeatedly and fully automatically
  auto = true
  batch = true
  copyonconflict = true
  #repeat = 60

  # the copy program must be manually specified in order to sync ACLs
  copythreshold=0
  copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
  copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress

  # general settings
  group = true
  owner = true
  #path = sharedfolder
  #path = users
  perms = -1
  sortbysize = true
  times = true

  Unison output with rsync 3.1.2-2.1ubuntu1.6
  root@fs72a:~# unison fs2b_unisontest -debug all
  [startup] Preferences:
  ui = graphic
  host =
  server = false
  prefsdocs = false
  doc =
  version = false
  silent = false
  dumbtty = false
  testserver = false
  rest = fs2b_unisontest
  showprev = false
  selftest = false
  confirmmerge = false
  retry = 0
  repeat =
  contactquietly = false
  key =
  label = Syncs P and S drives between fs72a and fs2a
  expert = false
  height = 15
  auto = true
  maxthreads = 0
  maxsizethreshold = -1
  prefer =
  force =
  sortnewfirst = false
  sortbysize = true
  keeptempfilesaftermerge = false
  diff = diff -u CURRENT2 CURRENT1
  copyonconflict = true
  backupdir =
  maxbackups = 2
  backups = false
  backupsuffix =
  backupprefix = .bak.$VERSION.
  backuploc = central
  copymax = 1
  copyquoterem = default
  copythreshold = 0
  copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress
  copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
  rsync = true
  fastcheck = default
  ignorelocks = false
  dumparchives = false
  showarchive = false
  rootsName =
  ignorearchives = false
  fastercheckUNSAFE = false
  fat = false
  allHostsAreRunningWindows = false
  someHostIsRunningWindows = false
  confirmbigdel = true
  batch = true
  root = ssh://fs2b.our.domain.org.uk//root/unison-test
  root = /root/unison-test
  killserver = false
  halfduplex = false
  stream = true
  addversionno = false
  servercmd =
  sshargs =
  rshargs =
  rshcmd = rsh
  sshcmd = ssh
  xferbycopying = true
  sshversion =
  clientHostName = fs72a
  ignoreinodenumbers = false
  links-aux = true
  links = default
  times = true
  group = true
  owner = true
  numericids = false
  dontchmod = false
  perms = -1
  watch = true
  rsrc-aux = false
  rsrc = default
  maxerrors = 1
  unicodeCS = false
  unicodeEnc = false
  unicode = default
  someHostIsInsensitive = false
  ignorecase = default
  timers = false
  terse = false
  logfile = /root/.unison/unison.log
  log = true
  debugtimes = false
  debug = all
  addprefsto =
  Contacting server...
  [remote] Shell connection: ssh (ssh, fs2b.our.domain.org.uk, -e, none, 
unison, -server)
  [globals] Checking path '' for expansions
  Connected [//fs2b//root/unison-test -> //fs72a//root/unison-test]
  [startup] Roots:
  /root/unison-test
  ssh://fs2b.our.domain.org.uk//root/unison-test
i.e.
  /root/unison-test
  ssh://fs2b.our.domain.org.uk//root/unison-test
i.e. (in canonical order)
 /root/unison-test
 //fs2b//root/unison-test

  [props] Setting permission mask to  (7 and )
  [stasher] initBackupsLocal
  [stasher] d = /
  [stasher] Prefix and suffix regexps for backup filenames have been updated
  [server: stasher] initBackupsLocal
  [server: stasher] d = /
  [server: stasher] Prefix and suffix regexps for backup filenames have been 
updated
  Looking for changes
  [ui] temp: Globals.paths =
  [update] Loading archive from /root/.unison/areaa7785bb2204bed0cb7af3360b3c323
  [update] Setting archive for 

[Touch-packages] [Bug 2009706] [NEW] rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison 2.48.4-1ubuntu1 on Bionic

[Thomas S]

Public bug reported:

Rsync 3.1.2-2.1ubuntu1.6, when used by Unison using the copyprog option
in Unison, produces an error message and fails to sync files. Rsync
3.1.2-2.1ubuntu1 succeeds in syncing files. I believe Rsync
3.1.2-2.1ubuntu1.5 succeeded but I no longer have the .deb file to test
with.

Steps to reproduce:

Create a unison profile similar to the one given below, to sync a folder
between a local machine and a remote ssh server. Both client and server
need the same Ubuntu and Unison versions, and I used unpassphrased SSH
keys for authentication. Place a test file in the folder to be synced,
then run 'unison profilename'.

Note that I have redacted domains in the below.

Unison profile:

label = Test Profile
root = /root/unison-test
root = ssh://fs2b.our.domain.org.uk//root/unison-test

# run repeatedly and fully automatically
auto = true
batch = true
copyonconflict = true
#repeat = 60

# the copy program must be manually specified in order to sync ACLs
copythreshold=0
copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress

# general settings
group = true
owner = true
#path = sharedfolder
#path = users
perms = -1
sortbysize = true
times = true

Unison output with rsync 3.1.2-2.1ubuntu1.6
root@fs72a:~# unison fs2b_unisontest -debug all
[startup] Preferences:
ui = graphic
host =
server = false
prefsdocs = false
doc =
version = false
silent = false
dumbtty = false
testserver = false
rest = fs2b_unisontest
showprev = false
selftest = false
confirmmerge = false
retry = 0
repeat =
contactquietly = false
key =
label = Syncs P and S drives between fs72a and fs2a
expert = false
height = 15
auto = true
maxthreads = 0
maxsizethreshold = -1
prefer =
force =
sortnewfirst = false
sortbysize = true
keeptempfilesaftermerge = false
diff = diff -u CURRENT2 CURRENT1
copyonconflict = true
backupdir =
maxbackups = 2
backups = false
backupsuffix =
backupprefix = .bak.$VERSION.
backuploc = central
copymax = 1
copyquoterem = default
copythreshold = 0
copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress
copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
rsync = true
fastcheck = default
ignorelocks = false
dumparchives = false
showarchive = false
rootsName =
ignorearchives = false
fastercheckUNSAFE = false
fat = false
allHostsAreRunningWindows = false
someHostIsRunningWindows = false
confirmbigdel = true
batch = true
root = ssh://fs2b.our.domain.org.uk//root/unison-test
root = /root/unison-test
killserver = false
halfduplex = false
stream = true
addversionno = false
servercmd =
sshargs =
rshargs =
rshcmd = rsh
sshcmd = ssh
xferbycopying = true
sshversion =
clientHostName = fs72a
ignoreinodenumbers = false
links-aux = true
links = default
times = true
group = true
owner = true
numericids = false
dontchmod = false
perms = -1
watch = true
rsrc-aux = false
rsrc = default
maxerrors = 1
unicodeCS = false
unicodeEnc = false
unicode = default
someHostIsInsensitive = false
ignorecase = default
timers = false
terse = false
logfile = /root/.unison/unison.log
log = true
debugtimes = false
debug = all
addprefsto =
Contacting server...
[remote] Shell connection: ssh (ssh, fs2b.our.domain.org.uk, -e, none, unison, 
-server)
[globals] Checking path '' for expansions
Connected [//fs2b//root/unison-test -> //fs72a//root/unison-test]
[startup] Roots:
/root/unison-test
ssh://fs2b.our.domain.org.uk//root/unison-test
  i.e.
/root/unison-test
ssh://fs2b.our.domain.org.uk//root/unison-test
  i.e. (in canonical order)
   /root/unison-test
   //fs2b//root/unison-test

[props] Setting permission mask to  (7 and )
[stasher] initBackupsLocal
[stasher] d = /
[stasher] Prefix and suffix regexps for backup filenames have been updated
[server: stasher] initBackupsLocal
[server: stasher] d = /
[server: stasher] Prefix and suffix regexps for backup filenames have been 
updated
Looking for changes
[ui] temp: Globals.paths =
[update] Loading archive from /root/.unison/areaa7785bb2204bed0cb7af3360b3c323
[update] Setting archive for //fs72a//root/unison-test
[server: update] Loading archive from 
/root/.unison/ar8a6c9477fdd76859c429c5bdd5afe2d9
[server: update] Setting archive for //fs2b//root/unison-test
[update] findOnRoot //fs2b//root/unison-test
[update] findOnRoot /root/unison-test
[update] findLocal /root/unison-test ()
[fpcache] opening cache file /root/.unison/fpeaa7785bb2204bed0cb7af3360b3c323 
for input
[fpcache] read chunk of 1 files
[fpcache] opening cache file /root/.unison/fpeaa7785bb2204bed0cb7af3360b3c323 
for output
[pred] ignore '' = false
[update] buildUpdateRec: /root/unison-test
[pred] immutable '' = false
[pred] ignore 'hello' = false
[update] buildUpdateRec: /root/unison-test/hello
[update]   buildUpdate -> New file
[fpcache] cache hit for path hello
[xferhint] insertEntry: fspath=/root/unison-test, path=hello, 
fp=(8ddd8be4b179a529afa5f2ffae4b9858,)
[update] Setting archive 

[Touch-packages] [Bug 2003576] Re: grayed buttons in Additional Drivers

[Thomas Queste]

Related: https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/1993370

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

Title:
  grayed buttons in Additional Drivers

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Not possible to install nvidia drivers using "Software
  Sources"->"Additional Drivers".

  When selecting driver using radio-box the following excetpion occurs.

  nvidia-driver-525-server 
  None 
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1067, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  
  Because the follwing row returns "None"

  modules_package = detect.get_linux_modules_metapackage(self.apt_cache,
  pkg_name)

  Current version:
  $ apt list --installed | grep software

  python3-software-properties/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]
  software-properties-common/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]
  software-properties-qt/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]

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


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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Thomas Ward]

Regarding NGINX, PCRE2 support is now available in NGINX nginx 1.21.5+
so there was support as of December 24th 2021 and later.

Which means that NGINX 1.22+ supports PCRE2.  This could be marked as
Triaged *for 23.04 and later* once NGINX is merged in from Debian
upstream, if someone can put a few cycles to build/test.

Refer to
https://trac.nginx.org/nginx/changeset/0b5f12d5c531be630a4aae644686be83cfed3267/nginx
and the "fixed" Trac bug https://trac.nginx.org/nginx/ticket/720

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  In Progress
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Fix Released
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete
Status in postfix package in Debian:
  Fix Released
Status in zsh package in Debian:
  Confirmed

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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


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

[Touch-packages] [Bug 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic

[Thomas Ward]

I've discussed this with mapreri who is another person on the
backporters team.

Given the API/ABI changes that happen during OpenSSL microreleases that
break packages integrations AND that this will add a security delta
(-backports doesn't receive Security Team support so if they change and
patch a CVE in -security or -updates it remains unpatched in -backports
which introduces a significant Security risk.

Additionally, if it's only 3 or 4 commits to fix
SSL_OP_LEGACY_SERVER_CONNECT then you need to follow the SRU process,
not the Backports process.

Rejecting this backport as "Won't Fix" due to the aforementioned
reasons.  Additionally, the Backporters Team are going to blacklist
`openssl` for backport requests unless it comes from Security at this
time.

** Changed in: openssl (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [BPO] openssl/3.0.5-2ubuntu2 from kinetic

Status in openssl package in Ubuntu:
  Won't Fix

Bug description:
  Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to
  jammy.

  [Impact]

  From the OpenSSL 3.0 migration guide:
  (https://www.openssl.org/docs/man3.0/man7/migration_guide.html)

  "Secure renegotiation is now required by default for TLS connections

  Support for RFC 5746 secure renegotiation is now required by default
  for SSL or TLS connections to succeed. Applications that require the
  ability to connect to legacy peers will need to explicitly set
  SSL_OP_LEGACY_SERVER_CONNECT. Accordingly,
  SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL."

  

  OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in
  the openssl.cnf file. The OpenSSL team documented this option but
  forgot to implement it
  (https://github.com/openssl/openssl/pull/18296).

  Users are recommending enabling UnsafeLegacyRenegotiation (see
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32)
  (see more examples in "Other Info")

  When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which
  is what the previous LTS, Focal, uses).

  Backporting the newer OpenSSL 3.0.5 would allow users to enable
  UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled.

  [Scope]

  Backport OpenSSL 3.0.5-2ubuntu2 from kinetic

  Backport to jammy

  [Other Info]
  Other places where users are recommending enabling UnsafeLegacyRenegotiation:
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6
  https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091
  
https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/

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


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

[Touch-packages] [Bug 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic

[Thomas Ward]

Mark, are you asking this to be backported in -backports or in -updates
and -security?  This is one of the packages that if we do this in
-backports any security patches applied by the Security team for OpenSSL
in -security and -updates would be ignored with the higher version of
this in -backports.

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

Title:
  [BPO] openssl/3.0.5-2ubuntu2 from kinetic

Status in openssl package in Ubuntu:
  New

Bug description:
  Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to
  jammy.

  [Impact]

  From the OpenSSL 3.0 migration guide:
  (https://www.openssl.org/docs/man3.0/man7/migration_guide.html)

  "Secure renegotiation is now required by default for TLS connections

  Support for RFC 5746 secure renegotiation is now required by default
  for SSL or TLS connections to succeed. Applications that require the
  ability to connect to legacy peers will need to explicitly set
  SSL_OP_LEGACY_SERVER_CONNECT. Accordingly,
  SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL."

  

  OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in
  the openssl.cnf file. The OpenSSL team documented this option but
  forgot to implement it
  (https://github.com/openssl/openssl/pull/18296).

  Users are recommending enabling UnsafeLegacyRenegotiation (see
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32)
  (see more examples in "Other Info")

  When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which
  is what the previous LTS, Focal, uses).

  Backporting the newer OpenSSL 3.0.5 would allow users to enable
  UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled.

  [Scope]

  Backport OpenSSL 3.0.5-2ubuntu2 from kinetic

  Backport to jammy

  [Other Info]
  Other places where users are recommending enabling UnsafeLegacyRenegotiation:
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6
  https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091
  
https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/

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


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

[Touch-packages] [Bug 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic

[Thomas Ward]

OpenSSL is one of those tricky things out there I would like to get a
Security insight for before we do any kind of backporting of it.
There's other things this could impact, backports or not.

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

Title:
  [BPO] openssl/3.0.5-2ubuntu2 from kinetic

Status in openssl package in Ubuntu:
  New

Bug description:
  Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to
  jammy.

  [Impact]

  From the OpenSSL 3.0 migration guide:
  (https://www.openssl.org/docs/man3.0/man7/migration_guide.html)

  "Secure renegotiation is now required by default for TLS connections

  Support for RFC 5746 secure renegotiation is now required by default
  for SSL or TLS connections to succeed. Applications that require the
  ability to connect to legacy peers will need to explicitly set
  SSL_OP_LEGACY_SERVER_CONNECT. Accordingly,
  SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL."

  

  OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in
  the openssl.cnf file. The OpenSSL team documented this option but
  forgot to implement it
  (https://github.com/openssl/openssl/pull/18296).

  Users are recommending enabling UnsafeLegacyRenegotiation (see
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32)
  (see more examples in "Other Info")

  When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which
  is what the previous LTS, Focal, uses).

  Backporting the newer OpenSSL 3.0.5 would allow users to enable
  UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled.

  [Scope]

  Backport OpenSSL 3.0.5-2ubuntu2 from kinetic

  Backport to jammy

  [Other Info]
  Other places where users are recommending enabling UnsafeLegacyRenegotiation:
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6
  https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091
  
https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Thomas Løcke]

This annoying bug rears its ugly head since I upgraded my own and my
wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop
or 20.04 workbox.

When using the Save As dialog, focus switches to the filter/search field
in the dialog when we start typing a name for the file. The focus change
happens after each character, so it's practically unusable.

Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap).

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Triaged

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 2003576] Re: grayed buttons in Additional Drivers

[Thomas Queste]

Occuring also with version 0.99.27 upon selection of an entry.


```
$ sudo software-properties-qt
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
modules_package_obj = self.apt_cache[modules_package]
TypeError: Expected a string or a pair of strings
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1059, in on_driver_selection_changed
pkg = self.apt_cache[pkg_name]
TypeError: Expected a string or a pair of strings

```

```
$ apt list --installed | grep software

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

python3-software-properties/kinetic,kinetic,now 0.99.27 all 
[installed,automatic]
software-properties-common/kinetic,kinetic,now 0.99.27 all [installed,automatic]
software-properties-qt/kinetic,kinetic,now 0.99.27 all [installed,automatic]
```

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

Title:
  grayed buttons in Additional Drivers

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Not possible to install nvidia drivers using "Software
  Sources"->"Additional Drivers".

  When selecting driver using radio-box the following excetpion occurs.

  nvidia-driver-525-server 
  None 
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1067, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  
  Because the follwing row returns "None"

  modules_package = detect.get_linux_modules_metapackage(self.apt_cache,
  pkg_name)

  Current version:
  $ apt list --installed | grep software

  python3-software-properties/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]
  software-properties-common/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]
  software-properties-qt/jammy-updates,jammy-updates,now 0.99.22.4 all 
[installerat,automatiskt]

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


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

[Touch-packages] [Bug 1999171] Re: tparm dynamic variables broken

[Thomas Dickey]

Dynamic variables are maintained as part of the currently opened terminal.
As noted, if you want to open a bug against ncurses (rather than Ubuntu 
packaging),
this won't get as much attention as the bug-ncurses mailing list, or the Debian 
package
(which Ubuntu provides without change).

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

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

Title:
  tparm dynamic variables broken

Status in ncurses package in Ubuntu:
  Invalid

Bug description:
  I use the Python curses library for convenience, but this seems to be
  an ncurses bug as Python simply wraps the ncurses library.

  As you can see from example below, the dynamic variable x gets stored as 4, 
but, when it's
  recalled, 0 is returned instead of 4. This was on 22.04 and 20.04 with 
libncurses6 6.3-2.

  I've confirm the behavior is correct on Fedora 36 with ncurses-
  libs-6.2-9.20210508. I apologize I haven't been able to narrow it down
  farther, but figured it would be good to get a bug logged in case
  someone has more insight.

  ```
  Python 3.10.6 (main, Nov  2 2022, 18:53:38) [GCC 11.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import curses
  >>> curses.setupterm()
  >>> curses.tparm(b'%p1%Px', 4)
  b''
  >>> curses.tparm(b'%gx%d')
  b'0'
  ```

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


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

[Touch-packages] [Bug 1999171] Re: tparm dynamic variables broken

[Thomas Dickey]

https://invisible-island.net/ncurses/man/terminfo.5.html#h3-Parameterized-Strings
https://invisible-island.net/personal/bug-reports.html#low_support

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

Title:
  tparm dynamic variables broken

Status in ncurses package in Ubuntu:
  New

Bug description:
  I use the Python curses library for convenience, but this seems to be
  an ncurses bug as Python simply wraps the ncurses library.

  As you can see from example below, the dynamic variable x gets stored as 4, 
but, when it's
  recalled, 0 is returned instead of 4. This was on 22.04 and 20.04 with 
libncurses6 6.3-2.

  I've confirm the behavior is correct on Fedora 36 with ncurses-
  libs-6.2-9.20210508. I apologize I haven't been able to narrow it down
  farther, but figured it would be good to get a bug logged in case
  someone has more insight.

  ```
  Python 3.10.6 (main, Nov  2 2022, 18:53:38) [GCC 11.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import curses
  >>> curses.setupterm()
  >>> curses.tparm(b'%p1%Px', 4)
  b''
  >>> curses.tparm(b'%gx%d')
  b'0'
  ```

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


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

[Touch-packages] [Bug 1997189] Re: [BPO] elfutils/0.188-1 from Lunar

[Thomas Ward]

> I intend to update Ubuntu's debuginfod instance to use this new
package in the near future.

By "update" do you mean SRU or via Backports?  If you are not going to
be doing this via Backports, then I would suggest that you hunt an SRU
on the sole basis that mixing and matching SRU/Backports makes things a
"Well, why do we need this?" situation on both Backports and Stable
Release Updates.

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

Title:
   [BPO] elfutils/0.188-1 from Lunar

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  New

Bug description:
  [Impact]

   * elfutils ships many ELF/DWARF related tools that are interesting
  for users and developers of low level code.

   * More specifically, elfutils ships the debuginfod library and
  server. The latest upstream version (0.188) introduces many
  interesting features that should make the life of debuginfod users
  easier; one of those features is the ability to serve sections of
  DWARF, instead of the whole file.  I intend to update Ubuntu's
  debuginfod instance to use this new package in the near future.

  [Scope]

   * I will backport elfutils/0.188 from Lunar.

   * I will backport elfutils/0.188 to Jammy.

  [Other Info]

   * None so far.

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Thomas Honigmann]

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

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Fix Released
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  This bug causes rsync 3.2.3 to wrongly report files with an exact same
  mtime as being "newer" implying they would need to be
  transfered/sync'ed where in fact they are "uptodate".

  This breaks users' scripts depending on "is newer" to signal that
  files need to be sync'ed when in fact, they don't need to be.

  [Test Plan]

  Steps to reproduce:

  1. Create a local file:
  $ touch foo

  2. Check if rsync would transfer it using the --update option:
  $ rsync -avv --update foo .

  If the regression is present, "foo is newer" would be reported:

  ```
  sending incremental file list
  delta-transmission disabled for local transfer or --whole-file
  foo is newer
  total: matches=0  hash_hits=0  false_alarms=0 data=0

  sent 61 bytes  received 96 bytes  314.00 bytes/sec
  total size is 0  speedup is 0.00
  ```

  If the updated package is installed (from -proposed), "foo is
  uptodate" should be reported:

  ```
  sending incremental file list
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate
  total: matches=0  hash_hits=0  false_alarms=0 data=0

  sent 60 bytes  received 106 bytes  332.00 bytes/sec
  total size is 0  speedup is 0.00
  ```

  [Regression potential]

  The patch changes the behavior of --update so if something goes wrong,
  it could break backup/sync jobs. To mitigate that, manual testing of
  rsync with and without the --update option was done in addition to the
  quick [Test Plan] outlined above.

  Please note the patch restores the behavior from before version 3.2.3
  and has been integrated by upstream in September 2021. It also is in
  Kinetic where no visible regression was observed.

  [Original description]

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.

  Obviously a file should not be listed as newer than itself.  Another
  way:

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Thomas Honigmann]

rsync (3.2.3-8ubuntu3.1) tested successfully.
Details can be found in attached TESTCASE document.

** Attachment added: "TESTCASE"
   
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5630638/+files/TESTCASE

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Fix Released
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  This bug causes rsync 3.2.3 to wrongly report files with an exact same
  mtime as being "newer" implying they would need to be
  transfered/sync'ed where in fact they are "uptodate".

  This breaks users' scripts depending on "is newer" to signal that
  files need to be sync'ed when in fact, they don't need to be.

  [Test Plan]

  Steps to reproduce:

  1. Create a local file:
  $ touch foo

  2. Check if rsync would transfer it using the --update option:
  $ rsync -avv --update foo .

  If the regression is present, "foo is newer" would be reported:

  ```
  sending incremental file list
  delta-transmission disabled for local transfer or --whole-file
  foo is newer
  total: matches=0  hash_hits=0  false_alarms=0 data=0

  sent 61 bytes  received 96 bytes  314.00 bytes/sec
  total size is 0  speedup is 0.00
  ```

  If the updated package is installed (from -proposed), "foo is
  uptodate" should be reported:

  ```
  sending incremental file list
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate
  total: matches=0  hash_hits=0  false_alarms=0 data=0

  sent 60 bytes  received 106 bytes  332.00 bytes/sec
  total size is 0  speedup is 0.00
  ```

  [Regression potential]

  The patch changes the behavior of --update so if something goes wrong,
  it could break backup/sync jobs. To mitigate that, manual testing of
  rsync with and without the --update option was done in addition to the
  quick [Test Plan] outlined above.

  Please note the patch restores the behavior from before version 3.2.3
  and has been integrated by upstream in September 2021. It also is in
  Kinetic where no visible regression was observed.

  [Original description]

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.

  Obviously a file should not be listed as newer than itself.  Another
  way:

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1991495] [NEW] gnome-gmail does not work as a helper application

[Reuben Thomas]

Public bug reported:

To enable gnome-gmail to work, the sanitized_helper profile in
/etc/apparmor.d/abstractions/ubuntu-helpers needs to allow the main
script of gnome-gmail to be exec'ed. I have added a minimal change to
allow that, which is attached to this bug:

  # Allow exec of gnome-gmail main script
  /usr/share/gnome-gmail/gnomegmail.py Pixr,

A more general change to support other (potential) helpers might be
useful. (Alternatively, this could be considered a gnome-gmail
problem—it's a weird way to package a Python program, to use a trivial
shell script that execs the main program!)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apparmor 3.0.4-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sun Oct  2 20:25:58 2022
InstallationDate: Installed on 2021-02-07 (601 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: Upgraded to jammy on 2022-08-16 (47 days ago)
mtime.conffile..etc.apparmor.d.abstractions.ubuntu-helpers: 
2022-10-02T20:21:41.874949

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


** Tags: amd64 apport-bug jammy

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

Title:
  gnome-gmail does not work as a helper application

Status in apparmor package in Ubuntu:
  New

Bug description:
  To enable gnome-gmail to work, the sanitized_helper profile in
  /etc/apparmor.d/abstractions/ubuntu-helpers needs to allow the main
  script of gnome-gmail to be exec'ed. I have added a minimal change to
  allow that, which is attached to this bug:

# Allow exec of gnome-gmail main script
/usr/share/gnome-gmail/gnomegmail.py Pixr,

  A more general change to support other (potential) helpers might be
  useful. (Alternatively, this could be considered a gnome-gmail
  problem—it's a weird way to package a Python program, to use a trivial
  shell script that execs the main program!)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apparmor 3.0.4-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Oct  2 20:25:58 2022
  InstallationDate: Installed on 2021-02-07 (601 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to jammy on 2022-08-16 (47 days ago)
  mtime.conffile..etc.apparmor.d.abstractions.ubuntu-helpers: 
2022-10-02T20:21:41.874949

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


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

[Touch-packages] [Bug 1886653] Re: cups-pki-expired

[Thomas Kalinowski]

I tried adding the option 'AllowExpiredCerts' and setting it 'true'. It
did not change anything for me: The printer state is set to 'Stopped'
with status message 'cups-pki-expired' as soon as I send a job.

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

Title:
  cups-pki-expired

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The printer always goes to stopped state in Ubuntu 20.04. Print
  properties window has status message saying: "cups-pki-expired". I
  have HP color laserjet m552, which Ubuntu discovers directly from the
  local network and configures automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 14:40:00 2020
  InstallationDate: Installed on 2019-11-03 (247 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: 
implicitclass://HP_Color_LaserJet_M552_5F80BF_/
  MachineType: LENOVO 81H1
  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.4.0-40-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1990315] Re: cannot link against libudev

[Thomas Debesse]

I had noticed `pkg-config --list-all` is listing two udev packages,
`udev` and `libudev`. `pkg-config --libs udev` prints nothing but `pkg-
config --libs libudev` prints `-ludev`.

I had also noticed that the link command did not featured `-ludev`. I
also had tried to set compile/link flags to `-ludev` using environment
variables without success at the time, but now that I just retried I
noticed that if I delete the build dir, the flags are used and the build
pass.

I assume `libudev.h` is found properly because the code compiles, the
error is a link error.

Now, why there are two udev packages listed by pkg-config and why the
linker flag isn't passed to mesa is a mystery to me.

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

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

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


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

[Touch-packages] [Bug 1990315] [NEW] cannot link against libudev

[Thomas Debesse]

Public bug reported:

When building Mesa vulkan drivers I get a lot of those error messages
and the build fails:

```
error: undefined symbol: udev_new
error: undefined symbol: udev_monitor_get_fd
error: undefined symbol: udev_monitor_new_from_netlink
error: undefined symbol: udev_monitor_receive_device
error: undefined symbol: udev_monitor_unref
error: undefined symbol: udev_unref
error: undefined symbol: udev_device_unref
error: undefined symbol: udev_device_get_property_value
error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
error: undefined symbol: udev_monitor_enable_receiving
```

It worked on Ubuntu 21.10.

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

** Package changed: nfs-utils (Ubuntu) => 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/1990315

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  New

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

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


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

[Touch-packages] [Bug 1988523] Re: Cannot install tomcat9 on ubuntu:18.04

[Thomas Bechtold]

This is not a systemd or tomcat bug. As I explained in 
https://bugs.launchpad.net/cloud-images/+bug/1988498 , a broken systemd package 
got removed from the archive but the broken version got included into the 
docker image.
We'll release a new docker image soon to fix the problem. Let's track that in 
https://bugs.launchpad.net/cloud-images/+bug/1988498 and close this bug here.

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

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

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

Title:
  Cannot install tomcat9 on ubuntu:18.04

Status in systemd package in Ubuntu:
  Invalid
Status in tomcat9 package in Ubuntu:
  Invalid

Bug description:
  ### Steps to reproduce

  1. `docker pull docker.io/library/ubuntu:18.04`
  2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash`
  2. Inside the docker container:
  ```bash
  apt-get update
  apt-get install -y tomcat9
  ```

  ### Expected result

  * `tomcat9` is installed successfully

  ### Actual result

  * Installation fails with unresolvable dependencies:

  ```bash
  root@c9849e6844d0:/# apt-get install -y tomcat9
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   tomcat9 : Depends: systemd (>= 215) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Attempting to install systemd results in the following:

  ```bash
  root@c9849e6844d0:/etc/apt# apt-get install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
 Recommends: libpam-systemd but it is not going to be installed
 Recommends: dbus but it is not going to be installed
 Recommends: networkd-dispatcher but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  ### Workaround

  * Installing tomcat9 works if you downgrade libsystemd:

  ```bash
  apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53
  ```

  ### Other info

  * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: 
`sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685`
  * Pulled from docker.io/library/ubuntu Fri Sep  2 07:57:03 UTC 2022

  I suspect this is caused by an issue in systemd having no version
  available that matches the latest libsystemd0, so I've included the
  `apt-cache policy` of systemd and libsystemd0 too.

  ```bash
  root@2d05688650c0:/# lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  ```

  ```
  root@2d05688650c0:/# apt-cache policy tomcat9
  tomcat9:
Installed: (none)
Candidate: 9.0.16-3ubuntu0.18.04.2
Version table:
   9.0.16-3ubuntu0.18.04.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
  root@2d05688650c0:/# apt-cache policy systemd
  systemd:
Installed: (none)
Candidate: 237-3ubuntu10.53
Version table:
   237-3ubuntu10.53 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   237-3ubuntu10.50 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  root@2d05688650c0:/# apt-cache policy libsystemd0
  libsystemd0:
Installed: 237-3ubuntu10.54
Candidate: 237-3ubuntu10.54
Version table:
   *** 237-3ubuntu10.54 100
  100 /var/lib/dpkg/status
   237-3ubuntu10.53 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   237-3ubuntu10.50 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  

[Touch-packages] [Bug 1961108] Re: network options greyed out in paprefs

[Thomas Boehm]

Bug still exists in Kubuntu 22.04.1 and Pulseaudio 15.99

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

Title:
  network options greyed out in paprefs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 21.10 which comes with pulseaudio
  1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
  greyed out. The problem seems to be, that the directory with the
  modules is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the
  modules in /usr/lib/pulse-15.0

  $ strace paprefs 2>&1 |grep /lib/pulse
  access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1 
ENOENT (No such file or directory)

  Creating a symlink /usr/lib/pulse-15.0 solves the problem

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


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

[Touch-packages] [Bug 1983414] Re: [BPO] dh-python 5.20220403 to focal

[Thomas Ward]

Marking this as Won't Fix because of identified issues and Unit
indicating that this should be withdrawn.

** Changed in: dh-python (Ubuntu Focal)
   Status: Incomplete => Won't Fix

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

Title:
  [BPO] dh-python 5.20220403 to focal

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python source package in Focal:
  Won't Fix

Bug description:
  [Impact]

   * This is needed to refresh the yt-dlp package as it has support for 
'environment markers'
   * This version could also be useful for other projects as it adds support 
for pyproject.

  [Scope]

  Backport from:
   * To me it makes sense to backport from jammy (LTS), though the version 
currently is the same as devel.

  Backport to:
   * focal

  
  [Other Info]

   * I have created a test backport in ppa:unit193/staging and have
  already utilized.

  [Testing]

  * focal:
  [x] Package builds without modification
  [x] dh-python installs cleanly and runs
  [?] pybuild-plugin-pyproject installs cleanly and runs

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


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

[Touch-packages] [Bug 1987356] Re: [BPO] elfutils/0.187-1 from Kinetic

[Thomas Ward]

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

Title:
  [BPO] elfutils/0.187-1 from Kinetic

Status in elfutils package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * elfutils ships many ELF/DWARF related tools that are interesting
  for users and developers of low level code.

   * More specifically, elfutils ships the debuginfod library and
  server.  Ubuntu is going to have a debuginfod server soon (see
  https://blog.sergiodj.net/2022/08/14/debuginfod-is-coming-to-
  ubuntu.html), and there have been many important changes that impact
  debuginfod's performance on 0.187.

  [Scope]

   * I will backport elfutils/0.187 from Kinetic.

   * I will backport elfutils/0.187 to Jammy.

  [Other Info]
   
   * None so far.

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


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

[Touch-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU

[Thomas Stieler]

Ok, I created this issue:

https://gitlab.freedesktop.org/drm/amd/-/issues/2088

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088
   https://gitlab.freedesktop.org/drm/amd/-/issues/2088

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

Title:
  UI glitches (coloured squares) in GTK application with AMDGPU

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After updating to (K)ubuntu 22.04, I see user interface glitches in
  GTK application.

  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.

  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.

  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.

  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
  The effect shows up there, too. So it's not only a problem of my
  current installation.

  I will upload some Gimp screenshots, so you can see what I mean...

  I'm not sure, but I tried to find the library used by all affected
  application: Maybe it's libcairo2, maybe not...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  stieler1622 F pulseaudio
   /dev/snd/pcmC3D0p:   stieler1622 F...m pulseaudio
   /dev/snd/controlC2:  stieler1622 F pulseaudio
   /dev/snd/controlC1:  stieler1622 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [148c:2402]
  InstallationDate: Installed on 2022-04-27 (55 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7B98
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill:
   
  Tags:  jammy ubuntu
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E1
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390-A PRO (MS-7B98)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7B98
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: 

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

[Thomas Dreibholz]

A helpful hwoto for users who want to update the weak KDC master key with 
state-of-the-art crypto:
https://docs.oracle.com/cd/E36784_01/html/E37126/st-mkey-1.html

-- 
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:
  New

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 1981697] [NEW] KDC: weak crypto in default settings

[Thomas Dreibholz]

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

Public security bug reported:

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)

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


** Tags: amd64 apport-bug jammy uec-images

** Information type changed from Private Security to Public Security

-- 
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:
  New

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 1979053] Re: UI glitches in GTK application with AMDGPU

[Thomas Stieler]

** Description changed:

  After updating to (K)ubuntu 22.04, I see user interface glitches in GTK
  application.
  
  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.
  
  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.
  
  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.
  
  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
- The effect show up there, too. So it's than a problem of my actual
+ The effect shows up there, too. So it's not a problem of my specific
  installation.
  
  I will upload some Gimp screenshots, so you can see what I mean...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After updating to (K)ubuntu 22.04, I see user interface glitches in GTK
  application.
  
  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.
  
  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.
  
  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.
  
  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
- The effect shows up there, too. So it's not a problem of my specific
+ The effect show up there, too. So it's than a problem of my actual
  installation.
  
  I will upload some Gimp screenshots, so you can see what I mean...
+ 
+ I'm not sure, but I tried to find the library used by all affected
+ application: Maybe it's libcairo2, maybe not...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After updating to (K)ubuntu 22.04, I see user interface glitches in GTK
  application.
  
  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.
  
  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.
  
  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.
  
  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
- The effect show up there, too. So it's than a problem of my actual
+ The effect shows up there, too. So it's not only a problem of my current
  installation.
  
  I will upload some Gimp screenshots, so you can see what I mean...
  
  I'm not sure, but I tried to find the library used by all affected
  application: Maybe it's libcairo2, maybe not...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  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 cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1979053

Title:
  UI glitches in GTK application with AMDGPU

Status in cairo package in Ubuntu:
  New

Bug description:
  After updating to (K)ubuntu 22.04, I see user interface glitches in
  GTK application.

  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.

  The glitches don't appear on a notebook with Intel 

[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

[Thomas Ward]

I've sponsored/uploaded both the Jammy and Kinetic debdiffs.  Kinetic is
accepted, jammy-proposed has to go through SRU.


Removing Sponsors as there is nothing more to sponsor here.

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Confirmed
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  Fix Released
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  Fix Released
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released
Status in apparmor source package in Jammy:
  Invalid
Status in quassel source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  Invalid
Status in quassel source package in Kinetic:
  Confirmed

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

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


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

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Thomas Ward]

If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.

Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark the package as
"Breaks:" for all Qt6 libraries.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011935

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

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

Re: [Touch-packages] [Bug 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd

[Thomas Schweikle]

I can't reproduce this issue on impish or jammy. It was fixed by a
change in handling sockets in systemd.

On Mon, May 9, 2022 at 6:25 PM Paride Legovini
<1957...@bugs.launchpad.net> wrote:
>
> Hello Thomas. You filed this bug against:
>
>   DistroRelease: Ubuntu 21.10
>   Package: openssh-server 1:8.4p1-6ubuntu2.1
>
> By "Solved by a later version of systemd and sshd". Do you mean that you
> found you can't reproduce the issue on Jammy (22.04 LTS)? Can you still
> reproruce the issue on Impish? Thank you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1957104
>
> Title:
>   updating openssh-server fails, because port 22 is in use by systemd
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+subscriptions
>


-- 
Thomas

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

Title:
  updating openssh-server fails, because port 22 is in use by systemd

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  openssh-server tries to restart itself, but openssh-server reports
  port 22 in use. This is true: systemd has taken port 22 to start sshd
  if one connects to port 22.

  two solutions:
  1. dont start sshd after installing.
 configure it without starting it afterwards.
  2. stop systemd listening on port 22
 before starting sshd, then start sshd,
 terminate it after configuring, then
 start systemd listening on port 22 again.

  Second problem:
  starting ssh.service does not check if "/run/sshd" exists. This directory has 
to be created before sshd is started. Unclear if this is an error with sshd not 
creating this directory before dropping privileges or if this has to be done 
once while installing. IMHO the first is the case.

  
  Workaround:
  systemctl stop ssh.service
  systemctl disable ssh.service
  apt upgrade
  systemctl enable ssh.service
  killall sshd
  mkdir /run/sshd
  systemctl start ssh.service

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: openssh-server 1:8.4p1-6ubuntu2.1
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Jan 11 19:11:47 2022
  InstallationDate: Installed on 2021-08-18 (146 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect

[Thomas Schweikle]

xubuntu and kubuntu, as lubuntu do use pipewire for audio.
kali switched last night to use it.
openSUSE did so too.

i did not test on a plain vanilla gnome based ubuntu until now. Will do
it later this day (if time permits).

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

Title:
  [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect,
  disconnect

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Paired Bluetooth devices are connected, then disconnected, connected
  again, then finally disconected.

  This is with
  - Ubuntu, xUbuntu 21.10
  - Ubuntu, xUbuntu 22.04(beta)

  It works with
  - kali (latest)
  - debian 11.3 (latest)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Apr 13 13:31:07 2022
  InstallationDate: Installed on 2021-08-18 (238 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BWS33U00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 1.17
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET52WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:3994 acl:7 sco:0 events:403 errors:0
TX bytes:46327 acl:7 sco:0 commands:367 errors:0

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


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

[Touch-packages] [Bug 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect

[Thomas Schweikle]

These modules seem to collide with pipewire-media-session, but are
required by bluez-stack to connect bluetooth headsets (or other devices)
to pulseaudio.

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

Title:
  [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect,
  disconnect

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Paired Bluetooth devices are connected, then disconnected, connected
  again, then finally disconected.

  This is with
  - Ubuntu, xUbuntu 21.10
  - Ubuntu, xUbuntu 22.04(beta)

  It works with
  - kali (latest)
  - debian 11.3 (latest)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Apr 13 13:31:07 2022
  InstallationDate: Installed on 2021-08-18 (238 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BWS33U00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 1.17
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET52WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:3994 acl:7 sco:0 events:403 errors:0
TX bytes:46327 acl:7 sco:0 commands:367 errors:0

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


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

[Touch-packages] [Bug 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect

[Thomas Schweikle]

Meanwhile even the distros working until yesterday stopped working today
(5. May 2022 around 22:00).

The bug seems related to pipewire and switching to this new infrastructure.
It breaks nearly everything related with sound and bluetooth.

Modules involved:
- pipewire-pulse
- wireplumber

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

Title:
  [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect,
  disconnect

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Paired Bluetooth devices are connected, then disconnected, connected
  again, then finally disconected.

  This is with
  - Ubuntu, xUbuntu 21.10
  - Ubuntu, xUbuntu 22.04(beta)

  It works with
  - kali (latest)
  - debian 11.3 (latest)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Apr 13 13:31:07 2022
  InstallationDate: Installed on 2021-08-18 (238 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BWS33U00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 1.17
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET52WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:3994 acl:7 sco:0 events:403 errors:0
TX bytes:46327 acl:7 sco:0 commands:367 errors:0

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


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

[Touch-packages] [Bug 1968028] Re: unattended-upgrades if enabled wont disable interactivemode

[Thomas Schweikle]

Solved by a new version of upgrade tools.

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

Title:
  unattended-upgrades if enabled wont disable interactivemode

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades if enabled wont disable interactive mode. In tune an 
unattended upgrade stops waiting for input never to expect, because the dialog 
displayed is never seen by anyone.
  Updates will not be installed at all in some cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: unattended-upgrades 2.8ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr  6 12:27:22 2022
  InstallationDate: Installed on 2021-08-18 (231 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd

[Thomas Schweikle]

Solved by a later version of systemd and sshd.
To have it work as intended sshd has to be compiled with different options set.

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

Title:
  updating openssh-server fails, because port 22 is in use by systemd

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  openssh-server tries to restart itself, but openssh-server reports
  port 22 in use. This is true: systemd has taken port 22 to start sshd
  if one connects to port 22.

  two solutions:
  1. dont start sshd after installing.
 configure it without starting it afterwards.
  2. stop systemd listening on port 22
 before starting sshd, then start sshd,
 terminate it after configuring, then
 start systemd listening on port 22 again.

  Second problem:
  starting ssh.service does not check if "/run/sshd" exists. This directory has 
to be created before sshd is started. Unclear if this is an error with sshd not 
creating this directory before dropping privileges or if this has to be done 
once while installing. IMHO the first is the case.

  
  Workaround:
  systemctl stop ssh.service
  systemctl disable ssh.service
  apt upgrade
  systemctl enable ssh.service
  killall sshd
  mkdir /run/sshd
  systemctl start ssh.service

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: openssh-server 1:8.4p1-6ubuntu2.1
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Jan 11 19:11:47 2022
  InstallationDate: Installed on 2021-08-18 (146 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1915707] Re: keyboard settings not applied

[Thomas Schweikle]

Solved with a later version of required packages

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

Title:
  keyboard settings not applied

Status in console-setup package in Ubuntu:
  Fix Released

Bug description:
  Global keyboard settings are set in /etc/defaults/keyboard:

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp"
  BACKSPACE="guess"

  These settings are not active any more after upgrading from focal to groovy. 
Same applies if upgrading from groovy to hirsute. The file 
/etc/defaults/keyboard is untouched, but any console uses an US keyboard.
  Same applies for X11-Sessions: all users have their keyboard defaulted to US 
layout. Any other layouts configured for any user vanishes. Configurations have 
to be done again as it they never where set.

  For all users settings -> Keyboard -> Keyboard Layout is set to use
  system-wide keyboard settings. This is set to US layout. This seems
  not changeable at all! If this depends on file /etc/defaults/keyboard.
  It does not respect this file.

  There has to be a way to set some other keyboard layout system-wide.
  Not only for one session or one user! And: this setting shall not be
  overwritten by upgrading. And it shall not be ignored after upgrading!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: console-setup 1.195ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb 15 12:10:46 2021
  InstallationDate: Installed on 2014-01-31 (2572 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago)

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


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

[Touch-packages] [Bug 1852474] Re: cups not printing if authentication required by server

[Thomas Schweikle]

Solved upstream with later versions of cups.

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

Title:
  cups not printing if authentication required by server

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  cups does not print if servers require authenticated users to print.
  No login-dialog is shown. Print jobs are on hold, waiting for
  legitimization. But no legitimization dialog will be shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 13 19:23:18 2019
  InstallationDate: Installed on 2019-09-09 (65 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat:
   device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
   device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', 
'/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied
   grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Touch-packages] [Bug 1856187] Re: Cups wont print to smb-shared printer requiring user authentication via kerberos

[Thomas Schweikle]

Solved upstream with later versions of cups

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

Title:
  Cups wont print to smb-shared printer requiring user authentication
  via kerberos

Status in cups package in Ubuntu:
  New

Bug description:
  Setup:
  - Print server part of an AD domain. Print server requires authentication.
  - Ubuntu client with cups-server. The client is part of the AD domain. The 
client does not share printers (and never will).
  - User authenticated by AD within the AD domain.
  - Now user wants to print. Printer is set up:
  
  UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837
  AuthInfoRequired none
  Info KONICA MINOLTA C364e
  Location E017
  MakeModel KONICA MINOLTA C364SeriesPS(P)
  DeviceURI smb:///drucker-muc
  PortMonitor tbcp
  State Idle
  StateTime 1576145797
  ConfigTime 1576146371
  Type 8401100
  Accepting Yes
  Shared No
  JobSheets none none
  QuotaPeriod 0
  PageLimit 0
  KLimit 0
  OpPolicy default
  ErrorPolicy retry-job
  Option print-quality 3
  

  Since AuthInfoRequired is set to "none" cups thinks everyone can print
  and no authentication would be necessary. That's not true: the printer
  requires authentication. Maybe a bug.

  This print server requires any user to be authenticated and have a
  kerberos ticket. This is true. The user has a kerberos ticket and this
  user is allowed to print. The users kerberos ticket cache is available
  in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it
  into account. May be a bug too.

  Changing "AuthInfoRequired" from "none" to "username,password" allows
  cups to print. But this has to be done editing
  /etc/cups/printers.conf. The web printer configuration just does not
  allow to set anything else than "none". This is a bug.

  Documentation misses what "AuthInfoRequired" has to be set for if
  kerberos authentication will be used. This is a bug too!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Dec 12 13:54:01 2019
  InstallationDate: Installed on 2019-09-09 (93 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat:
   device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
   device for PDF: cups-pdf:/
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied
   grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission 
denied
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Touch-packages] [Bug 1971534] [NEW] connecting bluetooth devices fails

[Thomas Schweikle]

Public bug reported:

Bluetooth devices do not connect. Or better: they connect, disconnect,
connect, then finally disconnect.

It is the same using graphical tools or cli.

It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35

Working distros are:
- kali (latest rolling)
- openSUSE Leap 15.4
- openSUSE tumbleweed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Wed May  4 08:57:30 2022
InstallationDate: Installed on 2021-08-18 (258 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BWS33U00
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.release: 1.17
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET52WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS33U00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS33U00
dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:4581 acl:7 sco:0 events:435 errors:0
TX bytes:46460 acl:7 sco:0 commands:399 errors:0

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


** Tags: amd64 apport-bug jammy

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

Title:
  connecting bluetooth devices fails

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth devices do not connect. Or better: they connect, disconnect,
  connect, then finally disconnect.

  It is the same using graphical tools or cli.

  It is the same for
  - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
  - debian 11.3
  - fedora 35

  Working distros are:
  - kali (latest rolling)
  - openSUSE Leap 15.4
  - openSUSE tumbleweed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed May  4 08:57:30 2022
  InstallationDate: Installed on 2021-08-18 (258 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BWS33U00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 1.17
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET52WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:4581 acl:7 sco:0 events:435 errors:0
TX bytes:46460 acl:7 sco:0 commands:399 errors:0

To manage notifications about this bug go to:

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Thomas]

Unsure if this helps. I too have this issue with my university's wifi. I
was able to work with one of the networking people in the tech center
and we found that 22.04 would not even show up as attempting to connect
on their end, (and we verified that 21.10 successfully connected as
expected. Unsure how much this helps but I thought it would be useful
information.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Thomas]

Simon, I changed it to DEFAULT@SECLEVEL=0 and ran sudo systemctl restart
wpa_supplicant.service, but unfortunately it did not make any
difference.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Thomas]

Simon, I tried your suggestion followed by running sudo systemctl
restart wpa_supplicant.service and I still am unable to connect.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1970207] [NEW] aureport shows "Number of failed logins" increased after successful ssh login

[Thomas]

Public bug reported:

aureport version 2.8.5
Ubuntu 20.04 LTS

Using ssh to login to the system and then evuating aureport shows the
"Number of failed logins" increased - every time I repeat ssh.

When I use a wrong password the "Number of failed logins" and the
"Number of failed authentications" increases.

Summary Report
==
Range of time in logs: 01/01/70 00:00:00.000 - 25/04/22 12:43:35.847
Selected time for report: 01/01/70 00:00:00 - 25/04/22 12:43:35.847
Number of changes in configuration: 0
Number of changes to accounts, groups, or roles: 0
Number of logins: 5
Number of failed logins: 10
Number of authentications: 8
Number of failed authentications: 5
Number of users: 6
Number of terminals: 9
Number of host names: 3
Number of executables: 5
Number of commands: 1
Number of files: 0
Number of AVC's: 0
Number of MAC events: 0
Number of failed syscalls: 0
Number of anomaly events: 0
Number of responses to anomaly events: 0
Number of crypto events: 0
Number of integrity events: 0
Number of virt events: 0
Number of keys: 0
Number of process IDs: 27186
Number of events: 163290


Regards

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


** Tags: auditd aureport

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

Title:
  aureport shows "Number of failed logins" increased after successful
  ssh login

Status in audit package in Ubuntu:
  New

Bug description:
  aureport version 2.8.5
  Ubuntu 20.04 LTS

  Using ssh to login to the system and then evuating aureport shows the
  "Number of failed logins" increased - every time I repeat ssh.

  When I use a wrong password the "Number of failed logins" and the
  "Number of failed authentications" increases.

  Summary Report
  ==
  Range of time in logs: 01/01/70 00:00:00.000 - 25/04/22 12:43:35.847
  Selected time for report: 01/01/70 00:00:00 - 25/04/22 12:43:35.847
  Number of changes in configuration: 0
  Number of changes to accounts, groups, or roles: 0
  Number of logins: 5
  Number of failed logins: 10
  Number of authentications: 8
  Number of failed authentications: 5
  Number of users: 6
  Number of terminals: 9
  Number of host names: 3
  Number of executables: 5
  Number of commands: 1
  Number of files: 0
  Number of AVC's: 0
  Number of MAC events: 0
  Number of failed syscalls: 0
  Number of anomaly events: 0
  Number of responses to anomaly events: 0
  Number of crypto events: 0
  Number of integrity events: 0
  Number of virt events: 0
  Number of keys: 0
  Number of process IDs: 27186
  Number of events: 163290


  Regards

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Thomas]

I am facing a similar problem after upgrading my Laptop from 21.10 to
22.04. I lost Wifi during the upgrade process, which also meant that
refreshing the snap packages failed. But I was unable to connect to my
Wifi again, even after reboot. I have a Unifi network set up for WPA
enterprise, using a Let's encrypt certificate. It works fine on all my
Windows machines and all machines on older Ubuntu.

I tried the work-around in comment #22, but sadly it does not work for
me. I am seeing an "internal error" in syslog:

Apr 23 10:41:31 thomas-laptop wpa_supplicant[3116]: SSL: SSL3 alert: write 
(local SSL3 detected an error):fatal:internal error
Apr 23 10:41:31 thomas-laptop wpa_supplicant[3116]: OpenSSL: openssl_handshake 
- SSL_connect error:0A0C0103:SSL routines::internal error
Apr 23 10:41:32 thomas-laptop wpa_supplicant[3116]: wlp0s20f3: 
CTRL-EVENT-EAP-FAILURE EAP authentication failed
Apr 23 10:41:32 thomas-laptop kernel: [  431.697248] wlp0s20f3: deauthenticated 
from xx:xx:xx:xx:xx:xx (Reason: 23=IEEE8021X_FAILED)

I attached my full /var/log/syslog output.

** Attachment added: "wpa-auth-error.log"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+attachment/5582874/+files/wpa-auth-error.log

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1968875] [NEW] Bluetooth devices disconnect, connect, disconnect

[Thomas Schweikle]

Public bug reported:

Paired Bluetooth devices are connected, then disconnected, connected
again, then finally disconected.

This is with
- Ubuntu, xUbuntu 21.10
- Ubuntu, xUbuntu 22.04(beta)

It works with
- kali (latest)
- debian 11.3 (latest)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Wed Apr 13 13:31:07 2022
InstallationDate: Installed on 2021-08-18 (238 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BWS33U00
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.release: 1.17
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET52WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS33U00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS33U00
dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:3994 acl:7 sco:0 events:403 errors:0
TX bytes:46327 acl:7 sco:0 commands:367 errors:0

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


** Tags: amd64 apport-bug jammy

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

Title:
  Bluetooth devices disconnect, connect, disconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  Paired Bluetooth devices are connected, then disconnected, connected
  again, then finally disconected.

  This is with
  - Ubuntu, xUbuntu 21.10
  - Ubuntu, xUbuntu 22.04(beta)

  It works with
  - kali (latest)
  - debian 11.3 (latest)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Apr 13 13:31:07 2022
  InstallationDate: Installed on 2021-08-18 (238 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BWS33U00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 1.17
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET52WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:AE:51:86  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:3994 acl:7 sco:0 events:403 errors:0
TX bytes:46327 acl:7 sco:0 commands:367 errors:0

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


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

[Touch-packages] [Bug 1968028] Re: unattended-upgrades if enabled wont disable interactivemode

[Thomas Schweikle]

This can be seen with
- 16.04
- 18.04
- 20.04
- 21.10
- 22.04

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

Title:
  unattended-upgrades if enabled wont disable interactivemode

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades if enabled wont disable interactive mode. In tune an 
unattended upgrade stops waiting for input never to expect, because the dialog 
displayed is never seen by anyone.
  Updates will not be installed at all in some cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: unattended-upgrades 2.8ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr  6 12:27:22 2022
  InstallationDate: Installed on 2021-08-18 (231 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1968028] [NEW] unattended-upgrades if enabled wont disable interactivemode

[Thomas Schweikle]

Public bug reported:

unattended-upgrades if enabled wont disable interactive mode. In tune an 
unattended upgrade stops waiting for input never to expect, because the dialog 
displayed is never seen by anyone.
Updates will not be installed at all in some cases.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: unattended-upgrades 2.8ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr  6 12:27:22 2022
InstallationDate: Installed on 2021-08-18 (231 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  unattended-upgrades if enabled wont disable interactivemode

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades if enabled wont disable interactive mode. In tune an 
unattended upgrade stops waiting for input never to expect, because the dialog 
displayed is never seen by anyone.
  Updates will not be installed at all in some cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: unattended-upgrades 2.8ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr  6 12:27:22 2022
  InstallationDate: Installed on 2021-08-18 (231 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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