[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set

[Michał Małoszewski]

** Description changed:

  [Impact]
  
  * User of openssh reported an issue that affects Lunar and Jammy.
  
  * This crash is caused by the wrong pointer manipulation in the if
  statement. The fix is to change the code to check if the value pointed
  to by the pointer 'charptr' is NULL.
  
  [Test Plan]
  
- TBD
+ Launch container: 
+ $ lxc launch ubuntu:jammy 
+ 
+ Shell into that container:
+ $ lxc shell 
+ 
+ Create the main directory for our task (e.g. “reproducer”)
+ # mkdir reproducer
+ 
+ Go to that directory using ‘cd’ command and from there create 2 more dirs 
that reflect users:
+ # mkdir certuser keyonlyuser
+ 
+ Go to the keyonlyuser and inside:
+ # ssh-keygen -t ed25519 -f key
+ 
+ Go to the certuser and inside:
+ # ssh-keygen -t rsa -f ca
+ # ssh-keygen -t ed25519 -f key
+ # ssh-keygen -s ca -I key_id -n certuser key.pub
+ 
+ Create a script‘/root/reproducer/authorized_principals’ with permissions 755 
as follows:
+ #!/bin/sh 
+ if [ "$1" = "otheruser" ]; then 
+ echo certuser
+ fi
+  
+ Exit from the file and set the permission bits: 
+ # chmod 755 authorized_principals
+ 
+ Stay in the same directory and create a user called otheruser:
+ # adduser --disabled-password otheruser
+ (Enter multiple times, leave all fields blank)
+ 
+ Then do the same for another user:
+ # adduser --disabled-password keyonlyuser
+ 
+ Go back to the reproducer/ directory and create a new script called 
authorized_keys:
+ # nano authorized_keys
+ 
+ Add inside:
+ #!/bin/sh 
+ if [ "$1" = "keyonlyuser" ]; then 
+ echo 
+ fi
+ 
+ Exit from the file and set permission bits: 
+ # chmod 755 authorized_keys
+ 
+ Go to the etc/ssh/sshd_config
+ Add at the top:
+ 
+ AuthorizedKeysCommand /root/reproducer/authorized_keys %u
+ AuthorizedKeysCommandUser root 
+ 
+ AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u 
AuthorizedPrincipalsCommandUser root
+ TrustedUserCAKeys /root/reproducer/certuser/ca.pub
+ 
+ Exit from the file and restart the ssh service:
+ systemctl restart ssh
+ 
+ Use these commands to manifest the bug:
+ 
+ # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key
+ 
+ # ssh otheruser@localhost -i /root/reproducer/certuser/key -o
+ CertificateFile=/root/reproducer/certuser/key-cert.pub
+ 
+ Expected results: both ssh commands should succeed.
+ 
+ Actual results:  the second ssh is fails because the
+ AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set.
  
  [Where problems could occur]
  
  * The patch itself modifies only the servconf.c, so regressions should
  be limited to the server configuration.
  
  * Since the fix touches pointers, there might be regression related to
  memory handling and fetching data.
  
  -original
  report--
  
- 
  Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code:
  
  if (*activep && options->authorized_keys_command == NULL)
  *charptr = xstrdup(str + len);
  
  However, this is executed for both authorized_keys_command and
  authorized_principals_command. As a result, if authorized_keys_command
  is set (for instance, if using ec2-instance-connect), any
  AuthorizedPrincipalsCommand configuration in sshd_config is ignored.
  This is fixed in 9.4p1 with the attached patch.

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

Title:
  AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  In Progress
Status in openssh source package in Lunar:
  In Progress
Status in openssh source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * User of openssh reported an issue that affects Lunar and Jammy.

  * This crash is caused by the wrong pointer manipulation in the if
  statement. The fix is to change the code to check if the value pointed
  to by the pointer 'charptr' is NULL.

  [Test Plan]

  Launch container: 
  $ lxc launch ubuntu:jammy 

  Shell into that container:
  $ lxc shell 

  Create the main directory for our task (e.g. “reproducer”)
  # mkdir reproducer

  Go to that directory using ‘cd’ command and from there create 2 more dirs 
that reflect users:
  # mkdir certuser keyonlyuser

  Go to the keyonlyuser and inside:
  # ssh-keygen -t ed25519 -f key

  Go to the certuser and inside:
  # ssh-keygen -t rsa -f ca
  # ssh-keygen -t ed25519 -f key
  # ssh-keygen -s ca -I key_id -n certuser key.pub

  Create a script‘/root/reproducer/authorized_principals’ with permissions 755 
as follows:
  #!/bin/sh 
  if [ "$1" = "otheruser" ]; then 
  echo certuser
  fi
   
  Exit from the file and set the permission bits: 
  # chmod 755 authorized_principals

  Stay in the same directory and create a user called otheruser:
  # adduser --disabled-password otheruser
  

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Bug Watch Updater]

** Changed in: apparmor (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 2028935] Re: Merge rsyslog 8.2306.0-2

[Heinrich Schuchardt]

Autopkgtest on armhf shows these unmatched lines in the logcheck test.
They do not appear on other architectures.

291s =-=-=-=-=-=-=
291s 2023-08-31T21:15:17.643352+00:00 autopkgtest-lxd-xjetox rsyslogd[1792]: 
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Permission denied.
291s 2023-08-31T21:15:17.643426+00:00 autopkgtest-lxd-xjetox rsyslogd[1792]: 
rsyslogd: activation of module imklog failed [v8.2306.0 try 
https://www.rsyslog.com/e/2145 ]
291s 2023-08-31T21:15:17.644738+00:00 autopkgtest-lxd-xjetox rsyslogd: imklog: 
cannot open kernel log (/proc/kmsg): Permission denied.
291s 2023-08-31T21:15:17.644899+00:00 autopkgtest-lxd-xjetox rsyslogd: 
activation of module imklog failed [v8.2306.0 try 
https://www.rsyslog.com/e/2145 ]
291s Aug 31 21:15:17 autopkgtest-lxd-xjetox rsyslogd[1792]: rsyslogd: imklog: 
cannot open kernel log (/proc/kmsg): Permission denied.
291s Aug 31 21:15:17 autopkgtest-lxd-xjetox rsyslogd[1792]: rsyslogd: 
activation of module imklog failed [v8.2306.0 try 
https://www.rsyslog.com/e/2145 ]
291s Aug 31 21:15:17 autopkgtest-lxd-xjetox rsyslogd[1792]: imklog: cannot open 
kernel log (/proc/kmsg): Permission denied.
291s Aug 31 21:15:17 autopkgtest-lxd-xjetox rsyslogd[1792]: activation of 
module imklog failed [v8.2306.0 try https://www.rsyslog.com/e/2145 ]

The permissions are specific to the setup of the test container. We
should add the messages to the list of expected messages
(debian/rsyslog.logcheck.ignore.server).

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

Title:
  Merge rsyslog 8.2306.0-2

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  Debian has upgraded rsyslog to 8.2306.0-2.

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


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

[Touch-packages] [Bug 2033670] Re: [Lenovo ThinkPad X13 Gen 3] Screen is flickering since last kernel upgrade

[Daniel van Vugt]

Thanks for the bug report. Your graphics packages appear to be from the
unsupported 'kisak' PPA. Please remove that PPA from your system, reboot
and then report new bugs for any issues you find.


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

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

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

Title:
  [Lenovo ThinkPad X13 Gen 3] Screen is flickering since last kernel
  upgrade

Status in Ubuntu:
  Invalid

Bug description:
  Please let me know how can I provide you valuable information to investigate 
the issue.
  When I work on the PC I get periodic (not constant) flickering on the screen 
(lateral from left to right).
  It seems a software issue because I didn´t find any relevant information in 
dmesg or similar log files.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:04:59 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi/1.12.0, 5.19.0-50-generic, x86_64: installed
   evdi/1.14.1, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] 
(rev d1) (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-11-29 (274 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_inu33p@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_inu33p ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R22ET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrR22ET55W(1.25):bd09/14/2022:br1.25:efr1.21:svnLENOVO:pn21CMCTO1WW:pvrThinkPadX13Gen3:rvnLENOVO:rn21CMCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CM_BU_Think_FM_ThinkPadX13Gen3:
  dmi.product.family: ThinkPad X13 Gen 3
  dmi.product.name: 21CMCTO1WW
  dmi.product.sku: LENOVO_MT_21CM_BU_Think_FM_ThinkPad X13 Gen 3
  dmi.product.version: ThinkPad X13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.1.6~kisak1~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.6~kisak1~j
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/2033670/+subscriptions


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

[Touch-packages] [Bug 2033670] Re: [Lenovo ThinkPad X13 Gen 3] Screen is flickering since last kernel upgrade

[Daniel van Vugt]

** Summary changed:

- Screen is flickering since last kernel upgrade
+ [Lenovo ThinkPad X13 Gen 3] Screen is flickering since last kernel upgrade

** Tags added: amdgpu

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

Title:
  [Lenovo ThinkPad X13 Gen 3] Screen is flickering since last kernel
  upgrade

Status in Ubuntu:
  Invalid

Bug description:
  Please let me know how can I provide you valuable information to investigate 
the issue.
  When I work on the PC I get periodic (not constant) flickering on the screen 
(lateral from left to right).
  It seems a software issue because I didn´t find any relevant information in 
dmesg or similar log files.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:04:59 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi/1.12.0, 5.19.0-50-generic, x86_64: installed
   evdi/1.14.1, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] 
(rev d1) (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-11-29 (274 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_inu33p@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_inu33p ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R22ET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrR22ET55W(1.25):bd09/14/2022:br1.25:efr1.21:svnLENOVO:pn21CMCTO1WW:pvrThinkPadX13Gen3:rvnLENOVO:rn21CMCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CM_BU_Think_FM_ThinkPadX13Gen3:
  dmi.product.family: ThinkPad X13 Gen 3
  dmi.product.name: 21CMCTO1WW
  dmi.product.sku: LENOVO_MT_21CM_BU_Think_FM_ThinkPad X13 Gen 3
  dmi.product.version: ThinkPad X13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.1.6~kisak1~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.6~kisak1~j
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/2033670/+subscriptions


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

[Touch-packages] [Bug 1906729] Re: Suspend and hibernate work, but hybrid-suspend does not

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Suspend and hibernate work, but hybrid-suspend does not

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I have a Lenovo e585, if it's relevant.

  I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`.
  EDIT: This is now 22.04 and `249 (249.11-0ubuntu3.9)`

  Suspend on my system doesn't wake up consistently, but hibernate does.

  Hybrid suspend would make an excellent fallback if wake fails.

  Since both work independently, they *should* work together.

  Happy to help debug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 16:58:44 2020
  InstallationDate: Installed on 2020-05-06 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic 
root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ 
resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/usr/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET74W (1.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET74W(1.54):bd07/23/2019:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.sleep.conf: 2020-12-03T16:22:33.696671

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


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

[Touch-packages] [Bug 2033647] Re: When monitor set to 60Hz, "join screens" enabled

[Daniel van Vugt]

The problem with the laptop screen getting turned on at resume-from-
suspend is already tracked in bug 2018158. So let's make this bug just
about the 30Hz problem.

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

** Tags added: multimonitor

** Tags added: resume suspend-resume

** Summary changed:

- When monitor set to 60Hz, "join screens" enabled
+ External monitor lowered to 30Hz when resuming from suspend

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

Title:
  External monitor lowered to 30Hz when resuming from suspend

Status in Ubuntu:
  Incomplete

Bug description:
  Hello there,

  I have Ubuntu 23.04 installed on a Dell XPS 13 9300 with an LG 32" 4K
  Ergo Monitor attached as an external display. When I set the "primary
  display" at 1080p@60Hz for the LG 32" only with the "secondary
  display" of the Dell XPS 13" disabled" and "suspend power" of the Dell
  XPS 13, both the "primary display" of the LG 32" and the "secondary
  display" of the Dell XPS 13 are both "enabled" when resuming from
  "power suspend". Also, the frequency of the "primary display" of the
  LG 32" is lowered to 30Hz.

  If the Ubuntu 23.04 software development team in charge of the X.org
  display could rectify the issue regarding the stability of my "primary
  display" at 1080p@60Hz during "power suspend" and "power on", that
  would be great.

  
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 05:03:37 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2023-05-07 (116 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=35826320-1bf8-43d1-831e-3b6e6d6a73e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2023
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0Y4GNJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd07/11/2023:br1.19:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr:sku096D:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1887507] Re: Please remove old libgtk2-perl from Recommends and drop dependency against gnome-icon-theme

[Bug Watch Updater]

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

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

Title:
  Please remove old libgtk2-perl from Recommends and drop dependency
  against gnome-icon-theme

Status in gdebi package in Ubuntu:
  Confirmed
Status in gdebi package in Debian:
  Fix Released

Bug description:
  Could you please remove old libgtk2-perl from Recommends and drop the
  dependency against gnome-icon-theme?

  libgtk2-perl and gnome-icon-theme is deprecated for gtk3 and replaced by 
adwaita-icon-theme.  
  If I'm not wrong, gdebi only uses one icon from gnome-icon-theme, 
gnome-mime-application-x-deb, this icon is not available in adwaita-icon-theme. 
BUT, can be replaced by the package-x-generic (which is also available in other 
icon themes). On my machine this is the same icon as for the .deb and .udeb 
files. An explicit dependency against adwaita-icon-theme should probably be 
avoided as libgtk3 will already pull it.

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


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

Re: [Touch-packages] [Bug 1971650] Re: wrong check for "server" in libssl3.postinst

[Seth Arnold]

On Tue, Aug 29, 2023 at 03:06:58PM -, Adrien Nader wrote:
> Shall we assume on both desktops and servers that an openssl update
> always requires a reboot? At least until we do anything related to
> needrestart.

Our needrestart work is already live, those big obnoxious modal dialogs
are something I don't quickly forget. :)

I think we can delete all the maintainer-script upgrade notices from
jammy onwards, and I wouldn't cry to see it go from earlier releases,
either.

Thanks

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

Title:
  wrong check for "server" in libssl3.postinst

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  A security update has just been applied to my system for openssl, and
  the 'reboot required' message just popped on my desktop.  I looked to
  see why this was, and found the following code in the libssl3
  postinst:

  # Here we issue the reboot notification for upgrades and
  # security updates. We do want services to be restarted when we
  # update for a security issue, but planned by the sysadmin, not
  # automatically.

  # Only issue the reboot notification for servers; we proxy this by
  # testing that the X server is not running (LP: #244250)
  if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x 
/usr/share/update-notifier/notify-reboot-required ]; then
  /usr/share/update-notifier/notify-reboot-required
  fi

  Now, AFAIK this is the only package that interfaces with notify-
  reboot-required but omits the notification on desktops, so that seems
  to be an inconsistent policy; but even if we thought that was the
  correct policy to apply, the above check for a desktop is not because
  it doesn't match in the case the user is running Xwayland, which most
  users not using the nvidia driver will be doing now by default.

  Also, this is now inside a block that checks for the presence of
  needrestart, which is part of the server seed; so in effect this
  notification now *never* fires on servers, it *only* fires on
  desktops.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  5 05:39:06 2022
  InstallationDate: Installed on 2019-12-23 (863 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: openssl
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago)

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


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

[Touch-packages] [Bug 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"

[Bug Watch Updater]

** Changed in: tzdata (Debian)
   Status: Unknown => Fix Released

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

Title:
  tzname[1] empty after tzset() with env TZ="UTC"

Status in django-mailman3 package in Ubuntu:
  New
Status in php8.2 package in Ubuntu:
  Triaged
Status in postgresql-15 package in Ubuntu:
  Fix Committed
Status in python-django package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata package in Debian:
  Fix Released

Bug description:
  The following program prints different output when run with tzdata
  2023c-7ubuntu1 from mantic, versus tzdata 2023c-8ubuntu1 from mantic-
  proposed:

  root@mantic:~# cat bug.c 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
  int r;

  r = setenv("TZ", ":UTC", 1);
  if (r < 0) {
  printf("Failed to set TZ env var: %s\n", strerror(errno));
  return 1;
  }

  tzset();

  printf("timezone = %lu, daylight = %d\n", timezone, daylight);
  printf("tzname[0] = %s, tzname[1] = %s\n", tzname[0], tzname[1]);
  }

  root@mantic:~# gcc bug.c
  root@mantic:~# ./a.out 
  timezone = 0, daylight = 0
  tzname[0] = UTC, tzname[1] = UTC
  root@mantic:~# apt-cache policy tzdata
  tzdata:
Installed: 2023c-7ubuntu1
Candidate: 2023c-7ubuntu1
Version table:
   *** 2023c-7ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  If I install tzdata from mantic-proposed, I get different output:

  root@mantic:~# vi /etc/apt/sources.list
  root@mantic:~# apt update && apt install tzdata
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease
  Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [118 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 
[35.9 kB]
  Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en 
[14.8 kB]
  Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11 
Metadata [2376 B]
  Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f 
Metadata [1004 B]
  Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
Packages [15.9 kB]
  Get:11 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted 
Translation-en [3564 B]
  Get:12 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
c-n-f Metadata [336 B]
  Fetched 192 kB in 1s (324 kB/s) 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  72 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@mantic:~# apt install tzdata=2023c-8ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libefiboot1 libefivar1
  Use 'apt autoremove' to remove them.
  The following packages will be upgraded:
tzdata
  1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
  Need to get 269 kB of archives.
  After this operation, 142 kB disk space will be freed.
  Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 tzdata all 
2023c-8ubuntu1 [269 kB]
  Fetched 269 kB in 0s (867 kB/s)
  Preconfiguring packages ...
  (Reading database ... 39935 files and directories currently installed.)
  Preparing to unpack .../tzdata_2023c-8ubuntu1_all.deb ...
  Unpacking tzdata (2023c-8ubuntu1) over (2023c-7ubuntu1) ...
  Setting up tzdata (2023c-8ubuntu1) ...

  Current default time zone: 'Etc/UTC'
  Local time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Universal Time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Run 'dpkg-reconfigure tzdata' if you wish to change it.

  Scanning processes... 


 
  Scanning candidates...


 

  Restarting services...
  Service restarts being deferred:
   systemctl restart systemd-logind.service
   systemctl restart unattended-upgrades.service

  No containers need to be restarted.

  No user sessions are running outdated binaries.

  No VM guests are running outdated 

[Touch-packages] [Bug 2009544] Re: OpenSSL 3 performance regression

[Rafael Lopez]

Tested some additional patches, including [1] (PR linked in bug desc)
plus [2] and [3]. PPAs for each at [4], [5] and [6]. All tests on same
hardware and VM 8vcpu/4G.

Baseline:
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 13.62  User: 24.44
Real: 13.84  User: 22.89
Real: 14.12  User: 23.71
Real: 13.72  User: 23.94
Real: 13.42  User: 24.31
ubuntu@openssl-jammy:~/openssl_python_ubuntu$

PR#18151[1]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 3.20  User: 13.89
Real: 2.43  User: 15.29
Real: 2.72  User: 14.88
Real: 2.77  User: 14.56
Real: 2.43  User: 15.46
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17881[2]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 2.02  User: 7.92
Real: 1.93  User: 7.87
Real: 1.89  User: 7.88
Real: 2.09  User: 8.46
Real: 1.89  User: 7.80
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17921[3]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 1.64  User: 5.30
Real: 1.74  User: 6.08
Real: 1.74  User: 5.80
Real: 1.69  User: 6.50
Real: 1.70  User: 5.68
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17881[2] + PR#17921[3]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 1.55  User: 3.79
Real: 1.64  User: 3.78
Real: 1.86  User: 4.36
Real: 1.73  User: 3.81
Real: 1.81  User: 3.72
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


[1] https://github.com/openssl/openssl/pull/18151
[2] https://github.com/openssl/openssl/pull/17881
[3] https://github.com/openssl/openssl/pull/17921
[4] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544
[5] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544-2
[6] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544-3

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

Title:
  OpenSSL 3 performance regression

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Hello, it sounds like there's some significant performance regressions
  in OpenSSL 3:

  https://github.com/openssl/openssl/issues/20286#issuecomment-1438826816

  Some we might be able to address with:
  https://github.com/openssl/openssl/pull/18151

  Some of the performance differences may be subject to ongoing work.

  Thanks

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


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

[Touch-packages] [Bug 2029930] Re: wget crash when printing download rate

[Bug Watch Updater]

** Changed in: wget (Debian)
   Status: Unknown => New

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

Title:
  wget crash when printing download rate

Status in wget package in Ubuntu:
  Confirmed
Status in wget package in Debian:
  New

Bug description:
  
  All supported versions of Ubuntu suffer from crashes in wget in printing of 
the download speed. I've been getting this on various servers. It's been fixed 
upstream and should probably be included in 'updates' of all supported Ubuntu 
versions.

  https://git.savannah.gnu.org/git/wget.git
  Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5

  https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html

  Patch attached.

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


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

[Touch-packages] [Bug 2028810] Re: rsync 3.1.3 performance regression

[Andreas Hasenack]

I'm a bit reluctant to release this because the update is not
documenting the new option, and I can't find out why. The original MP[1]
review implies that documentation was present, both in -h output, and in
the manpage, but I don't see it in the package in proposed. This makes
it very hard for users to discover the jammy package would now have this
new option.

Do we know what happened here? Was it a conscious decision to not
include the doc changes? Or did something fell through the cracks
between review and upload to unapproved? Note the --help output comes
from a section of the manpage.


1. 
https://code.launchpad.net/~lvoytek/ubuntu/+source/rsync/+git/rsync/+merge/448637/comments/1197139

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

Title:
  rsync 3.1.3 performance regression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Recent necessary security fixes to rsync have caused a slow down in
  transfer speeds due to additional authentication. In more recent
  versions of rsync this can be mitigated when the environment is
  trusted with the --trust-sender flag.

  In order to accomidate this use case, the flag should be backported to
  focal too.

  [Test Plan]

  $ lxc launch ubuntu:focal test-rsync-receiver
  $ lxc exec test-rsync-receiver bash
  # apt update && apt dist-upgrade -y
  # apt install openssh-server rsync -y
  # passwd ubuntu
  - set password for user
  # exit

  - Check ip of receiver with lxc list
  $ lxc list

  $ lxc launch ubuntu:focal test-rsync-sender
  $ lxc exec test-rsync-sender bash
  # apt update && apt dist-upgrade -y

  # apt install rsync -y

  - Create a random file to send over
  # dd if=/dev/urandom of=randomfile.bin bs=1M count=1000

  - Send without --trust-sender
  # rsync -av randomfile.bin ubuntu@:~/file1.bin

  - Send with --trust-sender
  # rsync -av --trust-sender randomfile.bin ubuntu@:~/file2.bin

  With the fix in place, --trust-sender is a valid argument and the
  transfer is notably faster as reported back by rsync.

  [Where problems could occur]

  Since this change adds a new feature in the form of an input flag,
  problems could occour when using it. This could include issues from
  skipping security checks between the sending and receiving machine.
  Another possible problem would be issues with command line input
  parsing due to the additional valid argument.

  [Other Info]
   
  The --trust-sender option is already available in Jammy and later

  [Original Description]

  OS: Ubuntu 20.04 Focal
  Package: rsync 3.1.3-8ubuntu0.5

  rsync's performance was regressed by ~7x amount after some security
  patch (debian/patches/CVE-2022-29154-*) was applied to the package,
  and introduced a list of filters that iterate on every file being
  transferred. We think that was where the performance regression came
  from.

  A Jammy version of the package (3.2.5) introduced a new flag "--trust-
  sender" that allowed user to avoid the expensive client-side filtering
  introduced by those security patches. After pulling this change
  
(https://github.com/WayneD/rsync/commit/cff8f044776c5143a5b270969d4bb0f1fea8b017)
  from rsync ourselves and applied it to the Focal version, the
  performance regression went away.

  The patch we used to backport our Focal rsync is attached in this
  thread. Can you please backport it too?

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


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

[Touch-packages] [Bug 119913] Re: bash hangs infinitely; related to replace_history_data

[Muneeb Siddiqui]

In addition to the aforementioned offers, we extend coupon rewards to
those who join our Telegram channel. This feature underscores our
dedication to delivering value to our community members and ensuring
they feel appreciated. https://www.casino-hera.com/

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

Title:
  bash hangs infinitely; related to replace_history_data

Status in bash package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bash

  I had it happen several times on my server that bash hung, when
  exiting from e.g. a "less" statement, before displaying the prompt
  again.

  I've attached gdb then and it revealed the following backtrace. This
  was with bash from Feisty (3.2-0ubuntu7).

  # gdb -p 10345
  GNU gdb 6.6-debian
  Copyright (C) 2006 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you are
  welcome to change it and/or distribute copies of it under certain conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for details.
  This GDB was configured as "i486-linux-gnu".
  Attaching to process 10345
  Reading symbols from /bin/bash...Reading symbols from 
/usr/lib/debug/bin/bash...done.
  Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
  done.
  termsig_sighandler (sig=11) at ../bash/sig.c:429
  429 ../bash/sig.c: No such file or directory.
  in ../bash/sig.c
  (gdb) bt
  #0  termsig_sighandler (sig=11) at ../bash/sig.c:429
  #1  
  #2  0x080ced45 in replace_history_data (which=-1, old=0x0, new=0x0) at 
../../../bash/lib/readline/history.c:420
  #3  0x080ca3d5 in rl_free_undo_list () at 
../../../bash/lib/readline/undo.c:122
  #4  0x080c898b in rl_free_line_state () at 
../../../bash/lib/readline/signals.c:455
  #5  0x080c8fb9 in rl_signal_handler (sig=2) at 
../../../bash/lib/readline/signals.c:145
  #6  
  #7  _rl_dispatch_subseq (key=13, map=0x14, got_subseq=0) at 
../../../bash/lib/readline/readline.c:723
  #8  0x080ba105 in _rl_dispatch (key=13, map=0x14) at 
../../../bash/lib/readline/readline.c:687
  #9  0x080ba41c in readline_internal_char () at 
../../../bash/lib/readline/readline.c:519
  #10 0x080ba7a5 in readline (
  prompt=0x8296708 
"\001\033[1;31m\002root\001\033[1;31m\002@\001\033[0;32m\002h170368 
\001\001\033[0;31m\002[es:1] \002\001\0
  33[0;33m\002[scr:1] \001\033[1;31m\002{ 
\001\033[0;32m\002/etc/monit\001\033[1;31m\002 }\r\n#\001\033[0m\002 ") at 
../../../bash
  /lib/readline/readline.c:545
  #11 0x080683d1 in yy_readline_get () at ../bash/parse.y:1213
  #12 0x08064098 in shell_getc (remove_quoted_newline=1) at ../bash/parse.y:1942
  #13 0x0806538a in read_token (command=) at 
../bash/parse.y:2562
  #14 0x0806898d in yyparse () at ../bash/parse.y:2208
  #15 0x080ee0a4 in _DYNAMIC ()
  #16 0x080ee084 in _DYNAMIC ()
  #17 0x080ee06c in _DYNAMIC ()
  #18 0x in ?? ()
  (gdb)

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


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

[Touch-packages] [Bug 1834250] Autopkgtest regression report (lvm2/2.03.07-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted lvm2 (2.03.07-1ubuntu1.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/20.10.25-0ubuntu1~20.04.1 (amd64, ppc64el, s390x)


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

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

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

Thank you!

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

Title:
  update-grub complains about non-existent drives (due to cardreader)

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * `update-grub` (actually `vgs`) complains about
     'No medium found' on systems with card readers
     that have no card in.

   * This may confuse users who aren't sure whether
     it means problems occurred with the bootloader,
     and concern their ability to safely boot again.

   * The workaround is to add a filter to LVM config,
     but this might be hard to find and error prone.
     (And not even seem relate to `update-grub` at
     all, specially on non-LVM storage layouts.)
     [See comment #16]

   * The fix replaces calls to `dev_open_readonly()`
 with `dev_open_readonly_quiet()` in scan path,
 where such errors are not a problem.

  [Test Plan]

   * Run `vgs` on a system with a card reader
     and check for 'No medium found' messages.

   * Run `strace -f -e openat vgs` to confirm
     system calls/error codes have no changes.

   * [See comment #20]

  [Where problems could occur]

   * The patch changes syscall error reporting on the
     'scan' path, so problems could occur when listing
     LVM resources in block devices (e.g., list volume
     groups with `vgs`).

   * There's little to no changes upstream on this area,
     and the change is present in Jammy; both help with
     a lower chance of regression.

  [Other Info]

   * `block-proposed-focal`: The upload is being staged
     as it's just a cosmetic change, but affects `lvm2`,
     which is present in so many systems, triggering a
     lot of upgrades/boot risk (in case something else
     broke and this upgrade could reveal it indirectly).

   * So, it will probably only be released once a more
     serious issue has to be fixed in `lvm2`.

   * Scope: Jammy has the fix, and Impish will EOL soon.

  [Original Bug Description]

  sudo update-grub

  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No medium found
  Found linux image: /boot/vmlinuz-5.0.0-17-generic
  Found initrd image: /boot/initrd.img-5.0.0-17-generic
  Found linux image: /boot/vmlinuz-5.0.0-16-generic
  Found initrd image: /boot/initrd.img-5.0.0-16-generic
    /dev/sdc: open failed: No medium found
    /dev/sdd: open failed: No medium found
    /dev/sde: open failed: No medium found
    /dev/sdf: open failed: No 

[Touch-packages] [Bug 2033670] Re: Screen is flickering since last kernel upgrade

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Screen is flickering since last kernel upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  Please let me know how can I provide you valuable information to investigate 
the issue.
  When I work on the PC I get periodic (not constant) flickering on the screen 
(lateral from left to right).
  It seems a software issue because I didn´t find any relevant information in 
dmesg or similar log files.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:04:59 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi/1.12.0, 5.19.0-50-generic, x86_64: installed
   evdi/1.14.1, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] 
(rev d1) (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-11-29 (274 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_inu33p@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_inu33p ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R22ET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrR22ET55W(1.25):bd09/14/2022:br1.25:efr1.21:svnLENOVO:pn21CMCTO1WW:pvrThinkPadX13Gen3:rvnLENOVO:rn21CMCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CM_BU_Think_FM_ThinkPadX13Gen3:
  dmi.product.family: ThinkPad X13 Gen 3
  dmi.product.name: 21CMCTO1WW
  dmi.product.sku: LENOVO_MT_21CM_BU_Think_FM_ThinkPad X13 Gen 3
  dmi.product.version: ThinkPad X13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.1.6~kisak1~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.6~kisak1~j
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/+source/xorg/+bug/2033670/+subscriptions


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

[Touch-packages] [Bug 2033670] [NEW] Screen is flickering since last kernel upgrade

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please let me know how can I provide you valuable information to investigate 
the issue.
When I work on the PC I get periodic (not constant) flickering on the screen 
(lateral from left to right).
It seems a software issue because I didn´t find any relevant information in 
dmesg or similar log files.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 18:04:59 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.12.0, 5.19.0-50-generic, x86_64: installed
 evdi/1.14.1, 6.2.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev 
d1) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-11-29 (274 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 21CMCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_inu33p@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_inu33p ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET55W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CMCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: ThinkPad
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvrR22ET55W(1.25):bd09/14/2022:br1.25:efr1.21:svnLENOVO:pn21CMCTO1WW:pvrThinkPadX13Gen3:rvnLENOVO:rn21CMCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CM_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CMCTO1WW
dmi.product.sku: LENOVO_MT_21CM_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.1.6~kisak1~j
version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.6~kisak1~j
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 third-party-packages ubuntu
-- 
Screen is flickering since last kernel upgrade
https://bugs.launchpad.net/bugs/2033670
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 2033684] [NEW] [ZenBook UX434FAC_UX434FA, Realtek ALC294, Speaker, Internal] fails after a while

[cyprian sulwe]

Public bug reported:

Audio plays for about 5 seconds then some noise comes and the sound goes
off.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cyprian   11565 F pulseaudio
 /dev/snd/pcmC0D0p:   cyprian   11565 F...m pulseaudio
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 22:11:31 2023
InstallationDate: Installed on 2023-08-17 (14 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 
Symptom_Type: Sound works for a while, then breaks
Title: [ZenBook UX434FAC_UX434FA, Realtek ALC294, Speaker, Internal] fails 
after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2019
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434FAC.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434FAC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434FAC.303:bd12/18/2019:br5.15:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FAC_UX434FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434FAC_UX434FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  [ZenBook UX434FAC_UX434FA, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Audio plays for about 5 seconds then some noise comes and the sound
  goes off.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cyprian   11565 F pulseaudio
   /dev/snd/pcmC0D0p:   cyprian   11565 F...m pulseaudio
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 22:11:31 2023
  InstallationDate: Installed on 2023-08-17 (14 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX434FAC_UX434FA, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2019
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434FAC.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434FAC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434FAC.303:bd12/18/2019:br5.15:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FAC_UX434FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434FAC_UX434FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

[Thomas Sthlm]

@oibaf
Thanx,

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

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

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

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

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

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

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

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

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

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2033678] [NEW] Unmodified files should not be rewritten

[Marcel Partap]

Public bug reported:

Right now, all sources list files will be rewritten regardless, even if
they have not changed. This loses their original last-modified
timestamp, obscuring sight of what files actually changed.

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

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

Title:
  Unmodified files should not be rewritten

Status in software-properties package in Ubuntu:
  New

Bug description:
  Right now, all sources list files will be rewritten regardless, even
  if they have not changed. This loses their original last-modified
  timestamp, obscuring sight of what files actually changed.

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


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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

[Julian Andres Klode]

@bmaupin You'll want to use `apt list` to actually then also see in the
output if they are all automatically installed, but if they all are feel
free to open a new bug, there's not much point putting that in this one.

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

Title:
  Only keep 2 kernels

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

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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


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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

[bmaupin]

So I did some more digging, and I guess the 5.15.0-82 kernel is there
because it's required by linux-image-generic:

$ dpkg -l | grep linux-image | grep ^ii
ii  linux-image-5.15.0-82-generic  5.15.0-82.91 
   amd64Signed kernel image generic
ii  linux-image-5.19.0-50-generic  5.19.0-50.50 
   amd64Signed kernel image generic
ii  linux-image-6.2.0-26-generic   6.2.0-26.26~22.04.1  
   amd64Signed kernel image generic
ii  linux-image-6.2.0-31-generic   6.2.0-31.31~22.04.1  
   amd64Signed kernel image generic
ii  linux-image-generic5.15.0.82.78 
   amd64Generic Linux kernel image
ii  linux-image-generic-hwe-22.04  6.2.0.31.31~22.04.8  

Although even after uninstalling linux-image-generic, sudo apt
autoremove still doesn't remove any additional kernels. I guess somehow
the logic that apt uses to remove unused kernels doesn't account for
when multiple linux-image-generic packages are installed because of HWE.

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

Title:
  Only keep 2 kernels

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

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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


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

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

[Oibaf]

Hi, I am not a maintainer, but maybe I can help you a bit.

Can you search in iptables bugzilla if your issue was already reported
(either still open or already closed)?
https://bugzilla.netfilter.org/query.cgi

Also, you may have a look at iptables source (
https://git.netfilter.org/iptables/log/ ) if you find a related fix
after 1.8.7 commit release (happened in 2021-01-15).

If not, report it at:
https://bugzilla.netfilter.org/enter_bug.cgi?product=iptables

Thanks.

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

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

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

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

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled

[Steve Langasek]

There has been a discussion between the several engineering teams
involved regarding a path forward on this bug.  It's acknowledged that
this is a regression which breaks the statement of user intent expressed
by setting the Unattended-Upgrade::Automatic-Reboot option.  However,
this is an uncommon configuration (if you are configuring your system to
automatically reboot on kernel upgrade, you are getting very little
value out of livepatch on top of that since in the common case the
kernel deb is made available to the system before the corresponding
livepatch) so most users are not expected to be using both in
combination.  And we have agreed that we should be getting richer
information from canonical-livepatch about the security bug coverage of
available livepatches vs kernel debs that will allow a more nuanced
decision about whether to tell the user a reboot is required.  This work
is planned for the 24.04 development cycle and we believe will cover
this regression as well; so a targeted fix for this issue is not
currently a priority.

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

Title:
  Unexpected / unwanted unattended-upgrades behaviour after kernel
  upgrade when Livepatch enabled

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Following the resolution for bug #1747499, after a kernel upgrade when
  Livepatch is enabled, the current behaviour in unattended-upgrades
  (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so
  as not to confuse users with two separate messages calling for a
  restart in motd. This functionality is implemented in the script at
  /etc/kernel/postinst.d/unattended-upgrades.

  While this works as intended in terms of suppressing an extra message
  in motd, it defeats the ability of unattended-upgrades to restart
  automatically with the new kernel, which is reliant on
  /var/run/reboot-required being present.

  This is unexpected / unwanted behaviour in scenarios where a)
  Livepatch is being used to provide fast-response kernel patching; and
  b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable
  automatic reboots during a regular maintenance window. In this case,
  without administrative intervention, the system could never boot into
  the new kernel even though it would be expected to, leaving Livepatch
  to do all the heavy lifting indefinitely, and unnecessarily.

  I believe this counts as a regression caused by the resolution to bug
  #1747499. It also has the potential to be a security threat if
  Livepatch doesn't work comprehensively for a particular kernel flaw,
  and an administrator is reliant on expected behaviour according to
  unattended-upgrades settings.

  Potential options for a fix that come to mind:
  1. Revert to original behaviour in 
/etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart 
required*** message to be less alarming or confusing when the cause is a kernel 
upgrade that's being patched by Livepatch.
  2. Add an extra configuration setting (eg 
Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot 
when it's 'recommended' by Livepatch, not reliant on the presence of 
/var/run/reboot-required.
  3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra 
file somewhere. When present, /var/run/reboot-required is always touched, even 
if Livepatch is enabled.

  (This is my first time reporting a bug in this system, and I apologise
  if I haven't followed the usual descriptive format.)

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


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

[Touch-packages] [Bug 2029148] Re: cups snap - can't add printer

[Jeremy Bícha]

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  cups snap - can't add printer

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  With cups as snap I can't add a printer.

  gnome-control-center printer
  20:27:44.5824cc-window[13155]: WARNING: Could not find settings 
panel "printer"
  smbXcli_negprot_smb1_done: No compatible protocol selected by server.
  smbXcli_negprot_smb1_done: No compatible protocol selected by server.
  20:27:50.3557cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:54.5122cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:54.6242cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:55.2845cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:57.9338cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.fedoraproject.Config.Printing was not provided by any .service files
  20:27:57.9348cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  20:27:57.9358cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.fedoraproject.Config.Printing was not provided by any .service files
  20:27:57.9358cc-printers-panel[13155]: WARNING: Installation of the new 
printer failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2029148/+subscriptions


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

[Touch-packages] [Bug 2029148] Re: cups snap - can't add printer

[Julian Andres Klode]

I think this is still Fix Released, the cups deb is back in main, hplip
has been force demoted to make everything sort of work (well no hp
drivers but that's tracked elsewhere).

** Changed in: ubuntu-meta (Ubuntu)
   Status: In Progress => Fix Released

** Tags removed: rls-mm-incoming

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

Title:
  cups snap - can't add printer

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  With cups as snap I can't add a printer.

  gnome-control-center printer
  20:27:44.5824cc-window[13155]: WARNING: Could not find settings 
panel "printer"
  smbXcli_negprot_smb1_done: No compatible protocol selected by server.
  smbXcli_negprot_smb1_done: No compatible protocol selected by server.
  20:27:50.3557cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:54.5122cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:54.6242cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:55.2845cc-printers-panel[13155]: WARNING: Install 
system-config-printer which provides DBus method "GroupPhysicalDevices" to 
group duplicates in device list.
  20:27:57.9338cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.fedoraproject.Config.Printing was not provided by any .service files
  20:27:57.9348cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  20:27:57.9358cc-printers-panel[13155]: WARNING: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.fedoraproject.Config.Printing was not provided by any .service files
  20:27:57.9358cc-printers-panel[13155]: WARNING: Installation of the new 
printer failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2029148/+subscriptions


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

[Touch-packages] [Bug 2030788] Re: Usability: "localectl set-x11-keymap" doesn't work in mantic

[Julian Andres Klode]

** Tags removed: rls-mm-incoming

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

Title:
  Usability: "localectl set-x11-keymap" doesn't work in mantic

Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On the raspi arm64 server image, I used to use cloud-init's keyboard
  module to set my keyboard to GB by default. However, on mantic
  localectl (which the keyboard module uses) is now reporting:

    $ localectl set-x11-keymap gb pc105
    Setting X11 and console keymaps is not supported in Debian

  So ... how do I get my £ key by default now? Or should this be filed
  against systemd as well?

  
  === update 
  cloud-init 23.3 release now writes /etc/default/keyboard directly instead of 
calling: localectl set-x11-keymap. After setting keymap/layout, cloud-init also 
runs: systemctl restart console-setup.

  The remaining question is do we want to improve usability of the error
  message or hints/docs for admins describing how to set up
  keymap/layout?

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


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

[Touch-packages] [Bug 2033129] Re: hplip is in universe and was dropped from Recommends

[Julian Andres Klode]

This depends on bug 2028054

** Tags removed: rls-mm-incoming

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  hplip is in universe and was dropped from Recommends

Status in hplip package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  When preparing the upload of ubuntu-meta 1.516 I wasn't enough
  attentive. Only afterwards I noticed that the update script had caused
  hplip to be removed from the meta packages, even if it is still here:

  https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/platform/tree/desktop-common#n69

  I don't know how to properly correct this. Please help.

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


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

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

[Thomas Sthlm]

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

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

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

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

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

  lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

[bmaupin]

Am I running into this bug or a different one?

apt dist-upgrade started failing for me today. In particular, linux-
firmware is failing to install because /boot is full.

But it looks like I have 4 kernels installed:

$ dpkg -l | grep linux-image-.*-generic  | grep ^ii
ii  linux-image-5.15.0-82-generic  5.15.0-82.91 
   amd64Signed kernel image generic
ii  linux-image-5.19.0-50-generic  5.19.0-50.50 
   amd64Signed kernel image generic
ii  linux-image-6.2.0-26-generic   6.2.0-26.26~22.04.1  
   amd64Signed kernel image generic
ii  linux-image-6.2.0-31-generic   6.2.0-31.31~22.04.1  
   amd64Signed kernel image generic

I tried running sudo apt-get autoremove --purge but it doesn't work, due
to the failed linux-firmware installation.

Should I file a new bug for this? I'm running Ubuntu 22.04 but that
doesn't seem to be listed for this bug.

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

Title:
  Only keep 2 kernels

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

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

Once more for all mixer items.

** Attachment added: "Screenshot from 2023-08-31 15-50-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033275/+attachment/5696829/+files/Screenshot%20from%202023-08-31%2015-50-22.png

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

Here is a screen of the mixer.

** Attachment added: "Screenshot from 2023-08-31 15-48-54.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033275/+attachment/5696828/+files/Screenshot%20from%202023-08-31%2015-48-54.png

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

Built-in sound test does not work at all despite other sound actually
playing briefly, before the silence.

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

Note that sound always starts working for a couple seconds after a
longer silence and then dies immediately again when more sounds are
triggered. Takes about a minute for the reload

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033653] Re: can't report crash in /var/crash with ubuntu-bug, "Network problem"

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Running into a series of bugs isn't the user experience
to be desired.

The HTTP error Bad gateway should be error code 502. Both error codes
502 and 503 indicate a problem on the server side. So this is not a bug
of the Apport client code, but the Launchpad server. So I am re-
assigning it to launchpad.

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

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

Title:
  can't report crash in /var/crash with ubuntu-bug, "Network problem"

Status in Launchpad itself:
  New

Bug description:
  Because of bug #2033652 I was trying to report a gdb crash from
  /var/crash. It spent a long time uploading data, then and then popped
  up an error dialog:

  Network problem
  Cannot connect to crash database, please check your internet connection.
  HTTP Error ???: Bad gateway

  (I don't remember the error code exactly)

  I tried again and had a slightly different result: "HTTP Error 503:
  Service Unavailable" instead of "Bad gateway".

  So... First gimp crashes (bug #2031907). I can't report the crash
  properly for it because gimp is wired to catch segfaults instead of
  letting the OS handle them. Then gdb crashes (bug #2033652) while I'm
  trying to debug the gimp issue. And then I can't report the gdb crash
  properly because of THIS issue.

  Jolly good all around.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, 
signal 11, core limit 0, dump mode 1
   INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb 
(command line "gdb /usr/bin/gimp")
   INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report 
/var/crash/_usr_bin_gdb.1000.crash
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 09:19:25 2023
  InstallationDate: Installed on 2019-01-02 (1702 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

It almost sounds like there is some internal echo or interference going
on before the sound shuts off into silence.

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033275] Re: Constant audio problems making Ubuntu unusable [hostname, Realtek ALC295, Speaker, Internal] fails after a while

[Vasek Tobey Vlcek]

I think this might be related - every key stroke seems to spawn one of
these plug-in things when I hold a key in the terminal.

** Attachment added: "Screenshot from 2023-08-31 15-18-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033275/+attachment/5696809/+files/Screenshot%20from%202023-08-31%2015-18-32.png

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

Title:
  Constant audio problems making Ubuntu unusable [hostname, Realtek
  ALC295, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Really wanted to switch to Ubuntu but there are always some problems.
  It's frustrating. Now, sound doesn't work again (after it fixed itself
  previously for no apparent reason). It just starts playing and
  literally dies out immediately (fades into silence with weird sound
  distortion). Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tobey 16688 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 12:37:23 2023
  InstallationDate: Installed on 2023-03-09 (171 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname, Realtek ALC295, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VD.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX550VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2033653] [NEW] can't report crash in /var/crash with ubuntu-bug, "Network problem"

[Jonathan Kamens]

Public bug reported:

Because of bug #2033652 I was trying to report a gdb crash from
/var/crash. It spent a long time uploading data, then and then popped up
an error dialog:

Network problem
Cannot connect to crash database, please check your internet connection.
HTTP Error ???: Bad gateway

(I don't remember the error code exactly)

I tried again and had a slightly different result: "HTTP Error 503:
Service Unavailable" instead of "Bad gateway".

So... First gimp crashes (bug #2031907). I can't report the crash
properly for it because gimp is wired to catch segfaults instead of
letting the OS handle them. Then gdb crashes (bug #2033652) while I'm
trying to debug the gimp issue. And then I can't report the gdb crash
properly because of THIS issue.

Jolly good all around.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportLog:
 INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, 
signal 11, core limit 0, dump mode 1
 INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb 
(command line "gdb /usr/bin/gimp")
 INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report 
/var/crash/_usr_bin_gdb.1000.crash
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 09:19:25 2023
InstallationDate: Installed on 2019-01-02 (1702 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apport
UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  can't report crash in /var/crash with ubuntu-bug, "Network problem"

Status in apport package in Ubuntu:
  New

Bug description:
  Because of bug #2033652 I was trying to report a gdb crash from
  /var/crash. It spent a long time uploading data, then and then popped
  up an error dialog:

  Network problem
  Cannot connect to crash database, please check your internet connection.
  HTTP Error ???: Bad gateway

  (I don't remember the error code exactly)

  I tried again and had a slightly different result: "HTTP Error 503:
  Service Unavailable" instead of "Bad gateway".

  So... First gimp crashes (bug #2031907). I can't report the crash
  properly for it because gimp is wired to catch segfaults instead of
  letting the OS handle them. Then gdb crashes (bug #2033652) while I'm
  trying to debug the gimp issue. And then I can't report the gdb crash
  properly because of THIS issue.

  Jolly good all around.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, 
signal 11, core limit 0, dump mode 1
   INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb 
(command line "gdb /usr/bin/gimp")
   INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report 
/var/crash/_usr_bin_gdb.1000.crash
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 09:19:25 2023
  InstallationDate: Installed on 2019-01-02 (1702 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


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

[Touch-packages] [Bug 2033652] [NEW] gdb crashes when debugging gimp, can't report crash

[Jonathan Kamens]

Public bug reported:

I was debugging gimp when gdb to debug bug #2031907 when gdb crashed on
me and reported a useless backtrace followed by this:

---

A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
.

Segmentation fault (core dumped)

---

I attempted to report the crash file in /var/crash rather than just
filing a bare bug like this without any crash info, but ubuntu-bug
failed to report the crash, about which I will file a separate bug
report because that's an apport bug rather than a gdb bug.

I imagine there must be a way to get the crash info to you but I don't
know what it is, so if you have any pointers that would be helpful.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gdb 14.0.50.20230810-0ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 09:16:17 2023
InstallationDate: Installed on 2019-01-02 (1702 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gdb
UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  gdb crashes when debugging gimp, can't report crash

Status in gdb package in Ubuntu:
  New

Bug description:
  I was debugging gimp when gdb to debug bug #2031907 when gdb crashed
  on me and reported a useless backtrace followed by this:

  ---

  A fatal error internal to GDB has been detected, further
  debugging is not possible.  GDB will now terminate.

  This is a bug, please report it.  For instructions, see:
  .

  Segmentation fault (core dumped)

  ---

  I attempted to report the crash file in /var/crash rather than just
  filing a bare bug like this without any crash info, but ubuntu-bug
  failed to report the crash, about which I will file a separate bug
  report because that's an apport bug rather than a gdb bug.

  I imagine there must be a way to get the crash info to you but I don't
  know what it is, so if you have any pointers that would be helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gdb 14.0.50.20230810-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 09:16:17 2023
  InstallationDate: Installed on 2019-01-02 (1702 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdb
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


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

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

** Description changed:

  unattended-upgrade ignores apt-pinning to not-allowed origins
  =
  
  BUG:
  
  unattended-upgrade notices an upgrade available in NOT-ALLOWED ORIGINS,
  but then completely ignores those repositories
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.
  
  The situation repeats every time there is an upgrade available in an
  external PPA.
  
  SOLUTION:
  
  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.
  
  
  Instructions for ubuntu lunar 23.04:
  
  
  0. Upgrade all packages, uninstall Firefox:
  
  $ sudo apt update
  
  $ sudo apt upgrade
  
  $ sudo snap remove firefox
  
  $ sudo apt remove firefox
  
  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 1:1snap1-0ubuntu3
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
  
  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:
  
  $ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
  lunar main' | sudo tee /etc/apt/sources.list.d/firefox.list
  
  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21
  
  $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox
  
  $ sudo apt update
  
  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  
  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):
  
  $ sudo apt install firefox
  
  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  100 /var/lib/dpkg/status
  
  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-Team's
  version for Ubuntu 23.04 to 22.04:
  
  Download .deb. file from Mozilla-Team's PPA:
  
  $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
- -d "'" | sed 's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')
+ -d "'" | sed 's/0ubuntu0\.[0-9]+\.[0-9]+\./0ubuntu0.22.04./')
  
  Install it:
  
  $ sudo dpkg -i firefox_*.22.04.*.deb
  dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
  (Reading database ... 295244 files and directories currently installed.)
  Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
  Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
  Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
  Please restart all running instances of firefox, or you will experience 
problems.
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for man-db (2.11.2-1) ...
  
  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.22.04.1~mt1 100
  100 /var/lib/dpkg/status
  
  4. Bug in unattended-upgrade:
  
  Firefox is now at priority 100 ("now").
  Firefox snap package is at priority 500.
  Mozilla-Team PPA has priority 1001, BUT IS NOT IN UNATTENDED-UPGRADE'S 
"ALLOWED ORIGINS".
  
  BUG: unattended-upgrade upgrades Firefox package to 1:1snap1-0ubuntu3:
  
  $ sudo unattended-upgrade -v
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=lunar, o=Ubuntu,a=lunar-security, 
o=UbuntuESMApps,a=lunar-apps-security, 

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

** Attachment added: "instructions-for-bug-2033646-v2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2033646/+attachment/5696805/+files/instructions-for-bug-2033646-v2.txt

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

Title:
  unattended-upgrade ignores apt-pinning to not-allowed origins

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrade ignores apt-pinning to not-allowed origins
  =

  BUG:

  unattended-upgrade notices an upgrade available in NOT-ALLOWED ORIGINS,
  but then completely ignores those repositories
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.

  The situation repeats every time there is an upgrade available in an
  external PPA.

  SOLUTION:

  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.

  Instructions for ubuntu lunar 23.04:
  

  0. Upgrade all packages, uninstall Firefox:

  $ sudo apt update

  $ sudo apt upgrade

  $ sudo snap remove firefox

  $ sudo apt remove firefox

  $ apt-cache policy firefox
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu3
    Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages

  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:

  $ echo 'deb
  https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar main' |
  sudo tee /etc/apt/sources.list.d/firefox.list

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox

  $ sudo apt update

  $ apt-cache policy firefox
  firefox:
    Installed: (none)
    Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
    Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
     1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages

  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):

  $ sudo apt install firefox

  $ apt-cache policy firefox
  firefox:
    Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
    Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
    Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
     1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  100 /var/lib/dpkg/status

  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-
  Team's version for Ubuntu 23.04 to 22.04:

  Download .deb. file from Mozilla-Team's PPA:

  $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 |
  tr -d "'" | sed -E 's/0ubuntu0\.[0-9]+\.[0-9]+\./0ubuntu0.22.04./')

  Install it:

  $ sudo dpkg -i firefox_*.22.04.*.deb
  dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
  (Reading database ... 295244 files and directories currently installed.)
  Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
  Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
  Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
  Please restart all running instances of firefox, or you will experience 
problems.
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for man-db (2.11.2-1) ...

  $ apt-cache policy firefox
  firefox:
    Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
    Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
    Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
     1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.22.04.1~mt1 100
  100 /var/lib/dpkg/status

  4. Bug in unattended-upgrade:

  Firefox is now at priority 100 ("now").
  Firefox snap package is at priority 500.
  

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

Bug https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308 is
most likely caused by this issue.

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

Title:
  unattended-upgrade ignores apt-pinning to not-allowed origins

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrade ignores apt-pinning to not-allowed origins
  =

  BUG:

  unattended-upgrade notices an upgrade available in NOT-ALLOWED ORIGINS,
  but then completely ignores those repositories
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.

  The situation repeats every time there is an upgrade available in an
  external PPA.

  SOLUTION:

  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.


  Instructions for ubuntu lunar 23.04:
  

  0. Upgrade all packages, uninstall Firefox:

  $ sudo apt update

  $ sudo apt upgrade

  $ sudo snap remove firefox

  $ sudo apt remove firefox

  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 1:1snap1-0ubuntu3
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages

  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:

  $ echo 'deb
  https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar main' |
  sudo tee /etc/apt/sources.list.d/firefox.list

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox

  $ sudo apt update

  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages

  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):

  $ sudo apt install firefox

  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  100 /var/lib/dpkg/status

  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-
  Team's version for Ubuntu 23.04 to 22.04:

  Download .deb. file from Mozilla-Team's PPA:

  $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 |
  tr -d "'" | sed
  's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')

  Install it:

  $ sudo dpkg -i firefox_*.22.04.*.deb
  dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
  (Reading database ... 295244 files and directories currently installed.)
  Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
  Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
  Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
  Please restart all running instances of firefox, or you will experience 
problems.
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for man-db (2.11.2-1) ...

  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.22.04.1~mt1 100
  100 /var/lib/dpkg/status

  4. Bug in unattended-upgrade:

  Firefox is now at priority 100 ("now").
  Firefox snap package is at priority 500.
  Mozilla-Team PPA has priority 1001, BUT IS NOT IN UNATTENDED-UPGRADE'S 
"ALLOWED ORIGINS".

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

** Description changed:

  unattended-upgrade ignores apt-pinning to not-allowed origins
  =
  
  BUG:
  
- unattended-upgrade completely ignores NOT ALLOWED ORIGINS
+ unattended-upgrade notices an upgrade available in NOT-ALLOWED ORIGINS,
+ but then completely ignores those repositories
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.
+ 
+ The situation repeats every time there is an upgrade available in an
+ external PPA.
  
  SOLUTION:
  
  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.
  
+ 
  Instructions for ubuntu lunar 23.04:
  
  
  0. Upgrade all packages, uninstall Firefox:
  
- $ sudo apt update
- 
- $ sudo apt upgrade
- 
- $ sudo snap remove firefox
- 
- $ sudo apt remove firefox
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: (none)
-   Candidate: 1:1snap1-0ubuntu3
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+ $ sudo apt update
+ 
+ $ sudo apt upgrade
+ 
+ $ sudo snap remove firefox
+ 
+ $ sudo apt remove firefox
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: (none)
+   Candidate: 1:1snap1-0ubuntu3
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
  
  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:
  
- $ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
+ $ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
  lunar main' | sudo tee /etc/apt/sources.list.d/firefox.list
  
- $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
+ $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21
  
- $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
+ $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox
  
- $ sudo apt update
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: (none)
-   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
-  117.0+build2-0ubuntu0.23.04.1~mt1 1001
-    1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
+ $ sudo apt update
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: (none)
+   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+  117.0+build2-0ubuntu0.23.04.1~mt1 1001
+1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  
  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):
  
- $ sudo apt install firefox
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
-  *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
-    1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
- 100 /var/lib/dpkg/status
+ $ sudo apt install firefox
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+  *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
+1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
+ 100 /var/lib/dpkg/status
  
  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-Team's
  version for Ubuntu 23.04 to 22.04:
  
  Download .deb. file from Mozilla-Team's PPA:
  
- $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
+ $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
  -d "'" | sed 's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')
  
  Install it:
  
- $ sudo dpkg -i firefox_*.22.04.*.deb
- dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
- (Reading database ... 295244 files and directories currently installed.)
- Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
-  

[Touch-packages] [Bug 2033647] [NEW] When monitor set to 60Hz, "join screens" enabled

[Alex]

Public bug reported:

Hello there,

I have Ubuntu 23.04 installed on a Dell XPS 13 9300 with an LG 32" 4K
Ergo Monitor attached as an external display. When I set the "primary
display" at 1080p@60Hz for the LG 32" only with the "secondary display"
of the Dell XPS 13" disabled" and "suspend power" of the Dell XPS 13,
both the "primary display" of the LG 32" and the "secondary display" of
the Dell XPS 13 are both "enabled" when resuming from "power suspend".
Also, the frequency of the "primary display" of the LG 32" is lowered to
30Hz.

If the Ubuntu 23.04 software development team in charge of the X.org
display could rectify the issue regarding the stability of my "primary
display" at 1080p@60Hz during "power suspend" and "power on", that would
be great.


Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 05:03:37 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
InstallationDate: Installed on 2023-05-07 (116 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Dell Inc. XPS 13 9300
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=35826320-1bf8-43d1-831e-3b6e6d6a73e5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2023
dmi.bios.release: 1.19
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.0
dmi.board.name: 0Y4GNJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd07/11/2023:br1.19:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr:sku096D:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar 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/2033647

Title:
  When monitor set to 60Hz, "join screens" enabled

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello there,

  I have Ubuntu 23.04 installed on a Dell XPS 13 9300 with an LG 32" 4K
  Ergo Monitor attached as an external display. When I set the "primary
  display" at 1080p@60Hz for the LG 32" only with the "secondary
  display" of the Dell XPS 13" disabled" and "suspend power" of the Dell
  XPS 13, both the "primary display" of the LG 32" and the "secondary
  display" of the Dell XPS 13 are both "enabled" when resuming from
  "power suspend". Also, the frequency of the "primary display" of the
  LG 32" is lowered to 30Hz.

  If the Ubuntu 23.04 software development team in charge of the X.org
  display could rectify the issue regarding the stability of my "primary
  display" at 1080p@60Hz during "power suspend" and "power on", that
  would be great.

  
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 05:03:37 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2023-05-07 (116 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

Bug https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308 is
most likely caused by this issue.

** Description changed:

  unattended-upgrade ignores apt-pinning to not-allowed origins
  =
  
  BUG:
  
  unattended-upgrade completely ignores NOT ALLOWED ORIGINS
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.
  
  SOLUTION:
  
  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.
  
- 
  Instructions for ubuntu lunar 23.04:
  
  
  0. Upgrade all packages, uninstall Firefox:
  
- $ sudo apt update
- 
- $ sudo apt upgrade
- 
- $ sudo snap remove firefox
- 
- $ sudo apt remove firefox
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: (none)
-   Candidate: 1:1snap1-0ubuntu3
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+ $ sudo apt update
+ 
+ $ sudo apt upgrade
+ 
+ $ sudo snap remove firefox
+ 
+ $ sudo apt remove firefox
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: (none)
+   Candidate: 1:1snap1-0ubuntu3
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
  
  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:
  
- $ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
+ $ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
  lunar main' | sudo tee /etc/apt/sources.list.d/firefox.list
  
- $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
+ $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21
  
- $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
+ $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox
  
- $ sudo apt update
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: (none)
-   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
-  117.0+build2-0ubuntu0.23.04.1~mt1 1001
-1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
+ $ sudo apt update
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: (none)
+   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+  117.0+build2-0ubuntu0.23.04.1~mt1 1001
+    1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  
  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):
  
- $ sudo apt install firefox
- 
- $ apt-cache policy firefox
- firefox:
-   Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
-   Version table:
-  1:1snap1-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
-  *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
-1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
- 100 /var/lib/dpkg/status
+ $ sudo apt install firefox
+ 
+ $ apt-cache policy firefox
+ firefox:
+   Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
+   Version table:
+  1:1snap1-0ubuntu3 500
+ 500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
+  *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
+    1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
+ 100 /var/lib/dpkg/status
  
  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-Team's
  version for Ubuntu 23.04 to 22.04:
  
  Download .deb. file from Mozilla-Team's PPA:
  
- $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
+ $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
  -d "'" | sed 's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')
  
  Install it:
  
- $ sudo dpkg -i firefox_*.22.04.*.deb
- dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
- (Reading database ... 295244 files and directories currently installed.)
- Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
- Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
-

[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.44.0-1ubuntu2

---
network-manager (1.44.0-1ubuntu2) mantic; urgency=medium

  * d/t/{nm.py,nm_netplan.py,network_test_base.py} (LP: #2033391):
- Wait until NM is ready before starting tests
- Add a delay loop checking if NM is already on-line before running each
  test.
  * d/t/nm.py: remove expectedFailure from both tests in Hotplug.
- It's not clear why they were expected to fail. With NM 1.44.0 they are 
passing.
- As this class states that the APs are set up with NM already running, in
  test_auto_detect_ap() self.start_nm() was moved to run before
  self.setup_ap() and the assert was fixed to get the actual gobject data.

 -- Danilo Egea Gondolfo   Wed, 30
Aug 2023 10:09:50 +0100

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

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

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

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


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

[Touch-packages] [Bug 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

** Attachment added: "instructions-for-bug-2033646.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2033646/+attachment/5696782/+files/instructions-for-bug-2033646.txt

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

Title:
  unattended-upgrade ignores apt-pinning to not-allowed origins

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrade ignores apt-pinning to not-allowed origins
  =

  BUG:

  unattended-upgrade completely ignores NOT ALLOWED ORIGINS
  even if they contain apt-pinned versions
  that are more favorable than versions from allowed origins.

  SOLUTION:

  unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
  but check them for providing more favorable version
  and in such case restrain from doing ANY upgrades for such packages.


  Instructions for ubuntu lunar 23.04:
  

  0. Upgrade all packages, uninstall Firefox:

  $ sudo apt update

  $ sudo apt upgrade

  $ sudo snap remove firefox

  $ sudo apt remove firefox

  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 1:1snap1-0ubuntu3
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages

  1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:

  $ echo 'deb
  https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar main' |
  sudo tee /etc/apt/sources.list.d/firefox.list

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  $ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
  Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox

  $ sudo apt update

  $ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages

  2. Install Firefox (from mozilla-team Firefox PPA, as pinned):

  $ sudo apt install firefox

  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
  100 /var/lib/dpkg/status

  3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-
  Team's version for Ubuntu 23.04 to 22.04:

  Download .deb. file from Mozilla-Team's PPA:

  $ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 |
  tr -d "'" | sed
  's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')

  Install it:

  $ sudo dpkg -i firefox_*.22.04.*.deb
  dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
  (Reading database ... 295244 files and directories currently installed.)
  Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb 
...
  Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
  Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
  Please restart all running instances of firefox, or you will experience 
problems.
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for man-db (2.11.2-1) ...

  $ apt-cache policy firefox
  firefox:
Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
   117.0+build2-0ubuntu0.23.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
   *** 117.0+build2-0ubuntu0.22.04.1~mt1 100
  100 /var/lib/dpkg/status

  4. Bug in unattended-upgrade:

  Firefox is now at priority 100 ("now").
  Firefox snap package is at priority 500.
  Mozilla-Team PPA has priority 1001, BUT IS NOT IN UNATTENDED-UPGRADE'S 
"ALLOWED ORIGINS".

  BUG: unattended-upgrade upgrades Firefox package to 

[Touch-packages] [Bug 2033646] [NEW] unattended-upgrade ignores apt-pinning to not-allowed origins

[Piotr Henryk Dabrowski]

Public bug reported:

unattended-upgrade ignores apt-pinning to not-allowed origins
=

BUG:

unattended-upgrade completely ignores NOT ALLOWED ORIGINS
even if they contain apt-pinned versions
that are more favorable than versions from allowed origins.

SOLUTION:

unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
but check them for providing more favorable version
and in such case restrain from doing ANY upgrades for such packages.


Instructions for ubuntu lunar 23.04:


0. Upgrade all packages, uninstall Firefox:

$ sudo apt update

$ sudo apt upgrade

$ sudo snap remove firefox

$ sudo apt remove firefox

$ apt-cache policy firefox
firefox:
  Installed: (none)
  Candidate: 1:1snap1-0ubuntu3
  Version table:
 1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages

1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:

$ echo 'deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
lunar main' | sudo tee /etc/apt/sources.list.d/firefox.list

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
9BDB3D89CE49EC21

$ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox

$ sudo apt update

$ apt-cache policy firefox
firefox:
  Installed: (none)
  Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
  Version table:
 1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
 117.0+build2-0ubuntu0.23.04.1~mt1 1001
   1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages

2. Install Firefox (from mozilla-team Firefox PPA, as pinned):

$ sudo apt install firefox

$ apt-cache policy firefox
firefox:
  Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
  Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
  Version table:
 1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
 *** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
   1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
100 /var/lib/dpkg/status

3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-Team's
version for Ubuntu 23.04 to 22.04:

Download .deb. file from Mozilla-Team's PPA:

$ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 | tr
-d "'" | sed 's/0ubuntu0\.[0-9][0-9]\.[0-9][0-9]\./0ubuntu0.22.04./')

Install it:

$ sudo dpkg -i firefox_*.22.04.*.deb
dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1 
to 117.0+build2-0ubuntu0.22.04.1~mt1
(Reading database ... 295244 files and directories currently installed.)
Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb ...
Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over 
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
Please restart all running instances of firefox, or you will experience 
problems.
Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-1) ...

$ apt-cache policy firefox
firefox:
  Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
  Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
  Version table:
 1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
 117.0+build2-0ubuntu0.23.04.1~mt1 1001
   1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main arm64 Packages
 *** 117.0+build2-0ubuntu0.22.04.1~mt1 100
100 /var/lib/dpkg/status

4. Bug in unattended-upgrade:

Firefox is now at priority 100 ("now").
Firefox snap package is at priority 500.
Mozilla-Team PPA has priority 1001, BUT IS NOT IN UNATTENDED-UPGRADE'S "ALLOWED 
ORIGINS".

BUG: unattended-upgrade upgrades Firefox package to 1:1snap1-0ubuntu3:

$ sudo unattended-upgrade -v
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=lunar, o=Ubuntu,a=lunar-security, 
o=UbuntuESMApps,a=lunar-apps-security, o=UbuntuESM,a=lunar-infra-security
Initial blacklist:
Initial whitelist (not strict):
Packages that will be upgraded: firefox
Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
Preconfiguring packages ...
Preconfiguring packages ...
(Reading database ... 295244 files and directories currently installed.)
Preparing to unpack .../firefox_1%3a1snap1-0ubuntu3_arm64.deb ...
=> Installing the firefox snap
==> Checking 

[Touch-packages] [Bug 2028935] Re: Merge rsyslog 8.2306.0-2

[Julian Andres Klode]

** Changed in: rsyslog (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Merge rsyslog 8.2306.0-2

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  Debian has upgraded rsyslog to 8.2306.0-2.

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


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

[Touch-packages] [Bug 2028935] Re: Merge rsyslog 8.2306.0-2

[Julian Andres Klode]

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: rsyslog (Ubuntu)
   Status: Incomplete => Triaged

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

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

Title:
  Merge rsyslog 8.2306.0-2

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  Debian has upgraded rsyslog to 8.2306.0-2.

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


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

[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1

[G]

In essences Trevor - yes.
I moved the directory, as i would have moved it back if the update had not been 
succeeded. (Being cautions)

To clarify, the move and running the fix install was after I had rebooted using 
previous 18.04 kernel set up, as the 20.04 was not complete/bootable.
So effectively running incomplete 20.04, under 18.04, (and therefore Libra 
Office and other applications did not run).
I hope that make sense.

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

Title:
  package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new
  apparmor package pre-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  package install error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.12-4ubuntu5.3
  ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
  Uname: Linux 4.15.0-213-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Aug 24 02:35:35 2023
  DuplicateSignature:
   package:apparmor:2.12-4ubuntu5.3
   Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-08-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic 
root=UUID=c5495aa8-cf2c-4042-a2ea-4533e9343808 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: apparmor
  Syslog:
   Aug 24 02:04:25 adminn-Lenovo-V110-15ISK dbus-daemon[4678]: [session 
uid=1000 pid=4678] AppArmor D-Bus mediation is enabled
   Aug 24 02:05:26 adminn-Lenovo-V110-15ISK dbus-daemon[856]: [system] AppArmor 
D-Bus mediation is enabled
   Aug 24 02:05:31 adminn-Lenovo-V110-15ISK dbus-daemon[1021]: [session uid=124 
pid=1021] AppArmor D-Bus mediation is enabled
   Aug 24 02:06:04 adminn-Lenovo-V110-15ISK dbus-daemon[1506]: [session 
uid=1000 pid=1506] AppArmor D-Bus mediation is enabled
   Aug 24 03:39:11 adminn-Lenovo-V110-15ISK dbus-daemon[9963]: [session uid=0 
pid=9956] AppArmor D-Bus mediation is enabled
  Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new 
apparmor package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2033639] [NEW] debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

[Benjamin Drung]

Public bug reported:

debug-me 1.20221231-1 fails to build from source on ppc64el due to
internal ld.gold error (binutils 2.41-4ubuntu1):

```
Linking dist/build/debug-me/debug-me ...
/usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050
collect2: error: ld returned 1 exit status
`powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
```

Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu-
mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz

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

** Affects: debug-me (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: update-excuse

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

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

Title:
  debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

Status in binutils package in Ubuntu:
  New
Status in debug-me package in Ubuntu:
  Triaged

Bug description:
  debug-me 1.20221231-1 fails to build from source on ppc64el due to
  internal ld.gold error (binutils 2.41-4ubuntu1):

  ```
  Linking dist/build/debug-me/debug-me ...
  /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050
  collect2: error: ld returned 1 exit status
  `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
  ```

  Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu-
  mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz

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


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

[Touch-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

[Julien Lemaire]

Upgrading to 23.04 didn’t solve the problem in my case.

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

Title:
  Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've tried various fixes without success, I did manage to get the
  NVIDA HDMI in the sound options but I've never had the inbuilt Intel
  Media Hardware working for sound.  22.04 LTS had the same issue and
  I've upgraded to the new version 23.04 which looks good.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 2245 F wireplumber
   /dev/snd/seq:daniel 2241 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 22 17:30:27 2023
  InstallationDate: Installed on 2023-06-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 067X4F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9730
  dmi.product.sku: 0BDB
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 2028935] Re: Merge rsyslog 8.2306.0-2

[Julian Andres Klode]

Heinrich please note that the previous Debian version is a bug fix upload that 
is adequate to go in now (that we might want for the `Update logcheck rules for 
latest debian defaults.
` bug fix), whereas the new Debian version is a new upstream release that has 
to wait for next cycle most likely.

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

Title:
  Merge rsyslog 8.2306.0-2

Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  Debian has upgraded rsyslog to 8.2306.0-2.

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


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

[Touch-packages] [Bug 2033597] Re: System theme messed up for no apparent reason

[Daniel van Vugt]

This is unfortunately a common problem when GTK theme updates get
installed. yaru-theme was updated last night so that's probably what
triggered this.


** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: yaru-theme (Ubuntu)

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  System theme messed up for no apparent reason

Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk4 package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Was browsing the web when all of a sudden all icons changed and system
  theme now looks like a blast from the past.

  Specifically:
  - "Home" icon on the desktop
  - Trash, disk icons on the app drawer
  - Icons and buttons on the "Restart required" msgbox, and its topbar icon 
(next to wifi)
  - Folder icons in Files (nautilus) window

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~beta2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 02:32:02 2023
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2023-08-26 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230825)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2033597/+subscriptions


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

[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

[Stefan Bader]

** Changed in: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

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


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

[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

The patch helped with nm.py and nm_netplan.py tests but the ones that
require building kernel modules are still failing due to the gcc
version.

1749s autopkgtest [00:14:05]:  summary
1749s wpa-dhclient PASS
1749s nm.pyPASS
1749s killswitches-no-urfkill FAIL non-zero exit status 2
1749s urfkill-integration  FAIL non-zero exit status 2
1749s nm_netplan.pyPASS

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

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

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


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