[Desktop-packages] [Bug 2012757] Re: Incorrect total system memory

[Adrian Feliks]

Changing units helped. Thanks

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Incomplete => Invalid

** Information type changed from Public to Private

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

Title:
  Incorrect total system memory

Status in gnome-system-monitor package in Ubuntu:
  Invalid

Bug description:
  Gnome System Monitor has been incorrectly showing the amount of RAM
  for some time (months?). Based on the system logs, I was able to
  determine that Gnome System Monitor has not been updated recently. So
  where is the incorrect data coming from?

  Gnome System Monitor:
  RAM: 33.5 GB
  SWAP: 1.5 GB

  $ free
     totalusedfree  shared  buff/cache   
available
  Mem:3270654012241184 5677344 122342814788012
11034196
  Swap:1459904   0 1459904

  Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
  In addition, SWAP is shown separately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2012757/+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 2022107] Re: printing dubugging doesnt work!

[Adrian]

What is so difficult to read in the dump posted which clearly states
which description / version / release it is ..  and that cups isnt
available nor that the websites referred to fail.

Expected result .. PRINTS 
Actual result  DOESNT PRINT

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

Title:
  printing dubugging doesnt work!

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  1  cupsdisable OKI-C332-411ACB 
  cupsdisable: Operation failed: client-error-not-found

  2   wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  --2023-06-01 21:57:49--  
http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Resolving people.canonical.com (people.canonical.com)... 185.125.188.97
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug 
[following]
  --2023-06-01 21:57:49--  
https://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:443... connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2023-06-01 21:57:49 ERROR 403: Forbidden.

  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  sudo: aa-complain: command not found

  /usr/lib/cups/backend/snmp
  network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA 
CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI
 C332;CID:OK_N_B800;" ""

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  1 21:59:57 2023
  InstallationDate: Installed on 2023-04-25 (37 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: 
implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Novatech N150ZU
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic 
root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TNO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022107/+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 2012757] [NEW] Incorrect total system memory

[Adrian Feliks]

Public bug reported:

Gnome System Monitor has been incorrectly showing the amount of RAM for
some time (months?). Based on the system logs, I was able to determine
that Gnome System Monitor has not been updated recently. So where is the
incorrect data coming from?

Gnome System Monitor:
RAM: 33.5 GB
SWAP: 1.5 GB

$ free
   totalusedfree  shared  buff/cache   available
Mem:3270654012241184 5677344 12234281478801211034196
Swap:1459904   0 1459904

Everything indicates that Gnome System Monitor as RAM, gives the amount of RAM 
+ SWAP. Why? Before that, the indications were correct - 32 GB RAM.
In addition, SWAP is shown separately.

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Gnome System Monitor has been incorrectly showing the amount of RAM for
  some time (months?). Based on the system logs, I was able to determine
  that Gnome System Monitor has not been updated recently. So where is the
  incorrect data coming from?
  
  Gnome System Monitor:
  RAM: 33.5 GB
  SWAP: 1.5 GB
  
- 
  $ free
-totalusedfree  shared  buff/cache   
available
+    totalusedfree  shared  buff/cache   
available
  Mem:3270654012241184 5677344 122342814788012
11034196
  Swap:1459904   0 1459904
  
- Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why?
+ Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
  In addition, SWAP is shown separately.

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

Title:
  Incorrect total system memory

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Gnome System Monitor has been incorrectly showing the amount of RAM
  for some time (months?). Based on the system logs, I was able to
  determine that Gnome System Monitor has not been updated recently. So
  where is the incorrect data coming from?

  Gnome System Monitor:
  RAM: 33.5 GB
  SWAP: 1.5 GB

  $ free
     totalusedfree  shared  buff/cache   
available
  Mem:3270654012241184 5677344 122342814788012
11034196
  Swap:1459904   0 1459904

  Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
  In addition, SWAP is shown separately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2012757/+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 2000835] Re: After resuming work, only the external screen works.

[Adrian Feliks]

I am attaching the logs.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+attachment/5639364/+files/journal.txt

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

Title:
  After resuming work, only the external screen works.

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Work on two monitors - extended.
  After a certain period of time, the monitor automatically shuts down and 
locks the screen. Starting work turns on the external screen only. The built-in 
one is disabled. I can't see the window when entering the password. The only 
way is to switch to one monitor, then turn both back on. Sometimes the order of 
the displays is swapped (the main one becomes the external monitor)

  nvidia-driver-525 - current report
  nvidia-driver-525-open - not working

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  1 13:45:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-53-generic, x86_64: installed
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-56-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] CoffeeLake-H GT2 [UHD Graphics 630] 
[1025:133a]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1337]
  InstallationDate: Installed on 2020-04-05 (1000 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Acer Aspire A715-74G
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vg_ubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Pidgey_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.29
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd04/09/2020:br1.29:efr1.27:svnAcer:pnAspireA715-74G:pvrV1.29:rvnCFL:rnPidgey_CFS:rvrV1.29:cvnAcer:ct10:cvrV1.29:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-74G
  dmi.product.sku: 
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+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 1993866] Re: package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Adrian Tritschler]

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

Probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/tex-
common/+bug/1970918, which happened six months ago at my last ubuntu
upgrade

** This bug has been marked a duplicate of bug 1970918
   package tex-common 6.17 failed to install/upgrade: installed tex-common 
package post-installation script subprocess returned error exit status 1

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

Title:
  package tex-common 6.17 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Upgrade Ubuntu 22.04 to 22.10, same as 21.10 to 22.04, system seems to
  get all the way through but there's an error with tex and the error
  message implies that the entire system upgrade may have failed

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: tex-common 6.17
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 22 09:31:10 2022
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-09-25 (391 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: tex-common
  Title: package tex-common 6.17 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1993866/+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 1993866] [NEW] package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Adrian Tritschler]

Public bug reported:

Upgrade Ubuntu 22.04 to 22.10, same as 21.10 to 22.04, system seems to
get all the way through but there's an error with tex and the error
message implies that the entire system upgrade may have failed

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: tex-common 6.17
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Oct 22 09:31:10 2022
ErrorMessage: installed tex-common package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2021-09-25 (391 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: tex-common
Title: package tex-common 6.17 failed to install/upgrade: installed tex-common 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kinetic need-duplicate-check

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

Title:
  package tex-common 6.17 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Upgrade Ubuntu 22.04 to 22.10, same as 21.10 to 22.04, system seems to
  get all the way through but there's an error with tex and the error
  message implies that the entire system upgrade may have failed

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: tex-common 6.17
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 22 09:31:10 2022
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-09-25 (391 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: tex-common
  Title: package tex-common 6.17 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1993866/+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 1992854] [NEW] Update wpebackend-fdo to 1.6.1

[Adrian Perez de Castro]

Public bug reported:

Impact
--

This is a minor bugfix release of the 1.6.x series:

  https://wpewebkit.org/release/wpebackend-fdo-1.6.1.html

The version currently in 20.04 LTS is 1.6.0, which accidentally shipped with
a bug that made the symbols wpe_fdo_get_{major,minor,micro}_version hidden.

These were supposed to be public (which is fixed in 1.6.1) and can be used
by other components to check the installed version at runtime.

In particular WebKitGTK depends on wpebackend-fdo, and we expect future
security updates may use these functions. The WebKitGTK team has committed
to making it possible for 20.04 to get updates until April 2023, and this
update makes those possible. Users of WebKit-based browsers should be able
to browse the Web with an up-to-date WebKitGTK stack that receives security
updates :)


Test Plan
-

The following C program can be used to check that the bug is present before
the wpebackend-fdo update, and that the issue was fixed afterwards:

  /*
   * $CC -o wpefdoversion wpefdoversion.c $(pkg-config --cflags --libs 
wpebackend-fdo-1.0)
   *
   * This will:
   *   - Fail to link with wpebackend-fdo 1.6.0
   *   - Succeed with version 1.6.1
   */

  #include 
  #include 

  int main(int argc, char *argv[]) {
printf("wpebackend-fdo runtime version: %d.%d.%d\n",
   wpe_fdo_get_major_version(), wpe_fdo_get_minor_version(), 
wpe_fdo_get_micro_version());
return 0;
  }

Browsers which use WebKitGTK for rendering web content running in a Wayland 
session
use wpebackend-fdo. Loading e.g. 
https://people.igalia.com/aperez/poster-circle.html
in Epiphany (package epiphany-browser) should work the same before and after 
the update.


What Could Go Wrong
---

Given the little amount of changes between versions 1.6.0 and 1.6.1, the 
possibility
of breakage is minimal to none. Diff:

  https://github.com/Igalia/WPEBackend-fdo/compare/1.6.0...1.6.1

If there were unexpected build failures for the package, an alternative would 
be to
continue shipping version 1.6.0 with commit 
1dda80de5372e56cdc6f818a3fca493f7cc1f9d6
applied, which would solve the issue with the 
wpe_fdo_get_{major,minor,micro}_version
symbols without including the rest of the changes from 1.6.1:

  https://github.com/Igalia/WPEBackend-
fdo/commit/1dda80de5372e56cdc6f818a3fca493f7cc1f9d6

Finally, given that default installs of Ubuntu desktop do not include a 
WebKitGTK
based browser, users are likely to have another web browser available if things 
were
to go wrong.

** Affects: wpebackend-fdo (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Test program C source"
   
https://bugs.launchpad.net/bugs/1992854/+attachment/5623985/+files/wpefdoversion.c

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

Title:
  Update wpebackend-fdo to 1.6.1

Status in wpebackend-fdo package in Ubuntu:
  New

Bug description:
  Impact
  --

  This is a minor bugfix release of the 1.6.x series:

https://wpewebkit.org/release/wpebackend-fdo-1.6.1.html

  The version currently in 20.04 LTS is 1.6.0, which accidentally shipped with
  a bug that made the symbols wpe_fdo_get_{major,minor,micro}_version hidden.

  These were supposed to be public (which is fixed in 1.6.1) and can be used
  by other components to check the installed version at runtime.

  In particular WebKitGTK depends on wpebackend-fdo, and we expect future
  security updates may use these functions. The WebKitGTK team has committed
  to making it possible for 20.04 to get updates until April 2023, and this
  update makes those possible. Users of WebKit-based browsers should be able
  to browse the Web with an up-to-date WebKitGTK stack that receives security
  updates :)

  
  Test Plan
  -

  The following C program can be used to check that the bug is present before
  the wpebackend-fdo update, and that the issue was fixed afterwards:

/*
 * $CC -o wpefdoversion wpefdoversion.c $(pkg-config --cflags --libs 
wpebackend-fdo-1.0)
 *
 * This will:
 *   - Fail to link with wpebackend-fdo 1.6.0
 *   - Succeed with version 1.6.1
 */

#include 
#include 

int main(int argc, char *argv[]) {
  printf("wpebackend-fdo runtime version: %d.%d.%d\n",
 wpe_fdo_get_major_version(), wpe_fdo_get_minor_version(), 
wpe_fdo_get_micro_version());
  return 0;
}

  Browsers which use WebKitGTK for rendering web content running in a Wayland 
session
  use wpebackend-fdo. Loading e.g. 
https://people.igalia.com/aperez/poster-circle.html
  in Epiphany (package epiphany-browser) should work the same before and after 
the update.

  
  What Could Go Wrong
  ---

  Given the little amount of changes between versions 1.6.0 and 1.6.1, the 
possibility
  of breakage is minimal to none. Diff:

[Desktop-packages] [Bug 1970918] [NEW] package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Adrian Tritschler]

Public bug reported:

Performing Ubuntu upgrade from 21.10 to 22.04, tex-common upgrade fails
and "the upgrade is aborted and may have left your system in an unstable
state"

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: tex-common 6.17
ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset zunicode zavl icp zcommon znvpair 
nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Apr 29 20:23:58 2022
ErrorMessage: installed tex-common package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2021-09-25 (216 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: tex-common
Title: package tex-common 6.17 failed to install/upgrade: installed tex-common 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package tex-common 6.17 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Performing Ubuntu upgrade from 21.10 to 22.04, tex-common upgrade
  fails and "the upgrade is aborted and may have left your system in an
  unstable state"

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: tex-common 6.17
  ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset zunicode zavl icp zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 29 20:23:58 2022
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-09-25 (216 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: tex-common
  Title: package tex-common 6.17 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1970918/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

[Adrian Wilkins]

So you can minimize this window and then have working Unity. If you
close it, your session ends.

This window belongs to a process of

/usr/libexec/gnome-session-failed

** Attachment added: "jammy-error-moved-aside.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582021/+files/jammy-error-moved-aside.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/1969357

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

[Adrian Wilkins]

Confirm (in KVM machines) that Unity works fine from gdm3 under Impish,
but a fresh VM of Jammy doesn't work with either lightdm or gdm for me.

I get to see a quick glimpse of the Unity desktop, then this fullscreen
splash error shows up

"Oh no! Something has gone wrong.

A problem has occurred and the system can't recover. 
All extensions have been disabled as a precaution."

Since it refers to extensions, I presume this is a part of GNOME Shell.

However... if you use the keyboard shortcut to left-split the window
(ctrl-super-left) ... you can see the Unity desktop is running. (I first
tried ctrl-alt-t to summon a terminal above it but the window is always-
on-top, I saw it lose focus though.)




** Attachment added: "jammy-gnome-shell-error.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582020/+files/jammy-gnome-shell-error.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/1969357

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

[Adrian Wilkins]

Is this a `gnome-session` issue? The source sayeth (@ gnome-
session/main.c:422)

/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
 * older versions of GDM,  other display managers, and startx,
 * set a fallback value if we don't find it set.
 */

There doesn't seem to be any other location in the code that sets
`XDG_CURRENT_DESKTOP` and this code hasn't changed between the two
versions listed above.

Is this because of a change to `gdm` ? Does it work if you switch to
lightdm?

`gdm` sets this from the session definition, which is patched into
gnome-session by

debian/patches/ubuntu/ubuntu-sessions.patch

(the patch file has changed between revisions but mostly to remove a
community session)


gdm fetches this @ daemon/gdm-session.c:2612  get_session_desktop_names()

filename = g_strdup_printf ("%s.desktop", get_session_name (self));
g_debug ("GdmSession: getting desktop names for file '%s'", filename);
keyfile = load_key_file_for_file (self, filename, NULL, NULL);
if (keyfile != NULL) {
  gchar **names;

  names = g_key_file_get_string_list (keyfile, 
G_KEY_FILE_DESKTOP_GROUP,
  "DesktopNames", NULL, NULL);

Can't see any obvious changes in GDM between Impish and Jammy that would
cause this just from looking at the diffs though.

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

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

Status in gnome-session package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
  (it works fine in the live session). I then tried installing the 21.10
  gnome-session package on 22.04 and Unity7 then worked perfectly fine.
  Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
  "Unity:7;Unity:ubuntu" with the Jammy version, which is really
  unexpected and might be causing these issues.

  seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
  changed between the two packages, and I think this is a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1966418]

[Adrian Perez]

(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
> 
> iris
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
> 
> zink
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

Zink will use internally lower-level parts from the Iris driver to access
the hardware, so at least this indicates that the issue is *below* the
OpenGL/GLES implementation. Could be EGL or hardware access, I suppose.

> i965
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
> 
> WaylandCompositor requires eglBindWaylandDisplayWL,
> eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
> Nested Wayland compositor could not initialize EGL
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

When a driver that was set explicitly like this fails to load, Mesa falls
back to using software rendering. This means you ended up here using the
swrast/llvmpipe driver, most likely (you can load “webkit://gpu” in the
Minibrowser or Epiphany to check this). This means that WebKit is most
likely using the GLX/EGL/OpenGL/GLES APIs correctly and the issue lies
somewhere in the Intel driver.

But the version of Mesa I am using here is the same as you and it works.
My suspicion is that one of the following is happening:

 * Patches applied by Debian/Ubuntu on top of Mesa are breaking the Intel
   driver. Here I am using Arch Linux, which does not apply any patches.
 * The Intel driver is being miscompiled somehow by the compiler toolchain
   shipped by Ubuntu. In case it helps, here Arch stable has GCC 11.2.0 as
   the default system compiler, so that's what gets used to build packages.
 * The bug could be related to your particular GPU model (and the
   corresponding code inside Mesa for it).

I hope this helps :)

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1966418]

[Adrian Vovk]

I don't compile WebKit w/ X11 support so I can't tell you if running
epiphany w/ GDK_BACKEND=x11 helps anything

---

I do not see those EGL errors when I run epiphany on the host. However,
if I run the Epiphany flatpak with FLATPAK_GL_DRIVERS=host, I get

EGLDisplay Initialization failed: EGL_BAD_PARAMETER
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

but the webviews still show up (they're just sluggish). When running
with FLATPAK_GL_DRIVERS=host, the epiphany flatpak starts crashing when
opening about:gpu

---

Downgrading to Mesa 21.3.8 on the host does not solve the issue for me.
Not sure what's going on here, because Epiphany from Flathub (using Mesa
21.3.8, WebKitGTK 2.36.0) works perfectly fine in my environment

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1966418/+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 1966418]

[Adrian Vovk]

OK I found a way to fix it @ package time! I previously built webkitgtk
with -DENABLE_X11_TARGET=OFF. I tried building with
-DENABLE_X11_TARGET=ON (since this is the major difference between my
build and the gnome-build-meta build, aside from Mesa version), and now
it works properly

Seems like disabling the x11 backend also accidentally disables parts of
the Wayland backend somewhere

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1966418/+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 1965518] [NEW] [USB-Audio - USB Audio, recording] Recording problem

[Adrian Hareńczyk]

Public bug reported:

Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek
ALC4080 is not recording audio. What I did found out, that the bar which
indicates that something is recording is going up, when I play some
sound on ubuntu, so input "thinks" it is output I think.

If raport is somehow saying I was not using that mic at the moment, that
is because I was using other card which I need to buy, for mic to
temporarly work. I rechecked it before sending report, and yes, that
original from MBO audio input is still not working.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Unity
Date: Fri Mar 18 10:39:26 2022
InstallationDate: Installed on 2022-03-12 (5 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
Symptom_Card: USB Audio - USB Audio
Symptom_Type: None of the above
Title: [USB-Audio - USB Audio, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.10
dmi.board.asset.tag: Default string
dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D31
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug impish

** Attachment added: "sound_configuration_on_gui.png"
   
https://bugs.launchpad.net/bugs/1965518/+attachment/5570349/+files/sound_configuration_on_gui.png

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

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio
  Realtek ALC4080 is not recording audio. What I did found out, that the
  bar which indicates that something is recording is going up, when I
  play some sound on ubuntu, so input "thinks" it is output I think.

  If raport is somehow saying I was not using that mic at the moment,
  that is because I was using other card which I need to buy, for mic to
  temporarly work. I rechecked it before sending report, and yes, that
  original from MBO audio input is still not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Fri Mar 18 10:39:26 2022
  InstallationDate: Installed on 2022-03-12 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: USB Audio - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default 

[Desktop-packages] [Bug 1952217] [NEW] bluetoothd coredumps from double free on connection of headset

[Adrian Wilkins]

Public bug reported:

Problem:

Since the security updates on 2021-11-23 connecting my headset causes
bluetoothd to crash, which drops all the other connections.

Expected:

Headset connects and works as it has done previously.


❯ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04

❯ apt-cache policy bluez
bluez:
  Installed: 5.53-0ubuntu3.4
  Candidate: 5.53-0ubuntu3.4


Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for 
the LDAC codecs for this headset.

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

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

Title:
  bluetoothd coredumps from double free on connection of headset

Status in bluez package in Ubuntu:
  New

Bug description:
  Problem:

  Since the security updates on 2021-11-23 connecting my headset causes
  bluetoothd to crash, which drops all the other connections.

  Expected:

  Headset connects and works as it has done previously.

  
  ❯ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ❯ apt-cache policy bluez
  bluez:
Installed: 5.53-0ubuntu3.4
Candidate: 5.53-0ubuntu3.4

  
  Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for 
the LDAC codecs for this headset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1913940] Re: Wifi keeps disconnecting and reconnecting all the time

[Adrian]

Hi, any sign that this issue is being looked at?

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

Title:
  Wifi keeps disconnecting and reconnecting all the time

Status in wpa package in Ubuntu:
  New

Bug description:
  I have a problem with WIFI not being stable, and disconnecting ->
  reconnecting, all the time (I have PC next to the router). It happens
  like every 10 seconds average (one time it happened twice in a row,
  and another time I got 30 seconds without disconnect).

  Specs:
  OS: Ubuntu 20.04.1 LTS (On 20.10 same issue)
  Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k)
  Motherboard: MSI X470 Gaming Plus Max
  CPU: AMD Ryzen 5 3600
  wpasupplicant: 2:2.9-1ubuntu4.1

  I've tried so far: disabling IPV6, disabling powersave mode, creating
  ath9k.conf and adding parameters, setting manually BSSID and MAC
  adress, installing backport-iwlwifi-dkms, installing firmware-ath9k-
  htc, using 2,4G network.

  What I expect:
  Wifi network stable without single drop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 12:09:00 2021
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Adrian Wilkins]

Been running -460 for ages, my syslog occupies 80GB of disk space and
out of 526M log lines, 99.996% of them mention "Nautilus".

** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1913940] Re: Wifi keeps disconnecting and reconnecting all the time

[Adrian]

Hi, any news on fixing this issue? If not, do you have any workaround I
could try at least?

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

Title:
  Wifi keeps disconnecting and reconnecting all the time

Status in wpa package in Ubuntu:
  New

Bug description:
  I have a problem with WIFI not being stable, and disconnecting ->
  reconnecting, all the time (I have PC next to the router). It happens
  like every 10 seconds average (one time it happened twice in a row,
  and another time I got 30 seconds without disconnect).

  Specs:
  OS: Ubuntu 20.04.1 LTS (On 20.10 same issue)
  Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k)
  Motherboard: MSI X470 Gaming Plus Max
  CPU: AMD Ryzen 5 3600
  wpasupplicant: 2:2.9-1ubuntu4.1

  I've tried so far: disabling IPV6, disabling powersave mode, creating
  ath9k.conf and adding parameters, setting manually BSSID and MAC
  adress, installing backport-iwlwifi-dkms, installing firmware-ath9k-
  htc, using 2,4G network.

  What I expect:
  Wifi network stable without single drop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 12:09:00 2021
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

[Adrian Barbuio]

Okay, ever since I installed this bug fix, my mouse has been playing up.
First, dragging and dropping across windows exhibited errant behaviour,
such as dropping the dragging item in between box borders. Now, every
once in a while, my mouse's primary buttons switch. The original issue
has been resolved but this new issue is a little bit more problematic. I
am using Ubuntu 20.04 with @cristiano patch

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/focal/+source/mutter/+bug/1892440/+attachment/5415961/+files/specsaver.txt

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

[Adrian Barbuio]

@Marco thank you for your post regarding the test packages (comment
#50). This has almost solved the problem for me. I still get enlarged
text at the decryption password screen. Not a problem for me, but maybe
the information will help you guys.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892521] Re: Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2

[Adrian Barbuio]

I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behavior. I am
fairly certain this isn't an issue with my mouse and the issue emerged
just as this update occurred.

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

Title:
  Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  See also bug 1892440.

  I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after 
a RECENT UPDATE
  (which upgraded the following packages : gir1.2-mutter-6:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 
(7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 
(8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 
5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 
5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) -
  the fonts automatically scale up after every reboot and ruin the look of my 
desktop.I had never encountered this problem before.It can be fixed by manually 
scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I 
really would love to have this fixed.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-21 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+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 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

[Adrian Barbuio]

I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behaviour. I am
fairly certain this isn't an issue with my mouse and the issue emerged
just as this update occured.

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

Title:
  Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04

[Adrian Barbuio]

Thankyou Konrad, your comment #17, has solved this issue for me. I did
not hold the package at 6-0, though. Personal preference, but I feel
that accidentally updating and breaking it again is a simple fix, while
having a hold on a package that you have to remember to unhold could sit
in the background for ages.

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

Title:
  [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892521] Re: UI bug - system fonts enlarge after every reboot

[Adrian Barbuio]

Hello Akhil

Thankyou for this suggestion and the time you have put in. I tried this,
and a few other workarounds from a few other forums, and they have all
failed for me. The only solution has been to roll back the recently
updated 'libmutter' package, as per comment #17 in
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 using the
command:

sudo apt install libmutter-6-0=3.36.1-3ubuntu3
gir1.2-mutter-6=3.36.1-3ubuntu3

the post suggests to also hold the update using:

sudo apt-mark hold libmutter-6-0

I haven't needed to use this command, but I imagine any future update
will have to be checked for a solution if this isn't run. In any case,
this has provided a complete solution, with the login screen now also
back to normal.

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

Title:
  UI bug - system fonts enlarge after every reboot

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after 
a RECENT UPDATE
  (which upgraded the following packages : gir1.2-mutter-6:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 
(7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 
(8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 
5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 
5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) -
  the fonts automatically scale up after every reboot and ruin the look of my 
desktop.I had never encountered this problem before.It can be fixed by manually 
scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I 
really would love to have this fixed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-21 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+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 1892521] Re: UI bug - system fonts enlarge after every reboot

[Adrian Barbuio]

0.walbert - where did you place these commands? I'm a little new to this
and I have been having the same problem.

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

Title:
  UI bug - system fonts enlarge after every reboot

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after 
a RECENT UPDATE
  (which upgraded the following packages : gir1.2-mutter-6:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 
(7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 
(8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 
(2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 
5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 
5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), 
libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 
(3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) -
  the fonts automatically scale up after every reboot and ruin the look of my 
desktop.I had never encountered this problem before.It can be fixed by manually 
scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I 
really would love to have this fixed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-21 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+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 1892979] [NEW] Sizing issue on Startup

[Adrian Barbuio]

Public bug reported:

Hello, I recently put together a new PC and installed a fresh Ubuntu
20.04. Immediately I noticed that, on startup, there was a flashing
cursor and the decryption password screen was unusually large, but the
login screen and desktop GUI was fine, so I thought nothing of it. With
a recent update, the decryption password screen and the login screen are
now both sized improperly and the text on the GUI is abnormally sized. I
have included an image of the GUI with the bug apparent. If I toggle the
'large text' in universal access on then off, the problem resolves, but
this is a hassle and happens every startup. I did have issues with the
display driver for the GPU on installation and this may be a contributor
but I am not sure and I am also not sure where to begin in
troubleshooting this problem. Any help would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 26 14:15:32 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
 nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] 
[1462:8d92]
InstallationDate: Installed on 2020-07-28 (28 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard
 Bus 001 Device 003: ID :0538   USB OPTICAL MOUSE
 Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B365M D3H
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: Default string
dmi.board.name: B365M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B365M D3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal fonts ubuntu

** Attachment added: "Screenshot of GUI with enlarged text"
   
https://bugs.launchpad.net/bugs/1892979/+attachment/5404595/+files/Screenshot%20from%202020-08-25%2020-36-38.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Adrian Nida]

Hi,  Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
display issue.  I also have the same graphics card:

>From lspci:
03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] 
(rev a1)

Is there any workaround I can perform to make this desktop usable? Other
than blowing away the install and going back to 19.10?

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  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.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: 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 N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+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 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Adrian Jones]

This bug is still happening ..   it really does render this whole
package unworkable ..  its equivalent to the computer not working at
all.   At least that way you know your data isn't being corrupted.   I'm
appalled at the cavalier attitude this bug is being treated...other
end itus ...   I agree more and more it appears to be an OS issue yet it
appears when only using word .. as well as outside word.

Either way some heads need to get together and fix the bug. It used to
be when a critical bug like this was encountered then the part at fault
was removed.. the bug fixed offline and then tested back in. It seems
the modern approach is the old micorshaft approach of let the users test
and fix the bug. If its NOT this then the people here should be putting
pressure on those whose area it is ..reporting bugs is difficult
enough without constantly being shunted around saying its somewhere else
you report it ..  (only to find you have to install software to prove
the bug was happening .. er.. it was happening before I had to install
mutter).

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

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

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1879968/+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 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Adrian Jones]

Incidentally this bug has been happening and someone suggested updating
Mutter to the latest version.

I had to install mutter to then update it to try and fix it  ..   so now
there are bugs due to software that was never installed in the first
place !!!

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Adrian Jones]

This is still happening despite the Ubuntu 20.04LTS installation being
fully patched using Liveupdate as at 25 May 2020.

In LibreOffice I have to hit Cntrl C repeatedly (more than 2 times or
click the copy icon sometimes 9 times or more to get some data   and
this is just staying within Office so office related only.

In the desktop other attempts to copy also to other applications and WINE 
applications still results in failures. 
The fix therefore has not worked.   If mutter was changed and has rendered the 
computer useless (I regard it as such right now as it is highly unreliable and 
induces errors) then it should be removed until the module has been fixed and 
tested.  DO NOT get the users to fix the problem.. that is why users have been 
driven away from Microsoft.

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

uname -rs keeps returning the Linux 5.4.0-28-generic despite having
upgraded the kernel to either of the solutions you mentioned.. it says
it has upgraded successfully then after the reboot returns the same
variant.

This is the sort of problem I would have expected from a beta release
and most certainly not a LTS

I know this is done with volunteers but as a basic user I should not
have to be replacing kernels ...   I'm still not sure why I am trying to
replace a kernel when the Gnome variant is still not updating ..  are
they the one and the same? if they are why are they on different
variants? if they aren't then what I am doing tinkering with the kernel?

there is no clear place that outlines the relationships between the
various components .. its just assumed knowledge!

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

thank you for helping but that means nothing to me ...

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

I am running the latest Gnome 3.36.1 that I can upgrade to ..  the
3.36.2 doesn't appear to be released

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

sorry but how do I change the kernel?   revert back totally to 18.04 ??

20 seems highly unstable with the copy/paste failure as well ..

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 694407] Re: [ICH - SiS SI7012] Playback problem

[Adrian C Morgan]

This was an old problem many years ago, I am suprised that I got this 
notification now especially as I am now using 18.04LTS and 19.10.

On 05/03/2020 07:01, Marcus Tomlinson wrote:
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue on a maintained version of Ubuntu please let us
> know.
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: Confirmed => Incomplete
>

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

Title:
  [ICH - SiS SI7012] Playback problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No sound after initial opening of Diablo II when running under Wine
  Ubuntu 10.04 LTS
  Wine 1.2

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 1332 F pulseaudio
    adrian21093 F winecfg.exe
   /dev/snd/pcmC0D0p:   adrian 1332 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SI7012'/'SiS SI7012 with AD1888 at irq 18'
 Mixer name : 'Analog Devices AD1888'
 Components : 'AC97a:41445368'
 Controls  : 45
 Simple ctrls  : 31
  Date: Sat Dec 25 22:37:22 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 SI7012 ICH - SiS SI7012
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [ICH - SiS SI7012] Playback problem
  dmi.bios.date: 10/08/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 760GXK8MC
  dmi.board.vendor: WinFast
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/08/2005:svn:pn:pvr:rvnWinFast:rn760GXK8MC:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/694407/+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 993196] Re: [Dell E6420] Mic not working in Ubuntu 12.04

[Adrian Bunk]

** Description changed:

- The internal mic of my laptop is not working in Skype and doesn't show
- up under Input in the Sound settings.
+ The internal mic of my laptop is not working and doesn't show up under
+ Input in the Sound settings.
  
  Internal speakers are working fine.
  
  The microphone of a USB headset is working fine.

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

Title:
  [Dell E6420] Mic not working in Ubuntu 12.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  The internal mic of my laptop is not working and doesn't show up under
  Input in the Sound settings.

  Internal speakers are working fine.

  The microphone of a USB headset is working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/993196/+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 1843999] Re: Printing fails since last update

[Adrian Midgley]

I had previously installed Gimp-Gutenprint as the driver for the
printer, via the control panel, and in fact going via Gimp File Print
gets a print, with the Gutenprint options in the "ordinary" print
dialogue.  I'm not sure it is quite so good though, so far, and I don't
have the icc profile stuff.

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

Title:
  Printing fails since last update

Status in cups package in Ubuntu:
  New

Bug description:
  I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
  It fails each time, reporting filter failure.
  I forget what the last update was, yesterday or day before, but it is only 
since then.

  ESC/P utility can print a nozzle check from the printer, that's
  working.

  CUPS seems to be telling me that a filter failed, due to a mismatch
  between device colour model and profile.

  I've tried with no profile in the setup:printer dialogue, no
  different.

  Where should I look?
  Is it likely to be a change in the last update?

  
  I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


  W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
  org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
  path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
  has already been added
  E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
  E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
  E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
  errors; please consult the error_log file for details.
  D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
  recorded from 00:29:51 to 00:29:51
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
  queued by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
  "Stylus-Photo-R2400" by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
  D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
  D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
  application/vnd.cups-pdf, cost 66)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
  (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
  (application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
  D [14/Sep/2019:00:29:51 +0100] [Job 350]
  argv[3]="[8-channel-printer-a] (imported)"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
  StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
  ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
  StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
  StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
  StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
  StpColorCorrection=None StpLightMagentaScale=None
  Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
  StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
  StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
  StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
  StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
  StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
  StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
  StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
  StpFineYellowDensity=None StpFineHGray2Trans=None
  StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
  StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
  StpFineHGray4Scale=None StpFineYellowBalance=None
  StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBleed
  StpFineHGray1Trans=None StpYellowBalance=None MediaType=Plain
  StpLightCyanValue=None StpBlackGamma=None StpContrast=None
  StpInkSet=ultra3photo StpFineDropSize1=None StpFineDropSize2=None
  StpFineDropSize3=None StpColorPrecision=Best StpFineMagentaGamma=None
  StpFineHGray2Value=None StpFineHGray3Scale=None
  StpPrintingDirection=None StpLightCyanScale=None
  StpFineLightMagentaTrans=None StpFineBlackDensity=None number-up=1
  StpFineHGray2Scale=None StpSubchannelCutoff=None StpImageType=Photo
  

[Desktop-packages] [Bug 1843999] Re: Printing fails since last update

[Adrian Midgley]

Removed and recreated printer.  No change.
Removed plugins - not Gutenprint of coure - no change.

Starting gimp in a terminal with --verbose leads to

Initializing plug-in: 
'/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Starting extension: 'extension-script-fu'
INIT: gui_restore_after_callback
Parsing '/home/akm/.config/GIMP/2.10/menurc'
Parsing '/home/akm/.config/GIMP/2.10/action-history'
Parsing '/home/akm/.config/GIMP/2.10/devicerc'
Parsing '/home/akm/.config/GIMP/2.10/controllerrc'
loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /image-menubar
/usr/lib/gimp/2.0/plug-ins/gutenprint: fatal error: Segmentation fault

The last line is the one which appears after an effort to print.

I'm stuck so far.

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

Title:
  Printing fails since last update

Status in cups package in Ubuntu:
  New

Bug description:
  I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
  It fails each time, reporting filter failure.
  I forget what the last update was, yesterday or day before, but it is only 
since then.

  ESC/P utility can print a nozzle check from the printer, that's
  working.

  CUPS seems to be telling me that a filter failed, due to a mismatch
  between device colour model and profile.

  I've tried with no profile in the setup:printer dialogue, no
  different.

  Where should I look?
  Is it likely to be a change in the last update?

  
  I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


  W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
  org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
  path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
  has already been added
  E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
  E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
  E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
  errors; please consult the error_log file for details.
  D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
  recorded from 00:29:51 to 00:29:51
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
  queued by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
  "Stylus-Photo-R2400" by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
  D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
  D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
  application/vnd.cups-pdf, cost 66)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
  (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
  (application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
  D [14/Sep/2019:00:29:51 +0100] [Job 350]
  argv[3]="[8-channel-printer-a] (imported)"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
  StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
  ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
  StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
  StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
  StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
  StpColorCorrection=None StpLightMagentaScale=None
  Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
  StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
  StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
  StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
  StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
  StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
  StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
  StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
  StpFineYellowDensity=None StpFineHGray2Trans=None
  StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
  StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
  StpFineHGray4Scale=None StpFineYellowBalance=None
  StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBleed
  

[Desktop-packages] [Bug 1843999] [NEW] Printing fails since last update

[Adrian Midgley]

Public bug reported:

I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
It fails each time, reporting filter failure.
I forget what the last update was, yesterday or day before, but it is only 
since then.

ESC/P utility can print a nozzle check from the printer, that's working.

CUPS seems to be telling me that a filter failed, due to a mismatch
between device colour model and profile.

I've tried with no profile in the setup:printer dialogue, no different.

Where should I look?
Is it likely to be a change in the last update?


I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
has already been added
E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
errors; please consult the error_log file for details.
D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
recorded from 00:29:51 to 00:29:51
D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
queued by "akm".
D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
"Stylus-Photo-R2400" by "akm".
D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
application/vnd.cups-pdf, cost 66)
D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
(application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
(application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
D [14/Sep/2019:00:29:51 +0100] [Job 350]
argv[3]="[8-channel-printer-a] (imported)"
D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
StpColorCorrection=None StpLightMagentaScale=None
Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
StpFineYellowDensity=None StpFineHGray2Trans=None
StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
StpFineHGray4Scale=None StpFineYellowBalance=None
StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBleed
StpFineHGray1Trans=None StpYellowBalance=None MediaType=Plain
StpLightCyanValue=None StpBlackGamma=None StpContrast=None
StpInkSet=ultra3photo StpFineDropSize1=None StpFineDropSize2=None
StpFineDropSize3=None StpColorPrecision=Best StpFineMagentaGamma=None
StpFineHGray2Value=None StpFineHGray3Scale=None
StpPrintingDirection=None StpLightCyanScale=None
StpFineLightMagentaTrans=None StpFineBlackDensity=None number-up=1
StpFineHGray2Scale=None StpSubchannelCutoff=None StpImageType=Photo
StpFineHGray1Value=None StpInkType=PhotoCMYK8 StpDitherAlgorithm=None
StpYellowGamma=None StpFineGCRUpper=None StpFeedSequence=None
StpFineHGray1Scale=None PageSize=A4 StpHGray5Trans=None
noStpLinearContrast StpFineLightMagentaValue=None StpWeave=None
StpFineGCRLower=None InputSlot=Standard StpBlackTrans=None
StpHGray4Trans=None StpFineLightMagentaScale=None StpGCRUpper=None
StpFineDensity=None StpSaturation=None StpiShrinkOutput=Shrink
StpHGray5Value=None StpLightMagentaTrans=None StpDensity=None
StpFineMagentaDensity=None StpHGray3Trans=None StpCyanDensity=None
StpFineSaturation=None StpFineInkLimit=None StpFineYellowGamma=None
StpGCRLower=None StpHGray5Scale=None StpCyanGamma=None
StpHGray4Value=None 

[Desktop-packages] [Bug 1839010] Re: Touchpad does not work after installing Ubuntu

[Adrian Barbuio]

** Attachment added: "list_devices"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281528/+files/list_devices

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

Title:
  Touchpad does not work after installing Ubuntu

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

Bug description:
  I previously had Windows 10 on my protab laptop. After wiping the hard
  drive and installing Ubuntu 19.04 on the device, the touchpad ceases
  to respond at all. I am using an external mouse currently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 02:39:36 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-22 (164 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1839010] Re: Touchpad does not work after installing Ubuntu

[Adrian Barbuio]

Here are the logs:

** Attachment added: "journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281525/+files/journal

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

Title:
  Touchpad does not work after installing Ubuntu

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

Bug description:
  I previously had Windows 10 on my protab laptop. After wiping the hard
  drive and installing Ubuntu 19.04 on the device, the touchpad ceases
  to respond at all. I am using an external mouse currently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 02:39:36 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-22 (164 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1839010] [NEW] Touchpad does not work after installing Ubuntu

[Adrian Barbuio]

Public bug reported:

I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:39:36 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  Touchpad does not work after installing Ubuntu

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

Bug description:
  I previously had Windows 10 on my protab laptop. After wiping the hard
  drive and installing Ubuntu 19.04 on the device, the touchpad ceases
  to respond at all. I am using an external mouse currently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 02:39:36 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-22 (164 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1839006] [NEW] No sound is playing from this laptop

[Adrian Barbuio]

Public bug reported:

I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output menu
moving with the playback audio. I have tried force
restarting/reinstalling Alsa mixer and pulse audio and all the obvious
things such as checking sound level settings.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:09:12 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  No sound is playing from this laptop

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

Bug description:
  I recently installed Ubuntu 19.04 on this protab laptop. In the
  settings menu the sound output shows a headphone and a multichannel
  output option. There is no sound coming out of either system, despite
  there being sound detection demonstrated in the sound bars in the
  output menu moving with the playback audio. I have tried force
  restarting/reinstalling Alsa mixer and pulse audio and all the obvious
  things such as checking sound level settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 02:09:12 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-22 (164 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839006/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I finally posted on the pulseaudio list and someone referred me to this
bug:

https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640

I uninstalled timidity and that seems to have fixed the problem.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

So is the next step that I should post this to pulseaudio-
disc...@lists.freedesktop.org?  Do I need to be a list member to post
there?

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

On my ubuntu 18.04 system I only have

/usr/bin/pulseaudio --start --log-target=syslog

owned by me.  On my 19.04 system

/usr/bin/pulseaudio --daemonize=no

also owned by me.  Note gdm is not running.  I assume lightdm, which is
running, is the alternative.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I already posted the log file a.txt in its entirety.  Here it is again:

D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
E: [pulseaudio] main.c: Failed to acquire autospawn lock

I'm guessing that the failure of autospawn prevented anything else from
being logged.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I forgot to mention that dpkg -S says:

libpulse0:amd64, libpulse0:i386: /etc/pulse/client.conf.d/00-disable-
autospawn.conf

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I looked around a bit and found ~/.config/pulse, a directory with
permission 700.  Changed it to 777.  That didn't make a difference.
Also found ~/.pulse with this contents:

12 -rw-r--r-- 1 adrian adrian 12288 Oct  7  2013 
11597e2b32f1c4cb56501b9c0008-card-database.tdb
 4 -rw-r--r-- 1 adrian adrian43 Apr 19  2014 
11597e2b32f1c4cb56501b9c0008-default-sink
 4 -rw-r--r-- 1 adrian adrian42 Apr 19  2014 
11597e2b32f1c4cb56501b9c0008-default-source
16 -rw-r--r-- 1 adrian adrian 16384 Apr 19  2014 
11597e2b32f1c4cb56501b9c0008-device-volumes.tdb
 0 lrwxrwxrwx 1 adrian adrian23 Apr 19  2014 
11597e2b32f1c4cb56501b9c0008-runtime -> /tmp/pulse-8aAagnINg7zP
16 -rw-r--r-- 1 adrian adrian 16384 Apr 19  2014 
11597e2b32f1c4cb56501b9c0008-stream-volumes.tdb
 0 lrwxrwxrwx 1 adrian adrian23 Nov 27  2011 
38756220f384bf82c1d1020046a3eb64-runtime -> /tmp/pulse-PKdhtXMmr18n
 0 lrwxrwxrwx 1 adrian adrian23 Sep 21  2009 
38756220f384bf82c1d1020046a3eb64:runtime -> /tmp/pulse-2L9K88eMlGn7
36 -rw-r--r-- 1 adrian adrian 36864 May  9 21:01 
d2db290d8cab75358b4e4df65352b09e-card-database.tdb
 4 -rw-r--r-- 1 adrian adrian48 May 11 11:34 
d2db290d8cab75358b4e4df65352b09e-default-sink
 4 -rw-r--r-- 1 adrian adrian42 May 11 11:34 
d2db290d8cab75358b4e4df65352b09e-default-source
12 -rw-r--r-- 1 adrian adrian 12288 May  9 20:57 
d2db290d8cab75358b4e4df65352b09e-device-volumes.tdb
32 -rw-r--r-- 1 adrian adrian 32768 May  9 20:56 
d2db290d8cab75358b4e4df65352b09e-stream-volumes.tdb
36 -rw-r--r-- 1 adrian adrian 36864 Apr 19  2014 
dde22083dcde33e18c82670353529afd-card-database.tdb
 4 -rw-r--r-- 1 adrian adrian43 Apr 19  2014 
dde22083dcde33e18c82670353529afd-default-sink
 4 -rw-r--r-- 1 adrian adrian42 Apr 19  2014 
dde22083dcde33e18c82670353529afd-default-source
12 -rw-r--r-- 1 adrian adrian 12288 Apr 19  2014 
dde22083dcde33e18c82670353529afd-device-volumes.tdb
16 -rw-r--r-- 1 adrian adrian 16384 Apr 19  2014 
dde22083dcde33e18c82670353529afd-stream-volumes.tdb
 8 -rw-r--r-- 1 adrian adrian  5982 Mar 10  2012 default.pa
 8 -rw-r--r-- 1 adrian adrian  5920 Mar 10  2012 default.pa~

Some kinda old stuff in there.  Deleted (well, renamed) the directory.
No change in behavior.  Also it didn't get re-created, which seemed a
bit surprising since some of the files in there were new.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  H

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I removed the 00-disable-autospawn.conf file and rebooted.  Then I get
a.txt containing this:

D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
E: [pulseaudio] main.c: Failed to acquire autospawn lock

which seems not very enlightening.  I tried alsa force-reload and it
works as usual and nothing more appears in a.txt.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I believe that I upgraded incrementally as new releases came out from
14.04. (Hard to recall for sure back that far.)  But definitely I got to
18.10 from 18.04 to 18.04 from 17.10.  And 18.04, I didn't have this
problem.  In fact, I have a second machine that I'm "scared" to upgrade
that's still running 18.04 because I don't want to have this problem on
two machines.

So you don't think the existence of /etc/pulse/client.conf.d/00-disable-
autospawn.conf with the contents

autospawn=no

could explain the lack of the log file?  I notice that this file does
not exist on my other machine.

If I enable autospawn does something else need to change?

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I followed the instructions but no log file was created.

I noticed in the man page for pulse-client.conf it says

extra-arguments= Extra arguments to pass to the PulseAudio daemon  when
   autospawning. 

and in /etc/pulse/client.conf.d I see

autospan=no

I tried playing sound, running "alsa force-reload" and checking for the
log file but nothing seemed to cause that file to be created.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Adrian S.]

The issue persists on 19.04.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

The before file was attached to the last comment.  Here's the after file
from pactl.

** Attachment added: "postforce"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command.  Results was as you predicted.  The pactl outputs before
and after appear below.

Here's the before output:

Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner Module: 5
Properties:
alsa.card = "1"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:01:00.1"
sysfs.path = 
"/devices/pci:00/:00:01.0/:01:00.1/sound/card1"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "0fbc"
device.string = "1"
device.description = "HDA NVidia"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, 
sources: 0, priority: 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(sinks: 1, sources: 0, priority: 5700, available: yes)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(sinks: 1, sources: 0, priority: 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: off
Ports:
hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "video-display"
Part of profile(s): output:hdmi-stereo, 
output:hdmi-surround, output:hdmi-surround71
hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency 
offset: 0 usec, available)
Properties:
device.icon_name = "video-display"
device.product.name = "DELL U2715H
 "
Part of profile(s): output:hdmi-stereo-extra1
hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "video-display"
Part of profile(s): output:hdmi-stereo-extra2, 
output:hdmi-surround-extra2, output:hdmi-surround71-extra2


---

Here is the after output:

Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner Module: 5
Properties:
alsa.card = "1"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:01:00.1"
sysfs.path = 
"/devices/pci:00/:00:01.0/:01:00.1/sound/card1"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "0fbc"
device.string = "1"
device.description = "HDA NVidia"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, 
sources: 0, priority: 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(sinks: 1, sources: 0, priority: 5700, available: yes)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(sinks: 1, sources: 0, priority: 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
off: 

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I rebooted and went into the "Ubuntu" desktop and looked at the sound
settings.  It shows an output tab and said "dummy".  I clicked and was
able to switch it to the nvidia card.  I think maybe the nvidia card was
off, which it should be since there's no output device connected.

I went back into my regular environment and observed that the nvidia
output was available but not the built-in sound.  I ran aplay test.wav
and could see in pavucontrol that sound output was going to the nvidia
output.  (It shows a real-time output level bar.)

I ran alsa force-reload.  When I do this the message "Terminating
processes: " appears and instantly at that point, the built in
sound appears in pavucontrol on the configuration tab.  For some reason
though, in this case, even after I selected it, I still got no sound.  I
rebooted again, went straight into my normal environment, confirmed that
only the nvidia card was available, ran 'alsa force-reload', the built-
in sound appears instantly as described above, then there is a many
second delay while alsa loads and messages about loading of sound driver
modules appears.  And then I can play sound, e.g. with aplay.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

If I look at the sound settings using pavucontrol (I don't normally use
gnome and don't seem to have a program called gnome-sound-setting
installed) then under the configuration tab I see the nvidia hardware
but not the built in audio.  (The nvidia card has only HDMI and my
speakers don't have that input, so I can't try using that.  I don't have
any devices with HDMI input.)

After running 'alsa force-reload' the built-in audio appears as a
configuration option.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

Summary: looks to me like aplay -l is showing the intel hardware.  No

adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x   3 root root  320 May  9 18:07 ./
0 drwxr-xr-x  20 root root 5080 May  9 18:07 ../
0 drwxr-xr-x   2 root root   80 May  9 18:07 by-path/
0 crw-rw+  1 root audio 116,  7 May  9 18:07 controlC0
0 crw-rw+  1 root audio 116, 12 May  9 18:07 controlC1
0 crw-rw+  1 root audio 116,  6 May  9 18:07 hwC0D0
0 crw-rw+  1 root audio 116, 11 May  9 18:07 hwC1D0
0 crw-rw+  1 root audio 116,  3 May  9 18:07 pcmC0D0c
0 crw-rw+  1 root audio 116,  2 May  9 18:07 pcmC0D0p
0 crw-rw+  1 root audio 116,  4 May  9 18:07 pcmC0D1p
0 crw-rw+  1 root audio 116,  5 May  9 18:07 pcmC0D2c
0 crw-rw+  1 root audio 116,  8 May  9 18:13 pcmC1D3p
0 crw-rw+  1 root audio 116,  9 May  9 18:13 pcmC1D7p
0 crw-rw+  1 root audio 116, 10 May  9 18:13 pcmC1D8p
0 crw-rw+  1 root audio 116,  1 May  9 18:07 seq
0 crw-rw+  1 root audio 116, 33 May  9 18:07 timer
adrian> aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
adrian> sudo chmod a+rw /dev/snd/*
[sudo] password for adrian: 
adrian> aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x   3 root root  320 May  9 18:07 ./
0 drwxr-xr-x  20 root root 5080 May  9 18:07 ../
0 drwxrwxrwx   2 root root   80 May  9 18:07 by-path/
0 crw-rw-rw-+  1 root audio 116,  7 May  9 18:07 controlC0
0 crw-rw-rw-+  1 root audio 116, 12 May  9 18:07 controlC1
0 crw-rw-rw-+  1 root audio 116,  6 May  9 18:07 hwC0D0
0 crw-rw-rw-+  1 root audio 116, 11 May  9 18:07 hwC1D0
0 crw-rw-rw-+  1 root audio 116,  3 May  9 18:15 pcmC0D0c
0 crw-rw-rw-+  1 root audio 116,  2 May  9 18:15 pcmC0D0p
0 crw-rw-rw-+  1 root audio 116,  4 May  9 18:15 pcmC0D1p
0 crw-rw-rw-+  1 root audio 116,  5 May  9 18:07 pcmC0D2c
0 crw-rw-rw-+  1 root audio 116,  8 May  9 18:15 pcmC1D3p
0 crw-rw-rw-+  1 root audio 116,  9 May  9 18:15 pcmC1D7p
0 crw-rw-rw-+  1 root audio 116, 10 May  9 18:15 pcmC1D8p
0 crw-rw+  1 root audio 116,  1 May  9 18:15 seq
0 crw-rw-rw-+  1 root audio 116, 33 May  9 18:07 timer

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Fail

[Desktop-packages] [Bug 1828136] ProcCpuinfo.txt

[Adrian Mariano]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262477/+files/ProcCpuinfo.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] CRDA.txt

[Adrian Mariano]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1828136/+attachment/5262473/+files/CRDA.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcModules.txt

[Adrian Mariano]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262480/+files/ProcModules.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] UdevDb.txt

[Adrian Mariano]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1828136/+attachment/5262481/+files/UdevDb.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcCpuinfoMinimal.txt

[Adrian Mariano]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262478/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I ran the "apport-collect 1828136" command as directed by the automated
script.  A little puzzled that it gave the message

dpkg-query: no packages found matching alsa-driver
dpkg-query: no packages found matching linux

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Lspci.txt

[Adrian Mariano]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1828136/+attachment/5262475/+files/Lspci.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcInterrupts.txt

[Adrian Mariano]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262479/+files/ProcInterrupts.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Lsusb.txt

[Adrian Mariano]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1828136/+attachment/5262476/+files/Lsusb.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

The automated script said I should change the status to "confirmed" even
though I am the reporter.

When 18.10 came out some other people reported similar issues:

https://ubuntuforums.org/showthread.php?t=2403077

https://ubuntuforums.org/showthread.php?t=2405764

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] WifiSyslog.txt

[Adrian Mariano]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262482/+files/WifiSyslog.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] AudioDevicesInUse.txt

[Adrian Mariano]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262472/+files/AudioDevicesInUse.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] CurrentDmesg.txt

[Adrian Mariano]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262474/+files/CurrentDmesg.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

apport information

** Tags added: apport-collected

** Description changed:

  After rebooting I have no sound.  My sound device doesn't show up at all
  in the mixer.
  
  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.
  
  This problem started in 18.10 and persists now in 19.04.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ DistroRelease: Ubuntu 19.04
+ HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
+ InstallationDate: Installed on 2014-04-19 (1845 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ IwConfig:
+  lono wireless extensions.
+  
+  eth0  no wireless extensions.
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/tcsh
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
+ RfKill:
+  
+ Tags:  disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 12/04/2012
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: DH67CL
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: AAG10212-203
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1828136/+attachment/5262471/+files/AlsaInfo.txt

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I repeat, immediately after a reboot, audacity is not running.  Are you
saying that audacity can prevent the system from recognizing my sound
hardware at boot just from being installed?

At the moment, sound works despite the audacity's configuration because
I ran "alsa force-reload'.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I'm a little confused here.  What does audacity have to do with the fact
that there is no sound after a reboot?  Audacity happens to be running
now...perhaps that's why it's the only program using ALSA.  (Is ALSA
deprecated?)  But audacity does not start automatically at boot, so it
is irrelevant to the problem, which is that the sound device is not even
recognized until "alsa force-reload".

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] [NEW] [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

Public bug reported:

After rebooting I have no sound.  My sound device doesn't show up at all
in the mixer.

Running "sudo alsa force-reload" corrects the problem, until the next
reboot.

This problem started in 18.10 and persists now in 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Tue May  7 21:50:22 2019
InstallationDate: Installed on 2014-04-19 (1844 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
Symptom_Jack: Grey SPDIF Out, Rear
Symptom_Type: No sound at all
Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10212-203
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug disco

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

Title:
  [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1823052] [NEW] After a screen lock, the desktop wallpaper turns to pixel garbage

[Adrian]

Public bug reported:

As mentioned, after a lock-wake cycle, the wallpaper turns to pixel
garbage as seen on the screenshot.

Workaround: Setting the wallpaper from GNOME Tweaks, just not in the
same adjustment mode as before. For example, if the adjustment was set
to Zoom, now I must set it to something else to repair it. Setting it to
Zoom again turns it once more into pixel garbage.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  3 19:22:13 2019
DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2018-12-31 (93 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0670 Acer, Inc 
 Bus 001 Device 002: ID 17ef:60b2 Lenovo 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-03-29 (4 days ago)
XorgConf:
 Section "Extensions"
 Option "XVideo" "Disable"
 EndSection
dmi.bios.date: 02/15/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN58WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption disco possible-manual-nvidia-install ubuntu

** Attachment added: "Screenshot from 2019-04-03 19-23-35.png"
   
https://bugs.launchpad.net/bugs/1823052/+attachment/5252546/+files/Screenshot%20from%202019-04-03%2019-23-35.png

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

Title:
  After a screen lock, the desktop wallpaper turns to pixel garbage

Status in xorg package in Ubuntu:
  New

Bug description:
  As mentioned, after a lock-wake cycle, the wallpaper turns to pixel
  garbage as seen on the screenshot.

  Workaround: Setting the wallpaper from GNOME Tweaks, just not in the
  same adjustment mode as before. For example, if the adjustment was set
  to Zoom, now I must set it to something else to repair it. Setting it
  to Zoom again turns it once more into pixel garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 

[Desktop-packages] [Bug 1822665] [NEW] Brightness can't be changed from keyboard

[Adrian]

Public bug reported:

Brightness level can't be changed from keyboard with the Fn key and the
corresponding designated key. Other functions like changing volumes
involving the Fn key work perfectly. The only way I can change
brightness is from the status bar.

Current OS: Ubuntu 19.04 Disco Dingo (development branch)
Package version: gnome-shell 3.32.0-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 20:46:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  Brightness can't be changed from keyboard

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Brightness level can't be changed from keyboard with the Fn key and
  the corresponding designated key. Other functions like changing
  volumes involving the Fn key work perfectly. The only way I can change
  brightness is from the status bar.

  Current OS: Ubuntu 19.04 Disco Dingo (development branch)
  Package version: gnome-shell 3.32.0-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:46:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822665/+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 1822639] [NEW] Login screen doesn't react to key pressings prior to entering the password

[Adrian]

Public bug reported:

Before the screen when you enter the password, where the clock is shown,
if a key is pressed, it does not retract the screen upwards, as it used
to. Now I have to manually use my mouse to drag the screen up. Not sure
if it is the way it was intended to be used, but I am submitting a bug
report to be sure.

I apologise if this is a bug with GNOME, but please do tell me so I can
send a bug report to them.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 18:23:16 2019
DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0670 Acer, Inc 
 Bus 001 Device 002: ID 17ef:60b2 Lenovo 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
XorgConf:
 Section "Extensions"
 Option "XVideo" "Disable"
 EndSection
dmi.bios.date: 02/15/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN58WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco possible-manual-nvidia-install ubuntu

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

Title:
  Login screen doesn't react to key pressings prior to entering the
  password

Status in xorg package in Ubuntu:
  New

Bug description:
  Before the screen when you enter the password, where the clock is
  shown, if a key is pressed, it does not retract the screen upwards, as
  it used to. Now I have to manually use my mouse to drag the screen up.
  Not sure if it is the way it was intended to be used, but I am
  submitting a bug report to be sure.

  I apologise if this is a bug with GNOME, but please do tell me so I
  can send a bug report to them.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  

[Desktop-packages] [Bug 1822500] [NEW] Screen corruption shown while in login screen

[Adrian]

Public bug reported:

In place of the login background I chose, I either see a white scree, or
what appears to be random pixels, with the normal clock on top.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 31 22:32:53 2019
DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2018-12-31 (90 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0670 Acer, Inc 
 Bus 001 Device 002: ID 17ef:60b2 Lenovo 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
XorgConf:
 Section "Extensions"
 Option "XVideo" "Disable"
 EndSection
dmi.bios.date: 02/15/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN58WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption disco possible-manual-nvidia-install ubuntu

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

Title:
  Screen corruption shown while in login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  In place of the login background I chose, I either see a white scree,
  or what appears to be random pixels, with the normal clock on top.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 22:32:53 2019
  

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Adrian S.]

After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from 
ppa:graphics-drivers.
Using 4.18.0-16-generic kernel.

I find that when I use Intel profile, powertop reports the nvidia card as 0% 
active, and the setting in Tunables shows up as Good.
However, /proc/acpi/bbswitch reports as :01:00.0 ON, and the *fans* are 
spinning.

Turning the graphics card OFF with bbswitch, the fans stop spinning.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Adrian S.]

> * If I understand correctly, the bug does not occur in Ubuntu 18.10.
The user can switch seamlessly between using the Intel or the Nvidia
discrete graphics card. Is this correct?

@jespestana
No, this bug is affecting me on 18.10.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Adrian]

I am facing the same issue in Ubuntu 18.10. The super key randomly stops
working and I loose control of all windows except for the active window,
which in some cases also stops working and cannot even do clicks there.
The workaround I found is to close all windows, lock the screen and the
problem solves for 5-10 min or so. But this is clearly impractical and I
can't really go on like this any further. I re-installed the OS but it
didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
found a solution to this yet? I'd appreciate it very much!

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/1181666/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Adrian S.]

I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and 
then using nvidia-settings or prime-select to set intel keeps the nvidia card 
on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch 
works.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1808757] [NEW] [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[Adrian Cosma]

Public bug reported:

No sound from headphones from ubuntu desktop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cosmadrian   1251 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 17 10:35:18 2018
InstallationDate: Installed on 2018-08-08 (131 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 924 F pulseaudio
  cosmadrian   1251 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.10
dmi.board.asset.tag: Default string
dmi.board.name: B360M PRO-VD (MS-7B53)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd02/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360MPRO-VD(MS-7B53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B53
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound from headphones from ubuntu desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cosmadrian   1251 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 10:35:18 2018
  InstallationDate: Installed on 2018-08-08 (131 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 924 F pulseaudio
cosmadrian   1251 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M PRO-VD (MS-7B53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd02/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360MPRO-VD(MS-7B53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B53
  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/1808757/+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 901622] Re: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) )

[Adrian Fonseca]

I have the same problem. I have /home in a separated filesystem, and
every time a wakeup my lap this ext4 partition is mounted as ro.

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

Title:
  Resume after pm-suspend with read-only ext4 root file system on USB
  disk (ext4 journal commit I/O error) )

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to Oneiric resume from pm-suspend no longer works, might be 
connected to change of kernel from 2.6.38 to 3.0.0... Issue also reported for 
Arch Linux and kernel 2.6.39 here: 
https://bbs.archlinux.org/viewtopic.php?pid=1008743
  See attached dmesg output for details

  This is for kernel 3.0.0-14-server x86_64 (but also occured on 3.0.0-13) and 
a NAS booting from a USB stick.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  Package: pm-utils 1.4.1-8ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (51 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd 
lpadmin netdev plugdev powerdev sambashare scanner tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/901622/+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 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

So I became somewhat frustrated by this issue and used new installation
media to completely reinstall ubuntu 18.04, removing the old partition and
starting again from scratch. I installed steam as soon as the
re-installation process had been completed, and downloaded/played Kerbal
Space Program. I had exactly the same problem as before, the screen cutting
out minutes into the game.


On Wed, 24 Oct 2018 at 13:40, Daniel van Vugt 
wrote:

> Thanks. Unfortunately you probably can't report crash files that were
> created before the system update. Only crash files from a fully-updated
> system are accepted.
>
> So please delete the existing crash files and wait for new ones to be
> created.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798739
>
> Title:
>   [amdgpu] All video games freeze 5-10mins into play
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I recently installed steam on my system (Ubuntu 18.04), installed a
>   couple of games and attemped to play them. About a couple of minutes
>   in to playing cities: skylines, kerbal space program and mount and
>   blade: warband, the screen goes blank and the computer freezes. A hard
>   reboot is the only way to proceed. I have reinstalled drivers several
>   times, with no change in this situation. I know it's not a specs
>   problem because I ran these games on the exact same machine a couple
>   of weeks ago when I had Windows 10 installed (which I have since
>   removed). I think this is an xorg problem but I am not sure.
>
>   xorg:
> Installed: 1:7.7+19ubuntu7.1
> Candidate: 1:7.7+19ubuntu7.1
> Version table:
>*** 1:7.7+19ubuntu7.1 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:7.7+19ubuntu7 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
>   Uname: Linux 4.15.0-36-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Oct 19 14:02:58 2018
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a day
>   GpuHangReproducibility: Yes, I can easily reproduce it
>   GpuHangStarted: Within the last week or two
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7
> 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller])
>  Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM]
> [1b0a:90c4]
>   InstallationDate: Installed on 2018-09-11 (37 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: Hewlett-Packard 500-002a
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_AU.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
> root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/05/2013
>   dmi.bios.vendor: AMI
>   dmi.bios.version: 8.15
>   dmi.board.name: 2ADA
>   dmi.board.vendor: Foxconn
>   dmi.board.version: 1.00
>   dmi.chassis.asset.tag: 4CE3190T0P
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
>   dmi.product.family: 103C_53316J G=D
>   dmi.product.name: 500-002a
>   dmi.sys.vendor: Hewlett-Packard
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
>   version.libgl1-mesa-dri: libgl1-mesa-dri
> 18.3~git1810170730.58a51d~oibaf~b
>   version.libgl1-mesa-glx: libgl1-mesa-glx
> 18.3~git1810170730.58a51d~oibaf~b
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:18.1.0+git1809261933.80514b~oibaf~b
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git1809061934.25c9a2~oibaf~b
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.15+git1807201019.ac8f7b~oibaf~b
>
> To manage notifications about 

Re: [Desktop-packages] [Bug 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

Just to add, this is the screenshot I took of another attempt. The upgrade
commands are there just to show what I see when I run those commands. They
were run previous to a reboot, then I ran them again to make the screenshot.

Regards, Adrian

On Tue, 23 Oct 2018 at 21:15, Adrian Barbuio 
wrote:

> Okay, so I have run the update and reboot commands. I tried to run the
> ubuntu-bug command again and I got exactly the same error message as was in
> the previous screenshot.
>
> On Tue, 23 Oct 2018 at 20:46, Daniel van Vugt <
> daniel.van.v...@canonical.com> wrote:
>
>> That screenshot shows that you can't report crash files because your
>> system is out of date. To fix that please do a full system update first:
>>
>>   1. sudo apt update
>>   2. sudo apt full-upgrade
>>   3. Reboot
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1798739
>>
>> Title:
>>   [amdgpu] All video games freeze 5-10mins into play
>>
>> Status in xorg-server package in Ubuntu:
>>   Incomplete
>> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   I recently installed steam on my system (Ubuntu 18.04), installed a
>>   couple of games and attemped to play them. About a couple of minutes
>>   in to playing cities: skylines, kerbal space program and mount and
>>   blade: warband, the screen goes blank and the computer freezes. A hard
>>   reboot is the only way to proceed. I have reinstalled drivers several
>>   times, with no change in this situation. I know it's not a specs
>>   problem because I ran these games on the exact same machine a couple
>>   of weeks ago when I had Windows 10 installed (which I have since
>>   removed). I think this is an xorg problem but I am not sure.
>>
>>   xorg:
>> Installed: 1:7.7+19ubuntu7.1
>> Candidate: 1:7.7+19ubuntu7.1
>> Version table:
>>*** 1:7.7+19ubuntu7.1 500
>>   500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main
>> amd64 Packages
>>   100 /var/lib/dpkg/status
>>1:7.7+19ubuntu7 500
>>   500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64
>> Packages
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: xorg 1:7.7+19ubuntu7.1
>>   ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
>>   Uname: Linux 4.15.0-36-generic x86_64
>>   ApportVersion: 2.20.9-0ubuntu7.4
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CompizPlugins: No value set for
>> `/apps/compiz-1/general/screen0/options/active_plugins'
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Fri Oct 19 14:02:58 2018
>>   DistUpgraded: Fresh install
>>   DistroCodename: bionic
>>   DistroVariant: ubuntu
>>   DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
>>   ExtraDebuggingInterest: Yes
>>   GpuHangFrequency: Several times a day
>>   GpuHangReproducibility: Yes, I can easily reproduce it
>>   GpuHangStarted: Within the last week or two
>>   GraphicsCard:
>>Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7
>> 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller])
>>  Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM]
>> [1b0a:90c4]
>>   InstallationDate: Installed on 2018-09-11 (37 days ago)
>>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
>> (20180426)
>>   MachineType: Hewlett-Packard 500-002a
>>   ProcEnviron:
>>TERM=xterm-256color
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>LANG=en_AU.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
>> root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
>>   SourcePackage: xorg
>>   Symptom: display
>>   Title: Xorg freeze
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 02/05/2013
>>   dmi.bios.vendor: AMI
>>   dmi.bios.version: 8.15
>>   dmi.board.name: 2ADA
>>   dmi.board.vendor: Foxconn
>>   dmi.board.version: 1.00
>>   dmi.chassis.asset.tag: 4CE3190T0P
>>   dmi.chassis.type: 3
>>   dmi.chassis.vendor: Hewlett-Packard
>>   dmi.modalias:
>> dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
>>   dmi.product.family: 103C_53316J G

Re: [Desktop-packages] [Bug 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

Okay, so I have run the update and reboot commands. I tried to run the
ubuntu-bug command again and I got exactly the same error message as was in
the previous screenshot.

On Tue, 23 Oct 2018 at 20:46, Daniel van Vugt 
wrote:

> That screenshot shows that you can't report crash files because your
> system is out of date. To fix that please do a full system update first:
>
>   1. sudo apt update
>   2. sudo apt full-upgrade
>   3. Reboot
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798739
>
> Title:
>   [amdgpu] All video games freeze 5-10mins into play
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I recently installed steam on my system (Ubuntu 18.04), installed a
>   couple of games and attemped to play them. About a couple of minutes
>   in to playing cities: skylines, kerbal space program and mount and
>   blade: warband, the screen goes blank and the computer freezes. A hard
>   reboot is the only way to proceed. I have reinstalled drivers several
>   times, with no change in this situation. I know it's not a specs
>   problem because I ran these games on the exact same machine a couple
>   of weeks ago when I had Windows 10 installed (which I have since
>   removed). I think this is an xorg problem but I am not sure.
>
>   xorg:
> Installed: 1:7.7+19ubuntu7.1
> Candidate: 1:7.7+19ubuntu7.1
> Version table:
>*** 1:7.7+19ubuntu7.1 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:7.7+19ubuntu7 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
>   Uname: Linux 4.15.0-36-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Oct 19 14:02:58 2018
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a day
>   GpuHangReproducibility: Yes, I can easily reproduce it
>   GpuHangStarted: Within the last week or two
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7
> 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller])
>  Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM]
> [1b0a:90c4]
>   InstallationDate: Installed on 2018-09-11 (37 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: Hewlett-Packard 500-002a
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_AU.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
> root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/05/2013
>   dmi.bios.vendor: AMI
>   dmi.bios.version: 8.15
>   dmi.board.name: 2ADA
>   dmi.board.vendor: Foxconn
>   dmi.board.version: 1.00
>   dmi.chassis.asset.tag: 4CE3190T0P
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
>   dmi.product.family: 103C_53316J G=D
>   dmi.product.name: 500-002a
>   dmi.sys.vendor: Hewlett-Packard
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
>   version.libgl1-mesa-dri: libgl1-mesa-dri
> 18.3~git1810170730.58a51d~oibaf~b
>   version.libgl1-mesa-glx: libgl1-mesa-glx
> 18.3~git1810170730.58a51d~oibaf~b
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:18.1.0+git1809261933.80514b~oibaf~b
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git1809061934.25c9a2~oibaf~b
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.15+git1807201019.ac8f7b~oibaf~b
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1798739/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.

Re: [Desktop-packages] [Bug 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

Hello Daniel

I attempted all three steps and I came across the message in the
screenshot. When I click send there is no further message. I am not sure
how to find an id number. Also, I checked the gnome-shell file and there
was no file labelled 'extensions'. I assume this is because I have no
extensions installed?

Regards, Adrian

On Tue, 23 Oct 2018 at 19:11, Daniel van Vugt 
wrote:

> Thanks. It looks like something is crashing at the end (where you see
> "whoopsie") but I can't yet tell what.
>
> Firstly, please remove/disable all gnome-shell extensions as they are
> often the cause of crashes.
>
> Secondly...
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798739
>
> Title:
>   [amdgpu] All video games freeze 5-10mins into play
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I recently installed steam on my system (Ubuntu 18.04), installed a
>   couple of games and attemped to play them. About a couple of minutes
>   in to playing cities: skylines, kerbal space program and mount and
>   blade: warband, the screen goes blank and the computer freezes. A hard
>   reboot is the only way to proceed. I have reinstalled drivers several
>   times, with no change in this situation. I know it's not a specs
>   problem because I ran these games on the exact same machine a couple
>   of weeks ago when I had Windows 10 installed (which I have since
>   removed). I think this is an xorg problem but I am not sure.
>
>   xorg:
> Installed: 1:7.7+19ubuntu7.1
> Candidate: 1:7.7+19ubuntu7.1
> Version table:
>*** 1:7.7+19ubuntu7.1 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:7.7+19ubuntu7 500
>   500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
>   Uname: Linux 4.15.0-36-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Oct 19 14:02:58 2018
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a day
>   GpuHangReproducibility: Yes, I can easily reproduce it
>   GpuHangStarted: Within the last week or two
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7
> 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller])
>  Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM]
> [1b0a:90c4]
>   InstallationDate: Installed on 2018-09-11 (37 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: Hewlett-Packard 500-002a
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_AU.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
> root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/05/2013
>   dmi.bios.vendor: AMI
>   dmi.bios.version: 8.15

Re: [Desktop-packages] [Bug 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

Hello Daniel. I have performed the tasks you requested and have the 
relevant text file attached.

Regards, Adrian

On 23/10/18 4:43 pm, Daniel van Vugt wrote:
> Please:
>
> 1. Reboot and run nothing other than one game that will trigger the bug.
> Do not run any other apps.
>
> 2. After the bug happens and you have to reboot a second time then run:
>
>journalctl --system -b-1 > previous_boot_sys.txt
>
> and attach it here again.
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
> Status: New => Incomplete
>


** Attachment added: "previous_boot_sys.txt"
   
https://bugs.launchpad.net/bugs/1798739/+attachment/5204391/+files/previous_boot_sys.txt

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

Title:
  [amdgpu] All video games freeze 5-10mins into play

Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I recently installed steam on my system (Ubuntu 18.04), installed a
  couple of games and attemped to play them. About a couple of minutes
  in to playing cities: skylines, kerbal space program and mount and
  blade: warband, the screen goes blank and the computer freezes. A hard
  reboot is the only way to proceed. I have reinstalled drivers several
  times, with no change in this situation. I know it's not a specs
  problem because I ran these games on the exact same machine a couple
  of weeks ago when I had Windows 10 installed (which I have since
  removed). I think this is an xorg problem but I am not sure.

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 14:02:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (prog-if 00 [VGA controller])
 Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM] [1b0a:90c4]
  InstallationDate: Installed on 2018-09-11 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard 500-002a
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.15
  dmi.board.name: 2ADA
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE3190T0P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 500-002a
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1810170730.58a51d~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810170730.58a51d~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1809261933.80514b~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

To manage notifications about this bug go to:
h

Re: [Desktop-packages] [Bug 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

Hello Daniel

I did not receive any instructions, or any text at all in your last 
message. I am just wanting to know if there is any update on this issue 
and how to solve it.

Regards, Adrian

On 22/10/18 6:22 pm, Daniel van Vugt wrote:
> ** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: xorg-server (Ubuntu)
> Status: Incomplete => New
>

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

Title:
  [amdgpu] All video games freeze 5-10mins into play

Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I recently installed steam on my system (Ubuntu 18.04), installed a
  couple of games and attemped to play them. About a couple of minutes
  in to playing cities: skylines, kerbal space program and mount and
  blade: warband, the screen goes blank and the computer freezes. A hard
  reboot is the only way to proceed. I have reinstalled drivers several
  times, with no change in this situation. I know it's not a specs
  problem because I ran these games on the exact same machine a couple
  of weeks ago when I had Windows 10 installed (which I have since
  removed). I think this is an xorg problem but I am not sure.

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 14:02:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (prog-if 00 [VGA controller])
 Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM] [1b0a:90c4]
  InstallationDate: Installed on 2018-09-11 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard 500-002a
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.15
  dmi.board.name: 2ADA
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE3190T0P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 500-002a
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1810170730.58a51d~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810170730.58a51d~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1809261933.80514b~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1798739/+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 1798739] Re: [amdgpu] All video games freeze 5-10mins into play

[Adrian Barbuio]

No worries. The txt file is attached.

Regards, Adrian

On 22/10/18 5:28 pm, Daniel van Vugt wrote:
> Thanks.
>
> Please also run this command and send us the output:
>
>dpkg -l > allpackages.txt
>
> ** Summary changed:
>
> - All video games freeze 5-10mins into play
> + [amdgpu] All video games freeze 5-10mins into play
>
> ** Package changed: ubuntu => xorg-server (Ubuntu)
>


** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/bugs/1798739/+attachment/5203873/+files/allpackages.txt

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

Title:
  [amdgpu] All video games freeze 5-10mins into play

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I recently installed steam on my system (Ubuntu 18.04), installed a
  couple of games and attemped to play them. About a couple of minutes
  in to playing cities: skylines, kerbal space program and mount and
  blade: warband, the screen goes blank and the computer freezes. A hard
  reboot is the only way to proceed. I have reinstalled drivers several
  times, with no change in this situation. I know it's not a specs
  problem because I ran these games on the exact same machine a couple
  of weeks ago when I had Windows 10 installed (which I have since
  removed). I think this is an xorg problem but I am not sure.

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 14:02:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (prog-if 00 [VGA controller])
 Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM] [1b0a:90c4]
  InstallationDate: Installed on 2018-09-11 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard 500-002a
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.15
  dmi.board.name: 2ADA
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE3190T0P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 500-002a
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1810170730.58a51d~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810170730.58a51d~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1809261933.80514b~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1798739/+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 1798739] [NEW] All video games freeze 5-10mins into play

[Adrian Barbuio]

Public bug reported:

I recently installed steam on my system (Ubuntu 18.04), installed a
couple of games and attemped to play them. About a couple of minutes in
to playing cities: skylines, kerbal space program and mount and blade:
warband, the screen goes blank and the computer freezes. A hard reboot
is the only way to proceed. I have reinstalled drivers several times,
with no change in this situation. I know it's not a specs problem
because I ran these games on the exact same machine a couple of weeks
ago when I had Windows 10 installed (which I have since removed). I
think this is an xorg problem but I am not sure.

xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.7+19ubuntu7 500
500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 19 14:02:58 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] 
[1002:6611] (prog-if 00 [VGA controller])
   Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM] [1b0a:90c4]
InstallationDate: Installed on 2018-09-11 (37 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard 500-002a
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2013
dmi.bios.vendor: AMI
dmi.bios.version: 8.15
dmi.board.name: 2ADA
dmi.board.vendor: Foxconn
dmi.board.version: 1.00
dmi.chassis.asset.tag: 4CE3190T0P
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53316J G=D
dmi.product.name: 500-002a
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1810170730.58a51d~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810170730.58a51d~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1809261933.80514b~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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


** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu

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

Title:
  All video games freeze 5-10mins into play

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed steam on my system (Ubuntu 18.04), installed a
  couple of games and attemped to play them. About a couple of minutes
  in to playing cities: skylines, kerbal space program and mount and
  blade: warband, the screen goes blank and the computer freezes. A hard
  reboot is the only way to proceed. I have reinstalled drivers several
  times, with no change in this situation. I know it's not a specs
  problem because I ran these games on the exact same machine a couple
  of weeks ago when I had Windows 10 installed (which I have since
  removed). I think this is an xorg problem but I am not sure.

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Adrian Limmi]

It worked like a charme. Thank you!

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Adrian Limmi]

Where do I put the .xpi file to be recognized by Thunderbird?

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+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 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

[Adrian Cochrane]

** Bug watch added: github.com/alcinnz/Odysseus/issues #147
   https://github.com/alcinnz/Odysseus/issues/147

** Also affects: webkit-open-source via
   https://github.com/alcinnz/Odysseus/issues/147
   Importance: Unknown
   Status: Unknown

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

Title:
  libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

Status in WebKit:
  Unknown
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Debian:
  Unknown

Bug description:
  2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=906519

  /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal 
error: jsc/jsc.h: No such file or directory
   #include 
    ^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1795901/+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 1300659]

[Adrian Johnson]

Created attachment 125086
Reduced test case

Reduced test case. This PDF strokes a single path of one of the boxes in
the original PDF. The original PDF draws the boxes with the fill-stroke
operator "B". I've replaced it with a stroke "S".

To reproduce:

pdftocairo -ps reduced-test-case.pdf out.ps

The output does not show the box.

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

Title:
  printed pdf file lacks item boxes

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  When I print the attached pdf file, then the little green boxes used to 
indicate items in the itemization are missing.
  The boxes are perfectly visible on screen, but when printing to a pdf file or 
printer or when using the pdf preview they are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1300659/+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 1300659]

[Adrian Johnson]

Created attachment 125087
Debug patch

This patch shows the problem is caused by
_cairo_path_fixed_stroke_extents().

If the operation is changed to a fill (change line 259 in the PDF from
"S" to "f") the box appears in the output.

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

Title:
  printed pdf file lacks item boxes

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  When I print the attached pdf file, then the little green boxes used to 
indicate items in the itemization are missing.
  The boxes are perfectly visible on screen, but when printing to a pdf file or 
printer or when using the pdf preview they are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1300659/+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