[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3

[Łukasz Zemczak]

Hello Robert, or anyone else affected,

Accepted simple-scan into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/simple-
scan/3.36.3-0ubuntu0.20.04.0 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  New
Status in simple-scan source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions

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

[Desktop-packages] [Bug 1883924] Update Released

[Łukasz Zemczak]

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

Title:
  Ubuntu.exe will not be detected properly if other LTS version is
  installed

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases when using from the Ubuntu
  app from Microsoft Store. When other LTS version of app is installed
  from Microsoft Store, baseexec generated by wslu on Ubuntu app will
  not be using ubuntu.exe but other LTS release apps (such as
  ubuntu1804.exe)

  [Test Case]

   * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store.
   * run any wslu tools (like wslfetch --help)
   * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe

  [Regression Potential]

  This patch will try to regenerate  ~/.config/wslu/baseexec when trying
  to execute any wslu commands (like wslfetch). Potential regressions
  would be a result of  ~/.config/wslu/baseexec not regenerated
  properly.

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

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

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1877016] Update Released

[Łukasz Zemczak]

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

Title:
  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Confirmed
Status in wslu source package in Bionic:
  Confirmed
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases. When PATH do not include
  Windows path, the all tools will complain that reg.exe is not found.

  [Test Case]

   * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf 
file, and restart the distribution
   * run any wslu tool (like wslfetch)
   * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown

  [Regression Potential]

  * For future release of wslu 3.1.0 proposed, huge refactoring will be
  needed.

  [Original Bug Report]

  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

  $ wslfetch
  /usr/bin/wslfetch: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:
     .++ .:/++/-.`sss/` BRANCH:
   .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS
  o:+o+:++. `'-/ooo+\   KERNEL: Linux 4.4.0-18362-Microsoft
     .:+o:+o/.  `+sssooo+\  UPTIME: 0d 2h 6m
    .++/+ +oo+o:` \sssooo;
   /+++//+: oo+o
   \+/+o+++ o++o   ydddhh+
    .++.o+ +oo+:` /dddhhh;
     .+.o+oo:.   odd+
  \+.++o+o` -.:ohdh+
   `:o+++  oyo++os:
     .o: .syhhh'.oo++o.
     /osyyy.+++\
     ` +oo+++o:/
    `oo++'`

  After :

  echo $PATH
  
/snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:.

  $ wslfetch

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:18363
     .++ .:/++/-.`sss/` BRANCH:   19h1_release
   .:++o: `\/:---:/-RELEASE:  Ubuntu 20.04 LTS
  

[Desktop-packages] [Bug 1883920] Update Released

[Łukasz Zemczak]

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

Title:
  ubuntu logo in wslfetch needs update

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases. The Ubuntu branding is
  the outdated version:
  https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png

  [Test Case]

   * Install Ubuntu WSL and install this fix.
   * run wslfetch command.
   * new logo should be shown like the following: 
https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png

  [Regression Potential]

  * This patch just update the logo of wslfetch to the proper current
  Ubuntu logo. Potential regressions would be a result of the patch
  having typo that caused error.

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

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

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

Title:
  SRU the current 3.36.4 stable update

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center 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-control-center/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the GNOME settings still work correctly

  * Regression potential

  Nothing specific to test in this update

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

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

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

Status in OEM Priority Project:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * audio input won't auto select and no pop-up dialog when headset is
  plugged

   * backporting fix gitlab_ucm_mixer_control_select.patch in groovy to
  focal.

  [Test Case]

   * Using Tiger Lake platform
   * Step to reproduce:
     1. plug-in headset
     2. check g-c-c

     Expected result:
       audio input switch to headset mic.

     Actual result:
       audio input is not changed.

  [Regression Potential]

   * the change corrupt the audio device selection, the audio
  input/output is not as expect

  [Other Info]

   * a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

   * Test pass after 'do-release-upgrade -d' on the Tiger Lake platform
  to groovy with gnome-control-center_1:3.36.4-1ubuntu1.

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

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

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

Title:
  No way to enroll multiple fingers for identification

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

Bug description:
  * Impact

  This is the continuation of bug #1865845.

  In g-c-c user panel, it is not possible to enroll more than one finger
  for authentication.

  * Test Case

  1. enroll fingerprint in gnome-control-center
  2. close the dialog
  3. click it again to enroll another finger
  4. it shows a dialog requiring you to delete your fingerprints

  * Impact

  As per this, GNOME design has produced some artwork that we want to implement 
to fix all these issues:
   - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18

  There will be few new strings, although most of the action events are
  already covered by the fprintd translations.

  UI will change quite a lot, but the current documentation [1] should
  not be affected by the change, being quite generic, but in case it
  might be updated to be clearer. The change are important improvements
  and oem request so believe it's right to carry over as a SRU and
  considered as hardware enablement

  The new strings are already translatable on launchpad and the
  translators mailing list has been notified, hopefully we can get some
  coverage for the new UI in time for the LTS .1 langpack refresh

  [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html

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

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

[Desktop-packages] [Bug 1886565] Update Released

[Łukasz Zemczak]

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

Title:
  SRU the current 3.36.7 stable update

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

  * Test case

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

  Open some pdf and ps documents, check that they render properly

  * Regression potential

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

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

-- 
Mailing list: https://launchpad.net/~desktop-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
  regressi

[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 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 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 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)
  Inst

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

[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 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 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 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 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 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
  version.

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

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

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

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

[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 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems

[Łukasz Zemczak]

When verifying this bug, can we make sure https://bugs.launchpad.net
/oem-priority/+bug/1875339 is still fixed?

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

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

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

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

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

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

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.4~0.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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1881586

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

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

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

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

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.4~0.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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1880564

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

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

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

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

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

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

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

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

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

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

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

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

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

[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized

[Łukasz Zemczak]

Hello Jani, or anyone else affected,

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

** 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/1871868

Title:
  Shell dialog text is truncated and ellipsized

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

Bug description:
  [ Impact ]

  Shell modal dialogs contain text that may be truncated when using
  certain locales

  [ Test case ]

  - Start a virtual machine with GNOME Boxes
  - The keyboard prompt should be all visible

  [ Regression potential ]

  Text isn't properly rendered or the dialog is not all visible in the
  display

  

  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10&show=all&search=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

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

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

[Desktop-packages] [Bug 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days

[Łukasz Zemczak]

Hello Heewa, or anyone else affected,

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

** 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/1885346

Title:
  gnome-shell-calendar-server leaks GBs of memory every few days

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

Bug description:
  [ Impact ]

  gnome-shell-calendar-server memory usage increases daily

  [ Test case ]

  Monitor the memory usage of gnome-shell-calendar-server process using
  top or similar tools and ensure that its memory usage is stable.

  [ Regression potential ]

  Events in gnome-shell calendar aren't visible anymore

  ---

  It's been happening repeatedly over the last maybe week? I have to
  manually kill it about once a day, when I start to feel everything
  slow down as the OS starts to swap.

  Actually, I tracked down and fixed a few leaks in the code, and it
  looks stable so far. I'll submit a patch soon, as well as send the fix
  upstream to Gnome.

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

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

[Desktop-packages] [Bug 1888060] Re: Update to 3.36.4 and SRU it

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

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

** Changed in: gnome-shell (Ubuntu Focal)
   Status: In Progress => 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/1888060

Title:
  Update to 3.36.4 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell 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.4

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  Calendar server received a major change, so need to ensure that events
  are still properly populating the gnome-shell calendar.

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

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

[Desktop-packages] [Bug 1889181] Re: ubuntu-drivers: fails with the deprecated autoinstall argument

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.4~0.20.04.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-
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: ubuntu-drivers-common (Ubuntu Focal)
   Status: In Progress => 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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1889181

Title:
  ubuntu-drivers: fails with the deprecated autoinstall argument

Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Test Case]

  1) Call the deprecated "ubuntu-drivers autoinstall".

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.3).

  3) Check that the command does not crash ubuntu-drivers.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The autoinstall argument is deprecated, and we only keep it for backward 
compatibility with ubiquity.

  
  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.5.2, the problem page at 
https://errors.ubuntu.com/problem/76b7e8c5d279fa00ea08b6d04c1e459fec30e02b 
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/1889181/+subscriptions

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

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

Title:
  ubuntu-drivers: fails with the deprecated autoinstall argument

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

Bug description:
  SRU Request:

  [Test Case]

  1) Call the deprecated "ubuntu-drivers autoinstall".

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.3).

  3) Check that the command does not crash ubuntu-drivers.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The autoinstall argument is deprecated, and we only keep it for backward 
compatibility with ubiquity.

  
  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.5.2, the problem page at 
https://errors.ubuntu.com/problem/76b7e8c5d279fa00ea08b6d04c1e459fec30e02b 
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/1889181/+subscriptions

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

[Desktop-packages] [Bug 1889106] Re: [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a higher version than the transitional deb in 20.04

[Łukasz Zemczak]

Hello Olivier, or anyone else affected,

Accepted chromium-browser into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/chromium-
browser/84.0.4147.89-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: chromium-browser (Ubuntu Focal)
   Status: In Progress => 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1889106

Title:
  [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
  browser due to a higher version than the transitional deb in 20.04

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  This bug is another manifestation of bug #1858500, but with a different 
upgrade path.
  bionic-{security,updates} will soon have chromium-browser 
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and 
when that happens the version number in focal will be lower, meaning that 
chromium-browser won't be updated to the new package that installs the snap for 
a user upgrading from 18.04 to 20.04.

  Since chromium-browser in 20.04 is a mostly empty transitional package
  that installs the chromium snap, all that's needed to fix this is to
  bump its version number.

  [Impact]

  Users upgrading from 18.04 to 20.04 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 18.04 is (will soon be) greater than 
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.

  [Test Case]

   * Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in 
bionic-{security,updates}
   * On a machine running 18.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 20.04
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions
  compared to the deb package, they are being tracked at
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
  snap is the desired behaviour though.

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

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

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

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

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

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell

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

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

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

Title:
  Update to 3.36.4 and SRU it

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

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

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

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

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

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

Bug description:
  [ Impact ]

  It's not possible to restore the application a non-fractional scaling
  configuration when fractional scaling was previously enabled and
  applied.

  [ Test case ]

  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

  [ Regression potential ]
  - Configuration can't be applied
  - Scaling (fractional or not) is not properly applied in single and 
multi-monitor
  - Fractional scaling can't be toggled anymore

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

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

[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows

[Łukasz Zemczak]

Hello Niels, or anyone else affected,

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

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

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

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

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Łukasz Zemczak]

Hello Iain, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1876894

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

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

Bug description:
  * Impact

  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

  * Test Case

  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  Repeat the same selecting 200% at 5., (or 100% if 200% was your
  default) and ensure it's applied.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  * Regression potential

  Verify that scaling changes are correctly applied on different setup

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Łukasz Zemczak]

Hello Matt, or anyone else affected,

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

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

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-

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

[Łukasz Zemczak]

Hello Ivan, or anyone else affected,

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

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

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

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

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values

[Łukasz Zemczak]

Hello Daniel, or anyone else affected,

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

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

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  [ Test case ]

  In a Nvidia system:
  - From g-c-c enable fractional scaling
  - Set all the available fractional scaling values and ensure they work
+ In any case the screen should be turned off

  [ Regression potential ]

  Wrong screen size is set and panning might be enabled.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200124)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3

[Łukasz Zemczak]

Thank you for your verification. That being said, when reviewing this
package I didn't notice that currently groovy is still on an older
version, so I can't really let this in into focal-updates before it
lands in groovy as well.

Are there any plans of uploading this to groovy? Once it is, please
switch the focal task back to 'Fix Committed'.

** Changed in: simple-scan (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan source package in Focal:
  Incomplete

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions

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

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

Title:
  HIde im-config in application menus/searches

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  Fix Released

Bug description:
  [Impact]

  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"

  Suggestion:
  ===
  Hide im-config from application menu / searches

  [Test Case]

  * Open Activities and find that "Input Method" is found

  * Install im-config from focal-proposed

  * Open Activities and find that "Input Method" is no longer found

  [Regression Potential]

  Minimal; only a tiny change in the .desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1885744/+subscriptions

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

[Desktop-packages] [Bug 1878285] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libfprint 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/1878285

Title:
  gnome-control-center / fprintd crashes on setting up fingerprint with
  vfs0050

Status in libfprint:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  When I try to setup my fingerprint in gnome-control-center, I first
  have to choose which finger I would use, and when I press the "next"
  button, it crashes : "Unable to access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  For information, my fingerprint sensor is :
  - lsusb
  Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint 
Sensor

  [ Test case ]

  With a fingerprint reader 138a:0050:
   - Open gnome-control-center user-accounts
   - Select the fingeprint row to enroll a finger
   - Follow the procedure and the finger should be enrolled
   - Verify with:
 fprintd-list $USER

  [ Regression potential ]

   - The fingerprint is not read by the sensor

  
  ---

  Ubuntu 20.04

  gnome-control-center:
    Installé : 1:3.36.1-1ubuntu5
    Candidat : 1:3.36.1-1ubuntu5
   Table de version :
   *** 1:3.36.1-1ubuntu5 500
  500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expected to happen, is that everything works and that I can set
  up my finger for unlocking.

  What happened instead : it crashes with the information "Unable to
  access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 22:00:30 2020
  InstallationDate: Installed on 2020-05-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886644] Update Released

[Łukasz Zemczak]

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

Title:
  SRU the current 3.36.4 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server 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/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

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

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

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

Title:
  gnome-shell-calendar-server leaks GBs of memory every few days

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  gnome-shell-calendar-server memory usage increases daily

  [ Test case ]

  Monitor the memory usage of gnome-shell-calendar-server process using
  top or similar tools and ensure that its memory usage is stable.

  [ Regression potential ]

  Events in gnome-shell calendar aren't visible anymore

  ---

  It's been happening repeatedly over the last maybe week? I have to
  manually kill it about once a day, when I start to feel everything
  slow down as the OS starts to swap.

  Actually, I tracked down and fixed a few leaks in the code, and it
  looks stable so far. I'll submit a patch soon, as well as send the fix
  upstream to Gnome.

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

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

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

Title:
  Shell dialog text is truncated and ellipsized

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Shell modal dialogs contain text that may be truncated when using
  certain locales

  [ Test case ]

  - Start a virtual machine with GNOME Boxes
  - The keyboard prompt should be all visible

  [ Regression potential ]

  Text isn't properly rendered or the dialog is not all visible in the
  display

  

  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10&show=all&search=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

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

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

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

Title:
  Update to 3.36.4 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell 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.4

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  Calendar server received a major change, so need to ensure that events
  are still properly populating the gnome-shell calendar.

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

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

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original descrip

[Desktop-packages] [Bug 1886692] Update Released

[Łukasz Zemczak]

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

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

Title:
   [SRU] libreoffice 6.4.5 for focal

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

Bug description:
  [Impact]

   * LibreOffice 6.4.5 is in its fifth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.4 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 96 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 96 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1884754] Update Released

[Łukasz Zemczak]

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

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

Title:
  Fractional scaling does not persist while resizing or rebooting in VM
  windows

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

Bug description:
  [ Impact ]

  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  [ Test case ]

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - After next reboot the setting is reverted to 100%, but should use previous 
value

  [ Regression potential ]

  Resolution doesn't adapt properly to the vmware player window size.

  
  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874567] Update Released

[Łukasz Zemczak]

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

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdr

[Desktop-packages] [Bug 1887998] Update Released

[Łukasz Zemczak]

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

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

Title:
  Update to 3.36.4 and SRU it

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

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

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

[Desktop-packages] [Bug 1886996] Update Released

[Łukasz Zemczak]

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

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

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

Bug description:
  [ Impact ]

  It's not possible to restore the application a non-fractional scaling
  configuration when fractional scaling was previously enabled and
  applied.

  [ Test case ]

  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

  [ Regression potential ]
  - Configuration can't be applied
  - Scaling (fractional or not) is not properly applied in single and 
multi-monitor
  - Fractional scaling can't be toggled anymore

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

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

[Desktop-packages] [Bug 1889090] Update Released

[Łukasz Zemczak]

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

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
  Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
  Jul 27 00:30:33 jojda gnome-shell[15068]: **
  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 

[Desktop-packages] [Bug 1873403] Update Released

[Łukasz Zemczak]

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

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  [ Test case ]

  In a Nvidia system:
  - From g-c-c enable fractional scaling
  - Set all the available fractional scaling values and ensure they work
+ In any case the screen should be turned off

  [ Regression potential ]

  Wrong screen size is set and panning might be enabled.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200124)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870867] Update Released

[Łukasz Zemczak]

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

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1857947] Update Released

[Łukasz Zemczak]

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

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

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

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

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

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

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

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

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

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

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

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

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

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

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

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

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

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

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

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

  On other systems, nothing changed.

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

  For fix 3), if there are U

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

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

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

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

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

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

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

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

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

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

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

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

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

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

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

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

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

  On other systems, nothing changed.

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

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

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

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Łukasz Zemczak]

Hello Hui, or anyone else affected,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Łukasz Zemczak]

Hello Kai-Heng, or anyone else affected,

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

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

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

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

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

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

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

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

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

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

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

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

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

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

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

  On other systems, nothing changed.

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

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

[Desktop-packages] [Bug 304393] Update Released

[Łukasz Zemczak]

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

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

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

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

Bug description:
  [impact]

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

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

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

  [test case]

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

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

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

  [regression potential]

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

  [scope]

  This is needed only for Bionic and earlier.

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

  [other info]

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

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

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

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

  [original description]

  Binary package hint: cups

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

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

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

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