[Touch-packages] [Bug 2060906] [NEW] attempt to add opensc using modutil suddenly fails

2024-04-10 Thread Garrett Warnell
Public bug reported:

The following command to add the OpenSC PKCS11 module for use in, eg,
Chrome fails:

modutil -dbdir sql:$HOME/.pki/nssdb -add "OpenSC" -libfile
/usr/lib/opensc-pkcs11.so


This has worked for me several times in the past, but today Chrome stopped 
detecting my smart card and when I tried to re-initialize ~/.pki/nssdb and 
re-add OpenSC using the command above, I received the following error:

ERROR: Failed to add module "OpenSC". Probabl cause : "Unknown code ___P
3".

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

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

Title:
  attempt to add opensc using modutil suddenly fails

Status in nss package in Ubuntu:
  New

Bug description:
  The following command to add the OpenSC PKCS11 module for use in, eg,
  Chrome fails:

  modutil -dbdir sql:$HOME/.pki/nssdb -add "OpenSC" -libfile
  /usr/lib/opensc-pkcs11.so

  
  This has worked for me several times in the past, but today Chrome stopped 
detecting my smart card and when I tried to re-initialize ~/.pki/nssdb and 
re-add OpenSC using the command above, I received the following error:

  ERROR: Failed to add module "OpenSC". Probabl cause : "Unknown code
  ___P 3".

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


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


[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-10 Thread Aaron Rainbolt
** Also affects: ubuntu-meta (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: wslu (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Noble)
Milestone: None => ubuntu-24.04

** Changed in: wslu (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New
Status in wslu source package in Noble:
  New

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

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


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


[Touch-packages] [Bug 2060898] [NEW] Trying to install gimp-help-en threatens to install wslu

2024-04-10 Thread Aaron Rainbolt
Public bug reported:

Filing this against ubuntu-meta since I believe this is a seed problem
that potentially affects all variants of Ubuntu (flavors or otherwise).

wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
such as for converting Linux paths to a Windows paths or creating Linux
application shortcuts on the Windows 10 Desktop." Obviously this package
should *never* be installed on a desktop or even on most VMs, but only
within WSL instances. However...

wslu provides the virtual package www-browser, as one of its features is
to open links in Windows 10 using the default browser set there. This
means that if a package depends or recommends www-browser, it may
attempt to pull in one of several packages, wslu included. In the past,
this hasn't been a problem because Firefox was present on all flavor
images, and Firefox provides www-browser as well. However, now that
Firefox is a Snap, it is possible for Firefox to be installed without
the firefox transitional apt package being installed. (This is the case
in a default installation of Kubuntu Noble Beta.) As it turns out,
Kubuntu Noble Beta ships with *no* packages that provide www-browser,
meaning that any package that depends on it will have to install a new
browser.

Due to some stroke of misfortune, apt is picking wslu out of all
packages as the package for this use case. Installing gimp-help-en will
also install www-browser, which results in wslu becoming installed.

wslu causes quite a few problems when installed on a desktop system -
among them, the syslog is spammed with errors due to the system not in
fact being a WSL VM, audio breaks in weird ways, and application
launchers sometimes fail. Why this happens is unclear, but the issues
appear to resolve once wslu is removed from the system. It is therefore
probably a good idea to avoid wslu becoming installed on accident in
this way.

Probably the best way to resolve this is to ensure that some package
that provides www-browser is available on every Ubuntu image. This could
be done via seeding or by adding a package to ubuntu-minimal.
Alternatively, wslu could be set to no longer provide www-browser,
though it's unclear if that would break its functionality.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could 

[Touch-packages] [Bug 2049988] Re: Latest kernel kills wifi.

2024-04-10 Thread Patrick M
Any news on this?

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

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


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


[Touch-packages] [Bug 2060809] Re: davinci not opening bro

2024-04-10 Thread Daniel van Vugt
The integrated GPU of your Intel i5-6400 is all that I can see, which
understandably may not be enough to run Davinci. What error do you see
exactly?

Also note that errors have been reported on your installation media,
probably meaning the USB drive used to install Ubuntu was faulty. You
may want to reinstall Ubuntu using a different thumb drive.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  davinci not opening bro

Status in Ubuntu:
  Incomplete

Bug description:
  gpu no to supporter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:14:28 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
  InstallationDate: Installed on 2024-04-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: ZEBRONICS H110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.name: H110
  dmi.board.vendor: ZEBRONICS
  dmi.board.version: Ver:2.32
  dmi.chassis.type: 3
  dmi.chassis.vendor: ZEBRONICS
  dmi.chassis.version: H110
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku:
  dmi.product.name: H110
  dmi.sys.vendor: ZEBRONICS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
  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

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


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


[Touch-packages] [Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled

2024-04-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/pam/+git/pam/+merge/464052

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  Triaged
Status in pam package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  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
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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


[Touch-packages] [Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled

2024-04-10 Thread Andreas Hasenack
We won't fix this in openssh for Ubuntu 24.04 due to the change in
behavior that it introduces at this stage in the cycle, but it should be
fixed in 24.10.

As for 24.04, what we will attempt to do is suppress the pam_env warning
in the src:pam package.

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

** Changed in: openssh (Ubuntu)
Milestone: None => later

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

** Changed in: pam (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: pam (Ubuntu)
Milestone: None => ubuntu-24.04

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  Triaged
Status in pam package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  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
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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


[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd

2024-04-10 Thread Nick Rosbrook
** Tags removed: foundations-todo

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

Title:
  sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
  privilege separation directory: /run/sshd

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Mantic:
  New

Bug description:
  Symptom: ssh.service is not running and not accepting new SSH
  connections and returns socket closed error upon attempted connection.
  ssh.service shows a failed with error message "Missing privilege
  separation directory: /run/sshd".

  The following line is needed in the SystemD Unit configuration of the
  ssh.service file for the openssh-server package to fix what appears to
  be a race condition when ssh.service is sometimes started before
  systemd-tmpfiles-setup.service is finished processing the file in
  /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the
  /run/sshd directory that is required by ssh.service to start property.

  There might be more depth or an alternative reason to why /run/sshd/
  still didn't exist after using ```systemctl reset-failed
  ssh.service```.  So more investigation is needed by someone with more
  background in systemd-tmpfiles-setup.service and openssh-server
  package after it when to socket activation.

  = Error Messages =

  ```
  $journalctl -u ssh.service -b-1

  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 1.
  Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 2.
  Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 3.
  Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 4.
  Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 5.
  Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Start request repeated too 
quickly.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:57 server systemd[1]: Failed 

[Touch-packages] [Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

2024-04-10 Thread Anders Kaseorg
Seems resolved.

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

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  Fix Released

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  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:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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


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


[Touch-packages] [Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled

2024-04-10 Thread Andreas Hasenack
Commit that added the warning to pam_env.c: https://github.com/linux-
pam/linux-pam/commit/ecd526743a27157c5210b0ce9867c43a2fa27784

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  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
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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


[Touch-packages] [Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled

2024-04-10 Thread Andreas Hasenack
Deprecation warning introduced here: https://github.com/linux-pam/linux-
pam/releases/tag/v1.5.0

Release notes for all releases up to 1.6.1 don't mention this again, so
it's still there: https://github.com/linux-pam/linux-pam/releases

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  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
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

2024-04-10 Thread Aleksandr Mikhalitsyn
** Patch added: "debdiff.diff"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2059550/+attachment/5763468/+files/debdiff.diff

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to skip this tests
  too for now.

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


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

[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

2024-04-10 Thread Aleksandr Mikhalitsyn
Ok, lxc/1:5.0.3-2ubuntu4 was uploaded and it's getting better but,
unfortunately, "lxc-test-unpriv" test wasn't skipped really.

Despite this bug
(https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461) I
was able to make my local autopkgtest environment to work:

autopkgtest \
  --apt-upgrade \
  --shell-fail \
  --output-dir dep8-lxc-pkg-ubuntu \
lxc-5.0.3/ \
  -- lxd --vm ubuntu-daily:noble -c limits.cpu=10 -c limits.memory=15GiB

==
PASS: lxc-tests: /usr/bin/lxc-test-snapshot
PASS: lxc-tests: /usr/bin/lxc-test-startone
PASS: lxc-tests: /usr/bin/lxc-test-state-server
PASS: lxc-tests: /usr/bin/lxc-test-symlink
PASS: lxc-tests: /usr/bin/lxc-test-sys-mixed
PASS: lxc-tests: /usr/bin/lxc-test-sysctls
IGNORED: lxc-tests: /usr/bin/lxc-test-unpriv
PASS: lxc-tests: /usr/bin/lxc-test-usernic
PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
PASS: lxc-tests: /usr/bin/lxc-test-utils

SUMMARY: pass=55, fail=0, ignored=1
autopkgtest [17:46:01]: test exercise: ---]
autopkgtest [17:46:02]: test exercise:  - - - - - - - - - - results - - - - - - 
- - - -
exercise PASS
autopkgtest [17:46:02]: test basics-create-destroy: preparing testbed


Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
(Reading database ... 69249 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [17:50:16]: test no-devel: [---
+ grep LXC_DEVEL /usr/include/lxc/version.h
+ grep 0
#define LXC_DEVEL 0
autopkgtest [17:50:17]: test no-devel: ---]
no-devel PASS
autopkgtest [17:50:17]: test no-devel:  - - - - - - - - - - results - - - - - - 
- - - -
autopkgtest [17:50:18]:  summary
exercise PASS
basics-create-destroy PASS (superficial)
no-devel PASS
==

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - 

[Touch-packages] [Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled

2024-04-10 Thread Andreas Hasenack
Fixing this in noble at this time will require a feature freeze
exception, because we would be changing behavior.

The default for user_readenv in pam_env is 0 (off). In the sshd config,
ubuntu/debian ship a pam config that sets it to on (1), therefore
~/.pam_environment will be read if it exists.

Upstream has flagged that this feature (of reading user-provided env var
files) will be removed in the future, and is thus catching the setting
of user_readenv=1 and showing the deprecation notice warning. To get rid
of the warning, we have to stop setting user_readenv=1, which will
*disable* the feature. Meaning, in noble, if we make this change,
~/.pam_environment (or the file specified by user_envfile) will NOT be
read anymore.

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  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
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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


[Touch-packages] [Bug 1942260] Re: compress firmware in /lib/firmware

2024-04-10 Thread Dave Jones
This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.

** Changed in: linux-firmware-raspi (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux-firmware-raspi (Ubuntu Mantic)
   Status: Confirmed => Won't Fix

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

Title:
  compress firmware in /lib/firmware

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Mantic:
  Fix Released
Status in initramfs-tools source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware-raspi source package in Mantic:
  Won't Fix

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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


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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

2024-04-10 Thread Nick Rosbrook
** Tags added: update-excuse

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to skip this tests
  too for now.

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


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


[Touch-packages] [Bug 2060666] Re: Memory leak in krb5 version 1.17

2024-04-10 Thread Athos Ribeiro
** Changed in: krb5 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Memory leak in krb5 version 1.17

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

Bug description:
  Commit 1cd2821 altered the memory
  management of krb5_gss_inquire_cred(), introducing defcred to act as
  an owner pointer when the function must acquire a default credential.
  The commit neglected to update the code to release the default cred
  along the successful path.  The old code does not trigger because
  cred_handle is now reassigned, so the default credential is leaked.

  The commit 
https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8 
fixes the leak.
  It's been part of newer krb5 releases (Jammy, and Noble have the releases 
with the fix). Bionic doesn't have the commit the introduced the memory leak.

  So this fix needs to be backported to Focal (only).

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


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


[Touch-packages] [Bug 2060810] Re: Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
Thank you for the quick reply, and the explanation.

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2060810] Re: Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread John Johansen
More applications will be getting confinement, on an individual level I
don't think it will be everything from debs. In this case its because it
uses unprivileged user namespaces. Which is now being restricted and
treated as a semi-privileged because it gives access to several
privileged kernel interfaces. Those privilege kernel interfaces should
be in theory safe, but the reality is that they aren't. Unprivileged
user namespaces are the first step in almost every kernel exploit chain
for the last 7 or so years.

In pwn2own last year 4 of the 5 exploits used unprivileged user
namespaces. This year all 4 did, however if you turn the restriction on
(present in 23.10 but not enabled by default) everyone one of the
exploits are blocked. The current step is far from perfect, but we are
working on improving it.

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2060810] Re: Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
In this case, Wike is installed as a deb, not snap. Why is it confined?

As far as I know, this is not how deb packages worked. Is this a very
new decision to confine all the apps even if they are installed via apt?

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

2024-04-10 Thread Bryce Harrington
** Tags removed: server-todo

** Tags removed: regression-update

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  2024-02-29 15:36:05.156467935 +
  +++ network.c 2024-02-29 15:36:38.733324350 +
  @@ -934,7 +934,8 @@
 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
  if (dienow)
  - die(s, daemon->addrbuff, EC_BADNET);
  + my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
  + //die(s, daemon->addrbuff, EC_BADNET);
  else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
  $ 

  If bind-dynamic is set, it should be modified so that it works even if
  errno==98.

  For reference, in the case of dnsmasq 2.80, the code is as follows, so
  no error occurs.

  network.c
  699 static int make_sock(union mysockaddr *addr, int type, int dienow)
  700 {
  701   int family = addr->sa.sa_family;
  702   int fd, rc, opt = 1;
  (snip)
  715 err:
  716   errsave = errno;
  717   port = prettyprint_addr(addr, daemon->addrbuff);
  718   if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
  719 sprintf(daemon->addrbuff, "port %d", port);
  720   s = _("failed to create listening socket for %s: %s");
  721   
  722   if (fd != -1)
  723 close (fd);
  724 
  725   errno = errsave;
  726 
  727   if (dienow)
  728 {
  729   /* failure to bind addresses given by --listen-address at 
this
  729  point
  730  is OK if we're doing bind-dynamic */
  731   if (!option_bool(OPT_CLEVERBIND))
  

[Touch-packages] [Bug 2060810] Re: Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread John Johansen
There are vague plans, yes. The time line of it has not been scoped, but
it would be something akin to what happens on macos when you try to run
a downloaded application for the first time and you have to go into
their security config to allow it.

The application will still be "confined" but it may not get its own
individual profile and share one with others the user has downloaded.
The unconfined profile's will also get developed into full profiles. The
plan is that unconfined profiles won't be a standard thing but an
exception.

Another thing going to happen in the next upload is bwrap gets its own
profile. Applications using bwrap might work through the bwrap profile.
There will still be cases where they will need their own profile, but
the bwrap profile will cover several cases that don't work today.
Applications that have already received an unconfined profile will
continue to work that way.

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

2024-04-10 Thread Athos Ribeiro
Moving to invalid as per the last comment.

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

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  2024-02-29 15:36:05.156467935 +
  +++ network.c 2024-02-29 15:36:38.733324350 +
  @@ -934,7 +934,8 @@
 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
  if (dienow)
  - die(s, daemon->addrbuff, EC_BADNET);
  + my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
  + //die(s, daemon->addrbuff, EC_BADNET);
  else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
  $ 

  If bind-dynamic is set, it should be modified so that it works even if
  errno==98.

  For reference, in the case of dnsmasq 2.80, the code is as follows, so
  no error occurs.

  network.c
  699 static int make_sock(union mysockaddr *addr, int type, int dienow)
  700 {
  701   int family = addr->sa.sa_family;
  702   int fd, rc, opt = 1;
  (snip)
  715 err:
  716   errsave = errno;
  717   port = prettyprint_addr(addr, daemon->addrbuff);
  718   if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
  719 sprintf(daemon->addrbuff, "port %d", port);
  720   s = _("failed to create listening socket for %s: %s");
  721   
  722   if (fd != -1)
  723 close (fd);
  724 
  725   errno = errsave;
  726 
  727   if (dienow)
  728 {
  729   /* failure to bind addresses given by --listen-address at 
this
  729  point
  730  is OK if we're doing bind-dynamic */
  731   

[Touch-packages] [Bug 2060806] Re: Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-good1.0 package in Ubuntu:
  In Progress

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

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


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


[Touch-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git

2024-04-10 Thread Andreas Karlson
Till,
I have pushed another commit that fixes this regression.
https://github.com/OpenPrinting/cups/issues/934#issuecomment-2047651106

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

Title:
  cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported
  commits from 2.4.x git

Status in cups package in Ubuntu:
  In Progress

Bug description:
  While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 
2.4.7-1.2ubuntu5),
  I noticed that cupsd crashes consistently after closing my Firefox tab / 
window.
  The title of the crash (from the bug-report window) is "cupsd crashed with 
SIGSEGV in ???()"

  I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying
  some updates from the noble and noble-proposed pockets.

  Reproduction steps:
  1. Open Firefox and manage CUPS on http://localhost:631
  2. Go to Administration -> Printers -> Add Printer and choose your printer
  3. Add your printer (I used the ipps:// protocol to manage the printer)
  4. After clicking the "Add printer" button, immediately close your Firefox tab
  5. cupsd will crash and Ubuntu will display a bug-report popup

  Versions:
  Firefox - 124.0.1-1 r4033
  CUPS - 2.4.7-1.2ubuntu5

  Printer:
  Lexmark MS415dn (supported)

  I am unable to reproduce this bug on versions prior to
  2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2).

  Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from 
the 2.4.x upstream git branch, so I also opened an issue on GitHub:
  https://github.com/OpenPrinting/cups/issues/934

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


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.3 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
The Debian maintainer pointed out 1.90.3 is the same as 1.90.4 except
for the version change so 1.90.3 is good enough for the fix you are
wanting.

** Summary changed:

- Upgrade UPower to 1.90.4 to lower cpu and disk usage
+ Upgrade UPower to 1.90.3 to lower cpu and disk usage

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

Title:
  Upgrade UPower to 1.90.3 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Changed in: upower (Ubuntu)
   Status: New => Triaged

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

** Tags added: noble upgrade-software-version

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Bug watch added: Debian Bug tracker #1068763
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068763

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

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2059830] Re: Port software-properties-gtk to GTK 4

2024-04-10 Thread Jeremy Bícha
** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Port software-properties-gtk to GTK 4

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  It still uses old GTK 3. Please upgrade it to GTK 4!

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


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


[Touch-packages] [Bug 2060813] [NEW] Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread ktecho
Public bug reported:

Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

Upower 1.90.4 has been released, which fixes an issue making some users
(maybe having Logitech devices and others) use more cpu and disk than
intended.

For me (I have Logitech mouse receiver), when I look at htop without
doing anything, I see upower appearing there as using CPU.

If the upgrade cannot be done at this stage, maybe the patch can be
added to 1.90.2 (the current version in the repository of 24.04):
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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

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

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  New

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2059830] Re: Port software-properties-gtk to GTK 4

2024-04-10 Thread Jeremy Bícha
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Port software-properties-gtk to GTK 4

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  It still uses old GTK 3. Please upgrade it to GTK 4!

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


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


[Touch-packages] [Bug 2060810] Re: Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
In the future, will there be some mechanism for allowing apps to run
without adding profiles for each app, like what is happening now?

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2060810] [NEW] Wike does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
Public bug reported:

Wike (deb package/compiled version) does not run in Ubuntu 24.04
possibly due to some interference between apparmor and webkit.

```
$ wike

(process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
bwrap: setting up uid map: Permission denied

** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
Trace/breakpoint trap
```

A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
```
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"

abi ,
include 

profile wike /usr/bin/wike flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}
```
Then run `sudo systemctl restart apparmor.service`


This is also reported in GitHub for Wike
https://github.com/hugolabe/Wike/issues/181

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

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

Title:
  Wike does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  Wike (deb package/compiled version) does not run in Ubuntu 24.04
  possibly due to some interference between apparmor and webkit.

  ```
  $ wike

  (process:11686): Gtk-WARNING **: 02:55:41.246: Unknown key gtk-modules in 
/home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (wike:11686): ERROR **: 02:55:41.837: Failed to fully launch dbus-proxy: 
Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround is to create the file `/etc/apparmor.d/wike` with the following 
contents:
  ```
  # This profile allows everything and only exists to give the
  # application a name instead of having the label "unconfined"

  abi ,
  include 

  profile wike /usr/bin/wike flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }
  ```
  Then run `sudo systemctl restart apparmor.service`


  This is also reported in GitHub for Wike
  https://github.com/hugolabe/Wike/issues/181

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


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


[Touch-packages] [Bug 2060767] Re: Foliate does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
Thank you for the fix, John. Wike is also affected
https://github.com/hugolabe/Wike/issues/181

Do you have to manually add exception for each app? That would be very
hard to implement, because someone might create a new app and it would
not work on Ubuntu.

** Bug watch added: github.com/hugolabe/Wike/issues #181
   https://github.com/hugolabe/Wike/issues/181

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

Title:
  Foliate does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  When I try to open any epub via Foliate (installed from official Ubuntu 
repositories), it does not run.
  ```
  $ foliate Alcott, Louisa May - Little Women.epub

  (com.github.johnfactotum.Foliate:2289): Gtk-WARNING **: 01:51:13.769: Unknown 
key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (com.github.johnfactotum.Foliate:2289): ERROR **: 01:51:14.283: Failed to 
fully launch dbus-proxy: Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround
  (https://github.com/johnfactotum/foliate/issues/1271#issuecomment-2016575770)
  is to create the `/etc/apparmor.d/foliate` file with the appropriate
  content described in that link.

  A similar bug was reported for VSCode
  (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)

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


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


[Touch-packages] [Bug 2060809] [NEW] davinci not opening bro

2024-04-10 Thread Mani P
Public bug reported:

gpu no to supporter

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 18:14:28 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
InstallationDate: Installed on 2024-04-08 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
MachineType: ZEBRONICS H110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2023
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: H110
dmi.board.vendor: ZEBRONICS
dmi.board.version: Ver:2.32
dmi.chassis.type: 3
dmi.chassis.vendor: ZEBRONICS
dmi.chassis.version: H110
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku:
dmi.product.name: H110
dmi.sys.vendor: ZEBRONICS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
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 wayland-session

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

Title:
  davinci not opening bro

Status in xorg package in Ubuntu:
  New

Bug description:
  gpu no to supporter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:14:28 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
  InstallationDate: Installed on 2024-04-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: ZEBRONICS H110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.name: H110
  dmi.board.vendor: ZEBRONICS
  dmi.board.version: Ver:2.32
  dmi.chassis.type: 3
  dmi.chassis.vendor: ZEBRONICS
  dmi.chassis.version: H110
  dmi.modalias: 

[Touch-packages] [Bug 2060806] [NEW] Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
Public bug reported:

Yesterday, there was a new bugfix release in the stable 1.24.2 series.
This bug is to track updates for Ubuntu 24.04 LTS.

https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: noble upgrade-software-version

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Triaged

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

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


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


[Touch-packages] [Bug 2060009] Re: mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

2024-04-10 Thread Heinrich Schuchardt
** Description changed:

  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072
  
- According to OpenSCAD maintainers this was a bug in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
- --- 
+ According to OpenSCAD maintainers this was a bug fixed in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
+ ---
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroRelease: Ubuntu 24.04
  DistroVariant: ubuntu
  DkmsStatus:
-  fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
-  fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  DpkgLog:
-  
+ 
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
+  Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2021-07-01 (1006 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
-  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
+  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20KV0008GE
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Tags: noble ubuntu regression reproducible
  Uname: Linux 6.8.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sispmctl sudo
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET83W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KV0008GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.63
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KV0008GE
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  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

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

Title:
  mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072

  According to 

[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

2024-04-10 Thread Aleksandr Mikhalitsyn
Thanks, Julian!

Once this version pass all tests and reach archives I'll prepare PRs for
https://salsa.debian.org/lxc-team/lxc to be in sync with Debian.

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to skip this tests
  too for now.

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


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

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-04-10 Thread Daniel van Vugt
I've installed the 20240410 iso on a couple of machines and this bug is
as good as fixed.

The systemd task would be nice to complete but that's more for the sake
of bug 1914409. Right now I have more important bugs to focus on...

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

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

2024-04-10 Thread Julian Andres Klode
Sponsored, thanks

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

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to skip this tests
  too for now.

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


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


[Touch-packages] [Bug 2060790] [NEW] package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

2024-04-10 Thread Braulio Rosero
Public bug reported:

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

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: udev 249.11-0ubuntu3.12
ProcVersionSignature: Ubuntu 5.4.0-176.196-generic 5.4.268
Uname: Linux 5.4.0-176-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CustomUdevRuleFiles: 70-snap.core.rules
Date: Wed Apr 10 11:52:12 2024
ErrorMessage: subproces van pakket udev werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
InstallationDate: Installed on 2018-01-04 (2287 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
MachineType: HP ProLiant DL360 Gen9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-176-generic 
root=UUID=09a43454-d2be-4fe1-8774-96cebabcf8ef ro
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.3
 apt  2.4.12
SourcePackage: systemd
Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van 
pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 
terug
UpgradeStatus: Upgraded to jammy on 2024-04-10 (0 days ago)
dmi.bios.date: 04/25/2017
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL360 Gen9
dmi.product.sku: 843374-425
dmi.sys.vendor: HP

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060790

Title:
  package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces
  van pakket udev werd script post-installation geïnstalleerd gaf de
  foutwaarde 1 terug

Status in systemd package in Ubuntu:
  New

Bug description:
  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.12
  ProcVersionSignature: Ubuntu 5.4.0-176.196-generic 5.4.268
  Uname: Linux 5.4.0-176-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Wed Apr 10 11:52:12 2024
  ErrorMessage: subproces van pakket udev werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
  InstallationDate: Installed on 2018-01-04 (2287 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP ProLiant DL360 Gen9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-176-generic 
root=UUID=09a43454-d2be-4fe1-8774-96cebabcf8ef ro
  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.3
   apt  2.4.12
  SourcePackage: systemd
  Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces 
van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 
terug
  UpgradeStatus: Upgraded to jammy on 2024-04-10 (0 days ago)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 843374-425
  dmi.sys.vendor: HP

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


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


[Touch-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi

2024-04-10 Thread Daniel van Vugt
** Changed in: webkit2gtk (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Screen corruption of slides during install on Raspberry Pi

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

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


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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

2024-04-10 Thread Aleksandr Mikhalitsyn
It's worth mentioning that this debdiff includes not only tests
disabling but also fix that allows to build source package on Ubuntu.

If you do:

pull-lp-source liblxc-dev noble-proposed
cd lxc-5.0.3
debuild -S -d

you will see something like this:

 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building lxc using existing ./lxc_5.0.3.orig.tar.gz
dpkg-source: info: building lxc using existing ./lxc_5.0.3.orig.tar.gz.asc
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: local changes detected, the modified files are:
 lxc-5.0.3/config/apparmor/abstractions/start-container.in
 lxc-5.0.3/config/apparmor/usr.bin.lxc-copy
 lxc-5.0.3/config/apparmor/usr.bin.lxc-start
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/lxc_5.0.3-2ubuntu3.diff.21HvOc
dpkg-source: info: Hint: make sure the version in debian/changelog matches the 
unpacked source tree
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -S -d failed

It's because of the way how we apply custom Ubuntu patches.

This debian diff file contains fix for this too.

** Summary changed:

- autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)
+ autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)

Status in lxc package in Ubuntu:
  New

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = 

[Touch-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble

2024-04-10 Thread Sebastien Bacher
** Also affects: mesa (Ubuntu Noble)
   Importance: High
 Assignee: Timo Aaltonen (tjaalton)
   Status: In Progress

** Tags removed: rls-nn-incoming

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

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Noble:
  In Progress

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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


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


[Touch-packages] [Bug 2060009] Re: mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

2024-04-10 Thread Timo Aaltonen
you probably meant "fixed in mesa 24.0.4"?

Anyway, we'll get that in the next merge after beta.

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

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

Title:
  mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072

  According to OpenSCAD maintainers this was a bug in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroRelease: Ubuntu 24.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2021-07-01 (1006 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20KV0008GE
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Tags: noble ubuntu regression reproducible
  Uname: Linux 6.8.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sispmctl sudo
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET83W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KV0008GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.63
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KV0008GE
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  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

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


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


[Touch-packages] [Bug 2060767] Re: Foliate does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread John Johansen
The fix has been merged upstream in
https://gitlab.com/apparmor/apparmor/-/merge_requests/1209

it will be in the next release.


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

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  Foliate does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  When I try to open any epub via Foliate (installed from official Ubuntu 
repositories), it does not run.
  ```
  $ foliate Alcott, Louisa May - Little Women.epub

  (com.github.johnfactotum.Foliate:2289): Gtk-WARNING **: 01:51:13.769: Unknown 
key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (com.github.johnfactotum.Foliate:2289): ERROR **: 01:51:14.283: Failed to 
fully launch dbus-proxy: Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround
  (https://github.com/johnfactotum/foliate/issues/1271#issuecomment-2016575770)
  is to create the `/etc/apparmor.d/foliate` file with the appropriate
  content described in that link.

  A similar bug was reported for VSCode
  (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)

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


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


[Touch-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble

2024-04-10 Thread Sebastien Bacher
It seems to be a mesa issue which should get fixed with the incoming
point release

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

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

** Package changed: gtk4 (Ubuntu) => mesa (Ubuntu)

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

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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


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


[Touch-packages] [Bug 2060679] [NEW] No icons for gtk4 applications under noble

2024-04-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I
noticed that all GTK4 applications appear to be missing various icons.
All lack the minimize / maximize / close icons (which are left as three
empty circles on the window), and others lack icons within the windows,
e.g. on various controls like radio buttons, or folder icons in
nautilus. GTK3 applications appear unaffected. I'll attach some
screenshots demonstrating the issue.

** Affects: mesa (Ubuntu)
 Importance: High
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress


** Tags: iso-testing rls-nn-incoming
-- 
No icons for gtk4 applications under noble
https://bugs.launchpad.net/bugs/2060679
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

2024-04-10 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff.diff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

Status in lxc package in Ubuntu:
  New

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to 

[Touch-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git

2024-04-10 Thread Andreas Karlson
Till,
Thanks for the quick reply!

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

Title:
  cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported
  commits from 2.4.x git

Status in cups package in Ubuntu:
  In Progress

Bug description:
  While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 
2.4.7-1.2ubuntu5),
  I noticed that cupsd crashes consistently after closing my Firefox tab / 
window.
  The title of the crash (from the bug-report window) is "cupsd crashed with 
SIGSEGV in ???()"

  I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying
  some updates from the noble and noble-proposed pockets.

  Reproduction steps:
  1. Open Firefox and manage CUPS on http://localhost:631
  2. Go to Administration -> Printers -> Add Printer and choose your printer
  3. Add your printer (I used the ipps:// protocol to manage the printer)
  4. After clicking the "Add printer" button, immediately close your Firefox tab
  5. cupsd will crash and Ubuntu will display a bug-report popup

  Versions:
  Firefox - 124.0.1-1 r4033
  CUPS - 2.4.7-1.2ubuntu5

  Printer:
  Lexmark MS415dn (supported)

  I am unable to reproduce this bug on versions prior to
  2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2).

  Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from 
the 2.4.x upstream git branch, so I also opened an issue on GitHub:
  https://github.com/OpenPrinting/cups/issues/934

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


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


[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

2024-04-10 Thread Aleksandr Mikhalitsyn
** Patch added: "debdiff.diff"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2059550/+attachment/5763115/+files/debdiff.diff

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

Status in lxc package in Ubuntu:
  New

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: ---]
  3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - 
- - - - - - - -
  3269s no-devel PASS
  3269s autopkgtest [20:29:48]:  summary
  3269s exercise FAIL non-zero exit status 1
  3269s unprivileged-containers FAIL non-zero exit status 1
  3269s basics-create-destroy PASS (superficial)
  3269s no-devel PASS
  =

  
  unprivileged-containers
  =
  1896s Unpacking the rootfs
  1900s 
  1900s ---
  1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
  1900s 
  1900s To enable SSH, run: apt install openssh-server
  1900s No default root or user password are set by LXC.
  1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start 
-n mycontainer
  1900s Failed to connect to bus: No medium found

  =

  exercise
  =
  1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
  1113s ---
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52927
  1113s Link:   veth1001_HZ75
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s Name:   c1
  1113s State:  RUNNING
  1113s PID:52994
  1113s Link:   veth1001_ujGT
  1113s  TX bytes:  0 bytes
  1113s  RX bytes:  0 bytes
  1113s  Total bytes:   0 bytes
  1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
  <...>
  1113s info: Removing crontab ...
  1113s info: Removing user `lxcunpriv' ...
  1113s FAIL
  1113s ---
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
  1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
  1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
  1114s 
  1114s SUMMARY: pass=55, fail=1, ignored=0
  1115s autopkgtest [19:53:54]: test exercise: ---]
  1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - 
- - - - - - - -
  1115s exercise FAIL non-zero exit status 1
  =

  
  In the previous version we had no unprivileged-containers testsuite because 
it was inherited from Debian.

  lxc-test-unpriv was a skipped test too because we had this piece of code:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
  =
  # Skip some tests due to cgroup v2 incompatibility
  if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

  [ "$testbin" = "lxc-test-apparmor-mount" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-autostart" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-no-new-privs" ] && \
  ignore "$STRING" && continue

  [ "$testbin" = "lxc-test-unpriv" ] && \
  ignore "$STRING" && continue

  fi
  =

  Just compare:
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
  and
  
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

  We want to fix all of this for sure, but it would be awesome to get an
  updated and actual version of LXC in the upcoming Ubuntu Noble release
  too. So, may be it makes sense to skip this tests for the sake of
  having LXC updated.

  What I found in Debian, is that autopkgtests are skipped too:
  https://ci.debian.net/packages/l/lxc/unstable/amd64/

  Taking this into account it (probably) reasonable to skip this tests
  too for now.

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


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


[Touch-packages] [Bug 2060767] [NEW] Foliate does not run in Ubuntu 24.04 due to apparmor issue

2024-04-10 Thread Archisman Panigrahi
Public bug reported:

When I try to open any epub via Foliate (installed from official Ubuntu 
repositories), it does not run.
```
$ foliate Alcott, Louisa May - Little Women.epub

(com.github.johnfactotum.Foliate:2289): Gtk-WARNING **: 01:51:13.769: Unknown 
key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
bwrap: setting up uid map: Permission denied

** (com.github.johnfactotum.Foliate:2289): ERROR **: 01:51:14.283: Failed to 
fully launch dbus-proxy: Child process exited with code 1
Trace/breakpoint trap
```

A workaround
(https://github.com/johnfactotum/foliate/issues/1271#issuecomment-2016575770)
is to create the `/etc/apparmor.d/foliate` file with the appropriate
content described in that link.

A similar bug was reported for VSCode
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)

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


** Tags: noble

** Description changed:

  When I try to open any epub via Foliate (installed from official Ubuntu 
repositories), it does not run.
  ```
- foliate Alcott, Louisa May - Little Women.epub
+ $ foliate Alcott, Louisa May - Little Women.epub
  
  (com.github.johnfactotum.Foliate:2289): Gtk-WARNING **: 01:51:13.769: Unknown 
key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied
  
  ** (com.github.johnfactotum.Foliate:2289): ERROR **: 01:51:14.283: Failed to 
fully launch dbus-proxy: Child process exited with code 1
  Trace/breakpoint trap
  ```
  
  A workaround
  (https://github.com/johnfactotum/foliate/issues/1271#issuecomment-2016575770)
  is to create the `/etc/apparmor.d/foliate` file with the appropriate
  content described in that link.
  
- 
- A similar bug was reported for VSCode 
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)
+ A similar bug was reported for VSCode
+ (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)

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

Title:
  Foliate does not run in Ubuntu 24.04 due to apparmor issue

Status in apparmor package in Ubuntu:
  New

Bug description:
  When I try to open any epub via Foliate (installed from official Ubuntu 
repositories), it does not run.
  ```
  $ foliate Alcott, Louisa May - Little Women.epub

  (com.github.johnfactotum.Foliate:2289): Gtk-WARNING **: 01:51:13.769: Unknown 
key gtk-modules in /home/archisman/.config/gtk-4.0/settings.ini
  bwrap: setting up uid map: Permission denied

  ** (com.github.johnfactotum.Foliate:2289): ERROR **: 01:51:14.283: Failed to 
fully launch dbus-proxy: Child process exited with code 1
  Trace/breakpoint trap
  ```

  A workaround
  (https://github.com/johnfactotum/foliate/issues/1271#issuecomment-2016575770)
  is to create the `/etc/apparmor.d/foliate` file with the appropriate
  content described in that link.

  A similar bug was reported for VSCode
  (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517)

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


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


[Touch-packages] [Bug 1958019]

2024-04-10 Thread thornley.david
FYI, broken again in 6.8.4, 6.8.3 (not sure about 6.8.2).

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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