[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>

[Rik Mills]

Also: https://launchpad.net/ubuntu/+source/qtlocation-opensource-
src/5.15.6+dfsg-2

Bumped to High, as causing multiple FTBFS in Lunar

** Changed in: llvm-toolchain-15 (Ubuntu)
   Importance: Medium => High

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

Title:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
  Constant:i32<2>

Status in LLVM:
  Fix Released
Status in llvm-toolchain-15 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in openSUSE:
  Unknown

Bug description:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, 
Constant:i32<2>
    0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 
0x2f84090:1, Constant:i32<4>
  0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0x2aad434, 0x2f63a30, Constant:i32<64>
    0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23
  0x2f51c10: i32 = Register %23
    0x2f82500: i32 = Constant<64>
  0x2f81b28: i32 = Constant<4>
    0x2f81e40: i32 = Constant<2>
  In function: fs_variant_partial

  [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic-
  armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz]

  Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't
  determine what project "fs_variant_partial" is in. Sounds like it
  might be in some old version of Mesa? The start of the log suggests
  it's running on focal.

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


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

[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>

[Rik Mills]

https://launchpadlibrarian.net/632541247/buildlog_ubuntu-lunar-
armhf.qtquickcontrols-opensource-src_5.15.6-2_BUILDING.txt.gz

LLVM ERROR: Cannot select: 0x2c26c78: v4i32 = ARMISD::VCMPZ 0x2c79870, 
Constant:i32<2>
  0x2c79870: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.326)> 0x2c3a588, 
0x2c2d4d8, Constant:i32<4>
0x2c2d4d8: i32 = add 0x2c615c0, Constant:i32<64>
  0x2c615c0: i32,ch = CopyFromReg 0x27bc73c, Register:i32 %35
0x2c2e590: i32 = Register %35
  0x2c48da8: i32 = Constant<64>
0x2c639c0: i32 = Constant<4>
  0x2c63b70: i32 = Constant<2>
In function: fs_variant_partial
Aborted (core dumped)


similar with qtdatavis3d-everywhere-src and qtdeclarative-opensource-src

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

Title:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
  Constant:i32<2>

Status in LLVM:
  Fix Released
Status in llvm-toolchain-15 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in openSUSE:
  Unknown

Bug description:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, 
Constant:i32<2>
    0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 
0x2f84090:1, Constant:i32<4>
  0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0x2aad434, 0x2f63a30, Constant:i32<64>
    0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23
  0x2f51c10: i32 = Register %23
    0x2f82500: i32 = Constant<64>
  0x2f81b28: i32 = Constant<4>
    0x2f81e40: i32 = Constant<2>
  In function: fs_variant_partial

  [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic-
  armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz]

  Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't
  determine what project "fs_variant_partial" is in. Sounds like it
  might be in some old version of Mesa? The start of the log suggests
  it's running on focal.

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


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

[Touch-packages] [Bug 1957909] Re: NetworkManager connectivity check fails

[Matthias Harter]

Still a problem in latest Ubuntu.

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

Title:
  NetworkManager connectivity check fails

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I randomly receive "No internet connection available" notification,
  even if my internet connection is stable. (Not the exact term)

  In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint 
  http://connectivity-check.ubuntu.com./
  is used. I manually pinged the endpoint.
  I live in europe and the server is located in the US. The latency is about 
160ms. Usually I have an approximate latency of 15ms.
  It is not a problem of my ISP, I receive this notification on different 
locations in Germany and Switzerland.

  I propose to use another endpoint or provide another server for the same 
endpoint for europe.
  So the DNS servers in europe provide the IP of a server located in europe.

  The config comes from the package "network-manager-config-
  connectivity-ubuntu" version 1.32.12-0ubuntu1.

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


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

[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)

[Daniel Johnson]

Starting today I will be running the copy next to an htop window ready
to capture screenshots (before, during, and after failure).  The first
run today did not fail.  I used a variation of your script to copy the
source file multiple times to different file names, in the hope that
taking my main storage to nearly-full might have an impact but it still
did not fail.

There will be another copy tonight / tomorrow.  I will keep you updated.
Thank you for your aid in trying to reproduce this on your system, too!

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

Title:
  systemd kills gnome-shell or gnome-terminal if gnome-terminal uses
  much memory (50% over 20s)

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  or
  "stress-ng --stack 0 --timeout 300"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup belongs to terminal.

  Both Wayland and Xorg can reproduce.

  over ssh and in multi-user.target work good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1985887/+subscriptions


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

[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

[John Goodman]

Sorry if I'm missing something obvious but I've done a full apt upgrade
and tried to build wine again and the problem still persists so I don't
think the fix has released and the status is incorrect.

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

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils-mingw-w64 package in Ubuntu:
  Triaged
Status in binutils source package in Jammy:
  Fix Released
Status in binutils-mingw-w64 source package in Jammy:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

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


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

[Touch-packages] [Bug 1995804] [NEW] 'more' locks up terminal

[Skewray]

Public bug reported:

When I run /bin/more in a terminal window (tried both LXTerminal and
xterm), the tab terminal application locks up at the end of the file and
is no longer responsive to keyboard input. Old window text below the end
of the file being 'more'ed is not erased. A new tab created in the same
application window works fine.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: util-linux 2.38-4ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sun Nov  6 09:16:58 2022
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 SHELL=/bin/tcsh
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  'more' locks up terminal

Status in util-linux package in Ubuntu:
  New

Bug description:
  When I run /bin/more in a terminal window (tried both LXTerminal and
  xterm), the tab terminal application locks up at the end of the file
  and is no longer responsive to keyboard input. Old window text below
  the end of the file being 'more'ed is not erased. A new tab created in
  the same application window works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: util-linux 2.38-4ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Nov  6 09:16:58 2022
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used

[Jeremy]

** Bug watch added: Linux Kernel Bug Tracker #216668
   https://bugzilla.kernel.org/show_bug.cgi?id=216668

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=216668
   Importance: Unknown
   Status: Unknown

** Project changed: bluez => linux

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

Title:
  MT7921K high latency when bluetooth headset is used

Status in Linux:
  Unknown
Status in bluez package in Ubuntu:
  New

Bug description:
  When I use onboard WiFi and Bluetooth headset at the same time, the
  latency goes from ~30-50ms to 200-6500ms

  Motherboard: ASUS TUF GAMING X670E-PLUS WIFI
  BIOS: 0809

  Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream
  6.0.[135]

  $ lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  Also made upstream kernel bz:
  https://bugzilla.kernel.org/show_bug.cgi?id=216668

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  Uname: Linux 6.0.5-060005-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 15:44:14 2022
  InstallationDate: Installed on 2022-10-15 (22 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic 
root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2022
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 10:6F:D9:DD:4A:B0  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN 
RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0
TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0

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


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

[Touch-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  MT7921K high latency when bluetooth headset is used

Status in bluez package in Ubuntu:
  New

Bug description:
  When I use onboard WiFi and Bluetooth headset at the same time, the
  latency goes from ~30-50ms to 200-6500ms

  Motherboard: ASUS TUF GAMING X670E-PLUS WIFI
  BIOS: 0809

  Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream
  6.0.[135]

  $ lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  Also made upstream kernel bz:
  https://bugzilla.kernel.org/show_bug.cgi?id=216668

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  Uname: Linux 6.0.5-060005-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 15:44:14 2022
  InstallationDate: Installed on 2022-10-15 (22 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic 
root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2022
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 10:6F:D9:DD:4A:B0  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN 
RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0
TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0

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


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

[Touch-packages] [Bug 1995798] [NEW] MT7921K high latency when bluetooth headset is used

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I use onboard WiFi and Bluetooth headset at the same time, the
latency goes from ~30-50ms to 200-6500ms

Motherboard: ASUS TUF GAMING X670E-PLUS WIFI
BIOS: 0809

Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream
6.0.[135]

$ lsb_release -rd
Description:Ubuntu 22.10
Release:22.10

Also made upstream kernel bz:
https://bugzilla.kernel.org/show_bug.cgi?id=216668

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: bluez 5.65-0ubuntu1
Uname: Linux 6.0.5-060005-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  6 15:44:14 2022
InstallationDate: Installed on 2022-10-15 (22 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic 
root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2022
dmi.bios.release: 8.9
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0809
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 10:6F:D9:DD:4A:B0  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN 
RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0
TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0

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


** Tags: amd64 apport-bug kinetic wayland-session
-- 
MT7921K high latency when bluetooth headset is used
https://bugs.launchpad.net/bugs/1995798
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

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

[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)

[jeremyszu]

Hi Daniel,

Finally, I tried to reproduce your scenario on my side but not able to
reproduce.

* Environment:
ubuntu 22.04
64G RAM (allocated a process to occupy 32G RAN)
NVMe storage
32G micron SD card (dd /dev/random to a 29G file)

* A script to reproduce:
#!/bin/bash

count=0
file="29G-file"
while [ 1 ]; do
count=$((count+1))
echo "--the $count times"
rm ${HOME}/${file}
sync
echo 3 | sudo tee /proc/sys/vm/drop_caches
ionice -c3 nice cp -a /mnt/mmc/${file} ${HOME}/${file}
sync
done

The result is it was pass 25 times of copying file.
I was monitor the system resource that in my case, the swapping was not trigger 
and the copy action didn't consume too many memory.

Could you please help to monitor the memory usage when you try to copy
file?

** Attachment added: "Screenshot from 2022-11-06 17-12-51.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+attachment/5629411/+files/Screenshot%20from%202022-11-06%2017-12-51.png

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

Title:
  systemd kills gnome-shell or gnome-terminal if gnome-terminal uses
  much memory (50% over 20s)

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  or
  "stress-ng --stack 0 --timeout 300"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup belongs to terminal.

  Both Wayland and Xorg can reproduce.

  over ssh and in multi-user.target work good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1985887/+subscriptions


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

Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Tim Richardson]

unconfinded snaps don't have thie problem (that is, --classic snaps), these
bypass all the snap sandboxing and I guess this means they bypass the
controls and restrictions of cgroups. If you want this fixed, you have to
get x2go fixed. Report the bug there.

On Sun, 6 Nov 2022 at 21:05, Luigi Caiazza <1951...@bugs.launchpad.net>
wrote:

> Same issue here.
>
> My configuration is a fresh install of Ubuntu Mate 22.04 LTS, meant to
> be used both locally and remotely (via X2GO).
>
> From local sessions, I have no anomalies for each application installed
> via snap, so I am sure that the system works like a charm under some
> conditions. In contrast, if I log in from a remote session and I try to
> start almost all applications installed via snap (e.g., Firefox, Brave,
> Arduino IDE), I fall into:
>
> /user.slice/user-1000.slice/session-14.scope is not a snap cgroup
>
> The "strange" thing is that I found an application that works pretty well
> even through remote sessions: Visual Studio Code, installed using this
> command:
> sudo snap install code --classic
>
> I have not yet understood what can make the difference here, but to have
> a full working system I prefer to rely on a sort of bugfixing, rather
> than (permanently) apply some workaround that distorts the behaviour of
> the system.
>
> I am curious to know why Visual Studio Code works (maybe the classic
> confinement?). Please, inform us if you get the point.
>
> Thank you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
>   Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>

-- 
Tim Richardson

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

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


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

[Touch-packages] [Bug 1995790] [NEW] apt-patterns does not work as described in man pages

[Mekaniserad Apelsin]

Public bug reported:

The awesome apt has a some wonderful tips on their EXAMPLES section
(printed below). The choice of name to "garbage" might not have been the
best but the function is extremely useful.

$ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
   apt remove ?garbage
   Remove all packages that are automatically installed and no longer 
needed -
   same as apt autoremove

   apt purge ?config-files
   Purge all packages that only have configuration files left

   apt list '~i !~M (~slibs|~sperl|~spython)'
   List all manually-installed packages in sections matching libs, 
perl, or
   python.

Lets mark a package as automatically installed, and use the examples.

$ sudo apt-mark auto shotwell
shotwell set to automatically installed.

$ sudo apt remove ?garbage
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libraw20 shotwell shotwell-common
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ sudo apt autoremove 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  libraw20 shotwell shotwell-common
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 9.806 kB disk space will be freed.
Do you want to continue? [Y/n] N
Abort.

Apt-patterns works as it should everywhere else, as far as I can see, it
works wonders with ie `apt list '~g|~c'` and many other applications. I
used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I
feel this is a regression.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.8
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  6 10:57:52 2022
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

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


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

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

Title:
  apt-patterns does not work as described in man pages

Status in apt package in Ubuntu:
  New

Bug description:
  The awesome apt has a some wonderful tips on their EXAMPLES section
  (printed below). The choice of name to "garbage" might not have been
  the best but the function is extremely useful.

  $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
 apt remove ?garbage
 Remove all packages that are automatically installed and no longer 
needed -
 same as apt autoremove

 apt purge ?config-files
 Purge all packages that only have configuration files left

 apt list '~i !~M (~slibs|~sperl|~spython)'
 List all manually-installed packages in sections matching libs, 
perl, or
 python.

  Lets mark a package as automatically installed, and use the examples.

  $ sudo apt-mark auto shotwell
  shotwell set to automatically installed.

  $ sudo apt remove ?garbage
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libraw20 shotwell shotwell-common
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt autoremove 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
libraw20 shotwell shotwell-common
  0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
  After this operation, 9.806 kB disk space will be freed.
  Do you want to continue? [Y/n] N
  Abort.

  Apt-patterns works as it should everywhere else, as far as I can see,
  it works wonders with ie `apt list '~g|~c'` and many other
  applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04
  for years, so I feel this is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.8
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 10:57:52 2022
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Luigi Caiazza]

Same issue here.

My configuration is a fresh install of Ubuntu Mate 22.04 LTS, meant to
be used both locally and remotely (via X2GO).

>From local sessions, I have no anomalies for each application installed
via snap, so I am sure that the system works like a charm under some
conditions. In contrast, if I log in from a remote session and I try to
start almost all applications installed via snap (e.g., Firefox, Brave,
Arduino IDE), I fall into:

/user.slice/user-1000.slice/session-14.scope is not a snap cgroup

The "strange" thing is that I found an application that works pretty well even 
through remote sessions: Visual Studio Code, installed using this command:
sudo snap install code --classic

I have not yet understood what can make the difference here, but to have
a full working system I prefer to rely on a sort of bugfixing, rather
than (permanently) apply some workaround that distorts the behaviour of
the system.

I am curious to know why Visual Studio Code works (maybe the classic
confinement?). Please, inform us if you get the point.

Thank you.

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

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


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

[Touch-packages] [Bug 1995785] Re: package libasound2-plugins (not installed) failed to install/upgrade: 共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' を上書きしようとしています。これはパッケージ libasound2

[th234]

Running "sudo dpkg --configure --pending" solved the problem.

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

Title:
  package libasound2-plugins (not installed) failed to install/upgrade:
  共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example'
  を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  When I install winehq-devel according to the instructions on the
  official website（https://wiki.winehq.org/Ubuntu）, I get the following
  error and cannot install libasound2-plugins.

  処理中にエラーが発生しました:
   
/tmp/apt-dpkg-install-Ah9NHP/173-libasound2-plugins_1.2.7.1-1ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libasound2-plugins (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Nov  6 12:25:27 2022
  ErrorMessage: 共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
  InstallationDate: Installed on 2022-11-04 (1 days ago)
  InstallationMedia: Ubuntu 22.04 "Jammy Jellyfish" - Release amd64(20220502)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins (not installed) failed to install/upgrade: 
共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
  UpgradeStatus: Upgraded to kinetic on 2022-11-04 (1 days ago)

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


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

[Touch-packages] [Bug 1995785] [NEW] package libasound2-plugins (not installed) failed to install/upgrade: 共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' を上書きしようとしています。これはパッケージ libasoun

[taichi]

Public bug reported:

When I install winehq-devel according to the instructions on the
official website（https://wiki.winehq.org/Ubuntu）, I get the following
error and cannot install libasound2-plugins.

処理中にエラーが発生しました:
 /tmp/apt-dpkg-install-Ah9NHP/173-libasound2-plugins_1.2.7.1-1ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: libasound2-plugins (not installed)
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun Nov  6 12:25:27 2022
ErrorMessage: 共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
InstallationDate: Installed on 2022-11-04 (1 days ago)
InstallationMedia: Ubuntu 22.04 "Jammy Jellyfish" - Release amd64(20220502)
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: alsa-plugins
Title: package libasound2-plugins (not installed) failed to install/upgrade: 
共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
UpgradeStatus: Upgraded to kinetic on 2022-11-04 (1 days ago)

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


** Tags: amd64 apport-package kinetic

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

Title:
  package libasound2-plugins (not installed) failed to install/upgrade:
  共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example'
  を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  When I install winehq-devel according to the instructions on the
  official website（https://wiki.winehq.org/Ubuntu）, I get the following
  error and cannot install libasound2-plugins.

  処理中にエラーが発生しました:
   
/tmp/apt-dpkg-install-Ah9NHP/173-libasound2-plugins_1.2.7.1-1ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libasound2-plugins (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Nov  6 12:25:27 2022
  ErrorMessage: 共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
  InstallationDate: Installed on 2022-11-04 (1 days ago)
  InstallationMedia: Ubuntu 22.04 "Jammy Jellyfish" - Release amd64(20220502)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins (not installed) failed to install/upgrade: 
共有されている '/etc/alsa/conf.d/99-pulseaudio-default.conf.example' 
を上書きしようとしています。これはパッケージ libasound2-plugins:amd64 の他の実体と異なります
  UpgradeStatus: Upgraded to kinetic on 2022-11-04 (1 days ago)

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


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