[Desktop-packages] [Bug 1892457] Re: intel graphics installer error

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug. You seem to need support more than have
issues with a bug asking "How can i fix this problem?"

I believe a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu (this bug report can be converted
to a question (which is aimed at support)). You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

I'm going to mark this bug incomplete, as it appears as if you haven't
followed the normal support procedures first. If however you believe I'm
in error, please leave a comment with details and change the status back
to "New".


** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  intel graphics installer error

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I install intel graphics driver using "sudo apt-get install 
xserver-xorg-video-intel" but the system returns a message like this
  "
  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:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.
  "
  How can i fix this problem? Im using Ubuntu 18.04.5 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 21 12:20:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90b8]
  InstallationDate: Installed on 2020-07-25 (26 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Sony Corporation SVF1421QSGB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2ad38f27-457e-4a00-9664-3f2f96b650c0 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0220DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF1421QSGB:pvrC10K9558:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVF1421QSGB
  dmi.product.sku: 54686500
  dmi.product.version: C10K9558
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892457/+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 1892457] [NEW] intel graphics installer error

[phi bien]

Public bug reported:

I install intel graphics driver using "sudo apt-get install 
xserver-xorg-video-intel" but the system returns a message like this
"
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:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.
"
How can i fix this problem? Im using Ubuntu 18.04.5 LTS

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 21 12:20:21 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90b8]
InstallationDate: Installed on 2020-07-25 (26 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: Sony Corporation SVF1421QSGB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2ad38f27-457e-4a00-9664-3f2f96b650c0 ro recovery nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0220DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF1421QSGB:pvrC10K9558:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVF1421QSGB
dmi.product.sku: 54686500
dmi.product.version: C10K9558
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  intel graphics installer error

Status in xorg package in Ubuntu:
  New

Bug description:
  I install intel graphics driver using "sudo apt-get install 
xserver-xorg-video-intel" but the system returns a message like this
  "
  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:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.
  "
  How can i fix this problem? Im using Ubuntu 18.04.5 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 21 12:20:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics 

[Desktop-packages] [Bug 1690719] Re: Mouse (and graphics) randomly pauses/stutters in gnome shell. It's not perfectly smooth.

[Daniel van Vugt]

In progress upstream:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1241

** Changed in: gnome-shell (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Mouse (and graphics) randomly pauses/stutters in gnome shell. It's not
  perfectly smooth.

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland).
  It's not reliably smooth like you would see in Xorg or Mir demo
  servers.

  Feels like there is a blocking call being made in a GUI thread that
  shouldn't have any blocking calls. Although it's not clear if this is
  just a problem with pointer input or the shell compositing in general.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  Date: Mon May 15 13:23:22 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1690719/+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 1880728] Re: [amdgpu] Gnome Shell freeze

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [amdgpu] Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  was logged in through team viewer and got kicked out.  when i was able
  to physically access the machine the screens were on, but was not able
  to move the mouse or interact with the computer.  performed hard
  reboot to get it back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 11:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA 
controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 
[174b:e347]
  InstallationDate: Installed on 2020-05-09 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.LM
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE(MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+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 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

[Launchpad Bug Tracker]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  wayland session hard freezes on login from GDM (X11 session works
  fine)

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │ ├─gsd-power───3*[{gsd-power}]
  │ ├─gsd-print-notif───2*[{gsd-print-notif}]
  │ ├─gsd-printer───2*[{gsd-printer}]
  │ ├─gsd-rfkill───2*[{gsd-rfkill}]
  │ 

[Desktop-packages] [Bug 1884367] Re: The display is flickering

[Launchpad Bug Tracker]

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  The display is flickering

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  For flickering display, I tried to update intel display drivers, and
  this bug report came during the process

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 18:39:54 2020
  DistUpgraded: 2020-06-10 01:24:34,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad]
  InstallationDate: Installed on 2018-01-23 (878 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=5b2de4e2-596a-412f-b22c-5aa72fb9234a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-06-09 (10 days ago)
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Aug 16 15:18:06 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1249 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1884367/+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 1884430] Re: Gnome Shell not responding to mouse clicks (during force quit dialog)

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Gnome Shell not responding to mouse clicks (during force quit dialog)

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Gnome Shell not responding to mouse clicks (during force quit dialog)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:34:08 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884430/+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 1892446] Re: scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia drivers

[JSigma]

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

Thank you for your prompt response,
I'll follow up on bug report 1892440.
Sorry about the duplicate.

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

Title:
  scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia
  drivers

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,

  Update from gir1.2-mutter-6 (3.36.3-0ubuntu0.20.04.1) to
  (3.36.4-0ubuntu0.20.04.2) zoom on fonts, shell and GDM.

  Same problem with kernel 5.8 or nvidia 450.

  The problem does not exist on Wayland with xx.org video.

  I need nvidia drivers and Xorg for the dual screen 4K.

  Thanks for your help

  Config :
  
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04
  CPU: Intel i7-7700HQ (8) @ 3.800GHz 
  GPU: NVIDIA GeForce GTX 1070 Mobile

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gir1.2-mutter-6 3.36.4-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Aug 21 05:20:56 2020
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4 small text in Ubuntu 20.04 with nvidia cards

[Daniel van Vugt]

** Summary changed:

- [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards
+ [focal] [nvidia] Mutter 3.36.4 small text in Ubuntu 20.04 with nvidia cards

** Summary changed:

- [focal] [nvidia] Mutter 3.36.4 small text in Ubuntu 20.04 with nvidia cards
+ [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 
with nvidia cards

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

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

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1892446] Re: scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia drivers

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1892440, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1892440
   [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia 
cards

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

Title:
  scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia
  drivers

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,

  Update from gir1.2-mutter-6 (3.36.3-0ubuntu0.20.04.1) to
  (3.36.4-0ubuntu0.20.04.2) zoom on fonts, shell and GDM.

  Same problem with kernel 5.8 or nvidia 450.

  The problem does not exist on Wayland with xx.org video.

  I need nvidia drivers and Xorg for the dual screen 4K.

  Thanks for your help

  Config :
  
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04
  CPU: Intel i7-7700HQ (8) @ 3.800GHz 
  GPU: NVIDIA GeForce GTX 1070 Mobile

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gir1.2-mutter-6 3.36.4-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Aug 21 05:20:56 2020
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892446/+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 1892446] [NEW] scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia drivers

[Sigma]

Public bug reported:

Hello,

Update from gir1.2-mutter-6 (3.36.3-0ubuntu0.20.04.1) to
(3.36.4-0ubuntu0.20.04.2) zoom on fonts, shell and GDM.

Same problem with kernel 5.8 or nvidia 450.

The problem does not exist on Wayland with xx.org video.

I need nvidia drivers and Xorg for the dual screen 4K.

Thanks for your help

Config :

Description: Ubuntu 20.04.1 LTS
Release: 20.04
CPU: Intel i7-7700HQ (8) @ 3.800GHz 
GPU: NVIDIA GeForce GTX 1070 Mobile

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gir1.2-mutter-6 3.36.4-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Aug 21 05:20:56 2020
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mutter (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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892446

Title:
  scale login GDM and shell with update gir1.2-mutter-6 + xorg + nvidia
  drivers

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,

  Update from gir1.2-mutter-6 (3.36.3-0ubuntu0.20.04.1) to
  (3.36.4-0ubuntu0.20.04.2) zoom on fonts, shell and GDM.

  Same problem with kernel 5.8 or nvidia 450.

  The problem does not exist on Wayland with xx.org video.

  I need nvidia drivers and Xorg for the dual screen 4K.

  Thanks for your help

  Config :
  
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04
  CPU: Intel i7-7700HQ (8) @ 3.800GHz 
  GPU: NVIDIA GeForce GTX 1070 Mobile

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gir1.2-mutter-6 3.36.4-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Aug 21 05:20:56 2020
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892446/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Hui Wang]

For the gsequencer/3.1.3-1 (s390x):

The last step fails, but it has nothing to do with alsalib, this is the log 
without regression reported:
ags-integration-unit-test PASS
ags-integration-functional-test FLAKY non-zero exit status 2
Creating nova instance adt-focal-s390x-gsequencer-20200820-095922 from image 
adt/ubuntu-focal-s390x-server-20200820.img (UUID 
6a71e79c-0324-4927-a49e-11d2b937df21)...

This is the log with regression reported:
ags-integration-unit-test PASS
ags-integration-functional-test FLAKY non-zero exit status 2
Creating nova instance adt-focal-s390x-gsequencer-20200820-100757 from image 
adt/ubuntu-focal-s390x-server-20200820.img (UUID 
6a71e79c-0324-4927-a49e-11d2b937df21)...
Unexpected error:
Traceback (most recent call last):
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 739, in mainloop
command()
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 668, in command
r = f(c, ce)
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 116, in cmd_close
cleanup()
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 694, in cleanup
caller.hook_cleanup()
  File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-ssh", line 500, in 
hook_cleanup
execute_setup_script('cleanup')
  File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-ssh", line 205, in 
execute_setup_script
stderr=subprocess.PIPE)
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 144, in 
execute_timeout
(out, err) = sp.communicate(instr)
  File "/usr/lib/python3.5/subprocess.py", line 1072, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.5/subprocess.py", line 1715, in _communicate
ready = selector.select(timeout)
  File "/usr/lib/python3.5/selectors.py", line 376, in select
fd_event_list = self._poll.poll(timeout)
  File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler
raise Timeout()
VirtSubproc.Timeout
autopkgtest [11:15:29]: ERROR: autopkgtest
: error cleaning up:

autopkgtest [11:15:29]: ERROR: testbed failure: cannot send to testbed:
[Errno 32] Broken pipe


It is an error on creating nova instance, it has nothing to do with
alsa-lib.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-C

[Desktop-packages] [Bug 1892419] Re: Displayport is not working

[Daniel van Vugt]

Please run this command:

  grep . /sys/class/drm/*/status > drm-status.txt

and then attach the resulting text file here.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Tags added: multimonitor

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

Title:
  Displayport is not working

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Can't get dysplayport to recognize. It is not the cable since I tested
  it on another PC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 16:54:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1993]
  InstallationDate: Installed on 2020-08-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP ProBook 650 G1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.32
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.asset.tag: 5CG5203T6Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.sku: K4L00UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892419/+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 1892427] Re: HDMI connected monitor wakeup problems

[Daniel van Vugt]

This sounds like two separate issues:

1. Needing to wake the TV with the remote. I would hazard a guess that's
a feature/bug of the TV firmware. TVs generally don't expect to be used
as monitors and may not implement power mode switching reliably like a
proper monitor. Most likely it's designed to respond to the remote only.
I don't think this is a software bug in Ubuntu, but probably in the TV
itself...

2. Windows get moved and resized. This should only happen if the monitor
(TV) is seen to be unplugged. But indeed sometimes power saving modes do
get confused for the monitor being unplugged. I wonder though if this is
also a problem with the TV failing to sleep correctly and instead
disconnecting from the computer... Can you test a (non-TV) monitor on
the same HDMI port?


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- HDMI connected monitor wakeup problems
+ HDMI connected TV wakeup problems

** Summary changed:

- HDMI connected TV wakeup problems
+ [amdgpu] HDMI connected TV wakeup problems

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-amdgpu
(Ubuntu)

** Tags added: amdgpu

** Tags added: multimonitor

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

Title:
  [amdgpu] HDMI connected TV wakeup problems

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  The setup here is critical to understanding the problem. A laptop is
  connected via HDMI to a TV monitor. Two displays are thus available to
  the OS. Everything works great both in mirror display and regular
  display. At the end of day, I lock the user account and the display
  manager (DM) tells the monitors to blank (sleep?). When I touch the DM
  and login the laptop display livens up and looks good. However, the TV
  display often doesn't and I need to wake up the TV with the TV control
  stick. This works OK, and the second display comes back. And all the
  windows associated with that display return from sleep OK. *HOWEVER*,
  all the geometry for those windows (term windows is one example) are
  lost. I can see the windows in the term overview, but I cant get to
  them on the second display.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  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: Thu Aug 20 17:00:58 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c8) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:8348]
  InstallationDate: Installed on 2018-04-20 (853 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: HP HP Laptop 17-ak0xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=79cc5ed4-f740-450d-9a89-c5b4f899d10e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8348
  dmi.board.vendor: HP
  dmi.board.version: 42.20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd11/02/2017:svnHP:pnHPLaptop17-ak0xx:pvrType1ProductConfigId:rvnHP:rn8348:rvr42.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-ak0xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Aug  5 16:27:12 2020
  xserver.configfile: default
  

[Desktop-packages] [Bug 1892404] Re: busted scale with lowercase characters

[Daniel van Vugt]

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

We're tracking this in bug 1892440 now.

** Tags added: focal nvidia

** This bug has been marked a duplicate of bug 1892440
   [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia 
cards

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

Title:
  busted scale with lowercase characters

Status in mutter package in Ubuntu:
  New

Bug description:
  UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
  The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

  Ubuntu 20.04.x LTS
  NVIDIA 440.x

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Daniel van Vugt]

** This bug is no longer a duplicate of bug 1889686
   [focal] [nvidia] Patch causes small text in Pop!OS: 
x11-Add-support-for-fractional-scaling-using-Randr.patch

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1889686] Re: [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-for-fractional-scaling-using-Randr.patch

[Daniel van Vugt]

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

Thanks. We will use bug 1892440 then.

** This bug has been marked a duplicate of bug 1892440
   [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia 
cards

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

Title:
  [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-
  for-fractional-scaling-using-Randr.patch

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  With the package currently proposed for 20.04, NVIDIA systems are
  experiencing very small text in GDM and GNOME Shell. Removing x11-Add-
  support-for-fractional-scaling-using-Randr.patch fixes it.

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Daniel van Vugt]

** Tags added: regression-update rls-ff-incoming

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1889686] Re: [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-for-fractional-scaling-using-Randr.patch

[Launchpad Bug Tracker]

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-
  for-fractional-scaling-using-Randr.patch

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  With the package currently proposed for 20.04, NVIDIA systems are
  experiencing very small text in GDM and GNOME Shell. Removing x11-Add-
  support-for-fractional-scaling-using-Randr.patch fixes it.

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Cristiano Nunes]

** This bug has been marked a duplicate of bug 1889686
   [focal] [nvidia] Patch causes small text in Pop!OS: 
x11-Add-support-for-fractional-scaling-using-Randr.patch

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Cristiano Nunes]

A workaround is set the "Fractional Scaling" to other value and back it
to 100%, to fix the font sizes. But after a reboot, all fonts still
smaller again.

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Cristiano Nunes]

After update to the mutter version (3.36.4-0ubuntu0.20.04.2) the fonts
were smaller (top menu and desktop menu) from Gnome Shell.

I have two computers here, the bug occur with only the computer with
NVIDIA card.

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1889686] Re: [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-for-fractional-scaling-using-Randr.patch

[Cristiano Nunes]

New this bug occur in Ubuntu 20.04 with mutter version
(3.36.4-0ubuntu0.20.04.2) as reported in #1892440.

I'm waiting a fix for this bug.

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

Title:
  [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-
  for-fractional-scaling-using-Randr.patch

Status in mutter package in Ubuntu:
  New

Bug description:
  With the package currently proposed for 20.04, NVIDIA systems are
  experiencing very small text in GDM and GNOME Shell. Removing x11-Add-
  support-for-fractional-scaling-using-Randr.patch fixes it.

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

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

[Desktop-packages] [Bug 1892440] Dependencies.txt

[Cristiano Nunes]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1892440/+attachment/5403289/+files/Dependencies.txt

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1892440] ProcCpuinfoMinimal.txt

[Cristiano Nunes]

apport information

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

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #271
   https://gitlab.gnome.org/GNOME/totem/-/issues/271

** Also affects: totem via
   https://gitlab.gnome.org/GNOME/totem/-/issues/271
   Importance: Unknown
   Status: Unknown

** Changed in: totem (Ubuntu)
   Status: New => Confirmed

** Changed in: totem (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1892440] ProcEnviron.txt

[Cristiano Nunes]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1892440/+attachment/5403291/+files/ProcEnviron.txt

** Tags added: nvidia xrandr-scaling

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1892440] [NEW] [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with nvidia cards

[Cristiano Nunes]

Public bug reported:

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

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

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


** Tags: apport-collected focal nvidia xrandr-scaling

** Tags added: apport-collected focal

** Description changed:

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

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

Title:
  [focal] [nvidia] New patch causes small text in Ubuntu 20.04 with
  nvidia cards

Status in mutter package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1892345] Re: sometimes drop-down menu in settings opens but closes instantly, when clicked with mouse.

[Daniel van Vugt]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not
  with my bluetooth mouse or wacom tablet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+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 1892345] Re: sometimes drop-down menu in settings opens but closes instantly, when clicked with mouse.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not
  with my bluetooth mouse or wacom tablet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Daniel van Vugt]

Not sure how many parts there will be to this in the end...

bluez: Fixed in 5.54? That's in Ubuntu 20.10 already.
linux: Fixed in 5.6-ish? That's coming to Ubuntu 20.10 soon via kernel 5.8.
pulseaudio: In progress (pulseaudio!227).

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Daniel van Vugt]

In progress here:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1892439] [NEW] [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all

[Ramon Machado]

Public bug reported:

ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio 
source.
Video works fine

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  voorhees857 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 21:46:38 2020
InstallationDate: Installed on 2020-08-04 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  voorhees857 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6UET38WW (1.16 )
dmi.board.name: 2901A3U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T410s
dmi.product.name: 2901A3U
dmi.product.version: ThinkPad T410s
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1892439

Title:
  [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio 
source.
  Video works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  voorhees857 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 21:46:38 2020
  InstallationDate: Installed on 2020-08-04 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  voorhees857 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET38WW (1.16 )
  dmi.board.name: 2901A3U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410s
  dmi.product.name: 2901A3U
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892439/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options

[Daniel van Vugt]

In progress here:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227

** No longer affects: bluez (Ubuntu)

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

Title:
  AptX and AptX HD unavailable as Bluetooth audio quality options

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

Bug description:
  Current situation:

  When one connects a Bluetooth audio device, at best one can choose
  between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback
  (A2DP Sink)". That is sad when the audio device supports AptX or AptX
  HD.

  
  Expected situation:

  One can select AptX or AptX HD as the Bluetooth audio output profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870829/+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 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #36
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36
   Importance: Unknown
   Status: Unknown

** No longer affects: bluez (Ubuntu)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: focal groovy

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

Title:
  Please add LDAC support in pulseaudio-module-bluetooth

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

Bug description:
  There is a project which enables these codecs in pulseaudio (by adding
  profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

  For LDAC (codec) it uses libldac from the AOSP project:
  https://android.googlesource.com/platform/external/libldac

  There is a libldac dispatcher by the same author:
  https://github.com/EHfive/ldacBT

  It would be nice to have this functionality out-of-the-box in Ubuntu.
  This cannot be merged to PulseAudio upstream because the Android
  libldac library is under Apache License 2.0 which is incompatible with
  pulseaudio license LGPL 2.1:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1892377/+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 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth

[Daniel van Vugt]

One codec at a time :)

AptX is already covered by bug 1870829

** Summary changed:

- Please add LDAC/AptX/AptX HD/AAC support in pulseaudio-module-bluetooth
+ Please add LDAC support in pulseaudio-module-bluetooth

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Wishlist

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Please add LDAC support in pulseaudio-module-bluetooth

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is a project which enables these codecs in pulseaudio (by adding
  profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

  For LDAC (codec) it uses libldac from the AOSP project:
  https://android.googlesource.com/platform/external/libldac

  There is a libldac dispatcher by the same author:
  https://github.com/EHfive/ldacBT

  It would be nice to have this functionality out-of-the-box in Ubuntu.
  This cannot be merged to PulseAudio upstream because the Android
  libldac library is under Apache License 2.0 which is incompatible with
  pulseaudio license LGPL 2.1:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892377/+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 1892427] [NEW] HDMI connected monitor wakeup problems

[Nicholas Strauss]

Public bug reported:

The setup here is critical to understanding the problem. A laptop is
connected via HDMI to a TV monitor. Two displays are thus available to
the OS. Everything works great both in mirror display and regular
display. At the end of day, I lock the user account and the display
manager (DM) tells the monitors to blank (sleep?). When I touch the DM
and login the laptop display livens up and looks good. However, the TV
display often doesn't and I need to wake up the TV with the TV control
stick. This works OK, and the second display comes back. And all the
windows associated with that display return from sleep OK. *HOWEVER*,
all the geometry for those windows (term windows is one example) are
lost. I can see the windows in the term overview, but I cant get to them
on the second display.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.24
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: Thu Aug 20 17:00:58 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c8) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Carrizo [103c:8348]
InstallationDate: Installed on 2018-04-20 (853 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: HP HP Laptop 17-ak0xx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=79cc5ed4-f740-450d-9a89-c5b4f899d10e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8348
dmi.board.vendor: HP
dmi.board.version: 42.20
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd11/02/2017:svnHP:pnHPLaptop17-ak0xx:pvrType1ProductConfigId:rvnHP:rn8348:rvr42.20:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 17-ak0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Aug  5 16:27:12 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  HDMI connected monitor wakeup problems

Status in xorg package in Ubuntu:
  New

Bug description:
  The setup here is critical to understanding the problem. A laptop is
  connected via HDMI to a TV monitor. Two displays are thus available to
  the OS. Everything works great both in mirror display and regular
  display. At the end of day, I lock the user account and the display
  manager (DM) tells the monitors to blank (sleep?). When I touch the DM
  and login the laptop display livens up and looks good. However, the TV
  display often doesn't and I need to wake up the TV with the TV control
  stick. This works OK, and the second display comes back. And all the
  windows associated with that display return from sleep OK. *HOWEVER*,
  all the geometry for those windows (term windows is one example) are
  lost. I can see the windows in the term overview, but I cant get to
  them on the second display.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1892425] [NEW] lightdm startup delay

[Sterling Butters]

Public bug reported:

https://askubuntu.com/questions/1268723/lightdm-startup-delay-in-20-04

I have had this issue for a long time where, once I login, all I can see
(for at least a minute) is the wallpaper and mouse. Eventually the rest
of the desktop environment is loaded and everything is good to go. If I
log out and back in, I don't have the same issue I do at startup.

I have tried many things including installation of haveged and also
trying to disable the lightdm.service and startx'ing (however I was
never able to even successfully disable the service). I also read
somewhere that it might not actually be lightdm but rather
accountsservice that is the source of the problem. And in fact I can see
some authentication warnings in the journalctl. Looking at the lightdm
log, there don't appear to be any significant gaps in the log entry
timestamps like people who have posted in other forums.

Description:Ubuntu 20.04.1 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 10:14:09 2020
InstallationDate: Installed on 2018-04-03 (870 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2020-05-22 (90 days ago)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1892425

Title:
  lightdm startup delay

Status in lightdm package in Ubuntu:
  New

Bug description:
  https://askubuntu.com/questions/1268723/lightdm-startup-delay-in-20-04

  I have had this issue for a long time where, once I login, all I can
  see (for at least a minute) is the wallpaper and mouse. Eventually the
  rest of the desktop environment is loaded and everything is good to
  go. If I log out and back in, I don't have the same issue I do at
  startup.

  I have tried many things including installation of haveged and also
  trying to disable the lightdm.service and startx'ing (however I was
  never able to even successfully disable the service). I also read
  somewhere that it might not actually be lightdm but rather
  accountsservice that is the source of the problem. And in fact I can
  see some authentication warnings in the journalctl. Looking at the
  lightdm log, there don't appear to be any significant gaps in the log
  entry timestamps like people who have posted in other forums.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 10:14:09 2020
  InstallationDate: Installed on 2018-04-03 (870 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-05-22 (90 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1892425/+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 1892419] [NEW] Displayport is not working

[Ramon Machado]

Public bug reported:

Can't get dysplayport to recognize. It is not the cable since I tested
it on another PC

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 16:54:01 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1993]
InstallationDate: Installed on 2020-08-20 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP ProBook 650 G1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L77 Ver. 01.32
dmi.board.name: 1993
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.3C
dmi.chassis.asset.tag: 5CG5203T6Z
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP ProBook 650 G1
dmi.product.sku: K4L00UT#ABA
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Displayport is not working

Status in xorg package in Ubuntu:
  New

Bug description:
  Can't get dysplayport to recognize. It is not the cable since I tested
  it on another PC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 16:54:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1993]
  InstallationDate: Installed on 2020-08-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP ProBook 650 G1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.32
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.asset.tag: 5CG5203T6Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.sku: K4L00UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: 

[Desktop-packages] [Bug 1891461] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gsequencer/3.1.3-1 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#alsa-lib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the 

[Desktop-packages] [Bug 1889217] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gsequencer/3.1.3-1 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#alsa-lib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  

[Desktop-packages] [Bug 1892404] [NEW] busted scale with lowercase characters

[Marco Giannini]

Public bug reported:

UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

Ubuntu 20.04.x LTS
NVIDIA 440.x

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

** Attachment added: "photo_2020-08-20_20-07-12.jpg"
   
https://bugs.launchpad.net/bugs/1892404/+attachment/5403214/+files/photo_2020-08-20_20-07-12.jpg

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

Title:
  busted scale with lowercase characters

Status in mutter package in Ubuntu:
  New

Bug description:
  UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
  The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

  Ubuntu 20.04.x LTS
  NVIDIA 440.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892404/+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 1892394] [NEW] Wifi kills laptop

[Paco Raxim]

Public bug reported:

I'm not so sure why this long lasting bug even exists.

If Wifi connection is not stable, it can kill the laptop,
and the only way to restart the computer if you hold the start button for 
seconds.
(simply you can break your hardware)

The wifi process does not release anything, and you can't kill the driver,
you can't do anything with it. You just can loose whatever you were working on.

It's a long lasting bug appeared from the initial release of 18.0.

Reproduction rate is 100%, and even larger the release number is, even bad it 
looks.
(18.5, every update is up-to-date)

Pls. fix this shit. There are many annoying really-really basic bugs on Ubuntu,
i'm not interested in re-branding, and i'm pretty sure, no user care about.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Wifi kills laptop

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not so sure why this long lasting bug even exists.

  If Wifi connection is not stable, it can kill the laptop,
  and the only way to restart the computer if you hold the start button for 
seconds.
  (simply you can break your hardware)

  The wifi process does not release anything, and you can't kill the driver,
  you can't do anything with it. You just can loose whatever you were working 
on.

  It's a long lasting bug appeared from the initial release of 18.0.

  Reproduction rate is 100%, and even larger the release number is, even bad it 
looks.
  (18.5, every update is up-to-date)

  Pls. fix this shit. There are many annoying really-really basic bugs on 
Ubuntu,
  i'm not interested in re-branding, and i'm pretty sure, no user care about.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1892394/+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 1892394] Re: Wifi kills laptop

[Paco Raxim]

anyway other issues which has been raised years ago, hasn't been fixed

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

Title:
  Wifi kills laptop

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not so sure why this long lasting bug even exists.

  If Wifi connection is not stable, it can kill the laptop,
  and the only way to restart the computer if you hold the start button for 
seconds.
  (simply you can break your hardware)

  The wifi process does not release anything, and you can't kill the driver,
  you can't do anything with it. You just can loose whatever you were working 
on.

  It's a long lasting bug appeared from the initial release of 18.0.

  Reproduction rate is 100%, and even larger the release number is, even bad it 
looks.
  (18.5, every update is up-to-date)

  Pls. fix this shit. There are many annoying really-really basic bugs on 
Ubuntu,
  i'm not interested in re-branding, and i'm pretty sure, no user care about.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1892394/+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 1876352] Re: App Grid icons out of alignment when opening from overview

[Brett Stevens]

This bug is still happening on ubuntu-dock version 68.
If I disable the dock it goes away but re-enable it and it comes straight back.

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

Title:
  App Grid icons out of alignment when opening from overview

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Affected version:
  Ubuntu 20.04
  Gnome Shell Version 3.36.1
  Only tested on xorg

  
  Bug summary:
  When opening the App Grid (aka "Show Applications) from the window overview 
(I don't know the technical terms) the icons shift out of alignment. This gets 
worse if you have multiple pages of apps (as I do), and it gets even worse the 
more you open and close the App Grid in this manner.
  I cannot see the same bug if you just open the App Grid from the desktop.

  
  Steps to reproduce:
  1. Open the overview window using the Super Key
  2. Click the "Show Applications" icon
  3. You will see the icons in the App Grid shift downwards
  4. Scroll down to see the icons move further out of alignment

  What did GNOME Shell do that was unexpected?:
  Display the App Window icons out of alignment when accessing the app grid via 
the window overview (pressing the Super key)

  What did you expect to happen:
  I expected the icons to display properly.

  Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 19:16:06 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-14 (169 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu (updated: including PCIe Bus Error)

[hatsune]

** Description changed:

  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.
  
  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter
  
  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be
  
  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G
  
  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details
+ 
+ 
+ ~Updated~
+ 
+ There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur 
due that wifi card - RTL8723BE
+ It usually appear when boot the device (before login screen) and currently i 
surpressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
+ 
+ I found https://github.com/rtlwifi-linux/rtlwifi_new and
+ https://github.com/silenoth/rtlwifi_new-extended it contain 'RTL8723BE'
+ however i found most people use them due wifi card does not display or
+ unable connect but i dont have such issue and users have reported
+ installation issues then didnt consider to put to my machine.

** Description changed:

  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.
  
  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter
  
  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be
  
  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G
  
  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details
  
  
  ~Updated~
  
  There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur 
due that wifi card - RTL8723BE
- It usually appear when boot the device (before login screen) and currently i 
surpressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
+ It usually appear when boot the device (before login screen) and currently i 
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
  
  I found https://github.com/rtlwifi-linux/rtlwifi_new and
  https://github.com/silenoth/rtlwifi_new-extended it contain 'RTL8723BE'
- however i found most people use them due wifi card does not display or
+ however most people had used them due wifi card does not display or
  unable connect but i dont have such issue and users have reported
  installation issues then didnt consider to put to my machine.

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu (updated: including PCIe Bus Error)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 

[Desktop-packages] [Bug 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu (updated: including PCIe Bus Error)

[hatsune]

** Summary changed:

- [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better 
uninstall ubuntu
+ [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better 
uninstall ubuntu (updated: including PCIe Bus Error)

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu (updated: including PCIe Bus Error)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1892377] Re: Please add LDAC/AptX/AptX HD/AAC support in pulseaudio-module-bluetooth

[Kyrylo Bohdanenko]

There are no logs to be provided, this is a feature request

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Please add LDAC/AptX/AptX HD/AAC support in pulseaudio-module-
  bluetooth

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is a project which enables these codecs in pulseaudio (by adding
  profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

  For LDAC (codec) it uses libldac from the AOSP project:
  https://android.googlesource.com/platform/external/libldac

  There is a libldac dispatcher by the same author:
  https://github.com/EHfive/ldacBT

  It would be nice to have this functionality out-of-the-box in Ubuntu.
  This cannot be merged to PulseAudio upstream because the Android
  libldac library is under Apache License 2.0 which is incompatible with
  pulseaudio license LGPL 2.1:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892377/+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 1892377] [NEW] Please add LDAC/AptX/AptX HD/AAC support in pulseaudio-module-bluetooth

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

There is a project which enables these codecs in pulseaudio (by adding
profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

For LDAC (codec) it uses libldac from the AOSP project:
https://android.googlesource.com/platform/external/libldac

There is a libldac dispatcher by the same author:
https://github.com/EHfive/ldacBT

It would be nice to have this functionality out-of-the-box in Ubuntu.
This cannot be merged to PulseAudio upstream because the Android libldac
library is under Apache License 2.0 which is incompatible with
pulseaudio license LGPL 2.1:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

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

-- 
Please add LDAC/AptX/AptX HD/AAC support in pulseaudio-module-bluetooth
https://bugs.launchpad.net/bugs/1892377
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

-- 
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 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Playback on 200% screen"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Display Settings screenshot 2"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Display Settings screenshot 1"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-54.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] [NEW] Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

Public bug reported:

I am using Ubuntu Focal Fossa with Wayland and two screens. 
Display 1 is a 3840 x 2160 screen at 200% scaling
Display 2 is a 1920x1200 at 100% scaling

Fractional Scaling is on. Display 2 is my Primary Display.

When I play a video on Display 2, everything works as expected. When I
play a video on Display 1 (whether I drag it there or it is there all
along) then it plays taking up only the top-left corner of the window.

May be related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1529008
https://gitlab.gnome.org/GNOME/totem/-/issues/271
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: totem 3.34.1-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 15:45:13 2020
InstallationDate: Installed on 2020-05-03 (108 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


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

** Attachment added: "Video playback on 100% screen"
   
https://bugs.launchpad.net/bugs/1892379/+attachment/5403147/+files/Screenshot%20from%202020-08-20%2015-54-27.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892373] [NEW] Firefox crashes on logout

[Mike Jing]

Public bug reported:

Every time I logout or shutdown the system with firefox open, it will
generate a crash report in about:crashes. However, there is no crash
dump in /var/crash.

I noticed this before I upgraded from 18.04 LTS recently, and at first I
thought the crash went away after the upgrade, but sadly it's not the
case.

I've tested with a fresh new user, with the same result. I'm running
Xubuntu 20.04.1 LTS.

This may be the same bug as bug #73536 ( Mozilla Bugzilla #336193), but
I can't be sure.

To reproduce:

Open firefox. Logout with firefox window open. login again and check
"about:crashes" in firefox.

The output of:

lsb_release -a; uname -a; apt-cache policy firefox

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
Linux celia 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
firefox:
  Installed: 79.0+build1-0ubuntu0.20.04.1
  Candidate: 79.0+build1-0ubuntu0.20.04.1
  Version table:
 *** 79.0+build1-0ubuntu0.20.04.1 500
500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-updates/main amd64 
Packages
500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 75.0+build3-0ubuntu1 500
500 http://mirror.csclub.uwaterloo.ca/ubuntu focal/main amd64 Packages

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

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

Title:
  Firefox crashes on logout

Status in firefox package in Ubuntu:
  New

Bug description:
  Every time I logout or shutdown the system with firefox open, it will
  generate a crash report in about:crashes. However, there is no crash
  dump in /var/crash.

  I noticed this before I upgraded from 18.04 LTS recently, and at first
  I thought the crash went away after the upgrade, but sadly it's not
  the case.

  I've tested with a fresh new user, with the same result. I'm running
  Xubuntu 20.04.1 LTS.

  This may be the same bug as bug #73536 ( Mozilla Bugzilla #336193),
  but I can't be sure.

  To reproduce:

  Open firefox. Logout with firefox window open. login again and check
  "about:crashes" in firefox.

  The output of:

  lsb_release -a; uname -a; apt-cache policy firefox

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04
  Codename: focal
  Linux celia 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  firefox:
Installed: 79.0+build1-0ubuntu0.20.04.1
Candidate: 79.0+build1-0ubuntu0.20.04.1
Version table:
   *** 79.0+build1-0ubuntu0.20.04.1 500
  500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-security/main 
amd64 Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://mirror.csclub.uwaterloo.ca/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892373/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.

[Bob]

Same issue with GU502GU with Mint or Pop OS

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

Title:
  [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack
  headphones.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.4 LTS dual boot with Windows 10.
  On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at 
all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, 
tried even 5.7-rc4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corsarstl   1728 F pulseaudio
   /dev/snd/pcmC0D0p:   corsarstl   1728 F...m pulseaudio
   /dev/snd/controlC1:  corsarstl   1728 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 20:25:27 2020
  InstallationDate: Installed on 2020-05-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
   /dev/snd/controlC1:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GU502GV.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GU502GV
  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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus M
  dmi.product.name: Zephyrus M GU502GV_GU502GV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu

[hatsune]

@seb128 the original issue based on Ubuntu 20.04.01 LTS (newly
installed)

Recently i moved to PopOS 20.04 LTS (due other purpose) however the bug
same as. below i attached as you requested

** Attachment added: "nmdebug"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+attachment/5403124/+files/nmdebug

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1891733] Re: Support better Arabic font

[Gunnar Hjalmarsson]

** Description changed:

- As per the  discussion.
+ [Impact]
+ 
+ Arabic speaking users have requested better rendering of Arabic. This
+ proposed upload addresses that wish. Related discussion is being hold at
+ .
+ 
+ So how is this an SRUable bug fix and not just an enhancement which
+ should go to -backports? Well, currently, if you install the Arabaic
+ language via Language Support, a couple of Arabic fonts packages are
+ pulled. But even if you set an Arabic locale, those fonts won't make a
+ difference. The explanation is that DejaVu fonts, which also are able to
+ render Arabic, have higher fontconfig precedence. The user must mess
+ with fontconfig themselves to change the effective font, which is a bug.
+ (I can't tell if it ever worked as intended.)
+ 
+ So to summarize: This is a combination of a bug fix and an enhancement.
+ 
+ [Test Case]
+ 
+ * Install the language-selector-{gnome,common} packages
+   from focal-proposed.
+ 
+ * Open the Language Support tool and install Arabic.
+ 
+ * Open a terminal window and run this command:
+ 
+   LC_CTYPE=ar_EG.UTF-8 fc-match -a | head -10
+ 
+ * Find that Noto fonts are at the top of the list.
+ 
+ [Regression risk]
+ 
+ This will change the effective font for rendering Arabic for some users.
+ But the user experience will be improved in those cases, not the
+ opposite.
+ 
+ The change in font will only happen for users with an Arabic locale. The
+ risk that other users would be affected by the change is low.

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

Title:
  Support better Arabic font

Status in Ubuntu Seeds:
  New
Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  In Progress
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Arabic speaking users have requested better rendering of Arabic. This
  proposed upload addresses that wish. Related discussion is being hold
  at .

  So how is this an SRUable bug fix and not just an enhancement which
  should go to -backports? Well, currently, if you install the Arabaic
  language via Language Support, a couple of Arabic fonts packages are
  pulled. But even if you set an Arabic locale, those fonts won't make a
  difference. The explanation is that DejaVu fonts, which also are able
  to render Arabic, have higher fontconfig precedence. The user must
  mess with fontconfig themselves to change the effective font, which is
  a bug. (I can't tell if it ever worked as intended.)

  So to summarize: This is a combination of a bug fix and an
  enhancement.

  [Test Case]

  * Install the language-selector-{gnome,common} packages
from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window and run this command:

LC_CTYPE=ar_EG.UTF-8 fc-match -a | head -10

  * Find that Noto fonts are at the top of the list.

  [Regression risk]

  This will change the effective font for rendering Arabic for some
  users. But the user experience will be improved in those cases, not
  the opposite.

  The change in font will only happen for users with an Arabic locale.
  The risk that other users would be affected by the change is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1891733/+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 1892345] Re: sometimes drop-down menu in settings opens but closes instantly, when clicked with mouse.

[Manik Raina]

** Description changed:

  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not with
- my bluetooth mouse.
+ my bluetooth mouse or wacom tablet.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

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

Title:
  sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not
  with my bluetooth mouse or wacom tablet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+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 1892348] [NEW] cups samba authetication dialog closes too early

[Stefan Helmert]

Public bug reported:

Using network printers with samba authentication on Ubuntu 20.04 the
authentication dialog is shown only a very short time and closes
unexpectedly. But authentication works with noninteractive
authentication using specifying username and password as part of the
samba address.

The interactive authentication dialog worked in Ubuntu 18.04 correctly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 12:57:13 2020
InstallationDate: Installed on 2020-07-07 (43 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20QF00AYGE
Papersize: a4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET50W (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QF00AYGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QF00AYGE
dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  cups samba authetication dialog closes too early

Status in cups package in Ubuntu:
  New

Bug description:
  Using network printers with samba authentication on Ubuntu 20.04 the
  authentication dialog is shown only a very short time and closes
  unexpectedly. But authentication works with noninteractive
  authentication using specifying username and password as part of the
  samba address.

  The interactive authentication dialog worked in Ubuntu 18.04
  correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 12:57:13 2020
  InstallationDate: Installed on 2020-07-07 (43 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QF00AYGE
  Papersize: a4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QF00AYGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QF00AYGE
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892348/+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 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892288/+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 1892345] Re: sometimes drop-down menu in settings opens but closes instantly, when clicked with mouse.

[Manik Raina]

** Attachment added: "a gif of the bug"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+attachment/5403100/+files/ubuntu20.04_dropdown_bug_mouse.gif

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

Title:
  sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not
  with my bluetooth mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+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 1892345] [NEW] sometimes drop-down menu in settings opens but closes instantly, when clicked with mouse.

[Manik Raina]

Public bug reported:

Sometimes drop-down menu in settings opens but closes instantly, when
clicked with mouse. It works fine with my laptop's touchpad but not with
my bluetooth mouse.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 15:28:01 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-08 (164 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

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


** Tags: amd64 apport-bug focal 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/1892345

Title:
  sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes drop-down menu in settings opens but closes instantly, when
  clicked with mouse. It works fine with my laptop's touchpad but not
  with my bluetooth mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:28:01 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-08 (164 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-08-09 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892345/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

[Christian Ehrhardt ]

From
https://libvirt.org/formatdomain.html#graphical-framebuffers

"Copy & Paste functionality (via Spice agent) is set by the clipboard
element. It is enabled by default, and can be disabled by setting the
copypaste property to no. Since 0.9.3"

So yeah if disabling this turns out to be a reliable bug fix for those
few that are affected that seems great. I'd not change the default
though as for most setups/cases it seems to work.


@Sebastian - I assumed with that disabled guest/host clipboard copy is totally 
switched off, or is it working but without the issues described here?

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-protocol source package in Focal:
  Incomplete
Status in spice-vdagent source package in Focal:
  Incomplete
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

[Sebastien Bacher]

libimobiledevice is built with openssl now

https://launchpad.net/ubuntu/+source/libimobiledevice/1.3.0-4

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Fix Released
Status in libplist package in Ubuntu:
  Fix Released
Status in libusbmuxd package in Ubuntu:
  Fix Released
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

[Sebastian Haag]

I came across the same issue with a guest distro.
I finally solved it by editing the XML File of the "Display Spice" section in 
the VM settings in virt-manager.

Open the details window of the affected VM in virt-manager.
Navigate to the section "Display Spice".
Click on the Tab "XML" (XML editing has to be enabled in the virt-manager 
settings).
Display Spice" section can be editted manually.
Add "" to the XML. It should look like this:

  
  


Source: https://unix.stackexchange.com/questions/341881/virt-manager-
copy-and-paste-is-possible-to-disable-it

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-protocol source package in Focal:
  Incomplete
Status in spice-vdagent source package in Focal:
  Incomplete
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1892333] Re: Hidden text in LibreOffice Calc when using Breeze Dark theme

[bitsmack]

** Description changed:

  There are cases where text and/or button graphics do not appear in
  LibreOffice (Calc and Draw, at least) when using the Breeze Dark theme
  in Kubuntu 20.04.1. This is one example.
  
  In Calc, in the "Find & Replace" window (CTRL-H), click on "Find All".
  If there are multiple results, they are listed with alternating
  background colors. When the background is white, the white text cannot
- be seen.
+ be seen. If you click on the missing text, the background will change
+ and make the text visible.
  
- Please see the attached screenshot.
+ Please see the attached screenshot. To recreate:
+ 1. Open LibreOffice Calc
+ 2. Type a string into multiple cells (e.g. "Test")
+ 3. Press CTRL-H to bring up the "Find & Replace" window
+ 4. Enter the string into the "Find" field
+ 5. Click "Find All".
  
  If I switch the Kubuntu theme to Breeze (System Settings -> Global
  Theme) then the results are displayed properly. If I switch back to
  Breeze Dark, the problem reappears.
  
  Please let me know if I can provide more information. Thank you for all
  of your work.
  
  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04
  
  $ apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:6.4.4-0ubuntu0.20.04.1
    Candidate: 1:6.4.4-0ubuntu0.20.04.1
    Version table:
   *** 1:6.4.4-0ubuntu0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  $ apt-show-versions -r libreoffice*
  libreoffice-base-core:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-calc:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-common:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-core:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-draw:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-help-common:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-help-en-us:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-impress:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-kf5:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-math:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-plasma:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-qt5:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-style-breeze:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-style-colibre:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-style-tango:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  libreoffice-writer:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-calc 1:6.4.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Aug 20 01:27:21 2020
  InstallationDate: Installed on 2020-05-05 (106 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1892333

Title:
  Hidden text in LibreOffice Calc when using Breeze Dark theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  There are cases where text and/or button graphics do not appear in
  LibreOffice (Calc and Draw, at least) when using the Breeze Dark theme
  in Kubuntu 20.04.1. This is one example.

  In Calc, in the "Find & Replace" window (CTRL-H), click on "Find All".
  If there are multiple results, they are listed with alternating
  background colors. When the background is white, the white text cannot
  be seen. If you click on the missing text, the background will change
  and make the text visible.

  Please see the attached screenshot. To recreate:
  1. Open LibreOffice Calc
  2. Type a string into multiple cells (e.g. "Test")
  3. Press CTRL-H to bring up the "Find & Replace" window
  4. Enter the string into the "Find" field
  5. Click "Find All".

  If I switch the Kubuntu theme to Breeze (System Settings -> Global
  Theme) then the results are displayed properly. If I switch back to
  Breeze Dark, the problem reappears.

  Please let me know if I can provide more information. Thank you for
  all of your work.

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  $ apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:6.4.4-0ubuntu0.20.04.1
    Candidate: 1:6.4.4-0ubuntu0.20.04.1
    

[Desktop-packages] [Bug 304393] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for rpcbind has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  Fix Released
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable allows anyone to
  disable the remote calls in x and/or b, and then upgrade to Focal
  without breaking rpcbind or needing to remove the env var. After the
  upgrade to Focal, the environment variable (defined in
  /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored
  without any change needed to the rpcbind package in Focal or later.

  [original description]

  Binary package hint: cups

  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.

  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd
  when started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

[Launchpad Bug Tracker]

This bug was fixed in the package rpcbind - 0.2.3-0.6ubuntu0.18.04.1

---
rpcbind (0.2.3-0.6ubuntu0.18.04.1) bionic; urgency=medium

  * d/rules: force dh_autoreconf to fix FTBFS (LP: #1885389)
  * d/p/lp304393/0001-rpcbind-Disable-remote-calls-by-default.patch,
d/p/lp304393/0002-rmt-calls.patch,
d/p/lp304393/0003-change-rmtcalls-default-to-enabled.patch:
- Allow disabling rmtcalls port binding (LP: #304393)

 -- Dan Streetman   Tue, 04 Aug 2020 17:17:50
-0400

** Changed in: rpcbind (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  Fix Released
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable allows anyone to
  disable the remote calls in x and/or b, and then upgrade to Focal
  without breaking rpcbind or needing to remove the env var. After the
  upgrade to Focal, the environment variable (defined in
  /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored
  without any change needed to the rpcbind package in Focal or later.

  [original description]

  Binary package hint: cups

  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.

  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd
  when started.

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

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

[Desktop-packages] [Bug 1891461] Please test proposed package

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.6 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but 

[Desktop-packages] [Bug 1889217] Please test proposed package

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.6 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  

[Desktop-packages] [Bug 1889217] Please test proposed package

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

Accepted alsa-lib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.2-2.1ubuntu2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-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/1889217

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  

[Desktop-packages] [Bug 1891461] Please test proposed package

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

Accepted alsa-lib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.2-2.1ubuntu2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-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/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are 

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Willy Nolan]

Totally makes sense.  It's just too bad as Microsoft Windows had this
figured out several years ago.  I want to do more than complain. I want
to help fix this mess.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  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-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1892333] [NEW] Hidden text in LibreOffice Calc when using Breeze Dark theme

[bitsmack]

Public bug reported:

There are cases where text and/or button graphics do not appear in
LibreOffice (Calc and Draw, at least) when using the Breeze Dark theme
in Kubuntu 20.04.1. This is one example.

In Calc, in the "Find & Replace" window (CTRL-H), click on "Find All".
If there are multiple results, they are listed with alternating
background colors. When the background is white, the white text cannot
be seen.

Please see the attached screenshot.

If I switch the Kubuntu theme to Breeze (System Settings -> Global
Theme) then the results are displayed properly. If I switch back to
Breeze Dark, the problem reappears.

Please let me know if I can provide more information. Thank you for all
of your work.

$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

$ apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:6.4.4-0ubuntu0.20.04.1
  Candidate: 1:6.4.4-0ubuntu0.20.04.1
  Version table:
 *** 1:6.4.4-0ubuntu0.20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:6.4.2-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

$ apt-show-versions -r libreoffice*
libreoffice-base-core:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-calc:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-common:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-core:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-draw:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-help-common:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-help-en-us:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-impress:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-kf5:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-math:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-plasma:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-qt5:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-style-breeze:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-style-colibre:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-style-tango:all/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate
libreoffice-writer:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 uptodate

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-calc 1:6.4.4-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Aug 20 01:27:21 2020
InstallationDate: Installed on 2020-05-05 (106 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug calc focal libreoffice

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1892333/+attachment/5403085/+files/Screenshot.png

** Description changed:

- There are many cases where text and/or button graphics do not appear in
+ There are cases where text and/or button graphics do not appear in
  LibreOffice (Calc and Draw, at least) when using the Breeze Dark theme
  in Kubuntu 20.04.1. This is one example.
  
  In Calc, in the "Find & Replace" window (CTRL-H), click on "Find All".
  If there are multiple results, they are listed with alternating
  background colors. When the background is white, the white text cannot
  be seen.
  
  Please see the attached screenshot.
  
  If I switch the Kubuntu theme to Breeze (System Settings -> Global
  Theme) then the results are displayed properly. If I switch back to
  Breeze Dark, the problem reappears.
  
  Please let me know if I can provide more information. Thank you for all
  of your work.
  
  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04
  
  $ apt-cache policy libreoffice-calc
  libreoffice-calc:
-   Installed: 1:6.4.4-0ubuntu0.20.04.1
-   Candidate: 1:6.4.4-0ubuntu0.20.04.1
-   Version table:
-  *** 1:6.4.4-0ubuntu0.20.04.1 500
- 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1:6.4.2-0ubuntu3 500
- 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 1:6.4.4-0ubuntu0.20.04.1
+   Candidate: 1:6.4.4-0ubuntu0.20.04.1
+   Version table:
+  *** 1:6.4.4-0ubuntu0.20.04.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1:6.4.2-0ubuntu3 500
+ 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  $ apt-show-versions -r libreoffice*
  libreoffice-base-core:amd64/focal-updates 1:6.4.4-0ubuntu0.20.04.1 

[Desktop-packages] [Bug 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.

[synapticjuice]

The Asus Rog Zephyrus S GX502GW line of laptops have the same problem.
The headphone/mic jack does not work in Linux but does in Windows. Again
this problem is listed in many forms and I have found no fix. When
headphones are plugged in sound continues via laptop speakers and
nothing from headphones. The sound card for Asus GX502GW is Realtek
ALC294. Thank you for any help with this matter.

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

Title:
  [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack
  headphones.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.4 LTS dual boot with Windows 10.
  On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at 
all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, 
tried even 5.7-rc4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corsarstl   1728 F pulseaudio
   /dev/snd/pcmC0D0p:   corsarstl   1728 F...m pulseaudio
   /dev/snd/controlC1:  corsarstl   1728 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 20:25:27 2020
  InstallationDate: Installed on 2020-05-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
   /dev/snd/controlC1:  gdm1227 F pulseaudio
corsarstl   1728 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GU502GV.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GU502GV
  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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus M
  dmi.product.name: Zephyrus M GU502GV_GU502GV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1857947/+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 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1870867/+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 1873403] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  [ Test case ]

  In a Nvidia system:
  - From g-c-c enable fractional scaling
  - Set all the available fractional scaling values and ensure they work
+ In any case the screen should be turned off

  [ Regression potential ]

  Wrong screen size is set and panning might be enabled.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200124)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+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 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1857947/+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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  [ Test case ]

  In a Nvidia system:
  - From g-c-c enable fractional scaling
  - Set all the available fractional scaling values and ensure they work
+ In any case the screen should be turned off

  [ Regression potential ]

  Wrong screen size is set and panning might be enabled.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200124)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+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 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  * Impact

  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

  * Test Case

  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  Repeat the same selecting 200% at 5., (or 100% if 200% was your
  default) and ensure it's applied.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  * Regression potential

  Verify that scaling changes are correctly applied on different setup

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC 

[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update to 3.36.4 and SRU it

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+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 1889090] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
  Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
  Jul 27 00:30:33 jojda gnome-shell[15068]: **
  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

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

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+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 1874567] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  

[Desktop-packages] [Bug 1887998] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update to 3.36.4 and SRU it

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+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 1889385] Re: Change zsys GC to only keep one month

[Launchpad Bug Tracker]

This bug was fixed in the package zsys - 0.4.7

---
zsys (0.4.7) focal; urgency=medium

  * Fix ZSys package post-installation failed when boot pool is not imported
(LP: #1886214)
  * Change ZSys GC to only keep one month (LP: #1889385)

 -- Didier Roche   Wed, 29 Jul 2020 11:32:33 +0200

** Changed in: zsys (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Change zsys GC to only keep one month

Status in zsys package in Ubuntu:
  Fix Released
Status in zsys source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  * People start experiencing /boot and disk near being full due to our 
snapshot policy.
  * Until we implement GC pressure based on disk space, mitigate the issue by 
only keeping last month.

  
  [Test Case]
  * Install new ZSys version
  * zsysctl show
  -> You should see history states that are older than one month
  * Wait for a GC pass to be ran, or run directly zsysctl service gc
  -> The history states older than a month should be gone (for states that 
don’t have dependencies)

  [Regression Potential] 
  This change is a configuration tweak, which is already covered by a great 
number of test cases. Manual testing has been done on a system with a bunch of 
history states.

  The regression would be too much or too few history states being
  removed, but as said, this scenario is already covered by other test
  cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1889385/+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 1886996] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

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

Bug description:
  [ Impact ]

  It's not possible to restore the application a non-fractional scaling
  configuration when fractional scaling was previously enabled and
  applied.

  [ Test case ]

  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

  [ Regression potential ]
  - Configuration can't be applied
  - Scaling (fractional or not) is not properly applied in single and 
multi-monitor
  - Fractional scaling can't be toggled anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+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 1884754] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

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

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+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 1886214] Re: zsys package post-installation failed when boot pool is not imported

[Launchpad Bug Tracker]

This bug was fixed in the package zsys - 0.4.7

---
zsys (0.4.7) focal; urgency=medium

  * Fix ZSys package post-installation failed when boot pool is not imported
(LP: #1886214)
  * Change ZSys GC to only keep one month (LP: #1889385)

 -- Didier Roche   Wed, 29 Jul 2020 11:32:33 +0200

** Changed in: zsys (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  zsys package post-installation failed when boot pool is not imported

Status in zsys package in Ubuntu:
  Fix Released
Status in zsys source package in Focal:
  Fix Released

Bug description:
  ** SRU **
  [Impact]
  For yet unknown reasons, bpool is sometimes not imported. This causes the 
upgrade script to fail because then /boot is not a mount point.
  The fix just ignores the return status of findmnt to prevent the postinst 
script to fail in this situation

  [Test Case]
  1. Install zsys 0.4.5
  2. Unmount /boot/grub/, /boot/efi and /boot
  3. Install the update of zsys

  [Regression potential]
  Low, since now the error is now ignored.

  
  ** Original Description **
  root@tmp:/home/pgray# zfs list -t snapshot -o name -S creation
  no datasets available

  root@tmp:/home/pgray# sudo apt-get install zsys
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  zsys is already the newest version (0.4.6).
  0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Requesting to save current system state
  Successfully saved as "autozsys_90843v"
  Setting up zsys (0.4.6) ...
  dpkg: error processing package zsys (--configure):
   installed zsys package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   zsys
  ZSys is adding automatic system snapshot to GRUB menu
  ERROR Service took too long to respond. Disconnecting client.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@tmp:/home/pgray# zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  rpool   107G  9.27G  97.7G- -10% 8%  1.00xONLINE  
-

  This was after a previous upgrade failed.
  Even after removing all snapshots for that pool, it fails.

  root@tmp:/home/pgray# lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  root@tmp:/home/pgray# apt-cache policy zsys
  zsys:
    Installed: 0.4.6
    Candidate: 0.4.6
    Version table:
   *** 0.4.6 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-09 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: zsys 0.4.5
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bgiwia@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_bgiwia ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  RelatedPackageVersions:
   zfs-initramfs  0.8.3-1ubuntu12.1
   zfsutils-linux 0.8.3-1ubuntu12.1
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  ZFSImportedPools:
   NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
   rpool   107G  9.66G  97.3G- -10% 9%  1.00xONLINE 
 -
   slow   29.1T   606G  28.5T- - 0% 2%  1.00xONLINE 
 -
  ZFSListcache-bpool:
   bpool/boot   off on  on  off on  off on  
off -   none
   bpool/BOOT   noneoff on  on  off on  off on  
off -   none
   bpool/BOOT/ubuntu_bgiwia /boot   on  on  on  off on  
off on  off -   none
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1886214/+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 1886996] Re: Restore previous configuration after turning off fractional scaling does not work

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

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

Bug description:
  [ Impact ]

  It's not possible to restore the application a non-fractional scaling
  configuration when fractional scaling was previously enabled and
  applied.

  [ Test case ]

  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

  [ Regression potential ]
  - Configuration can't be applied
  - Scaling (fractional or not) is not properly applied in single and 
multi-monitor
  - Fractional scaling can't be toggled anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+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 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-0ubuntu0.20.04.2

---
mutter (3.36.4-0ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

mutter (3.36.4-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't export patch-only private symbol
  * debian/libmutter-6-0.symbols:
- Remove ubuntu-only private symbol

mutter (3.36.3-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/control:
- Revert BD on adwaita-icon-theme 3.36.1-2ubuntu3. It was just temporary fix
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Use pre-computed CRTC layout size for computing screen size (LP: #1874567,
  LP: #1873403)
- Decouple the output mode from layout mode capabilities (LP: #1876894,
  LP: #1886996)
- Ensure we notify CRTC changes on integer scaling changes (LP: #1876894)
- Apply proper layout monitor config when using fractional scaling
  (LP: #1884754)
- Restore the fractional settings when reverting to fractional layout
  (LP: #1886996)
  * debian/libmutter-6-0.symbols: Add new private symbol

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
17:04:41 +0200

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda 

[Desktop-packages] [Bug 1886692] Re: [SRU] libreoffice 6.4.5 for focal

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:6.4.5-0ubuntu0.20.04.1

---
libreoffice (1:6.4.5-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1886692)

 -- Rico Tzschichholz   Mon, 06 Jul 2020 09:00:10
+0200

** Changed in: libreoffice (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
   [SRU] libreoffice 6.4.5 for focal

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.4.5 is in its fifth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.4 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 96 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 96 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886692/+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 1886692] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
   [SRU] libreoffice 6.4.5 for focal

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.4.5 is in its fifth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.4 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 96 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 96 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886692/+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 1891733] Re: Support better Arabic font

[Gunnar Hjalmarsson]

** Changed in: language-selector (Ubuntu Focal)
   Status: Confirmed => In Progress

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

Title:
  Support better Arabic font

Status in Ubuntu Seeds:
  New
Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  In Progress
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  As per the  discussion.

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