[Desktop-packages] [Bug 1861358] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for tracker 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 tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1861358

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Released

Bug description:
  * Impact
  the tracker search utility isn't working

  * Test case
  $ tracker search something

  it should return results if there are any matching items

  * regression potential
  it's a build flag change, just check that the tracker search works including 
in the desktop and nautilus

  --

  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1896073] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for tracker 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 tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896073

Title:
  SRU the current 2.3.6 stable update

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker 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/tracker/-/blob/tracker-2.3/NEWS

  The update add a 'tracker export' command, that's new and not used
  into any integration so has no real regression potential. It's an
  optional new option that can be used to export the data to migrate
  them to the incoming tracker3.

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that file search works correctly from the command line, shell
  and nautilus

  * Regression potential

  There is no specific change or feature to test in that update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+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 1908167] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1908167

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1910709] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for nvidia-graphics-
drivers-340 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/1910709

Title:
  DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  nvidia-340 dkms fails to build against the current HWE kernel in focal, 
regressing the user experience.

  [Test case]
  Install the update, check that the dkms builds and works.

  [Where things could go wrong]
  The changes only add support for newer kernels so that the module can build, 
and it's identical to what's in groovy. In theory it could break the build 
against 5.4 but that's highly unlikely.

  
  --

  Last linux kernel update "linux-headers-5.8.0-34-generic" broke
  nvidia-340 driver and Desktop access. In make log:

  [...]
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid."; \
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\
  echo >&2 ;
  [...]

  Full DKMS log file attacked.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-D3H
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    

[Desktop-packages] [Bug 1912498] Re: Preinstall some new essential raspi packages in the official raspi images

[Łukasz Zemczak]

All branches ready for review, attaching debdiff for review of the
ubuntu-meta package changes as well - would appreciate some feedback.

It's worth mentioning the status for hirsute. So basically in hirsute
and groovy we only use the seeds for the raspi desktop images. In
hirsute, with as things are right now, adding it would be hard as we'd
be generating a lot of component mismatches due to pulling things from
restricted, universe etc. It's a problem conceptually and for migration
reasons, but for a stable series like focal it's less so. Especially
that since ages we've been building raspi images from universe +
multiverse packages anyway, so it's already 'bad'.

** Patch added: "ubuntu-meta_1.450.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1912498/+attachment/5454877/+files/ubuntu-meta_1.450.3.debdiff

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

Title:
  Preinstall some new essential raspi packages in the official raspi
  images

Status in livecd-rootfs package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Opinion
Status in livecd-rootfs source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress

Bug description:
  [Impact]

  For 20.04.2, also as part of support for some new Pi variants (CM4,
  Pi400), we want to preinstall some new essential packages in our raspi
  images such as rpi-eeprom, raspberrypi-userland etc.

  This can be done in two possible ways. One is the 'old way', with a
  single change to livecd-rootfs adding the new packages. But what we'd
  like to propose this time is actually a more proper way, i.e.
  introducing device-specific raspi seeds and a raspi meta-package that
  would pull in all the needed dependencies. This way is better for the
  future, as if we decide we want to add new packages to existing raspi
  installations, we can do it easily by modifying the seeds and
  rebuilding meta. Currently we have no way like this.

  So the current approach includes changes in the following components:
   * The ubuntu and platform seeds (git branches)
   * ubuntu-meta package (adding ubuntu-server-raspi)
   * livecd-rootfs package (installing the raspi-server task)

  [Test Case]

  After accepting all the package into -proposed (and making sure the git seed 
changes are merged), run a raspi arm64 and armhf build. Check if the image 
boots. Confirm that the new images have the following seeded: rpi-eeprom, 
libraspberrypi-bin, flash-kernel, pi-bluetooth.
  Compare manifests between a normal, previous raspi image build and the one 
using seeds - check if nothing has been 'dropped'.

  Also, check if no other image builds have been affected and still
  build correctly, compare image manifests.

  [Where problems could occur]

  In its current form, as the update touches some livecd-rootfs
  auto/config paths, it's possible that a malformed cut-paste broke some
  edge case scenario, so it's good if other non-raspi builds are also
  checked for correctness. Seed changes are less likely to break
  anything, but manifests should be checked in case something got
  dropped by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images

[Łukasz Zemczak]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/+merge/396583

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/+merge/396585

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

Title:
  Preinstall some new essential raspi packages in the official raspi
  images

Status in livecd-rootfs package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Opinion
Status in livecd-rootfs source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress

Bug description:
  [Impact]

  For 20.04.2, also as part of support for some new Pi variants (CM4,
  Pi400), we want to preinstall some new essential packages in our raspi
  images such as rpi-eeprom, raspberrypi-userland etc.

  This can be done in two possible ways. One is the 'old way', with a
  single change to livecd-rootfs adding the new packages. But what we'd
  like to propose this time is actually a more proper way, i.e.
  introducing device-specific raspi seeds and a raspi meta-package that
  would pull in all the needed dependencies. This way is better for the
  future, as if we decide we want to add new packages to existing raspi
  installations, we can do it easily by modifying the seeds and
  rebuilding meta. Currently we have no way like this.

  So the current approach includes changes in the following components:
   * The ubuntu and platform seeds (git branches)
   * ubuntu-meta package (adding ubuntu-server-raspi)
   * livecd-rootfs package (installing the raspi-server task)

  [Test Case]

  After accepting all the package into -proposed (and making sure the git seed 
changes are merged), run a raspi arm64 and armhf build. Check if the image 
boots. Confirm that the new images have the following seeded: rpi-eeprom, 
libraspberrypi-bin, flash-kernel, pi-bluetooth.
  Compare manifests between a normal, previous raspi image build and the one 
using seeds - check if nothing has been 'dropped'.

  Also, check if no other image builds have been affected and still
  build correctly, compare image manifests.

  [Where problems could occur]

  In its current form, as the update touches some livecd-rootfs
  auto/config paths, it's possible that a malformed cut-paste broke some
  edge case scenario, so it's good if other non-raspi builds are also
  checked for correctness. Seed changes are less likely to break
  anything, but manifests should be checked in case something got
  dropped by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images

[Łukasz Zemczak]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/396582

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

Title:
  Preinstall some new essential raspi packages in the official raspi
  images

Status in livecd-rootfs package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Opinion
Status in livecd-rootfs source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress

Bug description:
  [Impact]

  For 20.04.2, also as part of support for some new Pi variants (CM4,
  Pi400), we want to preinstall some new essential packages in our raspi
  images such as rpi-eeprom, raspberrypi-userland etc.

  This can be done in two possible ways. One is the 'old way', with a
  single change to livecd-rootfs adding the new packages. But what we'd
  like to propose this time is actually a more proper way, i.e.
  introducing device-specific raspi seeds and a raspi meta-package that
  would pull in all the needed dependencies. This way is better for the
  future, as if we decide we want to add new packages to existing raspi
  installations, we can do it easily by modifying the seeds and
  rebuilding meta. Currently we have no way like this.

  So the current approach includes changes in the following components:
   * The ubuntu and platform seeds (git branches)
   * ubuntu-meta package (adding ubuntu-server-raspi)
   * livecd-rootfs package (installing the raspi-server task)

  [Test Case]

  After accepting all the package into -proposed (and making sure the git seed 
changes are merged), run a raspi arm64 and armhf build. Check if the image 
boots. Confirm that the new images have the following seeded: rpi-eeprom, 
libraspberrypi-bin, flash-kernel, pi-bluetooth.
  Compare manifests between a normal, previous raspi image build and the one 
using seeds - check if nothing has been 'dropped'.

  Also, check if no other image builds have been affected and still
  build correctly, compare image manifests.

  [Where problems could occur]

  In its current form, as the update touches some livecd-rootfs
  auto/config paths, it's possible that a malformed cut-paste broke some
  edge case scenario, so it's good if other non-raspi builds are also
  checked for correctness. Seed changes are less likely to break
  anything, but manifests should be checked in case something got
  dropped by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images

[Łukasz Zemczak]

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Importance: High => Wishlist

** Changed in: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: ubuntu-meta (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Opinion

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Opinion

** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: New => In Progress

** Changed in: ubuntu-meta (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  Preinstall some new essential raspi packages in the official raspi
  images

Status in livecd-rootfs package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Opinion
Status in livecd-rootfs source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress

Bug description:
  [Impact]

  For 20.04.2, also as part of support for some new Pi variants (CM4,
  Pi400), we want to preinstall some new essential packages in our raspi
  images such as rpi-eeprom, raspberrypi-userland etc.

  This can be done in two possible ways. One is the 'old way', with a
  single change to livecd-rootfs adding the new packages. But what we'd
  like to propose this time is actually a more proper way, i.e.
  introducing device-specific raspi seeds and a raspi meta-package that
  would pull in all the needed dependencies. This way is better for the
  future, as if we decide we want to add new packages to existing raspi
  installations, we can do it easily by modifying the seeds and
  rebuilding meta. Currently we have no way like this.

  So the current approach includes changes in the following components:
   * The ubuntu and platform seeds (git branches)
   * ubuntu-meta package (adding ubuntu-server-raspi)
   * livecd-rootfs package (installing the raspi-server task)

  [Test Case]

  After accepting all the package into -proposed (and making sure the git seed 
changes are merged), run a raspi arm64 and armhf build. Check if the image 
boots. Confirm that the new images have the following seeded: rpi-eeprom, 
libraspberrypi-bin, flash-kernel, pi-bluetooth.
  Compare manifests between a normal, previous raspi image build and the one 
using seeds - check if nothing has been 'dropped'.

  Also, check if no other image builds have been affected and still
  build correctly, compare image manifests.

  [Where problems could occur]

  In its current form, as the update touches some livecd-rootfs
  auto/config paths, it's possible that a malformed cut-paste broke some
  edge case scenario, so it's good if other non-raspi builds are also
  checked for correctness. Seed changes are less likely to break
  anything, but manifests should be checked in case something got
  dropped by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Łukasz Zemczak]

It seems this behavior is expected, although probably insufficiently
documented. We will make sure to clear things out in various
documentation bits, but with 20.04 it has been decided that the Ubuntu
Desktop flavor will be shipping a HWE kernel by default from the start.
Apologies for this unclear situation, I have no idea how this got missed
in the announcements.

Per:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Ubuntu_Desktop

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly built with ‘linux-generic’ but the 20.04 and 20.04.1
  images were built with ‘linux-generic-hwe-20.04‘. This can be easily
  verified by looking at the iso manifest:

  https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
  amd64.manifest

  Note: old-release manifests (where 20.04 Beta and 20.04 reside) must
  be downloaded here:

  https://old-releases.ubuntu.com/releases/20.04/

  The expected behavior is for Ubuntu Focal users to remain on the 5.4
  series kernel unless they install with 20.04.2 or later images as
  indicated here:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  While not entirely updated it says “if one wants to remain on the
  original GA (General Availability) stacks, the options [include];
  Install from a previous
  12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
  release and update”.

  Jump just below that to the Focal specific notes and it says “The
  20.04.2 and newer point releases will ship with an updated kernel and
  X stack by default for the desktop”. Since 20.04.2 is not even due for
  release until next month it makes no sense for updates to the 5.8
  series kernel to be occurring unless the focal-proposed repos are
  enabled even if HWE protocols had been changed.

  It’s also worth noting that thankfully no accompanying HWE X stack is
  yet available in the repos. I say thankfully because my efforts at
  downgrading the X stack in 16.04 and 18.04 were never successful! But
  the lack of a matching X stack may explain the many complaints on the
  forums about broken graphics???

  It’s also worth noting that even the release notes say that “Ubuntu
  20.04 LTS is based on the long-term supported Linux release series
  5.4“.

  https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

  Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1
  are supposed to be supported with the 5.4 series kernel for the entire
  5 year life span:

  https://ubuntu.com/kernel/lifecycle

  The other flavors’ 20.04 and 20.04.1 images were all built correctly
  with ‘linux-generic’ with the possible exception of Ubuntu Studio
  which uses a kernel stack I’m not familiar with. I’m also uncertain
  about Ubuntu server because I’m simply not familiar with it.

  Original bug description below:

  ##

  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1899509] Update Released

[Łukasz Zemczak]

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

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 gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1899509

Title:
  Mouse/touchpad settings not applied on hotplug/reconnect/resume

Status in gnome-control-center:
  Unknown
Status in GNOME Settings Daemon:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  When I plug in a touchpad via USB, my chosen scrolling and speed
  settings are not applied, unless I adjust them again in the settings
  UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1899509/+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 1908158] 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/1908158

Title:
  Update to 3.38.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Groovy:
  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.38.2

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

  Updates on background painting, input devices settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+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 1908167] 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.10 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/1908167

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

Accepted pulseaudio into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.2-1ubuntu2.3 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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-groovy

** Tags added: 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/1908167

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1901609] Re: signond causes qprocess crash

[Łukasz Zemczak]

** Changed in: signon (Ubuntu Focal)
   Status: Incomplete => Opinion

** Changed in: signon (Ubuntu Focal)
   Status: Opinion => Fix Committed

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Released
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1908699] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.04.1 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1908699

Title:
  New bugfix release 20.2.6

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

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.9-2ubuntu1.1~20.04.1 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1902244

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.04.1 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.

** Changed in: xorg-server (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1908699] Re: New bugfix release 20.2.6

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.6-0ubuntu0.20.10.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: mesa (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

** Changed in: mesa (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  New bugfix release 20.2.6

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

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1849142] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1849142

Title:
  appindicator extension slows down GUI spamming the log with
  "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible
  to lookup icon"

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Using discord application, causes the shell to slowdown and trigger
  lots of "unable to lookup icon ..." errors

  [ Test case ]

  Install discord app:
   - snap install discord

  Run it, starting a call seems to trigger it more

  [ Regression potential ]

  Icons may not be loaded properly, there may be delays between a good
  icon and an invalid one (and vice-versa).

  ---

  Updated bug #1817073 about this, but it's not really the same since
  this does not crash the shell fully.

  When speaking in discord there is supposed to be an icon change on the
  appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable
  to lookup icon for discord1_40.

  The whole desktop freezes for a moment when talking in discord if the 
appindicator package is installed.
  Easily reproduced by joining a voice channel in discord and just doing stuff 
in the gnome ui, watching a video or whatever while talking.

  This is pretty bad since it leaves no choice but to uninstall gnome-
  shell-extension-appindicator and loosing that functionality if people
  wants to use discord on ubuntu.

  This is also reported on the extensions github page:
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171
  https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157

  Someone also made a video on youtube showing the problem:
  https://www.youtube.com/watch?v=ABavT7yXlso

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1849142/+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 1870795] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1870795

Title:
  Appindicator not showing under wayland

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  An app-indicator icon does not show when I login using the default
  gnome session (wayland).  If I choose the xorg session, the icon shows
  as normal.  Under wayland, the icon does appear if I lock my session
  then log back in.

  [ Test case ]

  Run a desktop session (better if Ubuntu wayland), ensure that all the
  startup-launched appindicators are showing in the status area.

  One affected indicator seems to be
  https://github.com/juliagoda/antimicroX/

  [ Regression potential ]

  Indicators may not load at all, wrong icons are shown instead.

  ---

  Upstream change: https://github.com/ubuntu/gnome-shell-extension-
  appindicator/pull/231

  
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  $ apt-cache policy gnome-session-wayland
  gnome-session-wayland:
    Installed: (none)
    Candidate: 3.36.0-2ubuntu1
    Version table:
   3.36.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  4 15:30:40 2020
  InstallationDate: Installed on 2019-12-15 (111 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+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 1896779] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1896779

Title:
  Appindicators use too much padding

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Padding on indicators is too wide, as per double-multiplication of the
  same, leading to very spread icons:

  https://user-
  images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea-
  9d65-ec9053290b2f.png

  [ Test case ]

  - Open various indicator, padding should be reduced to be consistent with 
other icons, for example:
    
https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png

  [ Regression potential ]

  Very low, there's just a style change to ensure we don't apply the
  very same padding two times.

  --

  Upstream fix: https://github.com/ubuntu/gnome-shell-extension-
  appindicator/pull/219

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896779/+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 1881669] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1881669

Title:
  Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been
  already finalized. Impossible to set any property to it

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Destroying an appindicator dbusmenu we fail with some (non-fatal)
  errors

  [ Test case ]

  Open/Close an application with appindicator
  Ensure that gnome-shell journal (journalctl -b0 /usr/bin/gnome-shell) doesn't 
show any error related to 

  Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While 
reading menu layout: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.
  Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy 
is null
  
DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9
  
wrapper@resource:///org/gnome/gjs/modules

  [ Regression potential ]

  Indicator may not show at all, but that was what we expect on
  destruction.

  ---

  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  jlquinn@cerberus:~/Videos$ apt-cache policy  
gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
    Installed: 18.04.1
    Candidate: 18.04.1
    Version table:
   *** 18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  This may be related to bug 1879016, but my stack trace is smaller and
  different.  I enabled the appindicator extension, and see the
  following my logs:

  Jun 01 17:24:15 cerberus gnome-shell[3318]: Object 
.Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. 
Impossible to set any property to it.
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for 
context 0x5582a28894b0 ==
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718eda00 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5a930 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7f6ee00
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718ee5e0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718eed80 b   
self-hosted:916 (0x7f70f00f12b8 @ 367)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718eee70 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190
 (0x7f6ee00adf78
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718efac0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5a800 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:176
 (0x7f6e
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718f06a0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5a760 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:170
 (0x7f6e
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #10 0x7ffc718f1290 I  
 resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #11 0x7ffc718f1a50 b  
 self-hosted:918 (0x7f70f00f12b8 @ 394)
  Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While 
reading menu layout: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.
  Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy 
is null
    

[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash

[Łukasz Zemczak]

Sadly I cannot release the focal SRU as it seems that the signon package
FTBFS on ppc64el there:

https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793

It seems to have built fine previously. Can someone take a look?

** Changed in: signon (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Incomplete
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1884396] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1884396

Title:
  Ubuntu freezing intermittently when the mega.nz appindicator is loaded

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Indicators using (big) pixmap icons cause the shell to use a lot of
  CPU computation, which interfere with user experience

  [ Test case ]

  - Install mega client from https://mega.nz/sync
  - Run it in ubuntu and ensure it doesn't block the UI while syncing
    (but even opening/closing the app should be enough to trigger

  Alternatively use this test tool:
   
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js

  Launch it with `gjs` and select the 'Crazy icons updates' menu item:
   - The shell should not hang

  [ Regression potential ]

  Icon updates may be late or not apply immediately (or at all).

  In general there has been a refactor of the iconCache, so internally
  it may happen that we load an icon more times, or that there could be
  an increase in RAM usage as per missing garbage collecting of it.

  

  I had similar issues when 20.04 was released, then it disappeared with
  an upgrade - but sadly it's back. I have short intermittent freezings
  of the OS. About every 15-30 seconds Ubunut freezes for a second or
  two. Eg when writing this description, the OS freezes every second
  word. When the freeze goes away the OS is snappy. I have tried
  switching between Wayland and Xorg - but the problem persists. If I
  write something when it freezes up the last
  character will be replicated many times -
  like what happened jut now. This
  problem did not show up in ubuntu 18.04 through 19.10. Hope U can
  fix this soon - using my laptop in unbearable.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 23:54:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
  InstallationDate: Installed on 2020-05-12 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M13
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C189
  dmi.product.version: M13
  dmi.sys.vendor: HUAWEI
  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
  

[Desktop-packages] [Bug 1896785] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1896785

Title:
  Exported DBus interface is missing info or using wrong names

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell when using this indicator should export the
  org.kde.StatusNotifierWatcher dbus interface, although some methods
  and properties are missing or invalid

  [ Test case ]

  Run:
   gdbus call --session --dest org.gnome.Shell --object-path 
/StatusNotifierWatcher \
   --method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher" 
ProtocolVersion

  -> Should return (<0>,)

  In particular, the API should contain

   gdbus introspect --session --dest org.gnome.Shell --object-path 
/StatusNotifierWatcher
  node /StatusNotifierWatcher {

     Default fdo properties stuff 

    interface org.kde.StatusNotifierWatcher {
  interface org.kde.StatusNotifierWatcher {
  methods:
    RegisterStatusNotifierItem(in  s service);
    RegisterStatusNotifierHost(in  s service);
  signals:
    StatusNotifierItemRegistered(s arg_0);
    StatusNotifierItemUnregistered(s arg_0);
    StatusNotifierHostRegistered();
    StatusNotifierHostUnregistered();
  properties:
    @org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
    readonly as RegisteredStatusNotifierItems = [ ... list of indicators 
path/obj-names ... ];
    readonly b IsStatusNotifierHostRegistered = true;
    readonly i ProtocolVersion = 0;
    };
  };

  In the old version we had an invalid "RegisterNotificationHost" method (not 
specified by specs nor used)
  We didn't expose the ProtocolVersion

  ---

  [ Regression potential ]

  We won't expose anymore some NON-STANDARD and NEVER USED dbus methods such as:
   - RegisterNotificationHost (was un-implemlented anyways)
   - ProtocolVersion (this was supposed to be a property, not a method)

  There are some changes to the interfaces xml files to follow the
  standard ones, but they don't involve any change, could happen though
  that we don't list a property that an indicator exposes lazily (don't
  think there are in real world).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896785/+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 1905756] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-desktop3 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 gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1905756

Title:
  SRU the current 3.36.8 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.8

  * Regression potential

  The update has some test and translations fixes and a change the
  version, check that translations and version display in settings are
  correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1905756/+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 1900452] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-drivers-common
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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1900452

Title:
  /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu-
  
drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * Listing the supported drivers can fail if the
 linux-restricted-modules for it are not available in the archive.

   * These changes unify the code for listing drivers (whether --gpgpu
 is passed in or not) and make it more robust.
   
   
  [Test Case]

   * Install ubuntu-drivers-common (1:0.8.6.2) from -proposed.
   
   * Call "ubuntu-drivers list" and "ubuntu-drivers list --gpgpu",
 and make sure that neither crashes ubuntu-drivers.

  [Regression Potential]

   * Low, the code should catch all the KeyErrors now.

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ubuntu-drivers-common.  This problem was most recently seen with package 
version 1:0.8.4~0.20.04.3, the problem page at 
https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d 
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/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+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 1901609] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for signon 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 signon in Ubuntu.
https://bugs.launchpad.net/bugs/1901609

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1903329] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for librsvg 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 librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1903329

Title:
  SRU the current 2.48.9 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, which fixes a number of
  issues, including a regression[1] since librsvg 2.40.x which was
  shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant
  changes between Ubuntu 20.04's current librsvg 2.48.7 (that version
  was also introduced by an SRU back in July[3]) and the current version
  2.48.9. The complete list of changes is available on GNOME GitLab[4].

  * Test case

  The update is part of GNOME stable updates[5].

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

  * Notes about this report

  This is my first SRU request (and at the same time my first launchpad
  bug report). I'm not really familiar with the whole SRU process which
  is why I first asked about it on Ubuntu's official discourse forum[6].
  Canonical's Sebastien Bacher encouraged me to open this ticket. I've
  copied over some parts of the last librsvg SRU ticket[3]. I hope this
  is fine.

  Thanks for considering this SRU.

  [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642

  [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  [3]: https://bugs.launchpad.net/bugs/1884326

  [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9

  [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get-
  librsvg2-microrelease-update-into-focal-updates/19238

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.1-1~ubuntu0.20.04.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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1902244

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics

[Łukasz Zemczak]

This SRU is blocked from being accepted by an already existing ubuntu-
drivers-common waiting for validation in groovy-proposed (SRU bug LP:
#1900452). We'd need to first get that one verified and released before
considering the next one.

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

Title:
  SRU: Backport the latest developments on drivers detection and hybrid
  graphics

Status in OEM Priority Project:
  New
Status in nvidia-prime package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in nvidia-prime source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in ubuntu-drivers-common source package in Groovy:
  In Progress

Bug description:
  As we introduced the "-server" NVIDIA drivers, and the concept of
  "LTSB" (Long Term Support Branch) and "NFB" (New Feature Branch)
  releases, the detection logic behind ubuntu-drivers needs an update to
  make the correct choices for the user.

  The introduction of the NVIDIA 450 series, also added runtime power
  management, which greatly improves user experience on systems with
  hybrid graphics, and allows greater power savings. When supported, on-
  demand mode and runtime power management are the default. Both gpu-
  manager and ubuntu-drivers in ubuntu drivers common, and the tools in
  the nvidia-prime package need updating as a result.

  Only the components in Ubuntu 20.10 require a fairly small diff for
  the backport. The rest is a direct sync of the 1:0.8.6.3 release in
  21.04.

  [Impact]

  * The ubuntu-drivers tool might install the wrong driver, or, in some
  cases, crash, if the new -server drivers are available.

  * The new runtime power management can't be used even when the
  hardware (Turing GPUs or newer) supports it.

  * We want to the default drivers to be Long Term support releases.
  Users may still pick different drivers manually.

  [Fix]

  * The code in Ubuntu 21.04 includes essential bug fixes, and more test
  cases in the test suite, to make sure that driver installation is more
  robust, and more accurate (LTSB vs NFB releases, and non-server vs
  -server releases).

  * ubuntu-drivers, gpu-manager, and prime-select now all support
  runtime power management.

  [Test Case]
  Install ubuntu-drivers-common and nvidia-prime from proposed, and check the 
following:

  1) ubuntu-drivers debug

  2) Make sure no nvidia driver is installed (sudo apt-get --purge
  remove '*nvidia*', and try installing an nvidia driver with "sudo
  ubuntu-drivers install"

  3) Reboot your system

  4) [optional] If you are running on a hybrid laptop, you can check if
  your system supports runtime power management:

  sudo prime-select on-demand

  (if you are already in "on-demand" mode, select "intel" mode first,
  then try "on-demand" again)

  5) If you followed step 4, reboot again

  6) Attach your /var/log/gpu-manager.log

  [Regression Risk]
  Medium, while this code includes many fixes, it needs careful testing.

  
  == Changes ==

  Only the components in Ubuntu 20.10 require a fairly small diff for
  the backport. The rest is a direct sync of the 1:0.8.6.3 release in
  21.04.

  == Ubuntu 20.10 ==

  ubuntu-drivers-common (1:0.8.6.3~0.20.10.1) groovy; urgency=medium

    * UbuntuDrivers/detect.py,
  tests/test_ubuntu_drivers.py:
  - Prefer LTSB releases over NFB ones for non gpgpu cases too.
    * gpu-manager.c:
  - Make it possible to force runtimepm by creating the
    /etc/u-d-c-nvidia-runtimepm-override file.
  - Make on-demand default on nvidia >= 450, when no
    previous settings are available.

  nvidia-prime (0.8.15.1~0.20.10.1) groovy; urgency=medium

    [ Anthony Fok ]
    * Remove obsolete udev rules during `postrm upgrade` too

  == Ubuntu 20.04 ==

  ubuntu-drivers-common (1:0.8.6.3~0.20.04.1) focal; urgency=medium

    * Backport 1:0.8.6.3 (LP: #1904583).

  nvidia-prime (0.8.15.1~0.20.04.1) focal; urgency=medium

    [ Alberto Milone ]
    * prime-select:
  - Enable runtimepm in on-demand mode if supported (LP: #1895855).
  - Disable workaround for on-demand mode.
  - Enable KMS if runtimepm is supported.

    [ Anthony Fok ]
    * Remove obsolete udev rules during `postrm upgrade` too

    [ Kai-Heng Feng ]
    * prime-select: Remove udev rules

  == Ubuntu 18.04 ==

  ubuntu-drivers-common (1:0.8.6.3~0.18.04.2) bionic; urgency=medium

    * Backport 1:0.8.6.3 (LP: #1904583).
    * gpu-manager.c: add missing PCI_CAP_ID_NULL definition

  nvidia-prime (0.8.15.1~0.18.04.1) bionic; urgency=medium

    * Backport 0.8.15.1 (LP: #1904583).

To manage notifications about 

[Desktop-packages] [Bug 1904859] Re: [snap] cannot send file from Nautilus

[Łukasz Zemczak]

Please include information about what testing has been performed as part
of the verification and on which versions of the package, as per the SRU
policy. Thank you!

** Tags removed: verification-done-focal
** Tags added: verification-needed-focal

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

Title:
  [snap] cannot send file from Nautilus

Status in nautilus-sendto package in Ubuntu:
  Fix Released
Status in nautilus-sendto source package in Focal:
  Fix Committed
Status in nautilus-sendto source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Nautilus->sendto fails to use the thunderbird snap command

  * Test case
  On a Ubuntu default session
  $ snap install thunderbird
  $ nautilus
  $ right click on a file and select the sendto entry

  -> thunderbird should be started with a composer dialog and the
  selected attachment included

  * Regression potential
  The patch removes an old hack that parsed and changed the thunderbird 
command, verify that thunderbird is still correctly start using it from 
different source (snap, deb, flatpak?)

  -

  
  TB 78.5.0 snap
  Focal

  Nothing happens when I right-click on a file (using Nautilus) from my
  home and choose 'send to'. I did not have such a problem using TB deb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+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 1904478] 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/1904478

Title:
   [SRU] libreoffice 7.0.3 for groovy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.0.3 is in its third bugfix release of the 7.0 line: 
   https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.3_release

   * Version 7.0.2 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.2 see the list of bugs fixed in the release candidate (that's a 
total of 92 bugs):
   https://wiki.documentfoundation.org/Releases/7.0.3/RC1#List_of_fixed_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.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

* A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_70/1450/

* More information about the upstream QA testing can be found here:
  * Automated tests - 
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests - 
https://wiki.documentfoundation.org/Development/UITests
  * Regression tests - 
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests - 
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/amd64/libr/libreoffice/20201110_032638_c4409@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/arm64/libr/libreoffice/20201110_220300_5fc9e@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/armhf/libr/libreoffice/20201110_083102_d4dab@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/ppc64el/libr/libreoffice/20201110_054031_89cb8@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/s390x/libr/libreoffice/20201110_020527_366f6@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 92 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/1904478/+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 1897224] 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/1897224

Title:
  Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
  display)

Status in Mutter:
  Unknown
Status in snapd:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Won't Fix
Status in mutter source package in Groovy:
  Fix Released
Status in snapd source package in Groovy:
  Won't Fix
Status in mutter source package in Hirsute:
  Fix Released
Status in snapd source package in Hirsute:
  Won't Fix

Bug description:
  [Impact]

   * Users who select the Wayland session on Ubuntu 20.10 cannot run snap
     confined X11 applications, due to gnome-shell no longer listening on an
     abstract socket for connections.

   * The fix, which has been accepted into upstream's gnome-3-38 branch
     reverts the change removing the abstract socket, and fixes the bug that
     prompted it's removal:

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

  [Test Case]

   * Start with a stock Ubuntu 20.10 desktop install.

   * At the GDM login screen, after selecting your user account use the gear
     icon to select the "Ubuntu on Wayland" session, and log in.

   * Ensure Chromium is installed by running "sudo snap install
  chromium".

   * Try to run "chromium" from the terminal.  Without the fix, it will fail
     with the error "Unable to open X display".  With the fix applied, it
     will launch as normal.

  [Regression Potential]

   * The patch modifies the logic gnome-shell uses to launch Xwayland.  So
     there is a potential that the change could break X11 application
     support on the Wayland session.

   * The default configuration for gnome-shell is to launch Xwayland on
     session start, so it should be immediately obvious if there are
     problems.

   * In addition to checking snapped X11 apps like Chromium, verify that a
     few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).

  [Other Info]

   * Running "ss -xlp | grep Xwayland" should show that it is listening on
     both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
     "@/tmp/.X11-unix/X0" (the abstract socket).

  ---
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when running 
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:

  > chromium
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[Łukasz Zemczak]

There are still some outstanding autopkgtest issues (as mentioned in
comment #11). Can anyone take a look at those? I can't release it
without resolved test issues.

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

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Confirmed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1900009] 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/199

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Invalid
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  Release: Ubuntu Groovy Gorilla (development branch) 20.10
  Package version: 3.38.1-1ubuntu1

  [ Impact ]

  When I tile windows using edge tiling, I want the window to tile on
  the same edge that I brought it to, however, if the window is mostly
  in monitor 1 when I try to tile it to the left (or right) edge of
  monitor 2, the window will tile to the left (or right) edge of monitor
  2.

  This happens on both my computer with an Nvidia GPU on x11 and my
  laptop using Intel integrated graphics on Wayland.

  [ Test case ]

  - In multi-monitor setup, grab a tile edge to the side where the other 
monitor is
  - The window should not be moved to the other monitor

  [ Regression potential ]

  Windows may be tiled to the wrong monitor once created

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

Title:
  xterm resize is wonky

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in xterm package in Ubuntu:
  Invalid
Status in mutter source package in Groovy:
  Fix Released
Status in xterm source package in Groovy:
  Invalid
Status in mutter source package in Hirsute:
  Fix Released
Status in xterm source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]

  When I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  [ Test case ]

  - Start Xterm
  - Resize the window from its top/left corner
  - It should resize normally, and not act as shown in

https://gitlab.gnome.org/GNOME/mutter/uploads/3c19763b7748ce76b0ba2958cde7636b/Screencast_from_02-04-19_14_03_24.webm

  [ Regression potential ]

  Windows resizing might not work correctly

  ---

  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  

[Desktop-packages] [Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.

[Łukasz Zemczak]

Normally we would need the version number of the package used during
verification, but I'll accept the validation as is for now.

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Invalid
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  Release: Ubuntu Groovy Gorilla (development branch) 20.10
  Package version: 3.38.1-1ubuntu1

  [ Impact ]

  When I tile windows using edge tiling, I want the window to tile on
  the same edge that I brought it to, however, if the window is mostly
  in monitor 1 when I try to tile it to the left (or right) edge of
  monitor 2, the window will tile to the left (or right) edge of monitor
  2.

  This happens on both my computer with an Nvidia GPU on x11 and my
  laptop using Intel integrated graphics on Wayland.

  [ Test case ]

  - In multi-monitor setup, grab a tile edge to the side where the other 
monitor is
  - The window should not be moved to the other monitor

  [ Regression potential ]

  Windows may be tiled to the wrong monitor once created

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/199/+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 1903936] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for snapd-glib 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 snapd-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1903936

Title:
  Update to 1.58

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Committed
Status in snapd-glib source package in Groovy:
  Fix Released
Status in snapd-glib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Changes to error message carry low risk of introducing an issue if such an 
error occurred. GIR annotation changes fix a call that was previously broken, 
and is unlikely to make that any worse.
  Risks are mitigated by automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libglvnd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.1 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.

** Changed in: libglvnd (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1904478] Re: [SRU] libreoffice 7.0.3 for groovy

[Łukasz Zemczak]

Hello Heather, or anyone else affected,

Accepted libreoffice into groovy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:7.0.3-0ubuntu0.20.10.1
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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: libreoffice (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
   [SRU] libreoffice 7.0.3 for groovy

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.0.3 is in its third bugfix release of the 7.0 line: 
   https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.3_release

   * Version 7.0.2 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.2 see the list of bugs fixed in the release candidate (that's a 
total of 92 bugs):
   https://wiki.documentfoundation.org/Releases/7.0.3/RC1#List_of_fixed_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.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

* A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_70/1450/

* More information about the upstream QA testing can be found here:
  * Automated tests - 
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests - 
https://wiki.documentfoundation.org/Development/UITests
  * Regression tests - 
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests - 
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/amd64/libr/libreoffice/20201110_032638_c4409@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/arm64/libr/libreoffice/20201110_220300_5fc9e@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/armhf/libr/libreoffice/20201110_083102_d4dab@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/ppc64el/libr/libreoffice/20201110_054031_89cb8@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/s390x/libr/libreoffice/20201110_020527_366f6@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 92 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
  

[Desktop-packages] [Bug 1896334] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for yaru-theme 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1896334

Title:
  SRU 3.36.6

Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  Incomplete
Status in yaru-theme 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/gnome-shell/-/commits/3.36.6

  Since the theme side of the project in ubuntu is shipped via Yaru
  theme, that project is included in the SRU.

  The changes involving yaru here are ONLY gnome-shell upstream changes applied 
to the Yaru sources, as per this we can consider them also part of the GNOME 
release.
  In fact:
  - Ubuntu's GNOME shell uses a Yaru theme based on upstream
gnome-shell This theme basically takes the shell's data/ directory,
applies some diffs and generates a gresource file out of it, that it's
then loaded on startup (in place of the upstream one).
  - GNOME Shell applied some fixes to the theme (se its data/
directory diffs)
  - In order to get those fixes in Ubuntu main session we have to sync
the upstream changes applied to such dir to yaru's src/gnome-shell
path
  - You can easily compare the diffs applied there to match the ones
happening in its upstream counterpart.

  The yaru-theme's `gnome-shell/upstream` directory is just for documentation 
and
  to allow three way merges when updating to new versions of gnome-shell,
  and it is not used for generating the final packages at all

  [ 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 popup-grab handling, gdm view fixes,
  lockscreen display changes in some hw, extensions updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1872950] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for nvidia-graphics-
drivers-340 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/1872950

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

[Łukasz Zemczak]

Though I do understand it is a bit annoying that smartcard login on
bionic doesn't work, it worries me that fixing this would involve a lot
of backporting. This isn't a regression and bionic has been like this
from day 0, right? Do we have an understanding on how wanted this is on
bionic?

I'm not saying no, but right now I wouldn't be comfortable in such a big
set of changes without a rationale. I would rather recommend them to
switch to focal and fixing it there. But I'd have to know more.

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in gdm:
  New
Status in GNOME Settings Daemon:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Won't Fix
Status in pam source package in Bionic:
  Invalid
Status in gdm3 source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  New
Status in pam source package in Focal:
  Invalid
Status in gdm3 source package in Groovy:
  Confirmed
Status in gnome-settings-daemon source package in Groovy:
  New
Status in pam source package in Groovy:
  Invalid

Bug description:
  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 14:30:30 2020
  InstallationDate: Installed on 2016-05-23 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865226/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/20.2.1-1~ubuntu0.20.04.1 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.

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

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libclc into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190827-7~ubuntu0.20.04.1
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.

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

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Confirmed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Łukasz Zemczak]

Hello ppp, or anyone else affected,

Accepted nvidia-graphics-drivers-340 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 removed: verification-done verification-done-groovy
** Tags added: verification-needed verification-needed-groovy

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1893300] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for system-config-printer
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 system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Focal:
  Fix Committed
Status in system-config-printer source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Very Low, if something went wrong in the change, then this issue happened 
again, due to this snippet will only be called during printer removed event.

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Łukasz Zemczak]

Whoops, I also missed that bracket typo while reviewing the package in
the SRU queue. I think we might need to re-upload with that fixed, as
otherwise we're missing one patch from this version.

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1900729] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-terminal 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 gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Fix Committed
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1902829] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-shell 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1902829

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1902829/+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 1891632] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for network-manager 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1891632

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  GitLab -
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1902244] Please test proposed package

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libdrm into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.102-1ubuntu1~20.04.1 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1902244

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  New
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.1 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-11 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-11/1:11.0.0-2~ubuntu20.04.1 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.

** Changed in: llvm-toolchain-11 (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

** Changed in: libdrm (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  New
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1896334] Please test proposed package

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted yaru-theme into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/yaru-
theme/20.04.10.1 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1896334

Title:
  SRU 3.36.6

Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  Incomplete
Status in yaru-theme source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6

  Since the theme side of the project in ubuntu is shipped via Yaru
  theme, that project is included in the SRU.

  The changes involving yaru here are ONLY gnome-shell upstream changes applied 
to the Yaru sources, as per this we can consider them also part of the GNOME 
release.
  In fact:
  - Ubuntu's GNOME shell uses a Yaru theme based on upstream
gnome-shell This theme basically takes the shell's data/ directory,
applies some diffs and generates a gresource file out of it, that it's
then loaded on startup (in place of the upstream one).
  - GNOME Shell applied some fixes to the theme (se its data/
directory diffs)
  - In order to get those fixes in Ubuntu main session we have to sync
the upstream changes applied to such dir to yaru's src/gnome-shell
path
  - You can easily compare the diffs applied there to match the ones
happening in its upstream counterpart.

  The yaru-theme's `gnome-shell/upstream` directory is just for documentation 
and
  to allow three way merges when updating to new versions of gnome-shell,
  and it is not used for generating the final packages at all

  [ 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 popup-grab handling, gdm view fixes,
  lockscreen display changes in some hw, extensions updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1896334] Re: SRU 3.36.6

[Łukasz Zemczak]

While the gnome-shell reverse dependency shell extensions regression
mitigation discussion is still in progress, I think we can unblock the
yaru-theme portion as it's unrelated to this. I have been told this
update is safe to go in without the gnome-shell part, and is needed for
some future fixes.

** Changed in: yaru-theme (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU 3.36.6

Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  Incomplete
Status in yaru-theme source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6

  Since the theme side of the project in ubuntu is shipped via Yaru
  theme, that project is included in the SRU.

  The changes involving yaru here are ONLY gnome-shell upstream changes applied 
to the Yaru sources, as per this we can consider them also part of the GNOME 
release.
  In fact:
  - Ubuntu's GNOME shell uses a Yaru theme based on upstream
gnome-shell This theme basically takes the shell's data/ directory,
applies some diffs and generates a gresource file out of it, that it's
then loaded on startup (in place of the upstream one).
  - GNOME Shell applied some fixes to the theme (se its data/
directory diffs)
  - In order to get those fixes in Ubuntu main session we have to sync
the upstream changes applied to such dir to yaru's src/gnome-shell
path
  - You can easily compare the diffs applied there to match the ones
happening in its upstream counterpart.

  The yaru-theme's `gnome-shell/upstream` directory is just for documentation 
and
  to allow three way merges when updating to new versions of gnome-shell,
  and it is not used for generating the final packages at all

  [ 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 popup-grab handling, gdm view fixes,
  lockscreen display changes in some hw, extensions updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Łukasz Zemczak]

Hello Darko, or anyone else affected,

Accepted gnome-terminal into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
terminal/3.38.0-1ubuntu1.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: gnome-terminal (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags removed: verification-failed verification-failed-groovy
** Tags added: verification-needed verification-needed-groovy

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1902829] Please test proposed package

[Łukasz Zemczak]

Hello Gunnar, or anyone else affected,

Accepted gnome-shell into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.1-1ubuntu1.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1902829

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1902829/+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 1902829] Re: Missing "Mobile Broadband" menu item

[Łukasz Zemczak]

Not the best regression potential analysis, but this time I'll accept it
as is due to the nature of the regression and fix. But please try
following the guidelines more as per the specification in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1902829/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Łukasz Zemczak]

Hello ppp, or anyone else affected,

Accepted nvidia-graphics-drivers-340 into groovy-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Committed

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1901318] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for usb-modeswitch 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 usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1901318

Title:
  needs to depend on tcl (not just tcl8.6)

Status in usb-modeswitch package in Ubuntu:
  Fix Committed
Status in usb-modeswitch source package in Groovy:
  Fix Released

Bug description:
  * Impact

  the usb-modeswitch dispatcher script fails to start on the default
  installation because it uses tclsh unversioned while we depends on
  tcl8.6

  
  * Test Case

  $ /usr/sbin/usb_modeswitch_dispatcher

  shouldn't bail out on an interpreter error

  (or better, test that plugging an usb modem is correctly handled)

  
  * Regression potential

  The script was bailing out due to a missing intepreter before so the
  code wasn't tested, it's possible that it triggers errors or could
  interact with the system in some way. The dispatcher reacts to udev
  events when an usb modem is connected, so try to use one of those and
  make sure that there is no negative effect (and if possible that the
  modem gets correctly handled)

  --

  
  the package currently depends on tcl8.6, but 
/usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which 
isn't provided by tcl8.6, so it likely would need to depend on something like 
tcl (= 8.6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+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 1901318] Re: needs to depend on tcl (not just tcl8.6)

[Łukasz Zemczak]

By looking at the comments (and comment #20 especially) it looks like
this is not caused by this upload. Releasing.

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

Title:
  needs to depend on tcl (not just tcl8.6)

Status in usb-modeswitch package in Ubuntu:
  Fix Committed
Status in usb-modeswitch source package in Groovy:
  Fix Released

Bug description:
  * Impact

  the usb-modeswitch dispatcher script fails to start on the default
  installation because it uses tclsh unversioned while we depends on
  tcl8.6

  
  * Test Case

  $ /usr/sbin/usb_modeswitch_dispatcher

  shouldn't bail out on an interpreter error

  (or better, test that plugging an usb modem is correctly handled)

  
  * Regression potential

  The script was bailing out due to a missing intepreter before so the
  code wasn't tested, it's possible that it triggers errors or could
  interact with the system in some way. The dispatcher reacts to udev
  events when an usb modem is connected, so try to use one of those and
  make sure that there is no negative effect (and if possible that the
  modem gets correctly handled)

  --

  
  the package currently depends on tcl8.6, but 
/usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which 
isn't provided by tcl8.6, so it likely would need to depend on something like 
tcl (= 8.6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+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 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10

[Łukasz Zemczak]

** Tags removed: regression-proposed

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

Title:
  usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I recently allowed groovy-proposed package install of usb-modeswitch 
2.6.1-1ubuntu2, because the default one which came with the system was useless.

  * What you expected to happen:

  My USB drive should be detected as mobile broadband connection faster
  as possible without any unpleasant inconvenience after boot stage.

  *  What happened instead:

  It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be 
truly ready for mobile broadband connection. Until then, any tries to connect 
to internet even if it appears to be ready on system menu or network settings - 
mobile broadband - results in failure. When I try to connect in that period, 
the USB mass is ejected and prepared for ready mode automatically after few 
secs beyond every time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-11-05 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Tags: groovy third-party-packages
  Uname: Linux 5.8.0-26-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1901460] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for im-config 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 im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1901460

Title:
  Back off also if IBus on Budgie

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  Fix Committed
Status in im-config source package in Groovy:
  Fix Released
Status in im-config package in Debian:
  Unknown

Bug description:
  [Impact]

  This is a follow-up of bug #1893551, where we stopped im-config from
  interfering in case of a GNOME desktop. Even if Budgie uses the same
  applicable GNOME components, we didn't change it for Budgie at that
  time since IBus input methods were not reliably reflected in the
  Keyboard Layout applet.

  However, that issue has been fixed now. Also, the most common ibus
  crash type is now Budgie related:

  https://errors.ubuntu.com/problem/f0690c64c769b06c2ce0513667bd7a52f53ebd27

  We have reasons to hope that letting im-config back off also for
  Budgie will reduce the number of crashes as has already happened for
  standard Ubuntu (see comment #2 at bug #1879958). At least we have
  nothing to lose by trying...

  [Test case]

  I'm not aware of a way to reproduce the crashes, and thus can't
  confirm in advance that the proposed upload makes a difference.

  However, we should confirm that IBus input methods can be used
  smoothly on Budgie:

  * Install Budgie in a VM

  * Install the version of im-config from -proposed

  * Install ibus-libpinyin

  * Add the Keyboard Layout applet in Budgie Desktop Settings

  * Re-login

  * Add Intelligent Pinyin to the input sources in Settings

  * Confirm that switching between the input sources works
without problems and that you can input Chinese characters

  [Regression risk]

  When used, im-config does two things: It launches an IM framework and
  sets some IM related variables. The test case serves the purpose of
  confirming that those things are properly accomplished without im-
  config in case of IBus. So given a successful verification the
  regression risk due to the proposed change should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1901460/+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 1900729] Proposed package removed from archive

[Łukasz Zemczak]

The version of gtk+3.0 in the proposed pocket of Groovy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  New
Status in gnome-terminal source package in Groovy:
  Triaged
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1900729] Proposed package removed from archive

[Łukasz Zemczak]

The version of gtk+3.0 in the proposed pocket of Groovy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  New
Status in gnome-terminal source package in Groovy:
  Triaged
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

[Łukasz Zemczak]

Hello hugh, or anyone else affected,

Accepted system-config-printer into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/system-config-printer/1.5.12-0ubuntu1.1 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.

** Changed in: system-config-printer (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Focal:
  Fix Committed
Status in system-config-printer source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Very Low, if something went wrong in the change, then this issue happened 
again, due to this snippet will only be called during printer removed event.

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

[Łukasz Zemczak]

Hello hugh, or anyone else affected,

Accepted system-config-printer into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/system-config-printer/1.5.12-0ubuntu3.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: system-config-printer (Ubuntu Groovy)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Focal:
  Fix Committed
Status in system-config-printer source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Very Low, if something went wrong in the change, then this issue happened 
again, due to this snippet will only be called during printer removed event.

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

[Łukasz Zemczak]

hm, I would appreciate a bit more information in the Regression
Potential section. In this section we need some analysis on where to
look for regressions after this lands into the archive. This should be
an exercise, thinking: "hmmm, if we change these parts of the code, what
could go wrong? Where should we expect regressions, new bugs?"

** Changed in: system-config-printer (Ubuntu Groovy)
   Status: Fix Committed => Incomplete

** Changed in: system-config-printer (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Focal:
  Incomplete
Status in system-config-printer source package in Groovy:
  Incomplete

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1901367] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-wallpapers 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 ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1901367

Title:
  Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from
  wallpaper chooser

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is
  shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser,
  because of a typo in the two listing files.

  I probably renamed the file but forgot to update this.

  [ Fix ]

  Fix the typo by replacing a space character with an underscore.

  [ QA ]

  Right click on the desktop, ideally on a clean system so you don't
  have other clutter. Pick "Change Background...". See that the
  Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper
  isn't there. I'll attach the picture down below so you can see what it
  will look like.

  Install the SRU and check that it now appears and becomes selected.

  [ Regression potential ]

  The code in Settings checks that the wallpaper exists before showing
  it. So if you can see it it must be there - there's no chance you can
  set a wallpaper which simply won't work via this UI.

  Thinking laterally, it might be considered a regression if this
  wallpaper is inappropriate in some way - like the resolution is too
  low, or it renders badly for another reason. Make sure it looks right,
  since this is the first time it's getting shown.

  [ Original description ]

  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+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 1901353] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-wallpapers 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 ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1901353

Title:
  Ubuntu Default Greyscale Wallpaper Sym Link Broken

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  I forgot to update the symlink for the greyscale default gorilla
  wallpaper and so it doesn't show up in the wallpaper chooser.

  [ Fix ]

  Fix the symlink.

  [ QA ]

  Right click on the desktop, ideally on a clean system so you don't
  have other clutter. Pick "Change Background...". See that the
  greyscale groovy wallpaper isn't there.

  Install the SRU and check that it now appears and becomes selected.

  [ Regression potential ]

  The code in Settings checks that the wallpaper exists before showing
  it. So if you can see it it must be there - there's no chance you can
  set a wallpaper which simply won't work via this UI.

  Thinking laterally, it might be considered a regression if this
  wallpaper is inappropriate in some way - like the resolution is too
  low, or it renders badly for another reason. Make sure it looks right,
  since this is the first time it's getting shown.

  [ Original description ]

  The sym link still links to the nonexistent Focal greyscale wallpaper.

  How to reproduce:

  Try to set the wallpaper to the default greyscale in Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-wallpapers 20.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 21:40:40 2020
  Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+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 1900812] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1900812

Title:
  pulseaudio crashed with SIGSEGV in
  pa_sink_move_streams_to_default_sink() from report_jack_state() from
  mixer_class_event() from hctl_elem_event_handler() from
  snd_hctl_elem_throw_event()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  * Impact

  There is a segfault issue started with the recent update

  * Test case

  We don't have specific steps to trigger the issue so test for regression and 
verify that reports stop on
  https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0

  * Regression potential

  The regression was created by a fix for gnome-control-center device
  selection issues, check that the settings still work correctly,
  allowing to change devices and showing the active one as selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1900812/+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 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken

[Łukasz Zemczak]

Hey everyone! Thank you for your verification. The version numbers in
the validation comments makes me a bit confused - the groovy SRU is
20.10.3-0ubuntu0.20.10.1, even though all verification seems to have
been done on 20.10.3-0ubuntu1? Which packages have been tested on groovy
in that case?

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

Title:
  Ubuntu Default Greyscale Wallpaper Sym Link Broken

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers source package in Groovy:
  Fix Committed

Bug description:
  [ Description ]

  I forgot to update the symlink for the greyscale default gorilla
  wallpaper and so it doesn't show up in the wallpaper chooser.

  [ Fix ]

  Fix the symlink.

  [ QA ]

  Right click on the desktop, ideally on a clean system so you don't
  have other clutter. Pick "Change Background...". See that the
  greyscale groovy wallpaper isn't there.

  Install the SRU and check that it now appears and becomes selected.

  [ Regression potential ]

  The code in Settings checks that the wallpaper exists before showing
  it. So if you can see it it must be there - there's no chance you can
  set a wallpaper which simply won't work via this UI.

  Thinking laterally, it might be considered a regression if this
  wallpaper is inappropriate in some way - like the resolution is too
  low, or it renders badly for another reason. Make sure it looks right,
  since this is the first time it's getting shown.

  [ Original description ]

  The sym link still links to the nonexistent Focal greyscale wallpaper.

  How to reproduce:

  Try to set the wallpaper to the default greyscale in Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-wallpapers 20.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 21:40:40 2020
  Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+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 1896919] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-control-center
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1896919

Title:
  [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the
  combo list after selecting the hdmi/dp audio in the g-c-c

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Released
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  After we plugging a hdmi/dp monitor with audio capability, we could
  select hdmi audio as output device in the g-c-c, but after we do
  that, the profile combo list will show up in the g-c-c and this combo
  list is empty, it should be stereo-hdmi by default according to 18.04

  [Fix]
  Backport a fix from g-c-c upstream, after applying this patch, the
  combo list update signals will be recevied after the pa finishes the
  changing active profile.

  [Test Case]
  Plug the hdmi/dp monitor with audio capability, then choose hdmi audio
  as active output device from g-c-c, we will find the profile combo list
  has hdmi-steoreo as the default profile. This is same as 18.04.

  [Regression Risk]
  It is possible to make the output and input device can't work after
  applying this patch, that is because the active profile is not set as
  our expected. But this possibility is very low, I tested this patch on
  2 lenovo and 2 dell laptops, there is no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1896919/+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 1873378] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-control-center
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873378

Title:
  gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Released

Bug description:
  * Impact

  The user panel hits a segfault sometimes

  * Test case

  Check that reports stop on 
  https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca

  * Regression potential

  The change is in the user panel's user initial avatar generation,
  check that the default image for profiles without an avatar is still
  generated

  ---

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Package version: 1:3.36.1-1ubuntu4

  The application was running in the background, with only Chrome running at 
the same time.
  It's a mid-2014 MacBook Pro, so some drivers are not very stable and can 
cause this kind of issues.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 23:41:09 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-08-10 (250 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d
   PC (0x7f303176e6e4) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r15d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   generate_default_avatar ()
   ?? ()
   ?? ()
  Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize()
  UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1873378/+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 1873184] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-control-center
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873184

Title:
  Wired and wireless connection details have not enough height and items
  overlap

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Released
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  * Impact

  The details of the connection settings sometime overlap

  * Test case

  Connect the computer to a wired ethernet, go to settings and check the
  connection details, the items should be displayed separated and not
  overlapping

  * Regression potential

  Check that the connection details dialog is correctly displayed on
  different typo of connections, the change is in the layout of the
  elements so it could impact the layout in other cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+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 1887707] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-control-center
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1887707

Title:
  Disabling fractional scaling after selecting another integer scaling
  may unselect user choice

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  If selecting another integer scaling after disabling fractional
  scaling

  [ Test case ]

  When running Ubuntu session under X11, in gnome-control-center, display panel:
   - Ensure 100% scaling is selected and applied
   - Enable fractional scaling
   - Select 200% scaling (or bigger integer scaling)
     - Green "Apply" button should be visible and clickable
   - Deactivate fractional scaling
     - Green "Apply" button stays and fractional scaling isn't disabled until 
applied

  Repeat with inverted scaling orders (applying 200% and then selecting
  100%)

  Currently, once another integer value is selected, we just deselect
  the user choice and restore the previous one, deactivating the
  fractional scaling promtply.

  [ Regression potential ]

  - Displays are wrongly disposed and configured when fractional scaling is 
enabled
  - Configurations are not applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887707/+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 1887731] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for gnome-control-center
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1887731

Title:
  gnome-control-center crashes in cc_display_config_manager_get_current
  -> get_valid_monitors -> get_dock_monitor ->
  update_dock_placement_combo_selection

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  Fix Released

Bug description:
  * Impact

  The appearance settings hit a segfault sometime

  * Test case

  The error reports should stop on
  https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 

  * Regression potential

  Check that that appearance settings still work correctly, including
  configuring on which screen the dock should be displayed

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.36.4-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 
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/ubuntu/+source/gnome-control-center/+bug/1887731/+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 1900452] Re: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu-drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_

[Łukasz Zemczak]

Can we get this bug description SRUified? We'd need to know if there is
some reliable test case for it or not.

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

Title:
  /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu-
  
drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ubuntu-drivers-common.  This problem was most recently seen with package 
version 1:0.8.4~0.20.04.3, the problem page at 
https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d 
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/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+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 1901367] Re: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser

[Łukasz Zemczak]

Hello Tanupy, or anyone else affected,

Accepted ubuntu-wallpapers into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
wallpapers/20.10.3-0ubuntu0.20.10.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from
  wallpaper chooser

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers source package in Groovy:
  Fix Committed

Bug description:
  [ Description ]

  The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is
  shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser,
  because of a typo in the two listing files.

  I probably renamed the file but forgot to update this.

  [ Fix ]

  Fix the typo by replacing a space character with an underscore.

  [ QA ]

  Right click on the desktop, ideally on a clean system so you don't
  have other clutter. Pick "Change Background...". See that the
  Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper
  isn't there. I'll attach the picture down below so you can see what it
  will look like.

  Install the SRU and check that it now appears and becomes selected.

  [ Regression potential ]

  The code in Settings checks that the wallpaper exists before showing
  it. So if you can see it it must be there - there's no chance you can
  set a wallpaper which simply won't work via this UI.

  Thinking laterally, it might be considered a regression if this
  wallpaper is inappropriate in some way - like the resolution is too
  low, or it renders badly for another reason. Make sure it looks right,
  since this is the first time it's getting shown.

  [ Original description ]

  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+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 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken

[Łukasz Zemczak]

Hello NP, or anyone else affected,

Accepted ubuntu-wallpapers into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
wallpapers/20.10.3-0ubuntu0.20.10.1 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

** Changed in: ubuntu-wallpapers (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Ubuntu Default Greyscale Wallpaper Sym Link Broken

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers source package in Groovy:
  Fix Committed

Bug description:
  [ Description ]

  I forgot to update the symlink for the greyscale default gorilla
  wallpaper and so it doesn't show up in the wallpaper chooser.

  [ Fix ]

  Fix the symlink.

  [ QA ]

  Right click on the desktop, ideally on a clean system so you don't
  have other clutter. Pick "Change Background...". See that the
  greyscale groovy wallpaper isn't there.

  Install the SRU and check that it now appears and becomes selected.

  [ Regression potential ]

  The code in Settings checks that the wallpaper exists before showing
  it. So if you can see it it must be there - there's no chance you can
  set a wallpaper which simply won't work via this UI.

  Thinking laterally, it might be considered a regression if this
  wallpaper is inappropriate in some way - like the resolution is too
  low, or it renders badly for another reason. Make sure it looks right,
  since this is the first time it's getting shown.

  [ Original description ]

  The sym link still links to the nonexistent Focal greyscale wallpaper.

  How to reproduce:

  Try to set the wallpaper to the default greyscale in Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-wallpapers 20.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 21:40:40 2020
  Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

[Łukasz Zemczak]

Hello Christian, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.43 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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.

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  In Progress
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 

[Desktop-packages] [Bug 1897934] Re: [Intel HDA] The initial sound level is set to zero (muted)

[Łukasz Zemczak]

I disagree with the importance of this bug being 'Low'. This is very important 
from the accessibility point of view - with the sound muted, it is not possible 
to properly use the screen reader for installation, live session or after boot, 
requiring a visually impaired person to fist figure out how to bring the volume 
back up.
If we can't fix it before release, too bad, we'll live. But certainly from the 
release POV it's a rather critical bug.

** Changed in: linux (Ubuntu)
   Importance: Low => Critical

** Changed in: pulseaudio (Ubuntu)
   Importance: Low => Critical

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

Title:
  [Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1899955] Re: FFe: Replace default wallpaper in Groovy

[Łukasz Zemczak]

As there was no further discussion and we already have (hopefully) final
release candidates for 20.10, marking as 'Won't Fix' for the wallpaper.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  FFe: Replace default wallpaper in Groovy

Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-wallpapers package in Ubuntu:
  Won't Fix

Bug description:
  Changing the default wallpaper from the existing Groovy Gorilla
  illustration to the one featuring Raspberry Pi tinted sunglasses.

  For the default desktop wallpaper we'll need to revert
  https://launchpad.net/ubuntu/+source/ubuntu-settings/20.10.2 and
  https://launchpad.net/ubuntu/+source/ubuntu-
  wallpapers/20.10.2-0ubuntu1 and update the warty-final-ubuntu.png and
  also include the with the plain sunglasses mascot wallpaper as an
  option.

  The background wallpaper for Ubiquity slideshow should also be changed
  to use the version featuring the mascot wearing Raspberry Pi tinted
  sunglasses.

  The benefit is to pay homage to the work various teams have been doing
  with the Raspberry Pi foundation and to their product. It's a way to
  signal our commitment to making their platform great and deepen our
  relationship with the Pi foundation.

  Any additional information which would be helpful in considering the
  decision

  The concerns people have are of product placement and forcing
  something onto peoples machines. There are several arguments against
  this, the option to change to the default easily, that there is no
  direct link to Raspberry Pi anything and its quite subtle. But
  ultimately the reason is we want to make a splash with the Raspberry
  Pi and arm in general and this is a very good way to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1899955/+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 1899955] Re: New Freeze Exception: Exceptional circumstance

[Łukasz Zemczak]

This really feels late for such a user-visible change. We are now after
final freeze and long after user interface freeze - we would really
prefer not to have such changes done basically a weekend away from
release week.

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

Title:
  New Freeze Exception: Exceptional circumstance

Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  Changing the default wallpaper from the existing Groovy Gorilla
  illustration to the one featuring Raspberry Pi tinted sunglasses.

  For the default desktop wallpaper we'll need to revert
  https://launchpad.net/ubuntu/+source/ubuntu-settings/20.10.2 and
  https://launchpad.net/ubuntu/+source/ubuntu-
  wallpapers/20.10.2-0ubuntu1 and update the warty-final-ubuntu.png and
  also include the with the plain sunglasses mascot wallpaper as an
  option.

  The background wallpaper for Ubiquity slideshow should also be changed
  to use the version featuring the mascot wearing Raspberry Pi tinted
  sunglasses.

  The benefit is to pay homage to the work various teams have been doing
  with the Raspberry Pi foundation and to their product. It's a way to
  signal our commitment to making their platform great and deepen our
  relationship with the Pi foundation.

  Any additional information which would be helpful in considering the
  decision

  The concerns people have are of product placement and forcing
  something onto peoples machines. There are several arguments against
  this, the option to change to the default easily, that there is no
  direct link to Raspberry Pi anything and its quite subtle. But
  ultimately the reason is we want to make a splash with the Raspberry
  Pi and arm in general and this is a very good way to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1899955/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Łukasz Zemczak]

** Tags removed: rls-ff-incoming

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error response 

[Desktop-packages] [Bug 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)

[Łukasz Zemczak]

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

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

Title:
   [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  The yaru icon style is explicitly shipped within the ubuntu source
  package of libreoffice.

  libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28"

  The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11"

  Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru-
  fullcolor/compare/2020-09-28...2020-10-11

  Most noticeable visual changes:
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1879183] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for cheese 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 cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1879183

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Released
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+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 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

[Łukasz Zemczak]

I have no reason to not believe the verification provided in comment
#20, as comment #21 does not provide any context and is rather
disrespectful. If this update does indeed cause a regression, please
fill a regression-update bug.

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Released
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+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 1897170] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for file-roller 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 file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1897170

Title:
  SRU the current 3.36.3 stable update

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller 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/file-roller/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that opening archives of different type still works correctly

  * Regression potential

  The update includes some fixes around drag and drop so that needs some
  extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1897170/+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 1894606] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894606

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+subscriptions

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

[Desktop-packages] [Bug 1866194] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1866194

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

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Selected audio output device in Settings is ignored after upgrading to
  Ubuntu 20.04.

  [Test Case]

  Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
  to 20.04. When done, attempt to connect a Bluetooth or USB audio
  device and use it via Settings.

  [Regression Potential]

  Unknown/low. The fix is from upstream and has already been released to
  Ubuntu 20.10 without any problems. Only worth noting it works by
  detecting and removing audio configurations made via older versions of
  PulseAudio. So upon upgrading some old settings may be reset to
  defaults, but the idea is that's less bad than audio devices being
  unusable (this bug).

  [Original Bug Report]

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

  Steps to reproduce:

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1897934] Re: The initial sound level is set to zero (mute)

[Łukasz Zemczak]

How was this in 20.04? Since you mentioned that it's a regression from
18.04 - does this mean we had it like this in focal as well?

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

Title:
  The initial sound level is set to zero (mute)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 18.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+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 1897858] Re: [UIFe] IBus 1.5.23

[Łukasz Zemczak]

It's late, but seeing that we're not really 'prepared' on many UI fronts
already (like missing the default wallpaper), I think it should be fine.
UIFe approved. Please inform the necessary teams and proceed!

** Changed in: ibus (Ubuntu)
   Status: New => Triaged

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

Title:
  [UIFe] IBus 1.5.23

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  Do we want IBus 1.5.23 in groovy? I built it successfully here:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

  and it seems to run smoothly. debian/ is from Debian's repo and only
  modified with the patch adjustments necessary to apply to the new
  upstream.

  Upstream's release notes:

  https://github.com/ibus/ibus/releases/tag/1.5.23

  The biggest change is that /usr/share/ibus/component/simple.xml, with
  the XKB keyboard layouts, is significantly larger than before. The UI
  for adding input methods seems to handle it fine. But the additional
  layouts should be seen as a bug fix IMO, in response to the bugs
  mentioned at bug #1835541.

  Otherwise it's mostly bug fixes (and insignificant low risk
  improvements).

  The UIFe request is due to some new translatable strings. I will
  notify the documentation and translation teams if this is approved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1897858/+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 1835220] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for sane-backends 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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1835220

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Committed
Status in sane-backends source package in Focal:
  Fix Released
Status in sane-backends source package in Groovy:
  Fix Released
Status in sane-backends package in Baltix:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  [Impact]

  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  sane-backends 1.0.31-1~experimental1 adds support for /usr/lib64/sane,
  and so do the debdiffs attached to this bug report for focal and
  bionic.

  [Test case]

  * Configure an affected scanner with drivers installed via
e.g. brscan2

  * Try to scan with simple-scan

  -> Find that the scanner is not found

  * Install libsane{,1}, libsane-common and sane-utils from
{focal,bionic}-proposed

  * Try to scan again

  -> Scanner found and scanning works

  [Regression risk]

  This only adds a directory to the lib search path via an existing
  patch, so the regression risk should be minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1897553] Re: Palm detect pressure is too easy to trigger so that the cursor stalled

[Łukasz Zemczak]

Sponsored for both groovy and focal.

** Also affects: libinput (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Palm detect pressure is too easy to trigger so that the cursor stalled

Status in OEM Priority Project:
  New
Status in libinput package in Ubuntu:
  In Progress
Status in libinput source package in Focal:
  New

Bug description:
  [Impact]

   * ALPS new i2c touchpads have capabilities for reporting ABS_PRESSURE and
 ABS_MT_PRESSURE event, However, it is very easy to over the default
 palm detect by pressure threshold 130. When the threshold is achieved,
 the cursor will be stalled, and not be able to keep following the
 finger's movement.

  [Test Case]

   * For touchpad vid 0488, and have pressure capabilities.

     The pressure capability can be easily obtain by evtest tool, there 
 should be ABS_PRESSURE and ABS_MT_PRESSURE event in ABS event type.

     Test step:
     Install libinput-tools
     1. $ sudo apt install libinput-tools
     2. $ sudo libinput measure touchpad-pressure
     3. Generally move the finger, the pressure max should not exceed the
palm pressure detect threshold

  [Regression Potential]

   * It only impacts ALPS i2c models
   * It won't impact the touchpad without capability to report pressure event.
   * For those touchpad with pressure capability will make the palm detect 
 pressure be less sensitive. However, ALPS said its firmware can support 
 firmware labeling palm detection, so it is okay that the palm detect 
 pressure become less sensitive.

  [Other Info]

   * The upstream commit has merged
     https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/505

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1897553/+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 1888575] Re: Split motd-news config into a new package

[Łukasz Zemczak]

Accepted the hopefully final ubuntu-meta change for xenial, finally
removing grub-legacy-ec2 from ubuntu-server. This requires re-running
the k) test-case, among other things.

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

i) verify grub-legacy-ec2 is not in the xenial server seed
ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise 

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Łukasz Zemczak]

Hello Andreas, or anyone else affected,

Accepted ubuntu-meta into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
meta/1.361.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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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.

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed verification-needed-xenial

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is 

[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font

[Łukasz Zemczak]

** Changed in: language-selector (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  Triaged

Bug description:
  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . There seems to be a consensus
  to make these adjustments:

  * Replace "Noto Sans Arabic UI" with "Noto Naskh Arabic UI" as
default Arabic font for sans-serif

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+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 1892320] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for fonts-noto 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 fonts-noto in Ubuntu.
https://bugs.launchpad.net/bugs/1892320

Title:
  No-change rebuild for focal-updates

Status in fonts-noto package in Ubuntu:
  Fix Released
Status in fonts-noto source package in Focal:
  Fix Released

Bug description:
  [Impact]

  The purpose with this no-change rebuild is to have the fonts-noto-core
  and fonts-noto-ui-core binaries land in focal-updates, and with that
  make it possible to move them to main. The measure is closely related
  to bug #1891733.

  [Test Case]

  Confirm that fonts-noto-core and fonts-noto-ui-core can be installed
  from focal-proposed.

  [Regression risk]

  Source unchanged - not applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1892320/+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