[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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, PROT_READ|PROT

[Desktop-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

[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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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

[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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 fro

[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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[ExploreWiki]

Josef, did you try the workaround in the original post? The workaround
fixed the problem for me on  Ubuntu 22.10.



[ Workaround ]

Add to /etc/environment (in Ubuntu 22.04):

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

or in Ubuntu 22.10 and later:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and then reboot.



Full instructions:

1. Open terminal: CTRL + ALT + T
2. Type: sudo nano /etc/environment
3. Enter your password
4. Add the following on a new line: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
5. Press: Ctrl + O
6. Press: Enter
7. Press: Ctr + X
8. Type: Reboot

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


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

[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session

[Gunnar Hjalmarsson]

** Tags added: lunar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1956916

Title:
  Using certain xkb-options, e.g. Alt+Shift, for switching input sources
  not reflected by the input source indicator in a wayland session

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Currently, there is no way to define Left Alt + Left Shift key combination to 
change keyboard layouts in Ubuntu 22.04. In previous versions there was a 
convenient "Keyboard Layout Options" window in which there was able to set 
required key combination. Since 22.04 release I can't find a way to do that 
because useless "Keyboard Shortcuts" window opens instead in which unable to 
set Left Alt + Left Shift as "Switch to the next source" shortcut.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-01-07 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  jammy wayland-session ubiquity-22.04.3
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions


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

[Desktop-packages] [Bug 2009235] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2009235

Title:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  1

Status in firefox package in Ubuntu:
  New

Bug description:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Mar  3 14:31:57 2023
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2023-03-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: firefox
  Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2023-03-03 (0 days ago)

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


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

[Desktop-packages] [Bug 2009235] [NEW] package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Raphael]

Public bug reported:

package firefox (not installed) failed to install/upgrade: new firefox
package pre-installation script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: firefox (not installed)
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Mar  3 14:31:57 2023
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
InstallationDate: Installed on 2023-03-03 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: firefox
Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to kinetic on 2023-03-03 (0 days ago)

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


** Tags: amd64 apport-package kinetic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2009235

Title:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  1

Status in firefox package in Ubuntu:
  New

Bug description:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Mar  3 14:31:57 2023
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2023-03-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: firefox
  Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2023-03-03 (0 days ago)

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


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

[Desktop-packages] [Bug 2008798] Re: webkit2gtk 2.39.90 fails to build on riscv64

[Jeremy Bícha]

** Bug watch added: bugs.webkit.org/ #250681
   https://bugs.webkit.org/show_bug.cgi?id=250681

** Changed in: webkit
 Remote watch: bugs.webkit.org/ #252758 => bugs.webkit.org/ #250681

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2008798

Title:
  webkit2gtk 2.39.90 fails to build on riscv64

Status in Webkit:
  Unknown
Status in webkit2gtk package in Ubuntu:
  Triaged

Bug description:
  webkit2gtk fails to build on riscv64.

  Debian's experimental build logs suggest that 2.39.3 built fine on
  riscv64, but this error has occurred since 2.39.5.

  https://launchpad.net/ubuntu/+source/webkit2gtk/2.39.90-1ubuntu1

  There are more details on the upstream bug report.

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


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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Yuri Gor]

Fresh 22.04, at first gnome tweaks helped, but then I changed 
Settings / Keyboard / Switch input source individually for each window
And now even gnome tweaks doesn't work anymore.
Changing back to "Use the same source for all windows" also doesn't help.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1218322

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in GNOME Settings Daemon:
  Unknown
Status in System76:
  New
Status in Ubuntu Flashback:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in Ubuntu GNOME Flashback:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Unknown
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a combination of two modifier keys such as Ctrl+Shift
  -> the UI should reflect the new keys

  - add at least two input sources through gnome-control-center's text entry
    settings
  - press and release Ctrl+Shift
  -> the current input source should change

  [Regression Potential]

  That UI was not working before, it should only be an improvement (some
  key combos are not working as expected, that's another issue and
  shouldn't be mixed with this one)

  The input switching shortcut might capture other non-modifier
  shortcuts, but users will need to consider this when choosing their
  switching shortcut anyways. For users this bug affects, this
  represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  You can use the tag keyboard-layout-switching-hotkeys to find related bugs.
  
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys

  For using layout switching hotkeys in Unity Greeter, see bug 1245137.
  For using layout switching hotkeys in GNOME lockscreen, see bug 1244548.
  For using layout switching hotkeys in GNOME FlashBack sessions, see bug 
1687466 (at least ).

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions


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

[Desktop-packages] [Bug 1993621] Please test proposed package

[Steve Langasek]

Hello Yao, or anyone else affected,

Accepted xorg-server into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.3-2ubuntu2.8 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: xorg-server (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1993621

Title:
  Force update keyboard LEDs after calling EnableDevice to fix its
  hardware state after VT switching

Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * This change will force update keyboard LED status after calling
  EnableDevice, in order to resolve LED status not syncing after
  switching VT to a X session.

   * This also fixes the issue with NVIDIA driver and Xorg, that after
  resuming from suspend the keyboard LED is always off.

  [ Test Plan ]

  1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around)

  2. Turn on NumLock on the keyboard

  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to
  switch back to desktop

  NumLock LED should be on after switching back to the desktop

  [ Where problems could occur ]

   * The changes are to push status to the device when enabling it
  regardless of actual keyboard state change, therefore switching
  between VTs and adding/removing keyboard/mouse/xinput devices should
  be affected by this change.

  [ Original Report ]

  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

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


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

[Desktop-packages] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching

[Steve Langasek]

Hello Yao, or anyone else affected,

Accepted xorg-server into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.4-2ubuntu1.6 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: xorg-server (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

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

** Changed in: xorg-server (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1993621

Title:
  Force update keyboard LEDs after calling EnableDevice to fix its
  hardware state after VT switching

Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * This change will force update keyboard LED status after calling
  EnableDevice, in order to resolve LED status not syncing after
  switching VT to a X session.

   * This also fixes the issue with NVIDIA driver and Xorg, that after
  resuming from suspend the keyboard LED is always off.

  [ Test Plan ]

  1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around)

  2. Turn on NumLock on the keyboard

  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to
  switch back to desktop

  NumLock LED should be on after switching back to the desktop

  [ Where problems could occur ]

   * The changes are to push status to the device when enabling it
  regardless of actual keyboard state change, therefore switching
  between VTs and adding/removing keyboard/mouse/xinput devices should
  be affected by this change.

  [ Original Report ]

  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

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


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

[Desktop-packages] [Bug 19175] Re: nautilus: "extract here" terminates without giving a reason (no disk space)

[Shane McKee]

Extracting a tarball without enough space now shows that there is not
enough free space when you extract in nautilus. Screenshot attached

** Attachment added: "Screenshot from 2023-03-03 12-07-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/19175/+attachment/5651447/+files/Screenshot%20from%202023-03-03%2012-07-05.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/19175

Title:
  nautilus: "extract here" terminates without giving a reason (no disk
  space)

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  I chose "extract here" in nautilus on a rar file (multiple rar files, if that 
matters
  ).  It started extracting files, but kept on terminating the program over and 
over 
  without giving a reason.  It took me a while to figure out I didn't have 
enough space 
  on that partition.

  http://bugzilla.gnome.org/show_bug.cgi?id=313313:
  http://bugzilla.gnome.org/show_bug.cgi?id=313313

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/19175/+subscriptions


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

Re: [Desktop-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 Desktop
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
  d

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Josef Frola]

Hello guys. Is this being worked on? I am experiencing this issue using
Wayland on Lenovo ThinkPad P14s Gen 3 on Ubuntu 22.04.2 LTS. Would be
nice to not have to restart my PC every damn time :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


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

Re: [Desktop-packages] [Bug 2003653] Re: package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returne

[Stephen Hammonds]

Yes, I ran the command to reinstall libreoffice and everything is working
as it should and I got no errors.

On Mon, Feb 27, 2023 at 2:10 PM Rico Tzschichholz <
2003...@bugs.launchpad.net> wrote:

> Please try running the following command and let us know whether that
> fixes the problem:
>
> sudo apt install --reinstall libreoffice-common
>
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2003653
>
> Title:
>   package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to
>   install/upgrade: installed libreoffice-common package post-
>   installation script subprocess returned error exit status 134
>
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Problem detected while system was attempting to update software.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 22.10
>   Package: libreoffice-common 1:7.4.4-0ubuntu0.22.10.1
>   ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
>   Uname: Linux 5.19.0-29-generic x86_64
>   ApportVersion: 2.23.1-0ubuntu3
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   Date: Sun Jan 22 11:49:57 2023
>   ErrorMessage: installed libreoffice-common package post-installation
> script subprocess returned error exit status 134
>   InstallationDate: Installed on 2023-01-08 (14 days ago)
>   InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
>   PackageArchitecture: all
>   Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal,
> 3.10.6-1
>   PythonDetails: N/A
>   RelatedPackageVersions:
>dpkg 1.21.9ubuntu1
>apt  2.5.3
>   SourcePackage: libreoffice
>   Title: package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to
> install/upgrade: installed libreoffice-common package post-installation
> script subprocess returned error exit status 134
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003653/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2003653

Title:
  package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to
  install/upgrade: installed libreoffice-common package post-
  installation script subprocess returned error exit status 134

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Problem detected while system was attempting to update software.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libreoffice-common 1:7.4.4-0ubuntu0.22.10.1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jan 22 11:49:57 2023
  ErrorMessage: installed libreoffice-common package post-installation script 
subprocess returned error exit status 134
  InstallationDate: Installed on 2023-01-08 (14 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to 
install/upgrade: installed libreoffice-common package post-installation script 
subprocess returned error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1730201] Re: Show Nautilus bookmarks when right clicking on its dock icon

[Coeur Noir]

Does not work :

It holds a few seconds and stops running.


** Attachment added: "nautilus app at start"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730201/+attachment/5651419/+files/nautilus_app_at_start.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1730201

Title:
  Show Nautilus bookmarks when right clicking on its dock icon

Status in gnome-session package in Ubuntu:
  Opinion
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid

Bug description:
  Hi…

  Don't know if it's related to nautilus or dock.

  Bookmarks - default ones like documents, videos, pictures… or manually
  added ones through ctrl+d - are not displayed on right click on
  nautilus icon.

  Only [ new window | remove from favorites | details ] appear.

  ( I'm a little dubious about the details usefulness here, too )

  I expected all the bookmarks to be displayed on right click, like in
  Unity.

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


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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

[Andy Chi]

** Tags added: originate-from-2007815

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

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


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

[Desktop-packages] [Bug 1838249] Re: crash on startup

[Fabrice]

Hi, I have this bug too, how to change this bug status ? Thanx

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249

Title:
  crash on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-29 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Tags:  disco
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2018-10-29 (1207 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: libreoffice-core 1:7.2.5-0ubuntu0.21.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-28-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-27 (52 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1838249/+subscriptions


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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2008613] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2008613

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_actor_queue_destroy(NULL) [ubuntu-
  d...@ubuntu.com/locations.js:370]

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  just got this after updating to the new packages on 23.04 beta,

  Thank you

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-14.14-generic 6.1.6
  Uname: Linux 6.1.0-14-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 04:52:05 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-10-04 (144 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  JournalErrors:
   Feb 26 04:52:01 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 43.2-6ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to lunar on 2022-11-18 (99 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2008613/+subscriptions


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

[Desktop-packages] [Bug 2008613] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2008613

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_actor_queue_destroy(NULL) [ubuntu-
  d...@ubuntu.com/locations.js:370]

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  just got this after updating to the new packages on 23.04 beta,

  Thank you

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-14.14-generic 6.1.6
  Uname: Linux 6.1.0-14-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 04:52:05 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-10-04 (144 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  JournalErrors:
   Feb 26 04:52:01 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 43.2-6ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to lunar on 2022-11-18 (99 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2008613/+subscriptions


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

[Desktop-packages] [Bug 2009143] Re: I have clear my rubbish bin and next my computer go on the lock screen

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2008613, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2009143/+attachment/5651278/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2009143/+attachment/5651280/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2009143/+attachment/5651281/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 2008613
   gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) 
[ubuntu-d...@ubuntu.com/locations.js:370]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2009143

Title:
  I have clear my rubbish bin and next my computer go on the lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have clear my rubbish bin and next my computer go on the lock screen

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.2-1ubuntu1
  Uname: Linux 5.19.0-21-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  3 11:23:50 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1673971989
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/judemont
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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


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

[Desktop-packages] [Bug 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
49-1

---
gnome-shell-extension-appindicator (49-1) unstable; urgency=medium

  * New upstream release
  * appIndicator: Make sure AppIndicatorProxy init_async is a wrapper
  * dbusMenu: Unset shellItem icon property on destruction
  * dbusMenu: cleanup StIcon initialization
  * appIndicator: Keep retrying till MAX retries to get needed properies
  * promiseUtils: Update promisify polyfill to last gjs version
  * util: Add utility function to refresh all properties on proxy
  * appIndicator: Move proxy specific methods to AppIndicatorProxy
  * appIndicator: Avoid dynamically initialized proxy parameters
  * util: Add CancellableChild
  * appIndicator: Use CancellableChild for property operations
  * appIndicator: Set properties we depend on
  * appIndicator: Use cancellable child to handle icons loading cancellation
  * appIndicator: Simplify argbToRgba code to use less promises
  * appIndicator: Consider Resource scale to pick right icon size
  * appIndicator: Log error for overlay icons loading error too
  * iconCache: Actually perform Garbage Collection
  * iconCache: Ensure GC is repeated if there are items to clear
  * iconCache: Keep track of active icons inside the cache
  * appIndicator: Avoid creating prototypes for simple objects
  * appIndicator: Manually load the file icons as GdkPixbuf (LP: #1991709)
  * appIndicator: Disable caching of Gio.FileIcons textures
  * iconCache: Increase GC interval and icon lifetime
  * iconCache, appIndicator: Update active state for any icon cached
  * appIndicator: Add more class elements for repeated data
  * appIndicator: Use better naming for function refreshing proxy properties
  * appIndicator: Use an object to hold returned icon parameters
  * appIndicator: Never deep unpack pixmaps properties
  * appIndicator: Move pixmap-related functions to a custom file
  * appIndicator: Unset cached properties on proxy destruction
  * appIndicator: Freeze objects used as enums
  * appIndicator: Free the cached pixmaps variants when not needed
  * appIndicator: Load icons as pixbufs using the required height only
  * appIndicator: Avoid getting icon scaling multiple times

 -- Marco Trevisan (Treviño)   Fri, 03 Mar 2023
03:39:23 +0100

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1991709

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled 
extensions:
  gnome-extensions list --enabled
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com

  other info: 
  lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 22:35:24 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-03 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1991709/+subscriptions


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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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