[Desktop-packages] [Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-05-17 Thread Kai-Heng Feng
Thanks. Please file an upstream bug.

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed
Status in lm-sensors package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
  5.8.0-34 the fan on my machine started switching on (for an instant)
  and off every 10 seconds even when idle with CPU at 48/50°C.

  Switching back to previous kernel solves temporary the problem, i.e.
  fans are always off with light desktop work.

  The new behavior is really annoying and I guess not healthy for the
  fans.

  I'm on latest Dell bios, with every other package updated.

  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gabriele   2370 F pulseaudio
   /dev/snd/controlC1:  gabriele   2370 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-06 (352 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Precision 7540
  Package: lm-sensors 1:3.6.0-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.11
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/08/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.2
  dmi.board.name: 0XMC3F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1928642] Re: [SRU] libreoffice 7.0.6 for groovy

2021-05-17 Thread Rico Tzschichholz
** Description changed:

  [Impact]
  
-  * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line:
-  https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release
+  * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line:
+  https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release
  
-  * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
-  https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs
+  * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
+  https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs
  
-  * Given the nature of the project, the complexity of the codebase and
+  * 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
+  * 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_linux_gcc_release/82662/console
+   * A recent set of upstream's automated jenkins testing can be found here:
+ https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console
  
-   * 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
+   * 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] ...
- * [arm64] ...
- * [armhf] ...
- * [ppc64el] ...
- * [s390x] ...
+  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/amd64/libr/libreoffice/20210518_015036_da635@/log.gz
+ * [arm64] ...
+ * [armhf] ...
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/ppc64el/libr/libreoffice/20210518_025204_037c5@/log.gz
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/s390x/libr/libreoffice/20210518_014102_69cc4@/log.gz
  
-  * General smoke testing of all the applications in the office suite
+  * 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 50 bug fixes always carries the
+  * A minor release with a total of 50 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
+  * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
  [SRU] libreoffice 7.0.6 for groovy

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

Bug description:
  [Impact]

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

   * Version 7.0.5 is currently released in groovy. For a

[Desktop-packages] [Bug 1928475] Re: Xorg freeze when booting up

2021-05-17 Thread Daniel van Vugt
Thanks but it's not obvious to me where the hang of a few minutes is in
that log. Can you say the exact time it occurred? Or can you reproduce
the hang again and tell us what time it occurred?

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

Title:
  Xorg freeze when booting up

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  when booting up Ubuntu 21 it hangs for a few minutes then it becomes
  responsive it should not hang

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 10:42:48 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2021-05-14 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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


[Desktop-packages] [Bug 1926811] Re: After upgrading to 20.04 applications no longer launch from overview

2021-05-17 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  After upgrading to 20.04 applications no longer launch from overview

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  System info:

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

  $ apt-cache policy gnome
  gnome:
Installed: (none)
Candidate: 1:3.30+2
Version table:
   1:3.30+2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/universe amd64 
Packages

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.7-0ubuntu0.20.04.1
Candidate: 3.36.7-0ubuntu0.20.04.1
Version table:
   *** 3.36.7-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages

  $ apt-cache policy ubuntu-desktop
  ubuntu-desktop:
Installed: 1.450.2
Candidate: 1.450.2
Version table:
   *** 1.450.2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.450 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages


  I upgraded my system from 19.10/Eoan to 20.04 and when I go to the
  overview (Activities menu/hotspot), search an application and click on
  it it no longer launches. If I right click on it and select "Add to
  favorites" and then go to the dock and click on it it launches fine.

  I have not been able to find how to debug this issue but it is very
  annoying. Someone said it may have to do with the way .desktop files
  are handled now.

  Can someone please help?

  Thank you!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-05-06 (729 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags: focal third-party-packages
  Uname: Linux 5.4.0-72-generic x86_64
  UpgradeStatus: Upgraded to focal on 2021-04-20 (14 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1926796] Re: [SRU] Enable support for Xena Cloud Archive

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.98.9.5

---
software-properties (0.98.9.5) focal; urgency=medium

  * cloudarchive: Enable support for the Xena Ubuntu Cloud Archive on
20.04 (LP: #1926796).

 -- Corey Bryant   Fri, 30 Apr 2021 14:13:30
-0400

** Changed in: software-properties (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Enable support for Xena Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Focal:
  Fix Released
Status in software-properties source package in Impish:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:xena
 cloud-archive:xena-proposed

  This will also need to be SRU'd back to focal.

  [Impact]
  End users have to manually enable the xena cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:xena
  sudo add-apt-repository cloud-archive:xena-proposed

  [Regression potential]
  Limited - just a data item addition

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

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


[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

2021-05-17 Thread Ivan Larionov
This is fixed in 21.04.

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

Title:
  nouveau timeout and system lockup

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 to 20.10 system is unusable anymore due to
  GPU issues with nouveau. Same system worked fine on 20.04.

  Switching to nvidia proprietary driver and Xorg fixes the issue.

  Symptoms:

  System starts just fine, but overall UI performance is bad, everything
  seems slow and CPU usage seems too high even when idle. After a while
  UI freezes completly. Sometimes it recovers after several minutes,
  other times it doesn't and system freezes forever, requiring hard
  reboot.

  Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon
  E3-1231 v3.

  dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

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


[Desktop-packages] [Bug 1927334] Update Released

2021-05-17 Thread Brian Murray
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/1927334

Title:
  [SRU] libreoffice 7.1.3 for hirsute

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

Bug description:
  [Impact]

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

   * Version 7.1.2 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.2 see the list of bugs fixed in the release candidates of 7.1.3 
(that's a total of 105 bugs):
   https://wiki.documentfoundation.org/Releases/7.1.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.1.3/RC2#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_linux_gcc_release/88872/console

    * 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://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210507_025053_79e42@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210507_065558_93940@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210507_020030_1b56f@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210507_163628_d1422@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210507_081728_18e2a@/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 105 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/1927334/+subscriptions

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


[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

2021-05-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

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

Title:
  nouveau timeout and system lockup

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 to 20.10 system is unusable anymore due to
  GPU issues with nouveau. Same system worked fine on 20.04.

  Switching to nvidia proprietary driver and Xorg fixes the issue.

  Symptoms:

  System starts just fine, but overall UI performance is bad, everything
  seems slow and CPU usage seems too high even when idle. After a while
  UI freezes completly. Sometimes it recovers after several minutes,
  other times it doesn't and system freezes forever, requiring hard
  reboot.

  Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon
  E3-1231 v3.

  dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

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


[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-05-17 Thread Ivan D
Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)

There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.

Thanks again

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

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

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


[Desktop-packages] [Bug 1928475] Re: Xorg freeze when booting up

2021-05-17 Thread andrew g
here is the file

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1928475/+attachment/5498299/+files/journal.txt

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

Title:
  Xorg freeze when booting up

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  when booting up Ubuntu 21 it hangs for a few minutes then it becomes
  responsive it should not hang

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 10:42:48 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2021-05-14 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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


[Desktop-packages] [Bug 1926811] Re: After upgrading to 20.04 applications no longer launch from overview

2021-05-17 Thread Gabriel
Hi,

that was it, I found the culprit, it was this extension:
https://extensions.gnome.org/extension/1025/hide-overview-when-click-
overview/. Disabling it fixed my issues. Thank you, you can close this.

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

Title:
  After upgrading to 20.04 applications no longer launch from overview

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  System info:

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

  $ apt-cache policy gnome
  gnome:
Installed: (none)
Candidate: 1:3.30+2
Version table:
   1:3.30+2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/universe amd64 
Packages

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.7-0ubuntu0.20.04.1
Candidate: 3.36.7-0ubuntu0.20.04.1
Version table:
   *** 3.36.7-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages

  $ apt-cache policy ubuntu-desktop
  ubuntu-desktop:
Installed: 1.450.2
Candidate: 1.450.2
Version table:
   *** 1.450.2 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.450 500
  500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages


  I upgraded my system from 19.10/Eoan to 20.04 and when I go to the
  overview (Activities menu/hotspot), search an application and click on
  it it no longer launches. If I right click on it and select "Add to
  favorites" and then go to the dock and click on it it launches fine.

  I have not been able to find how to debug this issue but it is very
  annoying. Someone said it may have to do with the way .desktop files
  are handled now.

  Can someone please help?

  Thank you!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-05-06 (729 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags: focal third-party-packages
  Uname: Linux 5.4.0-72-generic x86_64
  UpgradeStatus: Upgraded to focal on 2021-04-20 (14 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-17 Thread Tim Ryder
This kernel also does not produce sound from the bottom bass speakers

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

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


[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-17 Thread Tim Ryder
Here it is.

** Attachment added: "alsa-project.org.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5498257/+files/alsa-project.org.txt

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

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


[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-17 Thread Tim Ryder
I'm running fedora 34, but I'm more then happy to install ubuntu back
today and try these kernels if it will help resolve the issue.  Just
need some time to get that done.

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

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


Re: [Desktop-packages] [Bug 1928082] Re: Display freezes and log flooded: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter act

2021-05-17 Thread moshood ope
Thanks, I'll check it out.

On Mon, 17 May 2021 at 10:30 AM, Daniel van Vugt <1928...@bugs.launchpad.net>
wrote:

> In that case please try uninstalling them, and log in again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1928082
>
> Title:
>   Display freezes and log flooded: Attempting to call back into JSAPI
>   during the sweeping phase of GC. This is most likely caused by not
>   destroying a Clutter actor or Gtk+ widget with ::destroy signals
>   connected, but can also be caused by using the destroy(), dispose(),
>   or remove() vfuncs. Because it would crash the application, it has
>   been blocked and the JS callback not invoked.
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   the display freezes when i try minimizing after a very long use time
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+22ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
>   Uname: Linux 5.11.0-16-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu65
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 11 13:09:28 2021
>   DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to
> execute child process “./xorg_fix_proprietary.py”: Failed to execve: No
> such file or directory (1))
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   DkmsStatus:
>virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
>virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
> [17aa:21f3]
>   InstallationDate: Installed on 2019-06-10 (701 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   MachineType: LENOVO 23445HU
>   ProcEnviron:
>LANGUAGE=en_NG:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_NG
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic
> root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago)
>   dmi.bios.date: 03/06/2014
>   dmi.bios.release: 2.64
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G1ETA4WW (2.64 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23445HU
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.ec.firmware.release: 1.13
>   dmi.modalias:
> dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T430
>   dmi.product.name: 23445HU
>   dmi.product.sku: LENOVO_MT_2344
>   dmi.product.version: ThinkPad T430
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
>   version.libdrm2: libdrm2 2.4.104-1build1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200714-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1928082/+subscriptions
>
-- 
Mosgizy

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

Title:
  Display freezes and log flooded: Attempting to call back into JSAPI
  during the sweeping phase of GC. This is most likely caused by not
  destroying a Clutter actor or Gtk+ widget with ::destroy signals
  connected, but can also be caused by using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has
  been blocked and the JS callback not invoked.

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

Bug description:
  the display freezes when i try minimizing after a very long use time

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignat

[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-17 Thread Dimitri John Ledkov
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-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/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Committed
Status in bcmwl source package in Focal:
  Fix Committed
Status in dahdi-linux source package in Focal:
  Fix Committed
Status in dm-writeboost source package in Focal:
  Fix Committed
Status in evdi source package in Focal:
  Fix Committed
Status in gost-crypto source package in Focal:
  Fix Committed
Status in iptables-netflow source package in Focal:
  Fix Committed
Status in liblzf source package in Focal:
  Fix Committed
Status in lime-forensics source package in Focal:
  Fix Committed
Status in lttng-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Committed
Status in oss4 source package in Focal:
  Fix Committed
Status in r8168 source package in Focal:
  Fix Committed
Status in rtl8812au source package in Focal:
  Fix Committed
Status in sysdig source package in Focal:
  Fix Committed
Status in v4l2loopback source package in Focal:
  Fix Committed
Status in virtualbox source package in Focal:
  Fix Committed
Status in virtualbox-hwe source package in Focal:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions

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


[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-17 Thread Jussi Pakkanen
Unfortunately I can only run live cd:s on this machine due to reasons.
Maybe someone else with the issue can give it a go?

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

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


[Desktop-packages] [Bug 711305]

2021-05-17 Thread Antishape
I had no problem like this until Ubuntu 21.04 (which I upgraded to lately).
Clicking on mailto-links in Firefox result in the error message by Thunderbird 
"TB already running..."
I have FF 88.0 and TB 78.8.1 - system is 64 Bit.
I recently had a problem (since the aforementioned upgrade) with Firefox not 
able to open tabs or windows when clicking on a link in an email (in TB), but 
today it was gone. Maybe as a result of an update I received yesterday?

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

Title:
  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system. Error received when clicking a mailto link in
  firefox.

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This thunderbird error is given when clicking a mailto link. Instead
  of using the thunderbird that's already open it tries to open a new
  instance. Preferred Applications has Thunderbird select, but I have
  also tried Custom command "thunderbird %s". This has been tested on
  10.04 and 10.10. Both result in this error if thunderbird is already
  running.

  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Tue Feb  1 10:19:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

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


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

2021-05-17 Thread Bradley Pearce
This issue does not affect me on 21.04 with a clean install.

GeForce GTX 1060

460 tested driver

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

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

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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


[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-17 Thread Hui Wang
Please install, reboot and test this testing kernel.
https://people.canonical.com/~hwang4/lp1926165/

And generate and upload the alsa-info.txt with the testing kernel.

thx.

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions

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


[Desktop-packages] [Bug 1928082] Re: Display freezes and log flooded: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor o

2021-05-17 Thread Daniel van Vugt
In that case please try uninstalling them, and log in again.

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

Title:
  Display freezes and log flooded: Attempting to call back into JSAPI
  during the sweeping phase of GC. This is most likely caused by not
  destroying a Clutter actor or Gtk+ widget with ::destroy signals
  connected, but can also be caused by using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has
  been blocked and the JS callback not invoked.

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

Bug description:
  the display freezes when i try minimizing after a very long use time

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 11 13:09:28 2021
  DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1))
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
   virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2019-06-10 (701 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 23445HU
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago)
  dmi.bios.date: 03/06/2014
  dmi.bios.release: 2.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA4WW (2.64 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23445HU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23445HU
  dmi.product.sku: LENOVO_MT_2344
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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


Re: [Desktop-packages] [Bug 1928082] Re: the minimize display freezes

2021-05-17 Thread moshood ope
yeah, i gat more than the three built-in extensions

On Mon, 17 May 2021 at 03:55, Daniel van Vugt <1928...@bugs.launchpad.net>
wrote:

> Moshood, please open the 'Extensions' app and tell us if you have any
> more than the three built-in extensions there.
>
> ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1739
>https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1739
>
> ** Also affects: gnome-shell via
>https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1739
>Importance: Unknown
>Status: Unknown
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Incomplete => Confirmed
>
> ** Changed in: gnome-shell (Ubuntu)
>Importance: Undecided => High
>
> ** Summary changed:
>
> - the minimize  display freezes
> + Display freezes and log flooded: Attempting to call back into JSAPI
> during the sweeping phase of GC. This is most likely caused by not
> destroying a Clutter actor or Gtk+ widget with ::destroy signals connected,
> but can also be caused by using the destroy(), dispose(), or remove()
> vfuncs. Because it would crash the application, it has been blocked and the
> JS callback not invoked.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Confirmed => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1928082
>
> Title:
>   Display freezes and log flooded: Attempting to call back into JSAPI
>   during the sweeping phase of GC. This is most likely caused by not
>   destroying a Clutter actor or Gtk+ widget with ::destroy signals
>   connected, but can also be caused by using the destroy(), dispose(),
>   or remove() vfuncs. Because it would crash the application, it has
>   been blocked and the JS callback not invoked.
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   the display freezes when i try minimizing after a very long use time
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+22ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
>   Uname: Linux 5.11.0-16-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu65
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 11 13:09:28 2021
>   DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to
> execute child process “./xorg_fix_proprietary.py”: Failed to execve: No
> such file or directory (1))
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   DkmsStatus:
>virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
>virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
> [17aa:21f3]
>   InstallationDate: Installed on 2019-06-10 (701 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   MachineType: LENOVO 23445HU
>   ProcEnviron:
>LANGUAGE=en_NG:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_NG
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic
> root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago)
>   dmi.bios.date: 03/06/2014
>   dmi.bios.release: 2.64
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G1ETA4WW (2.64 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23445HU
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.ec.firmware.release: 1.13
>   dmi.modalias:
> dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T430
>   dmi.product.name: 23445HU
>   dmi.product.sku: LENOVO_MT_2344
>   dmi.product.version: ThinkPad T430
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
>   version.libdrm2: libdrm2 2.4.104-1build1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200714-1ubuntu1
>   v

[Desktop-packages] [Bug 1928642] [NEW] [SRU] libreoffice 7.0.6 for groovy

2021-05-17 Thread Rico Tzschichholz
Public bug reported:

[Impact]

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

 * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
 https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/7.0.6/RC2#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_linux_gcc_release/82662/console

  * 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] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [s390x] ...

 * 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 50 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.

** Affects: libreoffice (Ubuntu)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Affects: libreoffice (Ubuntu Groovy)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => High

** Changed in: libreoffice (Ubuntu Groovy)
   Importance: Undecided => High

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

** Changed in: libreoffice (Ubuntu)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu Groovy)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
  [SRU] libreoffice 7.0.6 for groovy

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

Bug description:
  [Impact]

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

   * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
   https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.0.6/RC2#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_linux_gcc_release/82662/console

* 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

 

[Desktop-packages] [Bug 1915681] Re: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384

2021-05-17 Thread Daniel van Vugt
Oops. Seems I was tricked by (b) in comment #3 again. The current
crashes being reported can't be attributed to "freeze/thaw" accounting
because errors.ubuntu.com doesn't look at enough of the stack trace to
confirm that. We only know that some people are experiencing crashes in
g_log(), which is itself correct because error level and higher messages
are meant to cause an abort().

We would need more concrete evidence of a crash in a current Ubuntu
release to pursue this further.

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

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

Title:
  Error in freeze/thaw accounting, GNOME Shell crashed with signal 5,
  resource:///org/gnome/shell/ui/windowManager.js:1384

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: Error in freeze/thaw accounting
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: GNOME Shell crashed with signal 5
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: == Stack trace for context 
0x561dd4480270 ==
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #0   561dd96ccf18 i   
resource:///org/gnome/shell/ui/windowManager.js:1384 (1c61e18d03d0 @ 589)
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #1   7ffc72c53090 b   
self-hosted:850 (22fd89d4e5b0 @ 454)

  Taken from https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1897765/comments/38

  This crash will also show up in the existing error buckets from bug
  1897765:

  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd

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

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


[Desktop-packages] [Bug 1915681] Re: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384

2021-05-17 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Error in freeze/thaw accounting, GNOME Shell crashed with signal 5,
  resource:///org/gnome/shell/ui/windowManager.js:1384

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: Error in freeze/thaw accounting
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: GNOME Shell crashed with signal 5
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: == Stack trace for context 
0x561dd4480270 ==
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #0   561dd96ccf18 i   
resource:///org/gnome/shell/ui/windowManager.js:1384 (1c61e18d03d0 @ 589)
  Feb 12 09:10:29 thinkpad gnome-shell[85476]: #1   7ffc72c53090 b   
self-hosted:850 (22fd89d4e5b0 @ 454)

  Taken from https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1897765/comments/38

  This crash will also show up in the existing error buckets from bug
  1897765:

  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd

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

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