[Touch-packages] [Bug 1970163] Re: [USB-Audio - H1n, playback] whole sound sounds lower

[Kisaragi Marine]

This seems happen when starting mic record while listening sound through
its playback.

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

Title:
  [USB-Audio - H1n, playback] whole sound sounds lower

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  ## Reproduce steps
  * Discord @ 0.0.17 (APT-Manual-Installed: yes, downloaded .deb package from 
https://discord.com)
  * Firefox @ 99.0+build2-0ubuntu0.20.04.2 (APT-Manual-Installed: no)

  0. Set sound output with H1n playback
  1. Open YouTube
  2. Play some movie
  3. After playing movie, join Discord's voice channel
  4. All sounds sound lower in system-wide
  5. The problem can be solved with the workaround(*)
  * After doing workaround, this seems does not happen again in the session.

  ## Workaround
  ```
  pulseaudio -k
  pulseaudio --start
  ```

  ## Isolation the cause
  1. problem of Discord: No, only joining Discord's voice channels does not 
cause this.
  2. problem of YouTube: No, only playing some movie on it does not cause this.
  3. problem of Firefox: No, only playing audio on other Platform does not 
cause this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kisaragi   3089 F pulseaudio
   /dev/snd/controlC2:  kisaragi   3089 F pulseaudio
   /dev/snd/controlC1:  kisaragi   3089 F pulseaudio
   /dev/snd/pcmC1D0p:   kisaragi   3089 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 25 15:34:51 2022
  InstallationDate: Installed on 2022-03-12 (44 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:H1n successful
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - H1n, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M2
  dmi.board.vendor: ECS
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/16/2012:br4.6:svnKOUZIROCo.,Ltd.:pnFRONTIERDT:pvr2.0:rvnECS:rnH61H2-M2:rvr2.0:cvnECS:ct3:cvr2.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: FRONTIERDT
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: KOUZIRO Co., Ltd.

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


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

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Thomas Ward]

If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.

Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark the package as
"Breaks:" for all Qt6 libraries.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011935

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

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 1975872] Re: Screen flickering on external monitor (laptop)

[Daniel van Vugt]

Thanks for the bug report.

While the flickering is happening please run:

  journalctl -b0 > journalwithflicker.txt

and attach the resulting text file here.

Next please try selecting 'Ubuntu on Xorg' on the login screen, login
and run:

  journalctl -b0 > journalwithxorg.txt
  xrandr --verbose > xrandr.txt

and attach the resulting text files here.


** Tags added: hybrid i915 multimonitor nouveau

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

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

** Summary changed:

- Screen flickering on external monitor (laptop)
+ [ASUS GL552VW] Screen flickering on external monitor

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

Title:
  [ASUS GL552VW] Screen flickering on external monitor

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  External screen flickers on and off (image is present and then signal is 
lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh 
installation.
  Details:
  - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. 
The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make 
that HDMI work with NVIDIA GTX 960M in my laptop).
  - Nothing was installed after installing the OS - i connected to the Internet 
while installing the system and marked the option to download the updates.
  - I had that issue on Windows 10 - I fixed it by installing a latest Intel 
GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers 
installed by Windows - they were the latest Intel drivers.
  - Internal screen works fine.
  - If I mirror external and internal monitor, external isn't flickering, but 
internal monitor's resolution is lower that external's one.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 22:34:16 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/mutter/+bug/1975872/+subscriptions


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Daniel van Vugt]

1) Safe mode is expected to fail because it disables graphics drivers.
2) Live session all working fine.
3) Graphics working but not able to start a terminal.

So the only problem here is the last one where you couldn't start a
terminal. Did you try Ctrl+Alt+T ? Did the shell respond to mouse
clicks? Were you able to launch any other apps?

** Summary changed:

- radeon / amdgpu bad performance or panics
+ Unknown bug

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

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

Title:
  Unknown bug

Status in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code

[Connor Nolan]

This also affects me:

May 26 08:47:22  systemd-oomd[542]: Killed
/user.slice/user-1000.slice/user@1000.service/app.slice/snap.firefox.firefox.cef581a2-89d2-4a72-86a9-8a0a30cfdb86.scope
due to memory used (14922825728) / total (16526151680) and swap used
(1944498176) / total (2147479552) being more than 90.00%

I never had any issues with Ubuntu 20.04 and this also occurs with
QtCreator (upstream version not distribution version).

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

Title:
  systemd-oomd frequently kills firefox and visual studio code

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since I installed Ubuntu 22.04, firefox and visual studio code are
  frequently killed by systemd-oomd (every 2hours).

  I have 8 GB memory and never experienced this before the upgrade to
  Ubuntu 22.04. I thus assume that the claim that there is not enough
  memory is abusive. Did 64GB of memory become the minimum requirement
  to run Ubuntu ?

  The second problem is that it gives a very bad user experience which
  is critical for new Ubuntu users.

  There should be a warning prior killing apps to give the opportunity
  to save the app data. There should at least be an apologize and an
  explanation after killing the app.

  The current behavior gives the impression that Ubuntu 22.04 is
  unreliable and unsafe to use which is a problem for an LTS release
  that many people might want to use for critical production context.

  There might be a configuration problem with systemd-oomd or simply a
  bogus behavior. I would recommend to disable it or remove it
  completely until this problem is resolved. This is what I will do for
  myself because I have work to do.

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


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

[Touch-packages] [Bug 1933796] Re: resume from suspend while connected to power results in roaring fans

[Kai-Heng Feng]

Does this still happen on 22.04?

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

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

Title:
  resume from suspend while connected to power results in roaring fans

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from
  suspend with a roaring fan. i have to make sure to start the resume
  while the power cord is not connected, let it wake up fully and only
  then connect the power cord. this is quite an annoying regression,
  still persisting in ubuntu 21.04, since there is no way to calm the
  fan noise except to do a complete shutdown and power on cycle (reboot
  still keeps the fan at max).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Jun 27 18:20:13 2021
  InstallationDate: Installed on 2021-05-10 (48 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HR0068GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR0068GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.17
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR0068GE
  dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1975883] [NEW] package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools exited with return code 1

[Jacques Amar]

Public bug reported:

During upgrade to ubuntu 22

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-33-generic 5.15.0-33.34
ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181
Uname: Linux 5.4.0-113-generic x86_64
AlsaDevices:
 total 0
 crw-rw+ 1 root audio 116,  1 May 26 23:42 seq
 crw-rw+ 1 root audio 116, 33 May 26 23:42 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Thu May 26 23:45:41 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-03-16 (71 days ago)
InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2022-05-26 (0 days ago)
dmi.board.name: Standard PC (i440FX + PIIX, 1996)
dmi.board.vendor: QEMU
dmi.board.version: pc-i440fx-4.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias: 
dmi:bvn:bvr:bd:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:rvnQEMU:rnStandardPC(i440FX+PIIX,1996):rvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.1
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-package jammy need-duplicate-check uec-images

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

Title:
  package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to
  install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  During upgrade to ubuntu 22

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181
  Uname: Linux 5.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 May 26 23:42 seq
   crw-rw+ 1 root audio 116, 33 May 26 23:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Thu May 26 23:45:41 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-03-16 (71 days ago)
  InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Andrew Hayzen]

I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2

I wonder if the situation can be improved though as if you are trying to
use Qt 6 tooling in a container image then you need workarounds :-/

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 1455967] Re: NM disables accept_ra for an IPv6 connection, where it should enable it!

[Brent Baccala]

I'm still seeing this behavior on Ubuntu 20.04.4 LTS

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

Title:
  NM disables accept_ra for an IPv6 connection, where it should enable
  it!

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Guys,

  I just installed Ubuntu 15.04 on a brand new Dell E7440 Laptop and
  Network Manager disable the Router Advertisement for my IPv6
  connection!

  My connection settings for both wired and WiFi have:

  Edit Connection -> Edit Settings -> IPv6 Settings -> Method =
  Automatic

  But, take a look:

  ---
  root@ultra:~# cat /proc/sys/net/ipv6/conf/wlan0/accept_ra
  0
  root@ultra:~# cat /proc/sys/net/ipv6/conf/eth0/accept_ra
  0
  ---

  So, my IPv6 connection doesn't work. I need to manually re-enable it,
  by running:

  ---
  echo 1 > /proc/sys/net/ipv6/conf/wlan0/accept_ra
  ---

  Then, my IPv6 works again! Everytime I reconnect to a network, I need
  to "echo 1 > accept_ra" again... Very annoying.

  Please, help!

  Thanks in advance...

  Cheers!
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.2
  ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
  Uname: Linux 3.19.0-17-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 17 15:02:12 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-15 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static  metric 400
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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


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

[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu

[Launchpad Bug Tracker]

This bug was fixed in the package kdesu - 5.94.0-0ubuntu2

---
kdesu (5.94.0-0ubuntu2) kinetic; urgency=medium

  * Disable use of sudo 'Defaults use_pty' for kdesu. (LP: #1965439)

 -- Rik Mills   Thu, 26 May 2022 15:13:22 +0100

** Changed in: kdesu (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Fix Released
Status in kubuntu-settings source package in Kinetic:
  In Progress
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  In Progress
Status in kdesu package in Debian:
  Unknown

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Touch-packages] [Bug 1975872] [NEW] Screen flickering on external monitor (laptop)

[Andrii Beznosiuk]

Public bug reported:

External screen flickers on and off (image is present and then signal is lost, 
flickering is random, but very often, ~3 times in 10 seconds) on a fresh 
installation.
Details:
- I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. 
The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make 
that HDMI work with NVIDIA GTX 960M in my laptop).
- Nothing was installed after installing the OS - i connected to the Internet 
while installing the system and marked the option to download the updates.
- I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU 
driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed 
by Windows - they were the latest Intel drivers.
- Internal screen works fine.
- If I mirror external and internal monitor, external isn't flickering, but 
internal monitor's resolution is lower that external's one.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 26 22:34:16 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]
InstallationDate: Installed on 2022-05-26 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2019
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: GL
dmi.product.name: GL552VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Screen flickering on external monitor (laptop)

Status in xorg package in Ubuntu:
  New

Bug description:
  External screen flickers on and off (image is present and then signal is 
lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh 
installation.
  Details:
  - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. 
The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make 
that HDMI work with NVIDIA GTX 960M in my laptop).
  - Nothing was installed after installing the OS - i connected to the Internet 
while installing the system and marked the option to download the updates.
  - I had that issue on Windows 10 - I fixed it by installing a latest Intel 
GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers 
installed by Windows - they were the latest Intel drivers.
  - Internal screen works fine.
  - If I mirror external and internal monitor, external isn't flickering, but 
internal monitor's resolution is lower that external's one.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] 

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Be]

I stumbled over this setting up CI for a Qt project that supports both
Qt6 and Qt5. I confirm that creating a /usr/lib/x86_64-linux-
gnu/qtchooser/qt6.conf file with the contents:

```
/usr/lib/qt6/bin
/usr/lib/x86_64-linux-gnu
```

and setting the QT_SELECT environment variable to `qt6` works around the
bug.

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 1975867] [NEW] printer cannon pixma mg2570s not printing color but only black and white

[Anjan Bora]

Public bug reported:

My printer is Canon Pixma MG2570S not printing color. I checked every
options, even then no result. I have installed driver cnijfilter-
mg2500serie and even cups-backend-bjnp. More than that when I run
command ink -p usb it crashes.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog:
 W [27/May/2022:00:07:57 +0530] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
 W [27/May/2022:00:08:11 +0530] CreateProfile failed: 
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.
 W [27/May/2022:00:30:10 +0530] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'MG2500-Gray..\' already 
exists
 W [27/May/2022:00:30:10 +0530] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'MG2500-RGB..\' already 
exists
Date: Fri May 27 00:39:38 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-04-26 (30 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lpstat: device for MG2500: usb://Canon/MG2500%20series?serial=815254=1
MachineType: ASUSTeK COMPUTER INC. X541NA
Papersize: a4
PpdFiles: MG2500: Canon MG2500 series - CUPS+Gutenprint v5.3.3
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X541NA.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X541NA
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.:bvrX541NA.309:bd05/25/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: X
dmi.product.name: X541NA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug jammy

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

Title:
  printer cannon pixma mg2570s not printing color but only black and
  white

Status in cups package in Ubuntu:
  New

Bug description:
  My printer is Canon Pixma MG2570S not printing color. I checked every
  options, even then no result. I have installed driver cnijfilter-
  mg2500serie and even cups-backend-bjnp. More than that when I run
  command ink -p usb it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [27/May/2022:00:07:57 +0530] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [27/May/2022:00:08:11 +0530] CreateProfile failed: 
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.
   W [27/May/2022:00:30:10 +0530] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'MG2500-Gray..\' already 
exists
   W [27/May/2022:00:30:10 +0530] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id \'MG2500-RGB..\' already 
exists
  Date: Fri May 27 00:39:38 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-04-26 (30 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lpstat: device for MG2500: 
usb://Canon/MG2500%20series?serial=815254=1
  MachineType: ASUSTeK COMPUTER INC. X541NA
  Papersize: a4
  PpdFiles: MG2500: Canon MG2500 series - CUPS+Gutenprint v5.3.3
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 

[Touch-packages] [Bug 1973149] Re: system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions

[madigal]

This has been silenced with the latest:

dpkg (1.21.8ubuntu1) kinetic

  * Packaging:
- Silence warning about merged-usr-via-aliased-dirs on 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/1973149

Title:
  system uses merged-usr-via-aliased-dirs, going behind dpkg's  back,
  breaking its core assumptions

Status in dpkg package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in dpkg source package in Kinetic:
  Triaged
Status in systemd source package in Kinetic:
  Invalid

Bug description:
  Got this warning on Kinetic, Mate flavor:

  Paramétrage de dpkg (1.21.7ubuntu3) ...
  dpkg: warning:

   This system uses merged-usr-via-aliased-dirs, going behind dpkg's
  back, breaking its core assumptions. This can cause silent file
  overwrites and disappearances, and its general tools misbehavior.

   See .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: dpkg 1.21.7ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags: kinetic package-from-proposed third-party-packages
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1975865] [NEW] Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz

[Gabriel M. Beddingfield]

Public bug reported:

When adding the debug repos, I am getting:

E: Failed to fetch 
http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz  
File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 
91.189.91.49 80]
   Hashes of expected file:
- Filesize:795487 [weak]
- 
SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81
- SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6
- SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak]
- MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak]
   Release file created at: Thu, 26 May 2022 08:04:16 +
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

When I manually go to the repositories... many (all?) of the hashes
listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not
match the files (e.g. http://ddebs.ubuntu.com/dists/bionic-
updates/main/binary-amd64/Packages.gz )

Note: I filed this against `apt` because `ubuntu-bug` forced me to
specify a package and I didn't know any other way to file the bug.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.14
Uname: Linux 5.16.18-1rodete2-amd64 x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
Date: Thu May 26 18:36:21 2022
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-
  updates/main/binary-amd64/Packages.gz

Status in apt package in Ubuntu:
  New

Bug description:
  When adding the debug repos, I am getting:

  E: Failed to fetch 
http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz  
File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 
91.189.91.49 80]
 Hashes of expected file:
  - Filesize:795487 [weak]
  - 
SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81
  - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6
  - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak]
  - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak]
 Release file created at: Thu, 26 May 2022 08:04:16 +
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  When I manually go to the repositories... many (all?) of the hashes
  listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not
  match the files (e.g. http://ddebs.ubuntu.com/dists/bionic-
  updates/main/binary-amd64/Packages.gz )

  Note: I filed this against `apt` because `ubuntu-bug` forced me to
  specify a package and I didn't know any other way to file the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.14
  Uname: Linux 5.16.18-1rodete2-amd64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  Date: Thu May 26 18:36:21 2022
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Sebastian Schauenburg]

Here are logs from 3 separate type of boots (actually I had to reboot at
least 20 times, because I had a lot of crashes/hangs):

1) USB safemode boot (since the normal USB boot didn't work ~ 5 times)
2) USB normal boot (it worked, don't know why, but I'm not complaining)
3) normal installed boot (could log in to GDM, but was not able to start a 
terminal. Had to switch to VT3 and back to get something useful from the 
system. Eventually I logged in via SSH. So I was not able to get glxinfo, hope 
the glxinfo from "2)" suffices.)

** Attachment added: "20220526_logs.zip"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5593151/+files/20220526_logs.zip

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

Title:
  radeon / amdgpu bad performance or panics

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in

[Balanarayan K]

Hi,

upower 0.99.18 version contains the fix for this. Are there plans to
integrate this version to Ubuntu 20.04?

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

Title:
  upower takes long time to detect laptop AC charger plugged in

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

  Laptop Model: Acer Aspire E15 E5-573G-56JN

  Laptop battery and AC charger is not faulty as the
  charging/discharging status gets correctly detected when using Windows
  10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1971299] Re: Merge nss from Debian unstable for kinetic

[Athos Ribeiro]

Our current delta has the following patches:

=== BEGIN DELTA ANALYSIS ===

  * New upstream release. (LP: #1959126) [2:3.68.2-0ubuntu1]

We went "ahead" of Debian here. We must drop this to get back to
tracking the Debian history.

  * d/p/CVE-2021-43527.patch: drop patch applied upstream.
[ Fixed in 3.68.1 ]
  * SECURITY UPDATE: heap overflow when verifying DSA/RSA-PSS DER-encoded
signatures
- debian/patches/CVE-2021-43527.patch: check signature lengths in
  nss/lib/cryptohi/secvfy.c.
- CVE-2021-43527

When dropping the "New upstream release", this would be re-introduced,
but since this was fixed in 3.68.1 already, it can be/remain dropped.

- d/libnss3.links: Make freebl3 available as library. (LP #1744328)
- d/libnss3.links.in: Symlink chk files to fix self-verification in
  FIPS mode. (LP #1885562)
- d/control: Add dh-exec to Build-Depends.
- d/rules: Make mkdir tolerate debian/tmp existing (due to dh-exec).

The packaging approach changed in Debian for 2:3.72-1 to stick to the upstream 
distribution approach. The libraries are now shipped in a single directory and 
therefore this patch is no longer needed.
dh-exec was only used for this links file and the related deltas are also no 
longer needed.

- d/p/disable_fips_enabled_read.patch: Disable reading fips_enabled flag
  in FIPS mode as libnss is not a FIPS certified library. (LP #1837734)

LP: #1837734, which introduced this patch, has a comment from the patch
author saying this was never needed in this package and was added to fix
an issue with firefox, which had libnss embedded back when this was
introduced. This can also be dropped.

- d/p/set-tls1.2-as-minimum.patch: Set TLSv1.2 as minimum TLS version.
  (LP #1856428)

This was included in upstream version 3.69 and can be dropped.

- d/p/fix-ftbfs-s390x.patch: Fix some uninitialized variable warnings
  and format overflows for s390x.
- d/p/fix-ftbfs-glibc-invalid-oob-error.patch: Disable non-null error
  checking on call to getcwd since this results in an erroneous warning
  that causes the build to fail otherwise.

There are no FTBFS issues with the current Debian version. Hence, these
are no longer needed. See https://launchpad.net/~athos-
ribeiro/+archive/ubuntu/nss377-transition/+packages

- d/rules: Disable LTO on s390x for now. (LP #1931104)

In the upstream issue linked in LP: #1931104, the Fedora packager re-
enabled LTO since version 3.69 and reported no issues/regressions were
observed. The same applies for our test builds at
https://launchpad.net/~athos-
ribeiro/+archive/ubuntu/nss377-transition/+packages. This can also be
dropped.

=== END DELTA ANALYSIS ===

Based on the report above, we can safely drop all delta for nss.

This can be a sync.

A bileto ticket was created to ensure rdeps sanity before we proceed
with sync'ing this package at https://bileto.ubuntu.com/#/ticket/4857

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43527

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

Title:
  Merge nss from Debian unstable for kinetic

Status in nss package in Ubuntu:
  In Progress

Bug description:
  Upstream: tbd
  Debian:   2:3.77-1
  Ubuntu:   2:3.68.2-0ubuntu1


  
  ### New Debian Changes ###

  nss (2:3.77-1) unstable; urgency=medium

* New upstream release.
* debian/libnss3.symbols: Add NSS_3.77 symbol version.

   -- Mike Hommey   Wed, 06 Apr 2022 09:18:22 +0900

  nss (2:3.75-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 09 Feb 2022 08:46:51 +0900

  nss (2:3.73.1-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Fri, 17 Dec 2021 06:16:55 +0900

  nss (2:3.73-1) unstable; urgency=medium

* New upstream release.
* Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded
  DSA and RSA-PSS signatures.

   -- Mike Hommey   Thu, 02 Dec 2021 06:04:31 +0900

  nss (2:3.72-2) unstable; urgency=medium

* debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1).
  Closes: #998733.

   -- Mike Hommey   Fri, 12 Nov 2021 06:21:05 +0900

  nss (2:3.72-1) unstable; urgency=medium

* New upstream release.
* debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h,
  nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c,
  nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo
  symbol and remove the previous workaround. Closes: #990058.
* debian/libnss3.lintian-overrides.in, debian/rules,
  nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c,
  nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile,
  nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a
  subdirectory. It's a deviation from upstream that is causing more problems
  than it's worth 

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[Brian Murray]

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

** Changed in: busybox (Ubuntu Jammy)
   Importance: Undecided => High

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

** Changed in: busybox (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

** Tags removed: rls-kk-incoming

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in busybox package in Ubuntu:
  Confirmed
Status in busybox source package in Jammy:
  Confirmed

Bug description:
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  
  His DHCP response looks like this:

  
  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..

  
  Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  
  Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

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


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

[Touch-packages] [Bug 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect

[Brian Murray]

** Tags removed: rls-ii-incoming rls-jj-incoming
** Tags added: rls-ii-notfixing

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

Title:
  systemd-resolved does not reset DNS server and search domain list
  properly after VPN disconnect

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

Bug description:
  Hi,
  in Ubuntu 21.10 I am facing a problem with DNS server list and search domain 
list is not properly reset back to the previous values after a VPN is 
disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded 
from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is 
not an "upgrade issue".

  I use this resolv.conf symlink:
  /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

  Actual behavior: 
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS 
server and search domain entries left there, so it is not reset back properly.

  Desired behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected DNS servers and search domain list 
is restored to exactly the same state as was prior to the VPN connection.

  Steps for reproducing:
  1. Before VPN is connected this is the DNS server and search domain list in 
/etc/resolv.conf:

  nameserver 192.168.122.1
  search .

  2. Once the VPN is connected, we see there were VPN's DNS server and
  serach domain list entries added:

  nameserver 2xx.xx.xx.x0
  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain1.local domain2.internal domain3.internal

  3. After VPN disconnection, we see the DNS server and search domain
  list in /etc/resolv.conf is not restored to the state at point (1.)
  and some entries from VPN is being kept there:

  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain2.internal domain3.internal

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 06:06:05 2022
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.14.0-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:sku:cvnQEMU:ct1:cvrpc-q35-6.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.0
  dmi.sys.vendor: QEMU

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


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

[Touch-packages] [Bug 1971299] Re: Merge nss from Debian unstable for kinetic

[Athos Ribeiro]

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

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

Title:
  Merge nss from Debian unstable for kinetic

Status in nss package in Ubuntu:
  In Progress

Bug description:
  Upstream: tbd
  Debian:   2:3.77-1
  Ubuntu:   2:3.68.2-0ubuntu1


  
  ### New Debian Changes ###

  nss (2:3.77-1) unstable; urgency=medium

* New upstream release.
* debian/libnss3.symbols: Add NSS_3.77 symbol version.

   -- Mike Hommey   Wed, 06 Apr 2022 09:18:22 +0900

  nss (2:3.75-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 09 Feb 2022 08:46:51 +0900

  nss (2:3.73.1-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Fri, 17 Dec 2021 06:16:55 +0900

  nss (2:3.73-1) unstable; urgency=medium

* New upstream release.
* Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded
  DSA and RSA-PSS signatures.

   -- Mike Hommey   Thu, 02 Dec 2021 06:04:31 +0900

  nss (2:3.72-2) unstable; urgency=medium

* debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1).
  Closes: #998733.

   -- Mike Hommey   Fri, 12 Nov 2021 06:21:05 +0900

  nss (2:3.72-1) unstable; urgency=medium

* New upstream release.
* debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h,
  nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c,
  nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo
  symbol and remove the previous workaround. Closes: #990058.
* debian/libnss3.lintian-overrides.in, debian/rules,
  nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c,
  nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile,
  nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a
  subdirectory. It's a deviation from upstream that is causing more problems
  than it's worth keeping. Closes: #737855, #846012, #979159.
* debian/libnss3-dev.links.in: Remove xulrunner-nss.pc.
* debian/rules: Stop forcing xz compression.
* debian/copyright: Add dot for continuation.
* debian/watch: Upgrade to version 4.
* debian/control: Upgrade Standard-Version to 4.6.0:
  - debian/rules: Build with `make -s` when DEB_BUILD_OPTIONS contains
terse.
  - debian/control: Add Rules-Requires-Root: no.
* debian/control: Remove conflict with libnss3-1d. The last Debian version
  with libnss3-1d was jessie, and it had a newer version anyways.
* debian/rules: Enable all hardening options.
* debian/libnss3-symbols: Add Build-Depends-Package in symbols file.
* debian/*.lintian-overrides*: Remove
  copyright-refers-to-versionless-license-file lintian overrides.
* debian/libnss3.lintian-overrides.in:
  - s/shlib-without-versioned-soname/shared-library-lacks-version/.
  - Add lacks-unversioned-link-to-shared-library overrides.
* debian/nss-config.in, debian/rules: Ship upstream nss-config instead of
  ours. Closes: #737855, #963136.
* debian/rules, debian/control: Always set Multi-Arch: same.
* debian/copyright:
  - Remove commas in `Files`.
  - Add missing license name for ifparser.
  - Add missing `Copyright`.
  - Remove copyright for mkdepend, which is not in the source tree anymore.
* debian/upstream/metadata: Add upstream bug tracking metadata.

[ Daniel Kahn Gillmor ]
* debian/control: correct Homepage (old URL redirects to 404)

[ Janitor ]
* debian/changelog: Trim trailing whitespace.
* debian/copyright: Use secure copyright file specification URI.
* debian/compat, debian/control:
  - Bump debhelper from deprecated 9 to 13.
  - Set debhelper-compat version in Build-Depends.
* debian/upstream/metadata: Set upstream metadata fields: Repository.
* debian/rules: Drop transition for old debug package migration.

   -- Mike Hommey   Tue, 02 Nov 2021 06:57:06 +0900

  nss (2:3.70-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 08 Sep 2021 08:31:23 +0900

  nss (2:3.68-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Mon, 19 Jul 2021 06:23:39 +0900


  
  ### Old Ubuntu Delta ###

  nss (2:3.68.2-0ubuntu1) jammy; urgency=medium

* New upstream release. (LP: #1959126)
* d/p/CVE-2021-43527.patch: drop patch applied upstream.
  [ Fixed in 3.68.1 ]

   -- Athos Ribeiro   Mon, 21 Feb 2022
  14:55:42 -0300

  nss (2:3.68-1ubuntu2) jammy; urgency=medium

* SECURITY UPDATE: heap overflow when verifying DSA/RSA-PSS DER-encoded
  signatures
  - debian/patches/CVE-2021-43527.patch: check signature lengths in
nss/lib/cryptohi/secvfy.c.
  - CVE-2021-43527

   -- Marc Deslauriers   Mon, 29 Nov 2021
  07:12:54 -0500

  nss (2:3.68-1ubuntu1) impish; urgency=medium

* Merge 

[Touch-packages] [Bug 1888347] Re: blk-availability unmounts filesystems before applications have finished using them

[Brian Murray]

** Changed in: lvm2 (Ubuntu)
   Importance: Undecided => High

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

Title:
  blk-availability unmounts filesystems before applications have
  finished using them

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  This bug is similar to the following:

Red Hat - https://bugzilla.redhat.com/show_bug.cgi?id=1701234#c2
Debian - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946882

  The blk-availability service is short-cutting
  RequiresMountsFor= dependencies during system shutdown and
  unmounting filesystems before those services have stopped, resulting
  in data file corruption and/or data loss.

  This can be worked around by adding "After=blk-availability.service"
  to the unit file for the service in question, but this is not self-
  evident and shouldn't be necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 21 16:37:17 2020
  InstallationDate: Installed on 2014-05-01 (2272 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-05-05 (77 days ago)

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


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

[Touch-packages] [Bug 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect

[Brian Murray]

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

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

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

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

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

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

Title:
  systemd-resolved does not reset DNS server and search domain list
  properly after VPN disconnect

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

Bug description:
  Hi,
  in Ubuntu 21.10 I am facing a problem with DNS server list and search domain 
list is not properly reset back to the previous values after a VPN is 
disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded 
from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is 
not an "upgrade issue".

  I use this resolv.conf symlink:
  /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

  Actual behavior: 
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS 
server and search domain entries left there, so it is not reset back properly.

  Desired behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected DNS servers and search domain list 
is restored to exactly the same state as was prior to the VPN connection.

  Steps for reproducing:
  1. Before VPN is connected this is the DNS server and search domain list in 
/etc/resolv.conf:

  nameserver 192.168.122.1
  search .

  2. Once the VPN is connected, we see there were VPN's DNS server and
  serach domain list entries added:

  nameserver 2xx.xx.xx.x0
  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain1.local domain2.internal domain3.internal

  3. After VPN disconnection, we see the DNS server and search domain
  list in /etc/resolv.conf is not restored to the state at point (1.)
  and some entries from VPN is being kept there:

  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain2.internal domain3.internal

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 06:06:05 2022
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.14.0-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:sku:cvnQEMU:ct1:cvrpc-q35-6.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.0
  dmi.sys.vendor: QEMU

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


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

[Touch-packages] [Bug 1975667] Re: systemd-resolved does not reset DNS server and search domain list properly after VPN disconnect

[Matthieu Clemenceau]

** Tags added: fr-2418

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

Title:
  systemd-resolved does not reset DNS server and search domain list
  properly after VPN disconnect

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

Bug description:
  Hi,
  in Ubuntu 21.10 I am facing a problem with DNS server list and search domain 
list is not properly reset back to the previous values after a VPN is 
disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded 
from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is 
not an "upgrade issue".

  I use this resolv.conf symlink:
  /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

  Actual behavior: 
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS 
server and search domain entries left there, so it is not reset back properly.

  Desired behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected DNS servers and search domain list 
is restored to exactly the same state as was prior to the VPN connection.

  Steps for reproducing:
  1. Before VPN is connected this is the DNS server and search domain list in 
/etc/resolv.conf:

  nameserver 192.168.122.1
  search .

  2. Once the VPN is connected, we see there were VPN's DNS server and
  serach domain list entries added:

  nameserver 2xx.xx.xx.x0
  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain1.local domain2.internal domain3.internal

  3. After VPN disconnection, we see the DNS server and search domain
  list in /etc/resolv.conf is not restored to the state at point (1.)
  and some entries from VPN is being kept there:

  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain2.internal domain3.internal

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 06:06:05 2022
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.14.0-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:sku:cvnQEMU:ct1:cvrpc-q35-6.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.0
  dmi.sys.vendor: QEMU

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


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

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[Brian Murray]

** Changed in: busybox (Ubuntu)
   Importance: Undecided => High

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  
  His DHCP response looks like this:

  
  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..

  
  Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  
  Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

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


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

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[Matthieu Clemenceau]

** Tags added: fr-2416

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  
  His DHCP response looks like this:

  
  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..

  
  Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  
  Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

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


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

[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1969162
   bad interaction between snapd and update-notifier when snapd package is 
being upgraded

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

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


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

[Touch-packages] [Bug 1975836] [NEW] [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[giemastruc]

Public bug reported:

I've installed a MOTU M2 USB Audio Sound Card. Pulse Audio do not shot
it while the sound card works with DAW softwares, but not with system
sounds or browser sounds.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-49.55-lowlatency 5.11.22
Uname: Linux 5.11.0-49-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jmaw   2067 F pulseaudio
 /dev/snd/controlC2:  jmaw   2067 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu May 26 16:35:45 2022
InstallationDate: Installed on 2021-10-08 (229 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jmaw   2067 F pulseaudio
 /dev/snd/controlC2:  jmaw   2067 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2012
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX3
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.:bvr0702:bd08/24/2012:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnM5A78L-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
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

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


** Tags: amd64 apport-bug hirsute

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

Title:
  [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've installed a MOTU M2 USB Audio Sound Card. Pulse Audio do not shot
  it while the sound card works with DAW softwares, but not with system
  sounds or browser sounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-49.55-lowlatency 5.11.22
  Uname: Linux 5.11.0-49-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaw   2067 F pulseaudio
   /dev/snd/controlC2:  jmaw   2067 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu May 26 16:35:45 2022
  InstallationDate: Installed on 2021-10-08 (229 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaw   2067 F pulseaudio
   /dev/snd/controlC2:  jmaw   2067 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2012
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX3
  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.:bvr0702:bd08/24/2012:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnM5A78L-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  

[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu

[Rik Mills]

** Changed in: kdesu (Ubuntu Jammy)
 Assignee: (unassigned) => Rik Mills (rikmills)

** Changed in: kdesu (Ubuntu Kinetic)
 Assignee: (unassigned) => Rik Mills (rikmills)

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

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Fix Committed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Fix Committed
Status in kubuntu-settings source package in Kinetic:
  In Progress
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  In Progress
Status in kdesu package in Debian:
  Unknown

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu

[Rik Mills]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011624

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

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

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Confirmed
Status in kubuntu-settings source package in Kinetic:
  In Progress
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  In Progress
Status in kdesu package in Debian:
  Unknown

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

[Andreas Hasenack]

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
 Assignee: Andreas Hasenack (ahasenack) => (unassigned)

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
   Status: Confirmed => Triaged

** Changed in: cyrus-sasl2 (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Triaged
Status in cyrus-sasl2 source package in Trusty:
  Won't Fix
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 source package in Focal:
  Triaged
Status in cyrus-sasl2 source package in Impish:
  Triaged
Status in cyrus-sasl2 source package in Jammy:
  Triaged
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

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


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

[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/423455

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Triaged
Status in cyrus-sasl2 source package in Trusty:
  Won't Fix
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 source package in Focal:
  Triaged
Status in cyrus-sasl2 source package in Impish:
  Triaged
Status in cyrus-sasl2 source package in Jammy:
  Triaged
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

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


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

[Touch-packages] [Bug 1926139] Re: dhclient doesn't receive dhcp offer from kernel

[Chris Patterson]

We've been investigating a similar issue in Ubuntu 20.04 (and now 22.04)
on Azure where Running PPS re-use fails to perform DHCP for 5 minutes
when dhclient is invoked by cloud-init.  dhclient is run by cloud-init,
but sees no DHCPOFFER.  It varies due to unknown reasons but it has
affected a ~0.3-2% of deployments in this scenario over time.

We instrumented our images to capture network traffic and see what is
happening and sure enough DHCP offers are coming through to the guest by
dhclient doesn't see them.  We instrumented dhclient and the "got_one()"
callback is never invoked in these failures.

18.04 does not have this issue.

This behavior can be reproduced multiple ways:
- Reproduce similar test environment to above scenario using cloud-init (switch 
hyperv nic to a different vnet while waiting the link status to reset, then 
perform dhcp).  This test case will reproduce in ~1,500 runs, though it varies 
and requires more complex setup.
- Repeatedly run dhclient in a loop until it fails (see test-sequential.sh).  
It may take a while, but even this simple test will reproduce this behavior in 
~50k runs for me in an LXD VM.
- Simply launch instances of dhclient in parallel (see test-parallel.sh). There 
is an excellent chance at least one of those dhclients will fail this way.

I noticed the uprev of bind9 libs in focal:
focal (net): 1:9.11.16+dfsg-3~build1
focal-updates (net): 1:9.11.16+dfsg-3~ubuntu1
impish (net): 1:9.11.19+dfsg-2.1ubuntu1
jammy (net): 1:9.11.19+dfsg-2.1ubuntu3
kinetic (net): 1:9.11.19+dfsg-2.1ubuntu3

I couldn't find any related issue on the isc-dhcp tracker, etc.  I did
build dhclient from the Debian master branch
(https://salsa.debian.org/debian/isc-dhcp/-/commits/master/debian) which
uses the in-tree bind libs and that seems to have addressed the issue
for all scenarios.  Not that it helps much to bisect this just yet.

** Attachment added: "parallel test"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593045/+files/test-parallel.sh

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

Title:
  dhclient doesn't receive dhcp offer from kernel

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Platform: Qemu/libvirt on AMD64
  Ubuntu version: 20.04
  isc-dhcp-client version: 4.4.1-2.1ubuntu5
  Problem: When dhclient is used during boot every few reboots the DHCP OFFER 
packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be 
seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no 
read event is triggered.
  Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these 
dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still 
occurs. So this issue might also be kernel related.

  Attached diff shows a strace of all threads and a pcap showing the
  tcpdump output.

  Edit:
  - Sometimes the dhclient command does receive the OFFER packet and connection 
is restored.
  - In my testing running dhclient manually from the terminal when the OFFERs 
aren't received will result in a new dhclient session which does receive the 
OFFER packet and connection is restored.

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


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

[Touch-packages] [Bug 1926139] Re: dhclient doesn't receive dhcp offer from kernel

[Chris Patterson]

** Attachment added: "sequential test"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593046/+files/test-sequential.sh

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

Title:
  dhclient doesn't receive dhcp offer from kernel

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Platform: Qemu/libvirt on AMD64
  Ubuntu version: 20.04
  isc-dhcp-client version: 4.4.1-2.1ubuntu5
  Problem: When dhclient is used during boot every few reboots the DHCP OFFER 
packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be 
seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no 
read event is triggered.
  Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these 
dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still 
occurs. So this issue might also be kernel related.

  Attached diff shows a strace of all threads and a pcap showing the
  tcpdump output.

  Edit:
  - Sometimes the dhclient command does receive the OFFER packet and connection 
is restored.
  - In my testing running dhclient manually from the terminal when the OFFERs 
aren't received will result in a new dhclient session which does receive the 
OFFER packet and connection is restored.

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


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

[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu

[Rik Mills]

** Also affects: sudo (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Also affects: ubuntustudio-default-settings (Ubuntu Kinetic)
   Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: In Progress

** Also affects: kubuntu-settings (Ubuntu Kinetic)
   Importance: High
   Status: In Progress

** Also affects: kdesu (Ubuntu Kinetic)
   Importance: High
   Status: Confirmed

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Confirmed
Status in kubuntu-settings source package in Kinetic:
  In Progress
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Touch-packages] [Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password

[DR. VIMAL HURRY]

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

I'm having the same problem on both my desktop & laptop running Kubuntu
22.04. Sudo muon e.g. gets the job done (to change software sources) but
it is very irritating that the dialog box won't accept my password. I
never had this problem on Kubuntu 21.10. Please fix this bug as soon as
possible. Thanks!

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

Title:
  Software Sources/software-properties-qt privilege escalation not
  accepting password

Status in plasma-discover package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  2) package version - apt-cache policy pkgname'

  plasma-discover:
Installed: 5.24.2.1-0ubuntu1

  software-properties-qt:
Installed: 0.99.19

  3) expected to happen
  * In Discover: Settings > Software Sources
  * opens a privilege escalation dialogue
  * enter user password
  * software-properties-qt opens

  4) happened instead
  * In Discover: Settings > Software Sources
  * opens a privilege escalation dialogue
  * insert known-correct user password
  * **does not accept known-correct user password**

  # Additional Info
  Note: described behaviour is for a post 20.04->22.04 devel daily upgrade 
found during a QA Testcase. Behaviour exists, but has slightly different 
symptoms in a virgin live 22.04 daily session (see below)

  * launching from terminal works as expected
  sudo software-properties-qt

  ## process & errors - post 20.04->22.04 devel daily upgrade
  * running Discover from terminal
$ plasma-discover

  * Settings > Software Sources 
  gives error on terminal:
  > org.kde.kdesu: Daemon not safe (not sgid), not using it.

  * insert known-correct user password
  gives error on terminal:
  > kf.su: [ ./src/stubprocess.cpp : 225 ]  Unknown request: "stop"
  > end

  * close password window
  gives error on terminal

  > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command
  > Runs a program with elevated privileges.

  > Options:
  >   -h, --help Displays help on commandline options.
  > [...]

  ## process & errors - live Kubuntu 22.04 daily

  similar behaviour, hoever password-asking window never appears.
  Terminal errors differ from above:

  * Settings > Software Sources 
  gives error on terminal:
  > org.kde.kdesu: Daemon not safe (not sgid), not using it.
  >
  > Don't need password!!
  >
  >kf.su: [./src/stubprocess.cpp : 255 ]  Unknown request: "ok"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: plasma-discover 5.24.2.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags: jammy third-party-packages
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu

[DR. VIMAL HURRY]

I'm having the same problem on both my desktop & laptop running Kubuntu
22.04. Sudo muon e.g. gets the job done (to change software sources) but
it is very irritating that the dialog box won't accept my password. I
never had this problem on Kubuntu 21.10. Please fix this bug as soon as
possible. Thanks!

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Daniel van Vugt]

We can't read crash files. You need to use the 'ubuntu-bug' or 'apport-
cli' tools to upload crash files.

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

Title:
  radeon / amdgpu bad performance or panics

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Sebastian Schauenburg]

With the live USB stick, there are also Xorg issues. Even got a nice
crash rapport.

** Attachment added: "_usr_lib_xorg_Xorg.127.crash"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5593009/+files/_usr_lib_xorg_Xorg.127.crash

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

Title:
  radeon / amdgpu bad performance or panics

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Daniel van Vugt]

The attachment in comment #16 shows Vulkan is now working, but only with
software rendering(?) so that's going to be slow...

Please run these again:

  lspci -k > lspci.txt
  journalctl -b0 > journal.txt
  glxinfo > glxinfo.txt

and attach the resulting text files here.

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

Title:
  radeon / amdgpu bad performance or panics

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1975788] [NEW] libopencv-core-dev package depends on wrong TBB devel package

[Vaclav Blazek]

Public bug reported:

OpenCV 4.5.4+dfsg-9ubuntu4 in 22.04 is compiled and linked against
libtbb.so.2 from the libtbb2 package, which is correctly recorded in its
binary packages, e.g.:

# dpkg -s libopencv-core4.5d | grep Depends
Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 11), libtbb2 (>= 
2017~U7), zlib1g (>= 1:1.1.4)

However, the libopencv-core-dev development package depends on libtbb-
dev instead of libttb2-dev:

# dpkg -s libopencv-core-dev | grep Depends
Depends: libopencv-core4.5d (= 4.5.4+dfsg-9ubuntu4), libtbb-dev, zlib1g-dev

This hinders any development using both OpenCV and TBB2.

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

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

Title:
  libopencv-core-dev package depends on wrong TBB devel package

Status in opencv package in Ubuntu:
  New

Bug description:
  OpenCV 4.5.4+dfsg-9ubuntu4 in 22.04 is compiled and linked against
  libtbb.so.2 from the libtbb2 package, which is correctly recorded in
  its binary packages, e.g.:

  # dpkg -s libopencv-core4.5d | grep Depends
  Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 11), libtbb2 
(>= 2017~U7), zlib1g (>= 1:1.1.4)

  However, the libopencv-core-dev development package depends on libtbb-
  dev instead of libttb2-dev:

  # dpkg -s libopencv-core-dev | grep Depends
  Depends: libopencv-core4.5d (= 4.5.4+dfsg-9ubuntu4), libtbb-dev, zlib1g-dev

  This hinders any development using both OpenCV and TBB2.

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


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

[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics

[Sebastian Schauenburg]

Here's the vulkaninfo. I got lucky, since the entire GUI hung shortly
after (don't think it's related to running this specific command
though).

Reverted the Wayland (GDM) change, so it's stock behaviour. And yes, I
switched back to stock config and kernel.

Will try to USB live version shortly.

** Attachment added: "vulkaninfosudo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5593007/+files/vulkaninfosudo.txt

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

Title:
  radeon / amdgpu bad performance or panics

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Recently I upgraded my machine and moved my GPU over from the old
  (Intel something) to the new machine (AMD Ryzen 7 5700X, B550
  motherboard). I did a fresh Ubuntu install (server) and added packages
  to get my GUI rolling (lightdm + awesomewm), just like before.

  The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has
  the R9 280X chip (TAHITI / Southern Islands). On my old system, I
  could play games with Vulkan, but with this system it doesn't work.

  If I run the 'default' setup, it uses the 'radeon' kernel module. The
  first couple of seconds I get reasonable performance (glxgears @ 60
  FPS), then it suddenly drop to 4 and motion is almost not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg (not installed)
  Uname: Linux 5.18.0-051800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 24 06:49:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] 
[1458:3001]
  InstallationDate: Installed on 2022-05-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.30
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

[bob]

This issue is still existing after the fresh installation on raspberry
pi 4 8GB desktop.

** Attachment added: "Screenshot from 2022-05-25 00-06-30.png"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+attachment/5593004/+files/Screenshot%20from%202022-05-25%2000-06-30.png

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

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

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

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

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

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

  Another reproduction case:

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

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

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

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


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

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

[IH]

Public bug reported:

failed to install initramfs-tools

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
Uname: Linux 5.16.19-76051619-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May 25 22:33:13 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-02-26 (88 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.8
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  failed to install initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  Uname: Linux 5.16.19-76051619-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May 25 22:33:13 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-02-26 (88 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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