[Touch-packages] [Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

[Ian Mackenzie]

After kernel + x.org updates this week, firefox is now displaying
properly using xserver-xorg on the Athlon 200GE.

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  

[Touch-packages] [Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

[Ian Mackenzie]

Similar hardware:

R7 240 graphics card (previous generation graphics cores) on Athlon
200GE: everything works fine on X11

Plugged SSD from Athlon install into 5600G (Vega 6 graphics instead of
Vega 3): everything works fine on X11.

So it seems to be something weird about Vega 3 graphics in relation to
amdgpu & xserver-xorg-video-amdgpu.

I don't speak Git, but I am happy to download, compile, and test
anything you would like me to if you don't have access to matching
hardware.

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: 

[Touch-packages] [Bug 2055351] xdpyinfo.txt

[Ian Mackenzie]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753661/+files/xdpyinfo.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] Xrandr.txt

[Ian Mackenzie]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/2055351/+attachment/5753659/+files/Xrandr.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] XorgLogOld.txt

[Ian Mackenzie]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753658/+files/XorgLogOld.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] acpidump.txt

[Ian Mackenzie]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753660/+files/acpidump.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

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

[Ian Mackenzie]

apport information

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

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

[Touch-packages] [Bug 2055351] ProcInterrupts.txt

[Ian Mackenzie]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753653/+files/ProcInterrupts.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev 

[Touch-packages] [Bug 2055351] XorgLog.txt

[Ian Mackenzie]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753657/+files/XorgLog.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] DpkgLog.txt

[Ian Mackenzie]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753644/+files/DpkgLog.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] Lspci-vt.txt

[Ian Mackenzie]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753646/+files/Lspci-vt.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] UdevDb.txt

[Ian Mackenzie]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2055351/+attachment/5753655/+files/UdevDb.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] ProcModules.txt

[Ian Mackenzie]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753654/+files/ProcModules.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

[Ian Mackenzie]

apport information

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

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev 

[Touch-packages] [Bug 2055351] ProcCpuinfo.txt

[Ian Mackenzie]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753650/+files/ProcCpuinfo.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

[Touch-packages] [Bug 2055351] Lsusb-t.txt

[Ian Mackenzie]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753648/+files/Lsusb-t.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] Lsusb.txt

[Ian Mackenzie]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2055351/+attachment/5753647/+files/Lsusb.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] Lsusb-v.txt

[Ian Mackenzie]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753649/+files/Lsusb-v.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] Lspci.txt

[Ian Mackenzie]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2055351/+attachment/5753645/+files/Lspci.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  

[Touch-packages] [Bug 2055351] CurrentDmesg.txt

[Ian Mackenzie]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753642/+files/CurrentDmesg.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 

[Touch-packages] [Bug 2055351] Dependencies.txt

[Ian Mackenzie]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2055351/+attachment/5753643/+files/Dependencies.txt

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 

[Touch-packages] [Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

[Ian Mackenzie]

It is similar but not identical.

I just updated Snap, Firefox, and Chromium, and, currently, Firefox with
hardware acceleration works fine using wayland, but not X11. Firefox
without hardware acceleration works on either.

I am attaching a screenshot of unaccelerated Firefox beside (corrupted)
accelerated Chromium on X11.

I will do another apport-collect 2055351 as the versions have changed.

** Attachment added: "Unaccelerated Firefox beside accelerated Chromium on 
X11.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2055351/+attachment/5753641/+files/Unaccelerated%20Firefox%20beside%20accelerated%20Chromium%20on%20X11.jpg

** Description changed:

  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)
  
  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.
  
  I think this is an xorg bug, because when I installed Wayland and logged
  in with a Wayland session, the browsers displayed correctly.
  
  Same behaviour with an Athlon 220GE.
  
  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  

[Touch-packages] [Bug 2055351] Re: firefox screen corruption on Athlon 200GE after fresh installation of 22.04.4

[Ian Mackenzie]

Verified that the package was called xorg and not X11

** 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/2055351

Title:
  firefox screen corruption on Athlon 200GE after fresh installation of
  22.04.4

Status in xorg package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be
  xorg vs Wayland that was the critical difference.

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


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

[Touch-packages] [Bug 2052648] [NEW] After a long work on debugging GDB crashed with segmentation fault

[Ian Ilyasov]

Public bug reported:

I've been debugging PostgreSQL REL_14_STABLE branch authentication code
starting the postgres postmaster, running psql and then connecting to a
new process using `sudo gdb -p `. After a long day of it, I met
this segmentation fault. This message says, that it is definitely a bug
and I should report it, but GDB site says, that probably I should
firstly message it to the distributor, which for my laptop(x86_64) OS
Ubuntu 22.04 is Ubuntu.

```
Fatal signal: Segmentation fault
- Backtrace -
0x556f0077 ???
0x557f2859 ???
0x557f2a22 ???
0x76c4251f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x76db1ebc ???
../sysdeps/x86_64/multiarch/strlen-evex.S:77
0x559b1671 ???
0x559b1ba4 ???
0x559b208f ???
0x559b2b89 ???
0x559c1381 ???
0x559c14be ???
0x5585b7f6 ???
0x55a387a8 ???
0x5585ea1e ???
0x5584e171 ???
0x55851308 ???
0x55845b64 ???
0x5586b9d4 ???
0x55ba4815 ???
0x55ba4cf9 ???
0x55a1aaab ???
0x558afa00 ???
0x558b1a16 ???
0x558b204e ???
0x5564815f ???
0x76c29d8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x76c29e3f __libc_start_main_impl
../csu/libc-start.c:392
0x5564dbf4 ???
0x ???
-

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

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

The only way I could reproduce this bug is to reboot and do debug using
gdb all day like I described in the begging of the message.

Sorry, if I provided little info.

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

** Attachment added: "Error message from GDB"
   
https://bugs.launchpad.net/bugs/2052648/+attachment/5745088/+files/gdb-segfault.txt

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

Title:
  After a long work on debugging GDB crashed with segmentation fault

Status in gdb package in Ubuntu:
  New

Bug description:
  I've been debugging PostgreSQL REL_14_STABLE branch authentication
  code starting the postgres postmaster, running psql and then
  connecting to a new process using `sudo gdb -p `. After a long
  day of it, I met this segmentation fault. This message says, that it
  is definitely a bug and I should report it, but GDB site says, that
  probably I should firstly message it to the distributor, which for my
  laptop(x86_64) OS Ubuntu 22.04 is Ubuntu.

  ```
  Fatal signal: Segmentation fault
  - Backtrace -
  0x556f0077 ???
  0x557f2859 ???
  0x557f2a22 ???
  0x76c4251f ???
  ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
  0x76db1ebc ???
  ../sysdeps/x86_64/multiarch/strlen-evex.S:77
  0x559b1671 ???
  0x559b1ba4 ???
  0x559b208f ???
  0x559b2b89 ???
  0x559c1381 ???
  0x559c14be ???
  0x5585b7f6 ???
  0x55a387a8 ???
  0x5585ea1e ???
  0x5584e171 ???
  0x55851308 ???
  0x55845b64 ???
  0x5586b9d4 ???
  0x55ba4815 ???
  0x55ba4cf9 ???
  0x55a1aaab ???
  0x558afa00 ???
  0x558b1a16 ???
  0x558b204e ???
  0x5564815f ???
  0x76c29d8f __libc_start_call_main
  ../sysdeps/nptl/libc_start_call_main.h:58
  0x76c29e3f __libc_start_main_impl
  ../csu/libc-start.c:392
  0x5564dbf4 ???
  0x ???
  -

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

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

  The only way I could reproduce this bug is to reboot and do debug
  using gdb all day like I described in the begging of the message.

  Sorry, if I provided little info.

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


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

[Touch-packages] [Bug 1615641] Re: initramfs waits for 5 seconds when executing /scripts/local-premount/resume

[Colin Ian King]

We may as well close this issue, I don't have that laptop any more, I
don't work for Canonical any more and the boot speed regressions seem to
have fallen off the CTO's "must do priority radar" otherwise this kind
of regression would have had more engineering time devoted to 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/1615641

Title:
  initramfs waits for 5 seconds when executing /scripts/local-
  premount/resume

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I've noticed that boots on Ubuntu Yakkety have slowed down recently.
  I added some debug into my kernel to see where delays are occurring
  and I can observe 5 seconds being consumed in  /scripts/local-
  premount/resume :

  Aug 22 14:34:36 lenovo kernel: [6.823263] _do_fork: 1 (init)
  Aug 22 14:34:36 lenovo kernel: [6.82] do_exec: 824 (init) 
/scripts/local-premount/ntfs_3g
  Aug 22 14:34:36 lenovo kernel: [6.823766] _do_fork: 1 (init)
  Aug 22 14:34:36 lenovo kernel: [6.823845] do_exec: 825 (init) 
/scripts/local-premount/resume
  Aug 22 14:34:36 lenovo kernel: [6.824214] _do_fork: 825 (resume)
  Aug 22 14:34:36 lenovo kernel: [6.824322] do_exec: 826 (resume) 
/sbin/wait-for-root
  Aug 22 14:34:36 lenovo kernel: [   11.825642] _do_fork: 1 (init)
  Aug 22 14:34:36 lenovo kernel: [   11.825800] do_exec: 827 (init) 
/sbin/wait-for-root
  Aug 22 14:34:36 lenovo kernel: [   11.826691] _do_fork: 1 (init)

  It seems that /scripts/local-premount/resume is being called and wait-
  for-root times out after 5 seconds. The resume script does set a 5
  second timeout, so I must be hitting that for some reason.

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


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

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Ian Russel Adem]

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/2031352

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

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


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

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Colin Ian King]

Thanks JJ, much appreciated :-)

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  New
Status in linux source package in Lunar:
  New
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

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


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

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Colin Ian King]

And also occurs in Ubuntu Mantic with 6.3.0-7-generic

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  New
Status in linux source package in Lunar:
  New
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

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


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

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Colin Ian King]

5.15.0.75 works fine, no problem, 5.19.0-45 kernel crashes, so issue
introduced between 5.15 and 5.19

** Also affects: apparmor (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: apparmor (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Also affects: apparmor (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Low
   Status: Incomplete

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  New
Status in linux source package in Lunar:
  New
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

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


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

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Colin Ian King]

And with 5.19.0-45-generic:

sudo ./stress-ng --apparmor 1 --klog-check
[sudo] password for cking: 
stress-ng: info:  [1179] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
stress-ng: info:  [1179] dispatching hogs: 1 apparmor
stress-ng: info:  [1180] klog-check: kernel cmdline: 
'BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 
ro'
stress-ng: error: [1180] klog-check: error: [93.527396] 'AppArmor DFA 
next/check upper bounds error'
stress-ng: error: [1180] klog-check: error: [93.827976] 'AppArmor DFA state 
with invalid match flags'
stress-ng: error: [1180] klog-check: error: [93.991395] 'AppArmor DFA 
next/check upper bounds error'
stress-ng: error: [1180] klog-check: error: [93.992189] 'AppArmor DFA 
next/check upper bounds error'
stress-ng: error: [1180] klog-check: error: [94.007400] 'AppArmor DFA state 
with invalid match flags'
stress-ng: error: [1180] klog-check: error: [94.059345] 'AppArmor DFA state 
with invalid match flags'
stress-ng: error: [1180] klog-check: error: [94.104414] 'AppArmor DFA 
next/check upper bounds error'
stress-ng: error: [1180] klog-check: alert: [94.128617] 'BUG: kernel NULL 
pointer dereference, address: 0130'
stress-ng: error: [1180] klog-check: alert: [94.128644] '#PF: supervisor read 
access in kernel mode'
stress-ng: error: [1180] klog-check: alert: [94.128659] '#PF: 
error_code(0x) - not-present page'
stress-ng: info:  [1180] klog-check: warning: [94.128685] 'Oops:  [#1] 
PREEMPT SMP PTI'
stress-ng: info:  [1180] klog-check: warning: [94.128698] 'CPU: 7 PID: 1185 
Comm: stress-ng-appar Not tainted 5.19.0-45-generic #46-Ubuntu'
stress-ng: info:  [1180] klog-check: warning: [94.128722] 'Hardware name: QEMU 
Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-5 04/01/2014'
stress-ng: info:  [1180] klog-check: warning: [94.128745] 'RIP: 
0010:aa_unpack+0x11f/0x530'
stress-ng: info:  [1180] klog-check: warning: [94.128762] 'Code: 00 48 85 c0 0f 
84 15 04 00 00 48 8d 75 a8 48 8d 7d b0 4c 8b 7d c0 e8 80 ec ff ff 48 89 c3 48 
3d 00 f0 ff ff 0f 87 00 02 00 00 <4c> 8b b0 30 01 00 00 4d 85 f6 0f 84 38 01 00 
00 49 8b 86 c8 00 00'
stress-ng: info:  [1180] klog-check: warning: [94.128807] 'RSP: 
0018:b1fdc0f57ce0 EFLAGS: 00010207'
stress-ng: info:  [1180] klog-check: warning: [94.129378] 'RAX: 
 RBX:  RCX: '
stress-ng: info:  [1180] klog-check: warning: [94.129928] 'RDX: 
 RSI:  RDI: '
stress-ng: info:  [1180] klog-check: warning: [94.130443] 'RBP: 
b1fdc0f57d40 R08:  R09: '
stress-ng: info:  [1180] klog-check: warning: [94.131056] 'R10: 
 R11:  R12: b1fdc0f57da8'
stress-ng: info:  [1180] klog-check: warning: [94.131572] 'R13: 
b1fdc0f57da0 R14: 9da384835962 R15: 9da384820010'
stress-ng: info:  [1180] klog-check: warning: [94.132090] 'FS:  
7fa65a059740() GS:9da3fbdc() knlGS:'
stress-ng: info:  [1180] klog-check: warning: [94.132652] 'CS:  0010 DS:  
ES:  CR0: 80050033'
stress-ng: info:  [1180] klog-check: warning: [94.133206] 'CR2: 
0130 CR3: 00010d432006 CR4: 00370ee0'
stress-ng: info:  [1180] klog-check: warning: [94.133739] 'DR0: 
 DR1:  DR2: '
stress-ng: info:  [1180] klog-check: warning: [94.134282] 'DR3: 
 DR6: fffe0ff0 DR7: 0400'
stress-ng: info:  [1180] klog-check: warning: [94.134868] 'Call Trace:'
stress-ng: info:  [1180] klog-check: warning: [94.135388] ' '
stress-ng: info:  [1180] klog-check: warning: [94.135933] ' 
aa_replace_profiles+0xa1/0x10b0'
stress-ng: info:  [1180] klog-check: warning: [94.136471] ' ? 
check_heap_object+0x29/0x1e0'
stress-ng: info:  [1180] klog-check: warning: [94.137018] ' ? 
__check_object_size.part.0+0x4c/0xf0'
stress-ng: info:  [1180] klog-check: warning: [94.137528] ' 
policy_update+0xd0/0x170'
stress-ng: info:  [1180] klog-check: warning: [94.138061] ' 
profile_replace+0xb9/0x150'
stress-ng: info:  [1180] klog-check: warning: [94.138612] ' 
vfs_write+0xb7/0x290'
stress-ng: info:  [1180] klog-check: warning: [94.139124] ' 
ksys_write+0x73/0x100'
stress-ng: info:  [1180] klog-check: warning: [94.139616] ' 
__x64_sys_write+0x19/0x30'
stress-ng: info:  [1180] klog-check: warning: [94.140104] ' 
do_syscall_64+0x58/0x90'
stress-ng: info:  [1180] klog-check: warning: [94.140651] ' ? 
syscall_exit_to_user_mode+0x29/0x50'
stress-ng: info:  [1180] klog-check: warning: [94.141130] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1180] klog-check: warning: [94.141630] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1180] klog-check: warning: [94.142117] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1180] klog-check: warning: [94.142627] ' 
entry_SYSCALL_64_after_hwframe+0x63/0xcd'
stress-ng: info:  [1180] klog-check: warning: 

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Colin Ian King]

On 6.2.0-21-generic I also get:

sudo ./stress-ng --apparmor 1 --klog-check

stress-ng: error: [1083] klog-check: alert: [66.442338] 'BUG: kernel NULL 
pointer dereference, address: 0030'
stress-ng: error: [1083] klog-check: alert: [66.442538] '#PF: supervisor read 
access in kernel mode'
stress-ng: error: [1083] klog-check: alert: [66.442718] '#PF: 
error_code(0x) - not-present page'
stress-ng: info:  [1083] klog-check: warning: [66.443080] 'Oops:  [#1] 
PREEMPT SMP PTI'
stress-ng: info:  [1083] klog-check: warning: [66.443256] 'CPU: 3 PID: 1088 
Comm: stress-ng-appar Not tainted 6.2.0-21-generic #21-Ubuntu'
stress-ng: info:  [1083] klog-check: warning: [66.443438] 'Hardware name: QEMU 
Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-5 04/01/2014'
stress-ng: info:  [1083] klog-check: warning: [66.443628] 'RIP: 
0010:aafs_create.constprop.0+0x7f/0x130'
stress-ng: info:  [1083] klog-check: warning: [66.443819] 'Code: 4c 63 e0 48 83 
c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 
45 31 c9 45 31 d2 c3 cc cc cc cc <4d> 8b 55 30 4d 8d ba a0 00 00 00 4c 89 55 c0 
4c 89 ff e8 8a 59 a1'
stress-ng: info:  [1083] klog-check: warning: [66.444227] 'RSP: 
0018:beb940907bd8 EFLAGS: 00010246'
stress-ng: info:  [1083] klog-check: warning: [66.33] 'RAX: 
 RBX: 41ed RCX: '
stress-ng: info:  [1083] klog-check: warning: [66.444646] 'RDX: 
 RSI:  RDI: '
stress-ng: info:  [1083] klog-check: warning: [66.444862] 'RBP: 
beb940907c18 R08:  R09: '
stress-ng: info:  [1083] klog-check: warning: [66.445074] 'R10: 
 R11:  R12: 93db8b18'
stress-ng: info:  [1083] klog-check: warning: [66.445291] 'R13: 
 R14:  R15: '
stress-ng: info:  [1083] klog-check: warning: [66.445503] 'FS:  
7f60f5c07740() GS:9578bbcc() knlGS:'
stress-ng: info:  [1083] klog-check: warning: [66.445721] 'CS:  0010 DS:  
ES:  CR0: 80050033'
stress-ng: info:  [1083] klog-check: warning: [66.445939] 'CR2: 
0030 CR3: 000124ffa004 CR4: 00370ee0'
stress-ng: info:  [1083] klog-check: warning: [66.446163] 'DR0: 
 DR1:  DR2: '
stress-ng: info:  [1083] klog-check: warning: [66.446387] 'DR3: 
 DR6: fffe0ff0 DR7: 0400'
stress-ng: info:  [1083] klog-check: warning: [66.446608] 'Call Trace:'
stress-ng: info:  [1083] klog-check: warning: [66.446829] ' '
stress-ng: info:  [1083] klog-check: warning: [66.447059] ' 
__aafs_profile_mkdir+0x3d6/0x480'
stress-ng: info:  [1083] klog-check: warning: [66.447290] ' 
aa_replace_profiles+0x862/0x1270'
stress-ng: info:  [1083] klog-check: warning: [66.447518] ' 
policy_update+0xe0/0x180'
stress-ng: info:  [1083] klog-check: warning: [66.447750] ' 
profile_replace+0xb9/0x150'
stress-ng: info:  [1083] klog-check: warning: [66.447981] ' 
vfs_write+0xc8/0x410'
stress-ng: info:  [1083] klog-check: warning: [66.448213] ' ? 
kmem_cache_free+0x1e/0x3b0'
stress-ng: info:  [1083] klog-check: warning: [66.448442] ' 
ksys_write+0x73/0x100'
stress-ng: info:  [1083] klog-check: warning: [66.448670] ' 
__x64_sys_write+0x19/0x30'
stress-ng: info:  [1083] klog-check: warning: [66.448892] ' 
do_syscall_64+0x58/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.449115] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.449337] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.449551] ' ? 
exit_to_user_mode_loop+0xe0/0x130'
stress-ng: info:  [1083] klog-check: warning: [66.449775] ' ? 
exit_to_user_mode_prepare+0x30/0xb0'
stress-ng: info:  [1083] klog-check: warning: [66.449996] ' ? 
syscall_exit_to_user_mode+0x29/0x50'
stress-ng: info:  [1083] klog-check: warning: [66.450220] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.450449] ' ? 
exit_to_user_mode_prepare+0x30/0xb0'
stress-ng: info:  [1083] klog-check: warning: [66.450681] ' ? 
syscall_exit_to_user_mode+0x29/0x50'
stress-ng: info:  [1083] klog-check: warning: [66.450915] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.451151] ' ? 
do_syscall_64+0x67/0x90'
stress-ng: info:  [1083] klog-check: warning: [66.451384] ' 
entry_SYSCALL_64_after_hwframe+0x72/0xdc'
stress-ng: info:  [1083] klog-check: warning: [66.451614] 'RIP: 
0033:0x7f60f5b0b9e4'
stress-ng: info:  [1083] klog-check: warning: [66.451848] 'Code: 15 39 a4 0e 00 
f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 80 3d fd 2b 0f 
00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 
28 48 89 54 24 18 48'
stress-ng: info:  [1083] klog-check: warning: [66.452341] 'RSP: 
002b:7ffdaa28bfb8 EFLAGS: 0202 ORIG_RAX: 0001'
stress-ng: info: 

[Touch-packages] [Bug 2024872] [NEW] package cups 2.4.1op1-1ubuntu4.4 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1

[Ian]

Public bug reported:

Just saw the bug notification, not sure how it happened.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.4
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 ieee-data:amd64: Install
 arp-scan:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog:
 W [22/Jun/2023:18:04:33 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-Gray..\' already exists
 W [22/Jun/2023:18:04:33 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-DeviceN..\' already exists
 W [22/Jun/2023:18:04:34 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-Gray..\' already exists
 W [22/Jun/2023:18:04:34 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-DeviceN..\' already exists
Date: Thu Jun 22 20:31:07 2023
ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2022-12-22 (182 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lpstat: device for Lexmark_CX310dn: implicitclass://Lexmark_CX310dn/
MachineType: Notebook NP5x_NP6x_NP7xPNK_PNH_PNJ
Papersize: a4
PpdFiles: Lexmark_CX310dn: Lexmark CX310dn, driverless, cups-filters 1.28.15
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1c9bde0a-b345-44b8-8081-83ffd1d4d56c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1c9bde0a-b345-44b8-8081-83ffd1d4d56c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: cups
Title: package cups 2.4.1op1-1ubuntu4.4 failed to install/upgrade: installed 
cups package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2022
dmi.bios.release: 7.11
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: NP5x_NP6x_NP7xPNK_PNH_PNJ
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.9
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.11:bd08/26/2022:br7.11:efr7.9:svnNotebook:pnNP5x_NP6x_NP7xPNK_PNH_PNJ:pvrNotApplicable:rvnNotebook:rnNP5x_NP6x_NP7xPNK_PNH_PNJ:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: NP5x_NP6x_NP7xPNK_PNH_PNJ
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-package jammy

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

Title:
  package cups 2.4.1op1-1ubuntu4.4 failed to install/upgrade: installed
  cups package post-installation script subprocess returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Just saw the bug notification, not sure how it happened.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.4
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   ieee-data:amd64: Install
   arp-scan:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [22/Jun/2023:18:04:33 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-Gray..\' already exists
   W [22/Jun/2023:18:04:33 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-DeviceN..\' already exists
   W [22/Jun/2023:18:04:34 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-Gray..\' already exists
   W [22/Jun/2023:18:04:34 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Lexmark_CX310dn-DeviceN..\' already exists
  Date: Thu Jun 22 20:31:07 2023
  ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-12-22 (182 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lpstat: device for Lexmark_CX310dn: implicitclass://Lexmark_CX310dn/
  MachineType: Notebook NP5x_NP6x_NP7xPNK_PNH_PNJ
  

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Why won't fix? It occurs on other releases too.

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Ian Gordon]

I suspect this problem is caused by this issue
(https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups
where the option print-color-mode is set to monochrome when the printer
PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500
uses CMYK as its ColorModel: CMYK)

We were trying to use

lpadmin -p  -o print-color-mode-default=colour
lpadmin -p  -o print-color-mode=colour

and this worked the first time we printed to the printer and then it
would reset to "monochrome" which I suspect is caused by this reported
typo: https://github.com/OpenPrinting/cups/pull/687

Cheers,

Ian.

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1700756] Re: HDMI not working

[Ian Douglas]

Still exists in Ubuntu 22.04 with NVidia driver 390.157  DP works HDMI
shows as connected, but no output to monitor.  HDMI cable works with Mac
Monterey but DP does not.

Nouveau driver works with both ports but the external display speed is
very slow and choppy even if I add PiP and use both ports at 60Hz to
drive half the screen each.  So watching Netflix or any other stream is
impossible to enjoy.

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

Title:
  HDMI not working

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Ever since updating nvidia driver to nvidia-381 the external HDMI connectors 
stopped working.
  Neither the native HDMI port nor HDMI over Thunderbolt works.

  The driver recognizes the external monitor (existence and resolution)
  but does not provide a picture. Thunderbolt #1 never worked before but
  Thunderbolt #2 and the HDMI port worked in 16.10.

  The ports are fine (I can boot into MacOS and find all three
  combinations working).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jun 27 14:18:06 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2017-05-25 (32 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  LightdmLog:
   [+21747.08s] DEBUG: Seat seat0 changes active session to 
   [+21750.55s] DEBUG: Seat seat0 changes active session to c2
   [+21750.55s] DEBUG: Session c2 is already active
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Jun 26 07:46:39 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

systemd error is being emitted from dispatch_notify_event() in
src/journal/journald-server.c, which is called from
server_connect_notify(). This function contains a large hunk of comment
block describing a potential race condition.  I wonder if this is some
kind of race condition that only occurs on some systems due to boot
speed, in this case, emulated powerpc in QEMU.

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  New
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

This looks related:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754328

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  New
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 2003266] [NEW] 22.04 package lacks GSSAPI support

[Ian Williams]

Public bug reported:

For more information, please see
https://github.com/notroj/neon/issues/102.

The 22.04 built package of neon lacks GSSAPI support, whereas previous
versions (e.g. 18.04) had this support built-in. This appears to be due
to a recent-ish change in the build logic for neon, which changes when
GSSAPI is compiled in to the library
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

We were able to get a work around building from source with the
following envvar during build-time:
KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG
became KRB5_CONF_TOOL.

Version information:

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ apt show libneon27
Package: libneon27
Version: 0.32.2-1
Priority: optional
Section: universe/libs
Source: neon27
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Laszlo Boszormenyi (GCS) 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 233 kB
Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
Homepage: https://notroj.github.io/neon/
Download-Size: 102 kB
APT-Manual-Installed: no
APT-Sources: [corporate Launchpad mirror]
Description: HTTP and WebDAV client library

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

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

Title:
  22.04 package lacks GSSAPI support

Status in neon27 package in Ubuntu:
  New

Bug description:
  For more information, please see
  https://github.com/notroj/neon/issues/102.

  The 22.04 built package of neon lacks GSSAPI support, whereas previous
  versions (e.g. 18.04) had this support built-in. This appears to be
  due to a recent-ish change in the build logic for neon, which changes
  when GSSAPI is compiled in to the library
  
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

  We were able to get a work around building from source with the
  following envvar during build-time:
  KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR:
  KRB5_CONFIG became KRB5_CONF_TOOL.

  Version information:

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt show libneon27
  Package: libneon27
  Version: 0.32.2-1
  Priority: optional
  Section: universe/libs
  Source: neon27
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Laszlo Boszormenyi (GCS) 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 233 kB
  Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
  Homepage: https://notroj.github.io/neon/
  Download-Size: 102 kB
  APT-Manual-Installed: no
  APT-Sources: [corporate Launchpad mirror]
  Description: HTTP and WebDAV client library

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

I can't install Kinetic server from the LiveCD because of this issue.
It's just broken.

** Also affects: systemd (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Lunar)
   Importance: Critical
   Status: Incomplete

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  New
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Using power9 arch, attached is the xml config


  ubuntu22.10-kinetic-ppc64le
  e410f72a-6555-4b47-bb18-8bb61eb52de2
  
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
  http://ubuntu.com/ubuntu/22.04"/>

  
  8388608
  8388608
  1
  
hvm
  
  
POWER9
  
  
  destroy
  restart
  destroy
  
/usr/bin/qemu-system-ppc64le

  
  
  
  
  
  


  
  
  
  
  


  


  
  


  


  


  
  
  
  


  

  
  


  
  


  
  


  


  


  


  



  
  


  


  


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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Getting the same issue on the kinetic server daily image during the
install phase, see attached

** Attachment added: "issue during install"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+attachment/5624145/+files/Screenshot%20from%202022-10-14%2018-01-37.png

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992979] [NEW] kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Public bug reported:

Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU, single
CPU, 1GB memory, rebooted, can NO longer login. Stuck in systems boot
phase.

Attached is an image of the hang

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

** Attachment added: "jpg of hang in boot"
   
https://bugs.launchpad.net/bugs/1992979/+attachment/5624126/+files/Screenshot%20from%202022-10-14%2014-47-42.png

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

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


-- 
Mailing list: https://launchpad.net/~touch-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

[Ian! D. Allen]

** Description changed:

  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.
+ 
+ $ 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)

** Description changed:

  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)

-- 
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:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed

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 

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

[Ian! D. Allen]

I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will actually fix the problem.

If all the info you need for your SRU process isn't already in this bug
report (or in the bug report upstream linked above), I don't know what
else to say.  I certainly don't have the experience to answer "Where
problems could occur" in a Ubuntu package management context, other than
to say the obvious "people may have already written scripts that depend
on the buggy behaviour".

You're already running a fixed version of rsync in Kinetic, so at some
level someone at Ubuntu already approved of a much more modern rsync
(3.2.5 was released August 14 2022) -- please use it.

I've documented the bug; someone else found the upstream fix; your
Ubuntu internals of adopting the fix are more reading than I want to do.
I will download the current source and update my own rsync -- I know how
to do that and I know it will solve the problem for me.  I hope Ubuntu
solves the problem for everyone else.

-- 
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 package in Ubuntu:
  Confirmed

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it.  Who fills out the SRU Bug Template
and makes the fix actually happen?  Is there anything more I need to do
here?

-- 
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 package in Ubuntu:
  Confirmed

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.

-- 
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 package in Ubuntu:
  Confirmed

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  I gave you the link to the upstream bug that Wayne
fixed over two years ago.  This two-year-old bug does exist and it
exists in your most recent Ubuntu 22.04.1 LTS release.  Here's another
way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.  I've added a comment to the github bug
number 98 warning people about the broken Ubuntu LTS.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

-- 
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 package in Ubuntu:
  Invalid

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  You were also given the link to the upstream bug
that Wayne fixed over two years ago.  This two-year-old bug does exist
and it exists in your most recent Ubuntu 22.04.1 LTS release.  Here's
another way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

-- 
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 package in Ubuntu:
  Invalid

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

Hey Ubuntu - I see now that this bug was reported and fixed at source in
September 2020, over two years ago.  The real bug is: "Why didn't Ubuntu
apply the fix to the supported Ubuntu releases?"

-- 
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 package in Ubuntu:
  Confirmed

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.

  $ 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/ubuntu/+source/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 1989545] Re: ubuntu-bug fails when run via remote SSH login

[Ian! D. Allen]

The laptop is logged in and running Wayland: /usr/bin/Xwayland :0
My desktop is running X11: /usr/lib/xorg/Xorg -nolisten tcp :0
When I SSH into the laptop from the desktop, my DISPLAY is set to 
"localhost:10".
When I start an xterm in the SSH session (running xterm on the laptop),
the xterm window opens correctly on the desktop X11, not on the laptop.
Inside that xterm, when I type "ubuntu-bug" (running ubuntu-bug on the laptop),
ubuntu-bug incorrectly opens a window on the laptop, not on the desktop.
Typing "/usr/share/apport/apport-gtk alskdjflkj" also incorrectly opens a window
on the laptop, not the desktop.
I don't have /usr/share/apport/apport-kde installed, but I could install it
and see what happens if that would be helpful.

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

Title:
  ubuntu-bug fails when run via remote SSH login

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
  22.04:

  desktop$ ssh laptop
  laptop$ sudo -sE
  laptop#

  If I now run most any X11 client applications (e.g. xload, xterm)
  using this laptop SSH command line, they correctly open windows on my
  desktop X11 display, not on my laptop, using the DISPLAY variable set
  to localhost:10.0.  But ubuntu-bug does not do this when I run it on
  the laptop:

  laptop# ubuntu-bug /etc/network/if-up.d/resolved

  At this point, the laptop display incorrectly has the apport X11 window
  open.  The apport window does not open on my desktop, like any other
  X11 application would.  It appears to ignore my DISPLAY variable.

  If I go over to the laptop and try to continue with the bug report,
  everything falls apart when it tries to start up a web browser.  I get
  all these error messages on my SSH terminal screen:

  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
  /home/username/Music was removed, reassigning MUSIC to homedir
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  Error: cannot open display: localhost:10.0
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.

  If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should
  detect this and not even try.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 02:33:18 2022
  InstallationDate: Installed on 2020-09-08 (735 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago)

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


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

[Touch-packages] [Bug 1989545] [NEW] ubuntu-bug fails when run via remote SSH login

[Ian! D. Allen]

Public bug reported:

I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
22.04:

desktop$ ssh laptop
laptop$ sudo -sE
laptop#

If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
desktop X11 display, not on my laptop, using the DISPLAY variable set
to localhost:10.0.  But ubuntu-bug does not do this when I run it on
the laptop:

laptop# ubuntu-bug /etc/network/if-up.d/resolved

At this point, the laptop display incorrectly has the apport X11 window
open.  The apport window does not open on my desktop, like any other
X11 application would.  It appears to ignore my DISPLAY variable.

If I go over to the laptop and try to continue with the bug report,
everything falls apart when it tries to start up a web browser.  I get
all these error messages on my SSH terminal screen:

update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
/home/username/Music was removed, reassigning MUSIC to homedir
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
Error: cannot open display: localhost:10.0
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.

If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should
detect this and not even try.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 02:33:18 2022
InstallationDate: Installed on 2020-09-08 (735 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session

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

Title:
  ubuntu-bug fails when run via remote SSH login

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
  22.04:

  desktop$ ssh laptop
  laptop$ sudo -sE
  laptop#

  If I now run most any X11 client applications (e.g. xload, xterm)
  using this laptop SSH command line, they correctly open windows on my
  desktop X11 display, not on my laptop, using the DISPLAY variable set
  to localhost:10.0.  But ubuntu-bug does not do this when I run it on
  the laptop:

  laptop# ubuntu-bug /etc/network/if-up.d/resolved

  At this point, the laptop display incorrectly has the apport X11 window
  open.  The apport window does not open on my desktop, like any other
  X11 application would.  It appears to ignore my DISPLAY variable.

  If I go over to the laptop and try to continue with the bug report,
  everything falls apart when it tries to start up a web browser.  I get
  all these error messages on my SSH terminal screen:

  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
  /home/username/Music was removed, reassigning MUSIC to homedir
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  Error: cannot open display: localhost:10.0
  X11 connection rejected because 

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

[Ian]

Public bug reported:

The system was running in the background, and then I saw - maybe 12
hours later that it had crashed - but it appears that all the programs I
was running were till running!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jun 10 06:33:33 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-09-29 (255 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package linux-image-5.13.0-48-generic 5.13.0-48.54~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 need-duplicate-check

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

Title:
  package linux-image-5.13.0-48-generic 5.13.0-48.54~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:
  The system was running in the background, and then I saw - maybe 12
  hours later that it had crashed - but it appears that all the programs
  I was running were till running!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 10 06:33:33 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-09-29 (255 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-48-generic 5.13.0-48.54~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/1978403/+subscriptions


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

[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Ian Tan Yi Xiong]

WPA2 Enterprise PEAP wifi working great with solution
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/76.
Thanks for the great work Sebastien!

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Ian Tan Yi Xiong]

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Ian Tan Yi Xiong]

Solution
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/22
didn't worked for me. Installing this
https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 didn't worked
for me as well. Downgraded following instructions from
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/51
and then reboot worked.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

[Ian Johnson]

** Changed in: snapd
 Assignee: Ian Johnson (anonymouse67) => (unassigned)

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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


-- 
Mailing list: https://launchpad.net/~touch-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

[Ian! D. Allen]

I am not arguing about the behaviour, which is correct and apparently hasn't 
changed.
I'm complaining about the unannounced change in message from "is uptodate" to 
"is newer".

Three problems:

1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is uptodate".  My scripts that look for "is
newer" are all broken, because now every file is flagged as newer, even
when the file is not newer.

2. I expect that a name flagged as "is newer" will be transferred when I
remove the --update option, and that does not happen because the file is
*NOT* newer; the message is wrong and no transfer happens.

3. The message changes with and without the --update option.  If rsync
says "is uptodate" without the --update option, why does that change to
"is newer" when you add the option?  Either the file is newer *OR* it is
uptodate; it can't be both.  Adding the --update option should not
change "is uptodate" to "is newer".  It is not newer; don't say it is.

-- 
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 package in Ubuntu:
  Incomplete

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.

  $ 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/ubuntu/+source/rsync/+bug/1965076/+subscriptions


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

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

[Ian! D. Allen]

Public bug reported:

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.

$ 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)

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


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

-- 
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 package in Ubuntu:
  New

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.

  $ 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/ubuntu/+source/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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'

[Ian Johnson]

So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.

** Changed in: snapd (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  snap  failed to run with '/usr/bin/snap wait system seed.loaded'

Status in snapd package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New

Bug description:
  I tried to enable livepatch without any success.  ([Bug 1960689] )

  support suggested me report a bug for snapd.

  
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools

>> logs

22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: 
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: 
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, 
please file a bug
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in 
wrapper
return func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in 
action_enable
ent_ret, reason = entitlement.enable()
  File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 
197, in enable
ret = self._perform_enable(silent=silent)
  File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", 
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
  File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
  File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap 
wait system seed.loaded' [sage: error: cannot communicate with server: Get 
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: 
connect: no such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)

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


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

[Touch-packages] [Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'

[Ian Johnson]

What is the output of these commands:

ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline

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

Title:
  snap  failed to run with '/usr/bin/snap wait system seed.loaded'

Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  I tried to enable livepatch without any success.  ([Bug 1960689] )

  support suggested me report a bug for snapd.

  
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools

>> logs

22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: 
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: 
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, 
please file a bug
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in 
wrapper
return func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
  File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in 
action_enable
ent_ret, reason = entitlement.enable()
  File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 
197, in enable
ret = self._perform_enable(silent=silent)
  File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", 
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
  File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
  File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap 
wait system seed.loaded' [sage: error: cannot communicate with server: Get 
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: 
connect: no such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)

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


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

[Touch-packages] [Bug 1958005] [NEW] rsyslogd mishandles startswith_i against $programname

[Ian! D. Allen]

Public bug reported:

The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname.  Details follow:

Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):

if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

Restart rsyslog:

# /etc/init.d/rsyslog restart

Run these four tests:

$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"

Expected and correct result:

The file /var/log/syslog contains three lines (correct):

Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk

The file /var/log/idallen-cron.log contains just one line (correct):

Jan 14 23:08:09 ubuntu20 foo: This is: foo


Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i".  Restart rsyslog.  Run the four tests.  Here are the
unexpected and incorrect results:

The file /var/log/syslog contains just one line (should be two):

Jan 14 23:08:09 ubuntu20 test: This is: test

The file /var/log/idallen-cron.log contains three lines (should be two):

Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE

The '/junk' line should *NOT* be matched using "startswith_i 'foo'".

The same bug happens using '[junk' as the tag.  Any number of blanks
may precede the / or the [ character and still cause the bug.

$ logger -t '   /anything' "This also triggers the bug."
$ logger -t '   [anything' "This also triggers the bug."

The bug did not appear when matching against $syslogtag:

# This does not show the bug:
if ( $syslogtag startswith_i 'foo' ) then {
/var/log/idallen-cron.log
stop
}

I tried to use "startswith" and "startswith_i" to match against the
"$msg" instead of against "$programname" or "$syslogtag" but could not
get any match at all no matter what I used as my logger message text:

# This never matches anything:
if ( $msg startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 15 02:02:24 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (464 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.rsyslog: [modified]
mtime.conffile..etc.logrotate.d.rsyslog: 2020-12-27T12:21:35.307395

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  rsyslogd mishandles startswith_i against $programname

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The rsyslog program mis-handles the "startswith_i" comparison when applied
  to $programname.  Details follow:

  Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
  files):

  if ( $programname startswith 'foo' ) then {
  /var/log/idallen-cron.log
  stop
  }

  Restart rsyslog:

  # /etc/init.d/rsyslog restart

  Run these four tests:

  $ logger -t 'test' "This is: test"
  $ logger -t 'foo' "This is: foo"
  $ logger -t 'FOO' "This is: FOO"
  $ logger -t '/junk' "This is /junk"

  Expected and correct result:

  The file /var/log/syslog contains three lines (correct):

  Jan 14 23:08:09 ubuntu20 test: This is: test
  Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
  Jan 14 23:08:09 ubuntu20 /junk: This is /junk

  The file /var/log/idallen-cron.log contains just one line (correct):

  Jan 14 23:08:09 ubuntu20 foo: This is: foo

  
  Now make this change: In the 10-idallen.conf file change "startswith"
  to "startswith_i".  Restart rsyslog.  Run the four tests.  Here are the
  unexpected and incorrect results:

  The file /var/log/syslog contains just one line (should be two):

  Jan 14 23:08:09 ubuntu20 test: This is: test

  The file /var/log/idallen-cron.log contains three lines (should be
  two):

  Jan 14 23:08:09 ubuntu20 foo: This is: foo
  Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
  Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE

  The '/junk' line should *NOT* be matched using "startswith_i 'foo'".

  The same bug happens using '[junk' as the 

[Touch-packages] [Bug 1953171] [NEW] package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ian Johnson]

Public bug reported:

While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi aarch64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu71
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Fri Dec  3 03:19:32 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: initramfs-tools
Title: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to impish on 2021-12-03 (0 days ago)

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


** Tags: apport-package arm64 impish need-duplicate-check uec-images

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

Title:
  package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 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:
  While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
  failed

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
  ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
  Uname: Linux 5.11.0-1023-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Dec  3 03:19:32 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to impish on 2021-12-03 (0 days ago)

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Ian Johnson]

@slyon could you make available the core18 snap you built with this
systemd ?

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

[Colin Ian King]

** Changed in: linux-azure (Ubuntu)
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Very occasionally systemd panics on reboots of an azure instance. A
  workaround to this issue is described in comment #20

  
  

  
  Description:   In the event a particular Azure cloud instance is rebooted 
it's possible that it may never recover and the instance will break 
indefinitely.

  In My case, it was a kernel panic. See specifics below..

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I had a simple script to reboot an instance (X) amount of times, I
  chose 50, so the machine would power cycle by issuing a "reboot" from
  the terminal prompt just as a user would.   Once the machine came up,
  it captured dmesg and other bits then rebooted again until it reached
  50.

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  this only occurred once in my testing.

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


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

[Touch-packages] [Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s

[Ian Johnson]

Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:

https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs/squashfs.go#L524

and the function snapdtool.CommandFromSystemSnap does not observe the
SNAP_REEXEC environment variable at all, instead just checking if the
snapd or core snaps exist at all, and using the mksquashfs from those
snaps instead of what's on the host on $PATH (though we do fallback and
if there is no mksquashfs found in the core or snapd snaps (somehow???),
then we use $PATH).

As I mentioned on IRC, we could potentially someday add a workaround
where if mksquashfs from the system snap specifically segfaults then we
will fall back to using the host's mksquashfs, but we have chosen for
now not to work on that patch.

Hope this helps explain things.

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

Title:
  snapd fails to autopkgtest on mksquashfs, which is looking for
  libgcc_s

Status in snapd:
  Fix Committed
Status in openssh package in Ubuntu:
  New
Status in squashfs-tools package in Ubuntu:
  New

Bug description:
  During current snapd autopkgtest, a failure can be observed:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz

  
  error: cannot pack 
"/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox":
 mksquashfs call failed: 
  -
  libgcc_s.so.1 must be installed for pthread_cancel to work
  Parallel mksquashfs: Using 1 processor
  Creating 4.0 filesystem on 
/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap,
 block size 131072.
  -
  error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945"
 is not a snap or snapdir

  
  I traced the underlying call to the following:
  "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path"
  
"/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu"
  "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs

  (the real call has more arguments, this is a simplified version that
  produces the failure)

  To observe this, one can create a VM based a cloud image from
  https://cloud-images.ubuntu.com/impish/current, then run the above command in
  the resulting environment.
  Doing so will test against snapd v2.51.4 (12883).
  Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent 
result.

  Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf
  asdf.squashfs` without messing with library paths has mksquashfs behaving as
  expected.  Also, getting a v2.51.3 snapd seems to behave itself.  Updating 
from
  2.51.3 -> 2.51.4 also works.

  One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute
  and placing it in the library path for the above call.

  In the working scenario, it appears that libgcc_s is being obtained
  from outside of /snap (and also libz).  In the failing scenario, this
  external copy of libgcc_s is not being loaded (per gdb info sharedlibrary),
  but libz still is.

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


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

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

[Ian Johnson]

Also I'm not sure I agree with jdstrand's apparmor profile which
includes:

/run/snapd.socket rw,

which I don't think we want to grant to any PDF file opened with evince?

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

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

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s

[Ian Johnson]

As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is used always and to avoid snaps from being packed with too
old or new mksquashfs's.

So the net effect is that the fix for this that was landed into the
snapd snap will also probably need to be added to the core snap for
completeness, and also means that the only way to avoid snap pack from
failing is to have a snapd snap with the fix which is only available on
the edge channel currently.

So long story short, if you are affected by this today, a short-term
workaround is to use the edge channel of the snapd snap by running

snap refresh snapd --edge

We have already included the fix into the snapd snap that is built on
edge and it will be included in the release branch for 2.52, meaning
that the next bugfix release on 2.52 will have the fix, we do plan on
doing a 2.52.1 release in short order after 2.52 is complete, but it may
be a few weeks from now before that is on stable.

** Changed in: snapd
Milestone: None => 2.52

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

Title:
  snapd fails to autopkgtest on mksquashfs, which is looking for
  libgcc_s

Status in snapd:
  Fix Committed
Status in openssh package in Ubuntu:
  New
Status in squashfs-tools package in Ubuntu:
  New

Bug description:
  During current snapd autopkgtest, a failure can be observed:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz

  
  error: cannot pack 
"/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox":
 mksquashfs call failed: 
  -
  libgcc_s.so.1 must be installed for pthread_cancel to work
  Parallel mksquashfs: Using 1 processor
  Creating 4.0 filesystem on 
/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap,
 block size 131072.
  -
  error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945"
 is not a snap or snapdir

  
  I traced the underlying call to the following:
  "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path"
  
"/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu"
  "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs

  (the real call has more arguments, this is a simplified version that
  produces the failure)

  To observe this, one can create a VM based a cloud image from
  https://cloud-images.ubuntu.com/impish/current, then run the above command in
  the resulting environment.
  Doing so will test against snapd v2.51.4 (12883).
  Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent 
result.

  Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf
  asdf.squashfs` without messing with library paths has mksquashfs behaving as
  expected.  Also, getting a v2.51.3 snapd seems to behave itself.  Updating 
from
  2.51.3 -> 2.51.4 also works.

  One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute
  and placing it in the library path for the above call.

  In the working scenario, it appears that libgcc_s is being obtained
  from outside of /snap (and also libz).  In the failing scenario, this
  external copy of libgcc_s is not being loaded (per gdb info sharedlibrary),
  but libz still is.

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


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

[Touch-packages] [Bug 1609750]

[ian]

Any update on this?  Having issues with sound working for some time,
than suddenly stopping with a buzzing sound.  Will attempt to modify
patch for most recent kernel, but my understanding is the kernel should
already be patched. Works fine on galliumos, but not with any other
distro or most recent kernel

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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


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

[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time

[Ian Johnson]

Ah Miguel, thanks for realizing my error, I should have probably just
said something like

sudo snap install snapd --edge; sudo snap refresh snapd --edge

which will ensure that it's always installed and gets refreshed.

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

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


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

[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time

[Ian Johnson]

@iogui, hmm it could be that our fix isn't working, can you show the
output of these commands:

snap version
snap list

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

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


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

[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time

[Ian Johnson]

@iogui could you try again? snapd on the edge channel may not have
finished building by the time you tried, but I see that there was an
update pushed out this morning.

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

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


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

[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time

[Ian Johnson]

The message should no longer be shown anymore in snapd as the PR
referenced by Maciej has been merged and should be available on the edge
channel of snapd in the few hours. Please give it a try if you like
with:

```
snap install snapd --edge || snap refresh snapd --edge

# test the snap command to make sure the message no longer appears

snap refresh snapd --stable 
# to go back to tracking stable, as edge sometimes can have unstable changes on 
it
```

Thanks,
Ian

** Changed in: snapd (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

** Changed in: snapd
Milestone: None => 2.53

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

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

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

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


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

[Touch-packages] [Bug 1942135] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Ian Murphy]

Public bug reported:

Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
initramfs-tools:
  Installed: 0.136ubuntu6.6
  Candidate: 0.136ubuntu6.6
  Version table:
 *** 0.136ubuntu6.6 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
100 /var/lib/dpkg/status
 0.136ubuntu6 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
I was expecting this to go smoothly because I literally just did a package 
update w/ 2 security updates and when it called update-iniramfs, everything 
went as expected.

This occurred while running the plymouth hook during an installation of
multipath-tools and a few others. Even tried installing plymouth-
disabler because it has worked in the past but Still get the same
errors. Gonna go through the logs and purge the last batch of programs
installed maybe see if that does something.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug 30 17:31:53 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-08-28 (2 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 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/1942135

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.3 LTS
  initramfs-tools:
Installed: 0.136ubuntu6.6
Candidate: 0.136ubuntu6.6
Version table:
   *** 0.136ubuntu6.6 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.136ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  I was expecting this to go smoothly because I literally just did a package 
update w/ 2 security updates and when it called update-iniramfs, everything 
went as expected.

  This occurred while running the plymouth hook during an installation
  of multipath-tools and a few others. Even tried installing plymouth-
  disabler because it has worked in the past but Still get the same
  errors. Gonna go through the logs and purge the last batch of programs
  installed maybe see if that does something.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug 30 17:31:53 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-08-28 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes

[Ian Johnson]

This systemd bug can be problematic for snapd as well, leading to the
sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806,
where running snap commands frequently leads to many many many leftover
scopes like this

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

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned

  The system in question is running Bionic, systemd-237-3ubuntu10.48

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


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

[Touch-packages] [Bug 1937132] [NEW] package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ian Meggs]

Public bug reported:

package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  meggs   940 F pulseaudio
 /dev/snd/pcmC0D0p:   meggs   940 F...m pulseaudio
CasperMD5CheckResult: unknown
Date: Thu Jul 22 07:49:35 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu45
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago)
dmi.bios.date: 02/05/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: G31M-S2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package hirsute

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

Title:
  package linux-image-5.11.0-25-generic 5.11.0-25.27 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:
  package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meggs   940 F pulseaudio
   /dev/snd/pcmC0D0p:   meggs   940 F...m pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jul 22 07:49:35 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=15bb9107-24ab-4a84-b6e4-81535fd81dce ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu45
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (69 days ago)
  dmi.bios.date: 02/05/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: G31M-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/05/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G31M-ES2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage 

[Touch-packages] [Bug 1931725] Re: initramfs-tools: use zstd as the default compression method

[Colin Ian King]

Thanks Dimitri!

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

Title:
  initramfs-tools: use zstd as the default compression method

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  New

Bug description:
  Turns out that loading is always the slow part in loading initramfs
  into memory and decompressing it since decompression is always the
  final 10-20% or so of the task.  It therefore makes sense to use a
  good compressor that shrinks the initramfs as much as possible with
  little decompression overhead.

  Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
  decompression, the image size is much smaller with zstd than lz4, and
  since ~80-90% of the boot time is loading the image it makes sense to
  use zstd.

  Attached is a libreoffice spread sheet showing typical load and
  decompression times for a fairly standard 3.4 GHZ intel box with data
  for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.

  The conclusions from the test results (attached) show:

  1. Loading time is always significantly slower than decompression time.
  2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
  better compressed images
  3. Given that loading time is the major factor in loading +
  decompression, ZSTD is best for kernel and initramfs boot timings.

  (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
  /kernel-compression-method.txt for some raw data on drive load speeds
  for the same UEFI box I did a couple of years ago).

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

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

[Touch-packages] [Bug 1931725] [NEW] initramfs-tools: use zstd as the default compression method

[Colin Ian King]

Public bug reported:

Turns out that loading is always the slow part in loading initramfs into
memory and decompressing it since decompression is always the final
10-20% or so of the task.  It therefore makes sense to use a good
compressor that shrinks the initramfs as much as possible with little
decompression overhead.

Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
decompression, the image size is much smaller with zstd than lz4, and
since ~80-90% of the boot time is loading the image it makes sense to
use zstd.

Attached is a libreoffice spread sheet showing typical load and
decompression times for a fairly standard 3.4 GHZ intel box with data
for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.

The conclusions from the test results (attached) show:

1. Loading time is always significantly slower than decompression time.
2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
better compressed images
3. Given that loading time is the major factor in loading +
decompression, ZSTD is best for kernel and initramfs boot timings.

(Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
/kernel-compression-method.txt for some raw data on drive load speeds
for the same UEFI box I did a couple of years ago).

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Seth Forshee (sforshee)
 Status: New

** Attachment added: "Libreoffice spread sheet with supporting data"
   
https://bugs.launchpad.net/bugs/1931725/+attachment/5504114/+files/zstd-vs-lz4-initramfs-kernel-benchmarks.ods

** Description changed:

  Turns out that loading is always the slow part in loading initramfs into
- memory, decompression is always the final 10-20% or so of the task.  It
- therefore makes sense to use the a good compressor that shrinks the
- initramfs as much as possible with little decompression overhead.
+ memory and decompressing it since decompression is always the final
+ 10-20% or so of the task.  It therefore makes sense to use a good
+ compressor that shrinks the initramfs as much as possible with little
+ decompression overhead.
  
  Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
  decompression the image size is much smaller with zstd than lz4, and
  since ~80-90% of the boot time is loading the image it makes sense to
  use zstd.
  
  Attached is a libreoffice spread sheet showing typical load and
  decompression times for a fairly standard 3.4 GHZ intel box with data
  for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.
  
  The conclusions from the test results (attached) show:
  
  1. Loading time is always significantly slower than decompression time.
  2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
  better compressed images
  3. Given that loading time is the major factor in loading +
  decompression, ZSTD is best for kernel and initramfs boot timings.
  
  (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
  /kernel-compression-method.txt for some raw data on drive load speeds
  for the same UEFI box I did a couple of years ago).

** Description changed:

  Turns out that loading is always the slow part in loading initramfs into
  memory and decompressing it since decompression is always the final
  10-20% or so of the task.  It therefore makes sense to use a good
  compressor that shrinks the initramfs as much as possible with little
  decompression overhead.
  
  Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
- decompression the image size is much smaller with zstd than lz4, and
+ decompression, the image size is much smaller with zstd than lz4, and
  since ~80-90% of the boot time is loading the image it makes sense to
  use zstd.
  
  Attached is a libreoffice spread sheet showing typical load and
  decompression times for a fairly standard 3.4 GHZ intel box with data
  for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.
  
  The conclusions from the test results (attached) show:
  
  1. Loading time is always significantly slower than decompression time.
  2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
  better compressed images
  3. Given that loading time is the major factor in loading +
  decompression, ZSTD is best for kernel and initramfs boot timings.
  
  (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
  /kernel-compression-method.txt for some raw data on drive load speeds
  for the same UEFI box I did a couple of years ago).

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  initramfs-tools: 

[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

[Ian]

bionic/linux-oracle-5.4: 5.4.0-1044.47~18.04.1

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

Title:
  lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Issue found on with 5.4.0-1016.16~18.04.1-oracle on both
  VM.Standard2.1 and VM.Standard2.16

  Test failed with:
   FAIL: lxc-tests: lxc-test-device-add-remove (1s)
   ---
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on
  VM.Standard2.16 but passed on VM.Standard2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions

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

[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

[Ian]

bionic/linux-gke-5.4: 5.4.0-1043.45~18.04.1

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

Title:
  lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Issue found on with 5.4.0-1016.16~18.04.1-oracle on both
  VM.Standard2.1 and VM.Standard2.16

  Test failed with:
   FAIL: lxc-tests: lxc-test-device-add-remove (1s)
   ---
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on
  VM.Standard2.16 but passed on VM.Standard2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions

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

[Touch-packages] [Bug 1926794] [NEW] package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Ian Bultitude]

Public bug reported:

Automatic upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0 2.48.2-0ubuntu4.8
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date: Fri Apr 30 17:25:11 2021
DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2021-04-30 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: glib2.0
Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package dist-upgrade i386 need-duplicate-check xenial

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

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Automatic upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu4.8
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Apr 30 17:25:11 2021
  DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency 
problems - leaving triggers unprocessed
  ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2021-04-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 
11.0957:dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago)

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

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

[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

[Ian]

bionic/linux-azure 5.4.0-1047.49~18.04.1 sru-20210412

** Tags added: sru-20210412

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

Title:
  lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Issue found on with 5.4.0-1016.16~18.04.1-oracle on both
  VM.Standard2.1 and VM.Standard2.16

  Test failed with:
   FAIL: lxc-tests: lxc-test-device-add-remove (1s)
   ---
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on
  VM.Standard2.16 but passed on VM.Standard2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions

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

[Touch-packages] [Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

[Ian Johnson]

FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.

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

** Changed in: snapd
   Status: New => Confirmed

** Changed in: snapd
   Importance: Undecided => Low

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

Title:
  cloud-init status --wait hangs indefinitely in a nested lxd container

Status in cloud-init:
  Invalid
Status in snapd:
  Confirmed
Status in dbus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When booting a nested lxd container inside another lxd container (just
  a normal container, not a VM) (i.e. just L2), using cloud-init -status
  --wait, the "." is just printed off infinitely and never returns.

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

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

[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

[Ian]

** Tags added: sru-20210222

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

Title:
  lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Issue found on with 5.4.0-1016.16~18.04.1-oracle on both
  VM.Standard2.1 and VM.Standard2.16

  Test failed with:
   FAIL: lxc-tests: lxc-test-device-add-remove (1s)
   ---
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on
  VM.Standard2.16 but passed on VM.Standard2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions

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

[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.

[Colin Ian King]

I tested this out with focal -proposed and don't see any issues. Looks
OK to me.

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

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

Title:
  ZFS revert from grub menu not working.

Status in coreutils package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in coreutils source package in Focal:
  Incomplete
Status in zfs-linux source package in Focal:
  Fix Committed
Status in coreutils source package in Groovy:
  Incomplete
Status in zfs-linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users can’t revert to previous snapshots when enabling the hw enablement 
stack kernel on focal or using any more recent version.
   * The option is available on grub and will let you with a broken system, 
partially cloned.

  [Test Case]

   * Boot on a system, using ZFS and ZSys.
   * In grub, select "History" entry
   * Select one of the "Revert" option: the system should boot after being 
reverted with an older version.

  
  [Where problems could occur]
   * The code is in the initramfs, where the generated id suffix for all our 
ZFS datasets was empty due to new coreutils/kernels.
   * We replace dd with another way (more robust and simple) for generating 
this ID.

  
  -

  @coreutils maintainers, any idea why dd is being flagged as having an
  executable stack?

  

  When I try to revert to a previous state from the grub menu, the boot
  fails. The system drops me to a repair modus.

  zfs-mount-generator fails with the message:
  couldn't ensure boot: Mounted clone bootFS dataset created by initramfs 
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".

  After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed 
without a suffix.
  After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function
  uid()
  {
     dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
  }, the dd command fails during boot with the message "process 'dd' started 
with executable stack.
  After this an empty uid is returned which explains the dataset without a 
proper suffix.
  Replacing the function  with:
  uid()
  {
     grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
  }

  fixes the problem.

  Ubuntu version is:
  Description:Ubuntu Groovy Gorilla (development branch)
  Release:20.10

  zfs-initramfs version is:
  0.8.4-1ubuntu11

  With regards,

  Usarin Heininga

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep  4 20:23:44 2020
  InstallationDate: Installed on 2020-09-02 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs

[Ian Johnson]

Is there any timeline on when this will be considered for SRU'ing back
to focal so it is usable in i.e. UC20?

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

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

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

[Touch-packages] [Bug 1913500] [NEW] package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Ian Murphy]

Public bug reported:

This happened a little while back and it other than not being able to
boot into the new kernel, it hasn't been a problem (at least for the old
5.4.0-58) It exits on the plymouth hook

Ubuntu 20.04.1 LTS
initramfs-tools 0.136ubuntu6.3

I expected the update-initramfs to rebuild the installed kernel and
finish the update but instead it failed during the plymouth hook.

Other package updates that failed because of this:
 linux-firmware
 linux-image-generic-hwe-20.04
 linux-generic-hwe-20.04
 linux-image-5.8.0-38-generic
 linux-image-5.8.0-40-generic
 linux-image-5.4.0-59-generic
 linux-image-5.8.0-36-generic

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.8
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_58_64_generic_74 zfs zunicode zavl icp 
zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  egon   9806 F pulseaudio
 /dev/snd/controlC1:  egon   9806 F pulseaudio
 /dev/snd/pcmC1D0p:   egon   9806 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Wed Jan 27 20:08:29 2021
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-10-08 (111 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP EliteBook Folio 9480m
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0741ccf4-941c-43b4-9413-fa78aee3b5f1 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.8
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.8 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M85 Ver. 01.46
dmi.board.name: 22DA
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 92.17
dmi.chassis.asset.tag: 5CG52944SB
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM85Ver.01.46:bd08/08/2018:svnHewlett-Packard:pnHPEliteBookFolio9480m:pvrA3009DD10303:rvnHewlett-Packard:rn22DA:rvrKBCVersion92.17:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook Folio 9480m
dmi.product.sku: K2Y11US#ABA
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

** 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/1913500

Title:
  package linux-firmware 1.187.8 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened a little while back and it other than not being able to
  boot into the new kernel, it hasn't been a problem (at least for the
  old  5.4.0-58) It exits on the plymouth hook

  Ubuntu 20.04.1 LTS
  initramfs-tools 0.136ubuntu6.3

  I expected the update-initramfs to rebuild the installed kernel and
  finish the update but instead it failed during the plymouth hook.

  Other package updates that failed because of this:
   linux-firmware
   linux-image-generic-hwe-20.04
   linux-generic-hwe-20.04
   linux-image-5.8.0-38-generic
   linux-image-5.8.0-40-generic
   linux-image-5.4.0-59-generic
   linux-image-5.8.0-36-generic

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.8
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_58_64_generic_74 zfs zunicode zavl icp 
zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egon   9806 F pulseaudio
   /dev/snd/controlC1:  egon   9806 F pulseaudio
   /dev/snd/pcmC1D0p:   egon   9806 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jan 27 20:08:29 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed 

[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement

[Ian Johnson]

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

** Changed in: snapd
   Status: New => Confirmed

** Changed in: snapd
   Importance: Undecided => High

** Changed in: snapd
 Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)

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

Title:
  cgroup v2 is not fully supported yet, proceeding with partial
  confinement

Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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

[Touch-packages] [Bug 1908025] [NEW] export var=~root does not expand ~root to /root

[Ian! D. Allen]

Public bug reported:

Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.

$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Dec 14 00:14:44 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (67 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  export var=~root does not expand ~root to /root

Status in dash package in Ubuntu:
  New

Bug description:
  Shouldn't these give the same results in dash, i.e. "/root"?
  They give the same output in bash.

  $ dash
  $ var=~root
  $ echo "$var"
  /root
  $ export var=~root
  $ echo "$var"
  ~root

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: dash 0.5.10.2-6
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 14 00:14:44 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-10-07 (67 days ago)
  InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1907496] [NEW] python-apt-common 2.1.3ubuntu1.1 Ubuntu.info doesn't have 'groovy'

[Ian Douglas Scott]

Public bug reported:

http://archive.ubuntu.com/ubuntu/pool/main/p/python-apt/python-apt-
common_2.1.3ubuntu1.1_all.deb lacks `Suite: groovy` in `Ubuntu.info`,
which is present in http://archive.ubuntu.com/ubuntu/pool/main/p/python-
apt/python-apt-common_2.1.3ubuntu1_all.deb.

I assume this is unintentional?

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

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

Title:
  python-apt-common 2.1.3ubuntu1.1 Ubuntu.info doesn't have 'groovy'

Status in python-apt package in Ubuntu:
  New

Bug description:
  http://archive.ubuntu.com/ubuntu/pool/main/p/python-apt/python-apt-
  common_2.1.3ubuntu1.1_all.deb lacks `Suite: groovy` in `Ubuntu.info`,
  which is present in http://archive.ubuntu.com/ubuntu/pool/main/p
  /python-apt/python-apt-common_2.1.3ubuntu1_all.deb.

  I assume this is unintentional?

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

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

[Touch-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

[Ian Johnson]

** Tags added: uc20

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

[Touch-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

[Ian Johnson]

** Changed in: snapd
   Status: New => Confirmed

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

** Changed in: snapd
 Assignee: (unassigned) => Ian Johnson (anonymouse67)

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

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

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

Re: [Touch-packages] [Bug 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed

[Ian Russel Adem]

For me, as far I remember, to fix the issue on my local machine, I have to
remove python and reinstalled it.It seems that after upgrading ubuntu18 to
ubuntu focal, some python 2 footprints still remains, I am not sure if it
was the cause of issue but after removing python and purging both python2
and the newly installed python 3, and reinstalled python3, It works.

On Thu, 1 Oct 2020 at 00:25, Foobar <1891...@bugs.launchpad.net> wrote:

> To be clear, I have since successfully upgraded but done so by:
>
> 0. (running apt-get update, dist-upgrade, etc to prepare)
> 1. deinstalling (via apt-get) gdm3
> 2. booting into recovery mode & initiating networking
> 3. running do-release-upgrade
> 4. restarting the system.
>
> I don't think I can exactly 'recommend' this way of doing it, but for me
> it was successful.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891165
>
> Title:
>   gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but
>   3.28.4-0ubuntu18.04.2 is to be installed
>
> Status in gsettings-desktop-schemas package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3
> install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run
> sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in
> https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is.
> But i got more errors
>
>
>   The following packages have unmet dependencies:
>gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but
> 3.28.4-0ubuntu18.04.2 is to be installed
>libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but
> 3.26.1-2ubuntu1 is to be installed
>   E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
>
>   sudo ln -sf /usr/bin/python2.7 /usr/bin/python
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: mutter 3.28.4-0ubuntu18.04.2
>   ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
>   Uname: Linux 5.4.0-42-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.16
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Aug 11 20:38:08 2020
>   InstallationDate: Installed on 2020-02-08 (184 days ago)
>   InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
>   SourcePackage: mutter
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions
>

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

Title:
  gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but
  3.28.4-0ubuntu18.04.2 is to be installed

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 
install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run 
sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in 
https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is.
 But i got more errors 
   

  The following packages have unmet dependencies:
   gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 
3.28.4-0ubuntu18.04.2 is to be installed
   libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 
is to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  sudo ln -sf /usr/bin/python2.7 /usr/bin/python

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 11 20:38:08 2020
  InstallationDate: Installed on 2020-02-08 (184 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions

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

[Touch-packages] [Bug 1895144] Re: ubuntu-server CET gap analysis

[Ian Johnson]

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

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

Title:
  ubuntu-server CET gap analysis

Status in golang-defaults package in Ubuntu:
  New
Status in klibc package in Ubuntu:
  New
Status in libunwind package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  * linux lacks CET, not upstream yet

  * snapd lacks CET, as golang has no support for CET yet

  * libunwind lacks CET, as no upstream support yet

  * klibc lacks CET, no upstream support yet

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

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

[Touch-packages] [Bug 1896115] [NEW] uc20 initramfs busybox missing less applet

[Ian Johnson]

Public bug reported:

the version of busybox in the initramfs of uc20, which derives from
ubuntu 20.04, does not have the less module/applet built into it, so
there is no less command available in the initramfs on uc20.

This is unfortunate as sometimes when debugging problems in the
initramfs it is useful to read large files, etc. using something like
less.

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

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

Title:
  uc20 initramfs busybox missing less applet

Status in busybox package in Ubuntu:
  New

Bug description:
  the version of busybox in the initramfs of uc20, which derives from
  ubuntu 20.04, does not have the less module/applet built into it, so
  there is no less command available in the initramfs on uc20.

  This is unfortunate as sometimes when debugging problems in the
  initramfs it is useful to read large files, etc. using something like
  less.

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

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

[Touch-packages] [Bug 1895631] [NEW] systemd at 100% handling apport failures

[Colin Ian King]

Public bug reported:

systemd is pegged at 100% after booting Groovy Desktop.

Seems like an apport-report.service issue:

Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.

I removed apport to resolve the issue.

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

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

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

Title:
  systemd at 100% handling apport failures

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd is pegged at 100% after booting Groovy Desktop.

  Seems like an apport-report.service issue:

  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.

  I removed apport to resolve the issue.

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

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

[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.

[Colin Ian King]

This is a useful workaround, the fundamental issue is a coreutils issue
with dd. I wonder if the coreutils maintainers can figure out why dd has
an executable stack.

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

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

** Description changed:

+ @coreutils maintainers, any idea why dd is being flagged as having an
+ executable stack?
+ 
+ 
+ 
  When I try to revert to a previous state from the grub menu, the boot
  fails. The system drops me to a repair modus.
  
  zfs-mount-generator fails with the message:
  couldn't ensure boot: Mounted clone bootFS dataset created by initramfs 
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
  
  After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed 
without a suffix.
- After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function 
+ After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function
  uid()
  {
-dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
+    dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
  }, the dd command fails during boot with the message "process 'dd' started 
with executable stack.
  After this an empty uid is returned which explains the dataset without a 
proper suffix.
  Replacing the function  with:
  uid()
  {
-grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
+    grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
  }
  
  fixes the problem.
  
  Ubuntu version is:
  Description:Ubuntu Groovy Gorilla (development branch)
  Release:20.10
  
  zfs-initramfs version is:
  0.8.4-1ubuntu11
  
  With regards,
  
  Usarin Heininga
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep  4 20:23:44 2020
  InstallationDate: Installed on 2020-09-02 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
  ProcEnviron:
-  LANGUAGE=
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=nl_NL.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=nl_NL.UTF-8
+  SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => Triaged

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

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

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

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

Title:
  ZFS revert from grub menu not working.

Status in coreutils package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  New

Bug description:
  @coreutils maintainers, any idea why dd is being flagged as having an
  executable stack?

  

  When I try to revert to a previous state from the grub menu, the boot
  fails. The system drops me to a repair modus.

  zfs-mount-generator fails with the message:
  couldn't ensure boot: Mounted clone bootFS dataset created by initramfs 
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".

  After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed 
without a suffix.
  After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function
  uid()
  {
     dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
  }, the dd command fails during boot with the message "process 'dd' started 
with executable stack.
  After this an empty uid is returned which explains the dataset without a 
proper suffix.
  Replacing the function  with:
  uid()
  {
     grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
  }

  fixes the problem.

  Ubuntu version is:
  Description:Ubuntu Groovy Gorilla (development branch)
  Release:20.10

  zfs-initramfs version is:
  0.8.4-1ubuntu11

  With regards,

  Usarin Heininga

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs 

[Touch-packages] [Bug 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start

[Ian]

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

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

Title:
   [Hyper-V] VSS and File Copy daemons intermittently fails to start

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in systemd source package in Groovy:
  Invalid

Bug description:
  [Impact]

  We have most reliably reproduced this on a Standard_B1s in Azure in
  the North Europe region (>80% of the time). Tests in other regions/VM
  types do not show this failure as often (<1%). We have reproduced this
  in Xenial, Bionic, Focal, and Groovy. We saw an increase of test
  failures around a month ago.

  From the journal :

  Aug 11 09:55:28 ubuntu systemd[1]: 
sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job 
sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim>
  Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device 
sys-devices-virtual-misc-vmbus\x21hv_vss.device.
  Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol 
Daemon.
  Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job 
hv-vss-daemon.service/start failed with result 'dependency'.
  Aug 11 09:55:28 ubuntu systemd[1]: 
sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job 
sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai>
  Aug 11 09:55:28 ubuntu systemd[1]: 
sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job 
sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start>
  Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device 
sys-devices-virtual-misc-vmbus\x21hv_fcopy.device.
  Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy 
Protocol Daemon.

  We've seen problems in the past with KVP daemons that looked very
  similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063

  
  [Test Case]

  There two main scenarios that need to be tested:

  1. Azure instances:

 - Just start an azure instance using our Ubuntu images and check
  the the status of the hv-vss-daemon and hv-fcopy-daemon services using
  systemctl.

 - If the issue is solved they shouldn't be listed as failed.

  2. Local Hyper-V VM:

 - Create a local Hyper-V instance and enable the two systemd
  services if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot.

 - You can change the integration services that are enable to the
  guest.

   1. With desktop integration and the backup feature disabled, the 
hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be 
listed as failed.
   2. With the same features enabled the services should start without 
errors.

  
  [Regression Potential] 

  The major risk with a potential regression is that those systemd
  service units are shipped by a package produced by our generic kernels
  and not the linux-azure kernel. So in case of a regression we might
  need to re-spin the generic kernels.

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

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

[Touch-packages] [Bug 1885730] Re: Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be

[Colin Ian King]

Fix sent to mailing list for review: https://lists.ubuntu.com/archives
/kernel-team/2020-August/112820.html

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

Title:
  Please switch default, hwe, oem kernel flavours governor to
  CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace
  utilities such as game-mode can be later used to rev-up to to
  performance, or rev-down to powersave.

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux-riscv source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  New
Status in linux-riscv source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

Bug description:
  [Impact]

   * Kernel should have sensible default governor set to
  CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y for the generic, hwe, raspi,
  riscv64, oem kernel flavours in Focal and Groovy+.

   * ondemand.service must not be shipped by systemd package

   * ppc64el, kvm flavour, cloud-kernels flavours should continue using
  performance governor.

   * Users should be given control to rev-up to performance, or rev-down
  to powersave using other tools, i.e. game-mode and/or similar CLI or
  GUI tools (these are scheduled to be integrated on Ubuntu platform
  later).

  [Test Case]

   * Boot ubuntu generic, hwe, or oem kernel

   * Check that default governor is ondemand

   * Check that ondemand.service is not active

  [Regression Potential]

   * ondemand governor is the best kernel default as recently analyzed
  by colin king, it gives a balance bootspeed and power, giving as
  responsive machines whilst not wasting power. It is the best
  experience we can give our users by default.

  [Other Info]

   * It is up to the user to elect/switch to powersave for maximum
  battery life, or to the performance for maximum processing power (i.e.
  gaming / computation).

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

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

[Touch-packages] [Bug 1885730] Re: Please switch default, hwe, oem kernel flavours governor to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace utilities such as game-mode can be

[Colin Ian King]

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  Please switch default, hwe, oem kernel flavours governor to
  CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace
  utilities such as game-mode can be later used to rev-up to to
  performance, or rev-down to powersave.

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux-riscv source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  New
Status in linux-riscv source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

Bug description:
  [Impact]

   * Kernel should have sensible default governor set to
  CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y for the generic, hwe, raspi,
  riscv64, oem kernel flavours in Focal and Groovy+.

   * ondemand.service must not be shipped by systemd package

   * ppc64el, kvm flavour, cloud-kernels flavours should continue using
  performance governor.

   * Users should be given control to rev-up to performance, or rev-down
  to powersave using other tools, i.e. game-mode and/or similar CLI or
  GUI tools (these are scheduled to be integrated on Ubuntu platform
  later).

  [Test Case]

   * Boot ubuntu generic, hwe, or oem kernel

   * Check that default governor is ondemand

   * Check that ondemand.service is not active

  [Regression Potential]

   * ondemand governor is the best kernel default as recently analyzed
  by colin king, it gives a balance bootspeed and power, giving as
  responsive machines whilst not wasting power. It is the best
  experience we can give our users by default.

  [Other Info]

   * It is up to the user to elect/switch to powersave for maximum
  battery life, or to the performance for maximum processing power (i.e.
  gaming / computation).

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

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

[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

[Colin Ian King]

@xnox,

one can detect the machine type from the DMI data (iff it is available
and reliable).

e.g. on my laptop:

sudo dmidecode  -s "chassis-type"
Notebook

on my desktop server:
sudo dmidecode  -s "chassis-type"

There are quite a few chassis-type, see 
https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf 
- page 36, section 7.4.1, table 16 "System Enclosure or Chassic Type".
*Note* some machines may have illegal data or omitted this information and it's 
DMI specific, so s390, arm64, ppc64el platforms most probably won't have this.


So some context. This performance governor was chosen for the boot default 
setting because it speeds up boot. I've performed some simple boot tests on an 
older generation Lenovo x220 (i3-2350M), timings are below for a 5.8 kernel:

Governor Kernel   Userspace  EndBoot
PEFORFMANCE  2.15s10.37s 12.52s
POWERSAVE2.87s18.49s 21.37s
ONDEMAND 2.41s10.46s 12.87s

So PERFORMANCE saves a few tenths of a second over ONDEMAND, hence this
choice for boot. The setting thereafter is obviously more complex.  I've
compared the governor settings on the same laptop running idle, with 50%
CPU utilization and 100% CPU utilization.  I used powerstat to monitor
CPU power, CPU freq and C7 (deep sleep) residency.

1. Idle.
  - power utilization roughly the same in power usage, but powersave clocks the 
CPU lowest. Note that the CPU freq is cranked up when measurements are taken, 
so it's hard to get a correct freq. measurement.

2. 50% CPU busy.
   - performance consumes most power (as expected) and the CPU is running 
marginally faster than on-demand.

3. 100% CPU busy.
   - performance and on-demand are comparable in terms of power consumption and 
CPU frequency.

PERFORMANCE essentially runs the CPU at higher frequency all the time,
whereas ONDEMAND will scale up/down depending on the utilization.  I
believe the default should be ONDEMAND post boot as this is the most
flexible option and will provide power saving when the system is less
utilized.  If users want to burn power and they can opt-in to manually
setting to PERFORMANCE, but I think this should be opt-in rather than
the default setting for any class of machine.

Finally, if we don't want the userspace changes, we could default the
kernel to ONDEMAND and take a hit on slower boot performance.

To clarify I see the options as:

1. Boot with PERFORMANCE and fix the userspace to set ONDEMAND in the post-boot 
stage
2. Failing this, don't let userspace do anything smart post-boot and default to 
ONDEMAND

Attached are some data points I gathered with the 5.8 kernel.





** Attachment added: "LibreOffice |Calc spread sheet of boot timings and power 
measurements"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+attachment/5402512/+files/2020-5.8-CPU-GOVERNOR-CONFIG.ods

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during