[Bug 2061068] Re: debsums check failed

[Pierre Equoy]

** Changed in: ubuntu
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061068

Title:
  debsums check failed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974842] Re: Audio card [8086:9d71] does not work at all (input, output) on 22.04

[Pierre Equoy]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974842

Title:
  Audio card [8086:9d71] does not work at all (input, output) on 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974842] [NEW] Audio card [8086:9d71] does not work at all (input, output) on 22.04

[Pierre Equoy]

Public bug reported:

A year ago, I filed lp:1915117 after an kernel update broke the audio on
my Acer Swift SF314-54. The bug has been marked as fixed, but I just
tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any
audio at all.

Please check lp:1915117 for some background, and the attached logs from
sosreport for more information.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: ubuntu:GNOME
Date: Sat May 21 00:27:20 2022
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Acer Swift SF314-54
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2021
dmi.bios.release: 1.17
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.17
dmi.board.name: Strongbow_KL
dmi.board.vendor: KBL
dmi.board.version: V1.17
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.17
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-54
dmi.product.sku: 
dmi.product.version: V1.17
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "sosreport-ubuntu-2022-05-21-mwvqzya.tar.xz"
   
https://bugs.launchpad.net/bugs/1974842/+attachment/5591649/+files/sosreport-ubuntu-2022-05-21-mwvqzya.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974842

Title:
  Audio card [8086:9d71] does not work at all (input, output) on 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968855] Re: apport fails when trying to report a problem about Cheese

[Pierre Equoy]

@lotuspsychje: I have the same problems as the ones you mention in
lp:1949183.

** Description changed:

  There is a problem with Cheese on 22.04 beta (image shows up scrambled
- even though it works as expected when I visit www.webcamtests.com).
+ even though it works as expected when I visit www.webcamtests.com)[1].
  
  I tried to report the problem using `ubuntu-bug cheese`.
  
  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error
  
  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...
  
  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -
  
  shows up in the terminal where I had launched `ubuntu-bug apport`.
  
  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ 
+ [1] https://gitlab.gnome.org/GNOME/cheese/-/issues/139

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968855

Title:
  apport fails when trying to report a problem about Cheese

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968855] Re: apport fails when trying to report a problem about Cheese

[Pierre Equoy]

Cheese issue filed in upstream project:

https://gitlab.gnome.org/GNOME/cheese/-/issues/139

** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #139
   https://gitlab.gnome.org/GNOME/cheese/-/issues/139

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968855

Title:
  apport fails when trying to report a problem about Cheese

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968855] Re: apport fails when trying to report a problem about Cheese

[Pierre Equoy]

** Attachment added: "Screenshot from 2022-04-13 16-31-40.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968855/+attachment/5580362/+files/Screenshot%20from%202022-04-13%2016-31-40.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968855

Title:
  apport fails when trying to report a problem about Cheese

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968855] [NEW] apport fails when trying to report a problem about Cheese

[Pierre Equoy]

Public bug reported:

There is a problem with Cheese on 22.04 beta (image shows up scrambled
even though it works as expected when I visit www.webcamtests.com).

I tried to report the problem using `ubuntu-bug cheese`.

I am asked if the problem is with Cheese, or with the image shown in
Cheese. I select the latter option, then after around 20 seconds, the
error

-
Setting pipeline to PAUSED ...
Failed to set pipeline to PAUSED.
Setting pipeline to NULL ...
ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
Freeing pipeline ...

(cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)
-

shows up in the terminal where I had launched `ubuntu-bug apport`.

Finally, Cheese is launched with a black screen instead of the webcam
picture and the text "There was an error playing the video from the
webcam".

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu80
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 13 16:24:43 2022
InstallationDate: Installed on 2022-04-01 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968855

Title:
  apport fails when trying to report a problem about Cheese

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967478] Re: Discrete GPU is not used even when using "Launch using dedicated graphics card" option

[Pierre Equoy]

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


** Summary changed:

- Dsicrete GPU is not used even when using "Launch using dedicated graphics 
card" option
+ Discrete GPU is not used even when using "Launch using dedicated graphics 
card" option

** This bug has been marked a duplicate of bug 1967456
   Jammy didn't use nvidia driver when executing firefox

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967478

Title:
  Discrete GPU is not used even when using "Launch using dedicated
  graphics card" option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox

[Pierre Equoy]

I just filed lp:1967478 before finding this issue... There might be
additional information there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967456

Title:
  Jammy didn't use nvidia driver when executing firefox

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967478] [NEW] Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option

[Pierre Equoy]

Public bug reported:

Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000 
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154) 

Summary
===

Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap applications.


Steps to reproduce
==

1. Install 22.04 beta image using third party software (nvidia proprietary 
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics Card"
6. Repeat step 3

Expected result
===

In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).

Actual result
=

In both step 3 and step 6, the active GPU is the integrated one:


Graphics


GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6


It might be a snap problem, because if I run the same test with a non-snap 
application (e.g. Terminal), it works as expected:

1. Open the terminal application, and run (you may have to install mesa-
utils package):

$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel

2. Close the terminal, right click on its icon, select  "Launch using
Discrete Graphics Card" and repeat step 1:

$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 15:46:39 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967478

Title:
  Dsicrete GPU is not used even when using "Launch using dedicated
  graphics card" option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967478] Re: Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option

[Pierre Equoy]

More logs coming from sosreport.

** Attachment added: "sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967478/+attachment/5575550/+files/sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967478

Title:
  Dsicrete GPU is not used even when using "Launch using dedicated
  graphics card" option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

[Pierre Equoy]

Just for the record, I see the same issue with a Dell Precision 7760
(CID 202103-28858) when running 22.04 beta on Wayland. I was told the
HDMI connector was wired directly to the Nvidia GPU, so gnome-shell
crashes when I connect an external monitor there, but even after logging
back in, the monitor cannot be used.

Plugging the same monitor to the USB-C connector (which is wired to
Intel GPU apparently) works like a charm...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964037

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

[Pierre Equoy]

The video shows what happens when user is using 175% fractional scaling
and then deactivate Fractional Scaling:

- only the upper left part of the screen is used
- a popup asks if user wants to keep or revert the changes
- if user clicks Revert, it doesn't actually revert back to Fractional Scaling, 
but it remains in integer scaling, and the whole screen is being used.

** Attachment added: "lp1967450_fractional_scaling.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+attachment/5575453/+files/lp1967450_fractional_scaling.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967450

Title:
  When switching from 175% fractional scaling back to integer scaling,
  only a quarter of the screen is used

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967450] [NEW] When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

[Pierre Equoy]

Public bug reported:

Steps
=

- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply

Expected results


The screen goes back to 200% integer scaling


Actual results
==

Only the upper left quarter of the screen is being used.

Workaround
==

After pressing Apply, a popup asks if we want to keep changes or revert
them.

Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!


Information
===

Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04

Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858

Third party software installed during installation

Wayland in use.

ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel and 
headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux 
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers for 
version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel 
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra 
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra 
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra 
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
signatures for nvidia modules for version 5.15.0-23-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
 b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967450

Title:
  When switching from 175% fractional scaling back to integer scaling,
  only a quarter of the screen is used

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

[Pierre Equoy]

You can clearly see what's going on in the attached video.

** Attachment added: "lp1967448_scaling300.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967448/+attachment/5575424/+files/lp1967448_scaling300.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967448

Title:
  All the windows and the desktop icons disappear constantly after
  setting Scaling to 300%

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967448] [NEW] All the windows and the desktop icons disappear constantly after setting Scaling to 300%

[Pierre Equoy]

Public bug reported:

Summary
===

Device with nvidia GPU, using proprietary drivers, wayland activated by
default.

By default, the scaling is set to 200% (the screen is UHD). If selecting
300%, all the windows close down, as well as the desktop icons (Home) as
long as the mouse cursor is in the way.

To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!), then
set Scaling back to 200% using the keyboard.

This problem does not happen in X11, and does not happen in Wayland if I
select 100%, 200% or even 400% scaling!

Steps to reproduce
==

- Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply

Expected result
===

The scaling is set to 300% and user can keep using the device.

Actual result
=

The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately if
the mouse cursor is hovering it. The desktop icons keep disappearing and
reappearing for as long as the mouse cursor is hovering the background.

The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.

Information
===

Version:Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release:22.04

Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858

Third party software installed during installation

Wayland in use.

ii  linux-generic-hwe-20.045.15.0.23.25 
   amd64Complete Generic Linux kernel and headers
ii  linux-headers-5.15.0-235.15.0-23.23 
   all  Header files related to Linux kernel version 5.15.0
ii  linux-headers-5.15.0-23-generic5.15.0-23.23 
   amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-20.045.15.0.23.25 
   amd64Generic Linux kernel headers
ii  linux-image-5.15.0-23-generic  5.15.0-23.23 
   amd64Signed kernel image generic
ii  linux-image-generic-hwe-20.04  5.15.0.23.25 
   amd64Generic Linux kernel image
ii  linux-modules-5.15.0-23-generic5.15.0-23.23 
   amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 
SMP
ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23 
   amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 
SMP
ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1   
   amd64Linux kernel nvidia modules for version 5.15.0-23
ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1   
   amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1   
   amd64Linux kernel nvidia modules for version 5.15.0-23 (objects)
ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1   
   amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-bug fixed-in-42.1 fixed-upstream jammy wayland-session

** Description changed:

  Summary
  ===
  
  Device with nvidia GPU, using proprietary drivers, wayland activated by
  default.
  
  By 

[Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310

[Pierre Equoy]

Cheese has a known issue working with some formats (see lp:1882896),
which was fixed, but the fix has not been backported to Ubuntu 20.04.

Could you also check the resolution found by the
https://webcamtests.com/ website?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945927

Title:
  Terrible resolution on integrated webcam on Dell XPS 13 Developer
  Edition 9310

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1945927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310

[Pierre Equoy]

Hello!

Sorry for the very late reply...

First of all, there have been a few Linux kernel updates in Ubuntu 20.04
since you opened this issue. Please upgrade your system and check if you
have the latest available version of the kernel installed; in a
terminal, you can run these commands:

sudo apt update
sudo apt upgrade
uname -r

You should get something like "5.13.0-30-generic".

If the problem still persists, install the Video4Linux utility package
and check what formats and resolutions are available for the webcam;
again, in a terminal:

sudo apt install v4l-utils
v4l2-ctl -D --list-formats-ext

You should get something like:

=
Driver Info:
Driver name  : uvcvideo
Card type: Video Capture 5
Bus info : usb-:00:14.0-3
Driver version   : 5.13.19
Capabilities : 0x84a1
(...)
[1]: 'MJPG' (Motion-JPEG, compressed)
Size: Discrete 640x480
(...)
=

Please attach the output of the v4l2-ctl command to this issue so we can
investigate.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945927

Title:
  Terrible resolution on integrated webcam on Dell XPS 13 Developer
  Edition 9310

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1945927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

[Pierre Equoy]

After upgrading to the last version of the packages:

gnome-shell41.3-1ubuntu1
mutter-common  41.3-1ubuntu1

the issue is gone and I can see the option when right-clicking on a
desktop launcher.

** Changed in: oem-priority
   Status: New => Invalid

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959362

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

[Pierre Equoy]

** Attachment added: "journalctl_lastboot.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557897/+files/journalctl_lastboot.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959362

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

[Pierre Equoy]

** Attachment added: "lspci-k.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557896/+files/lspci-k.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959362

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959362] [NEW] "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

[Pierre Equoy]

Public bug reported:

Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
Image: Jammy daily (20220126 build)

Test steps
==

Secure Boot enabled

Installation options:

- used ubiquity (not the new flutter installer)
- normal installation
- checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
- left "Configure Secure Boot" checked
- Setup a password for Secure Boot MOK enrollment
- Used "Erase disk and install Ubuntu" option

After installation completes, the device reboots and I enroll the MOK in
the UEFI BIOS.

At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
Wayland"), which seems to be expected given that I am using NVidia
proprietary drivers.

Once logged in, nvidia-settings and GNOME Settings About screen both
show that the GPU is available. It is set in "On-Demand" in nvidia-
settings.


$ switcherooctl 
Device: 0
  Name:Intel® UHD Graphics
  Default: yes
  Environment: DRI_PRIME=pci-_00_02_0

Device: 1
  Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
  Default: no
  Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1


Expected result
===

When right-clicking on an icon in the launcher (for instance Firefox or
Files), a "Launch using dedicated graphics card" option is available and
launches the selected software using Nvidia GPU.

Actual result
=

However, there is no "Launch using dedicated graphics card" option
available when right-clicking on an application launcher on the left.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 28 14:00:33 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-01-28 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: oem-priority
 Importance: High
 Assignee: jeremyszu (os369510)
 Status: New

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


** Tags: amd64 apport-bug jammy oem-priority third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959362

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929902] Re: [EHL] enable USB-dw3

[Pierre Equoy]

Following Kent's comment #18, a few additional steps are required to
complete the test, as described to me by Jacob Wu from Asus. The
following steps are a more detailed "step 5" from previous comment, if
you will:

1. Create a device image for partition, in this case 400MB memory space:
[Command]
$ sudo dd if=/dev/zero of=/temp.img bs=1M count=400
[Return]
400+0 records in
400+0 records out

2. Format partition as FAT32
[Command]
$ sudo mkdosfs -F 32 /temp.img
[Return]
mkfs.fat 4.1 (2017-01-24)

3. Load g_mass_storage for partition
[Command]
$ sudo modprobe g_mass_storage file=/temp.img stall=0

4. From an Ubuntu (or Windows) host, connect a cable to the USB OTG port
(on Aaeon EHL board, it's the USB type C connector) of the device under
test (DUT), and a new mass storage should be available in the host.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929902

Title:
  [EHL] enable USB-dw3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936903] Re: CDTS Network (Ethernet) failures

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Incomplete

** Changed in: intel/lookout-canyon
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903

Title:
  CDTS Network (Ethernet) failures

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Importance: Undecided => Critical

** Changed in: intel/lookout-canyon
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939505] Re: [ehl] Ubuntu Core boot fails on EHL

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Triaged

** Changed in: intel/lookout-canyon
   Importance: Undecided => Critical

** Changed in: intel/lookout-canyon
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939505

Title:
  [ehl] Ubuntu Core boot fails on EHL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946223

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945548

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929895] Re: [EHL] Enable ISHTP

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929895

Title:
  [EHL] Enable ISHTP

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929890

Title:
  [EHL][TGL][ADL] PMC Time-aware GPIO

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929901] Re: [EHL][TGL][ADL] EDAC support

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929901

Title:
  [EHL][TGL][ADL] EDAC support

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929902] Re: [EHL] enable USB-dw3

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929902

Title:
  [EHL] enable USB-dw3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929903

Title:
  [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945548

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946223

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938298

Title:
  [EHL][Graphic]Removing force probe protection from EHL platform

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938298

Title:
  [EHL][Graphic]Removing force probe protection from EHL platform

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936903] Re: CDTS Network (Ethernet) failures

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903

Title:
  CDTS Network (Ethernet) failures

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938408] Re: [ehl] board does not support soft reboot

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938408

Title:
  [ehl] board does not support soft reboot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938413] Re: [ehl] Shutdown hangs on board

[Pierre Equoy]

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413

Title:
  [ehl] Shutdown hangs on board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

[Pierre Equoy]

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939505] Re: [ehl] Ubuntu Core boot fails on EHL

[Pierre Equoy]

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939505

Title:
  [ehl] Ubuntu Core boot fails on EHL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943524] Re: [EHL] Intel ishtp VNIC driver

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943524

Title:
  [EHL] Intel ishtp VNIC driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943587] Re: [Ethtool][TSN] Support frame preemption

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943587

Title:
  [Ethtool][TSN] Support frame preemption

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929889

Title:
  [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929890

Title:
  [EHL][TGL][ADL] PMC Time-aware GPIO

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929895] Re: [EHL] Enable ISHTP

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929895

Title:
  [EHL] Enable ISHTP

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929901] Re: [EHL][TGL][ADL] EDAC support

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929901

Title:
  [EHL][TGL][ADL] EDAC support

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929902] Re: [EHL] enable USB-dw3

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929902

Title:
  [EHL] enable USB-dw3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929903

Title:
  [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938413] Re: [ehl] Shutdown hangs on board

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413

Title:
  [ehl] Shutdown hangs on board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939505] Re: [ehl] Ubuntu Core boot fails on EHL

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939505

Title:
  [ehl] Ubuntu Core boot fails on EHL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945548

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946223

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

After additional discussion with other members, I retried with the same
config as in comment #9:

CID: 202109-29496
SKU: AAEON UPN-EHL01
Image used: ubuntu-core-20-amd64+intel-iot.img.xz (20211014.2)
kernel: 5.13.0-1007-intel

Turns out, as Doug mentioned in comment #11, the UC20 configuration is
based on the initial setup wizard when installing UC20. In my case, I
had only plugged one of the two network interfaces (enp1s0), so only
this one was configured. The other was marked as `disabled` and never
used, even when plugging a cable afterwards.

The netplan configuration looked like this:

$ cat /etc/netplan/00-snapd-config.yaml 
# This is the network config written by 'console-conf'
network:
  ethernets:
enp1s0:
  dhcp4: true
  version: 2


In order to change this, I edited it like so:

$ cat /etc/netplan/00-snapd-config.yaml 
# This is the network config written by 'console-conf'
network:
  ethernets:
enp1s0:
  dhcp4: true
enp2s0:
  dhcp4: true
  version: 2

then ran `sudo netplay apply`, and the second interface (enp2s0) got an
IP shortly afterwards.

So, at least on my side (Aaeon EHL board), it's a non-issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945548

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

Trying this with

CID: 202109-29496
SKU: AAEON UPN-EHL01
Image used: ubuntu-core-20-amd64+intel-iot.img.xz (20211014.2)
kernel: 5.13.0-1007-intel

When plugging in both Ethernet ports, only one of them retrieves an IP:

$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 00:07:32:61:5b:08 brd ff:ff:ff:ff:ff:ff
3: enp1s0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:07:32:61:5b:07 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.126/24 brd 192.168.1.255 scope global dynamic enp1s0
   valid_lft 86268sec preferred_lft 86268sec
inet6 fe80::207:32ff:fe61:5b07/64 scope link 
   valid_lft forever preferred_lft forever


Nothing happens in `dmesg -w` when I unplug/replug an Ethernet cable in enp2s0.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945548

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935818] Re: Black screen if PAM session fails to initialize completely

[Pierre Equoy]

Verified OK on focal-proposed using gdm3 3.36.3-0ubuntu0.20.04.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935818

Title:
  Black screen if PAM session fails to initialize completely

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

Following a discussion with Chris, I checked /usr/share/alsa/ucm2/ and
discovered that /usr/share/alsa/ucm2/hda-dsp/ was missing.

I created it and put the files from https://github.com/alsa-project
/alsa-ucm-conf/tree/master/ucm2/hda-dsp in it.

I then restarted the computer and selected the 5.10.0-1035-oem kernel
provided by Chris.

Now, not only the sound output works as expected from internal speakers,
but the internal microphone works as well! I can also plug headsets
using the Jack output and the sound is output as expected.


I attach pulseaudio logs for reference (without any headset connected).


** Attachment added: "pulseaudio-info.logs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5509024/+files/pulseaudio-info.logs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

$ cat /sys/module/snd_intel_dspcfg/parameters/dsp_driver 
2

Same result, though... still Dummy Output in Sound Settings.

** Attachment added: 
"dmesg_kernel_5.10.0-1035-oem_snd_intel_dspcfg.dsp_driver_2.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507896/+files/dmesg_kernel_5.10.0-1035-oem_snd_intel_dspcfg.dsp_driver_2.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

** Attachment added: "dmesg_kernel_5.10.0-1035-oem.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507874/+files/dmesg_kernel_5.10.0-1035-oem.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

Here is the dmesg output as well as some output from aplay and pactl
after installing the kernel from:

https://people.canonical.com/~mschiu77/lp1915117/v2/


$ uname -a
Linux 5.10.0-1035-oem #36 SMP Mon Jun 28 16:41:34 CST 2021 x86_64 x86_64 x86_64 
GNU/Linux

I can now see the audio card with aplay -l, but it still shows "Dummy
Output" in the Sound Settings and no sound can be heard when trying to
play a sound with aplay.

** Attachment added: "alsa-pulseaudio-info.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507875/+files/alsa-pulseaudio-info.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

For the sake of testing, I checked on the latest Impish daily image,
with kernel 5.11.0-18-generic. Same problem. dmesg attached. Alsa and
PulseAudio don't detect any sound card, even though in dmesg we can see:

$ sudo dmesg | grep -i snd
[   26.169850] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[   26.169858] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ 
platform, using SST driver


$ aplay -l
aplay: device_list:276: no soundcards found...
ubuntu@ubuntu:~$ pactl list cards
ubuntu@ubuntu:~$ pactl list sources
Source #0
State: SUSPENDED
Name: auto_null.monitor
Description: Monitor of Dummy Output
Driver: module-null-sink.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 13
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: auto_null
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Dummy Output"
device.class = "monitor"
device.icon_name = "audio-input-microphone"
Formats:
pcm
ubuntu@ubuntu:~$ pactl list sinks
Sink #0
State: SUSPENDED
Name: auto_null
Description: Dummy Output
Driver: module-null-sink.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 13
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: auto_null.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY SET_FORMATS 
Properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"
Formats:
pcm


** Attachment added: "dmesg_kernel_5.11.0-18-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507056/+files/dmesg_kernel_5.11.0-18-generic.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

This is what I have now, with:

kernel command line:

BOOT_IMAGE=/vmlinuz-5.10.0-1025-oem root=/dev/mapper/vgubuntu-root ro
quiet splash vt.handoff=7

uname -a
Linux 5.10.0-1025-oem #26 SMP Thu May 6 16:43:31 CST 2021 x86_64 x86_64 x86_64 
GNU/Linux


** Attachment added: "dmesg_20210625_kernel_5.10.0-1025-oem.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506963/+files/dmesg_20210625_kernel_5.10.0-1025-oem.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

And related dmesg.log

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506571/+files/dmesg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

And the related logs from alsa-info when the dsp_driver is set to 2.

** Attachment added: "alsa-info.txt.6e591x7epf"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506569/+files/alsa-info.txt.6e591x7epf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

Attached is the output of pactl list sources.

Both aplay -l and arecord -l output the following error message:

aplay: device_list:274: no soundcards found...

I tried "snd_intel_dspcfg.dsp_driver=2", it's activated (cat
/sys/module/snd_intel_dspcfg/parameters/dsp_driver returns "2"), but
still only a Dummy output.

** Attachment added: "pactl_list_sources.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506567/+files/pactl_list_sources.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

@Chris thanks for the heads up!

Still "Dummy output" in the Sound Settings. Here are the steps I
followed:

1. Downdloaded and installed the *.deb you pointed to:

$ sudo dpkg -i *.deb

2. Copied the Intel SST firmware binary file to /lib/firmware:

$ sudo cp skl_hda_dsp_generic-tplg.bin /lib/firmware/

3. Rebooted, disabled Secure Boot and selected the new kernel
(5.10.0-1025-oem).

In dmesg, I see the following:

$ dmesg | grep snd
[   10.027748] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[   10.027752] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ 
platform, using SST driver
[   10.051128] snd_soc_skl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[   10.051132] snd_soc_skl :00:1f.3: Digital mics found on Skylake+ 
platform, using SST driver
[   10.051879] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   10.103255] snd_soc_skl :00:1f.3: Direct firmware load for 
9d71-ACRSYS-ACRPRDCT-2-tplg.bin failed with error -2
[   10.103261] snd_soc_skl :00:1f.3: tplg fw 
9d71-ACRSYS-ACRPRDCT-2-tplg.bin load failed with -2, trying alternative tplg 
name skl_hda_dsp_generic-tplg.bin
[   10.104296] snd_soc_skl :00:1f.3: ASoC: Parent card not yet available, 
widget card binding deferred
[   10.129385] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   10.129388] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   10.129389] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   10.129390] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0
[   10.129390] snd_hda_codec_realtek ehdaudio0D0:inputs:
[   10.129392] snd_hda_codec_realtek ehdaudio0D0:  Internal Mic=0x1a
[   10.129393] snd_hda_codec_realtek ehdaudio0D0:  Headset Mic=0x19


Please see the attached log for full dmesg.

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5495892/+files/dmesg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924681] Re: black screen after boot system

[Pierre Equoy]

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

I have exactly the same issue with a Dell Precision 5750 laptop that was
previously enabled with 20.04:

https://ubuntu.com/certification/hardware/202002-27726


$ prime-select query
nvidia
$ nvidia-xconfig -v

nvidia-xconfig:  version 460.67
  The NVIDIA X Configuration Tool.

  This program is used to manipulate X configuration files, specifically
to enable NVIDIA X driver functionality.


01:00.0 VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX 3000 
Mobile / Max-Q] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell TU106GLM [Quadro RTX 3000 Mobile / Max-Q]
Flags: bus master, fast devsel, latency 0, IRQ 230, IOMMU group 1
Memory at 7200 (32-bit, non-prefetchable) [size=16M]
Memory at 6000 (64-bit, prefetchable) [size=256M]
Memory at 7000 (64-bit, prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Expansion ROM at 7308 [virtual] [disabled] [size=512K]
Capabilities: 
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924681

Title:
  black screen after boot system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924685] [NEW] No sound output/input available after installing 21.04

[Pierre Equoy]

Public bug reported:

Image: Hirsute 21.04 (20210415 daily build)

Device: Dell Precision 5750

After installing 21.04, the sound card is unavailable. In Sound
Settings, there is only one choice: "Dummy Output" .

The only way to hear sound is to connect a Bluetooth speaker.

Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

https://certification.ubuntu.com/hardware/202002-27726

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-14-generic 5.11.0-14.15
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1561 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 15:10:05 2021
InstallationDate: Installed on 2021-04-16 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
MachineType: Dell Inc. Precision 5750
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-14-generic N/A
 linux-backports-modules-5.11.0-14-generic  N/A
 linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5750
dmi.product.sku: 0990
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug hirsute

** Description changed:

  Image: Hirsute 21.04 (20210415 daily build)
  
  Device: Dell Precision 5750
  
  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .
  
  The only way to hear sound is to connect a Bluetooth speaker.
  
- Attached are logs from `pactl list` and `alsa-info`.
+ Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:
+ 
+ https://certification.ubuntu.com/hardware/202002-27726
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  1561 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.11.0-14-generic N/A
-  linux-backports-modules-5.11.0-14-generic  N/A
-  linux-firmware 1.197
+  linux-restricted-modules-5.11.0-14-generic N/A
+  linux-backports-modules-5.11.0-14-generic  N/A
+  linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924685

Title:
  No sound output/input available after installing 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

Adding alsa-info log from the mainline kernel.

** Attachment added: "alsa-info..mainline-kernel-5.11.0-051100-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5464398/+files/alsa-info..mainline-kernel-5.11.0-051100-generic.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

I installed the following:

linux-headers-5.11.0-051100_5.11.0-051100.202102142330_all.deb
linux-headers-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb
linux-image-unsigned-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb
linux-modules-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb


I was warned for a bunch of "possible missing firmwares" for module i915:

W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module 
i915

(see install.log attached for complete logs)

After disabling Secure Boot and botting in kernel 5.11, I still face the
same issue: no input (nor output) sound devices (only "Dummy Output").

** Attachment added: "install.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5464397/+files/install.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

I've also tried booting a live USB with the latest alpha version from
21.04, based on kernel 5.8.0-36-generic, and the results are the same:
no sound card detected, "Dummy Output" displayed in Sound Settings. See
attached archive with same logs (dmesg, pactl, alsa-info).

** Attachment added: "21.04-kernel-5.8.0-36-audio-logs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461562/+files/21.04-kernel-5.8.0-36-audio-logs.tar.xz

** Description changed:

  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11
  
  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)
  
  Summary
  ===
  
  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound card
  is available.
  
  Steps to reproduce
  ==
  
  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8
  
  Expected results
  
  
  Sound output still works.
  
  Actual results
  ==
  
- No more sound card detected (Sound Settings display "Dummy Output" in
- the list of output devices).
+ 2. Sound card is available, and sound can be output to the internal speakers.
+ 4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-41-generic N/A
-  linux-backports-modules-5.8.0-41-generic  N/A
-  linux-firmware1.190.3
+  linux-restricted-modules-5.8.0-41-generic N/A
+  linux-backports-modules-5.8.0-41-generic  N/A
+  linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

** Attachment added: "pactl-list-20.10-kernel-5.4.0-65-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461560/+files/pactl-list-20.10-kernel-5.4.0-65-generic.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

** Attachment added: "dmesg-20.10-kernel-5.4.0-65-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461559/+files/dmesg-20.10-kernel-5.4.0-65-generic.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

As a point of comparison, below are attached logs when using the same
device with the same Ubuntu (20.10) but with an older 5.4.0-65-generic
kernel.

** Attachment added: "alsa-info.20.10-kernel-5.4.0-65-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461558/+files/alsa-info.20.10-kernel-5.4.0-65-generic.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915117] [NEW] [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Pierre Equoy]

Public bug reported:

Ubuntu version: 20.10 (updated from 20.04)
Kernel: 5.8.0-41-generic #46-Ubuntu
Manufacturer: Acer
Product Name: Swift SF314-54
BIOS Revision: 1.11

Audio card: Realtek High Definition Audio
Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)

Summary
===

After upgrading from linux kernel 5.4 to 5.8, there is no more sound
card available. However, if I select kernel 5.4 in GRUB, the sound card
is available.

Steps to reproduce
==

1. Install 20.04 or 20.10 with a kenel 5.4
2. Check that sound output works as excepted (Settings > Sound > Output > Test)
3. Check that `alsa-info` command returns information
4. Upgrade kernel to 5.8

Expected results


Sound output still works.

Actual results
==

2. Sound card is available, and sound can be output to the internal speakers.
4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-41-generic 5.8.0-41.46
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  9 14:42:00 2021
InstallationDate: Installed on 2019-01-20 (751 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Swift SF314-54
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-41-generic N/A
 linux-backports-modules-5.8.0-41-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
dmi.bios.date: 11/21/2018
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.name: Strongbow_KL
dmi.board.vendor: KBL
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.ec.firmware.release: 1.6
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-54
dmi.product.sku: 
dmi.product.version: V1.11
dmi.sys.vendor: Acer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Pierre Equoy]

Hi Salima,

this bug has been identified as happening only for people who were
upgrading from a previous version of Ubuntu (that came with a previous
version of Pulseaudio). Daniel Van Vugt found a workaround (check
comments 18 and 19 above), and a fix has been made by the Pulseaudio
developers and is being reviewed (see comment 41 above).

In your case, it seems the issue happens on a fresh install, so I
believe this issue is different. Please file a new bug for this.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866194

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses

[Pierre Equoy]

If that can be of any help, I have the following use case:

In addition to the default Firefox launcher, I created two other
.desktop files:

- One called "Wayland Firefox #1" to run Firefox on Wayland with user 
profile #1
- The other called "Wayland Firefox #2" to run Firefox on Wayland with user 
profile #2

I'm using a 4k screen (3840×2160), so I have *a lot* of space available
on the screen.

And yet, GNOME uses ellipsis and this is what I get when I look for
"Firefox" in the GNOME Overview screen (see attachment).

I hope this gets fixed soon. Something as simple as a tooltip when
putting the cursor on top of the icon or text would be very helpful
already.

** Attachment added: "gnome-activities.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/968213/+attachment/5379588/+files/gnome-activities.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968213

Title:
  Too many icons in Gnome Shell Activities Overview require ellipses

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878258] Re: wifi missing on core20 image with rpi

[Pierre Equoy]

** Description changed:

  With the rpi images for core20, no wifi interface is detected. I've
  tried this on rpi4 for certain, but I believe it is also happening on
  all other rpi devices with wifi.
  
- This can be reproduced on this image, as well as others:
- http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/
- 
+ This can be reproduced on both armhf and arm64 images, as well as
+ others: http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/
  
  Only lo and eth0 are detecte:
  $ ip link show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: eth0:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
- link/ether dc:a6:32:59:ce:25 brd ff:ff:ff:ff:ff:ff
+ link/ether dc:a6:32:59:ce:25 brd ff:ff:ff:ff:ff:ff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878258

Title:
  wifi missing on core20 image with rpi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1878258/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20

[Pierre Equoy]

I have the same issue with the armhf image:

$ uname -a
Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:49:33 UTC 2020 armv7l 
armv7l armv7l GNU/Linux

$ snap list
Name   VersionRev   Tracking Publisher   Notes
core20 20 633   latest/beta  canonical✓  base
pi 20-1   5920/beta  canonical✓  gadget
pi-kernel  5.4.0-1011.11  153   20/beta  canonical✓  kernel
snapd  2.45   7779  latest/beta  canonical✓  snapd

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878271

Title:
  rpi: no uboot or kernel boot mesages on console during boot on core20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878271/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874377] Re: Netplan does not connect to Wireless after `sudo netplan apply` until reboot

[Pierre Equoy]

** Description changed:

  Summary
  ===
  
+ Issue observed using 20200422 images 
focal-preinstalled-server-arm64+raspi.img.xz and 
focal-preinstalled-server-armhf+raspi.img.xz on:
+ - Rapsberry Pi 4 4GB
+ - Rapsberry Pi 3B
+ 
  When setting up Wireless network via netplan config on a Raspberry Pi 4
- 4GB with Ubuntu Server 20.04 (image focal-preinstalled-server-
- arm64+raspi.img.xz 2020-04-22 19:39 667M), the settings are not taken
- into account until the device is rebooted, because the service created
- (netplan-wpa-wlan0.service) is in a "inactive (dead)" state.
+ 4GB with Ubuntu Server 20.04, the settings are not taken into account
+ until the device is rebooted, because the service created (netplan-wpa-
+ wlan0.service) is in a "inactive (dead)" state.
  
  A workaround is to manually restart the service after applying netplan
  configuration
  
  $ sudo netplan apply
  $ sudo systemctl restart netplan-wpa-wlan0.service
  
  This should be done automatically when a new netplan configuration is
  applied.
  
  Steps to reproduce
  ==
  
  1. Install Ubuntu Server 20.04 image 
(focal-preinstalled-server-arm64+raspi.img.xz) on a Raspberry Pi 4 4GB (I 
haven't tested with Ubuntu Server on other devices).
  2. Connect a screen and a USB keyboard, or connect to the device via serial 
console (UART).
  3. By default, the device is not connected to the network yet:
  
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
- inet 127.0.0.1/8 scope host lo
-valid_lft forever preferred_lft forever
- inet6 ::1/128 scope host 
-valid_lft forever preferred_lft forever
- 2: eth0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
- link/ether dc:a6:32:57:b9:ba brd ff:ff:ff:ff:ff:ff
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
+ 2: eth0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
+ link/ether dc:a6:32:57:b9:ba brd ff:ff:ff:ff:ff:ff
  3: wlan0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
- link/ether dc:a6:32:57:b9:bb brd ff:ff:ff:ff:ff:ff
- 
- $ networkctl
- IDX LINK  TYPE OPERATIONAL SETUP  
-   1 loloopback carrier unmanaged  
-   2 eth0  etherno-carrier  configuring
-   3 wlan0 wlan off unmanaged  
+ link/ether dc:a6:32:57:b9:bb brd ff:ff:ff:ff:ff:ff
+ 
+ $ networkctl
+ IDX LINK  TYPE OPERATIONAL SETUP
+   1 loloopback carrier unmanaged
+   2 eth0  etherno-carrier  configuring
+   3 wlan0 wlan off unmanaged
  
  3 links listed.
- 
  
  4. Create a netplan config file to match your WiFi router config and
  copy it to /etc/netplan/:
  
- $ cat lab.yaml 
+ $ cat lab.yaml
  network:
-   version: 2
-   wifis:
- wlan0:
-   access-points:
- ubuntu-cert-wpa:
-   password: myp455w0rd
-   dhcp4: yes
+   version: 2
+   wifis:
+ wlan0:
+   access-points:
+ ubuntu-cert-wpa:
+   password: myp455w0rd
+   dhcp4: yes
  
  $ sudo cp lab.yaml /etc/netplan/
- 
  
  5. Apply the new configuration:
  
  $ sudo netplan apply
  
  In journalctl:
  
  Apr 23 03:57:38 ubuntu systemd[1]: systemd-networkd-wait-online.service: 
Succeeded.
  Apr 23 03:57:38 ubuntu systemd[1]: Stopped Wait for Network to be Configured.
  Apr 23 03:57:38 ubuntu systemd[1]: Stopping Network Service...
  Apr 23 03:57:38 ubuntu systemd[1]: systemd-networkd.service: Succeeded.
  Apr 23 03:57:38 ubuntu systemd[1]: Stopped Network Service.
  Apr 23 03:57:39 ubuntu systemd[1]: Starting Network Service...
  Apr 23 03:57:39 ubuntu sudo[1674]: pam_unix(sudo:session): session closed for 
user root
  Apr 23 03:57:39 ubuntu systemd-networkd[1687]: Enumeration completed
  Apr 23 03:57:39 ubuntu systemd[1]: Star[  223.067294] brcmfmac: 
brcmf_cfg80211_set_power_mgmt: power save enabled
  ted Network Service.
  Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: IPv6 successfully 
enabled
  Apr 23 03:57:39 ubuntu systemd-networkd[1687]: eth0: IPv6 successfully enabled
  Apr 23 03:57:39 ubuntu kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power 
save enabled
  Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: Link UP
  
  $ networkctl
- IDX LINK  TYPE OPERATIONAL SETUP  
-   1 loloopback carrier unmanaged  
-   2 eth0  etherno-carrier  configuring
-   3 wlan0 wlan no-carrier  configuring
+ IDX LINK  TYPE OPERATIONAL SETUP
+   1 loloopback carrier unmanaged
+   2 eth0  etherno-carrier  configuring
+   3 wlan0 wlan no-carrier  configuring
  
  3 links listed.
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
- inet 127.0.0.1/8 scope host lo
-valid_lft 

[Bug 1874377] [NEW] Netplan does not connect to Wireless after `sudo netplan apply` until reboot

[Pierre Equoy]

Public bug reported:

Summary
===

When setting up Wireless network via netplan config on a Raspberry Pi 4
4GB with Ubuntu Server 20.04 (image focal-preinstalled-server-
arm64+raspi.img.xz 2020-04-22 19:39 667M), the settings are not taken
into account until the device is rebooted, because the service created
(netplan-wpa-wlan0.service) is in a "inactive (dead)" state.

A workaround is to manually restart the service after applying netplan
configuration

$ sudo netplan apply
$ sudo systemctl restart netplan-wpa-wlan0.service

This should be done automatically when a new netplan configuration is
applied.

Steps to reproduce
==

1. Install Ubuntu Server 20.04 image 
(focal-preinstalled-server-arm64+raspi.img.xz) on a Raspberry Pi 4 4GB (I 
haven't tested with Ubuntu Server on other devices).
2. Connect a screen and a USB keyboard, or connect to the device via serial 
console (UART).
3. By default, the device is not connected to the network yet:

$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether dc:a6:32:57:b9:ba brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether dc:a6:32:57:b9:bb brd ff:ff:ff:ff:ff:ff

$ networkctl
IDX LINK  TYPE OPERATIONAL SETUP  
  1 loloopback carrier unmanaged  
  2 eth0  etherno-carrier  configuring
  3 wlan0 wlan off unmanaged  

3 links listed.


4. Create a netplan config file to match your WiFi router config and
copy it to /etc/netplan/:

$ cat lab.yaml 
network:
  version: 2
  wifis:
wlan0:
  access-points:
ubuntu-cert-wpa:
  password: myp455w0rd
  dhcp4: yes

$ sudo cp lab.yaml /etc/netplan/


5. Apply the new configuration:

$ sudo netplan apply

In journalctl:

Apr 23 03:57:38 ubuntu systemd[1]: systemd-networkd-wait-online.service: 
Succeeded.
Apr 23 03:57:38 ubuntu systemd[1]: Stopped Wait for Network to be Configured.
Apr 23 03:57:38 ubuntu systemd[1]: Stopping Network Service...
Apr 23 03:57:38 ubuntu systemd[1]: systemd-networkd.service: Succeeded.
Apr 23 03:57:38 ubuntu systemd[1]: Stopped Network Service.
Apr 23 03:57:39 ubuntu systemd[1]: Starting Network Service...
Apr 23 03:57:39 ubuntu sudo[1674]: pam_unix(sudo:session): session closed for 
user root
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: Enumeration completed
Apr 23 03:57:39 ubuntu systemd[1]: Star[  223.067294] brcmfmac: 
brcmf_cfg80211_set_power_mgmt: power save enabled
ted Network Service.
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: IPv6 successfully enabled
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: eth0: IPv6 successfully enabled
Apr 23 03:57:39 ubuntu kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power 
save enabled
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: Link UP

$ networkctl
IDX LINK  TYPE OPERATIONAL SETUP  
  1 loloopback carrier unmanaged  
  2 eth0  etherno-carrier  configuring
  3 wlan0 wlan no-carrier  configuring

3 links listed.
$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether dc:a6:32:57:b9:ba brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc fq_codel state 
DOWN group default qlen 1000
link/ether dc:a6:32:57:b9:bb brd ff:ff:ff:ff:ff:ff


Even if I wait 5 minutes, nothing moves. networkctl tells me wlan0 is 
"configuring", but nothing happens in the journal.

Trying to restart systemd-networkd doesn't help:

$ sudo systemctl status systemd-networkd
● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; ven>
 Active: active (running) since Thu 2020-04-23 03:57:39 UTC; 1min 18s ago
TriggeredBy: ● systemd-networkd.socket
   Docs: man:systemd-networkd.service(8)
   Main PID: 1687 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4434)
 CGroup: /system.slice/systemd-networkd.service
 └─1687 /lib/systemd/systemd-networkd

Apr 23 03:57:39 ubuntu systemd[1]: Starting Network Service...
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: Enumeration completed
Apr 23 03:57:39 ubuntu systemd[1]: Started Network Service.
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: IPv6 successfully enabled
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: eth0: IPv6 successfully enabled
Apr 23 03:57:39 ubuntu systemd-networkd[1687]: wlan0: Link UP

$ sudo systemctl restart 

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

@Daniel:

I've tried the workaround I've described in bug 1866194 comment 7, but
it doesn't work on this device.

As Rex mentioned, it's probably a known limitation... for the time
being, I'll use the HDMI audio output and plug my headphones to my
external screen (that works fine).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871536] Re: "Ubuntu Software" icon absent from dash after installing 20.04 beta

[Pierre Equoy]

** Tags added: ce-qa-concern

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871536

Title:
  "Ubuntu Software" icon absent from dash after installing 20.04 beta

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871536] [NEW] "Ubuntu Software" icon absent from dash after installing 20.04 beta

[Pierre Equoy]

Public bug reported:

Ubuntu: 20.04 (beta image)

Summary
===

After a fresh install, the "Ubuntu Software" icon is absent from the
dash. To find it, user has to click "Show Applications" at the bottom
left and search for "Ubuntu Software".

Steps to reproduce
==

1. Install 20.04 beta (in my case, because of lp:1871268, I did the 
installation without being connected to the Internet)
2. When the first use panel is shown (asking if you want Live Update, send the 
anonymized info to Canonical, etc.), when the screen about softwares is shown, 
don't click "Open".

Expected results


At the end of the installation, "Ubuntu Software" is among the icons
available in the dash.

Actual results
==

No "Ubuntu Software" icon in the dash.

My guess is that since the "snap store" snap is now being used instead
of the gnome-software Debian package, something is missing to add the
icon to the dash by default.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 01:43:15 2020
InstallationDate: Installed on 2020-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871536

Title:
  "Ubuntu Software" icon absent from dash after installing 20.04 beta

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871523] [NEW] linux-modules-5.4.0-1002-oem installed on certified systems after installing focal beta

[Pierre Equoy]

Public bug reported:

Summary
===

After installing Ubuntu focal (20.04) beta image on two certified
systems (see "Additional info" below), I can see `linux-
modules-5.4.0-1002-oem` package installed when running `dpkg -l | grep
-i oem`.

On both systems, the following packages are installed during the
installation process:

linux-oem-20.04
linux-image-5.4.0-1002-oem
linux-oem-5.4-headers-5.4.0-1002
linux-modules-5.4.0-1002-oem


then these ones are purged:

linux-image-5.4.0-1002-oem
linux-oem-5.4-headers-5.4.0-1002
linux-oem-20.04
linux-headers-oem-20.04
linux-headers-5.4.0-1002-oem
linux-image-oem-20.04

but for some reason, linux-modules-5.4.0-1002-oem is not purged.

For info:

$ apt rdepends linux-modules-5.4.0-1002-oem
linux-modules-5.4.0-1002-oem
Reverse Depends:
  Depends: linux-image-5.4.0-1002-oem
  Depends: linux-image-unsigned-5.4.0-1002-oem

but neither linux-image-unsigned-5.4.0-1002-oem or linux-
image-5.4.0-1002-oem are installed.


Additional info
===

Ubuntu version: focal beta image

Seen on Certified Devices:
 - Dell Vostro 5590 
 - Dell XPS 13 9300

Please see attached logs from both system for more information.

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


** Tags: ce-qa-concern champagne focal oem ubuntu-certified

** Attachment added: "vostro-5590-201905-27083-apt-history.log"
   
https://bugs.launchpad.net/bugs/1871523/+attachment/5349145/+files/vostro-5590-201905-27083-apt-history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871523

Title:
  linux-modules-5.4.0-1002-oem installed on certified systems after
  installing focal beta

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871523] Re: linux-modules-5.4.0-1002-oem installed on certified systems after installing focal beta

[Pierre Equoy]

** Attachment added: "xps-9300-201911-27469-apt-history.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871523/+attachment/5349146/+files/xps-9300-201911-27469-apt-history.log

** Tags added: ce-qa-concern champagne focal oem

** Tags added: ubuntu-certified

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871523

Title:
  linux-modules-5.4.0-1002-oem installed on certified systems after
  installing focal beta

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

** Tags added: ce-qa-concern champagne

** Tags added: ubuntu-certified

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

** Attachment added: "pactl_info_internal_speakers.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348499/+files/pactl_info_internal_speakers.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

** Attachment added: "pactl_list_internal_speakers.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348501/+files/pactl_list_internal_speakers.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] [NEW] No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

Public bug reported:


Summary
===

Internal speakers work as expected, but when plugging headphones through
the 3.5mm jack, the "Select Audio Device" panel doesn't show up (it
normally shows up to allow user to select what kind of device has been
plugged in, be it headphones, microphone or headset). In the Sound
Settings, the Output Device automatically switches to "Headphones - sof-
hda-dsp", but no sound can be heard even though the vumeter in the Sound
Settings moves!

Steps to reproduce
==

1. Install focal beta
2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
3. Plug headphones in jack 3.5mm interface

Expected Results


- In Sound Settings, the headphones are automatically selected as output device
- In Sound Settings, the vumeter under the Output Device moves according to the 
sound
- Sound can be heard through the headphones


Actual results
==

- In Sound Settings, the headphones are automatically selected as output device 
(OK)
- In Sound Settings, the vumeter under the Output Device moves according to the 
sound (OK)
- No sound can be heard (Not OK)

Attached are output of `pactl info` and `pactl list` before and after
plugging headphones, while playing a tune on Bandcamp in Firefox.


Additional Info
===

Ubuntu: 20.04 beta image
Certified device: 
system-manufacturer: Dell Inc.
system-product-name: Vostro 5590
bios-version: 1.1.0
CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
kernel-version: 5.4.0-21-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pieq   1768 F pulseaudio
 /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
 /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 16:33:27 2020
InstallationDate: Installed on 2020-04-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5590
dmi.product.sku: 095A
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

** Attachment added: "pactl_list_headphones.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348500/+files/pactl_list_headphones.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Pierre Equoy]

** Attachment added: "pactl_info_headphones.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348498/+files/pactl_info_headphones.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Pierre Equoy]

If the exact same installation process is followed *without being
connected to the Internet*, the installation can be completed
successfully.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Pierre Equoy]

One more info: my system has a nvidia card and has secure boot enabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Clean Install first time

[Pierre Equoy]

Forgot to mention I'm using Ubuntu image, not Xubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Clean Install first time

[Pierre Equoy]

Facing a crash that looks similar.

In ubiquity install.trace file, I can see:

apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not
perform immediate configuration on 'libgcc-s1:i386'. Please see man 5
apt.conf under APT::Immediate-Configure for details. (2)

Device: Dell Vostro 5590
Image: Focal 20.04 beta
Install: connected to the Internet (using an Ethernet cable)
Install options:
 - erase disk and install Ubuntu
 - use LVM partitioning
 - use encryption

I installed 20.04 a few weeks ago on the same device and didn't face
this issue.

Also, I tried booting in "safe graphics mode" for the install but it
didn't help.

** Attachment added: "201905-27083_focal_beta_install_crashlogs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871268/+attachment/5348320/+files/201905-27083_focal_beta_install_crashlogs.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store

[Pierre Equoy]

Installed focal fossa beta this morning on a XPS 13 (9300), and facing
the same issue.

The first thing I usually do is to install GNOME Tweaks, and this
doesn't show in Snap Store.

Tried snap-store rev336 (installed by default) and rev344 (from edge
channel): same result.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870184

Title:
  Snap store not showing ubuntu repository apt apps inthe store

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

[Pierre Equoy]

Installed bluez 5.50 -> same result.

Installed linux 5.3 -> same result.

Tried a combination of all the linux/bluez possibilites -> same result.

Until now, I was only looking at the output of btmon (so basically, low
level BT commands).

Then, while I was doing one of the tests above, I tailed
/var/log/syslog, and I saw this weird thing whenever I tried pairing a
BT device (just when it turned from "connected" to immediately
"disconnected" in g-c-c):

bluetoothd[965]: a2dp-sink profile connect failed for 88:C6:26:1A:9E:AF: 
Protocol not available
bluetoothd[965]: a2dp-source profile connect failed for 88:C6:26:1A:9E:AF: 
Protocol not available

Turns out [1] this is because I was lacking the pulseaudio-module-
bluetooth package! After installing it and restarting the device, I can
pair and connect my usual BT devices...

I don't know why it used to work earlier (while I was already on 20.04)
and why it broke one day. I kept upgrading regularly using `sudo apt
update` and `sudo apt dist-upgrade`...

Anyway, it seems the issue was a non-issue... and I wasted a lot of time
investigating it!


[1] 
https://donjajo.com/bluetooth-fix-a2dp-source-profile-connect-failed-xx-protocol-not-available-linux/

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869857

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs