Input / output devices keep restarting or changing their volume
This bug report will be marked for expiration in 38 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pipewire (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Pipewire or another tool is with a bug that keeps messing with the input/output devices.
caiotor
description: Desktop Computer
product: System Product Name (SKU)
vendor: System manufacturer
version: System Version
serial: System Serial Number
width: 64 bits
capabilities: smbios-3.1.1 dmi-3.1.1 smp vsyscall32
configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=1435e9b6-
*-core
description: Motherboard
product: PRIME H310M-E R2.0/BR
vendor: ASUSTeK COMPUTER INC.
physical id: 0
version: Rev X.0x
serial: 210565208200332
slot: Default string
*-firmware
vendor: American Megatrends Inc.
physical id: 0
version: 2208
date: 07/09/2021
size: 64KiB
capacity: 16MiB
*-memory
physical id: 38
slot: System board or motherboard
size: 48GiB
*-bank:0
slot: ChannelA-DIMM1
size: 32GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-bank:1
slot: ChannelB-DIMM1
size: 16GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-cache:0
physical id: 3c
slot: L1 Cache
size: 384KiB
capacity: 384KiB
*-cache:1
physical id: 3d
slot: L2 Cache
size: 1536KiB
capacity: 1536KiB
*-cache:2
physical id: 3e
slot: L3 Cache
size: 9MiB
capacity: 9MiB
*-cpu
product: Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz
vendor: Intel Corp.
physical id: 3f
bus info: cpu@0
version: 6.158.10
serial: To Be Filled By O.E.M.
slot: LGA1151
size: 3300MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
*-pci
product: 8th Gen Core Processor Host Bridge/DRAM Registers
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 07
width: 32 bits
clock: 33MHz
*-display
bus info: pci@0000:00:02.0
width: 64 bits
clock: 33MHz
*-usb
bus info: pci@0000:00:14.0
width: 64 bits
clock: 33MHz
bus info: usb@1
bus info: usb@2
bus info: pci@0000:00:16.0
width: 64 bits
clock: 33MHz
*-sata
bus info: pci@0000:00:17.0
width: 32 bits
clock: 66MHz
*-disk
bus info: scsi@1:0.0.0
*-pci:0
bus info: pci@0000:00:1c.0
width: 32 bits
clock: 33MHz
*-pci:1
bus info: pci@0000:00:1c.7
width: 32 bits
clock: 33MHz
bus info: pci@0000:02:00.0
*-pci:2
bus info: pci@0000:00:1d.0
width: 32 bits
clock: 33MHz
*-isa
bus info: pci@0000:00:1f.0
width: 32 bits
clock: 33MHz
*-memory UNCLAIMED
bus info: pci@0000:00:1f.2
width: 32 bits
clock: 33MHz (30.3ns)
bus info: pci@0000:00:1f.3
width: 64 bits
clock: 33MHz
*-serial
bus info: pci@0000:00:1f.4
width: 64 bits
clock: 33MHz
*-power UNCLAIMED
description: To Be Filled By O.E.M.
product: To Be Filled By O.E.M.
vendor: To Be Filled By O.E.M.
physical id: 1
version: To Be Filled By O.E.M.
serial: To Be Filled By O.E.M.
capacity: 32768mWh
*-input:0
product: Sleep Button
physical id: 2
logical name: input0
logical name: /dev/input/event0
*-input:1
product: Power Button
physical id: 3
logical name: input1
logical name: /dev/input/event1
*-input:2
product: Video Bus
physical id: 4
logical name: input10
logical name: /dev/input/event10
*-input:3
product: Power Button
physical id: 5
logical name: input2
logical name: /dev/input/event2
*-input:4
product: Eee PC WMI hotkeys
physical id: 6
logical name: input9
logical name: /dev/input/event9
*-network
description: Wireless interface
physical id: 7
bus info: usb@1:3
logical name: wlx90de803f5d82
serial: 90:de:80:3f:5d:82
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pipewire-pulse 1.0.5-1
ProcVersionSign
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sun May 26 16:00:30 2024
InstallationDate: Installed on 2024-05-26 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-
XDG_RUNTIME_
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures.
At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Please also ensure that you include the release and flavour of Ubuntu that you are using.
Thank you!