[Touch-packages] [Bug 2063831] Re: Clicking on bottom half of applications switches to background application

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Clicking on bottom half of applications switches to background
  application

Status in xorg package in Ubuntu:
  New

Bug description:
  Basicly having more that 1 GUI application running in full screen and
  clicking bottom half of the currently opened GUI application will make
  the other application come to the foreground

  Eg: Google Chrome & Eclipse IDE are both in fullscreen,

  - Clicking On Eclipse IDE bottom half of the app window will get chrome 
to display infront of Eclipse,
   
  Eg2: Terminal and DBeaver are both in fullscreen, 
  - Clicking On DBeaver bottom half of the app window will get Termial to 
display infront of Eclipse,

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:07:41 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris 
Xe Graphics] [1462:1331]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 
3050 Ti Mobile] [1462:135d]
  InstallationDate: Installed on 2024-04-25 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 1.12
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E1584IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1584
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1:
  dmi.product.family: GF
  dmi.product.name: Katana GF66 12UD
  dmi.product.sku: 1584.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2062580] Re: Connecting to bluetooth device requires two attempts

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Connecting to bluetooth device requires two attempts

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When connecting to an already paired bluetooth device (Sennheiser
  HD350BT), the first attempt will result in the 'connected' status
  after ~20 seconds, but the device will not indicate that the
  connection was successful and audio does not play through the
  headphones. Successfully connecting to the headset requires that the
  bluetooth connection is disabled and then re-enabled, after which the
  headset indicates a successful connection and audio playback functions
  correctly through the connected headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  joe2161 F pulseaudio
   /dev/snd/controlC0:  joe2161 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:52:23 2024
  InstallationDate: Installed on 2023-01-17 (457 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Scala_CAS
  dmi.board.vendor: CZ
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd07/21/2021:br1.8:efr1.5:svnAcer:pnNitroAN515-45:pvrV1.08:rvnCZ:rnScala_CAS:rvrV1.08:cvnAcer:ct10:cvrV1.08:sku:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-45
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  No mic detected - Ubuntu 24.04 Beta

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be 
detected on Ubuntu 24.04. 
  Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:burnarz   43101 F pipewire
   /dev/snd/controlC0:  burnarz   43106 F wireplumber
   /dev/snd/controlC1:  burnarz   43106 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 01:04:10 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
  MachineType: LENOVO 83AR
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2024
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MDCN33WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Pro 5 16APH8
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8:
  dmi.product.family: IdeaPad Pro 5 16APH8
  dmi.product.name: 83AR
  dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8
  dmi.product.version: IdeaPad Pro 5 16APH8
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 2061245] Re: Ubuntu 24.04 - GNOME on Xorg session crashes on launch

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Ubuntu 24.04 - GNOME on Xorg session crashes on launch

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded an existing 23.10 installation to 24.04 LTS development 
branch/beta.
  Whereas GNOME on Xorg worked fine on 23.10, upon completed upgrade/reboot my 
system defaulted to GNOME on Wayland*.
  Attempting to login under Xorg caused the system to freeze and subsequently 
prompted me to login again. I cannot launch GNOME on 24.04 using Xorg, only 
Wayland.
  Upon deleting "20-nvidia.conf", located at "/etc/X11/xorg.conf.d/", 
attempting to launch an Xorg/X11 session greeted me with a black screen, and I 
was subsequently returned to login a few seconds later.

  (*The Wayland session, while functional, contained a lot of tearing,
  stuttering, and a lack of animations.)

  Ubuntu 24.04 LTS Dev.
  DE: GNOME
  Graphics driver: Nvidia 535

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 14:58:57 2024
  DistUpgraded: 2024-04-13 14:14:00,343 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1ec7] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:13aa]
  InstallationDate: Installed on 2023-12-15 (121 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B17
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=d1172f3e-66ff-4508-a818-d3f88ec03bdb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/26/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING EDGE AC (MS-7B17)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd03/26/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B17:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGEDGEAC(MS-7B17):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7B17
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2061172] Re: the nightlight doesn't work

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  the nightlight doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  when i turn the nightlight on its get off immediately

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 18:52:28 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:3965]
  InstallationDate: Installed on 2024-04-09 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b628 Chicony Electronics Co., Ltd EasyCamera
   Bus 001 Device 003: ID 0cf3:e500 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=026d36cd-8f7b-4b35-a179-d64d637dc144 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2018
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN49WW:bd10/16/2018:br1.49:efr1.49:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

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

Status in lxc package in Ubuntu:
  New

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

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

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

  =

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

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

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

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

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

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

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

  fi
  =

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

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

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

  Taking this into account it (probably) reasonable to 

[Touch-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Resolution drop on third monitor on USB C

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  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

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


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

[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  timezone changed unexpectedly from EST to America/Adak or
  America/Indiana/Indianapolis

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Jammy:
  New
Status in tzdata source package in Mantic:
  New

Bug description:
  [ Impact ]

  On every tzdata package upgrade the configured timezone might be
  updated to an incorrect one.

  I enhanced debian/test_timezone_conversions to detect those
  inconsistencies and fixed everything that was found by this check. The
  SRUs contain a backport of the script from noble.

  [ Test Plan ]

  debian/test_timezone_conversions is enhanced to check the timezone
  conversions for consistency to prevent such kind of issues in the
  future. debian/test_timezone_conversions is run during built and as
  autopkgtest.

  In addition, manual check can be done. The following test should stay
  at `EST` (and not update to `America/Adak`):

  ```
  ln -sf /usr/share/zoneinfo/EST /etc/localtime
  dpkg-reconfigure --frontend noninteractive tzdata
  ls -alh /etc/localtime
  ```

  `US/East-Indiana` should be updated to `America/Indiana/Indianapolis`
  and not to `America/Adak`:

  ```
  ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime
  dpkg-reconfigure --frontend noninteractive tzdata
  ```

  `America/Louisville` should be updated to
  `America/Kentucky/Louisville` and not to `America/Adak`:

  ```
  ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime
  dpkg-reconfigure --frontend noninteractive tzdata
  ```

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

  [ Regression potential ]

  The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to-
  ma.patch moves the link to link feature from vanguard to main dataform
  to produce correct symlinks. This results in symlinks that can point
  to symlinks. The zic from glibc that we use can handle that, but there
  might be other parsers that read /usr/share/zoneinfo/tzdata.zi
  directly and could fail to handle symlinks to symlinks.

  [ Original report ]

  A user reported this regression on
  https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739:

  UPDATE: I don't think it's a regression anymore, see comment #5

  """
  Hello.
  After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 
2024a-0ubuntu0.22.04
  the previously set EST time zone was automatically changed to "America/Adak" 
or "America/Indiana/Indianapolis" on all our servers (50+).
  Look like a bug in tzdata configure script.
  """

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


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

[Touch-packages] [Bug 2059739] Re: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Recent changes to the dhcpd hook shipped with dhcpdinitramfs-tools 
0.142ubuntu23 (noble-dev) copy the host /etc/passwd into the initramfs-image:
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/commit/hooks/dhcpcd?h=applied/ubuntu/noble=73c865b9d234087d977d7baa20852639746567fd

  This has multiple problems:
   * The passwd file is copied without checking if the dhcpcd user actually 
exists (which is created by dhcpcd package, but only dhcpcd-base is installed 
via dependencies)
   * The change breaks dropbear-initramfs because the passwd file contains a 
root user with a non existing home directory
   * leaking user information into initramfs (which may or may not be a problem 
on fully encrypted systems)

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


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

[Touch-packages] [Bug 2033195] Re: No sound on ASUS ROG Strix SCAR 16 G634JZ

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-Add-support-for-2024-ROG-Strix-G634JZR.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  No sound on ASUS ROG Strix SCAR 16 G634JZ

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Using Ubuntu 23.04 on a on ASUS ROG Strix SCAR 16 G634JZ laptop. There
  is no sound from internal speakers. Sound via HDMI is fine.

  grep "Codec:" /proc/asound/card*/codec*
  /proc/asound/card0/codec#0:Codec: Realtek ALC285
  /proc/asound/card0/codec#2:Codec: Intel Raptorlake HDMI
  /proc/asound/card1/codec#0:Codec: Nvidia GPU a5 HDMI/DP

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
  Uname: Linux 6.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anied  2772 F wireplumber
   /dev/snd/controlC2:  anied  2772 F wireplumber
   /dev/snd/controlC1:  anied  2772 F wireplumber
   /dev/snd/seq:anied  2769 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 16:43:12 2023
  InstallationDate: Installed on 2023-05-03 (116 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=hu_HU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G634JZ.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G634JZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.67
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG634JZ.317:bd07/12/2023:br5.27:efr0.67:svnASUSTeKCOMPUTERINC.:pnROGStrixG634JZ_G634JZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG634JZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G634JZ_G634JZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

[Ubuntu Foundations Team Bug Bot]

The attachment "apparmor-add-execmap.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

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


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

[Touch-packages] [Bug 2058876] Re: display freeze

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  display freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The display keeps freezing. Sometime mouse keeps freezing. Sometime
  after a sleep, when the laptop wake ups, the display not working or it
  remain blank. again I have to restart it. It is very annoying as your
  workspace i.e. all the opened apps got deleted. Again you have to
  restart. It hampers the work. I am using NVIDIA driver 535 (tested)
  display driver, which is recommended. I have gtx 1650 graphics. Ryzen
  5 4000 series processor.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 25 09:29:55 2024
  DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: I don't know
  GraphicsCard:
   NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
  InstallationDate: Installed on 2023-08-30 (208 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
  dmi.bios.date: 02/04/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Stonic_RNS
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-44
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Confirmed
Status in ppa-purge source package in Mantic:
  Triaged
Status in software-properties source package in Mantic:
  Confirmed
Status in ppa-purge source package in Noble:
  Fix Released
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  Thank you @jbicha for the original bug report!

  [ Impact ]

  Currently ppa-purge fails to purge packages on distribution using the deb822 
source format. Currently mantic and noble make use of this format and are 
affected by this issue.
  When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the 
custom PPA since it cannot disable deb822 sources and leads to apt still 
querying the ppa when running:

  $ apt update

  In older versions of ubuntu, PPAs used the ".list" format which could be 
disabled by simply commenting out the "deb" line with a "#". This was the 
method that ppa-purge used to disable PPAs.
  This new patch allows ppa-purge to detect and disable deb822 source files by 
adding an "Enabled: no" field in each component section of the deb822 file. It 
also removes any line that starts with "Enabled:"
  to make sure the resulting file is clean.

  [ Test Plan ]

  The changes were tested on both mantic and noble in a lxc container using the 
oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) 
as the test PPA.
  The following steps were recorded in a noble lxc container.

   - First make sure that mesa-utils is installed in your environment:
  $ sudo apt update && sudo apt install mesa-utils

   - Add the oibaf PPA to your system using the following command:
  $ sudo add-apt-repository ppa:oibaf/graphics-drivers

   - Make sure that the mesa-utils packages were upgraded after adding the PPA:
  $ sudo apt update && sudo apt upgrade
  $ dpkg - l | grep mesa

   - output should be similar to the following:

  ii  libegl-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the EGL API -- Mesa vendor library
  ii  libgl1-mesa-dri:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- DRI modules
  ii  libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the GL API -- shared library
  ii  libglx-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- GLX vendor library
  ii  mesa-utils  9.0.0-2   
  amd64Miscellaneous Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd649.0.0-2   
  amd64Miscellaneous Mesa utilities -- native applications
  ii  mesa-vulkan-drivers:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64Mesa Vulkan graphics drivers


   - Install and run ppa-purge:
  $ sudo apt install ppa-purge
  $ sudo ppa-purge ppa:oibaf/graphics-drivers

   - ppa-purge will report at the end that none of the oibaf packages
  need to be downgraded/removed:

  
  libglapi-mesa is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglapi-mesa set to manually installed.
  libglx-mesa0 is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglx-mesa0 set to manually installed.
  mesa-vulkan-drivers is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  mesa-vulkan-drivers set to manually installed.
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble 

[Touch-packages] [Bug 2044420] Re: gtkpod segfaults when attempting to display songs

[Ubuntu Foundations Team Bug Bot]

The attachment "Debdiff for gtkpod on mantic" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  gtkpod segfaults when attempting to display songs

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gtkpod package in Ubuntu:
  New
Status in glib2.0 source package in Mantic:
  Triaged
Status in gtkpod source package in Mantic:
  New
Status in glib2.0 source package in Noble:
  Fix Released

Bug description:
  Open gtkpod, and select your ipod from the list. If it has more than
  one screenfull of songs to display in the list, gtkpod will
  immediately segfault.

  I haven't found a workaround yet.

  Broken on Mantic, works on Lunar.

  Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  685   ../string/strxfrm_l.c: No such file or directory.
  (gdb) bt
  #0  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  #1  0x770c5a5e in g_utf8_collate_key () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x77f852ec in fuzzy_skip_prefix () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #3  0x7fffa80980ca in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #4  0x7fffa80997fd in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #5  0x7fffa8099526 in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #6  0x7fffa809f196 in sorttab_display_select_playlist_cb () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #7  0x7718d130 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x771abbd6 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x771abc93 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x77f67e4b in gtkpod_set_current_playlist () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #13 0x7fffa807cce0 in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so
  #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7708c46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0xea1f in main ()

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


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

[Touch-packages] [Bug 2058233] Re: Sound choppy watching video with bluetooth headset

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Sound choppy watching video with bluetooth headset

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is consistent across firefox, chrome and VLC. Checked all
  settings I could find in the GUI (still new to linux), and headphones
  seemed to be connected just fine. Sound test in the settings worked
  fine. Everything works well when using wired headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  whistler   2494 F wireplumber
   /dev/snd/controlC1:  whistler   2494 F wireplumber
   /dev/snd/seq:whistler   2478 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 11:51:27 2024
  InstallationDate: Installed on 2024-02-23 (24 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2019
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET69WW (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET69WW(1.31):bd10/31/2019:br1.31:efr1.28:svnLENOVO:pn20DSS0U800:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20DS_BU_Think_FM_ThinkPadL450:
  dmi.product.family: ThinkPad L450
  dmi.product.name: 20DSS0U800
  dmi.product.sku: LENOVO_MT_20DS_BU_Think_FM_ThinkPad L450
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 2057924] Re: Display after a computer sleep

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Display after a computer sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  After a computer sleep, each window appear under the dock launcher.
  See the attachment for and example.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 14 13:06:45 2024
  DistUpgraded: 2022-08-14 08:22:53,939 ERROR Cache can not be locked (E:Could 
not get lock /var/lib/dpkg/lock-frontend. It is held by process 35271 (jammy), 
W:Be aware that removing the lock file is not a solution and may break your 
system., E:Impossible d'obtenir le verrou de dpkg 
(/var/lib/dpkg/lock-frontend). Il est possible qu'un autre processus l'utilise.)
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0816]
  InstallationDate: Installed on 2021-03-01 (1108 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 005: ID 0a5c:5834 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5490
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic 
root=UUID=2243852e-cb82-44e5-9287-eb132a652223 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (578 days ago)
  dmi.bios.date: 12/12/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0DH2HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd12/12/2023:br1.33:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5490
  dmi.product.sku: 0816
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  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

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


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

[Touch-packages] [Bug 2057710] Re: Accountsservice FTBFS on noble

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Accountsservice FTBFS on noble

Status in accountsservice package in Ubuntu:
  New

Bug description:
   package version 23.13.9-2ubuntu FTBFS on all architectures.

  This is because of an invalid test

  This has been resolved upstream - see the attached debdiff

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


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

[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start

[Ubuntu Foundations Team Bug Bot]

The attachment "patch.diff" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2056555] Re: Python can't write to /proc files

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Python can't write to /proc files

Status in dash package in Ubuntu:
  New

Bug description:
  Occurs since an update around March 2 Ubuntu 24.04.

  Bitbake is broken due to file permission problem.

  Traceback (most recent call last):
File "/home/hains/openpli-oe-core/bitbake/bin/bitbake-worker", line 268, in 
child
  bb.utils.disable_network(uid, gid)
File "/home/hains/openpli-oe-core/bitbake/lib/bb/utils.py", line 1653, in 
disable_network
  with open("/proc/self/uid_map", "w") as f:
  PermissionError: [Errno 1] Operation not permitted

  Test code

  with open("/proc/self/uid_map", "w") as f:
f.write("%s %s 1" % (1000, 1000))

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: dash 0.5.12-6ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 14:34:08 2024
  InstallationDate: Installed on 2023-03-24 (350 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: dash
  UpgradeStatus: Upgraded to noble on 2024-01-10 (58 days ago)

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


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

[Touch-packages] [Bug 2056488] Re: audio output defaults to dummy output

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  audio output defaults to dummy output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  audio defaults to dummu output instead of HDMI audio
  Using Ubuntu 23.04
  Audio need to stay at HDMI output from shutdown or restart 
  Alsamixer did not repair problem and am unable to download Pulse Audio

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  photom  923 F wireplumber
   /dev/snd/controlC1:  photom  923 F wireplumber
   /dev/snd/seq:photom  917 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 14:27:41 2024
  InstallationDate: Installed on 2023-07-08 (243 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-17 (111 days ago)
  dmi.bios.date: 11/18/2016
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M PLUS/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 2056194] Re: Networking broken in early boot on Oracle Native instances

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Networking broken in early boot on Oracle Native instances

Status in cloud-images:
  New
Status in cloud-init package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  BACKGROUND:

  cloud-init-local.service runs before networking has started. On non-
  Oracle platforms, before networking has come up, cloud-init will
  create an ephemeral connection to the cloud's IMDS using DHCP to
  retrieve instance metadata. On Oracle, this normally isn't necessary
  as we boot with connectivity to the IMDS out of the box. This can be
  seen in the following Jammy instance using an SR-IOV NIC:

  2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open 
'http://169.254.169.254/opc/v2/instance/' with {'url': 
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects': 
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
  : 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} 
configuration
  2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from 
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
  2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup, 
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/', 
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
  2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open 
'http://169.254.169.254/opc/v2/instance/' with {'url': 
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects': 
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
  .3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
  2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from 
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts

  Notice the "Skip ephemeral DHCP setup, instance has connectivity".
  This means that cloud-init has determined that it already has
  connectivity and doesn't need to do any additional setup to retrieve
  data from the IMDS.

  We can also see the same behavior on a Noble paravirtualized instance:

  2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open 
'http://169.254.169.254/opc/v2/instance/' with {'url': 
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects': 
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent': 
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}} 
configuration
  2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from 
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
  2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup, 
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/', 
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
  2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open 
'http://169.254.169.254/opc/v2/instance/' with {'url': 
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects': 
True, 'method': 'GET', 'headers': {'User-Agent': 
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}} 
configuration
  2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from 
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
  2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to 
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes

  PROBLEM:

  On a Noble instance using Hardware-assisted (SR-IOV) networking, this
  is not working. cloud-init-local.service no longer has immediate
  connectivity to the IMDS. Since it cannot connect, in then attempts to
  create an ephemeral connection to the IMDS using DHCP. It is able to
  obtain a DHCP lease, but then when it tries to connect to the IMDS,
  the call just hangs. The call has no timeout, so this results in an
  instance that cannot be logged into even via the serial console
  because cloud-init is blocking the rest of boot. A simple cloud-init
  workaround is to add something along the lines of `timeout=2` to
  https://github.com/canonical/cloud-
  init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
  allows cloud-init to boot. Looking at the logs, we can see that cloud-
  init is unable to connect to the IMDS:

  2024-03-05 14:23:54,836 - ephemeral.py[DEBUG]: Received dhcp lease on ens3 
for 10.0.0.133/255.255.255.0
  2024-03-05 14:23:54,837 - url_helper.py[DEBUG]: [0/3] open 
'http://169.254.169.254/opc/v2/instance/' with {'url': 
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects': 
True, 'method': 'GET', 'timeout': 2.0, 'headers': {'User-Agent': 
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}} 
configuration
  2024-03-05 14:23:56,841 - url_helper.py[DEBUG]: Please wait 1 seconds while 

[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  fails to configure BOOTIF when using iscsi

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in open-iscsi package in Ubuntu:
  Invalid

Bug description:
  we have a bad interaction between initramfs-tools and open-iscsi,
  resulting in the boot interface not being configured.

  when the iscsi has a static address, the script `local-top/iscsi` from
  open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
  interface. The existence of this file makes configure_networking()
  skip configuring the BOOTIF later due to this code in
  `scripts/functions`:

  for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
  if [ -e "$x" ]; then
  IP=done
  break
  fi
  done

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


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

[Touch-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

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


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

[Touch-packages] [Bug 2054851] Re: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()

[Ubuntu Foundations Team Bug Bot]

The attachment "proposed fix in upstream" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Touch-packages] [Bug 2055304] Re: openssl 3.0.2 backport IgnoreUnexpectedEOF ssl config option from 3.2

[Ubuntu Foundations Team Bug Bot]

The attachment "Add IgnoreUnexpectedEOF as configuration option for
3.0.2-0ubuntu1.15" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  openssl 3.0.2 backport IgnoreUnexpectedEOF ssl config option from 3.2

Status in openssl package in Ubuntu:
  New

Bug description:
  I get "Closing connection 0 curl: (35) error:0A000126:SSL
  routines::unexpected eof while reading" accessing some web servers.
  AFAIS "SSL_OP_IGNORE_UNEXPECTED_EOF" can help here. With 3.2[0] it can
  be configured in openssl.cnf, whereas 3.0[1] cannot. Would you mind to
  backport the mini patch[2] to be configured with 3.0, too?

  Example:
  $ tail -n 3 /etc/ssl/openssl.cnf 
  [system_default_sect]
  CipherString = DEFAULT:@SECLEVEL=2
  Options = IgnoreUnexpectedEOF

  
  [0] https://www.openssl.org/docs/man3.2/man3/SSL_CONF_cmd.html
  [1] https://www.openssl.org/docs/man3.0/man3/SSL_CONF_cmd.html
  [2] 
https://github.com/openssl/openssl/commit/51cf034433d528876f3c235c5150c5acfe88f24d

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


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

[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

[Ubuntu Foundations Team Bug Bot]

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

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

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  Won't Fix
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Won't Fix
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

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


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

[Touch-packages] [Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call

[Ubuntu Foundations Team Bug Bot]

The attachment "dd-count.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  unmkinitramfs: wrong and unneeded count= in a dd call

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Speaking about this line in unmkinitramfs:

  113: dd < "$initramfs" skip=$start count=$((end - start))
  iflag=skip_bytes 2> /dev/null |

  dd's block size is 512 by default. iflag=skip_bytes does not change
  that. Both $end and $start are byte-offsets. Hence the count is
  ($end-$start) blocks or ($end-$start)*512 bytes which is wrong.

  Anyways, the script just works because the count is unneeded: dd's
  output is piped into cpio which stops on the first end-of-archive
  marker, no matter how much data it is fed with.

  I think it is the best to just drop the count option (the patch is
  attached).

  If there is still a need to explicitly limit data fed to cpio, dd is
  impractical in this case. The only way to count= in bytes is bs=1,
  which makes dd extremely slow on lengthy data chunks. For example
  ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded
  uncompressed cpio archives of such sizes:

  77312
  7200768
  78615040

  A combo of dd+head could be used intead to skip and count
  respectively:

  113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null |
  head -c$((end - start)) |

  Or even tail+head:

  113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) |

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


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

[Touch-packages] [Bug 2054171] Re: dhcpcd hook breaks when using libc6-prof's libc.so.6

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  dhcpcd hook breaks when using libc6-prof's libc.so.6

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I have the libc6-prof package installed to provide a frame pointer
  enabled libc.so.6.

  I have a custom configuration file in /etc/ld.so.conf.d putting
  /lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker
  search paths. (I really like having frame pointers!)

  This confuses the `multiarch_dir=$(ldd /usr/sbin/dhcpcd | sed -En
  's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p')` line in /usr/share/initramfs-
  tools/hooks/dhcpcd because the libc.so.6 path is different.

  Default ldd output:

  ```
  ldd /usr/sbin/dhcpcd
  linux-vdso.so.1 (0x7fff9a735000)
  libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7f50d280)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240)
  /lib64/ld-linux-x86-64.so.2 (0x7f50d2f27000)
  ```

  My ldd output:

  ```
  ldd /usr/sbin/dhcpcd
  linux-vdso.so.1 (0x7fff802db000)
  libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7fce87e0)
  libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 
(0x7fce87a0)
  /lib64/ld-linux-x86-64.so.2 (0x7fce88514000)
  ```

  ```
  -libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240)
  +libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0)
  ```

  When running the modified search paths, `ldd /usr/sbin/dhcpcd | sed
  -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p'` evaluates to an empty
  string and exits 0. This results in `copy_exec
  "/usr/lib//dhcpcd/dev/udev.so"`, which breaks that script.

  This in turn breaks initramfs.

  ```
  Processing triggers for linux-image-6.5.0-17-generic (6.5.0-17.17) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-6.5.0-17-generic
  E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.
  update-initramfs: failed for /boot/initrd.img-6.5.0-17-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-6.5.0-17-generic (--configure):
   installed linux-image-6.5.0-17-generic package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-6.5.0-17-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  I can work around the issue by hacking up the dhcpcd hook or by
  modifying the dynamic link path search order, running `ldconfig`, then
  `update-initramfs -u`.

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


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

[Touch-packages] [Bug 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Monitor Not Detected when Connected to Belkin Docking Station via
  DisplayPort on Ubuntu

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear Ubuntu Bug Tracking Team,

  I hope this message finds you well. I am writing to report an issue I
  have encountered while using Ubuntu.

  Issue Description:
  When connecting my BenQ monitor to a Belkin docking station via DisplayPort, 
Ubuntu fails to detect the monitor. Other monitor connected to same docking 
station via hdmi is working

  
  Thank you for your attention to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 12:33:13 2024
  DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac]
  InstallationDate: Installed on 2020-06-01 (1355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago)
  dmi.bios.date: 07/17/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2SET31W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20SDCTO1WW
  dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  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

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


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

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

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-5.15.0-94-generic 5.15.0-94.104~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:
  Invalid

Bug description:
  no details

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-94-generic 5.15.0-94.104~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-92.102~20.04.1-generic 5.15.131
  Uname: Linux 5.15.0-92-generic x86_64
  NonfreeKernelModules: vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb 15 06:58:38 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-09-24 (509 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  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.10
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-94-generic 5.15.0-94.104~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/2054153/+subscriptions


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

[Touch-packages] [Bug 2054121] Re: Random Freezing

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Random Freezing

Status in xorg package in Ubuntu:
  New

Bug description:
  Random lockups in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 09:08:41 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
  InstallationDate: Installed on 2024-02-16 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3JKT3CA
  dmi.board.name: 32DD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305435660291
  dmi.chassis.type: 35
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
  dmi.product.family: ThinkStation P350 Tiny
  dmi.product.name: 30EF004VUS
  dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
  dmi.product.version: ThinkStation P350 Tiny
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2052859] Re: Windows go to behind others when clicking with mouse

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Windows go to behind others when clicking with mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
  bug appears.

  When there are several windows on top of each other, clicking within
  the topmost window, the window seems to disappear.  Actually, the
  window is still there, but just goes behind another window, that comes
  in front of the clicked window.  The program in the window that is
  clicked will not notice the click.

  This does not happen with all programs.  Mines is a good example
  program.  If the window fills full screen, this happens, but if it is
  smaller, only partially covering the screen, it does not happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.fabric-imex-mgmt:
   DeviceFileMinor: 4323
   DeviceFileMode: 256
   DeviceFileModify: 1
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..2d.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  550.40.07  Thu Jan 18 
07:30:58 UTC 2024
   GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 10 17:56:32 2024
  DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
  InstallationDate: Installed on 2012-12-22 (4067 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
  dmi.bios.date: 02/28/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.J0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Fri Feb  9 20:05:59 2024
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.7-3ubuntu2.7

To manage notifications 

[Touch-packages] [Bug 2052755] Re: CPU spikes observed when playing youtube videos

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  CPU spikes observed when playing youtube videos

Status in xorg package in Ubuntu:
  New

Bug description:
  CPU is going almost 100% and videos feel laggy. Playing just one video
  on youtube , the cpu goes to almost 70% usage and then if 2 or 3 tabs
  are opened for video playback, the cpu goes to 100% usage. Its a
  recent phenomenon. I tried uninstalling and reinstalling nvidia
  drivers, still the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  9 06:45:36 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA106 [RTX A2000 12GB] [10de:2571] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:1611]
  InstallationDate: Installed on 2023-08-16 (176 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=44a159e4-2bf4-4656-bf23-dd33975faef6 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.00
  dmi.board.name: A320M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.00:bd07/16/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.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

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


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

[Touch-packages] [Bug 2052717] Re: USB sound card not detected

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  USB sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Xubuntu 22.04. Updating the kernel from 5.15.0-92 to 5.15.0-94 results
  in my headset and webcam no longer being recognized.

  Rebooting back into the old kernel, and everything works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136
  Uname: Linux 5.15.0-94-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:brad   4147 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Feb  8 17:37:04 2024
  InstallationDate: Installed on 2022-08-05 (552 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4501
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI)
  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.:bvr4501:bd04/19/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):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: ASUS

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


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

[Touch-packages] [Bug 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Raspberry Pi mouse buttons left and right unresponsive

Status in xorg package in Ubuntu:
  New

Bug description:
  Using the event tracker tool 
  (
  xmodmap -pp > ~/xmodmap-pp
  xev | grep -i button 
  ), buttons 4 and 5 are responsive, optical works (the cursor moves across the 
screen).

  Left and right click buttons are unresponsive. Mouse connected via
  USB.

  MOUSE INFO:
  Raspberry Pi Mouse
  CAN ICES-3 (B)/NMB-3(B)
  Model No.: RPI-MOUSE

  This issue has been extant every since I have tried to use this mouse.
  Currently using Ubuntu Mantic Minotaur (23.10)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 21:24:11 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
  InstallationDate: Installed on 2023-12-16 (45 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 00V66M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3510
  dmi.product.sku: 09ED
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2051367] Re: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When using 2 external monitors via a dual HDMI adapter plugged on the
  usb-c port, when i go to play sound at all, 1 of the external monitors
  is always selected as the default output device when this should still
  be the laptop internal speakers. Annoying as hell to have to go into
  the settings everytime i switch the laptop on and there is no sound on
  sound output. It would be great if you could fix it so it leaves its
  always "laptop internal speakers" as default.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131
  Uname: Linux 5.15.0-92-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  smiler 7478 F pulseaudio
   /dev/snd/pcmC2D0c:   smiler 7478 F...m pulseaudio
   /dev/snd/controlC1:  smiler 7478 F pulseaudio
   /dev/snd/controlC0:  smiler 7478 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 14:17:02 2024
  InstallationDate: Installed on 2022-02-04 (720 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DTCN25WW(V1.11)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ARE05
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
  dmi.product.family: IdeaPad 5 14ARE05
  dmi.product.name: 81YM
  dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
  dmi.product.version: IdeaPad 5 14ARE05
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 2051292] Re: blutooth

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  blutooth

Status in bluez package in Ubuntu:
  New

Bug description:
  when I connect to my headset it's work couple of seconds or  minutes
  then disconnect  alone

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 22:15:26 2024
  InstallationDate: Installed on 2023-06-27 (211 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Inspiron 3721
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 044D20
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3721
  dmi.product.sku: Inspiron 3721
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:2A:70:BE:D0:62  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5227 acl:60 sco:0 events:440 errors:0
TX bytes:36549 acl:67 sco:0 commands:391 errors:0

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


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

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Touch-packages] [Bug 2049995] Re: System volume doesn't change volume

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  System volume doesn't change volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, as described here https://askubuntu.com/questions/1487030/system-
  volume-doesnt-change-app-volume, I also have this problem.

  I've already tried to boot with a Manjaro USB live with Gnome and
  there the volume works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  japimentel   8590 F wireplumber
   /dev/snd/controlC0:  japimentel   8590 F wireplumber
   /dev/snd/seq:japimentel   8580 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 10:28:26 2024
  InstallationDate: Installed on 2023-11-21 (61 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MLCN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Pro 7 14APH8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN21WW:bd07/12/2023:br1.21:efr1.21:svnLENOVO:pn82Y8:pvrYogaPro714APH8:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrYogaPro714APH8:skuLENOVO_MT_82Y8_BU_idea_FM_YogaPro714APH8:
  dmi.product.family: Yoga Pro 7 14APH8
  dmi.product.name: 82Y8
  dmi.product.sku: LENOVO_MT_82Y8_BU_idea_FM_Yoga Pro 7 14APH8
  dmi.product.version: Yoga Pro 7 14APH8
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 2049972] Re: Can't change screen brightness

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Can't change screen brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  HP Victus with Radeon 6500 graphics, Ubuntu 22.04.3. When pressing
  functions key, a brightness popup appears, but the brightness is still
  maximum. I tried to update GRUB with adding "acpi_osi=Linux
  acpi_backlight=vendor" but after that even the popup doesn't show by
  pressing functions key, nothing really happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 20 13:35:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Hewlett-Packard Company Device [103c:8a3f]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Cezanne [103c:8a3f]
  InstallationDate: Installed on 2024-01-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: HP Victus by HP Gaming Laptop 15-fb0xxx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=82abbfb4-55a4-49f1-aaf8-f00a4d56e35f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2023
  dmi.bios.release: 15.18
  dmi.bios.vendor: AMI
  dmi.bios.version: F.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8A3F
  dmi.board.vendor: HP
  dmi.board.version: 35.44
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 35.44
  dmi.modalias: 
dmi:bvnAMI:bvrF.18:bd08/11/2023:br15.18:efr35.44:svnHP:pnVictusbyHPGamingLaptop15-fb0xxx:pvr:rvnHP:rn8A3F:rvr35.44:cvnHP:ct10:cvrChassisVersion:sku9Q377EA#AKD:
  dmi.product.family: 103C_5335M7 HP VICTUS
  dmi.product.name: Victus by HP Gaming Laptop 15-fb0xxx
  dmi.product.sku: 9Q377EA#AKD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2037595] [gpgme1.0/focal] verification still needed

[Ubuntu Foundations Team Bug Bot]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  _gpgme_io_select breaks when more than 1024 file descriptors are open

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in gpgme1.0 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Launchpad's buildd-manager is a complex event-driven daemon that
  manages several hundred builders on production.  As such, it can often
  end up with more than 1024 file descriptors open.  It also uses gpgme
  from time to time to fetch signing keys for PPAs when dispatching
  builds that involve PPAs.

  On focal (and also on jammy), this breaks because `_gpgme_io_select`
  is implemented using select(2), whose manual page says: "WARNING:
  select() can monitor only file descriptors numbers that are less than
  FD_SETSIZE (1024)—an unreasonably low limit for many modern
  applications—and this limitation will not change.  All modern
  applications should instead use poll(2) or epoll(7), which do not
  suffer this limitation."  This is exactly the limitation we're running
  into, resulting in mysterious "Too many open files" errors despite
  resource limits being set to more than comfortable values.

  Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
  
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
  and lunar has that fix.  focal and jammy do not (there may be a
  similar problem with older LTSes too, but I only care about it back to
  focal).  buildd-manager currently runs on focal.

  We've been running buildd-manager with a cherry-picked fix from
  upstream for a few weeks now, and I'd like to get that SRUed back into
  Ubuntu so that we don't accidentally lose this patch in the event of a
  security update or similar.

  [Test Plan]

  William Grant provided this minimal reproducer:

  ```
  root@tmp:~# python3
  Python 3.8.10 (default, May 26 2023, 14:05:08)
  [GCC 9.4.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import gpg
  >>> c = gpg.Context()
  >>> list(c.keylist())
  []
  >>> fs = []
  >>> for i in range(1024):
  ... fs.append(open('/dev/null'))
  ...
  >>> list(c.keylist())
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
  key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in 
op_keylist_next
  raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in 
op_keylist_next
  errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
  raise GPGMEError(retval, extradata)
  gpg.errors.GPGMEError: GPGME: Too many open files
  ```

  [Where problems could occur]

  `_gpgme_io_select` is pretty central to gpgme, so if something is
  wrong the package will be pretty broken.  On the other hand, that also
  means any glaring problems are likely to be caught by the package's
  test suite.

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


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

[Touch-packages] [Bug 2049119] Re: my audio wont work at all no mater what i do

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  my audio wont work at all no mater what i do

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i had updated some stuff such as chrome and fire fox and after that my
  volume keys stopped working then my volume would turn up and down on
  its own then i couldn't even adjust the volume from settings and it
  would be on full blast and now its just wont work anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gage   1069 F wireplumber
   /dev/snd/controlC0:  gage   1069 F wireplumber
   /dev/snd/seq:gage   1062 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Jan 11 18:36:25 2024
  InstallationDate: Installed on 2023-12-19 (23 days ago)
  InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2023
  dmi.bios.release: 15.72
  dmi.bios.vendor: AMI
  dmi.bios.version: F.72
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B7
  dmi.board.vendor: HP
  dmi.board.version: 28.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 28.23
  dmi.modalias: 
dmi:bvnAMI:bvrF.72:bd10/04/2023:br15.72:efr28.23:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.23:cvnHP:ct10:cvrChassisVersion:sku26Z02UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-fq0xxx
  dmi.product.sku: 26Z02UA#ABA
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 2048012] Re: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Line Out, N/A] No sound at all

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Line Out, N/A] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no sound at all. Sometimes restarting several times gets the
  sound back but the sound is cracking.And sometimes no sound at all
  even after restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arjun  8184 F pipewire-media-
arjun  8185 F pulseaudio
   /dev/snd/seq:arjun  8183 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  4 10:12:29 2024
  InstallationDate: Installed on 2022-03-13 (661 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arjun  8184 F pipewire-media-
arjun  8185 F pulseaudio
   /dev/snd/seq:arjun  8183 F pipewire
  Symptom_Jack: Line Out, N/A
  Symptom_Type: No sound at all
  Title: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Line Out, N/A] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.0
  dmi.board.name: 0XGX0C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.0:bd06/12/2023:br1.25:svnDellInc.:pnInspiron3501:pvr:rvnDellInc.:rn0XGX0C:rvrA01:cvnDellInc.:ct10:cvr:sku0A25:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3501
  dmi.product.sku: 0A25
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status

[Ubuntu Foundations Team Bug Bot]

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

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  upgraded from 22.04 -> 24.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: systemd-resolved 253.5-1ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Jan  3 21:06:55 2024
  ErrorMessage: installed systemd-resolved package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-27 (311 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.1ubuntu5
   apt  2.7.6
  SourcePackage: systemd
  Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: 
installed systemd-resolved package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
  mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158

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


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

[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Jammy:
  New
Status in tzdata source package in Lunar:
  New
Status in tzdata source package in Mantic:
  New

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

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


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

[Touch-packages] [Bug 1964506] [iputils/focal] verification still needed

[Ubuntu Foundations Team Bug Bot]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

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

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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

[Touch-packages] [Bug 2046802] Re: External display stay blank when connected through the docking station (HP USB-C Dock G5) but is OK when directly connected

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  External display stay blank when connected through the docking station
  (HP USB-C Dock G5) but is OK when directly connected

Status in xorg package in Ubuntu:
  New

Bug description:
  External display is detected and X believes it is OK as the desktop
  correctly extends to the 2nd monitor but said monitor remains blank.
  It used to work a couple of days ago but I guess some upgrade is the
  cause. I tried to downgrade amd64-microcode and linux-firmware, to no
  avail : dmesg still shows issues with drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Dec 18 12:14:54 2023
  DistUpgraded: 2023-12-18 10:58:52,052 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Barcelo [103c:8b5c]
  InstallationDate: Installed on 2023-08-08 (132 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=d29d3432-7c6f-4376-a050-c86365d7b922 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-12-18 (0 days ago)
  dmi.bios.date: 04/25/2023
  dmi.bios.release: 2.1
  dmi.bios.vendor: HP
  dmi.bios.version: V78 Ver. 01.02.01
  dmi.board.name: 8B5C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 53.1D.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 83.29
  dmi.modalias: 
dmi:bvnHP:bvrV78Ver.01.02.01:bd04/25/2023:br2.1:efr83.29:svnHP:pnHPProBook44514inchG10NotebookPC:pvr:rvnHP:rn8B5C:rvrKBCVersion53.1D.00:cvnHP:ct10:cvr:sku852U8ES#UUZ:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 445 14 inch G10 Notebook PC
  dmi.product.sku: 852U8ES#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2046639] Re: qt DialogMirror.py argument 1 has unexpected type 'float' while selecting best mirror

[Ubuntu Foundations Team Bug Bot]

The attachment "patch to cast float to int for progress dialog" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  qt DialogMirror.py argument 1 has unexpected type 'float' while
  selecting best mirror

Status in software-properties package in Ubuntu:
  New

Bug description:
  While selecting the best mirror in software-properties-qt, there's a
  traceback:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line 
227, in on_report_progress
  self.dialog.setValue(frac*100)
  TypeError: setValue(self, progress: int): argument 1 has unexpected type 
'float'

  I didn't investigate thoroughly, but it looks like maybe someone
  updated how progress was being updated but didn't check types or test
  all the way through before releasing.  It can be fixed with a simple
  patch:

  diff --git a/softwareproperties/qt/DialogMirror.py 
b/softwareproperties/qt/DialogMirror.py
  index 972c4fb..4d1c150 100644
  --- a/softwareproperties/qt/DialogMirror.py
  +++ b/softwareproperties/qt/DialogMirror.py
  @@ -223,7 +223,7 @@ class DialogMirror(QDialog):
 def on_report_progress(self, current, max, borders=(0,1), mod=(0,0)):
 #self.dialog.setLabelText(_("Completed %s of %s tests") % \
 #   (current + mod[0], max + mod[1]))
  -  frac = borders[0] + (borders[1] - borders[0]) / max * current
  +  frac = int(borders[0] + (borders[1] - borders[0]) / max * current)
 self.dialog.setValue(frac*100)

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy pkgname software-properties-qt
  software-properties-qt:
Installed: 0.99.39
Candidate: 0.99.39
Version table:
   *** 0.99.39 500
  500 https://mirror.it.ubc.ca/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status
  N: Unable to locate package pkgname

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


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

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

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-5.15.0-91-generic 5.15.0-91.101~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:
  Invalid

Bug description:
  got fail massage at end up big update & just tried to auto send report
  here. not sure what needs to be included

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 11 12:37:24 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-02-16 (1027 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~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/2046179/+subscriptions


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

[Touch-packages] [Bug 2046076] Re: cursor dissapears when I type

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  cursor dissapears when I type

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using version Ubuntu 23.10 (gnome), and when I type in the default
  terminal the cursor dissapears when I'm typing and I have the cursor
  placed on the terminal window, this also happens when Im using
  IntellyJ IDEA community

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..29.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 18:35:58 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660 SUPER] 
[19da:5527]
  InstallationDate: Installed on 2023-12-10 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=UUID=655899b5-3bf1-4977-87ff-935d66071b9b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: 229200
  dmi.board.name: A320M-A PRO (MS-7C51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 229200
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/08/2020:br5.14:svnMegaport:pn229200:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:sku34:
  dmi.product.family: 229200
  dmi.product.name: 229200
  dmi.product.sku: 34
  dmi.product.version: 1.0
  dmi.sys.vendor: Megaport
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2045817] Re: Bluetooth issues in Ubuntu 23.10

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Bluetooth issues in Ubuntu 23.10

Status in bluez package in Ubuntu:
  New

Bug description:
  similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14
  generic kernels.

  ❯ uname -a; lsb_release -a
  Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC 
Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 23.10
  Release: 23.10
  Codename: mantic

  2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
  2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
  2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
  2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware 
version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode
  2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
  2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
  2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | 
branchlink2
  2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
  2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
  2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
  2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
  2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
  2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon 
time
  2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
  2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
  2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
  2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
  2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
  2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
  2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
  2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
  2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
  2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
  2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
  2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
  2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
  2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
  2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
  2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd 
Id
  2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
  2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | 
l2p_control
  2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | 
l2p_duration
  2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | 
l2p_mhvalid
  2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
  2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | 
lmpm_pmg_sel
  2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
  2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | 
flow_handler
  2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
  2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
  2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
  2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
  2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
  2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
  2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
  2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 

[Touch-packages] [Bug 2045722] Re: Ubuntu freeze randomly

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Ubuntu freeze randomly

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes happens when I leave it (probably screen lock), sometimes
  happens when I about to shutdown, sometimes happens when running. The
  log shows it is related to xorg or nvidia.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  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
  Date: Wed Dec  6 10:53:21 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] 
[103c:878e]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] 
[103c:878e]
  InstallationDate: Installed on 2021-06-05 (913 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.7
  dmi.bios.vendor: AMI
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2045196] Re: two monitors have night light, one does not

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  two monitors have night light, one does not

Status in xorg package in Ubuntu:
  New

Bug description:
  Two monitors have night light, one does not. It's on a scheduler
  (although I don't think the scheduler is turning it off properly once
  it's on, either) for sunset and sunrise. Including a screen shot.
  Tried turning it off and on again in display settings to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 16:43:52 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed
   amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G 
OC [1462:3418]
  InstallationDate: Installed on 2023-10-30 (30 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Micro-Star International Co., Ltd MS-7B86
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450-A PRO MAX (MS-7B86)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B86
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 4.0
  dmi.sys.vendor: Micro-Star International Co., Ltd
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2045088] Re: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not permitted

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade:
  unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new':
  Operation not permitted

Status in perl package in Ubuntu:
  New

Bug description:
  I was trying to exit Mozilla Thunderbird.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: perl-modules-5.34 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 28 06:27:18 2023
  DpkgTerminalLog:
   Preparing to unpack .../perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb ...
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  DuplicateSignature:
   package:perl-modules-5.34:5.34.0-3ubuntu1.2
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-05-17 (2021 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: perl
  Title: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: 
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  UpgradeStatus: Upgraded to jammy on 2022-08-13 (472 days ago)

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


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

[Touch-packages] [Bug 2045072] Re: Bug on galaky book2 750xed

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Bug on galaky book2 750xed

Status in xorg package in Ubuntu:
  New

Bug description:
  I had to set nomode parameter to avoid the screen become dark and then
  change the line of the file /etc/default/grub

  from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  then add to the file /etc/systemd/logind.conf

  the instructions:

  HandleLidSwitch=ignore
  HandleLidSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:00:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe 
Graphics] [144d:c1c6]
  InstallationDate: Installed on 2023-11-13 (15 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P13CFG.039.230726.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP750XED-KC2IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
  dmi.product.family: Galaxy Book2
  dmi.product.name: 750XED
  dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
  dmi.product.version: P13CFG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Debian:
  New

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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


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

[Touch-packages] [Bug 2043904] Re: User desktop does not work and Ubuntu Desktop settings not found

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  User desktop does not work and Ubuntu Desktop settings not found

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  This issue started with the upgrade to Ubuntu 23.04 and is only happening to 
1 user on the machine.
  When logging into the laptop, it is apparent that the desktop is not loading 
(it's supposed to have files saved on it). I can still start application 
because the dock shows and I can press the Super key to view the workspaces.
  When going to Setting and selecting Ubuntu Desktop, there is a frowning face 
and the message: "No ubuntu settings found" then recommends filling a bug 
report (the desktop setting page displays for a second or so then this message 
appears).
  I've looked thru forums but couldn't find a similar issue.
  I tried looking for the desktop file but couldn't find anything wrong.
  I tried, from the command line, removing Ubuntu-Desktop and adding it again 
but it didn't make a difference.
  I created a new user and it doesn't have that issue.
  In my Home directory in Nautilus, I do have a desktop folder which contains 
the files that are supposed to be accessible from my desktop.
  I was hoping upgrading to 23.10 would solve this issue but there was no 
difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-desktop 1.524
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 18 16:10:12 2023
  InstallationDate: Installed on 2020-11-20 (1093 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to mantic on 2023-10-25 (25 days ago)

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


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

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

[Ubuntu Foundations Team Bug Bot]

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

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

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

Status in apparmor package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.12-4ubuntu5.3
  ProcVersionSignature: Ubuntu 4.15.0-219.230~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-219-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov 17 18:49:22 2023
  DuplicateSignature:
   package:apparmor:2.12-4ubuntu5.3
   Preparing to unpack .../06-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MWiOD0/06-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-09-05 (2265 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-219-generic 
root=UUID=e90319c7-172e-4d34-bd93-9a8d38a0672e ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: apparmor
  Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new 
apparmor package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-11-18 (0 days ago)

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


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

[Touch-packages] [Bug 2043598] Re: A vertical strip on the screen is unresponsive or does not allow iteration

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  A vertical strip on the screen is unresponsive or does not allow
  iteration

Status in xorg package in Ubuntu:
  New

Bug description:
  A fraction of the screen, located on the right side of the entire
  vertical, that is, from the minimize, restore and maximize buttons to
  the bottom of the screen, the click action (single or double) does not
  work.

  Today I am forced to make the window smaller to be able to close it,
  for example.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:50:44 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus: virtualbox/7.0.6, 6.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0792]
  InstallationDate: Installed on 2023-11-03 (11 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: Dell Inc. Vostro 14-3468
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=b18f1fb8-30b8-49f3-81fe-227de68fb188 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2019
  dmi.bios.release: 3.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.3.0
  dmi.board.name: 02HKXD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.3.0:bd01/17/2019:br3.3:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn02HKXD:rvrA00:cvnDellInc.:ct9:cvr:sku0792:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.product.sku: 0792
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Mantic:
  New
Status in linux source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the needed driver 
(on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  
usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst

  Test case on Microsoft Surface Laptop 4: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs).

  [ Apport report ]

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ubuntu2.3
   libpam-modules-bin 1.4.0-11ubuntu2.3
   libpam0g 1.4.0-11ubuntu2.3
   libpcre2-8-0 10.39-3ubuntu0.1
   libpng16-16 1.6.37-3build5
   libseccomp2 2.5.3-2ubuntu2
   libselinux1 3.3-1build2
   libsemanage-common 3.3-1build2
   libsemanage2 3.3-1build2
   libsepol2 3.3-1build1
   libsmartcols1 2.37.2-4ubuntu3
   libssl3 3.0.2-0ubuntu1.8
   libstdc++6 12.1.0-2ubuntu1~22.04
   libsystemd0 249.11-0ubuntu3.6
   libtasn1-6 4.18.0-4build1
   libtext-charwidth-perl 0.04-10build3
   

[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  [ Impact ]

  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the SPI and PCI 
driver (on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst

  Test case on MacBook Pro 2017 laptops: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs).

  [ Remaining original report ]

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

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


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

[Touch-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Ubuntu Foundations Team Bug Bot]

The attachment "use-triggers.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

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


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

[Touch-packages] [Bug 2043492] Re: Installed 23.10 on Huawei 16s. Speakers don't work. When I plug in headphones, the speakers work. the operating system seems to have the two switched. Also, on googl

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Installed 23.10 on Huawei 16s.  Speakers don't work.  When I plug in
  headphones, the speakers work.  the operating system seems to have the
  two switched.  Also, on google meets, it cannot find a sound device.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noe2350 F pipewire
noe2357 F wireplumber
   /dev/snd/seq:noe2350 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 16:42:30 2023
  InstallationDate: Installed on 2023-11-01 (13 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.23
  dmi.board.asset.tag: N/A
  dmi.board.name: CREF-XX-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1010
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1010
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.23:bd11/08/2022:br1.23:efr1.23:svnHUAWEI:pnCREF-XX:pvrM1010:rvnHUAWEI:rnCREF-XX-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
  dmi.product.family: MateBook
  dmi.product.name: CREF-XX
  dmi.product.sku: C100
  dmi.product.version: M1010
  dmi.sys.vendor: HUAWEI

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


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

[Touch-packages] [Bug 2043255] Re: Wayland user session terminates when screen is disabled on inactivity

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Wayland user session terminates when screen is disabled on inactivity

Status in xorg package in Ubuntu:
  New

Bug description:
  Reproducibly, the user is logged out the moment the screen gets
  disabled due to inactivity. Can be worked around by disabling the
  "screen disabling on inactivity" feature in the system settings.

  Issue started after upgrade from 23.04 to 23.10. Wayland is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 09:21:02 2023
  DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2021-08-27 (806 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
  dmi.bios.date: 05/17/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET27W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YHS00A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YHS00A00
  dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2043053] Re: Xorg/Wayland crash - maybe gnome-shell

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Xorg/Wayland crash - maybe gnome-shell

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently upgraded a Dell OptiPlex 7000 from 23.04 to 23.10 and a new
  install of Ubuntu 23.10 on a fresh Dell Latitude 7440. Both are now
  unstable, regularly crashing out of gnome with a full plain white
  screen with a sad terminal and "Oh no! Something has gone wrong." and
  the only option being  to Log Out.

  It is regularly triggered when starting up totem/video or rhythmbox
  and youtube in a browser, so perhaps audio or video related on both X
  and Wayland. Also can be triggered on X with `Alt-F2 r`.

  Has been happening for 2 weeks, regularly updating the system with
  `wajig update; wajig distupgrade`. The issue remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 08:20:50 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Raptor Lake-P [Iris Xe Graphics] [1028:0c0b]
  InstallationDate: Installed on 2023-10-19 (20 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0982JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.asset.tag: 080753
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd09/12/2023:br1.8:efr1.6:svnDellInc.:pnLatitude7440:pvr:rvnDellInc.:rn0982JK:rvrA03:cvnDellInc.:ct10:cvr:sku0C0B:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7440
  dmi.product.sku: 0C0B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Ubuntu Foundations Team Bug Bot]

The attachment "1-23.2.1-1ubuntu4.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Mantic:
  New
Status in mesa source package in Noble:
  Confirmed

Bug description:
  This was reported by someone else upstream and is already fixed by
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions


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

[Touch-packages] [Bug 2042970] Re: no sound anywhere

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  no sound anywhere

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No problems up until recently.
  After upgrading to 23.04 (and then to 23.10) I have no more sound anywhere.
  I have investigated the usual suspects (I'm a Ubuntu newbie though): alas, I 
found nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henkie 2542 F wireplumber
   /dev/snd/seq:henkie 2525 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 18:52:16 2023
  InstallationDate: Installed on 2022-04-19 (567 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  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: Upgraded to mantic on 2023-11-04 (4 days ago)
  dmi.bios.date: 10/30/2009
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0F327M
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/30/2009:br1.8:efr1.8:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0F327M:rvr:cvnDellInc.:ct8:cvr:sku:
  dmi.product.name: Latitude E6500
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 2042823] Re: Login blank background (gray) after update

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Login blank background (gray) after update

Status in xorg package in Ubuntu:
  New

Bug description:
  Today I booted up and the update manager came to inform me I had
  updates (system was recently updated). I chose to do them because I'm
  having issues with HDMI audio (and audio in general, only headset via
  USB works) and it is an NVIDIA GPU.

  However after reboot, the login screen is just blank with only the
  gray background. It is still the GUI but just no login
  box/logo/anything else.

  I chose xorg as the issue but I'm not certain of it. Not sure how to
  troubleshoot this as I'm unfamiliar with the inner workings of this.

  I have since attempted to reinstall the NVIDIA drivers using apt purge
  ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as
  well as reinstalling ubuntu-desktop and related components. I can
  still log in via terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Nov  6 11:14:02 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed
   virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev 
a1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] 
[1043:882e]
  InstallationDate: Installed on 2021-11-03 (732 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4201
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI)
  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.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):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: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2042772] Re: Display corrupted/freeze

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Display corrupted/freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  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
  Date: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Keyboard navigation in the Show Applications menu

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello.

  My bug, if it is one, is in Wayland, or more likely in new desktop icon 
management thingy, which was introduced with one of the last Ubuntu versions.
  I can't navigate the "Show Applications" menu with the keyboard when I go 
into a subfolder. This means that I can navigate in "Show Applications" with 
the keyboard as long as I stay at the top level. But when I go to a folder that 
contains several programs, such as the "Utilities" folder, the keyboard 
navigation no longer works. The cursor will stuck no matter which arrow key I 
press. Even the Tab key is of no use. I've already searched for this problem on 
the Internet, but couldn't find it. Either I'm the only one who has this 
problem, or most others simply prefer to use the mouse to navigate. I only use 
the keyboard when possible. I am a heavy keyboard/hotkey user.
  The problem has existed for me for a long time. It either came with the 
switch to Wayland or with the switch to the new desktop icon management thingy. 
It's just a small problem, but for a massive keyboard user, it's really 
annoying. And definitely also for people who can't use a mouse.

  Kind regards
  Chris

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 11:22:55 2023
  DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M] 
[1043:05db]
  InstallationDate: Installed on 2021-09-16 (779 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: P35C-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: P35C-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2041789] Re: amd 7840, ubuntu 22.04, display goes to wrong

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  amd 7840, ubuntu 22.04, display goes to wrong

Status in xorg package in Ubuntu:
  New

Bug description:
  release version: Ubuntu 22.04.3 LTS
  kernel: linux-oem-22.04d, others just the default of the official release, 
with update

  the screen display goes to white or black or full of stripe, but I can still 
move the pointer. I can restore the display by lock and unlock the screen. 
there is a photo attached.
  I have test the default kernel or linux-oem-22.04c linux-oem-22.04d, the 
problem dont go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1004.4-oem 6.5.3
  Uname: Linux 6.5.0-1004-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 13:16:07 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1004-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2041728] Re: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o subprocesso instalado, do pacote initramfs-tools, o script post-installation retornou erro do st

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o
  subprocesso instalado, do pacote initramfs-tools, o script post-
  installation retornou erro do status de saída 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  from the system itself
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.4
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 28 14:18:03 2023
  ErrorMessage: o subprocesso instalado, do pacote initramfs-tools, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2023-07-03 (116 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: o 
subprocesso instalado, do pacote initramfs-tools, o script post-installation 
retornou erro do status de saída 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/2041728/+subscriptions


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

[Touch-packages] [Bug 2041700] Re: release upgrade to 23.04 failed on Odroid N2+

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => python3-defaults (Ubuntu)

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

Title:
  release upgrade to 23.04 failed on  Odroid N2+

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Failure during release upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: python3 3.11.2-1
  Uname: Linux 5.15.0-odroid-arm64 aarch64
  ApportVersion: 2.26.1-0ubuntu2.1
  AptOrdering: NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudBuildName: server
  CloudSerial: 20220423
  Date: Fri Oct 27 22:58:30 2023
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: python3-defaults
  Title: package python3 3.11.2-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to lunar on 2023-10-27 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]
  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: 2022-06-28T20:42:18.309253

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


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

[Touch-packages] [Bug 2040615] Re: Xorg freeze

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  the screen regularly freezes sometime when using some application and
  also sometime when doing nothing i have tried reisub command but it
  has no effect

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-87.97~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-87-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  535.104.12  Release 
Build  (dvs-builder@U16-I3-A14-4-4)  Wed Sep 20 09:32:00 UTC 2023
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 23:55:09 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation Device [8086:9ba4] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:170d]
   NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:170d]
  InstallationDate: Installed on 2023-10-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 30fa:0400  USB OPTICAL MOUSE 
   Bus 001 Device 004: ID 13d3:3563 IMC Networks Wireless_Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LHB_FX506LHB
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-87-generic 
root=UUID=3ee592ff-12a3-43bf-8dba-b143740cba7e ro quiet splash acpi=force 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LHB.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LHB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX506LHB.311:bd02/09/2022:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LHB_FX506LHB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LHB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LHB_FX506LHB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.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-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

[Ubuntu Foundations Team Bug Bot]

The attachment "UBUNTU-CORE-support-etc-default-in-writable.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale
  to the specified one. Also, *localectl* should return the current
  locale.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

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


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

[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines

[Ubuntu Foundations Team Bug Bot]

The attachment "aarch64-pauth-registers.patch" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  gdb crashes upon `run` on some arm64 machines

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon
  `run` on some arm64 machines (confirmed on Apple M-series, both under
  hypervisor and bare metal, everything else with PAC should also be
  affected).

  It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb-
  patches/20230316103904.1947447-1-luis.mach...@arm.com/.

  Debian bookworm's gdb_13.1-3 also includes the same patch as
  `aarch64-pauth-registers.patch`.

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


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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Ubuntu Foundations Team Bug Bot]

The attachment "set LXC_DEVEL to 0" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
  New

Bug description:
  Dear colleagues,

  As I can see from:
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
  - 
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

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

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

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

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

  And also, as I can see the source code that was used to build LXC
  5.0.0 in Jammy/Kinetic is not precisely the same as in the official
  LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

  I understand that Jammy is a LTS release and making any changes is a
  problem and we should go through the SRU process. But I believe that
  we have to do something at least with LXC_DEVEL to make things work
  properly.

  Kind regards,
  Alex

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


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

[Touch-packages] [Bug 2040017] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-plugins (Ubuntu)

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

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  I dont know much about

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: libasound2-plugins 1.2.7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 21 02:05:11 2023
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu2
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2022-12-23 (301 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago)

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


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

[Touch-packages] [Bug 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s

[Ubuntu Foundations Team Bug Bot]

The attachment "modemmanager-1.20.6-1ubuntu2.patch" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in /usr/share/ModemManager/fcc-
  unlock.available.d/ whose name is the PCIe ID of this specific device.
  PCIe IDs are documented here: https://cateee.net/lkddb/web-
  lkddb/MHI_BUS.html.

  Also links in this folder have no effect on the system, unless the
  user manually enable the appropriate fcc unlock script, typically by
  adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate
  modem model script.

  [ Other Info ]
   
  I am working on a debdiff, and will upload shortly

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


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

[Touch-packages] [Bug 2039429] Re: Please merge wget 1.21.4 (main) from Debian unstable

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
   Please merge wget 1.21.4 (main) from Debian unstable

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  Please merge wget 1.21.4 (main) from Debian unstable.

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


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

[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

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


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

[Touch-packages] [Bug 2039280] Re: Support IP address protocol

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Mantic:
  New

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks, regression potential should be low.

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


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

[Touch-packages] [Bug 2038998] Re: Screen artifacts/UI oddities on Wayland following Steam/Proton session

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Screen artifacts/UI oddities on Wayland following Steam/Proton session

Status in xorg package in Ubuntu:
  New

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-UBUNTU-SAUCE-no-up-apparmor-
disable-1ea37b26d720-UBU.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions


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

[Touch-packages] [Bug 2038813] Re: Nvidia Driver External Display Stability Issues

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Nvidia Driver External Display Stability Issues

Status in xorg package in Ubuntu:
  New

Bug description:
  When using an external HDMI monitor, the screen frequently goes blank
  for a few seconds. This only happens with the external monitor and not
  the integral screen of the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.12  Wed Sep 20 
09:35:17 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 10:30:44 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0c00]
 Subsystem: Dell Device [1028:0c00]
  InstallationDate: Installed on 2023-09-07 (31 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Dell Inc. Latitude 5440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-34-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0CDJ5X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: IT099142
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd07/12/2023:br1.6:efr1.3:svnDellInc.:pnLatitude5440:pvr:rvnDellInc.:rn0CDJ5X:rvrA00:cvnDellInc.:ct10:cvr:sku0C00:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5440
  dmi.product.sku: 0C00
  dmi.sys.vendor: Dell Inc.
  nvidia-settings: ERROR: An internal driver error occurred
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1957024] Re: pam-mkhomedir does not honor private home directories

[Ubuntu Foundations Team Bug Bot]

The attachment "private_homedir.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  pam-mkhomedir does not honor private home directories

Status in pam package in Ubuntu:
  New

Bug description:
  As reported in https://discourse.ubuntu.com/t/private-home-
  directories-for-ubuntu-21-04-onwards/19533/13:

  A common situation is to have a central set of users (e.g. in LDAP)
  and use pam_mkhomedir.so to create the home directory when the user
  first logs in.

  These changes do not cover this situation. The default configuration
  of pam_mkhomedir.so will result in a home directory created with 0755
  permissions.

  To make pam_mkhomedir.so create a home directory by default with
  permissions consistent with the other tools then a umask argument can
  be added to the pam_mkhomedir.so module in the file /usr/share/pam-
  configs/mkhomedir. I believe this would have to be done before
  enabling the module. The file is part of the libpam-modules package.

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


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

[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  udev issues with mantic beta

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libblockdev package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Fix Committed

Bug description:
  While installing mantic beta (on s390x, LPAR and z/VM - but this might not be 
architecture specific) I faced issues with udev.
  In my installation I've updated the installer to "edge/lp-2009141" (subiquity 
 22.02.2+git1762.1b1ee6f4  5164).

  During my installations I first noticed bad response times in case of
  dealing with devices (like enabling new devices with chzdev). chzdev
  is used during the installation, hence the installation procedure is
  also affected by this. (I mainly notice this issue in case of DASD
  ECKD disk enablements.)

  But even after after a successful (but due to this issue less snappier) 
installation, means after the post-install reboot, in the installed system I 
can find several udev related processes, like:
69448 root  20   0   31280  11944   2560 S  39.2   0.0   2:51.67 
(udev-worker)
  509 root  20   0   31276  13812   4600 S  20.6   0.0   2:07.76 
systemd-udevd
  893 root  20   0  469016  13544  10496 R  17.3   0.0   1:43.53 
udisksd  
1 root  20   0  168664  12748   8396 S  16.3   0.0   1:40.47 
systemd  
  which is not only unusual, but (as one can see) they consume quite some 
resources.
  Even the remote ssh into that system is impacted by this high load.

  So far I only see this in mantic.
  I tried 20.04.3 as well as lunar, but both do not seem to be affected by this 
udev problem.
  I neither face the bad response on device enablement, nor can see any udev 
related processes still running after post-install-reboot in the installed 
system.

  (Sometimes I could also see a growing log file 'syslog').

  I cannot say yet what is causing this, but since I see 'systemd-udevd'
  as prominent process in top, I'll first of all mark this as affecting
  systemd-udevd (or systemd).

  I've attached the outcome of some more investigations I did ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions


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

[Touch-packages] [Bug 2037698] Re: Icon theme changed after recent update

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Icon theme changed after recent update

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Recently the software got updated and all the icons of the pre-
  installed apps were changed. I tried to change the icon theme using
  gnome-tweaks. But it is of no use. I need the icons to be like the
  time of my first installation of ubuntu. I have also tried to copy the
  theme from my friend's laptop to edit the change, But this was also of
  no use. Please look into it and help me to find the solution

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 11:58:30 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) 
[103c:8778]
  InstallationDate: Installed on 2022-11-01 (331 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14s-er0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8778
  dmi.board.vendor: HP
  dmi.board.version: 14.14
  dmi.chassis.asset.tag: 5CG0172W2M
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.14
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-er0xxx
  dmi.product.sku: 3C465PA#ACJ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2036362] Re: Computer hangs randomly: screen is frozen and all inputs as well

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Computer hangs randomly: screen is frozen and all inputs as well

Status in xorg package in Ubuntu:
  New

Bug description:
  So, basically as title says, randomly display would freeze and
  computer not reacting to anything (and nothing on the screen changes,
  even the clock or something). If I was listening to music, it would
  stop as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Mon Sep 18 00:30:46 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2023-04-20 (150 days ago)
  InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:49b5 Realtek Semiconductor Corp. USB Audio
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2035061] Re: uptime -p reports incorrect output after 52 weeks

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  uptime -p reports incorrect output after 52 weeks

Status in procps package in Ubuntu:
  New
Status in procps source package in Focal:
  New
Status in procps source package in Jammy:
  New

Bug description:
  [IMPACT]

  uptime will provide incorrect data after 52 weeks. This is at least confusing 
for users utilizing this tool.
  Issue is already fixed in upstream 
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
  Latest procps releases already include this patch (procps 4.0.3 lunar/mantic)
  The fix is needed for following set of packages:
  procps | 2:3.3.17-6ubuntu2   | jammy
  procps | 2:3.3.16-1ubuntu2   | focal

  [TEST CASE]

  UPTIME="31528920 31528800"; mkfifo uptime_fifo; while true; do cat <<<$UPTIME 
> uptime_fifo; done & sudo mount -obind uptime_fifo /proc/uptime
  uptime -p
  Running above commands will result in incorrect uptime output.

  [REGRESSION POTENTIAL]

  The patch is already available in upstream, lunar/mantic releases
  already include is as well.

  [OTHER]
  Bug upstream: https://gitlab.com/procps-ng/procps/-/issues/217
  Following patch is needed for older releases: 
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749

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


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

[Touch-packages] [Bug 2035047] Re: No output/input devices listed on Settings app

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  No output/input devices listed on Settings app

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My laptop suddenly stopped playing sound, so I tried to change from
  "headset" (A2DP) to "handsfree" mode and back as it usually solves the
  problem, but this time not only did it fully stopped responding but
  also the settings app is not displaying input or output devices.

  It seems my laptop has lost its ability to connect to the "handsfree"
  mode, and this has unsynced the quick settings from the settings app.
  I tried restarting the bluetooth from the quick settings as well as
  turning my headphone on and off.

  
  ```
  set 10 23:46:15 N bluetoothd[15656]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 5C:C6:E9:1F:1D:23: Connection refused (111)
  set 10 23:46:15 N bluetoothd[15656]: src/service.c:btd_service_connect() 
a2dp-sink profile connect failed for 5C:C6:E9:1F:1D:23: Protocol not available
  set 10 23:46:15 N gnome-shell[1392]: Failed to connect device "EDIFIER 
W800BT": GDBus.Error:org.bluez.Error.Failed: br-connection-refused
  set 10 23:46:41 N bluetoothd[15656]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.freedesktop.DBus.Error.NoReply, Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  ```

  
  `lsb_release -rd` output:
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  After I marked audio in `ubuntu-bug`, this bug report page suggested
  alsa-driver as the package, but I couldn't find it in `apt` to get its
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  junior 1251 F pipewire
   /dev/snd/pcmC0D0p:   junior 1251 F...m pipewire
   /dev/snd/seq:junior 1251 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 23:44:59 2023
  InstallationDate: Installed on 2023-07-25 (47 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Zoro_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.70
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd03/04/2016:br0.0:efr2.70:svnAcer:pnAspireE5-574:pvrV1.14:rvnAcer:rnZoro_SL:rvrV1.14:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-574_100C_1.14:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-574
  dmi.product.sku: Aspire E5-574_100C_1.14
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  4k white screen on kernel-6.20 with AMD7950x

Status in Linux:
  Unknown
Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  1. AMD7950X, without any other gpu
  2. 4k display
  3. if kernel.version >= 6.14
  => the 4k display white screen

  ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354
  ps2: this bug has occured long time ago, but amd never fix it, so i can not 
upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  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
  Date: Tue Sep  5 10:46:23 2023
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
  InstallationDate: Installed on 2023-07-31 (35 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago)
  dmi.bios.date: 07/28/2023
  dmi.bios.release: 16.36
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1636
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B650M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx: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: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Screen is flickering since last kernel upgrade

Status in xorg package in Ubuntu:
  New

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

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

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


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

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

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

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

Status in alsa-driver package in Ubuntu:
  New

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

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

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


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

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

[Ubuntu Foundations Team Bug Bot]

The attachment "add-trusted-sender-arg.patch" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  rsync 3.1.3 performance regression

Status in rsync package in Ubuntu:
  New

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

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

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

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

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


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

[Touch-packages] [Bug 2028767] Re: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwe

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  error code 1

  I don't find a documentation for this error code

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.2
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   amd64-microcode:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 26 13:53:55 2023
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2023-05-20 (67 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.2 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  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/2028767/+subscriptions


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

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

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  -- initramfs-tools

  [Impact]

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

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

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

  [Where problems could occur]

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

  [Other Info]
  Original bug report

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

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

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

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


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

[Touch-packages] [Bug 2011574] Re: rsyslogd: /dev/console permission errors

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-Grant-the-syslog-user-access-to-the-tty-group-so-
it-.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  rsyslogd: /dev/console permission errors

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  See: https://bugs.launchpad.net/bugs/1890177

  I am opening a new ticket because I believe there may have been a
  regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
  see this issue.

  /etc/rsyslog.d/90-google.conf:
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  Logs are filled with:
  rsyslogd: action 'action-8-builtin:omfile' suspended (module 
'builtin:omfile'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ]
  rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') 
[v8.2112.0 try https://www.rsyslog.com/e/2359 ]

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

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


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

[Touch-packages] [Bug 2028193] Re: Machine doesn't resume after sleep

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Machine doesn't resume after sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  When machine resumes after having been in sleep mode the screen is
  corrupted. Hard reboot required.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 19 16:12:01 2023
  DistUpgraded: 2023-07-11 13:24:17,567 DEBUG icon theme changed, re-reading
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon Vega 8 Mobile [103c:83c6]
  InstallationDate: Installed on 2018-05-14 (1892 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   LANG=en_CA.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=30332ede-31ab-439d-a665-2d2c504399cb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-07-11 (8 days ago)
  dmi.bios.date: 08/12/2021
  dmi.bios.release: 15.23
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 63.18
  dmi.modalias: 
dmi:bvnAMI:bvrF.23:bd08/12/2021:br15.23:efr63.18:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:sku1UG91UA#ABL:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.product.sku: 1UG91UA#ABL
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2027880] Re: Wifi is not appearing . ethernet is working just fine

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Wifi is not appearing . ethernet is working just fine

Status in network-manager package in Ubuntu:
  New

Bug description:
  Im sorry of this is already one of the previously reported bugs. I was
  on wifi, connected to ethernet and then when i tried going back to
  ethernet there was not wifi option or anything.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Jul 15 13:44:34 2023
  DpkgTerminalLog:
   Purging configuration files for network-manager-gnome (1.24.0-1ubuntu3) ...
   Purging configuration files for network-manager (1.36.6-0ubuntu2) ...
   rm: cannot remove '/var/lib/NetworkManager': Device or resource busy
   dpkg: error processing package network-manager (--purge):
installed network-manager package post-removal script subprocess returned 
error exit status 1
  ErrorMessage: installed network-manager package post-removal script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-07-13 (2 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  IpRoute:
   default via 192.168.0.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.0.0/24 dev enp8s0 proto kernel scope link src 192.168.0.6 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp8s0no wireless extensions.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: network-manager
  Title: package network-manager 1.36.6-0ubuntu2 failed to install/upgrade: 
installed network-manager package post-removal script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp8s0  ethernet  connected  full  full  
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
4741e0e4-2ea2-3ace-8a50-8a1625c5f168  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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