[Desktop-packages] [Bug 2053296] Re: UnboundLocalError Python error when running `ubuntu-drivers autoinstall`

[Pierre Equoy]

This looks very similar to lp:1995158, but I wanted to complete the
`ubuntu-bug` process in order to capture the logs for that machine.

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

Title:
  UnboundLocalError Python error when running `ubuntu-drivers
  autoinstall`

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  As part of the Certification regression testing process, we
  automatically provision devices in our Certification lab with
  different versions of Ubuntu to make sure no regressions are
  introduced during the SRU process.

  Recently, we got an issue when trying to provision Ubuntu 22.04 on a
  device with a Nvidia GPU. The Nvidia drivers should be installed with
  the ubuntu-drivers autoinstall command, however when run, the
  following exception is thrown:

  ubuntu@10.102.163.75 sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.1/:01:00.0 ==
  modalias : pci:v10DEd2571sv103Csd1611bc03sc00i00
  vendor   : NVIDIA Corporation
  driver   : nvidia-driver-525-open - distro non-free
  driver   : nvidia-driver-470-server - distro non-free
  driver   : nvidia-driver-535-server-open - distro non-free
  driver   : nvidia-driver-535 - distro non-free
  driver   : nvidia-driver-545-open - distro non-free recommended
  driver   : nvidia-driver-535-server - distro non-free
  driver   : nvidia-driver-470 - distro non-free
  driver   : nvidia-driver-535-open - distro non-free
  driver   : nvidia-driver-525-server - distro non-free
  driver   : nvidia-driver-545 - distro non-free
  driver   : nvidia-driver-525 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  == /sys/devices/pci:00/:00:1f.4 ==
  modalias : pci:v8086d7AA3sv103Csd895Ebc0Csc05i00
  vendor   : Intel Corporation
  driver   : oem-stella-asobo-meta - distro free

  + _run sudo ubuntu-drivers autoinstall
  + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.163.75 sudo ubuntu-drivers autoinstall
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-drivers-common 1:0.9.6.2~0.22.04.6
  ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
  Uname: Linux 5.15.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
  Date: Thu Feb 15 21:53:15 2024
  InstallationDate: Installed on 2022-05-10 (646 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2053296/+subscriptions


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

[Desktop-packages] [Bug 1995158] Re: "ubuntu-drivers autoinstall" fails with Python UnboundLocaError

[Pierre Equoy]

** Tags added: cert-sru

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

Title:
  "ubuntu-drivers autoinstall" fails with Python UnboundLocaError

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  I'm having problems with an external monitor on my laptop, so I wanted
  to update the NVIDA drivers.

  I first tried this in the "Additional Drivers" tab of "Software &
  Updates". I selected a newer driver, clicked "Apply Changes", and
  entered my password to install updates. This showed a progress bar and
  seemed to be working, but after a few seconds I got a blank error
  dialogue, with only an X button. I tried a few other driver versions
  with the same result.

  Next, I tried running `ubuntu-drivers autoinstall` from the command
  line. I expected this would install some drivers. Instead, I got this
  error trace:

  ```
  $ sudo ubuntu-drivers autoinstall
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment
  ```

  
  Looking at the code I believe the 'finally' block is trying to use the 
'version' variable set in the `try`, which can only work if the try succeeds. 
Seeing this, I modified the script to set a default value for 'version':

  ```
  *** /home/edward/detect.py.original   2022-10-29 15:40:49.515765835 +1100
  --- /home/edward/detect.py.fixed  2022-10-29 15:39:55.383555776 +1100
  ***
  *** 828,839 
  --- 828,840 
'''Applies changes that need to happen before installing the NVIDIA 
drivers'''
with_nvidia_kms = False

# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
  + version = -1
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
  ```

  With this change `ubuntu-drivers autoinstall` ran successfully and
  installed a bunch of packages. I can now see in Software & Updates
  that I am updated to the latest NVIDIA driver versions. (However my
  monitor isn't working yet so there may be another underlying issue.)

  
  

  Version information:

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
   *** 1:0.9.6.1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-drivers-common 1:0.9.6.1 [modified: 
usr/lib/python3/dist-packages/UbuntuDrivers/detect.py]
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 15:31:57 2022
  InstallationDate: Installed on 2021-04-01 (575 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1995158/+subscriptions


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

[Desktop-packages] [Bug 2053296] [NEW] UnboundLocalError Python error when running `ubuntu-drivers autoinstall`

[Pierre Equoy]

Public bug reported:

As part of the Certification regression testing process, we
automatically provision devices in our Certification lab with different
versions of Ubuntu to make sure no regressions are introduced during the
SRU process.

Recently, we got an issue when trying to provision Ubuntu 22.04 on a
device with a Nvidia GPU. The Nvidia drivers should be installed with
the ubuntu-drivers autoinstall command, however when run, the following
exception is thrown:

ubuntu@10.102.163.75 sudo ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.1/:01:00.0 ==
modalias : pci:v10DEd2571sv103Csd1611bc03sc00i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : nvidia-driver-545-open - distro non-free recommended
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-545 - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

== /sys/devices/pci:00/:00:1f.4 ==
modalias : pci:v8086d7AA3sv103Csd895Ebc0Csc05i00
vendor   : Intel Corporation
driver   : oem-stella-asobo-meta - distro free

+ _run sudo ubuntu-drivers autoinstall
+ ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.163.75 sudo ubuntu-drivers autoinstall
Traceback (most recent call last):
  File "/usr/bin/ubuntu-drivers", line 513, in 
greet()
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
  File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
  File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-drivers-common 1:0.9.6.2~0.22.04.6
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
Date: Thu Feb 15 21:53:15 2024
InstallationDate: Installed on 2022-05-10 (646 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  UnboundLocalError Python error when running `ubuntu-drivers
  autoinstall`

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  As part of the Certification regression testing process, we
  automatically provision devices in our Certification lab with
  different versions of Ubuntu to make sure no regressions are
  introduced during the SRU process.

  Recently, we got an issue when trying to provision Ubuntu 22.04 on a
  device with a Nvidia GPU. The Nvidia drivers should be installed with
  the ubuntu-drivers autoinstall command, however when run, the
  following exception is thrown:

  ubuntu@10.102.163.75 sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.1/:01:00.0 ==
  modalias : 

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

Just to clarify, my webcam is a very simple (and old, like 10 years
old!) USB webcam: 046d:0802 Logitech, Inc. Webcam C200.

Attached output from v4l-info.

** Attachment added: "v4linfo.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635648/+files/v4linfo.log

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

And this is the logs from Chromium when running the steps in the
previous comment.

** Attachment added: "chromium_hwacc_no_webcam.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635526/+files/chromium_hwacc_no_webcam.log

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

1. The Pipewire flag was set to "Default", but even when set to "Enabled", the 
webcam does not work.
2. journalctl.log attached when accessing framatalk.org and creating a room.

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635525/+files/journalctl.log

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

** Tags added: snap

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

** Attachment added: "chromium_hwacc_no_webcam_google_meet.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635474/+files/chromium_hwacc_no_webcam_google_meet.log

** Description changed:

  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).
  
  However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc
  branch), the same test does not work.
  
  The only difference between the two in `snap connections chromium` is
  
  content   chromium:va-driver-non-free -
  -
  
  Test:
  
  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera
  
  Expected result:
  
  Image from camera is displayed on screen
  
  Actual result:
  
  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").
  
  In the settings, I can see the camera name ("UVC Camera (046d:0802)").
  
  Attached are two logs:
  
  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.
+ 
+ 
+ Configuration information
+ =
+ 
+ - Desktop with AMD GPU RX580
+ - Ubuntu 20.04 (kernel 5.15.0-56-generic)
+ - Webcam: 046d:0802 Logitech, Inc. Webcam C200
+ - Headset: 046d:0a38 Logitech, Inc. Headset H340

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

** Attachment added: "chromium_hwacc_no_webcam_framatalk.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635473/+files/chromium_hwacc_no_webcam_framatalk.log

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] [NEW] Webcam does not work with v107.0.5304.121-hwacc

[Pierre Equoy]

Public bug reported:

With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc
branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content   chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

- One retrieved by launching Chromium with `chromium --enable-logging=stderr`, 
accessing framatalk.org and clicking on "Create a room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Assignee: Nathan Teodosio (nteodosio)
 Status: New

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967456

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

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478

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

Status in firefox package in Ubuntu:
  New

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478

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

Status in firefox package in Ubuntu:
  New

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478

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

Status in firefox package in Ubuntu:
  New

Bug description:
  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: 

[Desktop-packages] [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 Desktop
Packages, which is subscribed to mutter in 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

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  This is on my weird desktop setup, with one monitor plugged into an
  AMD card and one into an NVIDIA card.

  When using the Wayland session, by default Shell will come up on the
  monitor connected to the AMD card, and the second (NVIDIA) monitor
  will be blank. Attempting to enable the second monitor in Display
  Settings will immediately and reproducibly crash gnome-shell.

  This is trivial for me to reproduce, so if you need patches tested I
  can easily do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 
5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2
  Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 09:37:51 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-11-02 (125 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in 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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in 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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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 

[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967448

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

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  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' 

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

[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1959362

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

Status in OEM Priority Project:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1959362

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

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1959362

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

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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)

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1959362

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

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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 

[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1924681

Title:
  black screen after boot system

Status in xorg-server package in Ubuntu:
  New

Bug description:
  system shows black screen after cold boot / warm boot.

  [Steps to reproduce]
  1) power off system
  2) power on system

  [Actual result]
  system shows black screen after boot
  system can login after switch text-mode to tty3 (pressing Ctrl+Alt+F3) then 
switch back tty1.

  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  Codename: hirsute
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ uname -r
  5.11.0-14-generic
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ prime-select query
  nvidia
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ 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.

  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 14:17:03 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:8736]
   NVIDIA Corporation TU104M [GeForce RTX 2080 SUPER Mobile / Max-Q] 
[10de:1e93] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104M [GeForce RTX 2080 SUPER Mobile / 
Max-Q] [103c:8736]
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: HP HP ZBook Studio G7 Mobile Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=e0dae7fa-accc-4dd8-b69d-6f09b94df1a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: S91 Ver. 01.04.01
  dmi.board.name: 8736
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.41.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.65
  dmi.modalias: 
dmi:bvnHP:bvrS91Ver.01.04.01:bd01/05/2021:br4.1:efr20.65:svnHP:pnHPZBookStudioG7MobileWorkstation:pvr:rvnHP:rn8736:rvrKBCVersion14.41.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: 

[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-control-center in 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.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/968213

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

Status in GNOME Shell:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Several apps in the default Ubuntu 17.04 or 17.10 install have
  Ellipses when shown in GNOME Shell's Activities Overview.

  This was made worse by switching GNOME Shell to use the Ubuntu font
  because the Ubuntu font is a bit wider than GNOME's default Cantarell
  font so some apps that didn't require ellipses in 17.04 require them
  now in 17.10 Alpha.

  The upstream GNOME bug proposes that apps names be allowed to use 2
  lines. This is similar to what the Settings app (gnome-control-center)
  does.

  This is also really bad for languages that use more characters than
  English.

  Original Bug Title
  --
  Gnome Shell Activities Overview should show full names on mouse hover

  Original Bug Report
  ---
  The title says it all --- especially when choosing recent documents, if they 
start with the same say 12 or 14 letters, it's impossible to differentiate them 
 (see attached screenshot).

  When mouse is hovering an icon, the full name of the
  application/document should be shown.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1871536

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

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  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)

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1871536

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

Status in gnome-software package in Ubuntu:
  New

Bug description:
  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)

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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.

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  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: 

[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1870184

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

Status in snap-store:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  Invalid
Status in gnome-tweaks package in Ubuntu:
  Invalid

Bug description:
  OS : Ubuntu 20.04 (20200401)
  Problem : repository (apt) apps are not showing

  Problem Simulation:
  Install ubuntu 20.04 current daily build > open Snap Store> Search 
gnome tweak (or anyother apt apps) > no results

  Expected Solution:
  The Snap store should show repository apps or the gnome software 
should have installed by default.
  Thank you

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

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

I filed an issue upstream:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

** Bug watch added: PulseAudio #832
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503
  
  Steps to reproduce:
  
- 1. Go to Bluetooth settings panel
- 2. Pair a BT device
- 3. Make sure it's marked as Connected, and go to the Sound settings
- 4. Make sure it's the one selected as "Output device"
- 5. Click "Test"
+ 1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
+ 2. Make sure it's the one selected as "Output device"
+ 3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
- 6. Select "Speakers - Built-in Audio" as Output device and click "Test"
+ 4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
- 7. Try to switch back to the BT device and click Test
- -> same result as in step 5
+ 5. Try to switch back to the BT device and click Test
+ -> same result as in step 3
  
- Tested with 2 different BT devices (one headset and one speaker)
+ Tested with 2 different BT devices (one headset and one speaker) as well
+ as a USB audio interface (Zoom H2N microphone).
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
  
  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output from
  the internal laptop speakers, even when the BT device is selected in the
  Sound settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
+ Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3
  
  Tested with 2 different BT devices (one headset and one speaker) as well
  as a USB audio interface (Zoom H2N microphone).
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
  
  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output from
  the internal laptop speakers, even when the BT device is selected in the
  Sound settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Summary changed:

- [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options 
but the sound keeps being emitted from the internal laptop speaker
+ [Dell Inspiron 7370] shows up in the sound output options but the sound keeps 
being emitted from the internal laptop speaker

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

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

Daniel,

this bug is not a duplicate of lp:1850766. In lp:1850766, selecting the
output device back and forth is an enough workaround to make it work.
Here, doing so doesn't do anything, and the only workaround I found is
by manually switching the sink-inputs as I described in comment #7.

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

Title:
  [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
  options but the sound keeps being emitted from the internal laptop
  speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5
  
  Tested with 2 different BT devices (one headset and one speaker)
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
+ 
+ I was previously using 19.04 and 19.10 on this device and never
+ experienced this kind of issue.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
  
  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output from
  the internal laptop speakers, even when the BT device is selected in the
  Sound settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

Title:
  [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
  options but the sound keeps being emitted from the internal laptop
  speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: 

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

Thanks a lot for the input, Ken!

You were right, it is not related to BT, but to the sound devices being
added and removed.

I happend to have a Zoom microphone that can be connected as USB and
creates a new audio interface (both input and output). Here are my new
tests and findings:

1. Plug the Zoom USB device
-> it appears in the Sound Settings Output Device and is automatically selected
2. Press Test and check the sound output
-> the sound outputs on the internal speakers (NOK)

After some investigation using pactl, I found how to fix the issue, for
both the USB audio interface and the Bluetooth speaker:

1. Make sure the audio interface you want is connected (in my case, I
connected both the USB and the Bluetooth speaker):

$ pactl list short sinks
1   alsa_output.pci-_00_1f.3.analog-stereo  module-alsa-card.c  
s16le 2ch 48000Hz   SUSPENDED
6   alsa_output.usb-ZOOM_Corporation_H2n_-00.iec958-stereo  
module-alsa-card.c  s16le 2ch 44100Hz   SUSPENDED
7   bluez_sink.88_C6_26_1A_9E_AF.a2dp_sink  module-bluez5-device.c  s16le 
2ch 44100Hz   SUSPENDED

2. Play an audio stream, for instance a Youtube video. The output should
come from the internal speakers, and can be seen in pactl as well:

$ pactl list short sink-inputs
10  1   16  protocol-native.c   float32le 2ch 44100Hz

3. Ask pactl to move the stream to the desired sink (output); for
instance, the Bluetooth speaker:

$ pactl move-sink-input 10 7

-> The sound outputs to the Bluetooth device! \o/

However, going back to Sound Settings (where the "Output Device" shows
my Bluetooth Speaker) and clicking Test still outputs to the internal
speakers


Do you think it could be a GNOME issue? What should I do next?


** Summary changed:

- After connecting a Bluetooth headset or speaker, it shows up in the sound 
output options but the sound keeps being emitted from the internal laptop 
speaker
+ After connecting an external output device (USB audio interface, Bluetooth 
speaker...), it shows up in the sound output options but the sound keeps being 
emitted from the internal laptop speaker

** Tags removed: a2dp

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

Title:
  After connecting an external output device (USB audio interface,
  Bluetooth speaker...), it shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Tags added: ce-qa-concern rls-ff-incoming

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] [NEW] After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

Public bug reported:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the Sound settings
4. Make sure it's the one selected as "Output device"
5. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
6. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
7. Try to switch back to the BT device and click Test
-> same result as in step 5

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the BT
device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pieq   1566 F pulseaudio
 /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
 /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present 

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Attachment added: "pactl_list_after_bt_speaker_connected.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333856/+files/pactl_list_after_bt_speaker_connected.log

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
+ Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
- -> the test sound outputs from the internal laptop speakers (NOK)
+ -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
- -> the test sound outputs from the internal laptop speakers (OK)
+ -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
- -> same result as in step 5
+ -> same result as in step 5
  
  Tested with 2 different BT devices (one headset and one speaker)
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pieq   1566 F pulseaudio
-  /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pieq   1566 F pulseaudio
+  /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5
  
  Tested with 2 different BT devices (one headset and one speaker)
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
+ 
+ I tried to reboot the device, and also to suspend/resume, but in each
+ case, the BT device can connect back, but the sound is still output from
+ the internal laptop speakers, even when the BT device is selected in the
+ Sound settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Attachment added: "btmon_bt_speaker.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333852/+files/btmon_bt_speaker.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Attachment added: "btmon_pair_headset.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333853/+files/btmon_pair_headset.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Pierre Equoy]

** Attachment added: "pactl_list_after_bt_headset_paired_and_connected.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333854/+files/pactl_list_after_bt_headset_paired_and_connected.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Pierre Equoy]

** Attachment added: 
"pactl_list_before_switching_output_device_back_and_forth.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Pierre Equoy]

I ran the following steps:

1. Power laptop on with bluetooth turned off
2. Turn BT on in gnome settings and set my BT headphones in pairing mode
3. Pair the headphones.
4. In Sound settings, it looks like the selected device is the BT headphones, 
but if I play something it outputs on the laptop speakers.

output of `pactl list` gives something interesting though:

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 30421 /  46% / -20.00 dB,   front-right: 30421 /  
46% / -20.00 dB
balance 0.00
Base Volume: 6554 /  10% / -60.00 dB
Monitor of Sink: n/a
Latency: 123 usec, configured 4 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC3254 Analog"
alsa.id = "ALC3254 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd1128000 irq 128"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9d71"
device.product.name = "Sunrise Point-LP HD Audio"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC3254"
alsa.components = "HDA:10ec0295,102807e9,0012 
HDA:8086280b,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-input-internal-mic: Internal Microphone (priority: 8900)
analog-input-headphone-mic: Microphone (priority: 8700, not 
available)
analog-input-headset-mic: Headset Microphone (priority: 8800, 
not available)
Active Port: analog-input-internal-mic
Formats:
pcm

Source #2
State: SUSPENDED
Name: bluez_sink.E3_28_E9_21_94_78.a2dp_sink.monitor
Description: Monitor of TaoTronics TT-BH07
Driver: module-bluez5-device.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 25
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: bluez_sink.E3_28_E9_21_94_78.a2dp_sink
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of TaoTronics TT-BH07"
device.class = "monitor"
device.string = "E3:28:E9:21:94:78"
device.api = "bluez"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_E3_28_E9_21_94_78"
bluez.class = "0x240404"
bluez.alias = "TaoTronics TT-BH07"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Formats:
pcm


This matches what I have, but not what I see in Sound settings.

5. Now, if I select the speakers as the output device in the sound
settings, then back to BT device, the sound is correctly output to the
BT headphones (and not the laptop speakers), and I see this in `pactl
list`:

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 30421 /  46% / -20.00 dB,   front-right: 30421 /  
46% / -20.00 dB
   

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Pierre Equoy]

** Attachment added: 
"pactl_list_after_switching_output_device_back_and_forth.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1850766] [NEW] Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Pierre Equoy]

Public bug reported:

Ubuntu 19.10 (using -proposed pocket)
Kernel 5.3.0-21-generic #22
pulseaudio 1:13.0-1ubuntu1
bluez 5.50-0ubuntu4

Device: Dell Inspiron 7370

Step to reproduce
=

1. Pair a bluetooth headset with the laptop
2. Go to sound settings
  -> in "Output device", the bluetooth headset is selected
3. Click Test, then "Front Left" and/or "Front Right"
  -> the sound outputs to the laptop speakers instead of the bluetooth headset

If I select "Speakers - Built-in audio" in the "Output device", then
select back the bluetooth headset from the "Output device" list and test
it, it works as expected.

I tried this with 2 different bluetooth headsets (UE Boom and TaoTronics
TT-BH07) which work fine on an Android device.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
Uname: Linux 5.3.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pieq   1532 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 31 17:36:10 2019
InstallationDate: Installed on 2019-07-02 (121 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug ce-qa-concern eoan ubuntu-certified wayland-session

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1845602] Re: Initial setup screen has thick white borders

[Pierre Equoy]

I installed the final image on this device a couple of times and could
not reproduce the issue.

Marking this as Invalid.

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => Invalid

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

Title:
  Initial setup screen has thick white borders

Status in gnome-initial-setup package in Ubuntu:
  Invalid

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  The initial setup screen has thick white borders. Other windows do
  not. See attached screenshot.

  Note that the screen scaling is automatically set to 200%.

  If I remove the file ~/.config/gnome-initial-setup-done and log out
  from my session then back in, the window appears again, but it looks
  normal (no thick white borders).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-initial-setup 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:15:57 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

Upstream issue opened here: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1736

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1736
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1736

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

Update: I can reproduce this also on the "Ubuntu on Wayland" session:

1. Open gedit and position the window somewhere in the middle-bottom of the 
screen
2. Swipe the touchscreen up to open OSK
3. Press the arrow down key on the OSK to hide the keyboard.
→ sometimes, two black rectangles remain on the sides (similar to the ones 
shown in osk-login.jpg)

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

@Daniel, I couldn't reproduce this issue on Wayland. However, I can
reproduce it in the login screen (see attached snapshot).

** Attachment added: "osk-login.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845623/+attachment/5292981/+files/osk-login.jpg

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

$ sudo lshw -C video
  *-display 
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   logical name: /dev/fb0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
   configuration: depth=32 driver=i915 latency=0 mode=3840x2160 
visual=truecolor xres=3840 yres=2160
   resources: iomemory:600-5ff iomemory:400-3ff irq:150 
memory:604a00-604aff memory:40-400fff ioport:3000(size=64) 
memory:c-d

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

** Attachment added: "osk-issue.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845623/+attachment/5291740/+files/osk-issue.mp4

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845623] [NEW] on screen keyboard leaves dark marks on screen after being hidden

[Pierre Equoy]

Public bug reported:

Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)

Steps to reproduce:
1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
2. Tap the arrow down key to hide the OSK

Expected result: the OSK disappears

Actual result: The OSK leaves dark traces on the sides of the screen.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 17:51:29 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-09-27 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ce-qa-concern eoan

** Tags added: ce-qa-concern

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845602] [NEW] Initial setup screen has thick white borders

[Pierre Equoy]

Public bug reported:

Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)

The initial setup screen has thick white borders. Other windows do not.
See attached screenshot.

Note that the screen scaling is automatically set to 200%.

If I remove the file ~/.config/gnome-initial-setup-done and log out from
my session then back in, the window appears again, but it looks normal
(no thick white borders).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-initial-setup 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 15:15:57 2019
InstallationDate: Installed on 2019-09-27 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ce-qa-concern eoan

** Attachment added: "initial-setup-window-border.png"
   
https://bugs.launchpad.net/bugs/1845602/+attachment/5291698/+files/initial-setup-window-border.png

** Description changed:

+ Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
+ Device: Dell XPS 13 7390 (201908-27305)
+ 
  The initial setup screen has thick white borders. Other windows do not.
  See attached screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-initial-setup 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:15:57 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Initial setup screen has thick white borders

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  The initial setup screen has thick white borders. Other windows do
  not. See attached screenshot.

  Note that the screen scaling is automatically set to 200%.

  If I remove the file ~/.config/gnome-initial-setup-done and log out
  from my session then back in, the window appears again, but it looks
  normal (no thick white borders).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-initial-setup 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:15:57 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845601] Re: Images blurry in Background selection screen when scaling > 100%

[Pierre Equoy]

** Attachment added: "scaling200.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845601/+attachment/5291695/+files/scaling200.png

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

Title:
  Images blurry in Background selection screen when scaling > 100%

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

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:

  0. Go to Settings > Devices > Displays and make sure the scaling is 200% or 
more
  1. Go to Settings > Background

  Expected result:

  1. The thumbnails for the suggested backgrounds are sharp

  Actual result:

  1. The thumbnails are blurry.

  I attached 3 screenshots of the Background screen at different scales
  (100%, 200%, 300%).

  This is a problem for people with UHD (4K) screens which are likely to
  select a 200% scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:03:35 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845601] Re: Images blurry in Background selection screen when scaling > 100%

[Pierre Equoy]

** Attachment added: "scaling300.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845601/+attachment/5291696/+files/scaling300.png

** Description changed:

- Image: 19.10 beta (20190926.1)
- Device: XPS 13 7390
+ Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
+ Device: Dell XPS 13 7390 (201908-27305)
  
  Steps to reproduce:
  
  0. Go to Settings > Devices > Displays and make sure the scaling is 200% or 
more
  1. Go to Settings > Background
  
  Expected result:
  
  1. The thumbnails for the suggested backgrounds are sharp
  
  Actual result:
  
  1. The thumbnails are blurry.
  
  I attached 3 screenshots of the Background screen at different scales
  (100%, 200%, 300%).
  
  This is a problem for people with UHD (4K) screens which are likely to
  select a 200% scaling.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:03:35 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Images blurry in Background selection screen when scaling > 100%

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

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:

  0. Go to Settings > Devices > Displays and make sure the scaling is 200% or 
more
  1. Go to Settings > Background

  Expected result:

  1. The thumbnails for the suggested backgrounds are sharp

  Actual result:

  1. The thumbnails are blurry.

  I attached 3 screenshots of the Background screen at different scales
  (100%, 200%, 300%).

  This is a problem for people with UHD (4K) screens which are likely to
  select a 200% scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:03:35 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845601] [NEW] Images blurry in Background selection screen when scaling > 100%

[Pierre Equoy]

Public bug reported:

Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)

Steps to reproduce:

0. Go to Settings > Devices > Displays and make sure the scaling is 200% or more
1. Go to Settings > Background

Expected result:

1. The thumbnails for the suggested backgrounds are sharp

Actual result:

1. The thumbnails are blurry.

I attached 3 screenshots of the Background screen at different scales
(100%, 200%, 300%).

This is a problem for people with UHD (4K) screens which are likely to
select a 200% scaling.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 15:03:35 2019
InstallationDate: Installed on 2019-09-27 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ce-qa-concern eoan

** Attachment added: "scaling100.png"
   
https://bugs.launchpad.net/bugs/1845601/+attachment/5291691/+files/scaling100.png

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

Title:
  Images blurry in Background selection screen when scaling > 100%

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

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:

  0. Go to Settings > Devices > Displays and make sure the scaling is 200% or 
more
  1. Go to Settings > Background

  Expected result:

  1. The thumbnails for the suggested backgrounds are sharp

  Actual result:

  1. The thumbnails are blurry.

  I attached 3 screenshots of the Background screen at different scales
  (100%, 200%, 300%).

  This is a problem for people with UHD (4K) screens which are likely to
  select a 200% scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 15:03:35 2019
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

[Pierre Equoy]

@Daniel

4/5. I collected the attached drminfo.txt while at login screen.

While in tty4, I noticed that the computer would freeze for more or less
long periods of time because of some nouveau-related kernel messages
that were printed on the screen. I managed to type the command you
mentioned between two freeze periods.

Hope this helps. Let me know if you need additional info!

** Attachment added: "drminfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+attachment/5250116/+files/drminfo.txt

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

[Pierre Equoy]

1/2/3. I made a fresh install.

On the first boot, device was blocked at the "Ubuntu" logo with the dots
blinking white and orange forever. Pressing Esc wouldn't do anything
(it's supposed to show the boot process) and pressing NumLock on the
numpad wouldn't light the NumLock LED (it's my to-go check to see if the
system froze or not).

I force-shutdown it, started again, this time it showed me the login
screen, I logged in and it remained on a dark purple screen with a black
mouse cursor for about 1-2 minutes before finally displaying the OOBE
screen (where you have to press Next and select if you want to send
anonymous report etc.).

I then typed `journalctl -b-1 > prevboot.txt`, this is the file attached
to this comment. Apologies as the locale is set to Chinese because my
timezone is Taipei.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+attachment/5250111/+files/prevboot.txt

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  

[Desktop-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

[Pierre Equoy]

To see a sample of dmesg when nouveau is activated, please refer to
lp:1822026

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  New

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1822047] [NEW] After install, cannot boot into system unless I use nomodeset kernel parameter

[Pierre Equoy]

Public bug reported:

System: Disco (19.04 beta)
Hardware: Dell Precision 7530

After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.

Steps to reproduce:

1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

Expected result:

2. The system boots and user can log in and see Gnome interface.

Actual result:

2. The first time, I could log into the system. However, when I tried to
access the Settings screen, the system froze. After that, everytime I
tried to boot the device, the screen was filled with dark purple, a
mouse cursor may appear, but nothing else would happen. At that stage,
the only thing I could do was to force shutdown the device, start it
again and at Grub screen, press `e` to edit the kernel parameters and
add `nomodeset`.

This bug is created from the actual device, using `nomodeset` kernel
parameter. `nouveau` graphics driver is most likely the culprit, like in
all the previous issues that have been raised (see lp:1822026,
lp:1822044, lp:1821882)

Two workarounds exist:

1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
2. During installation, install third party drivers. If Secure Boot is enabled, 
this requires to set a password that will be asked when the device reboots.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 15:39:40 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
 NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
InstallationDate: Installed on 2019-03-28 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: Dell Inc. Precision 7530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7530
dmi.product.sku: 0889
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug ce-qa-concern disco rls-dd-incoming ubuntu

** Tags added: ce-qa-concern rls-dd-incoming

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  New

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, 

[Desktop-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

[Pierre Equoy]

** Tags added: ce-qa-concern

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [   

[Desktop-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

[Pierre Equoy]

I tried the same while blacklisting nouveau driver in grub:

$ cat /proc/cmdline
BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

This time, I have "acpi_video0" in /sys/class/backlight, but the result
is the same. The screen is very dark.

/sys/class/backlight/acpi_video0/brightness is 100 by default. I can
modify this value with

$ sudo su
# echo 60 > /sys/class/backlight/acpi_video0/brightness

and the brightness actually changes to something even darker. If I try
to set it over 100, I get:

write error: Invalid argument

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI: Skipping parse 

[Desktop-packages] [Bug 1821882] [NEW] Screen is very dark and brightness cannot be adjusted

[Pierre Equoy]

Public bug reported:

Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the 
nVidia GPU is used.

When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)

There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
intel_backlight):

$ ll /sys/class/backlight/
total 0
drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

Trying to manually change brightness doesn't do anything:

$ sudo su
root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
root@ubuntu:/sys/class/backlight/nv_backlight# ll
total 0
drwxr-xr-x 3 root root0 Mar 27 09:28 ./
drwxr-xr-x 4 root root0 Mar 27 09:28 ../
-r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
-rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
-rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
-r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
drwxr-xr-x 2 root root0 Mar 27 09:28 power/
lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
-r--r--r-- 1 root root 4096 Mar 27 09:28 type
-rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
50

Although the value is changed, the screen brightness doesn't change.

in dmesg, I can see the following:

[0.241878] ACPI: Added _OSI(Module Device)
[0.241878] ACPI: Added _OSI(Processor Device)
[0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.241878] ACPI: Added _OSI(Processor Aggregator Device)
[0.241878] ACPI: Added _OSI(Linux-Dell-Video)
[0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288625] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289376] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.289379] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.289381] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289382] ACPI BIOS Error (bug): Failure creating 

[Desktop-packages] [Bug 1606743] Re: Font Viewer desktop file does not launch gnome-font-viewer

[Pierre Equoy]

Exactly the same issue here with Ubuntu 16.04 on two different devices.

I would add that opening gnome-font-viewer from the terminal for a given
font file works too:

gnome-font-viewer font-file.ttf

works as expected.

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

Title:
  Font Viewer desktop file does not launch gnome-font-viewer

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1
  gnome-font-viewer 3.16.2

  What I expect: When I double-click the Font Viewer icon from the Dash
  Applications scope it should launch the Font Viewer.

  What actually happens: It does not. I get the waiting cursor and the
  Font Viewer tile on the launcher for a few seconds and then the tile
  disappears.

  I can go to a terminal and type "gnome-font-viewer" and it runs
  without any issues.

  Here is the content of the desktop file:

  [Desktop Entry]
  Name=Font Viewer
  Comment=View fonts on your system
  Keywords=fonts;fontface;
  Icon=preferences-desktop-font
  Exec=gnome-font-viewer %u
  Terminal=false
  Type=Application
  DBusActivatable=true
  StartupNotify=true
  Categories=GTK;GNOME;Utility;X-GNOME-Utilities;
  
MimeType=application/x-font-ttf;application/x-font-pcf;application/x-font-type1;application/x-font-otf;
  X-GNOME-Bugzilla-Bugzilla=GNOME
  X-GNOME-Bugzilla-Product=gnome-font-viewer
  X-GNOME-Bugzilla-Component=general
  X-GNOME-Bugzilla-OtherBinaries=gnome-thumbnail-font
  X-GNOME-Bugzilla-Version=3.16.2
  X-Ubuntu-Gettext-Domain=gnome-font-viewer

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

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

[Desktop-packages] [Bug 1588266] [NEW] Almost no info about Krita snap in Ubuntu Software

[Pierre Equoy]

Public bug reported:

Krita 3.0 was released [1] and it was packaged as a snap which is
available in Ubuntu Software.

However, when a user looks for "krita" in Ubuntu Software, (s)he will
find one package without an icon, without screenshots, without user
reviews... and with a scary "non-free" warning box. See attached
screenshot.

Krita has been around for a while and the previous versions were
available in the repo, so I'm sure there used to be an icon, some user
reviews and probably some screenshots as well :)


[1] https://krita.org/item/krita-3-0-released/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_4_0_22_40_generic_7
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jun  2 18:00:34 2016
InstallationDate: Installed on 2016-04-25 (38 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "krita_ubuntu_software.png"
   
https://bugs.launchpad.net/bugs/1588266/+attachment/4675102/+files/krita_ubuntu_software.png

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

Title:
  Almost no info about Krita snap in Ubuntu Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Krita 3.0 was released [1] and it was packaged as a snap which is
  available in Ubuntu Software.

  However, when a user looks for "krita" in Ubuntu Software, (s)he will
  find one package without an icon, without screenshots, without user
  reviews... and with a scary "non-free" warning box. See attached
  screenshot.

  Krita has been around for a while and the previous versions were
  available in the repo, so I'm sure there used to be an icon, some user
  reviews and probably some screenshots as well :)

  
  [1] https://krita.org/item/krita-3-0-released/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_4_0_22_40_generic_7
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun  2 18:00:34 2016
  InstallationDate: Installed on 2016-04-25 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1493722] Re: [Media services] Volume up/down long press should skip to next/previous track

[Pierre Equoy]

Hi Peter,

when I raised this issue, the rationale behind it was to be able to
control the music from my pocket without having to take the smartphone
out of my pocket. This is the method I use in the bus with my current
Android phone for instance, and it's incredibly useful.

Shaking the phone is, in my humble opinion, a very bad idea. Plus, my
request is for the long press to be globally recognized, i.e. no matter
the phone screen is off or not. If we apply a gesture, that means your
playlist would randomly go to next/previous track as you walk...

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

Title:
  [Media services] Volume up/down long press should skip to
  next/previous track

Status in Canonical System Image:
  Confirmed
Status in Media Hub:
  Invalid
Status in Ubuntu Music App:
  New
Status in Ubuntu UX:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A handy feature of music players is the ability to quickly skip tracks
  by long-pressing the volume buttons. This allows users to control
  their music without having to take the device out of their pocket,
  turn its screen on, unlock it, go to the music app and press "Next".

  As of now, when I long press the volume button, it rapidly increases
  the volume, which is not very nice to my ears ;-)

  Is it possible to control the music app this way on Ubuntu phone?

  Music app version tested: 2.2.910 (2015-09-03)
  Device: Meizu MX 4
  System info: Ubuntu 15.04 (r4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493722/+subscriptions

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

[Desktop-packages] [Bug 1493722] Re: [Media services] Volume up/down long press should skip to next/previous track

[Pierre Equoy]

Well, the situations in which the Volume key is maintained are pretty
rare in my experience (and I keep my device in my pocket all day long).

I filed this issue specifically to address the skip to next/previous
track without having to turn the device screen on and going in the music
app to finally press a button.

If other people think we should have an issue for the "rapid volume
increase", I can raise a separate issue for this.

I still hope this current feature request can be address, though :)

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

Title:
  [Media services] Volume up/down long press should skip to
  next/previous track

Status in Canonical System Image:
  New
Status in Media Hub:
  Invalid
Status in Ubuntu Music App:
  New
Status in Ubuntu UX:
  Triaged
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A handy feature of music players is the ability to quickly skip tracks
  by long-pressing the volume buttons. This allows users to control
  their music without having to take the device out of their pocket,
  turn its screen on, unlock it, go to the music app and press "Next".

  As of now, when I long press the volume button, it rapidly increases
  the volume, which is not very nice to my ears ;-)

  Is it possible to control the music app this way on Ubuntu phone?

  Music app version tested: 2.2.910 (2015-09-03)
  Device: Meizu MX 4
  System info: Ubuntu 15.04 (r4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493722/+subscriptions

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

[Desktop-packages] [Bug 1493722] Re: Volume up/down long press should skip to next/previous track

[Pierre Equoy]

Hi Victor,

thanks for your quick answer :)

I agree with you about the long press quickly increasing the volume.
When you have in-ear earphones, it's really terrible for your ears!

As for the "skip track" feature, it's been a pet peeve for a lot of
Android users. On some phones it's implemented by default, on some
others it's the same anti-feature of "rapidly increasing volume".

On Android, some developers tackled the issue and created the Xposed
framework [1] that allows to control lower layers of Android more
easily. Thanks to this, a module called  Physical Button Music Control
[2] has been created that answers exactly this problem: you can control
very precisely your music with shortcuts you define. I think this is a
bit overkill, as I just want a ~300ms press on volume up/down key to
skip to next/previous track.

Hope this helps :)


[1] http://repo.xposed.info/module/de.robv.android.xposed.installer
[2] http://repo.xposed.info/module/xeed.xposed.cbppmod

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

Title:
  Volume up/down long press should skip to next/previous track

Status in Canonical System Image:
  New
Status in Media Hub:
  Invalid
Status in Ubuntu Music App:
  New
Status in Ubuntu UX:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A handy feature of music players is the ability to quickly skip tracks
  by long-pressing the volume buttons. This allows users to control
  their music without having to take the device out of their pocket,
  turn its screen on, unlock it, go to the music app and press "Next".

  As of now, when I long press the volume button, it rapidly increases
  the volume, which is not very nice to my ears ;-)

  Is it possible to control the music app this way on Ubuntu phone?

  Music app version tested: 2.2.910 (2015-09-03)
  Device: Meizu MX 4
  System info: Ubuntu 15.04 (r4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493722/+subscriptions

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

[Desktop-packages] [Bug 1431714] [NEW] [xorg-edgers] Held broken packages (libgbm1) from Xorg-edgers PPA

[Pierre Equoy]

Public bug reported:

My laptop (Aspire VN7-591G) comes with an nVidia graphic card that is
not supported by default in Ubuntu Trusty (14.04.2, amd64).

I installed the Xorg-edgers PPA to be able to install nvidia-340 which
contains the proper drivers for my card (and allow me to switch between
the Intel and the nVidia GPU).

Later, I realized there is a dependency issue with package libgbm1:

sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libgbm1
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Using aptitude to have more information, I get this:

--\ Packages being automatically held in their current state (1)
i A  libgbm1
10.1.3-0ubuntu 10.6.0~git2015

libgbm1 will not be upgraded to version 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~trusty, to avoid breaking the 
following dependencies:
  * libgbm1 replaces libgbm1:i386 ( 10.1.3-0ubuntu0.3)

It appears that this package is used by the xorg-edgers PPA:

% apt-cache policy libgbm1
libgbm1:
  Installed: 10.1.3-0ubuntu0.3
  Candidate: 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~trusty
  Version table:
 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~trusty 0
500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ trusty/main amd64 
Packages
 *** 10.1.3-0ubuntu0.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 10.1.0-4ubuntu5 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

I tried to force-install package libgbm1 but get the following error:

sudo apt-get install libgbm1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgbm1 : Depends: libgl1-mesa-dri (= 
10.6.0~git20150310.5750595c-0ubuntu0ricotz3~trusty)
E: Unable to correct problems, you have held broken packages.

What can I do to fix this?

Thanks in advance!


P.S.: This issue was reported on askubuntu [1] but I didn't get any feedback.

[1] http://askubuntu.com/questions/595461/held-broken-packages-libgbm1
-from-xorg-edgers-ppa

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar 13 15:55:01 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.16.0-31-generic, x86_64: installed
 nvidia-340, 340.76, 3.16.0-31-generic, x86_64: installed
 nvidia-340-uvm, 340.76, 3.16.0-31-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0926]
InstallationDate: Installed on 2015-03-02 (10 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Acer Aspire VN7-591G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=34c5f558-cdcb-4f13-980e-41873de8a019 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-591G
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: V1.08
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08:
dmi.product.name: Aspire VN7-591G
dmi.product.version: V1.08
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A

[Desktop-packages] [Bug 1431128] [NEW] screen remains blank after waking up from suspend

[Pierre Equoy]

Public bug reported:

Steps:
1. Suspend the computer by pressing the Sleep key
2. Press any key on the keyboard or the Power button to wake the device up

Expected results:
1. The system suspends and the Power button LED blinks
2. The system wakes up and user can log in.

Actual results:
1. The system suspends and the Power button LED blinks (OK)
2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

Additional information:

- In a few additional occasions, after performing this action several
times (pressing the Sleep key to suspend the system, then wake it up),
the system freezes at log in screen just before going to suspend mode.
It has to be force-stopped and restarted.

- Please note that this problem does NOT happen when suspending from the
User Menu or using the Power button and selecting Suspend.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Thu Mar 12 11:19:32 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
InstallationDate: Installed on 2015-02-10 (29 days ago)
InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150205-07:08
LightdmConfig:
 [SeatDefaults]
 autologin-guest=false
 autologin-user-timeout=0
 autologin-session=lightdm-autologin
 #autologin-user=u
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: oem-priority/trusty
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  screen remains blank after waking up from suspend

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1413035] [NEW] Cannot launch Ubuntu Software Center

[Pierre Equoy]

Public bug reported:

When I try to open the Ubuntu Software Center, the icon blinks for a few
seconds then stops, and nothing happens.

When I try to launch it using the command line, I have the following
error:

% software-center
2015-01-21 09:52:46,360 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 
'None'
Traceback (most recent call last):
  File /usr/bin/software-center, line 130, in module
app = SoftwareCenterAppGtk3(options, args)
  File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 397, in 
__init__
self.icons)
  File 
/usr/share/software-center/softwarecenter/ui/gtk3/panes/installedpane.py, 
line 95, in __init__
CategoriesParser.__init__(self, db)
  File /usr/share/software-center/softwarecenter/db/categories.py, line 251, 
in __init__
self._build_string_template_dict()
  File /usr/share/software-center/softwarecenter/db/categories.py, line 303, 
in _build_string_template_dict
region = %s % get_region_cached()[countrycode]
KeyError: 'countrycode'

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: software-center 13.10-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 21 09:48:52 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-15 (66 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Cannot launch Ubuntu Software Center

Status in software-center package in Ubuntu:
  New

Bug description:
  When I try to open the Ubuntu Software Center, the icon blinks for a
  few seconds then stops, and nothing happens.

  When I try to launch it using the command line, I have the following
  error:

  % software-center
  2015-01-21 09:52:46,360 - softwarecenter.ui.gtk3.app - INFO - setting up 
proxy 'None'
  Traceback (most recent call last):
File /usr/bin/software-center, line 130, in module
  app = SoftwareCenterAppGtk3(options, args)
File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 397, 
in __init__
  self.icons)
File 
/usr/share/software-center/softwarecenter/ui/gtk3/panes/installedpane.py, 
line 95, in __init__
  CategoriesParser.__init__(self, db)
File /usr/share/software-center/softwarecenter/db/categories.py, line 
251, in __init__
  self._build_string_template_dict()
File /usr/share/software-center/softwarecenter/db/categories.py, line 
303, in _build_string_template_dict
  region = %s % get_region_cached()[countrycode]
  KeyError: 'countrycode'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 21 09:48:52 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-15 (66 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 896595] Re: Ubuntu does not remember LID brightness

[Pierre Equoy]

The problem still happens with Ubuntu 14.04.

I'm using an Asus K43SD (Intel® Pentium(R) CPU B970 @ 2.30GHz × 2 and
GeForce 610M/PCIe/SSE2 GPU).

Steps to reproduce:

1. Using Settings  Brightness  Lock (or Brightness Indicator 
https://launchpad.net/~indicator-brightness/+archive/ubuntu/ppa/+packages), 
set the screen brightness to minimum (see attachement for details).
2. Wait until the screen turns off (in my case, 5 minutes).
3. Wake up the screen by moving the mouse/typing on the keyboard
→ the screen brightness is back to 100% (Not OK)
→ Brightness indicator indicates brightness=0
→ Brightness level in Settings is also to the minimum, which is in 
contradiction with the fact that screen brightness is to the max.

If I scroll down on the brightness indicator, the screen will
immediately go to the dimmest brightness.

I hope a solution can be found for this issue! :)

** Attachment added: brightness-settings.png
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/896595/+attachment/4177063/+files/brightness-settings.png

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

Title:
  Ubuntu does not remember LID brightness

Status in Gnome Settings Daemon:
  Unknown
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Baltix:
  Confirmed
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  Everytime I boot Ubuntu (or ArchLInux, but this is a bug report for
  Ubuntu...) screen brightness gets set to maximum. I think it's a
  problem of a kernel, but kernel.org doesn't have a bug report form
  yet, and as far as I know Ubuntu has a little bit patched kernel, so
  maybe someone will create a patch for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: udev 173-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov 26 17:08:38 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: ASUSTeK Computer Inc. K43SJ
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic 
root=UUID=422db72c-3b01-4413-ac35-541447d8f6af ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SJ.210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K43SJ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.210:bd02/16/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43SJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 896595] Re: Ubuntu does not remember LID brightness

[Pierre Equoy]

P.S.: it looks like there was a similar issue in earlier versions of Ubuntu, 
but a fix was released... I don't know if this issue is related:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137598

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

Title:
  Ubuntu does not remember LID brightness

Status in Gnome Settings Daemon:
  Unknown
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Baltix:
  Confirmed
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  Everytime I boot Ubuntu (or ArchLInux, but this is a bug report for
  Ubuntu...) screen brightness gets set to maximum. I think it's a
  problem of a kernel, but kernel.org doesn't have a bug report form
  yet, and as far as I know Ubuntu has a little bit patched kernel, so
  maybe someone will create a patch for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: udev 173-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov 26 17:08:38 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: ASUSTeK Computer Inc. K43SJ
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic 
root=UUID=422db72c-3b01-4413-ac35-541447d8f6af ro quiet splash vt.handoff=7
  SourcePackage: udev
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SJ.210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K43SJ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.210:bd02/16/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43SJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1297903] [NEW] (Traditional Chinese install) main screen mostly in English in Live CD

[Pierre Equoy]

Public bug reported:

Version tested: Ubuntu 14.04 LTS beta1 i386
(http://iso.qa.ubuntu.com/qatracker/milestones/313/builds/65364/downloads)

Using Tradition Chinese install, the first screen showed contains mostly
English (see screenshot attached).

When clicking on the time (top right of the screen), the calendar shown
is in Chinese, and when hovered, some of the icons on the left shows
Chinese characters (for instance the first one to install Ubuntu is in
Chinese), but the other are not (e.g. System Settings).

After launching the installation itself, everything is correctly in
Chinese apart from the timezone detection (Taipei is shown as is
instead of 臺北市 for instance). I'm not sure if this is correct

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


** Tags: trusty

** Attachment added: Screenshot from 2014-03-26 23:11:33.png
   
https://bugs.launchpad.net/bugs/1297903/+attachment/4045065/+files/Screenshot%20from%202014-03-26%2023%3A11%3A33.png

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

Title:
  (Traditional Chinese install) main screen mostly in English in Live CD

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Version tested: Ubuntu 14.04 LTS beta1 i386
  (http://iso.qa.ubuntu.com/qatracker/milestones/313/builds/65364/downloads)

  Using Tradition Chinese install, the first screen showed contains
  mostly English (see screenshot attached).

  When clicking on the time (top right of the screen), the calendar
  shown is in Chinese, and when hovered, some of the icons on the left
  shows Chinese characters (for instance the first one to install Ubuntu
  is in Chinese), but the other are not (e.g. System Settings).

  After launching the installation itself, everything is correctly in
  Chinese apart from the timezone detection (Taipei is shown as is
  instead of 臺北市 for instance). I'm not sure if this is correct

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

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

[Desktop-packages] [Bug 1297907] [NEW] (Traditional Chinese install) after install, freeze during shutdown/restart process

[Pierre Equoy]

Public bug reported:

While testing Ubuntu 14.04 LTS beta1
(http://iso.qa.ubuntu.com/qatracker/milestones/313/builds/65364/downloads)
in Virtualbox:

Step 1 - 10 OK
Step 11. Once the installer has finished click the Restart now button.
Step 12. Remove the disc and press Enter.
- Not OK: the installation process freezes before and never ask me to remove 
the CD and press Enter. (see attached screenshot)
Earlier today, I installed the English version successfully with the same ISO 
and saw the text asking me to remove the CD and press Enter (and once done, the 
VM was restarted)

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


** Tags: trusty

** Attachment added: Screenshot from 2014-03-26 22:57:41.png
   
https://bugs.launchpad.net/bugs/1297907/+attachment/4045078/+files/Screenshot%20from%202014-03-26%2022%3A57%3A41.png

** Package changed: ibus (Ubuntu) = ubiquity (Ubuntu)

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

Title:
  (Traditional Chinese install) after install, freeze during
  shutdown/restart process

Status in “ubiquity” package in Ubuntu:
  New

Bug description:
  While testing Ubuntu 14.04 LTS beta1
  (http://iso.qa.ubuntu.com/qatracker/milestones/313/builds/65364/downloads)
  in Virtualbox:

  Step 1 - 10 OK
  Step 11. Once the installer has finished click the Restart now button.
  Step 12. Remove the disc and press Enter.
  - Not OK: the installation process freezes before and never ask me to remove 
the CD and press Enter. (see attached screenshot)
  Earlier today, I installed the English version successfully with the same ISO 
and saw the text asking me to remove the CD and press Enter (and once done, the 
VM was restarted)

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

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