[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

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


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

[Touch-packages] [Bug 1068553] Re: package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different f

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libgl1-mesa-
  dri/changelog.Debian.gz', which is different from other instances of
  package libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  Expired

Bug description:
  This was an automatic bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libgl1-mesa-dri 9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.51  Tue Sep 18 17:16:56 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Fri Oct 19 22:51:29 2012
  DistUpgraded: 2012-10-19 22:38:49,539 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current-updates, 304.51, 3.2.0-32-generic, x86_64: installed
   nvidia-current-updates, 304.51, 3.5.0-17-generic, x86_64: installed
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:2384]
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  JockeyStatus:
   kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, 
kernel module and VDPAU library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, 
Not in use)
  MachineType: Gigabyte Technology Co., Ltd. EX38-DQ6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=a4f5de5c-8804-4fe0-a0f1-22ca034917f3 ro quiet splash elevator=deadline
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 9.0-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which 
is different from other instances of package libgl1-mesa-dri:amd64
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (0 days ago)
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4B
  dmi.board.name: EX38-DQ6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EX38-DQ6
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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


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

[Touch-packages] [Bug 1063991] Re: mupen64plus crashes with illegal instruction

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  mupen64plus crashes with illegal instruction

Status in mesa package in Ubuntu:
  Expired

Bug description:
  haver@gamemaster:~$ mupen64plus n64/Mario_Kart_64/Mario\ Kart\ 64\ 
\(USA\).n64 
   __  __ __   _  _     _ 
  |  \/  |_   _ _ __   ___ _ __  / /_ | || | |  _ \| |_   _ ___ 
  | |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|  
  | |  | | |_| | |_) |  __/ | | | (_) |__   _|  __/| | |_| \__ \  
  |_|  |_|\__,_| .__/ \___|_| |_|\___/   |_| |_|   |_|\__,_|___/  
   |_| http://code.google.com/p/mupen64plus/  
  Mupen64Plus Console User-Interface Version 1.99.4

  UI-console: attached to core library 'Mupen64Plus Core' version 1.99.4
  Includes support for Dynamic Recompiler.
  Core: Goodname: Mario Kart 64 (U) [!]
  Core: Name: MARIOKART64
  Core: MD5: 3A67D9986F54EB282924FCA4CD5F6DFF
  Core: CRC: 3e5055b6 2e92da52
  Core: Imagetype: .v64 (byteswapped)
  Core: Rom size: 12582912 bytes (or 12 Mb or 96 Megabits)
  Core: Version: 1446
  Core: Manufacturer: Nintendo
  Core: Country: USA
  UI-Console: Cheat codes disabled.
  UI-console: using Video plugin: 'Mupen64Plus OpenGL Video Plugin by Rice' 
v1.99.4
  UI-console: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v1.99.4
  Input: N64 Controller #1: Forcing default keyboard configuration
  Input: Using auto-configuration for device 'Keyboard'
  UI-console: using Input plugin: 'Mupen64Plus SDL Input Plugin' v1.99.4
  UI-console: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP 
Plugin' v1.99.4
  Input: N64 Controller #1: Using keyboard/mouse
  Input: 1 controller(s) found, 1 plugged in and usable in the emulator
  Input: Mupen64Plus SDL Input Plugin version 1.99.4 initialized.
  Video: SSE processing enabled.
  Video: Found ROM 'Mario Kart 64', CRC b655503e52da922e-45
  Video: Enabled hacks for game: 'MARIOKART64'
  Video: Initializing OpenGL Device Context.
  Core: Setting 32-bit video mode: 640x480
  Video: Using OpenGL: Tungsten Graphics, Inc - Mesa DRI Intel(R) 945G  : 1.4 
Mesa 8.0.4
  Video: OpenGL Combiner: Fragment Program
  Audio: Initializing SDL audio subsystem...
  /dev/mixer: : No such file or directory
  Core: Starting R4300 emulator: Dynamic Recompiler
  Core: R4300: starting 64-bit dynamic recompiler at: 0x7fa578049200
  /dev/mixer: : No such file or directory
  Illegal instruction (core dumped)

  The window is popping up and after a while I am seeing an illegal
  instruction error.

  Here the end of the strace run:

  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/save", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  stat("/home/haver/.local/share/mupen64plus/save/", {st_mode=S_IFDIR|0700, 
st_size=4096, ...}) = 0
  open("/home/haver/.local/share/mupen64plus/save/Mario Kart 64 (U) [!].mpk", 
O_RDONLY) = 9
  fstat(9, {st_mode=S_IFREG|0664, st_size=131072, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7ff9f327b000
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  read(9, 
"\201\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"...,
 32768) = 32768
  close(9)= 0
  munmap(0x7ff9f327b000, 4096)= 0
  open("/home/haver/.local/share/mupen64plus/save/Mario Kart 64 (U) [!].mpk", 
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
  fstat(9, {st_mode=S_IFREG|0664, st_size=0, ...}) = 0
  mmap(NULL, 4096, 

[Touch-packages] [Bug 1071531] Re: package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to install/upgrade: libgl1-mesa-dri:amd64. The i386 packages seem to conflict with my 64-bit AMD machine and di

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to
  install/upgrade: libgl1-mesa-dri:amd64. The i386 packages seem to
  conflict with my 64-bit AMD machine and disable Synaptic.

Status in mesa package in Ubuntu:
  Expired

Bug description:
  I keep getting constant error messages that tell me that Ubuntu
  Software Center will not function until these unmet dependencies are
  resolved, and they can't be resolved.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Thu Oct 25 18:49:42 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 8.960, 3.2.0-23-generic, x86_64: installed
   fglrx-updates, 8.960, 3.2.0-24-generic, x86_64: installed
   fglrx-updates, 8.960, 3.2.0-27-generic, x86_64: installed
  DpkgTerminalLog:
   dpkg: error processing libgl1-mesa-dri:i386 (--configure):
libgl1-mesa-dri:i386 8.0.2-0ubuntu3.1 cannot be configured because 
libgl1-mesa-dri:amd64 is in a different version (8.0.3+8.0.2-0ubuntu3.2)
   dpkg: error processing libgl1-mesa-dri (--configure):
libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be configured because 
libgl1-mesa-dri:i386 is in a different version (8.0.2-0ubuntu3.1)
  ErrorMessage: libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be 
configured because libgl1-mesa-dri
  ExtraDebuggingInterest: I just need an easy workaround
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Device [1002:9647] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:169b]
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, 
Disabled, Not in use)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic 
root=UUID=34B0B293B0B25AD6 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 failed to 
install/upgrade: libgl1-mesa-dri:amd64 8.0.3+8.0.2-0ubuntu3.2 cannot be 
configured because libgl1-mesa-dri
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 169B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 18.1A
  dmi.chassis.asset.tag: 5CG2070LFS
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.46:bd01/16/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn169B:rvrKBCVersion18.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 06901320461620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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


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

[Touch-packages] [Bug 1080575] Re: package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different from

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libglapi-
  mesa/changelog.Debian.gz', which is different from other instances of
  package libglapi-mesa:amd64

Status in mesa package in Ubuntu:
  Expired

Bug description:
  crash after upgrade from 12.04 to 12.10

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libglapi-mesa 9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Sun Nov 18 01:42:18 2012
  DistUpgraded: 2012-11-18 01:33:26,098 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 9.000, 3.5.0-18-generic, x86_64: installed
   virtualbox, 4.1.18, 3.2.0-33-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-18-generic, x86_64: installed
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different from 
other instances of package libglapi-mesa:amd64
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:9715]
  InstallationDate: Installed on 2011-10-13 (402 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic 
root=UUID=2c4c4398-c1f6-4a17-b94d-505bec8059e9 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  Title: package libglapi-mesa 9.0-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which 
is different from other instances of package libglapi-mesa:amd64
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 1: X Error of failed request:  BadRequest (invalid request code or no 
such operation)
 Major opcode of failed request:  153 (GLX)
 Minor opcode of failed request:  19 (X_GLXQueryServerString)
 Serial number of failed request:  22
 Current serial number in output stream:  22
  UpgradeStatus: Upgraded to quantal on 2012-11-17 (1 days ago)
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: 880GXH/USB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd06/24/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GXH/USB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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 1:0.9.8.4+bzr3407-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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


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

[Touch-packages] [Bug 2007625] Re: New upstream microrelease 2.5.14

[Steve Langasek]

Hello Sergio, or anyone else affected,

Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: openldap (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  New upstream microrelease 2.5.14

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  Fix Committed
Status in openldap source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.14.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/TZQHR4SIWUA5BZTKDAKSFDOOGDVU4TU7/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4816

   * Upstream "call for testing":

  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/ZJTFCIIY3HHUZIHENR3TUDGGFWIVJOCF/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/XVFN3TCIDUZCWJA7RKFTZI2762UELAGM/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/YZIFGANGSBCV2E547KS5C6DJGJ4Z4CEX/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
    - kinetic: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25633699/+files/buildlog_ubuntu-kinetic-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.10.1~ppa1_BUILDING.txt.gz
    - jammy: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25601017/+files/buildlog_ubuntu-jammy-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz

   * Bileto ticket: N/A (bileto is not working at the moment)

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.13+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

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


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

[Touch-packages] [Bug 2007625] Re: New upstream microrelease 2.5.14

[Steve Langasek]

Hello Sergio, or anyone else affected,

Accepted openldap into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Changed in: openldap (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

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

Title:
  New upstream microrelease 2.5.14

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  In Progress
Status in openldap source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.14.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/TZQHR4SIWUA5BZTKDAKSFDOOGDVU4TU7/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4816

   * Upstream "call for testing":

  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/ZJTFCIIY3HHUZIHENR3TUDGGFWIVJOCF/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/XVFN3TCIDUZCWJA7RKFTZI2762UELAGM/
  
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/message/YZIFGANGSBCV2E547KS5C6DJGJ4Z4CEX/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
    - kinetic: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25633699/+files/buildlog_ubuntu-kinetic-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.10.1~ppa1_BUILDING.txt.gz
    - jammy: 
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap/+build/25601017/+files/buildlog_ubuntu-jammy-amd64.openldap_2.5.14+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz

   * Bileto ticket: N/A (bileto is not working at the moment)

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.13+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

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


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

[Touch-packages] [Bug 2009239] [NEW] Updating base-files at point releases is pointless, misleading, and causes confusion and anxiety

[Dimitri John Ledkov]

Public bug reported:

Updating base-files at point releases is pointless, misleading, and
causes confusing and anxiety

Can we please stop updating base-files at point releases?

Building new installer media, and calling it with a new .N number is
good, and helps to differentiate what the initial state the machine
roughly was, given that ultimately the serial # of the installer media
is what matters.

Updating base-files on the installed system => not so much. As it is an
artificial line in the sand that doesn't change anything to the systems,
that are continuously upgrading. The upgrade of base-files package,
doesn't require to refresh snaps to latest revisions; install debs of
latest versions; nor is anything else happening to force that (i.e.
copying all packages from -updates to -security, like debian does).

But it does cause confusion and anxiety among enterprise customers, who
notice an update to base-files and a change of prompts, and suddenly
demand to revert back from .2 release to .1. Which is understandable,
since point releases in other operating systems have longer timespan,
and are allowed to remain on an older substream for longer, and require
admin actions to upgrade. Which is not the case with Ubuntu. Our interim
releases, are actually closer to what windows/rhel call point releases.
Since they are distinct, one can skip them, and they have a different
time window. Our LTS is just a single stream of updates, which is
continiously maintained, and thus it should always be recognized on the
installed systems as "24.04 LTS".

references:

Windows 10 https://learn.microsoft.com/en-
us/lifecycle/products/windows-10-home-and-pro note how windows 10
support multiple year/half releases, which are a track one can stay on
for a long time, even as a new one is already out.

Rhel point release timeframes
https://access.redhat.com/support/policy/updates/errata#viii notice how
every other point release is supported for up to 4 years, and is a track
one can stay on for that period of time.

Whereas Ubuntu LTS is a single track, that one cannot get off. There
isn't a point release subtrack.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Updating base-files at point releases is pointless, misleading, and causes 
confusing and anxiety
+ Updating base-files at point releases is pointless, misleading, and causes 
confusion and anxiety

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

Title:
  Updating base-files at point releases is pointless, misleading, and
  causes confusion and anxiety

Status in base-files package in Ubuntu:
  New

Bug description:
  Updating base-files at point releases is pointless, misleading, and
  causes confusing and anxiety

  Can we please stop updating base-files at point releases?

  Building new installer media, and calling it with a new .N number is
  good, and helps to differentiate what the initial state the machine
  roughly was, given that ultimately the serial # of the installer media
  is what matters.

  Updating base-files on the installed system => not so much. As it is
  an artificial line in the sand that doesn't change anything to the
  systems, that are continuously upgrading. The upgrade of base-files
  package, doesn't require to refresh snaps to latest revisions; install
  debs of latest versions; nor is anything else happening to force that
  (i.e. copying all packages from -updates to -security, like debian
  does).

  But it does cause confusion and anxiety among enterprise customers,
  who notice an update to base-files and a change of prompts, and
  suddenly demand to revert back from .2 release to .1. Which is
  understandable, since point releases in other operating systems have
  longer timespan, and are allowed to remain on an older substream for
  longer, and require admin actions to upgrade. Which is not the case
  with Ubuntu. Our interim releases, are actually closer to what
  windows/rhel call point releases. Since they are distinct, one can
  skip them, and they have a different time window. Our LTS is just a
  single stream of updates, which is continiously maintained, and thus
  it should always be recognized on the installed systems as "24.04
  LTS".

  references:

  Windows 10 https://learn.microsoft.com/en-
  us/lifecycle/products/windows-10-home-and-pro note how windows 10
  support multiple year/half releases, which are a track one can stay on
  for a long time, even as a new one is already out.

  Rhel point release timeframes
  https://access.redhat.com/support/policy/updates/errata#viii notice
  how every other point release is supported for up to 4 years, and is a
  track one can stay on for that period of time.

  Whereas Ubuntu LTS is a single track, that one cannot get off. There
  isn't a point release subtrack.

To manage notifications 

[Touch-packages] [Bug 2007331] Please test proposed package

[Steve Langasek]

Hello Kai-Heng, or anyone else affected,

Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions


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

[Touch-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Steve Langasek]

Hello Kai-Heng, or anyone else affected,

Accepted pulseaudio into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-kinetic

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

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

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions


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

[Touch-packages] [Bug 2008393] Re: armhf dep8 failure due to restrictions changing apparmor profile status

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 8.2302.0-1ubuntu2

---
rsyslog (8.2302.0-1ubuntu2) lunar; urgency=medium

  * d/t/simple-*, d/t/control: ignore aa-enforce error, which can happen
on armhf in the Ubuntu DEP8 infrastructure, and allow-stderr for
these tests (LP: #2008393)

 -- Andreas Hasenack   Thu, 23 Feb 2023 18:56:07
-0300

** Changed in: rsyslog (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  armhf dep8 failure due to restrictions changing apparmor profile
  status

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  The armhf DEP8 testers in Ubuntu infrastructure have some restrictions
  and cannot change an apparmor profile. This is causing the tests to
  fail, because they try to make sure rsyslog is being tested in
  enforced mode:

  Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile
  Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode.

  ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd".
  Permission denied; attempted to load a profile while confined?

  The package migrated to lunar even with this error because it never
  had DEP8 tests before, and the armhf baseline was born in this error
  state.

  These are the LXD settings used for armhf containers:
  https://git.launchpad.net/autopkgtest-
  cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-
  cloud/tools/armhf-lxd.userdata#n76

  I created an armhf container on a pi4 host (arm64) with these
  settings, but couldn't reproduce the issue there. There is something
  else going on in the autopkgtest infra regarding arhmf.

  FTR, I created the container like this:

  lxc launch ubuntu-daily:lunar pi4:l-armhf \
  -c raw.lxc="apparmor.profile=unconfined" \
  -c raw.lxc="seccomp.profile=" \
  -c security.nesting=true

  EDIT: hm, the above actually doesn't work. Only the last raw.lxc value
  is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc-
  configuration-to-lxd/

  But still, apparmor works just fine. There is some other setup going
  on in the autopkgtest infrastructure.

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


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

[Touch-packages] [Bug 2009230] Re: AppArmor denials for rsyslog

[Georgia Garcia]

** Also affects: gce-compute-image-packages (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.
  
  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console
  
  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console
  
  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf
  
  So in gce cloud images, we are getting the following denials:
  
  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0
  
+ To fix it, we just need to add
+   /dev/console rw,
+ to /etc/apparmor.d/usr.sbin.rsyslogd
  
- To fix it, we just need to add 
-   /dev/console rw,
- to /etc/apparmor.d/usr.sbin.rsyslogd
+ or the same permission should be added to a file in
+ /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package

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

** Also affects: gce-compute-image-packages (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

Title:
  AppArmor denials for rsyslog

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in gce-compute-image-packages source package in Lunar:
  New
Status in rsyslog source package in Lunar:
  New

Bug description:
  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.

  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console

  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf

  So in gce cloud images, we are getting the following denials:

  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0

  To fix it, we just need to add
    /dev/console rw,
  to /etc/apparmor.d/usr.sbin.rsyslogd

  or the same permission should be added to a file in
  /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+subscriptions


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

[Touch-packages] [Bug 2009230] [NEW] AppArmor denials for rsyslog

[Georgia Garcia]

Public bug reported:

The AppArmor profile for rsyslog, which had been disabled on previous
Ubuntu versions, was enabled in lunar.

The package google-compute-engine added a config file to rsyslog which
requires rw access to /dev/console

google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
# Google Compute Engine default console logging.
#
# daemon: logging from Google provided daemons.
# kern: logging information in case of an unexpected crash during boot.
#
daemon,kern.* /dev/console

google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
google-compute-engine: /etc/rsyslog.d/90-google.conf

So in gce cloud images, we are getting the following denials:

[ 1500.302082] audit: type=1400 audit(1677876883.728:495):
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0


To fix it, we just need to add 
  /dev/console rw,
to /etc/apparmor.d/usr.sbin.rsyslogd

** Affects: gce-compute-image-packages (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  AppArmor denials for rsyslog

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.

  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console

  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf

  So in gce cloud images, we are getting the following denials:

  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0

  
  To fix it, we just need to add 
/dev/console rw,
  to /etc/apparmor.d/usr.sbin.rsyslogd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+subscriptions


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

[Touch-packages] [Bug 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Steve Langasek]

I'd like to understand better exactly how it happened that the user got
this crash.  Is it a matter of a corrupted .crash file on input, or is
it that the user tried to feed in a file that was not intended to be
input for apport-unpack?  I see that the command line that triggered
this appears to be taking a 'core' file as input rather than a file
ending in .crash, so I'm suspecting the latter.

If it's the latter, then I wouldn't normally consider this SRU-worthy
(though it's borderline to consider it as part of a larger SRU).

If it's the former, then I would be concerned about why the invalid
input happened in the first place, which I don't see addressed here.

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

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

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Incomplete

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing. This bug does not happen that often, but the fix
  for this bug is the foundation for the fix for bug #1995100.

  Test Plan
  =

  1. Create malformed report:
  ```
  printf 'AB\xfc:CD\n' > malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

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


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

[Touch-packages] [Bug 1993572] Re: samba profile: missing rule for mkdir /var/cache/samba/printing

[Steve Langasek]

Hello Andreas, or anyone else affected,

Accepted apparmor into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.7-1ubuntu2.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apparmor (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

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

Title:
  samba profile: missing rule for mkdir /var/cache/samba/printing

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  Users who chose to:

  a) install apparmor-profiles (a package with extra optional apparmor
  profiles, including samba)

  b) change the samba related profiles from complain (the default) to
  enforce mode

  will find out that sharing a printing in samba and using it won't
  work.

  In by itself this is *definitely* not worth an SRU for apparmor, which
  impacts all users of Ubuntu (because it's installed everywhere). But,
  if apparmor is to be updated for another more important reason, then
  this fix could be bundled together with it. Therefore I'm adding the
  block-proposed-kinetic tag to this bug.

  [ Test Plan ]

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

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

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

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

  Probe it via samba:
  rpcclient -Uroot%root localhost -c 'getprinter testprinter 2'
  (some printer related output, or even an error, doesn't matter)

  Check dmesg and look for an apparmor ALLOWED message:
  [497031.827841] audit: type=1400 audit(1669215188.733:555): 
apparmor="ALLOWED" operation="mkdir" class="file" 
namespace="root//lxd-l-samba-apparmor_" 
profile="samba-rpcd-spoolss" name="/var/cache/samba/printing/" pid=388168 
comm="rpcd_spoolss" requested_mask="c" denied_mask="c" fsuid=100 
ouid=100

  With the updated package, there should be no apparmor message for
  samba-rpcd-spoolss.

  NOTE: since, for this test, we are not switching the apparmor profile
  to enforce mode, this means that the mkdir attempted by rpcd_spoolss
  will succeed, and if you try the rpcclient command one more time,
  there will be no further apparmor messages about it in the logs.

  
  [ Where problems could occur ]

  This change is adding an apparmor rule to a samba-related apparmor
  profile. Without this rule (and with the apparmor profile in confine
  mode), then printing does not work, so regressing that aspect of it is
  hard.

  Maybe some exotic future security vulnerability could take advantage
  of this new apparmor rule which allows writing to (and therefore
  deleting from) /var/cache/samba/printing.

  What's more likely perhaps (but still rare) is that an apparmor
  upgrade, which triggers all apparmor profiles to be reloaded, would
  find some error in an existing profile and fail to load it, and
  perhaps stop loading all other profiles after that, perhaps leaving
  the system without confinement. But this should be caught by the
  upgrade process since postinst would exit non-zero (hopefully).

  [ Other Info ]
  Not at this time.

  [Original Description]

  After the fix for bug #1990692, one more rule is needed it seems.

  I put all samba profiles in enforce mode, and when I ran that final
  rpcclient command, got an error and an apparmor denied message:

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

  Set a password for the samba "root" user:
  

Re: [Touch-packages] [Bug 2009224] Bug is not a security issue

[George R Lunney]

This bug may NOT BE A SECURITY ISSUE, but without access to audio I
cannot do 90% of the work I do in Ubuntu. I suggest that you acknowledge
the problem and fix it. For the meantime I will be using Windows 10.

G


Bug description:
   I didn't have sound after an update to Ubuntu (and a reboot  the next day). 
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I 
have switched to Windows 10 (I have a dual boot computer).
   LSPCI finds my sound card but alsa and pacmd don't.
   Until this is fixed, I am no longer using UBuntu but am switching to Windows 
10.
   Let me know when this issue is resolved.

   ProblemType: Bug
   DistroRelease: Ubuntu 22.04
   Package: alsa-base 1.0.25+dfsg-0ubuntu7
   ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
   Uname: Linux 5.19.0-35-generic x86_64
   ApportVersion: 2.20.11-0ubuntu82.3
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1:  george 4472 F pipewire-media-
/dev/snd/pcmC1D0c:   george 4473 F...m pulseaudio
/dev/snd/seq:george 4471 F pipewire
   CasperMD5CheckResult: unknown
   CurrentDesktop: ubuntu:GNOME
   Date: Fri Mar  3 13:14:07 2023
   InstallationDate: Installed on 2021-07-19 (592 days ago)
   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
   PackageArchitecture: all
   ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
   SourcePackage: alsa-driver
   Symptom: audio
   Title: PCI/internal sound card not detected
   UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago)
   dmi.bios.date: 03/18/2016
   dmi.bios.release: 5.11
   dmi.bios.vendor: American Megatrends Inc.
   dmi.bios.version: R01-A3
   dmi.board.name: H11H4-AD2
   dmi.board.vendor: Acer
   dmi.board.version: V:1.1
   dmi.chassis.type: 3
   dmi.chassis.vendor: Acer
   dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku:
   dmi.product.family: Acer Desktop
   dmi.product.name: SoniaHC
   dmi.product.sku: 
   dmi.sys.vendor: Acer

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


On 3/3/23 2:09 PM, Paulo Flabiano Smorigo wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>

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

Title:
  pulseaudio does not recognize PCI SoundBlaster card

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I didn't have sound after an update to Ubuntu (and a reboot  the next day). 
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I 
have switched to Windows 10 (I have a dual boot computer).
  LSPCI finds my sound card but alsa and pacmd don't.
  Until this is fixed, I am no longer using UBuntu but am switching to Windows 
10.
  Let me know when this issue is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  george 4472 F pipewire-media-
   /dev/snd/pcmC1D0c:   george 4473 F...m pulseaudio
   /dev/snd/seq:george 4471 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  3 13:14:07 2023
  InstallationDate: Installed on 2021-07-19 (592 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago)
  dmi.bios.date: 03/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A3
  dmi.board.name: H11H4-AD2
  dmi.board.vendor: Acer
  dmi.board.version: V:1.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku:
  dmi.product.family: 

[Touch-packages] [Bug 2009224] Bug is not a security issue

[Paulo Flabiano Smorigo]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  pulseaudio does not recognize PCI SoundBlaster card

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I didn't have sound after an update to Ubuntu (and a reboot  the next day). 
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I 
have switched to Windows 10 (I have a dual boot computer).
  LSPCI finds my sound card but alsa and pacmd don't.
  Until this is fixed, I am no longer using UBuntu but am switching to Windows 
10.
  Let me know when this issue is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  george 4472 F pipewire-media-
   /dev/snd/pcmC1D0c:   george 4473 F...m pulseaudio
   /dev/snd/seq:george 4471 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  3 13:14:07 2023
  InstallationDate: Installed on 2021-07-19 (592 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago)
  dmi.bios.date: 03/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A3
  dmi.board.name: H11H4-AD2
  dmi.board.vendor: Acer
  dmi.board.version: V:1.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: SoniaHC
  dmi.product.sku: 
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 2009224] [NEW] pulseaudio does not recognize PCI SoundBlaster card

[George R Lunney]

Public bug reported:

I didn't have sound after an update to Ubuntu (and a reboot  the next day). 
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I 
have switched to Windows 10 (I have a dual boot computer).
LSPCI finds my sound card but alsa and pacmd don't.
Until this is fixed, I am no longer using UBuntu but am switching to Windows 10.
Let me know when this issue is resolved.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  george 4472 F pipewire-media-
 /dev/snd/pcmC1D0c:   george 4473 F...m pulseaudio
 /dev/snd/seq:george 4471 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  3 13:14:07 2023
InstallationDate: Installed on 2021-07-19 (592 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago)
dmi.bios.date: 03/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A3
dmi.board.name: H11H4-AD2
dmi.board.vendor: Acer
dmi.board.version: V:1.1
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: SoniaHC
dmi.product.sku: 
dmi.sys.vendor: Acer

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2009224

Title:
  pulseaudio does not recognize PCI SoundBlaster card

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I didn't have sound after an update to Ubuntu (and a reboot  the next day). 
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I 
have switched to Windows 10 (I have a dual boot computer).
  LSPCI finds my sound card but alsa and pacmd don't.
  Until this is fixed, I am no longer using UBuntu but am switching to Windows 
10.
  Let me know when this issue is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  george 4472 F pipewire-media-
   /dev/snd/pcmC1D0c:   george 4473 F...m pulseaudio
   /dev/snd/seq:george 4471 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  3 13:14:07 2023
  InstallationDate: Installed on 2021-07-19 (592 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago)
  dmi.bios.date: 03/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A3
  dmi.board.name: H11H4-AD2
  dmi.board.vendor: Acer
  dmi.board.version: V:1.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: SoniaHC
  dmi.product.sku: 
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Confirmed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Confirmed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Confirmed

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions


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

[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[Irham]

i have the same issue

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

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


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

[Touch-packages] [Bug 2006940] Re: PIN validation affects interface even if the manual token button is selected

[Nathan Teodosio]

** Merge proposal linked:
   
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438313

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

Title:
  PIN validation affects interface even if the manual token button is
  selected

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  1. software-properties-gtk 
  2. Go to Ubuntu Pro 
  3. Go to Enable Ubuntu Pro 
  4. Press "Or add token manually button" radio
  5. Go to ubuntu.com/pro/attach and submit the PIN

  Expected: Nothing happens until the user clicks "Enter code..." radio.

  Observed: UI is locked with "Valid token" message next to the manual
  token field, which won't allow to attach the token received from PIN
  validation.

  Similar issue happens when PIN expires instead of being validated.

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


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

[Touch-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Athos Ribeiro]

** Changed in: pixman (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

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


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

[Touch-packages] [Bug 2009168] Re: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: 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/2009168

Title:
  package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  every time i boot the computer an error appear on that package

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Mar  3 06:41:03 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-10-17 (136 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2009168] [NEW] package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Santiago Anaya]

Public bug reported:

every time i boot the computer an error appear on that package

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Mar  3 06:41:03 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-10-17 (136 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  every time i boot the computer an error appear on that package

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Mar  3 06:41:03 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-10-17 (136 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2009145] Re: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

[Launchpad Bug Tracker]

This bug was fixed in the package xubuntu-meta - 2.248

---
xubuntu-meta (2.248) lunar; urgency=medium

  * Refreshed dependencies
  * Added dbus-x11 to desktop-minimal-recommends, desktop-recommends
(LP: #2009145)

 -- Sean Davis   Fri, 03 Mar 2023 05:56:02 -0500

** Changed in: xubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

Status in xorg package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

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


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

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

[Sergio Callegari]

After further investigation, I would say that "Discover" wants to
upgrade a package (libmm-glib0) notwithstanding the fact that it is
phased and that apt does not want to upgrade it.

Funny enough, Discover does not indicate the other phased packages (it
is up to 24!) as upgradable.

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

Title:
  When apt keeps back packages due to phased updates, it should list
  them separately

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


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

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

[Sergio Callegari]

There is a further problem, I do not know if it should be a separate
issue.

The updates icon in the system tray now appears also when there are in
fact no updates that can be applied. Don't know if this actually depends
on the presence of updates that are phased out or on the presence of
Ubuntu Pro (esm-apps) that are not enabled.

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

Title:
  When apt keeps back packages due to phased updates, it should list
  them separately

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


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

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

[Lug Skeiwoker]

Hi, what is the current status? Apport seems to be default-enabled on
all the live images I tried. Also let me ask, the informational link
where one can query one’s own uploads, it does not seem to display
whether or not a coredump was uploaded. Could you provide the same? It
was said that if retracers fail, the coredump with all your data stays
for good in the system. it was nice if the tools would display such
problems and maybe offer a way to request deletion in case of accidental
submission.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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


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

[Touch-packages] [Bug 2009145] [NEW] Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

[Sean Davis]

Public bug reported:

Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

The dbus-x11 package is being deprecated. As a result, the Xfce packages
from upstream Debian no longer pull it in. Until the xorg packages have
been updated accordingly in Ubuntu, the Xubuntu settings found in
/etc/xdg/xdg-xubuntu are ignored.

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

** Affects: xubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lunar

** Summary changed:

- Xubuntu defaults are ignored
+ Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

** Description changed:

  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17
  
  The dbus-x11 package is being deprecated. As a result, the Xfce packages
  from upstream Debian no longer pull it in. Until the xorg packages have
  been updated accordingly in Ubuntu, the Xubuntu settings found in
- /etc/xdg are ignored.
+ /etc/xdg/xdg-xubuntu are ignored.

** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: lunar

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

Status in xorg package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

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


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

[Touch-packages] [Bug 1891016] Re: [Keyboard Layouts] No actual keyboard layouts for many languages

[නොදන්නා]

It seems keyboard layouts available for xkb layouts but not for m17n
layouts

** Changed in: console-setup (Ubuntu)
   Status: New => Invalid

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

Title:
  [Keyboard Layouts] No actual keyboard layouts for many languages

Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 20.4.1 LTS

  gsettings set org.gnome.desktop.input-sources show-all-sources true
  (done)

  On ubuntu, proper keyboard layouts not available for many languages. Below 
few examples
  - Chinese (Available layouts: Chinese, Hanyu Pinyin(altgr)
  - Sinhala (Available layouts: US, with sinhala letters, Sinhala (phonetic)
  and many other languages

  According above two examples, it's better to not add above mentioned
  layouts because no useful at all.

  See the windows 10, it has exact proper keyboard layouts for nearly
  all popular languages. Review them and implement the same for ubuntu

  Furthermore, there're huge amount of keyboard layouts available with
  english characters for many languages.(eg: japanese, thai and more)
  it's better remove them and basically duplicate with english keyboard
  layouts (or you may able to merge into english keyboards list if
  necessary)

  Read the conversation as well
  https://answers.launchpad.net/ubuntu/+question/692310

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


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

[Touch-packages] [Bug 2009110] Re: USB audio card not recognized

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  USB audio card not recognized

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My USB audio card, named CM383-80864, was plugged in and recognized in
  alsamixer but not shown in setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seeker-liu   1741 F wireplumber
   /dev/snd/controlC0:  seeker-liu   1741 F wireplumber
   /dev/snd/seq:seeker-liu   1737 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  3 13:47:25 2023
  InstallationDate: Installed on 2022-12-14 (79 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-12-19 (73 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.H0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.H0:bd07/27/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 2009110] [NEW] USB audio card not recognized

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My USB audio card, named CM383-80864, was plugged in and recognized in
alsamixer but not shown in setting.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  seeker-liu   1741 F wireplumber
 /dev/snd/controlC0:  seeker-liu   1741 F wireplumber
 /dev/snd/seq:seeker-liu   1737 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  3 13:47:25 2023
InstallationDate: Installed on 2022-12-14 (79 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2022-12-19 (73 days ago)
dmi.bios.date: 07/27/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.H0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.H0:bd07/27/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug kinetic wayland-session
-- 
USB audio card not recognized
https://bugs.launchpad.net/bugs/2009110
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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