[Touch-packages] [Bug 1947194] [NEW] Wayland only partially works

2021-10-14 Thread Chris Hall
Public bug reported:

When using Wayland in 21.04, the display often never wakes up after lock
up. Also, on boot up, desktop icons and most favorites on dash are not
displayed, even though desktop icons are enabled. I can get them to show
up only by re-enabling desktop icons. The workaround now is to disable
Wayland, and the original xorg server works fine. The display driver is:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)

The monitor is an HP 22cwa running of of a displayport interface.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 14 14:32:26 2021
DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
InstallationDate: Installed on 2018-12-04 (1044 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. OptiPlex 990
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
dmi.bios.date: 11/24/2011
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute third-party-packages ubuntu

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

Title:
  Wayland only partially works

Status in xorg package in Ubuntu:
  New

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: 

[Touch-packages] [Bug 1948978] [NEW] Thunderbird write e-mail window never released in wayland

2021-10-27 Thread Chris Hall
Public bug reported:

If I run Thunderbird (latest version), when I write an e-mail or reply
to an e-mail, a new window opens. When I send the e-mail, it works
correctly and the e-mail is sent, but the red dot on the Thunderbird
icon on the task bar never goes out. If I close or pkill Thunderbird,
only the main Thunderbird window is released by the display manager and
it is not possible to open Thunderbird again without logging out or
restarting gdm3. This is with Wayland. There is no Thunderbird process
left to kill.

Everything works fine with Xorg, so on this computer running 21.10, I
will be using Xorg instead of Wayland for now.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 27 14:53:29 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
   Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
InstallationDate: Installed on 2020-03-06 (600 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: TOSHIBA Satellite L305
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=baeb07e4-08ee-4d13-be78-7571c5723e1d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd12/09/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-04X02F:skuMontevina_Fab:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite L305
dmi.product.sku: Montevina_Fab
dmi.product.version: PSLB8U-04X02F
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


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

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

Title:
  Thunderbird write e-mail window never released in wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  If I run Thunderbird (latest version), when I write an e-mail or reply
  to an e-mail, a new window opens. When I send the e-mail, it works
  correctly and the e-mail is sent, but the red dot on the Thunderbird
  icon on the task bar never goes out. If I close or pkill Thunderbird,
  only the main Thunderbird window is released by the display manager
  and it is not possible to open Thunderbird again without logging out
  or restarting gdm3. This is with Wayland. There is no Thunderbird
  process left to kill.

  Everything works fine with Xorg, so on this computer running 21.10, I
  will be using Xorg instead of Wayland for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 14:53:29 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 

[Touch-packages] [Bug 1987939] [NEW] Suspend does not work with Wayland. OK with Xorg

2022-08-27 Thread Chris Hall
Public bug reported:

Automatic suspend requires hard reboot. Manual suspend initiates
restart. When Wayland is disabled, behavior goes back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd 249.11-0ubuntu3.4
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 27 09:39:18 2022
InstallationDate: Installed on 2022-06-06 (81 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
 Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
 Bus 001 Device 002: ID 5986:210e Acer, Inc EasyCamera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80XB
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=16aed434-ebdc-44fa-b56a-895d07782547 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.release: 2.51
dmi.bios.vendor: LENOVO
dmi.bios.version: 4QCN51WW(V2.15)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad FLEX 5-1570
dmi.ec.firmware.release: 2.51
dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn80XB:pvrLenovoideapadFLEX5-1570:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX5-1570:skuLENOVO_MT_80XB_BU_idea_FM_ideapadFLEX5-1570:
dmi.product.family: ideapad FLEX 5-1570
dmi.product.name: 80XB
dmi.product.sku: LENOVO_MT_80XB_BU_idea_FM_ideapad FLEX 5-1570
dmi.product.version: Lenovo ideapad FLEX 5-1570
dmi.sys.vendor: LENOVO

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


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

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

Title:
  Suspend does not work with Wayland. OK with Xorg

Status in systemd package in Ubuntu:
  New

Bug description:
  Automatic suspend requires hard reboot. Manual suspend initiates
  restart. When Wayland is disabled, behavior goes back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 27 09:39:18 2022
  InstallationDate: Installed on 2022-06-06 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:210e Acer, Inc EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=16aed434-ebdc-44fa-b56a-895d07782547 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN51WW(V2.15)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 5-1570
  dmi.ec.firmware.release: 2.51
  dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn80XB:pvrLenovoideapadFLEX5-1570:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX5-1570:skuLENOVO_MT_80XB_BU_idea_FM_ideapadFLEX5-1570:
  dmi.product.family: ideapad FLEX 5-1570
  dmi.product.name: 80XB
  dmi.product.sku: LENOVO_MT_80XB_BU_idea_FM_ideapad FLEX 5-1570
  dmi.product.version: Lenovo ideapad FLEX 5-1570
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

Re: [Touch-packages] [Bug 1987939] Re: Suspend does not work with Wayland. OK with Xorg

2022-09-17 Thread Chris Hall
My problem is that my Lenovo Ideapad Flex 5-1570 in dual boot mode would 
not come out of suspend if Wayland was active. Behavior is fine with 
Xorg. Suspend requires a hard reset. I was not sure what package to use 
for the ubuntu-bug report. It could have been mutter I suppose. To 
recreate the problem, I'd have to enable Wayland. There's no "crash" per 
se, just a hard reset. If you can specify what files to send and where 
to send them, I can try. However, I'm not keen on risking possible file 
system corruption.


On 9/16/2022 1:17 PM, Nick Rosbrook wrote:
> I'm not sure I understand the problem you are experiencing. Can you
> please expand on what you are trying to do, and what unexpected behavior
> you are seeing?
>
> Ideally, if you could provide steps to reproduce the problem, we can
> better investigate the issue.
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Suspend does not work with Wayland. OK with Xorg

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspend requires hard reboot. Manual suspend initiates
  restart. When Wayland is disabled, behavior goes back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 27 09:39:18 2022
  InstallationDate: Installed on 2022-06-06 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:210e Acer, Inc EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=16aed434-ebdc-44fa-b56a-895d07782547 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN51WW(V2.15)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 5-1570
  dmi.ec.firmware.release: 2.51
  dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn80XB:pvrLenovoideapadFLEX5-1570:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX5-1570:skuLENOVO_MT_80XB_BU_idea_FM_ideapadFLEX5-1570:
  dmi.product.family: ideapad FLEX 5-1570
  dmi.product.name: 80XB
  dmi.product.sku: LENOVO_MT_80XB_BU_idea_FM_ideapad FLEX 5-1570
  dmi.product.version: Lenovo ideapad FLEX 5-1570
  dmi.sys.vendor: LENOVO

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


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


Re: [Touch-packages] [Bug 1987939] Re: Suspend does not work with Wayland. OK with Xorg

2022-09-17 Thread Chris Hall
I just booted into 22.04 with Wayland and the computer woke OK from 
suspend both on power save and closing the lid, so it may be that some 
recent updates have fixed the problem.

On 9/16/22 13:17, Nick Rosbrook wrote:
> I'm not sure I understand the problem you are experiencing. Can you
> please expand on what you are trying to do, and what unexpected behavior
> you are seeing?
>
> Ideally, if you could provide steps to reproduce the problem, we can
> better investigate the issue.
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Suspend does not work with Wayland. OK with Xorg

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspend requires hard reboot. Manual suspend initiates
  restart. When Wayland is disabled, behavior goes back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 27 09:39:18 2022
  InstallationDate: Installed on 2022-06-06 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:210e Acer, Inc EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=16aed434-ebdc-44fa-b56a-895d07782547 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN51WW(V2.15)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 5-1570
  dmi.ec.firmware.release: 2.51
  dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn80XB:pvrLenovoideapadFLEX5-1570:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX5-1570:skuLENOVO_MT_80XB_BU_idea_FM_ideapadFLEX5-1570:
  dmi.product.family: ideapad FLEX 5-1570
  dmi.product.name: 80XB
  dmi.product.sku: LENOVO_MT_80XB_BU_idea_FM_ideapad FLEX 5-1570
  dmi.product.version: Lenovo ideapad FLEX 5-1570
  dmi.sys.vendor: LENOVO

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


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


Re: [Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Chris Hall
Well, on one of my machines I installed Mesa from the kisak more stable 
ppa ("turtle"), which is more up to date than mesa from the jammy 
repository. I was able to re-enable hardware acceleration with no 
problems. So there is something in the whole collection of mesa packages 
that broke several chromium based browsers.

On 5/26/23 11:14 AM, Nathan Teodosio wrote:
>> Any idea if the mesa driver
>> problem will be addressed in the next update?
> Time will tell, if my reading of #12 is correct then this isn't really a
> problem with Mesa but with upstream.
>
>> An ironic thing about the about://gpu url is that unless you disable the
>> gpu, it's not possible to even read  the url. A real chicken and egg
>> problem.
> One could do a blind
>
> Ctrl+L
> about:gpu
> 
> 
>
> to get the report to clipboard, but you would never know that without
> seeing the page. (:
>
> That information isn't otherwise available even with
> --enable-logging=stderr --v=1...
>

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions


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


[Touch-packages] [Bug 2020796] [NEW] Latest Ubuntu update kills Chrome and Brave

2023-05-25 Thread Chris Hall
Public bug reported:

The update installed this morning (May 25, 2023) disabled both Brave and
Chrome. Firefox is OK. I have installed a newer Brave-beta and it works
fine. The problem first appeared in Xorg, where no page could be
rendered, including settings. I then rebooted into Wayland and Brave and
Chrome can render pictures but not text. The Brave version is brave-
browser/stable,now 1.51.118 amd64 [installed]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 25 11:26:48 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 bcmwl/6.30.223.271+bdcom, 5.19.0-41-generic, x86_64: installed
 bcmwl/6.30.223.271+bdcom, 5.19.0-42-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity 2 [Radeon HD 7520G] [103c:1992]
InstallationDate: Installed on 2022-06-15 (344 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Hewlett-Packard HP ProBook 645 G1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=20cda528-3e8f-4a58-b19f-969a0f06aae3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2018
dmi.bios.release: 1.47
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L72 Ver. 01.47
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1992
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 05.34
dmi.chassis.asset.tag: 016269
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 5.52
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL72Ver.01.47:bd07/30/2018:br1.47:efr5.52:svnHewlett-Packard:pnHPProBook645G1:pvrA3009DD10303:rvnHewlett-Packard:rn1992:rvrKBCVersion05.34:cvnHewlett-Packard:ct10:cvr:skuD2Z92AV:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 645 G1
dmi.product.sku: D2Z92AV
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Latest Ubuntu update kills Chrome and Brave

Status in xorg package in Ubuntu:
  New

Bug description:
  The update installed this morning (May 25, 2023) disabled both Brave
  and Chrome. Firefox is OK. I have installed a newer Brave-beta and it
  works fine. The problem first appeared in Xorg, where no page could be
  rendered, including settings. I then rebooted into Wayland and Brave
  and Chrome can render pictures but not text. The Brave version is
  brave-browser/stable,now 1.51.118 amd64 [installed]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 25 11:26:48 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl/6.30.223.271+bdcom, 5.19.0-41-generic, x86_64: installed
   bcmwl/6.30.223.271+bdcom, 5.19.0-42-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7520G] 
[1002:9990] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity 2 [Radeon HD 7520G] [103c:1992]
  InstallationDate: Installed on 2022-06-15 (344 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 

[Touch-packages] [Bug 2058310] [NEW] Dummy output with Celeron Silver audio

2024-03-18 Thread Chris Hall
Public bug reported:

Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there
is no sound. I believe the CPU sound unit is essx-8336. Many people have
reported similar problems, with the system sound being "dummy output".
My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do
work with this machine, as does the Win 11 dual boot, so the hardware
works. Will this problem be fixed in version 24.04?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 21:29:33 2024
InstallationDate: Installed on 2024-03-11 (7 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2023
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GM118C_V33.1180.01
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 140.15
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992

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


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

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

Title:
  Dummy output with Celeron Silver audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Built in speakers have alsa driver as sof-audio-pci-intel-apl, but
  there is no sound. I believe the CPU sound unit is essx-8336. Many
  people have reported similar problems, with the system sound being
  "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora
  39 live images do work with this machine, as does the Win 11 dual
  boot, so the hardware works. Will this problem be fixed in version
  24.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 21:29:33 2024
  InstallationDate: Installed on 2024-03-11 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2023
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GM118C_V33.1180.01
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 140.15
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992

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


-- 
Mailing list: 

[Touch-packages] [Bug 2058435] [NEW] After recent update, pulseaudio crashes

2024-03-19 Thread Chris Hall
Public bug reported:

Intel ALC269VB Analog worked fine until today's update. Now all I get is
"dummy output" and after running ubuntu-bug, the diagnostic says that
pulseaudio has crashed. Reloading does not help.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 19 22:28:54 2024
InstallationDate: Installed on 2018-12-04 (1932 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2018
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A24
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

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

Title:
  After recent update, pulseaudio crashes

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Intel ALC269VB Analog worked fine until today's update. Now all I get
  is "dummy output" and after running ubuntu-bug, the diagnostic says
  that pulseaudio has crashed. Reloading does not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 19 22:28:54 2024
  InstallationDate: Installed on 2018-12-04 (1932 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A24
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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


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