date:20221012

[Touch-packages] [Bug 1992731] Re: The cursor can be freely moved around and used to erase characters on the TTY while at the login prompt

2022-10-12 Thread Alkis Georgopoulos

Reproduced in Ubuntu 22.04 and 20.04.
Could NOT reproduce in Ubuntu 18.04.

I think the problem is in `agetty` though, not in `login`.
Added `util-linux` to affected packages.

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The cursor can be freely moved around and used to erase characters on
  the TTY while at the login prompt

Status in shadow package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  Welp, this is a weird one. Known to affect Ubuntu Server and multiple
  flavors of Ubuntu.

  Steps to reproduce:

  1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a 
TTY.
  2. At the login prompt, press the up arrow key twice.
  3: Press Backspace twice.
  4: Press Enter.

  Expected result: Nothing should happen, or possibly key codes should
  appear when the arrow keys are pressed, and those key codes should be
  erased when backspace is pressed.

  Actual result: The cursor moves up two lines when the up arrow key is
  pressed twice, and the "." and "4" of "22.04.1" are erased when
  Backspace is pressed twice. Upon pressing Enter, the TTY seems to
  freeze (no user input causes anything to happen), then the login
  prompt reverts back to its original state and the cursor assumes its
  proper location.

  Notes:
  This bug was first reported by a user named Liver_K on IRC as happening on 
Ubuntu Server 22.04 after upgrading from 20.04. alkisg then confirmed it on 
Ubuntu MATE 22.04, and I confirmed it on Kubuntu Focus Suite 22.04.

  Yes, you can indeed use this to erase everything in the TTY screen and
  leave the cursor in the upper-left corner as if the system was stuck.
  Pressing Enter resolves it after a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: login 1:4.8.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15
  Uname: Linux 5.17.0-1017-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 13 00:44:03 2022
  InstallationDate: Installed on 2022-10-04 (8 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" (20220916)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992731] [NEW] The cursor can be freely moved around and used to erase characters on the TTY while at the login prompt

2022-10-12 Thread Aaron Rainbolt

Public bug reported:

Welp, this is a weird one. Known to affect Ubuntu Server and multiple
flavors of Ubuntu.

Steps to reproduce:

1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a 
TTY.
2. At the login prompt, press the up arrow key twice.
3: Press Backspace twice.
4: Press Enter.

Expected result: Nothing should happen, or possibly key codes should
appear when the arrow keys are pressed, and those key codes should be
erased when backspace is pressed.

Actual result: The cursor moves up two lines when the up arrow key is
pressed twice, and the "." and "4" of "22.04.1" are erased when
Backspace is pressed twice. Upon pressing Enter, the TTY seems to freeze
(no user input causes anything to happen), then the login prompt reverts
back to its original state and the cursor assumes its proper location.

Notes:
This bug was first reported by a user named Liver_K on IRC as happening on 
Ubuntu Server 22.04 after upgrading from 20.04. alkisg then confirmed it on 
Ubuntu MATE 22.04, and I confirmed it on Kubuntu Focus Suite 22.04.

Yes, you can indeed use this to erase everything in the TTY screen and
leave the cursor in the upper-left corner as if the system was stuck.
Pressing Enter resolves it after a while.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: login 1:4.8.1-2ubuntu2
ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15
Uname: Linux 5.17.0-1017-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 13 00:44:03 2022
InstallationDate: Installed on 2022-10-04 (8 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" (20220916)
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Description changed:

- Welp, this is a weird one. Affects Ubuntu Desktop and Ubuntu Server.
+ Welp, this is a weird one. Affects Ubuntu Server and multiple flavors of
+ Ubuntu.
  
  Steps to reproduce:
  
  1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a 
TTY.
  2. At the login prompt, press the up arrow key twice.
  3: Press Backspace twice.
  4: Press Enter.
  
  Expected result: Nothing should happen, or possibly key codes should
  appear when the arrow keys are pressed, and those key codes should be
  erased when backspace is pressed.
  
  Actual result: The cursor moves up two lines when the up arrow key is
  pressed twice, and the "." and "4" of "22.04.1" are erased when
  Backspace is pressed twice. Upon pressing Enter, the TTY seems to freeze
  (no user input causes anything to happen), then the login prompt reverts
  back to its original state and the cursor assumes its proper location.
  
  Notes:
  This bug was first reported by a user named Liver_K on IRC as happening on 
Ubuntu Server 22.04 after upgrading from 20.04. alkisg then confirmed it on 
Ubuntu MATE 22.04, and I confirmed it on Kubuntu Focus Suite 22.04.
  
  Yes, you can indeed use this to erase everything in the TTY screen and
  leave the cursor in the upper-left corner as if the system was stuck.
  Pressing Enter resolves it after a while.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: login 1:4.8.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15
  Uname: Linux 5.17.0-1017-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 13 00:44:03 2022
  InstallationDate: Installed on 2022-10-04 (8 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" (20220916)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- Welp, this is a weird one. Affects Ubuntu Server and multiple flavors of
- Ubuntu.
+ Welp, this is a weird one. Known to affect Ubuntu Server and multiple
+ flavors of Ubuntu.
  
  Steps to reproduce:
  
  1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a 
TTY.
  2. At the login prompt, press the up arrow key twice.
  3: Press Backspace twice.
  4: Press Enter.
  
  Expected result: Nothing should happen, or possibly key codes should
  appear when the arrow keys are pressed, and those key codes should be
  erased when backspace is pressed.
  
  Actual result: The cursor moves up two lines when the up arrow key is
  pressed twice, and the "." and "4" of "22.04.1" are erased when
  Backspace is pressed twice. Upon pressing Enter, the TTY seems to freeze
  (no user input causes anything to happen), then the login prompt reverts
  back to its original state and the cursor assumes its proper location.
  
  Notes:
  This bug was first reported by a user named Liver_K on IRC as happening on 
Ubuntu Server 22.04 after upgrading from 20.04. alkisg then confirmed it on 
Ubuntu MATE 22.04, and I confirmed it on Kubuntu Focus Suite 22.04.
  
  Yes, you c

[Touch-packages] [Bug 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

2022-10-12 Thread Bug Watch Updater

** Changed in: firefox
   Importance: Medium => Unknown

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

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


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

[Touch-packages] [Bug 1992727] [NEW] package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-10-12 Thread yevgen

Public bug reported:

it just said it want to report a problem

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Oct 13 07:00:41 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-01-09 (641 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  it just said it want to report a problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 13 07:00:41 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-01-09 (641 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992105] Re: missing httpform plugin for saslauthd

2022-10-12 Thread Amit

Hi Lena, Does this ppa include packages for ARM64?  The update/upgrade
steps didn't seem to pull down any packages on my local VM running on
Mac M1 chip.

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

Title:
  missing httpform plugin for saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 source package in Jammy:
  In Progress
Status in cyrus-sasl2 source package in Kinetic:
  In Progress

Bug description:
  Hi, we noticed missing httpform plugin for saslauthd.  We are
  migrating from Centos.

  == On Centos (Notice the httpform at the end)

  /usr/sbin/saslauthd -v
  saslauthd 2.1.26
  authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform

  
  == On Ubuntu jammy
  /usr/sbin/saslauthd -v
  saslauthd 2.1.27
  authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap

  
  == Potential fix

  add the "--enable-httpform" flag to the sasl2-bin package build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct  6 14:54:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cyrus-sasl2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992707] Re: Extreme lag when switching to workspace overview

2022-10-12 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Tags added: nvidia

** Tags added: multimonitor

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

Title:
  Extreme lag when switching to workspace overview

Status in Ubuntu:
  Incomplete

Bug description:
  I recently updated from Ubuntu 20.04 to 22.04 and am experiencing
  significantly more lag. The most noticeable one is when entering and
  leaving the workspace overview. In 20.04 this was very fast (~0.5
  seconds?) and now it is taking ~2.8s after pressing Windows key before
  I can see the workspace overview and click to a different window or
  search for an application. The same in reverse; ~2.8s after pressing
  Esc or Windows key before I am returned control inside an application.

  I currently have some extensions installed but removed them all and
  was experiencing the same thing. This still occurs if I have no
  windows opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.14.0-1052.59-oem 5.14.21
  Uname: Linux 5.14.0-1052-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..18.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  520.61.05  Thu Sep 29 
05:30:25 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 13 11:14:08 2022
  DistUpgraded: 2022-10-07 13:42:32,957 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/520.61.05, 5.14.0-1052-oem, x86_64: installed
   nvidia/520.61.05, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P620] [10de:1cb6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GP107GL [Quadro P620] [10de:1264]
  InstallationDate: Installed on 2020-04-30 (895 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 30BBS6MG00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1052-oem 
root=UUID=124d9ac4-32b7-4679-a582-019a8f4235e0 ro quiet splash 
acpi_enfore_resources=lax vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-10-07 (5 days ago)
  dmi.bios.date: 07/21/2020
  dmi.bios.release: 1.48
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S04KT48A
  dmi.board.name: 1037
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 19.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrS04KT48A:bd07/21/2020:br1.48:efr19.31:svnLENOVO:pn30BBS6MG00:pvrThinkStationP720:rvnLENOVO:rn1037:rvrNODPK:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30BB_BU_Think_FM_ThinkStationP720:
  dmi.product.family: ThinkStation P720
  dmi.product.name: 30BBS6MG00
  dmi.product.sku: LENOVO_MT_30BB_BU_Think_FM_ThinkStation P720
  dmi.product.version: ThinkStation P720
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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/1992707/+subscriptions


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

[Touch-packages] [Bug 1992707] Re: Extreme lag when switching to workspace overview

2022-10-12 Thread 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/1992707

Title:
  Extreme lag when switching to workspace overview

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently updated from Ubuntu 20.04 to 22.04 and am experiencing
  significantly more lag. The most noticeable one is when entering and
  leaving the workspace overview. In 20.04 this was very fast (~0.5
  seconds?) and now it is taking ~2.8s after pressing Windows key before
  I can see the workspace overview and click to a different window or
  search for an application. The same in reverse; ~2.8s after pressing
  Esc or Windows key before I am returned control inside an application.

  I currently have some extensions installed but removed them all and
  was experiencing the same thing. This still occurs if I have no
  windows opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.14.0-1052.59-oem 5.14.21
  Uname: Linux 5.14.0-1052-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..18.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  520.61.05  Thu Sep 29 
05:30:25 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 13 11:14:08 2022
  DistUpgraded: 2022-10-07 13:42:32,957 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/520.61.05, 5.14.0-1052-oem, x86_64: installed
   nvidia/520.61.05, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P620] [10de:1cb6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GP107GL [Quadro P620] [10de:1264]
  InstallationDate: Installed on 2020-04-30 (895 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 30BBS6MG00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1052-oem 
root=UUID=124d9ac4-32b7-4679-a582-019a8f4235e0 ro quiet splash 
acpi_enfore_resources=lax vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-10-07 (5 days ago)
  dmi.bios.date: 07/21/2020
  dmi.bios.release: 1.48
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S04KT48A
  dmi.board.name: 1037
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 19.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrS04KT48A:bd07/21/2020:br1.48:efr19.31:svnLENOVO:pn30BBS6MG00:pvrThinkStationP720:rvnLENOVO:rn1037:rvrNODPK:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30BB_BU_Think_FM_ThinkStationP720:
  dmi.product.family: ThinkStation P720
  dmi.product.name: 30BBS6MG00
  dmi.product.sku: LENOVO_MT_30BB_BU_Think_FM_ThinkStation P720
  dmi.product.version: ThinkStation P720
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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/1992707/+subscriptions


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

[Touch-packages] [Bug 1992707] [NEW] Extreme lag when switching to workspace overview

2022-10-12 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I recently updated from Ubuntu 20.04 to 22.04 and am experiencing
significantly more lag. The most noticeable one is when entering and
leaving the workspace overview. In 20.04 this was very fast (~0.5
seconds?) and now it is taking ~2.8s after pressing Windows key before I
can see the workspace overview and click to a different window or search
for an application. The same in reverse; ~2.8s after pressing Esc or
Windows key before I am returned control inside an application.

I currently have some extensions installed but removed them all and was
experiencing the same thing. This still occurs if I have no windows
opened.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.14.0-1052.59-oem 5.14.21
Uname: Linux 5.14.0-1052-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..18.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  520.61.05  Thu Sep 29 05:30:25 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 13 11:14:08 2022
DistUpgraded: 2022-10-07 13:42:32,957 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/520.61.05, 5.14.0-1052-oem, x86_64: installed
 nvidia/520.61.05, 5.15.0-50-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107GL [Quadro P620] [10de:1cb6] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GP107GL [Quadro P620] [10de:1264]
InstallationDate: Installed on 2020-04-30 (895 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 30BBS6MG00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1052-oem 
root=UUID=124d9ac4-32b7-4679-a582-019a8f4235e0 ro quiet splash 
acpi_enfore_resources=lax vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-10-07 (5 days ago)
dmi.bios.date: 07/21/2020
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: S04KT48A
dmi.board.name: 1037
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 19.31
dmi.modalias: 
dmi:bvnLENOVO:bvrS04KT48A:bd07/21/2020:br1.48:efr19.31:svnLENOVO:pn30BBS6MG00:pvrThinkStationP720:rvnLENOVO:rn1037:rvrNODPK:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30BB_BU_Think_FM_ThinkStationP720:
dmi.product.family: ThinkStation P720
dmi.product.name: 30BBS6MG00
dmi.product.sku: LENOVO_MT_30BB_BU_Think_FM_ThinkStation P720
dmi.product.version: ThinkStation P720
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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 performance possible-manual-nvidia-install 
ubuntu
-- 
Extreme lag when switching to workspace overview
https://bugs.launchpad.net/bugs/1992707
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 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Alex Murray

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

** This bug has been marked a duplicate of bug 1991704
   Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)

2022-10-12 Thread Daniel van Vugt

Thanks for the bug report. Yes the screenshot shows texture corruption
which may also relate to missing windows. If DG2 is anything like the
desktop Arc chips then you will need Mesa 22.2 (Ubuntu 22.10) to support
it. As well as kernel 6.0.

Please run:

  lspci -k > lspci.txt

and attach the resulting text file here.

Please also consider testing Ubuntu 22.10:

  https://cdimage.ubuntu.com/daily-live/current/

because that's probably the only Ubuntu release with an adequate Mesa
version.

** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

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

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

Title:
  Application windows invisible (on DG2 graphics)

Status in linux-oem-6.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992667] [NEW] Application windows invisible (on DG2 graphics)

2022-10-12 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

When using GNOME Shell with Wayland, all application windows become
invisible from time to time. This usually happens right after starting
GNOME Shell for the first time or after having a VRAM intensive
application open, such as a game.

I have installed the latest linux-oem-6.0 kernel and manually enabled
support for DG2 graphics by passing the i915.force_probe parameter with
the PCIe ID of the graphics card.

I have attached a screenshot of the described behavior below.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 17:23:40 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-10-11 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy
-- 
Application windows invisible (on DG2 graphics)
https://bugs.launchpad.net/bugs/1992667
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

[Touch-packages] [Bug 1992684] Re: Opening programs crashes xorg to login screen Ubuntu 20.04

2022-10-12 Thread Daniel van Vugt

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Tags added: matrox mgag200

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

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

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

Title:
  Opening programs crashes xorg to login screen Ubuntu 20.04

Status in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Opening programs such as Firefox, terminal, and files crashes Ubuntu
  20.04 to the login screen. When Ubuntu crashes, it makes a core file
  from xorg crash.

  This crash behavior began around September 25 2022. I have been using
  Ubuntu 20.04 since it was released and I have not experienced any
  crashing before.

  I am unsure what other information would be useful. The computer is a
  dell poweredge r410.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Oct 12 13:47:05 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Dell PowerEdge R410 MGA G200eW WPCM450 [1028:028c]
  InstallationDate: Installed on 2020-05-25 (870 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. PowerEdge R410
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=bb831c8f-6ec7-4c90-b98b-f4dc367f632b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 01V648
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd05/30/2018:br1.14:svnDellInc.:pnPowerEdgeR410:pvr:rvnDellInc.:rn01V648:rvrA06:cvnDellInc.:ct23:cvr:sku:
  dmi.product.name: PowerEdge R410
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1990742] Re: screen not consistently locking when lid is closed

2022-10-12 Thread Daniel van Vugt

Bug 1857392 occurs on practically all machines every day so I recommend
ignoring that one specifically. In comment #13 I think I was just
pointing out there seems to be a common root cause if we can find out
why/where bug 1857392 occurs so often.

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

Title:
  screen not consistently locking when lid is closed

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have GNOME configured to lock the screen when the screen is blanked,
  and to blank the screen when the lid is closed:

  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
  org.gnome.desktop.screensaver lock-delay uint32 0
  org.gnome.desktop.screensaver lock-enabled true

  This worked fine in Jammy: whenever my screen was unlocked and I
  closed my laptop lid, it locked immediately, i.e., if I immediately
  reopened my lid, the screen was locked.

  After having just upgraded to Kinetic, however, sometimes when I close
  the lid it locks as described above, and sometimes it just... doesn't,
  i.e., when I open the lid again the screen is unlocked and I can just
  keep working.

  I have been unable to determine what the factors are which control
  whether the screen locks when I close the lid.

  There is a moderate security implication here, as it's problematic for
  someone's screen not to lock when they think that it did.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:57:37 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)

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


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

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-12 Thread Daniel van Vugt

Duplicate bug 1970402 mentions that:

> Workaround: Disable Secure Boot and SGX.

works for multiple people.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/buil

[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-10-12 Thread Daniel van Vugt

Which package should be marked as Fix Released for 22.10?

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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

[Touch-packages] [Bug 1992701] [NEW] Issue with opening module dependency file

2022-10-12 Thread Michal Dziczkowski

Public bug reported:

Tested on: Trusty, Xenial (used as recovery system)

I'm unable to manage (modprobe, insmod) modules due following error:

"modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could
not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'"

I don't know why, but it seem like in the libkmod.c was a bug that
attempt to load an old kernel after it got upgraded (replaced with) a
newer one.

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


** Tags: kmod

** Attachment added: "Screenshoot of the error message in terminal"
   
https://bugs.launchpad.net/bugs/1992701/+attachment/5623647/+files/kmod_error.png

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

Title:
  Issue with opening module dependency file

Status in kmod package in Ubuntu:
  New

Bug description:
  Tested on: Trusty, Xenial (used as recovery system)

  I'm unable to manage (modprobe, insmod) modules due following error:

  "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could
  not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'"

  I don't know why, but it seem like in the libkmod.c was a bug that
  attempt to load an old kernel after it got upgraded (replaced with) a
  newer one.

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


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

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Dimitri John Ledkov

initramfs-tools also mounts /dev with nosuid, without noexec

> mount -t devtmpfs -o nosuid,mode=0755 udev /dev

I believe all of these should be the same, thus kernel can mount /dev
with nosuid, but should not mount it with noexec.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Dave Chiluk

Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality.  I do
think the nosuid flag does still provide some benefit even if we decide
not to include the noexec flag by default until 5.17+.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1990742] Re: screen not consistently locking when lid is closed

2022-10-12 Thread Nick Rosbrook

When I configure my systemd to lock on lid switch, I do see this debug-
level message:

Oct 12 16:19:45 six systemd-logind[1173]: Inhibitor GNOME Shell (GNOME
needs to lock the screen) pid=2894 uid=1000 mode=delay started.

I am not sure exactly how GNOME handles locking the screen, but maybe
the bug that Daniel pointed out (bug 1857392) is preventing GNOME from
processing an Inhibitor DBus signal and locking the screen in a timely
manner.

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

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

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

Title:
  screen not consistently locking when lid is closed

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have GNOME configured to lock the screen when the screen is blanked,
  and to blank the screen when the lid is closed:

  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
  org.gnome.desktop.screensaver lock-delay uint32 0
  org.gnome.desktop.screensaver lock-enabled true

  This worked fine in Jammy: whenever my screen was unlocked and I
  closed my laptop lid, it locked immediately, i.e., if I immediately
  reopened my lid, the screen was locked.

  After having just upgraded to Kinetic, however, sometimes when I close
  the lid it locks as described above, and sometimes it just... doesn't,
  i.e., when I open the lid again the screen is unlocked and I can just
  keep working.

  I have been unable to determine what the factors are which control
  whether the screen locks when I close the lid.

  There is a moderate security implication here, as it's problematic for
  someone's screen not to lock when they think that it did.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:57:37 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)

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


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

[Touch-packages] [Bug 1990742] Re: screen not consistently locking when lid is closed

2022-10-12 Thread Nick Rosbrook

My first guess is that there is an inhibitor lock for "handle-lid-
switch" in place which is blocking or delaying the screen lock.

Jonathan - Can you please enable debug level logging on systemd-
logind.service by doing the following?

$ systemctl edit systemd-logind.service

In the editor, add a section like this:

 [Service]
 Environment=SYSTEMD_LOG_LEVEL=debug

Then reboot, and next time you experience this issue share the log:

$ journalctl -b -u systemd-logind --no-pager > systemd-logind.log

It is probably also worth sharing your logind.conf:

$ systemd-analyze cat-config systemd/logind.conf > logind.conf

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

Title:
  screen not consistently locking when lid is closed

Status in systemd package in Ubuntu:
  New

Bug description:
  I have GNOME configured to lock the screen when the screen is blanked,
  and to blank the screen when the lid is closed:

  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
  org.gnome.desktop.screensaver lock-delay uint32 0
  org.gnome.desktop.screensaver lock-enabled true

  This worked fine in Jammy: whenever my screen was unlocked and I
  closed my laptop lid, it locked immediately, i.e., if I immediately
  reopened my lid, the screen was locked.

  After having just upgraded to Kinetic, however, sometimes when I close
  the lid it locks as described above, and sometimes it just... doesn't,
  i.e., when I open the lid again the screen is unlocked and I can just
  keep working.

  I have been unable to determine what the factors are which control
  whether the screen locks when I close the lid.

  There is a moderate security implication here, as it's problematic for
  someone's screen not to lock when they think that it did.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:57:37 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)

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


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

[Touch-packages] [Bug 1992690] Re: Fix large thumbnails with Nautilus

2022-10-12 Thread Bug Watch Updater

** Changed in: glib
   Status: Unknown => Fix Released

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

Title:
  Fix large thumbnails with Nautilus

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 package in Debian:
  New

Bug description:
  Impact
  --

  Copying this report from Debian.

  I have a 4K monitor with 175% fractional scaling.

  Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite
  loop trying to create x-large and xx-large thumbnails, consuming CPU
  forever.

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


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

[Touch-packages] [Bug 1992692] Re: tzdata 2022e release

2022-10-12 Thread Benjamin Drung

** Description changed:

  New timezone data, with the following timezones impacted:
  - Palestine transitions are now Saturdays at 02:00. This means 2022 falls
-   back 10-29 at 02:00, not 10-28 at 01:00.
+   back 10-29 at 02:00, not 10-28 at 01:00.
  - Simplify three Ukraine zones into one.
  - Jordan and Syria switch from +02/+03 with DST to year-round +03.
+ 
+ icu update to 2022e: https://unicode-org.atlassian.net/browse/ICU-22178

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

Title:
  tzdata 2022e release

Status in tzdata package in Ubuntu:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Palestine transitions are now Saturdays at 02:00. This means 2022 falls
    back 10-29 at 02:00, not 10-28 at 01:00.
  - Simplify three Ukraine zones into one.
  - Jordan and Syria switch from +02/+03 with DST to year-round +03.

  icu update to 2022e: https://unicode-
  org.atlassian.net/browse/ICU-22178

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


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

[Touch-packages] [Bug 1992692] Re: tzdata 2022e release

2022-10-12 Thread Benjamin Drung

** Changed in: tzdata (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  tzdata 2022e release

Status in tzdata package in Ubuntu:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
  - Simplify three Ukraine zones into one.
  - Jordan and Syria switch from +02/+03 with DST to year-round +03.

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


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

[Touch-packages] [Bug 1969671] Re: Misspelled Ukrainian cities in tzdata

2022-10-12 Thread Benjamin Drung

And the remaining cities are addressed in 2022d: "Simplify three Ukraine
zones into one". Uzhgorod and Zaporozhye are merged into Europe/Kyiv.

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

Title:
  Misspelled Ukrainian cities in tzdata

Status in tzdata package in Ubuntu:
  New

Bug description:
  When user is prompted to choose a city in the region 'Europe' they
  have a choice of 4 cities in Ukraine:

  23. Kiev  -> should be Kyiv
  46. Simferopol  - > OK
  54. Uzhgorod  -> should be Uzhhorod
  62. Zaporozhye -> should be Zaporizhzhia

  The 'should be' variant is the only correct transliteration from
  Ukrainian into English.

  

  Possible useful pieces of ubuntu-bug report (run in a headless
  ubuntu/latest docker image):

  DistroRelease: Ubuntu 20.04
  Package: tzdata 2022a-0ubuntu0.20.04
  Tags:  focal
  PackageArchitecture: all

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


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

[Touch-packages] [Bug 1992692] Re: tzdata 2022e release

2022-10-12 Thread Benjamin Drung

** Summary changed:

- tzdata 2022c release
+ tzdata 2022e release

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

Title:
  tzdata 2022e release

Status in tzdata package in Ubuntu:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
  - Simplify three Ukraine zones into one.
  - Jordan and Syria switch from +02/+03 with DST to year-round +03.

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


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

[Touch-packages] [Bug 1980408] Re: Update glib to 2.72.4

2022-10-12 Thread Jeremy Bicha

** Summary changed:

- Update glib to 2.72.3
+ Update glib to 2.72.4

** Description changed:

  Impact
  --
  There is a new bugfix release in the stable 2.72 series
  
- https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS
+ https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS
  
  Test Case 1
  ---
  glib has an extensive test suite.
  
  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.
  
  Ensure that there aren't autopgktest regressions triggered by this
  update and that the builds complete successfully
  
  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser
  
  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

** Changed in: glib2.0 (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

Title:
  Update glib to 2.72.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.72 series

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopgktest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

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


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

[Touch-packages] [Bug 1992692] [NEW] tzdata 2022c release

2022-10-12 Thread Benjamin Drung

Public bug reported:

New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
  back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST to year-round +03.

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

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

Title:
  tzdata 2022c release

Status in tzdata package in Ubuntu:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
  - Simplify three Ukraine zones into one.
  - Jordan and Syria switch from +02/+03 with DST to year-round +03.

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


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

[Touch-packages] [Bug 1992690] Re: Fix large thumbnails with Nautilus

2022-10-12 Thread Bug Watch Updater

** Changed in: glib2.0 (Debian)
   Status: Unknown => New

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

Title:
  Fix large thumbnails with Nautilus

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 package in Debian:
  New

Bug description:
  Impact
  --

  Copying this report from Debian.

  I have a 4K monitor with 175% fractional scaling.

  Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite
  loop trying to create x-large and xx-large thumbnails, consuming CPU
  forever.

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


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

[Touch-packages] [Bug 1934559] Re: Typo in capital of Ukraine

2022-10-12 Thread Benjamin Drung

Marking this bug as fixed since tzdata >= 2022b is in Ubuntu >= 18.04
via updates.

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

** Changed in: tzdata (Ubuntu)
   Status: New => 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/1934559

Title:
  Typo in capital of Ukraine

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  During installation on a map and in timezone settings there's "Kiev" city, 
but it's not correct.
  Should be Kyiv - https://en.wikipedia.org/wiki/Kyiv.
  Ubuntu 21.04.

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


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-10-12 Thread soonan

I wrote a solution on this GitHub
thread:https://github.com/wwmm/easyeffects/issues/1644

However I think this package should get an update to fix this. Thanks!

** Bug watch added: github.com/wwmm/easyeffects/issues #1644
   https://github.com/wwmm/easyeffects/issues/1644

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

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


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

[Touch-packages] [Bug 1992690] [NEW] Fix large thumbnails with Nautilus

2022-10-12 Thread Jeremy Bicha

Public bug reported:

Impact
--

Copying this report from Debian.

I have a 4K monitor with 175% fractional scaling.

Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite
loop trying to create x-large and xx-large thumbnails, consuming CPU
forever.

** Affects: glib
 Importance: Unknown
 Status: Unknown

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: In Progress

** Affects: glib2.0 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: kinetic

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

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

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2767
   https://gitlab.gnome.org/GNOME/glib/-/issues/2767

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/-/issues/2767
   Importance: Unknown
   Status: Unknown

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

Title:
  Fix large thumbnails with Nautilus

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 package in Debian:
  Unknown

Bug description:
  Impact
  --

  Copying this report from Debian.

  I have a 4K monitor with 175% fractional scaling.

  Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite
  loop trying to create x-large and xx-large thumbnails, consuming CPU
  forever.

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


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

[Touch-packages] [Bug 1990692] Re: samba profile needs updating

2022-10-12 Thread Launchpad Bug Tracker

This bug was fixed in the package apparmor - 3.0.7-1ubuntu2

---
apparmor (3.0.7-1ubuntu2) kinetic; urgency=medium

  * ubuntu/add-mqueue-support.patch: add message queue IPC support to
parser, python tools, and regression tests.
  * ubuntu/add-userns-support.patch: add user namespace support to
parser.
  * ubuntu/lp1990692-update-samba-profile.patch: update samba policy to
enable the printing subsystem to work (LP: #1990692)

 -- Georgia Garcia   Fri, 23 Sep 2022
18:21:44 -0300

** Changed in: apparmor (Ubuntu)
   Status: New => 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/1990692

Title:
  samba profile needs updating

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  kinetic
  apparmor 3.0.7-1ubuntu1

  sudo apt install apparmor-profiles apparmor-utils apparmor-profiles-extra
  sudo apt install samba smbclient cups cups-client

  Create a fake printer:
  sudo lpadmin -p testprinter -E -v /dev/null

  Set a password for the samba "root" user:
  printf "root\nroot\n" | sudo smbpasswd -a root

  Just to be sure, restart things:
  sudo systemctl restart smbd nmbd

  Check it's there:
  sudo lpstat -l -p testprinter

  This command (using the password you chose in smbpasswd earlier) will trigger 
a bunch of apparmor ALLOWED messages regarding the samba profiles:
  rpcclient -Uroot%root localhost -c 'getprinter testprinter 2'

  
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.870:99): 
apparmor="ALLOWED" operation="mknod" profile="smbd" 
name="/run/samba/msg.sock/1002" pid=1002 comm="smbd" requested_mask="c" 
denied_mask="c" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.886:100): 
apparmor="ALLOWED" operation="file_mmap" profile="samba-dcerpcd" 
name="/usr/libexec/samba/samba-dcerpcd" pid=1003 comm="samba-dcerpcd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.906:101): 
apparmor="ALLOWED" operation="open" profile="samba-dcerpcd" 
name="/usr/libexec/samba/" pid=1003 comm="samba-dcerpcd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.910:102): 
apparmor="ALLOWED" operation="mknod" profile="samba-dcerpcd" 
name="/run/samba/msg.sock/1003" pid=1003 comm="samba-dcerpcd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.910:103): 
apparmor="ALLOWED" operation="file_lock" profile="samba-dcerpcd" 
name="/run/samba/names.tdb" pid=1003 comm="samba-dcerpcd" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.910:104): 
apparmor="ALLOWED" operation="mknod" profile="samba-dcerpcd" 
name="/run/samba/msg.sock/1004" pid=1004 comm="samba-dcerpcd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.914:105): 
apparmor="ALLOWED" operation="file_lock" profile="samba-dcerpcd" 
name="/run/samba/gencache.tdb" pid=1004 comm="samba-dcerpcd" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.918:106): 
apparmor="ALLOWED" operation="file_lock" profile="samba-dcerpcd" 
name="/run/samba/epmdb.tdb" pid=1004 comm="samba-dcerpcd" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.926:107): 
apparmor="ALLOWED" operation="file_mmap" profile="samba-rpcd" 
name="/usr/libexec/samba/rpcd_epmapper" pid=1007 comm="rpcd_epmapper" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [Fri Sep 23 18:37:42 2022] audit: type=1400 audit(1663958262.926:108): 
apparmor="ALLOWED" operation="file_mmap" profile="samba-rpcd" 
name="/usr/libexec/samba/rpcd_fsrvp" pid=1008 comm="rpcd_fsrvp" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  We have the following classes:
  a) /run/samba/msg.sock/
  This msg.sock/ stuff used to live in /var/lib/samba/private, and was covered 
by other apparmor rules, but in 2:4.16.1+dfsg-1 was moved[1] to /run/samba. I 
suggest this change in abstractions/samba:
  -  @{run}/{,lock/}samba/msg.lock/ rwk,
  -  @{run}/{,lock/}samba/msg.lock/[0-9]* rwk,
  +  @{run}/{,lock/}samba/msg.{lock,sock}/ rwk,
  +  @{run}/{,lock/}samba/msg.{lock,sock}/[0-9]* rwk,

  
  b) "k" on /run/samba/*.tdb
  I suggest this on abstractions/samba:
  -  @{run}/{,lock/}samba/*.tdb rw,
  +  @{run}/{,lock/}samba/*.tdb rwk,

  
  c) libexec
  Since [2], many binary helpers were moved to /usr/libexec/samba
  Unsure where this is best allowed. Not all profiles include 
abstractions/samba or abstractions/samba-rpcd

  d) ncalrpc
  Seems fixed already in upstream apparmor:
  $ grep ncalrpc -r .
  ./profiles/apparmor.d/samba-dcerpcd:  @{run}/samba/ncalrpc/ rw,
  ./profiles/apparmor.d/sam

[Touch-packages] [Bug 1992684] [NEW] Opening programs crashes xorg to login screen Ubuntu 20.04

2022-10-12 Thread Cole

Public bug reported:

Hello,

Opening programs such as Firefox, terminal, and files crashes Ubuntu
20.04 to the login screen. When Ubuntu crashes, it makes a core file
from xorg crash.

This crash behavior began around September 25 2022. I have been using
Ubuntu 20.04 since it was released and I have not experienced any
crashing before.

I am unsure what other information would be useful. The computer is a
dell poweredge r410.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Oct 12 13:47:05 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
   Subsystem: Dell PowerEdge R410 MGA G200eW WPCM450 [1028:028c]
InstallationDate: Installed on 2020-05-25 (870 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. PowerEdge R410
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=bb831c8f-6ec7-4c90-b98b-f4dc367f632b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2018
dmi.bios.release: 1.14
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.name: 01V648
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd05/30/2018:br1.14:svnDellInc.:pnPowerEdgeR410:pvr:rvnDellInc.:rn01V648:rvrA06:cvnDellInc.:ct23:cvr:sku:
dmi.product.name: PowerEdge R410
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1992684

Title:
  Opening programs crashes xorg to login screen Ubuntu 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  Opening programs such as Firefox, terminal, and files crashes Ubuntu
  20.04 to the login screen. When Ubuntu crashes, it makes a core file
  from xorg crash.

  This crash behavior began around September 25 2022. I have been using
  Ubuntu 20.04 since it was released and I have not experienced any
  crashing before.

  I am unsure what other information would be useful. The computer is a
  dell poweredge r410.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Oct 12 13:47:05 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Dell PowerEdge R410 MGA G200eW WPCM450 [1028:028c]
  InstallationDate: Installed on 2020-05-25 (870 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. PowerEdge R410
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=bb831c8f-6ec7-4c90-b98b-f4dc367f632b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 01V648
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd05/30/2018:br1.14:svnDellInc.:pnPowerEdgeR410:pvr:rvnDellInc.:rn01V648:rvrA06:cvnDellInc.:ct23:cvr:sku:
  dmi.product.name: PowerEdge R410
  dmi.sys.vendor: Dell Inc.
  version.compiz: compi

[Touch-packages] [Bug 1992658] Re: In GUI Network status is showing as Registered when modem is in connected State

2022-10-12 Thread Brian Murray

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

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

Title:
  In GUI Network status is showing as Registered when modem is in
  connected State

Status in modemmanager package in Ubuntu:
  New

Bug description:
  RVP:   ADLPWWAN613
  Kernel Version: 5.15.36--wwan-bkc-5
  OS Version:   Ubuntu 22.04. LTS
  IOSM: IOSM_DRIVER_v8.06.13_5.15.36-wwan-bkc-5_2022_SEP01
  MSDK Version :  MSDK_4G_ML_2022_SEP29_00
  Modem Version: M2_7560_R_01.2240.00
  ModemManager Version (ModemManager -V) : 1.19.1
  libMbim Version (mbimcli -V):   1.27.5

  Test steps:

  1. Boot the RVP
  2. Run the Modem Manager in debug mode
  3. Enable AP Mode ON & check Modem details in GUI
  4. Attach to the LTE Network & check Modem details in GUI
  8. Move the modem to connected state using connect API & check Modem details 
in GUI
  >Observation:- 
  1. When Modem is in AP mode on observed Network Status as unknown

  2. When Modem is in connected state able to see Network status as
  Registered in GUI.

  Expected result:- 
  When Modem is in connected state should be able to see Network status as 
Connected in GUI.

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


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

[Touch-packages] [Bug 1992658] [NEW] In GUI Network status is showing as Registered when modem is in connected State

2022-10-12 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

RVP:   ADLPWWAN613
Kernel Version: 5.15.36--wwan-bkc-5
OS Version:   Ubuntu 22.04. LTS
IOSM: IOSM_DRIVER_v8.06.13_5.15.36-wwan-bkc-5_2022_SEP01
MSDK Version :  MSDK_4G_ML_2022_SEP29_00
Modem Version: M2_7560_R_01.2240.00
ModemManager Version (ModemManager -V) : 1.19.1
libMbim Version (mbimcli -V):   1.27.5

Test steps:

1. Boot the RVP
2. Run the Modem Manager in debug mode
3. Enable AP Mode ON & check Modem details in GUI
4. Attach to the LTE Network & check Modem details in GUI
8. Move the modem to connected state using connect API & check Modem details in 
GUI
>Observation:- 
1. When Modem is in AP mode on observed Network Status as unknown

2. When Modem is in connected state able to see Network status as
Registered in GUI.

Expected result:- 
When Modem is in connected state should be able to see Network status as 
Connected in GUI.

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


** Tags: bot-comment
-- 
In GUI Network status is showing as Registered when modem is in connected State
https://bugs.launchpad.net/bugs/1992658
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to modemmanager 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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Nick Rosbrook

FWIW upstream systemd removed the MS_NOEXEC flag from /dev in
https://github.com/systemd/systemd/commit/4eb105fa4aae30566d23382e8c9430eddf1a3dd4.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-12 Thread Simon Déziel

I packaged the upstream fix (minus the changes to NEWS.md) and created
the debdiff attached.

** Description changed:

+ [Impact]
+ 
+ This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime 
as being "newer"
+ implying they would need to be transfered/sync'ed where in fact they are 
"uptodate".
+ 
+ This breaks users' scripts depending on "is newer" to signal that files need 
to be sync'ed
+ when in fact, they don't need to be.
+ 
+ [Test Plan]
+ 
+ Steps to reproduce:
+ 
+ 1. Create a local file:
+ $ touch foo
+ 
+ 2. Check if rsync would transfer it using the --update option:
+ $ rsync -avv --update foo .
+ 
+ 
+ If the regression is present, "foo is newer" would be reported:
+ 
+ ```
+ sending incremental file list
+ delta-transmission disabled for local transfer or --whole-file
+ foo is newer
+ total: matches=0  hash_hits=0  false_alarms=0 data=0
+ 
+ sent 61 bytes  received 96 bytes  314.00 bytes/sec
+ total size is 0  speedup is 0.00
+ ```
+ 
+ If the updated package is installed (from -proposed), "foo is uptodate"
+ should be reported:
+ 
+ ```
+ sending incremental file list
+ delta-transmission disabled for local transfer or --whole-file
+ foo is uptodate
+ total: matches=0  hash_hits=0  false_alarms=0 data=0
+ 
+ sent 60 bytes  received 106 bytes  332.00 bytes/sec
+ total size is 0  speedup is 0.00
+ ```
+ 
+ [Regression potential]
+ 
+ The patch changes the behavior of --update so if something goes wrong, it 
could break backup/sync
+ jobs. To mitiate that, manual testing of rsync with and without the --update 
option was done
+ in addition to the quick [Test Plan] outlined above.
+ 
+ Please note the patch restores the behavior from before version 3.2.3 and has 
been integrated by upstream
+ in September 2021. It also is in Kinetic where no visible regression was 
observed.
+ 
+ 
+ [Original description]
+ 
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98
  
  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  
  Obviously a file should not be listed as newer than itself.  Another
  way:
  
  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00
  
  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

** Patch added: "rsync_3.2.3-8ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Fix Released
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Triaged

Bug description:
  [Impact]

  This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime 
as being "newer"
  implying they would need to be transfered/sync'ed where in fact they are 
"uptodate".

  This breaks users' scripts depending on "is newer" to signal that files need 
to be sync'ed
  when in fact, they don't need to be.

  [Test Plan]

  Steps to reproduce:

  1. Create a local file:
  $ touch foo

  2. Check if rsync would transfer it using the --update option:
  $ rsync -avv --update foo .

  
  If the regression is present, "foo is newer"

[Touch-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-10-12 Thread Sebastian Heiden

Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.

It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Touch-packages] [Bug 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets

2022-10-12 Thread Lukas Märdian

Netplan does not support any pre/post-up/down hooks on its own, but is
referring to a mapping table from ifupdown to its two backend renderers
“NetworkManager-dispatcher” and “networkd-dispatcher”, which we are
currently updating to better explain the details, pitfalls and
differences: https://github.com/canonical/netplan.io/pull/245


It’s not a 1:1 mapping, as the three hook dispatchers behave slightly 
differently, especially wrt. Networkd-dispatcher being a pure listener, running 
hook scripts asynchronous, whereas ENI and NM handle the hook scripts natively 
and allow them to interject the interface configuration process.

Also, systemd-networkd does not keep an internal state (in contrast to
ENI & NM) but relies on the kernel’s netlink state, thus uses different
stages and cannot implement a “pre-down” hook at all.

Unfortunately, this is the best we can do for now, without requiring
upstream changes to systemd, inroducing a possibility to block network
configuration, controlled by external hooks, which the systemd devs want
to avoid, due to performance concerns.

** Changed in: netplan
   Status: New => Fix Committed

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

Title:
  Not possible to render pre-up, pre-down, post-up, or post-down
  snippets

Status in netplan:
  Fix Committed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Many configurations require scripts to run before or after an
  interface comes up or down.

  Example: I had a situation where I needed to render a post-up script
  to monitor an interface with ifupdown (and with the interface set to
  manual mode, because if the link was down I didn't want to require
  DHCP to run before the system continued booting). This is similar to
  what NetworkManager does in order to launch (or kill) a DHCP client.

  Other use cases involve setting up custom routes (such as when complex
  logic involving metrics or source routing is required) or anything
  else the designers of the netplan rendering engine didn't think of,
  such as invoking workarounds or special settings required for a
  particular NIC or environment, iptables rules that should be added or
  removed, etc.

  A follow-on issue is, it should be possible to ask that custom scripts
  run if the *link* is detected to come up or down. But I'll be happy if
  netplan first can simply replicate the custom-script-invoking behavior
  of ifupdown.

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


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

[Touch-packages] [Bug 1992656] [NEW] FFE: Mesa 22.2.1

2022-10-12 Thread Timo Aaltonen

Public bug reported:

This is a minor bugfix release, and also enables llvm for riscv64 (LP:
#1980386).

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

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

Title:
  FFE: Mesa 22.2.1

Status in mesa package in Ubuntu:
  New

Bug description:
  This is a minor bugfix release, and also enables llvm for riscv64 (LP:
  #1980386).

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


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

[Touch-packages] [Bug 1991492] Re: Upgrade to version 1.1.0

2022-10-12 Thread polina

thank you for adding it to the 23.04 release!
is there a way to make it installable via package managers on lower versions of 
Ubuntu (18 and 20)? would be super useful if you can provide it

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

Title:
  Upgrade to version 1.1.0

Status in libsndfile package in Ubuntu:
  Fix Committed

Bug description:
  Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding
  support. It would be great if the version here could be updated.

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


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

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-12 Thread sudodus

Another workaround might be to use Ubuntu's own compressed image with a
preinstalled Ubuntu Server (although not officially released) according
to the following link

https://ubuntuforums.org/showthread.php?t=2474692

Scroll down to read also the following posts, that describe how to
install Lubuntu. In the same way you can install Ubuntu Desktop as well
as all the community flavours.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.co

[Touch-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-10-12 Thread Timo Aaltonen

** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.0 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain

2022-10-12 Thread Louis Bouchard

Slightly modified debdiff which will only run the tests once.

** Patch removed: "iptables_1.8.7-1ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+attachment/5623037/+files/iptables_1.8.7-1ubuntu7.debdiff

** Patch removed: "iptables_1.8.7-1ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+attachment/5622997/+files/iptables_1.8.7-1ubuntu7.debdiff

** Patch added: "iptables_1.8.7-1ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+attachment/5623422/+files/iptables_1.8.7-1ubuntu7.debdiff

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

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


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

[Touch-packages] [Bug 1992206] Re: bash: non existent locale crashes bash

2022-10-12 Thread Bug Watch Updater

** Changed in: bash (Debian)
   Status: New => Confirmed

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

Title:
  bash: non existent locale crashes bash

Status in bash package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Committed
Status in bash package in Debian:
  Confirmed

Bug description:
  Imported from Debian bug http://bugs.debian.org/1021109:

  Package: libc6
  Version: 2.35-1
  Severity: grave
  Justification: renders package unusable
  X-Debbugs-Cc: kos...@debian.org

  Dear maintainer,

  After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
locale setting
  starts to crash the system.

  This is dangerous because a remote system might not always have the same 
locale installed.
  An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
  before attempting to ssh.

  Steps to reproduce:

  From a clean installed Debian sid, upgrade to libc6 2.35-1.
  Only install C locale and en_US.UTF-8.

  $ LC_ALL=ja_JP.UTF-8 bash
  bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
  Segmentation fault (core dumped)

  $ LC_ALL=ja_JP.UTF-8 gdb bash

  Fatal signal: Segmentation fault
  - Backtrace -
  0x55ed3e1e8dcf ???
  0x55ed3e2df312 ???
  0x55ed3e2df488 ???
  0x7f0b4a39ba9f ???
  0x7f0b4b412204 _rl_init_locale
  0x7f0b4b4122f1 _rl_init_eightbit
  0x7f0b4b3f10f2 rl_initialize
  ... snip ...

  Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
  state was invalidated when upgrading.

  Thanks,
  Kan-Ru

  
  -- System Information:
  Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages libc6 depends on:
  ii  libgcc-s1  12.2.0-3

  Versions of packages libc6 recommends:
  ii  libidn2-0  2.3.3-1+b1

  Versions of packages libc6 suggests:
  ii  debconf [debconf-2.0]  1.5.79
  pn  glibc-doc  
  ii  libc-l10n  2.35-1
  pn  libnss-nis 
  pn  libnss-nisplus 
  ii  locales2.35-1

  -- debconf information:
glibc/kernel-too-old:
glibc/restart-failed:
glibc/disable-screensaver:
glibc/upgrade: true
  * libraries/restart-without-asking: false
  * glibc/restart-services: cron
glibc/kernel-not-supported:

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


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

[Touch-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

2022-10-12 Thread Julian Andres Klode

It does yeah, and obviously that's a solver bug that's going to need
some more work to root cause.


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

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

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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


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

[Touch-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

2022-10-12 Thread Lukas Märdian

Does this also happen when you use the more recent version 2.4.8 from
the jammy-updates pocket?

** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: foundations-triage-discuss

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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


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

[Touch-packages] [Bug 1992472] Re: APT hooks do not respect the -q option

2022-10-12 Thread Lukas Märdian

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

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

** Tags added: foundations-triage-discuss

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

Title:
  APT hooks do not respect the -q option

Status in apt package in Ubuntu:
  Triaged

Bug description:
  ubuntu-advantage-tools recently used an APT Cli hook
  (AptCli::Hooks::Upgrade) to add a message to the output. We were asked
  in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1992026/comments/9 to honor the -q (-qq, -qqq) option of
  APT upgrade, and hide the output.

  However, the hook does not expose this option, so there is nothing we
  can do from our side.

  APT could either treat those messages based on the "quietness" defined
  when running the command, or expose the flag somehow so we could
  configure our message to respect it.

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


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

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Dimitri John Ledkov

./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev

when booting containers

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

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Dimitri John Ledkov

./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev

when booting containers

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Lukas Märdian

Setting the systemd bug task to "Invalid", as this is being handled in
the kernel.

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

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

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

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Touch-packages] [Bug 1991829] Re: machinectl read-only does not work

2022-10-12 Thread Lukas Märdian

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

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

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

Title:
  machinectl read-only does not work

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  [impact]

  machinectl read-only does not work

  [test case]

  On a system where the systemd machines dir is *not* on a btrfs volume
  (e.g. it's on a normal ext4 fs), create an image 'test' and then:

  $ sudo machinectl image-status test
  test
  Type: directory
  Path: /var/lib/machines/test
  Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
   Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

  $ sudo machinectl read-only test
  Could not mark image read-only: Access denied

  [regression potential]

  failure marking images ro or rw

  [scope]

  this is needed in all releases that include machinectl

  this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

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


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

[Touch-packages] [Bug 1811937] Re: shows network profiles on wrong device

2022-10-12 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: Unknown => 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/1811937

Title:
  shows network profiles on wrong device

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I have two network ports (ens 34 and ens 37) I'm able to create per
  port its own named profile where it is defined if this used profile
  should use DHCP, use manual DNS and others.

  But if I connect my android Smartphone with USB tethering all named
  Profiles are showing below the new network Port (USB Ethernet) and not
  any more below their defined port. (visual error only) That should
  only happened if a profile is not active but in this case I would
  prefer a separate profile menu where I could choose one and add to a
  specific port.

  Sometimes the network manager entry in the menu also shows confusing
  or empty entries. See print screen attached

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


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

[Touch-packages] [Bug 1811937] Re: shows network profiles on wrong device

2022-10-12 Thread Sebastien Bacher

the fix landed upstream now in https://gitlab.gnome.org/GNOME/gnome-
control-center/-/commit/118de73b

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #353
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/353

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/353
   Importance: Unknown
   Status: Unknown

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

Title:
  shows network profiles on wrong device

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I have two network ports (ens 34 and ens 37) I'm able to create per
  port its own named profile where it is defined if this used profile
  should use DHCP, use manual DNS and others.

  But if I connect my android Smartphone with USB tethering all named
  Profiles are showing below the new network Port (USB Ethernet) and not
  any more below their defined port. (visual error only) That should
  only happened if a profile is not active but in this case I would
  prefer a separate profile menu where I could choose one and add to a
  specific port.

  Sometimes the network manager entry in the menu also shows confusing
  or empty entries. See print screen attached

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


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

[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

2022-10-12 Thread Lukas Märdian

** Tags added: foundations-triage-discuss

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

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

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

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


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

[Touch-packages] [Bug 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"

2022-10-12 Thread Lukas Märdian

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

** Changed in: zram-config (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: zram-config (Ubuntu Jammy)
   Importance: Undecided => Low

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

Title:
  systemd-oomd and zram-config services: "Swap is currently not
  detected; memory pressure usage will be degraded"

Status in systemd package in Ubuntu:
  Invalid
Status in zram-config package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Invalid
Status in zram-config source package in Jammy:
  Triaged

Bug description:
  Problem summary:
  
  I've installed the zram-config package. By default it creates a zram swap 
device with half the physical memory size of the system. For instance, in an 
8GB RAM system:

  # swapon
  NAME   TYPE  SIZE USED PRIO
  /dev/zram0 partition 3,8G   1M5

  #zramctl
  NAME   ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
  /dev/zram0 lzo-rle   3,8G  496K 74,9K  376K   4 [SWAP]

  The problem is that when systemd-oomd.service is started during boot
  it doesn't detect that zram swap device because zram-config.service is
  started later. So when systemd-oomd.service was started the zram
  device didn't exists yet. This is the message shown during boot:

  systemd-oomd[587]: Swap is currently not detected; memory pressure
  usage will be degraded

  If you restart systemd-oomd.service after boot it's correctly started
  because zram-config.service was previously loaded and zram device
  exists. So I think it's just a matter of dependencies during boot
  process; it's necessary to make zram-config.service be started before
  systemd-oomd.service (or to make systemd-oomd.service be restarted
  when zram-config.service is started).

  Aditional info:
  ---
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy systemd-oomd
  systemd-oomd:
Instalados: 249.11-0ubuntu3.1
Candidato:  249.11-0ubuntu3.1
Tabla de versión:
   *** 249.11-0ubuntu3.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  # apt-cache policy zram-config
  zram-config:
Instalados: 0.7build1
Candidato:  0.7build1
Tabla de versión:
   *** 0.7build1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
  100 /var/lib/dpkg/status

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


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

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-12 Thread Lukas Märdian

This needs an SRU for Jammy, patch is available here:
https://github.com/WayneD/rsync/commit/fd6839b7464f53afb4cf016e4b4f6d2c477eb8d8
(context: https://github.com/WayneD/rsync/issues/98)

I marked it "Fix Released" for the development release, according to
comment #7 and added a bug task for the Jammy SRU.

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

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

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

** Changed in: rsync (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Fix Released
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Triaged

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.

  Obviously a file should not be listed as newer than itself.  Another
  way:

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

2022-10-12 Thread Gijs Peskens

Also affects Jammy. Unfortunately my work around script doesn't work
anymore due to the Audio plumbing having been changed.

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults

2022-10-12 Thread Lukas Märdian

Could somebody confirm if this issue is still happening with omshell
v4.4.3 from the Ubuntu Kinetic package?

I wonder if this is a problem with the build environment (LTO, etc...),
the Debian/Ubuntu distro patches, or if it was fixed upstream in between
4.4.1->4.4.3?

** Changed in: isc-dhcp (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  Incomplete

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
  works reliably.  (They are using the same python script to drive
  omshell.)  The DHCP server on the new system appears to be working 
  just fine as reported by omshell on the peer and systemctl.

  I was curious if the problem could be with the mis-matched versions
  of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system
  and get the same results.

  I also tried using a python script with the pypureomapi module to
  try and determine if the problem was in omshell or the server.  I 
  got very similar results when I attempted to get information about
  the failover state of the server.  Interestingly interrogating
  the server about host information seems to work just fine.

  This is a critical bug since I don't see how to fail over a DHCP
  that is running the isc-dhcp-server on 20.04 without being able
  to issue omapi commands.

  I am attaching apport output to this bug report.

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


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

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

2022-10-12 Thread Lukas Märdian

** Tags added: foundations-triage-discuss

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Triaged

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

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


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

[Touch-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

2022-10-12 Thread Gijs Peskens

Also affects Jammy. Unfortunately my work around script doesn't work
anymore due to the Audio plumbing having been changed.

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 1992580] ProcCpuinfoMinimal.txt

2022-10-12 Thread Gijs Peskens

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1992580/+attachment/5623383/+files/ProcCpuinfoMinimal.txt

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1992580] ProcEnviron.txt

2022-10-12 Thread Gijs Peskens

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1992580/+attachment/5623384/+files/ProcEnviron.txt

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

The card initializes properly on linux-image-
unsigned-6.0.0-06-generic


** Attachment added: "Good boot with kernel 6.0"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992580/+attachment/5623380/+files/i915_good_kernel_6.0

** Tags added: apport-collected kinetic wayland-session

** Description changed:

  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2020-12-06 (674 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Package: linux
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
+ Tags:  wayland-session kinetic
+ Uname: Linux 5.19.0-19-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
+ _MarkForUpload: True

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1992580] Dependencies.txt

2022-10-12 Thread Gijs Peskens

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1992580/+attachment/5623382/+files/Dependencies.txt

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1823985] Re: isc-dhcp-server can't load leases file with apparmor enabled

2022-10-12 Thread Lukas Märdian

Does it work if the profile is modified to use the dac_override
capability? As suggested by @sarnold in comment #1


** Changed in: isc-dhcp (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Low

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

Title:
  isc-dhcp-server can't load leases file with apparmor enabled

Status in isc-dhcp package in Ubuntu:
  Incomplete

Bug description:
  I can't start isc-dhcp-server with apparmor enabled.

  I set a custom leases file in the dhcpd.conf:
   lease-file-name "/test/var/lib/dhcp/dhcpd.leases";

  and created a custom apparmor profile for that in 
/etc/apparmor.d/local/usr.sbin.dhcpd:
  /test/var/lib/dhcp/dhcpd{,6}.leases* lrw,

  But when I try to start I see the following errors from dhcpd:

  Internet Systems Consortium DHCP Server 4.3.5
  Copyright 2004-2016 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  Config file: /etc/dhcp/dhcpd.conf
  Database file: /test/var/lib/dhcp/dhcpd.leases
  PID file: /run/dhcp-server/dhcpd.pid
  Can't open /test/var/lib/dhcp/dhcpd.leases for append.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.

  
  And in the messages log I can see errors like this:

  Apr  9 17:07:03.601 myhost dhcpd[27361]: Can't open 
/test/var/lib/dhcp/dhcpd.leases for append.
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: If you think you have received this 
message due to a bug rather
  Apr  9 17:07:03.601 myhost dhcpd[27361]: than a configuration issue please 
read the section on submitting
  Apr  9 17:07:03.601 myhost dhcpd[27361]: bugs on either our web page at 
www.isc.org or in the README file
  Apr  9 17:07:03.601 myhost dhcpd[27361]: before submitting a bug.  These 
pages explain the proper
  Apr  9 17:07:03.601 myhost dhcpd[27361]: process and the information we find 
helpful for debugging..
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: exiting.
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"



  After disabling apparmor for dhcpd everything works as expected:

  ln -s /etc/apparmor.d/usr.sbin.dhcpd /etc/apparmor.d/disable/
  apparmor_parser -R /etc/apparmor.d/usr.sbin.dhcpd

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


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

[Touch-packages] [Bug 1992580] Missing required logs.

2022-10-12 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1992580

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

** Attachment added: "lspci gpu's"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+attachment/5623378/+files/lspci_gpu

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

Sigh. It somehow incorrectly selected initramfs-tools. That's totally
unrelated. No idea on how to remove it.

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1992563] Re: Boot freeze

2022-10-12 Thread Daniel van Vugt

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

Looks like bug 1973098 is the same.

** Tags added: hybrid i915 multigpu nvidia

** Tags added: regression-update

** Summary changed:

- Boot freeze
+ Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon - 
[drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

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

** This bug has been marked a duplicate of bug 1973098
   Intermittent freezing and LSPCON init failed kernel messages

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

Title:
  Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  - [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

Status in linux package in Ubuntu:
  New

Bug description:
  After recent update during boot Ubuntu freezes or I should wait a
  couple of minutes before gui starts.

  Laptop is Ubuntu certified (Thinkpad 17p gen1)

  Dmesg shows the following errors:
   [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 09:37:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
   nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
  InstallationDate: Installed on 2020-11-20 (690 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20SN002WRT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SN002WRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SN002WRT
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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/ubunt

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

** Attachment added: "dmsg full"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+attachment/5623376/+files/dmesg_full

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

** Attachment added: "dmsg i915"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+attachment/5623375/+files/i915_bad

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1992580] Re: i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

** Attachment added: "lspci full"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+attachment/5623377/+files/lspci_full

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1992580] [NEW] i915 DG1 fails to load

2022-10-12 Thread Gijs Peskens

Public bug reported:

On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

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


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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2022-10-12 Thread Lukas Märdian

The KeepConfiguration= setting is part of systemd nowadays, so I'm
closing the systemd component.

Netplan does not currently make use of "KeepConfiguration=" [0] though.
Marcin, could you try to place a systemd-networkd override file, e.g. in
/etc/systemd/network/10-netplan-eth0.network.d/override.conf (depending
on your interface name), that contains a corresponding KeepConfiguration
setting and check if that makes any difference?

[0]
https://www.freedesktop.org/software/systemd/man/systemd.network.html#KeepConfiguration=

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

** Changed in: netplan
   Status: Fix Released => Incomplete

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

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Incomplete
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs

[Touch-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

2022-10-12 Thread Timo Aaltonen

llvm-toolchain-15 has JIT

** Package changed: llvm-toolchain-14 (Ubuntu Kinetic) => llvm-
toolchain-15 (Ubuntu Kinetic)

** Changed in: llvm-toolchain-15 (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 source package in Jammy:
  New
Status in mesa source package in Jammy:
  Confirmed
Status in llvm-toolchain-15 source package in Kinetic:
  Fix Released
Status in mesa source package in Kinetic:
  Confirmed

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+subscriptions


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

[Touch-packages] [Bug 1992563] Re: Boot freeze

2022-10-12 Thread 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/1992563

Title:
  Boot freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After recent update during boot Ubuntu freezes or I should wait a
  couple of minutes before gui starts.

  Laptop is Ubuntu certified (Thinkpad 17p gen1)

  Dmesg shows the following errors:
   [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 09:37:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
   nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
  InstallationDate: Installed on 2020-11-20 (690 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20SN002WRT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SN002WRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SN002WRT
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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/1992563/+subscriptions


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

[Touch-packages] [Bug 1283309] Re: bash built-in read timeout (-t) doesn't work

2022-10-12 Thread Lukas Märdian

I cannot seem to reproduce this issue on Jammy bash 5.1-6ubuntu1:
```
$ time read -t 2 test

real0m2,000s
user0m0,000s
sys 0m0,000s
$
```

@crtiger Could you please describe your "changing the system clock and
wait for ntp run" reproducer in more detail?

** Changed in: bash (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

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


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

[Touch-packages] [Bug 1992563] [NEW] Boot freeze

2022-10-12 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

After recent update during boot Ubuntu freezes or I should wait a couple
of minutes before gui starts.

Laptop is Ubuntu certified (Thinkpad 17p gen1)

Dmesg shows the following errors:
 [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 12 09:37:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
 nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
InstallationDate: Installed on 2020-11-20 (690 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20SN002WRT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.26
dmi.bios.vendor: LENOVO
dmi.bios.version: N30ET43W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20SN002WRT
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
dmi.product.family: ThinkPad P17 Gen 1
dmi.product.name: 20SN002WRT
dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
dmi.product.version: ThinkPad P17 Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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 freeze jammy ubuntu
-- 
Boot freeze
https://bugs.launchpad.net/bugs/1992563
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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

2022-10-12 Thread Daniel van Vugt

** No longer affects: gstreamer-vaapi (Ubuntu)

** No longer affects: gstreamer1.0 (Ubuntu)

** No longer affects: libx11 (Ubuntu)

** No longer affects: libxcb (Ubuntu)

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

80 matches

Mail list logo