date:20210121

I had to bypass Debian salsa git because the existing focal version
isn't in there.

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

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell crashes at random times when the Desktop or home directory
  is modified, and the desktop-icons extension tries to refresh.

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

  [Test Case]

  Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell
  should not crash or freeze.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading, like this bug.

  [Other Info]

  See also bug 1898910

  ---

  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2

Here's a fix for focal.

** Patch added: 
"gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+attachment/5455420/+files/gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.2.debdiff

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Status: Triaged => In Progress

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

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell crashes at random times when the Desktop or home directory
  is modified, and the desktop-icons extension tries to refresh.

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

  [Test Case]

  Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell
  should not crash or freeze.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading, like this bug.

  [Other Info]

  See also bug 1898910

  ---

  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1912202] Re: ubuntu-drivers-common fix FTBFS in focal

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => High

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

** Tags added: ftbfs

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

Title:
  ubuntu-drivers-common fix FTBFS in focal

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

Bug description:
  [Impact]

   * ubuntu-drivers-common is not available on riscv64 in focal due to
  failing test cases. In later releases riscv64 is built without
  unittests. This is preventing creating Focal based riscv64 cloud-
  images & hifive images.

  [Test Case]

   * Check that ubuntu-drivers-common is now available and installable
  on riscv64.

  [Where problems could occur]

   * This is no change rebuild for all other arches. And certain ubuntu-
  drivers-common functionality may not be working correctly on riscv64 -
  on par with later releases.

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

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

[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6

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

** Tags added: upgrade-software-version

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

Title:
  SRU 3.36.6

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in popup-grab handling, gdm view fixes,
  lockscreen display changes in some hw, extensions updates

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

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

[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

** Tags added: upgrade-software-version

** Changed in: gnome-shell (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  [SRU] Update gnome-shell to 3.36.7 in Focal

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

Bug description:
  [Impact]

  This is the current GNOME 3.36.x stable update, including some fixes
  and translation updates.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS

  3.36.7
  ==
  * Fix potential stack overflow in libcroco [Michael; !1404]
  * Fix system action search regressions [Florian; #3169]
  * Fix week number alignment when using font-scaling [Joonas; !1415]
  * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, 
!1451, #2230, !1423]

  Contributors:
  Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, 
Bastien Nocera, Daniel van Vugt

  Translators:
  Marek Černocký [cs]

  3.36.6
  ==
  * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071]
  * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420]

  Contributors:
  Sebastian Keller, Zephaniah E. Loss-Cutler-Hull

  Translators:
  Goran Vidović [hr], Balázs Úr [hu]

  3.36.5
  ==
  * Fix extension updates when many extensions are installed [Jeremias; !1363]
  * Fix missing icons in on-screen keyboard [Emre; #2631, #3007]
  * Fix delay when showing calendar events [Sebastian; #2992]
  * Fix app picker regressions on small displays [Sebastian; #2234, !1375, 
!1378]
  * Fix top bar navigation when NumLock is active [Olivier; #550]
  * Delay login animation until wallpaper has loaded [Michael; #734996]
  * Revert changes that caused mispositioning in overview in multi-monitor 
setups [Robert; #2971]
  * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997]
  * Fix stuck grab when destroying open popup menu [Florian; #3022]
  * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, 
!1381, #3037, #3005, !1386, !1390]

  Contributors:
  Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian 
Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias 
Ortega, Ray Strode, Emre Uyguroglu

  Translators:
  Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR]

  [Test case]

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

  GNOME Shell and its components should continue working well.

  The verification is going to include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [Regression potential]

  There have been fixes in various places: system actions search in
  different languages, alignment of week numbers in calendar menu, lock
  screen, scaling of app icons on Hi-dpi displays, extension updates,
  missing icons in OSK and showing calendar events in calendar menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 19:40:03 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-26 (198 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886592] Re: Add support for VMware Horizon SSO to gnome-shell

** Changed in: gnome-shell (Ubuntu Eoan)
   Importance: Undecided => Wishlist

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

Title:
  Add support for VMware Horizon SSO to gnome-shell

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  VMware Horizon is a VDI product that runs atop of VMware's normal
  virtualisation stack, and it supports SSO authentication for login.

  In the past, the VMware Horizon agent has been pretty buggy, and
  requires SSO patches to be present to function, otherwise it breaks
  and causes entire outages for anyone trying to use the VDI.

  To solve this, VMware had been custom compiling their own libgnome-
  shell.so libraries with their SSO patches, which are based on oVirt's
  SSO implementation. When you install VMware Horizon agent to the
  instance, it overwrites Ubuntu's libgnome-shell.so with their custom
  compiled one.

  VMware don't keep their custom compiled libgnome-shell.so library up
  to date, so bugs that have already been fixed still live on in their
  library. Also, when Ubuntu updates our gnome-shell packages, it
  overwrites the custom libgnome-shell.so library, which then causes the
  Horizon agent to break, and causes outages for anyone using the VDI,
  which have to be solved by manually copying the custom library back.

  This situation is untenable for VMware Horizon users, so I have asked
  VMware to upstream their SSO patches. After a long painful process,
  they have landed in gnome-shell master.

  This SRU will significantly improve the quality of life for VMware
  Horizon users, and will remove the need for VMware to distribute
  custom libraries.

  [Testcase]

  You need an instance that runs on VMware Horizon, and the Horizon
  agent needs to be installed and running. Ideally, SSO authentication
  should be enabled to test all features, but it is not necessary to
  partially test.

  Test packages are available in this ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf247978-test

  If you install the test package in a VMware Horizon VDI, the instance
  should come up cleanly after reboot and function properly, especially
  with SSO login.

  The instance should be able to function without custom libgnome-
  shell.so libraries provided by VMware.

  [Regression Potential]

  The code refactors the oVirt SSO implementation into a more
  generalised interface, which other virtualisation platforms can use.
  oVirt has been transitioned to this interface as part of the
  refactoring, which means that any if the new oVirt SSO implementation
  is broken, it could break users running in oVirt.

  VMware's patches also use the new generalised interface, which is much
  simpler than before, and it has been tested internally by VMware.
  There was a very long review process with upstream GNOME, which ironed
  out all of their concerns.

  I have been reviewing the code along the way, and I am confident that
  it will not cause any regressions. If a regression did occur, then it
  would break SSO functionality only.

  [Other Information]

  Upstream Issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1983
  Upstream merge-request: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/915

  Commits:

  commit 809f820cd4a4eebb120ab5dde3f1985d35bcb540
  Author: yun341 <5933...@qq.com>
  Date: Sat, 4 Jan 2020 00:31:15 +0800
  Subject: gdm: Refactor oVirt to a generic CredentialManager interface
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/809f820cd4a4eebb120ab5dde3f1985d35bcb540

  commit 4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5
  Author: yun341 <5933...@qq.com>
  Date: Thu, 2 Jul 2020 06:54:55 +0800
  Subject: gdm: Introduce vmware credential manager for pre-authenticated logins
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5

  commit 00437750ed9c7e0982854e20be8c36c6bda7b254
  Author: Andre Moreira Magalhaes 
  Date:   Mon Aug 17 18:41:04 2020 -0300
  Subject: authPrompt: Properly get oVirt service name
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/00437750ed9c7e0982854e20be8c36c6bda7b254

  commit 3fb321fd214469130539e1e31461257a749bff21
  Author: yun341 <5933...@qq.com>
  Date:   Mon Sep 21 22:11:41 2020 +0800
  Subject: authPrompt: set value of beginRequestType to 'DONT_PROVIDE_USERNAME'
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/3fb321fd214469130539e1e31461257a749bff21

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

-- 
Mailing

[Desktop-packages] [Bug 1908187] Re: Taking a screenshot during a game may lead to crash

** Changed in: gnome-shell (Ubuntu Focal)
   Importance: Undecided => Low

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

Title:
  Taking a screenshot during a game may lead to crash

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

Bug description:
  [ Impact ]

  A screenshot of the Left 4 Dead 2 or Garry's Mod window causes the
  gnome-shell to terminate the user's session.

  [ Test case ]

  - Launch a game (Left 4 Dead 2 or Garry's Mod)
  - Open GNOME Screenshot app
  - Set "Window" in Capture Area menu and "Delay in Seconds" to 2-3 seconds
  - Alt-tab (or switch by Super key) to an open game
  - GNOME Screenshot app terminates the user session with an error "something 
went wrong".

  [ Regression potential ]

  No screenshot may be taken when requested

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

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

[Desktop-packages] [Bug 1904902] Re: Pulseaudio produces a lot of crackling audio after awhile

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

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

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

Title:
  Pulseaudio produces a lot of crackling audio after awhile

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  1) Description:   Ubuntu 20.10
 Release: 20.10

  2) pulseaudio:
Instalado: 1:13.99.2-1ubuntu2
Candidato: 1:13.99.2-1ubuntu2
Tabela de versão:
   *** 1:13.99.2-1ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

  3) What you expected to happen: It shouldn't produce any crackles in the 
audio after a set amount of time.
  4) What happened instead: It starts to crackle with a very low volume, then 
it keeps increasing until it reaches the same volume as the music/audio. 
Running systemctl --user restart pulseaudio.service fixes the issue until the 
next restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 19 14:09:37 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2020-06-16 (156 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1905076] Re: module-alsa-sink's "control" argument causes segmentation fault

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

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

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Status: New => Triaged

** Tags added: fixed-in-3.36.9 fixed-in-3.38.2

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

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Triaged
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell crashes at random times when the Desktop or home directory
  is modified, and the desktop-icons extension tries to refresh.

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

  [Test Case]

  Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell
  should not crash or freeze.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading, like this bug.

  [Other Info]

  See also bug 1898910

  ---

  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

** Package changed: pulseaudio (Ubuntu) => alsa-ucm-conf (Ubuntu)

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

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

Title:
sounds not working on Dell XPS 17 (9700)

Status in alsa-ucm-conf package in Ubuntu:
New
Status in linux package in Ubuntu:
New

Bug description:
My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install
the 5.6 kernel with the above driver. Your system may be more stable
with 5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files
from the Ubuntu linux-firmware package first. Note if this package
gets updated from Canoncial and they don't update these, you will have
to delete and then reextract. Files go into the
/usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers
do not play, you may need to run alsamixer (non-root) from a terminal and
unmute and set the mixer levels all the way up.
"""

This solution worked for me on linux-image-5.6.0-1042-oem AFTER
manually opening alsa-mixer and changing soundcard to sof. The sound
would otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:

https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/

https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/

https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: neoh 1786 F pulseaudio
/dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio
/dev/snd/controlC0: neoh 1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
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: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1912670] Re: Mouse buttons and keyboard unresponsive after idle time

Thanks for the bug report. This sounds a power management problem.

1. If you have 'tlp' installed the please uninstall it. It's known to
cause bugs like this.

2. Try installing 'powertop' and then look in its 'Tunables' section. By
changing some of those to 'Bad' (which is actually better than 'Good' in
this case) you can stop them suspending so much.

3. The kernel team should have some more ideas. I will move this bug
there...


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

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

Title:
  Mouse buttons and keyboard unresponsive after idle time

Status in linux package in Ubuntu:
  New

Bug description:
  If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1,
  Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and
  most keyboard presses become unresponsive. My "system power saving"
  setting is disabled (set to "never") and "display power management" is
  set to blank after 15 minutes, but the problem seems to occur sooner
  than that. Unplugging and re-inserting the mouse after a few seconds
  has no effect.

  The only keystrokes that have any effect are Ctrl+Alt+F1 for a
  terminal session (where I can type normally). Returning to the desktop
  with Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before.
  This occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26
  kernel and the problem happens with that too. When I reboot the
  machine everything works fine again, but after a few minutes of idle
  time, the same problem occurs again. I've only noticed the problem
  occurring in the last ~2-3 weeks.

  When I leave a terminal window open on the desktop running the command:
tail -f /var/log/Xorg.0.log
  and allow lots of time for the problem to occur, no lines are appended in the 
terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 
and log in at the terminal console, the following additional lines appear in 
/var/log/xorg.0.log :
  [  3805.283] (II) event1  - Power Button: device removed
  [  3805.296] (II) event0  - Power Button: device removed
  [  3805.312] (II) event3  - Logitech USB Optical Mouse: device removed
  [  3805.344] (II) event4  - Eee PC WMI hotkeys: device removed
  [  3805.364] (II) event2  - AT Translated Set 2 keyboard: device removed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
  Uname: Linux 5.4.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 16:37:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501]
  InstallationDate: Installed on 2020-05-17 (249 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic 
root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5406
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about

[Desktop-packages] [Bug 1912472] Re: Display freezes randomly - high CPU usage

We can often tell exactly what caused a freeze after rebooting and
looking at the log of the previous boot where the freeze occurred.

Next time the freeze happens, please reboot and then in a Terminal
window run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

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

Title:
  Display freezes randomly - high CPU usage

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Randomly, system freezes with high CPU usage (cooling fan goes high
  when the problem happens) since update to Ubuntu 20.04.1 LTS.

  Same problem with X11 and Wayland.

  Display freezes and keyboard or mouse inputs won't change anything.
  Caps and num lock won't react either.

  Ctrl+alt+anything doesn't solve the issue.

  Only possibility is then to force reboot using power button.

  After reboot, I could find in logs :
  gnome-shell
  libinput error: client bug: timer event6 debounce short: scheduled expiry is 
in the past (-15ms), your system is too slow

  Problem happens in any situation, for example while videoconferencing
  with any software, or using LibreOffice Writer, sometimes with
  Firefox.

  The only common fact seems to be that Firefox is always opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 10:27:48 2021
  InstallationDate: Installed on 2020-11-15 (65 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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/1912472/+subscriptions

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

[Desktop-packages] [Bug 1912667] Re: In vertically stacked monitor setup, most windows open on the top monitor

** Tags added: multimonitor

** Package changed: gnome-control-center (Ubuntu) => gnome-shell
(Ubuntu)

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

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

Title:
  In vertically stacked monitor setup, most windows open on the top
  monitor

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Basically, when I have at least 2 monitors that are vertically stacked, where 
Primary display is on the bottom (see attached screenshot), most apps (on the 
first launch after boot up) and their new windows open up on the second monitor 
(top one). Also, all desktop icons are reset to the top after each boot even if 
they were manually moved to the Primary (bottom) screen.
  What I mean by "on the first launch", for example Chrome (at least if "On 
startup - Continue where you left off" setting is selected), and Spotify, when 
launching first time after booting, they both appear on the top screen. But if 
they are moved, then closed and then opened up once again - they appear at the 
same location where I moved them. By "and their new windows" I mean that, in 
Chrome for example, it works when multiple accounts exist, and so opening each 
of those, will open on the top monitor.
  Some of the apps are pretty random to this and sometimes remember their last 
position, sometimes - no. For example, although the toolbar is on the bottom 
screen, with Jetbrains Toolbox, after opening the Toolbox (from the toolbar 
icon), window will always appear on the top screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 18:41:10 2021
  InstallationDate: Installed on 2020-12-29 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy

Please also check you have the latest version installed:

  dpkg -s gnome-shell-extension-desktop-icons | grep Version

It should say:

  Version: 20.04.0+git20200908-5~ubuntu20.10.0

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

Title:
  gnome-shell freezes randomly after upgrading to groovy

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

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

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

[Desktop-packages] [Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy

Thanks. We released an update to gnome-shell-extension-desktop-icons
this week with some fixes that might help. Please update your system:

  sudo apt update
  sudo apt full-upgrade

and then reboot.

If the freeze still happens after that then when it does, please reboot
and run:

  journalctl -b-1 > prevboot.txt
  lspci -kv > lspci.txt

and attach the resulting text files here.


** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-desktop-icons 
(Ubuntu)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-shell freezes randomly after upgrading to groovy

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

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

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

[Desktop-packages] [Bug 1909241] Re: Unreadable text with two monitors

Thanks. The connected TV appears to be 115 cm x 65 cm, which is about 52
inches diagonally. At FHD that makes it about 42 pixels per inch. So the
real DPI of the TV is more like 42, not 96, meaning text appearing small
by default is probably expected and not a bug.

You will need to tweak your system settings to change the default sizes
of everything, but I don't see a bug here at the moment.


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

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Unreadable text with two monitors

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  - Machine: Dell 15 Inspiron Gaming Laptop (7567)
  - External 1080p60 monitor connected (recognized by X as 1080i60). Changing 
resolution manually fixes the resolution until next reboot.

  When external monitor is already connected before boot, and turning
  system on, X calculates wrong resolution/dpi for the monitors,
  rendering fonts very small. On default Gnome3 desktop, only the window
  titles are affected. On Kubuntu, all SDDM items and several desktop
  resources are affected too, rendering Kubuntu desktop unusable.

  Running gome-tricks applet restore font size when clicking on "Fonts" and 
changing font sizes.
  On Kubuntu, changing font settings does not have any effect. One can run on a 
root terminal "xrandr --dpi 96" as a workaround. But it solves only for the 
next window opening of a program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 24 11:50:44 2020
  DistUpgraded: 2020-08-23 11:50:00,001 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-48-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2020-03-22 (277 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0a93686d-0008-4b58-8574-fe382bc8eda1 ro locale=pt_BR quiet splash 
intel_iommu=on vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-23 (123 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: H70NVN2
  dmi.chassis.type: 10
  dmi.chassis.vendor:

[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

2021-01-21 Thread Chlon Michaël

Hi,

Just install the update and everything is OK, after 
2 weeks ...

Anyway, thanks and good job.

Rgds,

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

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

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

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

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

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

  
  --

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

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

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

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

[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

2021-01-21 Thread iGadget

@Sebastian Bacher - genuine question: does not a single person in the
chromium-snap team use this feature? Because I can't think of any other
reason why this regression (when compared to regular chromium) is
treated like a 'wishlist' item. Please, enlighten me.

Currently, on any Ubuntu recent Ubuntu version you're forced to use
privacy-invading Chrome if you want to use WebApps. Firefox removed the
feature (curiously enough, it does work on mobile), chromium-snap
crippled it, chromium non-snap is pretty hard to install for most users
and leaves you with a(nother) third-party repo on your system. So what's
the rationale here?

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

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

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

[Desktop-packages] [Bug 1303316] Re: Digital S/PDIF output is not present in 5.1 mode

2021-01-21 Thread Hicks

Nothing new?

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

Title:
  Digital S/PDIF output is not present in 5.1 mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have the sound connected through digital S / PDIF 
  Sound works properly selecting stereo, but can not get it to work using 5.1 
  When I select stereo sound, appears on the tab below to phonon spdif output 
option. 
  When I select Output 5.1, that option does not appear. 

  I imagine the error will also occur selecting 7.1

  Deputy screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: phonon 4:4.7.0really4.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Apr  6 13:12:42 2014
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: phonon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1912667] Re: In vertically stacked monitor setup, most windows open on the top monitor

2021-01-21 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => gnome-control-center (Ubuntu)

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

Title:
  In vertically stacked monitor setup, most windows open on the top
  monitor

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

Bug description:
  Basically, when I have at least 2 monitors that are vertically stacked, where 
Primary display is on the bottom (see attached screenshot), most apps (on the 
first launch after boot up) and their new windows open up on the second monitor 
(top one). Also, all desktop icons are reset to the top after each boot even if 
they were manually moved to the Primary (bottom) screen.
  What I mean by "on the first launch", for example Chrome (at least if "On 
startup - Continue where you left off" setting is selected), and Spotify, when 
launching first time after booting, they both appear on the top screen. But if 
they are moved, then closed and then opened up once again - they appear at the 
same location where I moved them. By "and their new windows" I mean that, in 
Chrome for example, it works when multiple accounts exist, and so opening each 
of those, will open on the top monitor.
  Some of the apps are pretty random to this and sometimes remember their last 
position, sometimes - no. For example, although the toolbar is on the bottom 
screen, with Jetbrains Toolbox, after opening the Toolbox (from the toolbar 
icon), window will always appear on the top screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 18:41:10 2021
  InstallationDate: Installed on 2020-12-29 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1912684] Re: gnome-control-center crashed with SIGSEGV in slab_allocator_free_chunk() CUPS

2021-01-21 Thread Gunnar Hjalmarsson

** Information type changed from Private to Public

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

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

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

Bug description:
  I was adjusting CUPS settings for a network printer and I got a crash
  notice.

  I have a Brother MFCL2750DW printer (with the three Brother deb
  packages installed).

  The printer is directly connected to this computer, but I was
  modifying the settings for the NETWORK connected printer to try to
  track down a random printing issue. (The printer occasionally hangs
  when printing a multi-page double-sided document.)

  Opened Gnome Control Center using the "Tools" menu in the top right of
  the Ubuntu desktop.

  Devices --> Printers

  I had just turned OFF the CUPS setting that was sharing all printers
  connected to this PC. The old printer was shared through this computer
  and the new one is connected directly to the network.

  I am looking at the NETWORK printer. (It has underscores in its name:
  "Brother_MFC_L2750DW_series" and it has a a generic icon that looks
  like stacked boxes.)

  I clicked the gear --> Printer Details.

  I clicked Select from Database

  I selected the printer from the list. There were two MFCL2750DW
  drivers listed

  (At some point the icon changed from the generic network printer
  icon.)

  AFTER THIS IS WHERE I BELIEVE IT CRASHED

  I had already chosen a driver

  I clicked the button that said "Search for Drivers"

  Next thing I knew I had the oopsie dialog and the browser opened the
  bug in launchpad.

  
  I know this is old software at this point so feel free to close this if it's 
already known. Just let me know if you need more info. I plan to upgrade to a 
newer version of Ubuntu, but I'm waiting for some regressions to be addressed 
in the LTS.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 12:54:49 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-07 (289 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0705d347f3:mov%rcx,0x18(%rsi)
   PC (0x7f0705d347f3) ok
   source "%rcx" ok
   destination "0x18(%rsi)" (0x1018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_slice_free1()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo

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

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

[Desktop-packages] [Bug 1912667] [NEW] In vertically stacked monitor setup, most windows open on the top monitor

You have been subscribed to a public bug:

Basically, when I have at least 2 monitors that are vertically stacked, where 
Primary display is on the bottom (see attached screenshot), most apps (on the 
first launch after boot up) and their new windows open up on the second monitor 
(top one). Also, all desktop icons are reset to the top after each boot even if 
they were manually moved to the Primary (bottom) screen.
What I mean by "on the first launch", for example Chrome (at least if "On 
startup - Continue where you left off" setting is selected), and Spotify, when 
launching first time after booting, they both appear on the top screen. But if 
they are moved, then closed and then opened up once again - they appear at the 
same location where I moved them. By "and their new windows" I mean that, in 
Chrome for example, it works when multiple accounts exist, and so opening each 
of those, will open on the top monitor.
Some of the apps are pretty random to this and sometimes remember their last 
position, sometimes - no. For example, although the toolbar is on the bottom 
screen, with Jetbrains Toolbox, after opening the Toolbox (from the toolbar 
icon), window will always appear on the top screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 18:41:10 2021
InstallationDate: Installed on 2020-12-29 (22 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy third-party-packages
-- 
In vertically stacked monitor setup, most windows open on the top monitor
https://bugs.launchpad.net/bugs/1912667
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

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

[Desktop-packages] [Bug 1797390] Re: Update to 8.9.15

2021-01-21 Thread Sebastien Bacher

https://bugs.launchpad.net/ubuntu/+source/libphonenumber/8.12.16-3

** Changed in: libphonenumber (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Update to 8.9.15

Status in libphonenumber package in Ubuntu:
  Fix Released
Status in libphonenumber package in Debian:
  New

Bug description:
  Our version is quite outdated (and with delta over Debian), we should
  review the delta and update, it is not a job for eoan though

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

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

[Desktop-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer

2021-01-21 Thread postroutine

Hello,

I got the same problem with the Schiit Audio Fulla 3 and the kernel
5.10.8 on Fedora.

But I got no problem with the Kernel 5.4.59 on Raspbian.

Kurt Bonatz reported a problem with the 5.4.0. Maybe there is a
difference in audio stack between Ubuntu and Raspbian.

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

Title:
  USB DAC/AMP unselectable from Sound Settings  and crashes alsamixer

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing the same issue with the same device described in
  this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1267866/comments/26

  The device works as expected with Windows 10 and macOS no drivers
  required. However, the device is not an option from Ubuntu's sound
  settings. It is visible in alsamixer, however, it crashes immediately
  upon selection with 'cannot load mixer controls: Broken pipe'.

  Here's some more debug information. Let me know if there is anymore I
  can provide or feel free to redirect me if there is another place this
  is better reported.

  Device: Schiit Audio Fulla 3 USB DAC/AMP
  Kernel version: 5.4.0-40-generic
  Ubuntu version: 20.04

  Alsa debug output: http://alsa-
  project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb

  `dmesg -w` output upon re-plugging in the device:
  [  895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd
  [  895.739125] usb 3-2.3: New USB device found, idVendor=30be, 
idProduct=0100, bcdDevice= 1.02
  [  895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  895.739131] usb 3-2.3: Product: I'm Fulla Schiit
  [  895.739133] usb 3-2.3: Manufacturer: Schiit Audio
  [  896.076914] input: Schiit Audio I'm Fulla Schiit as 
/devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20
  [  896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 
Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3
  [  896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/NetworkManager" 
interface="org.freedesktop.NetworkManager" member="CheckPermissions" 
name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1

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

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

[Desktop-packages] [Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy

2021-01-21 Thread Ian Johnson

So indeed after enabling _only_ the Desktop Icon extension I experienced
a freeze. Here are the logs: https://pastebin.ubuntu.com/p/XwJS7N4tF5/

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

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

Title:
  gnome-shell freezes randomly after upgrading to groovy

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

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

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

[Desktop-packages] [Bug 1912673] [NEW] sounds not working on Dell XPS 17 (9700)

2021-01-21 Thread Niklas

Public bug reported:

My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install the
5.6 kernel with the above driver. Your system may be more stable with
5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files from
the Ubuntu linux-firmware package first. Note if this package gets
updated from Canoncial and they don't update these, you will have to
delete and then reextract. Files go into the /usr/lib/firmware/intel/sof
and /usr/lib/firmware/intel/sof-tplg folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers 
do not play, you may need to run alsamixer (non-root) from a terminal and 
unmute and set the mixer levels all the way up.
"""


This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually
opening alsa-mixer and changing soundcard to sof. The sound would
otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:
https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/
https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/
https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  neoh   1786 F pulseaudio
 /dev/snd/pcmC1D0p:   neoh   1786 F...m pulseaudio
 /dev/snd/controlC0:  neoh   1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
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: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal package-from-proposed

** Description changed:

  My investigation process:
  
  Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
  worked.
  
- I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones, 
+ I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
  using linux-image-5.4.0-42-generic, I did not try blutooth.
  
  I sudo apt upgrade, dist-upgrade to get kernels
  
- linux-image-5.8.0-38-generic 
+ linux-image-5.8.0-38-generic
  linux-image-5.8.0-40-generic
  
- Sounds did not work. 
+ Sounds did not work.
  I download linux-image-unsigned-5.10.9-051009-generic.
  Sounds did not work.
  
  I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
  Sounds did not work.
  
  After googling I found this solution in the comments:

[Desktop-packages] [Bug 1912675] [NEW] [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound

2021-01-21 Thread Julian Åström

Public bug reported:

I tried to record with my microphone but its making crackling noises
both microphone and headset

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  julletime   1530 F pulseaudio
 /dev/snd/controlC2:  julletime   1530 F pulseaudio
 /dev/snd/controlC3:  julletime   1530 F pulseaudio
 /dev/snd/controlC1:  julletime   1530 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 18:29:42 2021
InstallationDate: Installed on 2021-01-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:X failed
Symptom_Card: Built-in Audio - Loopback
Symptom_PulseAudioLog: jan 21 18:13:50 julletimes-dator dbus-daemon[793]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=992 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2020
dmi.bios.release: 1.25
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17E2IMS.119
dmi.board.asset.tag: Default string
dmi.board.name: MS-17E2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17E2IMS.119:bd03/16/2020:br1.25:svnMicro-StarInternationalCo.,Ltd.:pnGP75Leopard9SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GP
dmi.product.name: GP75 Leopard 9SD
dmi.product.sku: 17E2.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I tried to record with my microphone but its making crackling noises
  both microphone and headset

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julletime   1530 F pulseaudio
   /dev/snd/controlC2:  julletime   1530 F pulseaudio
   /dev/snd/controlC3:  julletime   1530 F pulseaudio
   /dev/snd/controlC1:  julletime   1530 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 18:29:42 2021
  InstallationDate: Installed on 2021-01-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:X failed
  Symptom_Card: Built-in Audio - Loopback
  Symptom_PulseAudioLog: jan 21 18:13:50 julletimes-dator dbus-daemon[793]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=992 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17E2IMS.119
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17E2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias:

[Desktop-packages] [Bug 1912670] [NEW] Mouse buttons and keyboard unresponsive after idle time

2021-01-21 Thread nick_s

Public bug reported:

If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1,
Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and
most keyboard presses become unresponsive. My "system power saving"
setting is disabled (set to "never") and "display power management" is
set to blank after 15 minutes, but the problem seems to occur sooner
than that. Unplugging and re-inserting the mouse after a few seconds has
no effect.

The only keystrokes that have any effect are Ctrl+Alt+F1 for a terminal
session (where I can type normally). Returning to the desktop with
Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before. This
occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26 kernel
and the problem happens with that too. When I reboot the machine
everything works fine again, but after a few minutes of idle time, the
same problem occurs again. I've only noticed the problem occurring in
the last ~2-3 weeks.

When I leave a terminal window open on the desktop running the command:
  tail -f /var/log/Xorg.0.log
and allow lots of time for the problem to occur, no lines are appended in the 
terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 
and log in at the terminal console, the following additional lines appear in 
/var/log/xorg.0.log :
[  3805.283] (II) event1  - Power Button: device removed
[  3805.296] (II) event0  - Power Button: device removed
[  3805.312] (II) event3  - Logitech USB Optical Mouse: device removed
[  3805.344] (II) event4  - Eee PC WMI hotkeys: device removed
[  3805.364] (II) event2  - AT Translated Set 2 keyboard: device removed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 21 16:37:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501]
InstallationDate: Installed on 2020-05-17 (249 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic 
root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5406
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X470-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Mouse buttons and keyboard unresponsive after idle time

Status in xorg package in Ubuntu:
  New

Bug description:
  If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1,
  Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and
  most keyboard presses become unresponsive. My "system power saving"
  setting is disabled (set to "never") and "display power management" is
  set to blank after 15 minutes, but the problem seems to occur sooner
  than that. Unplugging and re-inserting the mouse after a few seconds
  has no effect.

  The only keystrokes that have any effect are Ctrl+Alt+F1 for a
  terminal session (where I

[Desktop-packages] [Bug 1912668] [NEW] [Q1U dynamic microphone - AT2020 USB, recording] fails after a while

2021-01-21 Thread Guillaume M

Public bug reported:

Opening sound control panel, or Audacity, ATH2020-USB microphone will show 
signal for a few seconds, then cut off (the meter stays stuck in last updated 
position). Same behavior using other apps that use the microphone.
Changed USB port, still the same result.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  surefoot   1972 F pulseaudio
 /dev/snd/controlC2:  surefoot   1972 F pulseaudio
 /dev/snd/controlC1:  surefoot   1972 F pulseaudio
 /dev/snd/pcmC1D0c:   surefoot   1972 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 18:00:16 2021
InstallationDate: Installed on 2020-10-31 (81 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - 
Xonar STX II
Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3902
dmi.board.asset.tag: Default string
dmi.board.name: RAMPAGE V EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3902:bd03/21/2018:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

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

Title:
  [Q1U dynamic microphone - AT2020 USB, recording] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Opening sound control panel, or Audacity, ATH2020-USB microphone will show 
signal for a few seconds, then cut off (the meter stays stuck in last updated 
position). Same behavior using other apps that use the microphone.
  Changed USB port, still the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  surefoot   1972 F pulseaudio
   /dev/snd/controlC2:  surefoot   1972 F pulseaudio
   /dev/snd/controlC1:  surefoot   1972 F pulseaudio
   /dev/snd/pcmC1D0c:   surefoot   1972 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 18:00:16 2021
  InstallationDate: Installed on 2020-10-31 (81 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) 
- Xonar STX II
  Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3902
  dmi.board.asset.tag: Default string
  dmi.board.name: RAMPAGE V EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string

[Desktop-packages] [Bug 1912659] [NEW] [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the sound

2021-01-21 Thread Michal Trachta

Public bug reported:

alsa force-reload + reboot helps, but only temporarily (similar to Bug
#1874689)

Unplugging and plugging in the headphones again results in losing the
sound.

During the time I was reporting the bug, the sound was OK. I unplugged
and plugged the headphones in -> no sound. Quite surprisingly, when I
finished the bug reporting, the sound was back.

Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer
hardware may be responsible for the issues

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 17:20:23 2021
InstallationDate: Installed on 2020-07-02 (203 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_Jack: Green Headphone Out, Front
Symptom_PulseAudioLog:
 led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
 led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] fails after a 
while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20a
dmi.board.asset.tag: Default string
dmi.board.name: X570 UD
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20a:bd06/16/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 UD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the
  sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  alsa force-reload + reboot helps, but only temporarily (similar to Bug
  #1874689)

  Unplugging and plugging in the headphones again results in losing the
  sound.

  During the time I was reporting the bug, the sound was OK. I unplugged
  and plugged the headphones in -> no sound. Quite surprisingly, when I
  finished the bug reporting, the sound was back.

  Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer
  hardware may be responsible for the issues

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 17:20:23 2021
  InstallationDate: Installed on 2020-07-02 (203 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulseAudioLog:
   led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front]

[Desktop-packages] [Bug 1910709] Update Released

2021-01-21 Thread Łukasz Zemczak

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

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

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

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

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

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

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

  
  --

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

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

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

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

[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.108-0ubuntu5.20.04.1

---
nvidia-graphics-drivers-340 (340.108-0ubuntu5.20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1910709)

 -- Timo Aaltonen   Thu, 14 Jan 2021 09:40:28 +0200

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

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

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

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

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

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

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

  
  --

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

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

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

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

[Desktop-packages] [Bug 783794]

2021-01-21 Thread kompilainenn

Still repro in

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 94f6765d6ecc3145fa2d266231124003cf953118
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

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

Title:
  [Upstream] Black text converted to white opening pptx

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description: Ubuntu 11.04
  Release: 11.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.3-1ubuntu1
Candidate: 1:3.3.3-1ubuntu1
Version table:
   *** 1:3.3.3-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Impress via the Terminal:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/783794/+attachment/2131821/+files/EDC%20Presentation%281%29.pptx
  -O info.pptx && loimpress -nologo info.pptx

  is the black text on white background for slide 2 looks as it does in
  PowerPoint.

  4) What happens instead is the black text is converted to white.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Mon May 16 22:45:50 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/783794/+subscriptions

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

[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

2021-01-21 Thread Stefan Belishki

I have the same errors in the syslog file and I am using Logitech mouse MX 
Master:
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

Regards

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

Title:
  Window manager warning: Overwriting existing binding of keysym 37 with
  keysym 37 (keycode 10).

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

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

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

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

[Desktop-packages] [Bug 1909241] Re: Unreadable text with two monitors

2021-01-21 Thread Luzemário

The external monitor is 'HDMI-0', connected to NVIDIA HDMI port.

** Attachment added: "Screenshot_20210121_123056.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909241/+attachment/5455172/+files/Screenshot_20210121_123056.png

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

Title:
  Unreadable text with two monitors

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  - Machine: Dell 15 Inspiron Gaming Laptop (7567)
  - External 1080p60 monitor connected (recognized by X as 1080i60). Changing 
resolution manually fixes the resolution until next reboot.

  When external monitor is already connected before boot, and turning
  system on, X calculates wrong resolution/dpi for the monitors,
  rendering fonts very small. On default Gnome3 desktop, only the window
  titles are affected. On Kubuntu, all SDDM items and several desktop
  resources are affected too, rendering Kubuntu desktop unusable.

  Running gome-tricks applet restore font size when clicking on "Fonts" and 
changing font sizes.
  On Kubuntu, changing font settings does not have any effect. One can run on a 
root terminal "xrandr --dpi 96" as a workaround. But it solves only for the 
next window opening of a program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 24 11:50:44 2020
  DistUpgraded: 2020-08-23 11:50:00,001 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-48-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2020-03-22 (277 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0a93686d-0008-4b58-8574-fe382bc8eda1 ro locale=pt_BR quiet splash 
intel_iommu=on vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-23 (123 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: H70NVN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd06/19/2020:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  version.compiz:

[Desktop-packages] [Bug 1909241] Re: Unreadable text with two monitors

2021-01-21 Thread Luzemário

Here is.

** Attachment added: "xrandr2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909241/+attachment/5455171/+files/xrandr2.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/1909241

Title:
  Unreadable text with two monitors

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  - Machine: Dell 15 Inspiron Gaming Laptop (7567)
  - External 1080p60 monitor connected (recognized by X as 1080i60). Changing 
resolution manually fixes the resolution until next reboot.

  When external monitor is already connected before boot, and turning
  system on, X calculates wrong resolution/dpi for the monitors,
  rendering fonts very small. On default Gnome3 desktop, only the window
  titles are affected. On Kubuntu, all SDDM items and several desktop
  resources are affected too, rendering Kubuntu desktop unusable.

  Running gome-tricks applet restore font size when clicking on "Fonts" and 
changing font sizes.
  On Kubuntu, changing font settings does not have any effect. One can run on a 
root terminal "xrandr --dpi 96" as a workaround. But it solves only for the 
next window opening of a program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 24 11:50:44 2020
  DistUpgraded: 2020-08-23 11:50:00,001 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-48-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2020-03-22 (277 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0a93686d-0008-4b58-8574-fe382bc8eda1 ro locale=pt_BR quiet splash 
intel_iommu=on vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-23 (123 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: H70NVN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd06/19/2020:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2

[Desktop-packages] [Bug 1912536] Re: Gnome Disk Utility can't mount audio CDs

2021-01-21 Thread Frank

At one time, gnome-disks or gnome-disk-utility did detect audio CDs.  I
just fired up Linux Mint 20.1 on a USB flash drive and whatever version
of gnome-disk-utility it has, it shows "Audio CD" instead of "unknown."

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

Title:
  Gnome Disk Utility can't mount audio CDs

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  1)  Ubuntu 20.10
  2)  3.38.0-1ubuntu1
  3)  Gnome Disks should be able to see an audio CD when mounted. 
  4)  Instead I get "unknown" in the contents and the Audio CD cannot be read.  
This occurs only in Ubuntu and not in Windows (dual boot).  Tried multiple CDs. 
 I also get the exact error on a USB Blu Ray drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-disk-utility 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Wed Jan 20 16:22:24 2021
  InstallationDate: Installed on 2020-09-16 (126 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to groovy on 2020-11-29 (52 days ago)

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

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

2021-01-21 Thread Dimitri John Ledkov

** Changed in: nvidia-prime (Ubuntu Focal)
Milestone: None => ubuntu-20.04.2

-- 
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:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

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.

  The nvidia-prime package also has a change to fix a problem where
  /lib/udev/rules.d/50-pm-nvidia.rules was left behind, after a system
  upgrade 20.04 LTS (focal) to 20.10 (groovy), and yet prime-select had
  lost the ability to remove the udev rules file, leaving the end user
  with no means to re-enable his/her Nvidia GPU.

  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.3~0.20.10.1) groovy; urgency=medium

* debian/postinst.in:
  - Remove obsolete udev rules (LP: #1904583).
* debian/rules:
  - Add postinst file to the autoclean target.
* prime-select:
  - Do not try to apply any changes unless an integrated GPU is
available.

  == 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.3~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.
* debian/postinst.in:
  - Remove obsolete udev rules in the postinst too.
* debian/rules:
  - Add

[Desktop-packages] [Bug 1912472] Re: Display freezes randomly - high CPU usage

2021-01-21 Thread Tristan Boureau

I have those manually installed extensions :
- hibernate-status@dromi
- update-extensi...@franglais125.gmail.com

I disabled them as required, so as to test if problem persists.

In case it does, I will tell you here in a new comment.

In case it solves the issue, I can't tell after how much time we can consider 
the problem fixed, as it has happened three times some days, and in december it 
only happened one time in total, it's totally random.
I can just tell that it didn't happen with the two previous LTS releases.
And that it persists after a complete OS re-install.

How should we process in case the problem doesn't happen for weeks ?

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

Title:
  Display freezes randomly - high CPU usage

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Randomly, system freezes with high CPU usage (cooling fan goes high
  when the problem happens) since update to Ubuntu 20.04.1 LTS.

  Same problem with X11 and Wayland.

  Display freezes and keyboard or mouse inputs won't change anything.
  Caps and num lock won't react either.

  Ctrl+alt+anything doesn't solve the issue.

  Only possibility is then to force reboot using power button.

  After reboot, I could find in logs :
  gnome-shell
  libinput error: client bug: timer event6 debounce short: scheduled expiry is 
in the past (-15ms), your system is too slow

  Problem happens in any situation, for example while videoconferencing
  with any software, or using LibreOffice Writer, sometimes with
  Firefox.

  The only common fact seems to be that Firefox is always opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 10:27:48 2021
  InstallationDate: Installed on 2020-11-15 (65 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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/1912472/+subscriptions

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

[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-21 Thread Hadmut Danisch

Oh yeah, that helps! :-)


Uldis, can you confirm?

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1

[Desktop-packages] [Bug 1899437] Re: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed libglib2.0-cil package post-installation script subprocess returned error exit status 1

2021-01-21 Thread Olav Kvittem

happened during dorelease-upgrade from 18.04 to 20.04
Could not install the upgrades 

The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a). 

Setting up libglib2.0-cil (2.12.40-3) ...
* Installing 1 assembly from libglib2.0-cil into Mono
Setting up libglib2.0-cil-dev (2.12.40-3) ...

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

Title:
  package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed
  libglib2.0-cil package post-installation script subprocess returned
  error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  Confirmed

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-cil 2.12.40-3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 12 09:13:09 2020
  ErrorMessage: installed libglib2.0-cil package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-26 (809 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed 
libglib2.0-cil package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-sharp2/+bug/1899437/+subscriptions

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

[Desktop-packages] [Bug 1911903] Re: Auto-reconnection of wifi doesn't work

2021-01-21 Thread Antonio Mazzarino

** Attachment added: "Evidences"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+attachment/5455167/+files/Evidences

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

Title:
  Auto-reconnection of wifi doesn't work

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi everyone :)

  It's a problem that occurs without any possible correlation with other
  event (wake up, sleep etc).

  In the middle of a session the Wi-Fi simply stop working and not only
  the system doesn't reconnect automatically, but you need to turn off
  and back on the Wi-Fi to be able to continue your activities.

  IDK if it's related, but sometimes also happens that the other Wi-Fi
  networks around me are not visible in the setting.

  If I can help in any way with logs of any other information please
  contact me

  Antonio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 15 12:56:08 2021
  InstallationDate: Installed on 2020-11-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev wlp2s0b1 proto dhcp metric 20600 
   169.254.0.0/16 dev br-90c79c39374f scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-90c79c39374f proto kernel scope link src 172.18.0.1 
linkdown 
   192.168.178.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.178.52 
metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.22.10  connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+subscriptions

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

[Desktop-packages] [Bug 1849680] Re: audit spam in dmesg (libreoffice)

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

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

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

Title:
  audit spam in dmesg (libreoffice)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  My dmesg is getting flooded by apparmor audit messages, mostly from
  libreoffice (profiles libreoffice-soffice and libreoffice-oosplash):

  $ dmesg | tail -n 25
  [13682.452555] audit: type=1400 audit(1571920851.001:3672): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453430] audit: type=1400 audit(1571920851.001:3673): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453933] audit: type=1400 audit(1571920851.001:3674): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.455491] audit: type=1400 audit(1571920851.005:3675): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=17792 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [13682.604100] audit: type=1400 audit(1571920851.153:3676): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13682.604138] audit: type=1400 audit(1571920851.153:3677): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris-22028640.log"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13683.097648] audit: type=1400 audit(1571920851.645:3678): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.mozilla/firefox/vq2zzheq.chris-2019-09/cert8.db" pid=17791 
comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  [16676.510664] kauditd_printk_skb: 1210 callbacks suppressed
  [16676.510665] audit: type=1400 audit(1571923845.047:4889): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.511473] audit: type=1400 audit(1571923845.047:4890): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.550636] audit: type=1400 audit(1571923845.087:4891): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.551394] audit: type=1400 audit(1571923845.087:4892): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552145] audit: type=1400 audit(1571923845.087:4893): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552568] audit: type=1400 audit(1571923845.087:4894): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.553912] audit: type=1400 audit(1571923845.091:4895): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=18543 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [16694.388901] audit: type=1400 audit(1571923862.923:4896): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/mountinfo" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388972] audit: type=1400 audit(1571923862.923:4897): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/cgroup" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388992] audit: type=1400 audit(1571923862.923:4898): 
apparmor="ALLOWED"

[Desktop-packages] [Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy

2021-01-21 Thread Ian Johnson

So after a full day of usage yesterday I did not see the freeze/crash at
all, so it does indeed appear to be caused by one of the extensions
bundled with Ubuntu. Should I try just enabling them one-by-one using
the Extensions app?

I can't remember what all Extensions are enabled by default, but I am
fairly confident the "Desktop Icons" extension was enabled so I'll start
with enabling that one today and see if the freezes reproduce.

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

Title:
  gnome-shell freezes randomly after upgrading to groovy

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

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

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-21 Thread Joe Zhou

Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad
now works with kernel 5.11.0, but it has problem with Nvidia GPU and the
brightness control is not working. I can have Nvidia GPU working and
manually do some fixes to enable brightness control with 5.8.0, though
touch pad is not working.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date:

[Desktop-packages] [Bug 1912536] Re: Gnome Disk Utility can't mount audio CDs

2021-01-21 Thread Daniel Letzeisen

Note: Audio CD's don't have a filesystem and don't mount. I don't use
Gnome or Gnome Disks, so I can't tell you whether this is expected
behavior for an audio CD or the program should offer more info about the
disc.

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

Title:
  Gnome Disk Utility can't mount audio CDs

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  1)  Ubuntu 20.10
  2)  3.38.0-1ubuntu1
  3)  Gnome Disks should be able to see an audio CD when mounted. 
  4)  Instead I get "unknown" in the contents and the Audio CD cannot be read.  
This occurs only in Ubuntu and not in Windows (dual boot).  Tried multiple CDs. 
 I also get the exact error on a USB Blu Ray drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-disk-utility 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Wed Jan 20 16:22:24 2021
  InstallationDate: Installed on 2020-09-16 (126 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to groovy on 2020-11-29 (52 days ago)

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

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

[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution

2021-01-21 Thread Dale Sch.

Same issue with my Ultrawide.
Workaround:
xrandr --newmode "2560x999_60.00"  211.75  2560 2720 2984 3408  999 1002 1012 
1037 -hsync +vsync
xrandr --addmode Virtual1 2560x999_60.00
xrandr --output Virtual1 --mode 2560x999_60.00

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

Title:
  XrandR does not propose 3440x1440 21:9 resolution

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 :

  How to reproduce :

  
  - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor 

  - Only 16:9 are proposed by xrandR

  - XrandR should propose all supported resolutions


  
  WorkAround : manually add the mode 

  
  xrandr --newmode "3440x1440_30.00"  196.90  3440 3600 3960 4480  1440 1441 
1444 1465  -HSync +Vsync
  xrandr --addmode HDMI-2 3440x1440_30.00
  xrandr --output HDMI-2 --mode 3440x1440_30.00

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

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

[Desktop-packages] [Bug 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band

2021-01-21 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  mac80211_hwsim: hostapd fails to start with S1G band

Status in wpa package in Ubuntu:
  New
Status in wpa source package in Hirsute:
  New

Bug description:
  Hostapd fails to start on a recent 5.10+ kernel:

  $ cat repro.sh 
  #!/bin/sh

  sudo modprobe mac80211_hwsim
  sudo  ip a flush dev wlan0
  sudo  ip a add 192.168.5.1/24 dev wlan0

  cat << EOF > hostapd.conf
  interface=wlan0
  driver=nl80211
  hw_mode=b
  channel=1
  ssid=fake net
  EOF

  sudo  hostapd hostapd.conf

  ubuntu@hirsute-amd64:~$ ./repro.sh 
  Configuration file: hostapd.conf
  nl80211: kernel reports: expected nested data
  Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net"
  wlan0: interface state UNINITIALIZED->ENABLED
  wlan0: AP-ENABLED 
  ^C
  wlan0: interface state ENABLED->DISABLED
  wlan0: AP-DISABLED  
  wlan0: CTRL-EVENT-TERMINATING 
  nl80211: deinit ifname=wlan0 disabled_11b_rates=0

  this due to the mismanagement of the newly added S1G band, the
  attached patch fixes it.

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

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

2021-01-21 Thread Alberto Milone

Tested on a Dell G7 laptop in Groovy:

:~$ apt-cache policy nvidia-prime
nvidia-prime:
  Installed: 0.8.15.3~0.20.10.1
  Candidate: 0.8.15.3~0.20.10.1
  Version table:
 *** 0.8.15.3~0.20.10.1 100
100 /var/lib/dpkg/status
 0.8.15 500
500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu groovy/main i386 Packages

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.8.6.3~0.20.10.1
  Candidate: 1:0.8.6.3~0.20.10.1
  Version table:
 *** 1:0.8.6.3~0.20.10.1 100
100 /var/lib/dpkg/status
 1:0.8.6.2 500
500 http://it.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
 1:0.8.6.1 500
500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

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

-- 
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:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in ubuntu-drivers-common source package in Groovy:
  Fix Committed

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.

  The nvidia-prime package also has a change to fix a problem where
  /lib/udev/rules.d/50-pm-nvidia.rules was left behind, after a system
  upgrade 20.04 LTS (focal) to 20.10 (groovy), and yet prime-select had
  lost the ability to remove the udev rules file, leaving the end user
  with no means to re-enable his/her Nvidia GPU.

  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

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2021-01-21 Thread Biep

Same here, 20.04 installed on a reformatted disk.  Nine months without
this problem (which had pestered me on 19.10), and now it suddenly pops
up - literally.  Any progress?

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band

2021-01-21 Thread Paolo Pisati

** Patch added: "Upstream cherry pick for S1G band fix"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455144/+files/wpa_2.9-1ubuntu10.debdiff

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

Title:
  mac80211_hwsim: hostapd fails to start with S1G band

Status in wpa package in Ubuntu:
  New
Status in wpa source package in Hirsute:
  New

Bug description:
  Hostapd fails to start on a recent 5.10+ kernel:

  $ cat repro.sh 
  #!/bin/sh

  sudo modprobe mac80211_hwsim
  sudo  ip a flush dev wlan0
  sudo  ip a add 192.168.5.1/24 dev wlan0

  cat << EOF > hostapd.conf
  interface=wlan0
  driver=nl80211
  hw_mode=b
  channel=1
  ssid=fake net
  EOF

  sudo  hostapd hostapd.conf

  ubuntu@hirsute-amd64:~$ ./repro.sh 
  Configuration file: hostapd.conf
  nl80211: kernel reports: expected nested data
  Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net"
  wlan0: interface state UNINITIALIZED->ENABLED
  wlan0: AP-ENABLED 
  ^C
  wlan0: interface state ENABLED->DISABLED
  wlan0: AP-DISABLED  
  wlan0: CTRL-EVENT-TERMINATING 
  nl80211: deinit ifname=wlan0 disabled_11b_rates=0

  this due to the mismanagement of the newly added S1G band, the
  attached patch fixes it.

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

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

[Desktop-packages] [Bug 1912609] [NEW] mac80211_hwsim: hostapd fails to start with S1G band

2021-01-21 Thread Paolo Pisati

Public bug reported:

Hostapd fails to start on a recent 5.10+ kernel:

$ cat repro.sh 
#!/bin/sh

sudo modprobe mac80211_hwsim
sudo  ip a flush dev wlan0
sudo  ip a add 192.168.5.1/24 dev wlan0

cat << EOF > hostapd.conf
interface=wlan0
driver=nl80211
hw_mode=b
channel=1
ssid=fake net
EOF

sudo  hostapd hostapd.conf

ubuntu@hirsute-amd64:~$ ./repro.sh 
Configuration file: hostapd.conf
nl80211: kernel reports: expected nested data
Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED 
^C
wlan0: interface state ENABLED->DISABLED
wlan0: AP-DISABLED  
wlan0: CTRL-EVENT-TERMINATING 
nl80211: deinit ifname=wlan0 disabled_11b_rates=0

this due to the mismanagement of the newly added S1G band, the attached
patch fixes it.

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

** Affects: wpa (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Patch added: "Upstream cherry pick for S1G band fix"
   
https://bugs.launchpad.net/bugs/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff

** Also affects: wpa (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Patch removed: "Upstream cherry pick for S1G band fix"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff

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

Title:
  mac80211_hwsim: hostapd fails to start with S1G band

Status in wpa package in Ubuntu:
  New
Status in wpa source package in Hirsute:
  New

Bug description:
  Hostapd fails to start on a recent 5.10+ kernel:

  $ cat repro.sh 
  #!/bin/sh

  sudo modprobe mac80211_hwsim
  sudo  ip a flush dev wlan0
  sudo  ip a add 192.168.5.1/24 dev wlan0

  cat << EOF > hostapd.conf
  interface=wlan0
  driver=nl80211
  hw_mode=b
  channel=1
  ssid=fake net
  EOF

  sudo  hostapd hostapd.conf

  ubuntu@hirsute-amd64:~$ ./repro.sh 
  Configuration file: hostapd.conf
  nl80211: kernel reports: expected nested data
  Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net"
  wlan0: interface state UNINITIALIZED->ENABLED
  wlan0: AP-ENABLED 
  ^C
  wlan0: interface state ENABLED->DISABLED
  wlan0: AP-DISABLED  
  wlan0: CTRL-EVENT-TERMINATING 
  nl80211: deinit ifname=wlan0 disabled_11b_rates=0

  this due to the mismanagement of the newly added S1G band, the
  attached patch fixes it.

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

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

[Desktop-packages] [Bug 1912472] Re: Display freezes randomly - high CPU usage

I mean gnome-shell extensions. In your list of apps you will find one
called 'Extensions'.

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

Title:
  Display freezes randomly - high CPU usage

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Randomly, system freezes with high CPU usage (cooling fan goes high
  when the problem happens) since update to Ubuntu 20.04.1 LTS.

  Same problem with X11 and Wayland.

  Display freezes and keyboard or mouse inputs won't change anything.
  Caps and num lock won't react either.

  Ctrl+alt+anything doesn't solve the issue.

  Only possibility is then to force reboot using power button.

  After reboot, I could find in logs :
  gnome-shell
  libinput error: client bug: timer event6 debounce short: scheduled expiry is 
in the past (-15ms), your system is too slow

  Problem happens in any situation, for example while videoconferencing
  with any software, or using LibreOffice Writer, sometimes with
  Firefox.

  The only common fact seems to be that Firefox is always opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 10:27:48 2021
  InstallationDate: Installed on 2020-11-15 (65 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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/1912472/+subscriptions

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

[Desktop-packages] [Bug 1912472] Re: Display freezes randomly - high CPU usage

2021-01-21 Thread Tristan Boureau

I never use fullscreen function under Firefox, so the problem is not
related to the mentioned bug.

Do you mean Firefox, or gnome-shell extensions ?

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

Title:
  Display freezes randomly - high CPU usage

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Randomly, system freezes with high CPU usage (cooling fan goes high
  when the problem happens) since update to Ubuntu 20.04.1 LTS.

  Same problem with X11 and Wayland.

  Display freezes and keyboard or mouse inputs won't change anything.
  Caps and num lock won't react either.

  Ctrl+alt+anything doesn't solve the issue.

  Only possibility is then to force reboot using power button.

  After reboot, I could find in logs :
  gnome-shell
  libinput error: client bug: timer event6 debounce short: scheduled expiry is 
in the past (-15ms), your system is too slow

  Problem happens in any situation, for example while videoconferencing
  with any software, or using LibreOffice Writer, sometimes with
  Firefox.

  The only common fact seems to be that Firefox is always opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 10:27:48 2021
  InstallationDate: Installed on 2020-11-15 (65 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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/1912472/+subscriptions

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

[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep