[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound

[Tim Richardson]

I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04
and 20.10 (a fairly new AMD Ryzen desktop system, different to the
machine I had the problem on earlier, which was a laptop). Not 24 hours
later, this problem again. I thought there was something wrong with Team
app ('bloody microsoft') but then my next meeting in Google Meet had the
same problem. And YouTube.

Then I remembered this.

This time I just removed speech-dispatcher. Maybe it is not installed by
default on pop, not sure. An ugly papercut.

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions

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

[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[Anthony Wong]

** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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

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

[Desktop-packages] [Bug 797094] Re: lxsession in Lubuntu uses 100% CPU

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: gnome-power-manager (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  lxsession in Lubuntu uses 100% CPU

Status in gnome-power:
  Unknown
Status in gnome-power-manager package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lxsession

  After fresh install of Lubuntu 11.10 alpha 1 on Acer Travelmate 240,
  after booting, the CPU usage is 100%. The fan rotates at moderate
  speed, accordingly.

  Killing the "/usr/bin/lxsession -s Lubuntu -e LXDE" process in htop
  makes the CPU usage drop near zero. (However, this either kills the
  desktop session, or only resets the user settings -- none of which is
  acceptable.)

  This bug was hard to determine, as htop shows 0.0% CPU usage at the
  line of the "/usr/bin/lxsession (...)" process (!).

  EDIT: I made a mistake reporting the bug. It is in _gnome-power-
  manager_, not in lxsession, which only was the parent process.

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

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

[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

Note: Lubuntu (universe) packages in Xenial 16.04 are unsupported,
having been since 2019-April.

** Changed in: lightdm
   Status: Triaged => Incomplete

** Changed in: lightdm/1.18
   Status: Triaged => Incomplete

** Changed in: hundredpapercuts
   Status: Triaged => Incomplete

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

** Changed in: lxsession (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Incomplete
Status in Light Display Manager:
  Incomplete
Status in Light Display Manager 1.18 series:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete
Status in lxsession package in Ubuntu:
  Incomplete
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

You probably need to be logged into a graphical session before that last
command will work.

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

[Oleg]

Same issue here with the files copied from my Sony a6000 camera. Any
suggestions how to fix it?

>After installing fuse-exfat 
It gives me "E: Unable to locate package fuse-exfat"

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[sepukkuhero]

The last command resulted in this error:

"failed to commit changes to dconf: Não foi possível iniciar
automaticamente o D-Bus sem X11 $DISPLAY"

Something like: "D-Bus could not be started automatically without X11 $
DISPLAY"

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

Thanks but that still shows you have a lot of extensions enabled, so
let's forcefully clean them out:

  cd ~/.local/share/gnome-shell
  rm -rf extensions
  gsettings reset org.gnome.shell enabled-extensions

then log out and log in again. Does the problem still occur?

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905200] Re: Ubuntu-dock in Wayland slow

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1874578
   [wayland] dock has very long load time when show-mounts is enabled

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

Title:
  Ubuntu-dock in Wayland slow

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

Bug description:
  Only in Ubuntu's wayland session, on 20.04 and 20.10:

  App icons will appear with a massive delay (~10 seconds) after
  launching an app currently not in the favorites.

  Also moving pinned icons within the dock will only appear in the new
  location after a similar long time span. Otherwise the dock works
  without delays.

  I could see this behavior on two completely different machines. No
  problems in the default Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 21:46:23 2020
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1905185] Re: [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work

[Daniel van Vugt]

** Summary changed:

- [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to detect 
card
+ [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work

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

Title:
  [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not
  work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  good evening, I have a problem with internal microphone, sometimes it works 
and sometimes it doesn't, it happens randomly, just a restart
  my pc should be Ubuntu certified

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
   /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 18:32:04 2020
  InstallationDate: Installed on 2020-11-20 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET56W(1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UJ0014IX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UJ0014IX
  dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1905228] Re: DIsplay Rotates to Portrait Mode when Certain Apps Open

[Daniel van Vugt]

Interestingly Xwayland thinks the screen is portrait:

XWAYLAND2 connected 2160x3840+0+0 (0x3d3) normal (normal left inverted
right x axis y axis) 190mm x 340mm

but the BIOS and Xorg think it is landscape:

[0.495406] efifb: mode is 3840x2160x32, linelength=15360, pages=1

[52.062] (II) modeset(0): Modeline "3840x2160"x60.0  533.25  3840
3888 3920 4000  2160 2163 2168  -hsync -vsync (133.3 kHz eP)

so that makes me think it's just mutter/gnome-shell giving the wrong
info to Xwayland and certain apps.

Do you find the same bug in Xorg sessions? Try logging into 'Ubuntu'
instead of 'Ubuntu on Wayland'.

** Tags added: amdgpu hybrid

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

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

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

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

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

Title:
  DIsplay Rotates to Portrait Mode when Certain Apps Open

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

Bug description:
  When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2
  in 1), the screen will frequently incorrectly rotate whenever some
  apps open. This has been observed with Settings, Videos, Steam,
  Lollypop and Firefox. Issue still occurs when the screen rotation is
  locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 22:59:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530 2-in-1
  dmi.product.sku: 08AC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1905184] Re: [Intel Gemini Lake] No video signal during Ubuntu splash screen and also during Logon procedure

[Daniel van Vugt]

This sounds like a kernel problem. And both plymouth and the login
screen do use the same kernel interfaces...

First, please try removing these kernel parameters:

  video=efifb fbcon=rotate:1

and if that doesn't solve it please also try changing the kernel
parameter "splash" to "nosplash".

Also you may be able to use this as a workaround for the login screen:
Edit /etc/gdm3/custom.conf and change:

  #WaylandEnable=false

to

  WaylandEnable=false


** Summary changed:

- No video signal during Ubuntu splash screen and also during Logon procedure
+ [Intel Gemini Lake] No video signal during Ubuntu splash screen and also 
during Logon procedure

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

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

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

Title:
  [Intel Gemini Lake] No video signal during Ubuntu splash screen and
  also during Logon procedure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

  To workaround this error, I can either:

  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
  Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.

  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.

  Workaround 3) Although I don't have video signal during Boot Splash and Logon 
screen, I do have backlight continuously applied to the display.
  If I wait 5 minutes or so in the logon screen the backlight will deactivate...
  However, when I touch the keyboard or touchpad the computer will then show 
video signal and I will be able to see the logon screen perfectly.
  Problem: I don't want to wait 5 minutes in the logon screen to obtain proper 
video signal.

  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Feel free to request any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Nov 22 19:56:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS CMPC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02.00.STD
  dmi.board.asset.tag: Default string
  dmi.board.name: ik Educational Software
  dmi.board.vendor: ECS
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 30
  dmi.chassis.vendor: NULL
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: CMPC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  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
  

[Desktop-packages] [Bug 1905153] Re: Brightness only works on one display, not two

[Daniel van Vugt]

Laptop brightness is unfortunately not an attribute of the screen
itself, but of the backlight. So Linux can only easily control the
brightness of those screens with known backlight interfaces, which means
the laptop monitor only.

If you wish to adjust the brightness of any other monitor then you
should do so using the monitor's own buttons so as to not lose colour
detail. If you don't mind losing colour detail then you can also use
something like:

  xrandr --output NAME --brightness VALUE

Even if interfaces did exist to implement what you want, we could still
never know the relative brightness of different models of LCD panel. So
choosing one brightness value for two different screens would be kind of
useless. Safe to say this will never be implemented, at least not as a
single brightness value.


** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Brightness only works on one display, not two

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

Bug description:
  Dell Inspiron 15-3567, Hirsute

  My display setup is the laptop and on the right a monitor.

  As I change my brightness, lower or higher, on the laptop the
  brightness will change but on the monitor it won't.

  Not the physical monitor brightness-that obviously can't be
  controlled-but the content of what the monitor shows should be
  dimming/brightening.  (For example if theoretically I turned the
  brightness to 0, to an all dark screen, it should be all dark on the
  monitor aswell, even if the monitor brightness is max, the OS is
  showing nothing)

  Yes, I looked through GNOME's settings daemon and this is most likely
  the package this occurs in.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 02:03:00 2020
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201120)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1905153/+subscriptions

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

[Azizkhan]

@pedrib,
am I right new kernel 5.9.10 includes fixes for our touchpad? Branch you gave 
as i see already included in 5.9.10...

-- 
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:
  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: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: 

[Desktop-packages] [Bug 1905142] Re: When vblank is send the monitors turn off then immediatly turn back on

[Daniel van Vugt]

It sounds like there are two bugs here so please choose which one you
would like this bug to be about.

Also "vblank" is something that happens 60 times per second when the
monitor is on, so I don't think you mean "vblank". Do you mean sleep
mode?

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Incomplete

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

Title:
  When vblank is send the monitors turn off then immediatly turn back on

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

Bug description:
  every time that happens the following message is shown in syslog:
  /usr/libexec/gdm-x-session[3330]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot 
get last vblank counter

  Also, the monitors turn on one by one which means that all windows are
  moved to the one that turns on first.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Uname: Linux 5.8.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 21 18:38:27 2020
  DistUpgraded: 2020-11-18 01:07:32,653 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2316]
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-30-generic 
root=UUID=556540f5-c271-4a31-8207-81a7fcaac401 ro amdgpu.dc=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-11-18 (3 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-03-16T23:17:19.931496
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Nov 17 23:04:32 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.4

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

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

[Desktop-packages] [Bug 1412066] Re: Cannot configure the vino-server "security type" control

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  Cannot configure the vino-server "security type" control

Status in vino package in Ubuntu:
  Incomplete

Bug description:
  I was setting up a testcase for gnome's vino server. Vino had to be
  tested to confirm it works at the basic level of vnc connection.

  Packages installed: vino, xvnc4viewer

  After installing vino and xvnc4viewer, in lubuntu, (xubuntu with
  lubuntu-desktop installed). The vino-server was started in Lubuntu
  14.04 using this following command: /usr/lib/vino/vino-server &. This
  is the output of the following command.

  (vino-server:16269): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-3lXPtqLo8q: Connection
  refused

  (vino-server:16269): EggSMClient-CRITICAL **: egg_sm_client_set_mode: 
assertion 'global_client == NULL || global_client_mode == 
EGG_SM_CLIENT_MODE_DISABLED' failed
  17/01/2015 04:39:40 PM WARNING: Width (1366) is not a multiple of 4. 
VncViewer has problems with that.
  17/01/2015 04:39:42 PM Autoprobing TCP port in (all) network interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
  17/01/2015 04:39:42 PM Autoprobing selected port 5900
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
  17/01/2015 04:39:42 PM Clearing securityTypes
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Clearing securityTypes
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Advertising authentication type: 'No Authentication' 
(1)
  17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900

  I have read multiple tutorials outlining procedures to enable and
  connect to a vino-server. In all instructions, "ssh" was used to
  establish the connection. This is the form of the command  to connect
  to a vino-server.

  "ssh -L 12345:localhost:5900 username@ipaddress".

  I tried testing vino on my own laptop by connecting to itself.

  Whenever I performed the connection with or without ssh, I always get
  this output from the server:

  17/01/2015 04:19:08 PM [IPv4] Got connection from client localhost
  17/01/2015 04:19:08 PM   other clients:
  17/01/2015 04:19:09 PM WARNING: New width (1366) is not a multiple of 4.
  17/01/2015 04:19:09 PM Client Protocol Version 3.7
  17/01/2015 04:19:09 PM Advertising security type 18
  17/01/2015 04:19:09 PM Client localhost gone
  17/01/2015 04:19:09 PM Statistics:
  17/01/2015 04:19:09 PM   framebuffer updates 0, rectangles 0, bytes 0

  This was after I used the command, ssh -L 12345:localhost:5900
  username@ipaddress

  I get this output after I typed xvnc4viewer from my local terminal:

   CConn:   connected to host 172.29.24.129 port 5900
   CConnection: Server supports RFB protocol version 3.7
   CConnection: Using RFB protocol version 3.7
   CConnection: No matching security types
   main:No matching security types

  It seems the problem is that I cannot establish a successful
  connection unless I am using the same security type. I could not find
  a way to configure the vino-server to change or remove the security
  type. There was no manpage for the vino-server. A manpage for the
  vino-server is needed, updated setup howto for all variants of ubuntu
  and an advanced configuration file for the vino-server to modify how
  it runs and behaves.

  From QA member Istimsak Abdulbasir (sak)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vino 3.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Jan 17 17:01:18 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-09 (8 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 

[Desktop-packages] [Bug 1792877] Re: during adding SMB printer shared from WinXP, 'Browse' button works but 'Verify' does not

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1792877

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  during adding SMB printer shared from WinXP, 'Browse' button works but
  'Verify' does not

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  LUbuntu 18.04.1 with all updates, 32-bit x86 PC, top-level package 
'lubuntu-desktop' is installed,
  smbclient/smbspool are installed but smbd/nmbd are not (to save runtime RAM)

  MFU Canon MF3228 is attached to Windows XP and shared from it by SMB
  XP is not a domain member, only workgroup.
  For 'security' reasons, a user is created on WinXP with name 'print' and 
password 'print1' (because guest access apparently did not work)

  Now, I start 'system-config-printer' as root and try to add a printer.
  I select 'Windows printer via Samba', I enter XP IP and printer share name 
into 'smb://' field, then click 'Browse'. After a short pause, I get 
'Authorization required' dialog where I can enter login, domain/workgroup and 
password. And there, my Authorization is successful, I can select shared 
printer name and click 'OK'.

  But to complete printer setup, I have to enter these login and password into 
'Authentication' section, where I see 'Verify' button. Above it I also see 
'Username:' and 'Password:' fields, where password is entered above the 
username for unknown reason, and no field for workgroup or domain.
  And I was never able to Verify the same login and password fields however I 
tried. I entered login and password in the reverse, I prepended XP hostname and 
workgroup name before login, I used '\' and '/' separators - no luck

  Surely I know that Linux interoperation with Windows is not of top
  priority with Ubuntu developers, but I would be happy if such kind of
  a very popular household scenario were tested for Ubuntu LTS releases
  in some way. Thank you in advance for your responses.

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

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

[Desktop-packages] [Bug 1801443] Re: package wbritish 2018.04.16-1 failed to install/upgrade: installed wbritish package post-removal script subprocess returned error exit status 2

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  package wbritish 2018.04.16-1 failed to install/upgrade: installed
  wbritish package post-removal script subprocess returned error exit
  status 2

Status in scowl package in Ubuntu:
  Incomplete

Bug description:
  I can't provide much - I was doing household chores & was away.
  Attached is $ `apt full-upgrade` output in case it's the cause of the
  'crash'; it was running when I left, and I was away and didn't see
  crash

  machine is dx6120 in my QA-testing - dx6120mt(pentium 4 dual-core,
  3gb, winfast clone of nvidia 7600gt), install was a 18.10 QA-test
  (maybe 4-6 weeks xubuntu I think, i've added lubuntu-desktop also to
  it..) - earlier today I changed xfce theme to "Pills" (really old but
  I like it)

  repo's used are my isp's mirror & canonical partner, & included -proposed
  # 19.04
  deb http://ftp.iinet.net.au/pub/ubuntu disco  main universe 
restricted multiverse
  deb http://ftp.iinet.net.au/pub/ubuntu disco-updates  main universe 
restricted multiverse
  deb http://ftp.iinet.net.au/pub/ubuntu disco-security main universe 
restricted multiverse
  deb http://ftp.iinet.net.au/pub/ubuntu disco-proposed main universe 
restricted multiverse

  deb http://archive.canonical.com/ubuntu disco  partner

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: wbritish 2018.04.16-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic i686
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: i386
  Date: Sat Nov  3 12:25:30 2018
  ErrorMessage: installed wbritish package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2018-10-15 (18 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181013.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.1, python3-minimal, 3.7.1-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: scowl
  Title: package wbritish 2018.04.16-1 failed to install/upgrade: installed 
wbritish package post-removal script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1801449] Re: package hunspell-en-us 1:2018.04.16-1 failed to install/upgrade: installed hunspell-en-us package post-removal script subprocess returned error exit status 2

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  package hunspell-en-us 1:2018.04.16-1 failed to install/upgrade:
  installed hunspell-en-us package post-removal script subprocess
  returned error exit status 2

Status in scowl package in Ubuntu:
  Incomplete

Bug description:
  Maybe refer to
  https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/1801443
  &
  https://bugs.launchpad.net/ubuntu/+source/aspell-en/+bug/1801445

  I was away (household chores) whilst an full-upgrade was being run, so
  didn't see till after.

  I'm using -proposed (see other url for my sources; my mirror is two
  hours behind)

  Box was a 18.10 QA-test install maybe 4-6 weeks ago, xubuntu (I think)
  but with lubuntu-desktop added, bumped to 19.04. It's x86 (i686 class)
  only

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: hunspell-en-us 1:2018.04.16-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic i686
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: i386
  Date: Sat Nov  3 12:25:45 2018
  Dependencies:
   
  ErrorMessage: installed hunspell-en-us package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2018-10-15 (18 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181013.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.1, python3-minimal, 3.7.1-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: scowl
  Title: package hunspell-en-us 1:2018.04.16-1 failed to install/upgrade: 
installed hunspell-en-us package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1455219] Re: Cannot connect to PPPoE using NetworkManager: Could not find pppoe binary.

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Cannot connect to PPPoE using NetworkManager: Could not find pppoe
  binary.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  TL;DR: NetworkManager requires "pppoe" package, which was not
  installed by default in Lubuntu 15.04.

  
  I tried using Network Manager (nm-applet) to configure a PPPoE connection. I 
can create the connection, but trying to connect to it fails.

  The erro message that shows up in a dialog is not helpful at all:

  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/23' failed in libnm-
  glib.

  What is helpful is a message buried in /var/log/syslog:

  
  NetworkManager[713]:  (eth0): PPPoE failed to start: Could not find 
pppoe binary.

  
  Workaround: apt-get install pppoe.

  Desirable solution: pppoe package being a dependency of another
  package (lubuntu-desktop seems like a good one).

  
  Using Lubuntu 15.04 (upgraded from previous versions). This is the first time 
configuring a DSL/PPPoE connection in this system.

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

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

[Desktop-packages] [Bug 1881129] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces
  post-removal script geïnstalleerd gaf een foutwaarde 1 terug

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  u

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  AptOrdering:
   lubuntu-desktop: Purge
   lubuntu-default-session: Purge
   lubuntu-core: Purge
   lubuntu-default-settings: Purge
   lightdm: Purge
  Architecture: i386
  Date: Thu May 28 13:54:09 2020
  DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal 
script geïnstalleerd gaf een foutwaarde 1 terug
  ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 
1 terug
  InstallationDate: Installed on 2014-09-27 (2069 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=marleen
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet
   
   ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet
   
   ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.24
  SourcePackage: lightdm
  Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces 
post-removal script geïnstalleerd gaf een foutwaarde 1 terug
  UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago)

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

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

[Desktop-packages] [Bug 1320483] Re: Using CTRL+SHIFT+(left/right cursor) starts an endless loop of taking screenshots

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  Using CTRL+SHIFT+(left/right cursor) starts an endless loop of taking
  screenshots

Status in gnome-screenshot package in Ubuntu:
  Incomplete

Bug description:
  I'm not 100% sure gnome-screenshot is the culprit here, since this
  problem exists both in Ubuntu 14.04 and in Lubuntu 14.04 with their
  respective default apps.

  The problem: Whenever I select text word by word using CTRL+SHIFT +
  the cursor keys, for example right in this bug report, some weird
  chain of events is triggered which starts an endless loop of the
  screenshot utility du jour (depending on the desktop that is running)
  taking screenshots and filling up my $HOME directory.

  In Ubuntu 14.04, this has the effect of the mouse cursor becoming a
  crosshair and the user being able to select a region. In Lubuntu 14.04
  this only takes a screenshot and puts it into $HOME. In both cases,
  there are so many screenshot processe spawned that the machine becomes
  unresponsive and the session has to be killed (in my last case, 607
  within ten seconds).

  Where are these processes spawned and why? The machine was installed
  with Ubuntu 14.04 default and then `apt install lubuntu-desktop` was
  used to change the desktop, both into clean user environments. I do
  not have this problem at all on another Ubuntu 14.04 machine and never
  had it in 12.04.

  Thanks for any help!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screenshot 3.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat May 17 14:40:48 2014
  InstallationDate: Installed on 2014-05-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896367] Re: package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Launchpad Bug Tracker]

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

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

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

Title:
  package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  error al actualizar

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software 3.36.1-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  AptOrdering:
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Sep 12 12:42:50 2020
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2020-02-17 (215 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.1-0ubuntu0.20.04.0
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gnome-software
  Title: package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to focal on 2020-05-10 (132 days ago)

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

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

[Desktop-packages] [Bug 1905186] GsettingsChanges.txt

[sepukkuhero]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1905186/+attachment/5437115/+files/GsettingsChanges.txt

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] ShellJournal.txt

[sepukkuhero]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1905186/+attachment/5437118/+files/ShellJournal.txt

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

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

[sepukkuhero]

apport information

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

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[sepukkuhero]

All of the above were previously uninstalled. There were some left
unmentioned and I just removed them all. The problem continues to happen
even after the session ends. In addition, this problem occurs with both
my integrated graphics card and the GPU.

I executed your command and sent a full report.

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

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

[sepukkuhero]

apport information

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

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop.txt

[sepukkuhero]

apport information

** Attachment added: 
"modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop.txt"
   
https://bugs.launchpad.net/bugs/1905186/+attachment/5437119/+files/modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop.txt

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[sepukkuhero]

apport information

** Tags added: apport-collected

** Description changed:

  Ubuntu 20.04.1 LTS
  
  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are duly
  updated to the present date.
  
  I hoped that when entering full screen it would be possible to bring the
  dock and the top bar when placing the mouse over the respective corners.
  And in fact it is partially possible.
  
  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct timing
  to open the programs on the dock, for example. It is possible to click,
  but it is as if they were triggered several times, as if I were placing
  and removing the mouse from the corner very quickly.
  
  I enter the program. Everything is OK. The problem arises when I use the
  fullscreen. Sometimes the docks and the top bar work perfectly for a
  while, and then they start flashing.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-07-24 (121 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
+ Tags:  focal
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
+ _MarkForUpload: True
+ mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 

[Desktop-packages] [Bug 1905228] [NEW] DIsplay Rotates to Portrait Mode when Certain Apps Open

[Patrick Garraud]

Public bug reported:

When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2 in
1), the screen will frequently incorrectly rotate whenever some apps
open. This has been observed with Settings, Videos, Steam, Lollypop and
Firefox. Issue still occurs when the screen rotation is locked.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 22:59:56 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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 wayland-session

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

Title:
  DIsplay Rotates to Portrait Mode when Certain Apps Open

Status in xorg package in Ubuntu:
  New

Bug description:
  When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2
  in 1), the screen will frequently incorrectly rotate whenever some
  apps open. This has been observed with Settings, Videos, Steam,
  Lollypop and Firefox. Issue still occurs when the screen rotation is
  locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 22:59:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

Thanks. That shows you still have two docks enabled simultaneously, but
also a lot of extensions that we don't support and may cause problems:

'places-m...@gnome-shell-extensions.gcampax.github.com', 'openweather-
extens...@jenslody.de', 'clipboard-indica...@tudmotu.com', 'user-theme
@gnome-shell-extensions.gcampax.github.com', 'caffe...@patapon.info',
'sound-output-device-choo...@kgshank.net', 'apps-menu@gnome-shell-
extensions.gcampax.github.com', 'transparent-top-...@zhanghai.me',
'status-area-horizontal-spac...@mathematical.coffee.gmail.com',
'coverflowalt...@palatis.blogspot.com', 'dash-to-d...@micxgx.gmail.com',
'hidetop...@mathieu.bidon.ca', 'ubuntu-d...@ubuntu.com'

Please uninstall/disable all but the last one, then log out and in
again. Does the problem still occur? If so then please next run:

  apport-collect 1905186

** Tags added: amdgpu

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

lspci.txt

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437088/+files/lspci.txt

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

Here we go. shellsettings.txt

** Attachment added: "shellsettings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437085/+files/shellsettings.txt

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

First of all, thanks for the effort in helping me.

The double docks problem was solved by me, but I don't know if there
were any side effects.

Do I paste the commands in the terminal? I did but nothing happened. It
only appears when I put the content before ">"

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1706199] Re: Left-handed mouse: tap produces right click

[PEtrushka]

Agreed, very unfriendly and existing since 2017. I can confirm it is still 
present in Ubuntu 20.04. 
Does anyone know what this is set to "Won't Fix"?

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

Title:
  Left-handed mouse: tap produces right click

Status in Xserver Xorg Input Synaptics:
  Won't Fix
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  First of all I’d like to say that documenting a bug doesn’t justify
  its existence.

  The issue I am reporting is documented in `man synaptics`:

  > If the device is switched to left-handed (an in-server mapping of
  physical buttons 1, 2, 3 to the logical buttons 3, 2, 1,
  respectively), both physical and TapButtons are affected. To
  counteract this, the TapButtons need to be set up in reverse order
  (TapButton1=3, TapButton2=1).

  Steps to reproduce:

  0) "Tap to click" is activated (by default), your computer has a touchpad
  1) Switch mouse and touchpad to the left-handed mode through Settings > Mouse 
and Touchpad
  2) Logout and login for the changes to take effect
  3) Tap the touchpad

  Expected result: a left click event is generated
  Actual result: right click event is generated, context menu is shown

  Steps to work around the problem (no sane person will consider this a real 
solution):
  1) Find in `man synaptics` the lines quoted above
  2) Find out the syntax of xinput to configure Tap Action (not in the `man 
xinput` since this particular case is not mentioned there, and not via 
xorg.conf which ceased to exist)
  3) Run this command via an entry in .config/autostart (since putting it in 
.profile and .xinputrc doesn’t have any effect)

  These configuration steps MUST NOT (RFC 2119) exist. Tapping the
  touchpad should continue to work normally even after switching the
  mouse to the left-handed mode.

  For the next poor soul trying to figure out the command to run: 
  1) Run `xinput` and find your touchpad there, remember its ID
  2) Run `xinput list-props  | grep "Tap Action"`, remember property ID
  3) Run `xinput set-prop --type=int --format=8   2 3 0 0 1 3 0` on 
login by adding it to "Startup applications"

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1706199/+subscriptions

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

Yes having double docks is known to cause bugs. But if you have disabled
the above extensions then you shouldn't have double docks at all.

To verify, if the bug is still occurring then please now run:

  gsettings list-recursively org.gnome.shell > shellsettings.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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1905186

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905169] Re: gnome-shell crashes with signal 5 in g_log_structured_array() when I click new notification window

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

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

Title:
  gnome-shell crashes with signal 5 in g_log_structured_array() when I
  click new notification window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  gnome-shell crashes when I click new notification window

  Including crash report as a screenshot as send button in that window does 
nothing for some reason
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-10-07 (1141 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905169] Re: gnome-shell crashes with signal 5 in g_log_structured_array() when I click new notification window

[Daniel van Vugt]

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

Comment #9 shows this:

[60331.554749] yurko-laptop gnome-shell[2466]: Error in freeze/thaw accounting
[60331.556071] yurko-laptop gnome-shell[2466]: GNOME Shell crashed with signal 5
[60331.556071] yurko-laptop gnome-shell[2466]: == Stack trace for context 
0x563976f93220 ==
[60331.556071] yurko-laptop gnome-shell[2466]: #0   56397b0fa018 i   
resource:///org/gnome/shell/ui/windowManager.js:1384 (1cb1499d03d0 @ 589)

** Summary changed:

- gnome-shell crashes when I click new notification window
+ gnome-shell crashes with signal 5 in g_log_structured_array() when I click 
new notification window

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

Title:
  gnome-shell crashes with signal 5 in g_log_structured_array() when I
  click new notification window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  gnome-shell crashes when I click new notification window

  Including crash report as a screenshot as send button in that window does 
nothing for some reason
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-10-07 (1141 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

Please also run:

  lspci -kv > lspci.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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1905186

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905199] Re: Computer crashing when exiting the lock screen after login, random admin authentication window stuck on the screen.

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1824874
   undismissable, unclickable authentication dialog left on screen (top-left 
corner) after policykit authentication [pushModal: invocation of begin_modal 
failed]

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

Title:
  Computer crashing when exiting the lock screen after login, random
  admin authentication window stuck on the screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move the mouse, without being able to interact. Everything is
  stuck and never comes back. I can only fix this problem by restarting
  the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 17:35:26 2020
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post 

[Desktop-packages] [Bug 1905084] Re: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard

[Daniel van Vugt]

I'm assuming you're using the equivalent feature of Super+P. Some models
of laptop have a dedicated key to do the same thing.

Looking at gnome-shell's switchMonitor.js it looks pretty simple but I
would recommend editing your ~/.config/monitors.xml and ensuring the
scaling settings you want are remembered there.

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

Title:
  Fractional scaling of external monitor and monitor positioning are
  lost when switching between single- and extended-display modes using
  the keyboard

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

Bug description:
  Steps to reproduce:

  0. Attach an external monitor to the laptop

  1. Set the external monitor as the primary monitor

  2. Change the fractional scaling of the external monitor to 150% and
  change the positioning of the built-in monitor to the desired
  positioning

  3. Switch to the single-display mode using the keyboard

  → 4. The fractional scaling of the external monitor changes to 100%
  (this could be the intended behaviour and not a bug)

  5. Change again the fractional scaling of the external monitor to 150%

  6. Switch to the extended-display mode using the keyboard

  → 7. The fractional scaling of the external monitor changes to 100%
  (this is a bug, it should persist)

  → 8. The positioning of the built-in monitor changes to the default
  (this is a bug, it should persist)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.6-1ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 20 20:04:26 2020
  InstallationDate: Installed on 2020-04-26 (208 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
  SourcePackage: mutter
  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/1905084/+subscriptions

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

Previously I had a problem with double docks at the same time (ubuntu
dock and dash to dock)... I solved this problem, but maybe it is related
to this new problem?

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905084] Re: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard

[Daniel van Vugt]

"Single" and "extended" display modes sound like different
configurations. You need to set each up separately with your preferred
settings in gnome-control-center, and save the settings of each. If you
have done that, and especially if you have verified it's been saved in
~/.config/monitors.xml then this is a bug.

Does it only happen in Wayland sessions?

** Tags added: multimonitor

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

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

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

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

Title:
  Fractional scaling of external monitor and monitor positioning are
  lost when switching between single- and extended-display modes using
  the keyboard

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

Bug description:
  Steps to reproduce:

  0. Attach an external monitor to the laptop

  1. Set the external monitor as the primary monitor

  2. Change the fractional scaling of the external monitor to 150% and
  change the positioning of the built-in monitor to the desired
  positioning

  3. Switch to the single-display mode using the keyboard

  → 4. The fractional scaling of the external monitor changes to 100%
  (this could be the intended behaviour and not a bug)

  5. Change again the fractional scaling of the external monitor to 150%

  6. Switch to the extended-display mode using the keyboard

  → 7. The fractional scaling of the external monitor changes to 100%
  (this is a bug, it should persist)

  → 8. The positioning of the built-in monitor changes to the default
  (this is a bug, it should persist)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.6-1ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 20 20:04:26 2020
  InstallationDate: Installed on 2020-04-26 (208 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
  SourcePackage: mutter
  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/1905084/+subscriptions

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

I uninstalled all the extensions mentioned. I also disabled all of them
and left only the default Ubuntu Dock.

The problem continues to happen in full screen, despite being apparently
more stable.

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

-- 
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:
  Incomplete

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 1904939] Re: Monitor Settings Don't Get Applied in Wayland

[Daniel van Vugt]

Please uninstall or just disable your extensions via the Extensions app,
then log out and log in again and tell us if the problem still occurs.
If it does then please reproduce the problem again, and again run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


** Tags added: amdgpu hybrid

** Tags added: multimonitor

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

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

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

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

** Changed in: mutter (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/1904939

Title:
  Monitor Settings Don't Get Applied in Wayland

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

Bug description:
  When configuring a 1080p monitor and a 4k monitor in extended screen
  mode while using Wayland, when trying to change the screen positions
  or which screen is the primary screen in the Monitor Settings, the
  settings reset to default when Apply is clicked. Choosing to "Revert
  the Settings" during the 15-second timer causes it to apply the
  changed settings, but this resets whenever a pop-up message appears or
  when returning to the Monitor Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 16:47:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  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:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530 2-in-1
  dmi.product.sku: 08AC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1904924] Re: Xorg freeze

[Daniel van Vugt]

If you can move the mouse around then Xorg is definitely not frozen. It
sounds like only gnome-shell is frozen.

** Summary changed:

- Xorg freeze
+ Gnome Shell freeze

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

** Tags added: nvidia

** Summary changed:

- Gnome Shell freeze
+ [nvidia] Gnome Shell freeze

** Summary changed:

- [nvidia] Gnome Shell freeze
+ [nvidia] Gnome Shell freeze (page allocation failure in nvidia_modeset)

** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-455
(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/1904924

Title:
  [nvidia] Gnome Shell freeze (page allocation failure in
  nvidia_modeset)

Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Sounds like a fairly common problem according to [this
  page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
  freezes, and while I'm still able to move the mouse around, I can't
  successfully click or type at any windows. It takes about 30 seconds
  for gnome-shell to restart, and then the clock starts running (and the
  system monitor starts updating) again.

  This problem has been bugging me for a few months now, but I'm not
  sure when it started. It tends to happen in clumps; sometimes it will
  go several days without happening, but once it starts it often happens
  twice pretty quickly, and often a few times across a day. I haven't
  been able to isolate what causes it, but more often than not it has
  something to do with clicking on a window or tab in Chrome. (It
  definitely also happens in other applications, though.)

  Every time it happens, dmesg contains a stack dump for gnome-shell
  ("page allocation failure"). I can provide gists of these dumps if
  that's helpful (and not already included in the apport data). So I'm
  not sure if this is actually an xorg thing or a gnome-shell thing.

  % lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  % dpkg -l xorg* gnome-shell* | grep '^ii'
  ii  gnome-shell  3.38.1-1ubuntu1.1
  amd64graphical shell for the GNOME desktop
  ii  gnome-shell-common   3.38.1-1ubuntu1.1
  all  common files for the GNOME graphical shell
  ii  gnome-shell-extension-appindicator   34-1 
  all  AppIndicator/KStatusNotifierItem support for GNOME Shell
  ii  gnome-shell-extension-desktop-icons  20.04.0+git20200908-1
  all  desktop icon support for GNOME Shell
  ii  gnome-shell-extension-prefs  3.38.1-1ubuntu1.1
  amd64tool to enable / disable GNOME Shell extensions
  ii  gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1 
  all  Display system information in GNOME Shell status bar
  ii  gnome-shell-extension-system76-power 
2.0.0~1602857239~20.10~914b531~dev all  Gnome-shell extension for 
System76 Power Management
  ii  gnome-shell-extension-ubuntu-dock68ubuntu20.10.1  
  all  Ubuntu Dock for GNOME Shell
  ii  gnome-shell-extensions   3.38.1-1 
  all  Extensions to extend functionality of GNOME Shell
  ii  xorg 1:7.7+19ubuntu15 
  amd64X.Org X Window System
  ii  xorg-docs-core   1:1.7.1-1.1  
  all  Core documentation for the X.org X Window System
  ii  xorg-sgml-doctools   1:1.11-1 
  all  Common tools for building X.Org SGML documentation

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 
5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic 5.8.17
  Uname: Linux 5.8.0-7630-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  

[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug

[Daniel van Vugt]

** Tags added: groovy

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

Title:
  switch-on-connect mistakes startup for USB hotplug

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

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  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.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx: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/pulseaudio/+bug/1877194/+subscriptions

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

[Desktop-packages] [Bug 1904903] Re: Pulseaudio always defaults to any external audio device connected when booting up

[Daniel van Vugt]

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

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


** Tags added: groovy

** This bug has been marked a duplicate of bug 1877194
   switch-on-connect mistakes startup for USB hotplug

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

Title:
  Pulseaudio always defaults to any external audio device connected when
  booting up

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I am booting the computer up, it never sets the default output to
  the one I was using previously, which should be the norm. This is also
  the same for audio inputs. It works perfectly fine when connecting any
  new sound sources to the PC, which then pulseaudio sets the
  output/input to. But regarding it's state when booting up, it should
  stay on the last used audio device.

  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

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

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

[Desktop-packages] [Bug 1904777] Re: Xorg randomly crashes under xrdp

[Daniel van Vugt]

The "Assertion" prefix might be localized to PL so try searching
something like:

  journalctl -b-1 | grep dixGetPrivateAddr

I am confident it will end up being bug 1861609 but it doesn't hurt to
check.

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

Title:
  Xorg randomly crashes under xrdp

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm using xrdp to log into a remote machine. Since upgrading it to
  20.04, my sessions started failing randomly. They would either not
  start at all, or get interrupted hours later.

  Here's a backtrace I found in a .xorgxrdp.log

  [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off
  [ 92697.915] rdpInDeferredRepeatCallback:
  [ 92697.916] rdpkeybChangeKeyboardControl:
  [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off
  [ 92712.569] (EE) 
  [ 92712.586] (EE) Backtrace:
  [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c]
  [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7ffa5424f41f]
  [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7ffa5408c18b]
  [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7ffa5406b859]
  [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a]
  [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) 
[0x7ffa5407cf36]
  [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) 
[0x5559b0103095]
  [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) 
[0x5559b01046e2]
  [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4]
  [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x5559affd6f34]
  [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4]
  [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7ffa5406d0b3]
  [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e]
  [ 92712.621] (EE) 
  [ 92712.621] (EE) 
  Fatal server error:
  [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting
  [ 92712.621] (EE) 
  [ 92712.623] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for 
additional information.
  [ 92712.623] (EE) 
  [ 92712.627] rdpmouseControl: what 4
  [ 92712.627] rdpkeybControl: what 4
  [ 92712.629] rdpLeaveVT:
  [ 92712.634] (EE) Server terminated with error (1). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Nov 18 20:07:37 2020
  DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609]
  MachineType: HP ProLiant MicroServer
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic 
root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 07/29/2011
  dmi.bios.vendor: HP
  dmi.bios.version: O41
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr:
  dmi.product.name: ProLiant MicroServer
  dmi.product.sku: 664447-425
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: 

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

[Daniel van Vugt]

Please report the issue to the developers at:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues

and then tell us the new issue ID.

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

-- 
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:
  Incomplete

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 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04

[Daniel van Vugt]

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

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

** Tags added: focal

** Changed in: pulseaudio (Ubuntu)
   Status: New => Fix Committed

** Tags added: fixed-in-13.99.2 fixed-upstream

** Also affects: pulseaudio (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Committed

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

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

** Tags added: rls-ff-incoming

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

Title:
  pavucontrol duplex profiles disappeared for SB Audigy after upgrading
  to Ubuntu 20.04

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

Bug description:
  I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile
  is gone. The duplex profile was there and was working properly before.

  The following seems to be related:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Hui Wang]

The Intel bluetooth firmware will be upgraded with this bug #1905214

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

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

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1904474] Re: Black/purple screen after booting Ubuntu

[Daniel van Vugt]

Thanks. That log does seem to show a problem. Maybe this is the issue:

Nov 19 13:47:24 alexander-ThinkPad-T460 gnome-session[1010]: 
gnome-session-binary[1010]: WARNING: Lost name on bus: org.gnome.SessionManager
Nov 19 13:47:24 alexander-ThinkPad-T460 gnome-session[1010]: 
gnome-session-binary[1010]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
Nov 19 13:47:24 alexander-ThinkPad-T460 gnome-session-binary[1010]: WARNING: 
Lost name on bus: org.gnome.SessionManager
Nov 19 13:47:24 alexander-ThinkPad-T460 systemd-logind[791]: System is powering 
down.
Nov 19 13:47:24 alexander-ThinkPad-T460 gnome-session-binary[1010]: CRITICAL: 
We failed, but the fail whale is dead. Sorry

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

Title:
  Black/purple screen after booting Ubuntu

Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my
  ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark
  screen, Ubuntu is not booting (also after 15mins of waiting ...).

  I first thought my issue would be a *Black/purple screen after you
  boot Ubuntu for the first time* like over here:
  https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-
  screen-what-options-do-i-have-to-fix-it

  So I added ```ǹomodeset``` in the script executed before booting
  Ubuntu. Interestingly I was able to boot and then made this change
  persistent by updating the bootloader. I tried some more times to boot
  and suddenly it stopped working properly (with same blackscreen as
  before). I also took a look to the bootscript, ```ǹomodeset``` was
  present there.

  Then I played around with some other obscure suggestions like adding
  ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace
  ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but
  nothing gave me a soultion which did not get stuck with black screen
  of death after some reboots.

  I am a little bit clueless at the moment, so I have appended the uncompressed 
logs in ```/var/log```, captured like in 
https://wiki.ubuntu.com/DebuggingKernelBoot .
  The files appended are from a boot that got stuck, I have killed my laptop 
after 10mins of nothing happening.

  Btw. I have a dual boot with Windows 10, but I do not know if this is
  relevant for this issue.

  Best
  Alexander
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
  Tags:  bionic
  Uname: Linux 5.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1904474] Re: Black/purple screen after booting Ubuntu

[Daniel van Vugt]

Please run this command:

  lspci -kv > lspci.txt

and then attach the resulting text file here.


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

** Changed in: gnome-session (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/1904474

Title:
  Black/purple screen after booting Ubuntu

Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my
  ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark
  screen, Ubuntu is not booting (also after 15mins of waiting ...).

  I first thought my issue would be a *Black/purple screen after you
  boot Ubuntu for the first time* like over here:
  https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-
  screen-what-options-do-i-have-to-fix-it

  So I added ```ǹomodeset``` in the script executed before booting
  Ubuntu. Interestingly I was able to boot and then made this change
  persistent by updating the bootloader. I tried some more times to boot
  and suddenly it stopped working properly (with same blackscreen as
  before). I also took a look to the bootscript, ```ǹomodeset``` was
  present there.

  Then I played around with some other obscure suggestions like adding
  ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace
  ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but
  nothing gave me a soultion which did not get stuck with black screen
  of death after some reboots.

  I am a little bit clueless at the moment, so I have appended the uncompressed 
logs in ```/var/log```, captured like in 
https://wiki.ubuntu.com/DebuggingKernelBoot .
  The files appended are from a boot that got stuck, I have killed my laptop 
after 10mins of nothing happening.

  Btw. I have a dual boot with Windows 10, but I do not know if this is
  relevant for this issue.

  Best
  Alexander
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
  Tags:  bionic
  Uname: Linux 5.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1903542] Re: Ubuntu 20.10 2-in-1 regression (auto-rotate and on-screen keyboard disabled)

[Daniel van Vugt]

** Tags added: osk

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

Title:
  Ubuntu 20.10  2-in-1 regression (auto-rotate and on-screen keyboard
  disabled)

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

Bug description:
  I have a 2-in-1 laptop (HP Spectre Folio) 
  With 20.04 my screen autorotated and I got a on-screen-keyboard. No it 
doesn't. So my laptop is no longer a 2-in-1 with Ubuntu. That's a serious 
regression.

  As far as I can tell this is a Gnome bug: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3255
  with a solution, but it needs to be resolved in Ubuntu 20.10.

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

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

[Desktop-packages] [Bug 1901901] Re: Lenovo Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
   Status: New => Fix Released

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

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

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

Title:
  Lenovo Yoga Slim 7: Sound output device is not detected after upgrade
  from Ubuntu 20.04 to 20.10

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04.
  But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card 
is not detected, "System => Sound => Output Device" shows only "Dummy Output".
  I'm able to reproduce it even with live Ubuntu 20.10 from USB key.

  I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 
and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x
  So it doesn't seem to be depend on used kernel.

  
---

  $ systemctl --user status pulseaudio.service 
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 3002 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1 
(alsa_card.pci-_03_00.6) more often than 5 time>

  
---

  When pulseaudio starts in verbose mode:

  $ pulseaudio -v
  ...
  I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16)
  I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or 
resource busy
  D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, 
probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0
  E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
  E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: 
"device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes avoid_resampling=no 
card_properties="module-udev-detect.discovered=1""): initialization failed.
  I: [pulseaudio] module-udev-detect.c: Card 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1 
(alsa_card.pci-_03_00.6) failed to load module.

  
---

  $ lspci -nnk | grep -A2 Audio
  03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:380d]
Kernel driver in use: snd_hda_intel
  --
  03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:380d]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:380d]
Kernel driver in use: snd_hda_intel
Kernel modules: 

[Desktop-packages] [Bug 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1905080

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI
  output disabled and doesn't turn on when I turn on the TV

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Before the upgrade the HDMI 4 digital stereo output was chosen
  automatically for my nvidia GF card and was usable by the players
  immediately after turning the TV on. After the upgrade I have to
  switch the profile from Disabled to HDMI4 each time I turn the TV on.
  It doesn't get stored properly.

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

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

Thanks for the bug report. Because so many bugs are caused by extensions
the first thing we ask is for you to uninstall all of these:

'places-m...@gnome-shell-extensions.gcampax.github.com', 'openweather-
extens...@jenslody.de', 'clipboard-indica...@tudmotu.com', 'ubuntu-
appindicat...@ubuntu.com', 'user-theme@gnome-shell-
extensions.gcampax.github.com', 'caffe...@patapon.info', 'sound-output-
device-choo...@kgshank.net', 'apps-menu@gnome-shell-
extensions.gcampax.github.com', 'transparent-top-...@zhanghai.me',
'status-area-horizontal-spac...@mathematical.coffee.gmail.com',
'coverflowalt...@palatis.blogspot.com', 'dash-to-d...@micxgx.gmail.com',
'hidetop...@mathieu.bidon.ca'

Then tell us if if the problem still occurs. If it doesn't then next
please enable just Ubuntu Dock and tell us if the problem happens with
only that extension.


** Changed in: gnome-shell (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/1905186

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1898943] Re: dock and top bar blinking at fullscreen

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1905186
   dock and top bar flashing non-stop at fullscreen

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

Title:
  dock and top bar blinking at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The dock is flashing (opening and closing) when I have smart hide mode
  enabled (Dash to Dock extension). The same phenomenon occurs when I
  use the "Hide Top Bar" extension with hidden mode ...

  The blinks occur with a certain pattern, which I believe is based on
  the values of the extensions (pressure setting etc.) ... Anyway, it is
  a problem that affects two different extensions at the same time.
  Usually the problem starts when I use Firefox's fullscreen. Sometimes
  the dock and the top bar work perfectly, but after a while they start
  to blink. You can click on the icons, but you need to reach the
  correct timing. If it blinks too fast, it becomes very difficult to
  use the dock in full screen.

  The problem happens only in some windows (which were used in
  fullscreen mode) and do not reach other windows. It is resolved with
  the closing and reopening of the program, but soon they reappear.

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

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

[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled

[Daniel van Vugt]

Remember this bug is closed. All new comments should go in open bugs
like bug 1904237.

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

Title:
  [Focal regression] On-screen keyboard (OSK) does not appear on touch
  under Xorg on convertible laptops in tablet mode when physical
  keyboard disabled

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

Bug description:
  [ Impact ]

  OSK doesn't appear in X11 when disabling physical keyboard

  [ Test case ]

  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this
 disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as
 gnome-shell > Activities > Search:
 - The OSK appear
  4. Swipe from bottom of screen in order to summon OSK on demand:
 - occurred on Ubuntu 18.04 through 19.10)

  [ Regression potential ]

  The OSK shows when not needed in setup with no touch-screen or with
  touch screen but when not required.

  ---

  Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
  Related upstream bugs:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1242

  [Note: Please someone add a bug watch for
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
  for the other and then Launchpad somehow did not let me again]

  Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS 
9575 2-in-1:
  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as  
gnome-shell > Activities > Search
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text
  4. Swipe from bottom of screen in order to summon OSK on demand:
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text 
fields of foreign toolkits that are expected not to trigger the OSK 
automatically)

  Note that the EXPECTED RESULT still happens under Wayland in 20.04.
  Only the Xorg session is affected by the issue described in this bug.

  Also note that Accessibility was NOT necessary to be enabled in 19.10
  and before. (When enabling it in 20.04, the OSK does appear under
  Xorg, but this should not be necessary)

  (On Wayland there is a different changed behavior with the OSK not appearing 
in the device's laptop mode, i.e. with the physical keyboard enabled. This 
seems intended and a different issue as per 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )

  This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
  I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this 
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
  It probably also worked with 19.04 and possibly 18.10, but I ran mostly 
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)

  Other hardware reported to reproduce the issue (and in part are said
  to have been working in 19.10 and before, down to 18.04) include:

  In bug #1866556;
  Lenovo ThinkPad L390 Yoga
  Asus ZenBook UX370UAF
  Acer Switch 11 V sw5-173 (said to have worked with 18.04)
  (Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the 
tablet mode seems unsupported on these devices and so the issue might be 
different)

  In upstream bug:
  Dell Inspiron 15 700 2-in-1

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 19:59:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (619 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)

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

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Mathew Hodson]

** No longer affects: xorg-server-hwe-18.04 (Ubuntu Groovy)

** No longer affects: xorg-server-hwe-18.04 (Ubuntu Focal)

** No longer affects: xorg-server-hwe-18.04 (Ubuntu)

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Groovy:
  Fix Released

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[Mathew Hodson]

** Changed in: xorg-server (Ubuntu Bionic)
   Status: Invalid => Won't Fix

** No longer affects: xorg-server-hwe-18.04 (Ubuntu Focal)

** No longer affects: xorg-server-hwe-18.04 (Ubuntu)

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

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

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

Bug description:
  [Impact]

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

  [Test case]

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

  [Regression potential]

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

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

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

  --

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

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

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

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

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

  if (!mode)
  return FALSE;

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

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

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

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

[Desktop-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

[Mathew Hodson]

** No longer affects: bluez (Ubuntu)

** No longer affects: bluez (Ubuntu Focal)

** No longer affects: bluez (Ubuntu Hirsute)

** No longer affects: bluez (Ubuntu Groovy)

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

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

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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

[Desktop-packages] [Bug 1903936] Re: Update to 1.58

[Mathew Hodson]

** Tags removed: verification-dine-groovy
** Tags added: upgrade-software-version verification-done-groovy

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

Title:
  Update to 1.58

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+subscriptions

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

[Desktop-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Mathew Hodson]

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

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

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

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

[Desktop-packages] [Bug 1609342] Re: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command

[Egmont Koblinger]

For setting: vte-2.91.sh is intended to do that... the ".sh" extension
was missing, sorry.

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

Title:
  Gnome-terminal sets directory to HOME for ctrl-shift-n and custom
  shell command

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 14.04 I could Ctrl-Shift-N in my gnome-terminal and
  another terminal window came up with the same working directory. When
  I upgraded to 16.04.1, the new terminal window now always uses $HOME
  as working directory. I want the 14.04 behavior.

  This has nothing to do with sourcing /etc/profile.d/vte.sh. Fish does
  this correctly as I can observe directory changes in the title bar. If
  I uncheck the custom command box in my gnome-terminal profile, the new
  terminal window correctly uses the current directory. However, it uses
  my system default shell: bash.

  For some reason gnome-terminal does not set the working directory if I
  use a custom command.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 12:32:22 2016
  InstallationDate: Installed on 2013-02-13 (1266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago)

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

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

[Desktop-packages] [Bug 1609342] Re: Gnome-terminal sets directory to HOME for ctrl-shift-n and custom shell command

[Egmont Koblinger]

gnome-terminal 3.36, which is included in Ubuntu 20.04, added a config
option Preferences ->  -> Command -> Preserve working
directory.

Older versions preserved the directory only when launching a shell, not
when launching a custom command. This behavior was frowned upon by some
folks, understandably.

The change is at https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/79b2291 , the two bugtracker entries are linked from
the commit message.

Now, in order for this to work, two more things have to happen:
Whichever application (presumably your shell) is running in the source
window has to set the desired value, and whichever application is
starting up in the new window has to respect it (not intentionally
override it).

For setting: vte-2.91 is intended to do that, see its __vte_osc7()
method. Now there's a chance that some fragment in your shell profile
overrides it. To debug I recommend to manually issue the given escape
sequence and then not give back control to the shell, not to give it a
chance to override from PS1 or PROMPT_COMMAND or so:

  printf "\e]7;file:/etc\e\\" ; sleep 1000

A newly opened tab should be in /etc now. If this fixes the problem then
try it without the sleep. If that still fixes then your shell just
doesn't emit it. If removing the sleep breaks it again then there's
something in your prompt overriding the value.

To debug the other side: Set up a custom command of "sleep 2000", open a
new window, from another terminal locate the pid of this sleep, and
check its working directory at /proc//cwd. If this is set
correctly, yet it doesn't work your shell or custom command, then it's
that command intentionally switching to some other directory.

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

Title:
  Gnome-terminal sets directory to HOME for ctrl-shift-n and custom
  shell command

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 14.04 I could Ctrl-Shift-N in my gnome-terminal and
  another terminal window came up with the same working directory. When
  I upgraded to 16.04.1, the new terminal window now always uses $HOME
  as working directory. I want the 14.04 behavior.

  This has nothing to do with sourcing /etc/profile.d/vte.sh. Fish does
  this correctly as I can observe directory changes in the title bar. If
  I uncheck the custom command box in my gnome-terminal profile, the new
  terminal window correctly uses the current directory. However, it uses
  my system default shell: bash.

  For some reason gnome-terminal does not set the working directory if I
  use a custom command.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 12:32:22 2016
  InstallationDate: Installed on 2013-02-13 (1266 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago)

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

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

[Desktop-packages] [Bug 1905200] Re: Ubuntu-dock in Wayland slow

[Jan Morten Rausch]

Please mark this bug as duplicate of

Bug #1874578

Saw the bug report to late.

Issue immediately vanishes after hiding mounted devices in the dock
with:

gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false

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

Title:
  Ubuntu-dock in Wayland slow

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

Bug description:
  Only in Ubuntu's wayland session, on 20.04 and 20.10:

  App icons will appear with a massive delay (~10 seconds) after
  launching an app currently not in the favorites.

  Also moving pinned icons within the dock will only appear in the new
  location after a similar long time span. Otherwise the dock works
  without delays.

  I could see this behavior on two completely different machines. No
  problems in the default Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 21:46:23 2020
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled

[Jan Morten Rausch]

I can confirm this bug an completely vanilla 20.04 and 20.10 installs on
two completely different machines.

Long startup for icons to appear at boot, non favourite apps will appear
with delay and moving apps will also have a big delay to appear in the
new order.

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

Title:
  [wayland] dock has very long load time when show-mounts is enabled

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

Bug description:
  I just upgraded from Ubuntu 18.04 to 20.04.

  When I boot my system I have to wait at least 10 to 15 seconds for the
  application icons to load on dock. Meanwhile everything else seems to
  be working properly. I didn't experience this behavior in Ubuntu
  18.04.

  Also the dock doesn't trigger when I move my cursor to the left of the 
screen. (I have set the docker to Auto-Hide mode and it's position is on the 
left of my screen).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2016-08-03 (1359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags: focal third-party-packages wayland-session
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905199] Re: Admin authentication crashing after exiting the lock screen

[SepukkuHero]

** Summary changed:

- Xorg freeze
+ Admin authentication crashing after exiting the lock screen

** Summary changed:

- Admin authentication crashing after exiting the lock screen
+ Computer crashing when exiting the lock screen after login, random admin 
authentication window stuck on the screen.

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

Title:
  Computer crashing when exiting the lock screen after login, random
  admin authentication window stuck on the screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move the mouse, without being able to interact. Everything is
  stuck and never comes back. I can only fix this problem by restarting
  the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 17:35:26 2020
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1905200] [NEW] Ubuntu-dock in Wayland slow

[Jan Morten Rausch]

Public bug reported:

Only in Ubuntu's wayland session, on 20.04 and 20.10:

App icons will appear with a massive delay (~10 seconds) after launching
an app currently not in the favorites.

Also moving pinned icons within the dock will only appear in the new
location after a similar long time span. Otherwise the dock works
without delays.

I could see this behavior on two completely different machines. No
problems in the default Xorg session.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
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
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 21:46:23 2020
InstallationDate: Installed on 2020-11-22 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/fish
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell-extension-ubuntu-dock (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 gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905200

Title:
  Ubuntu-dock in Wayland slow

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

Bug description:
  Only in Ubuntu's wayland session, on 20.04 and 20.10:

  App icons will appear with a massive delay (~10 seconds) after
  launching an app currently not in the favorites.

  Also moving pinned icons within the dock will only appear in the new
  location after a similar long time span. Otherwise the dock works
  without delays.

  I could see this behavior on two completely different machines. No
  problems in the default Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 21:46:23 2020
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1905199] [NEW] Xorg freeze

[SepukkuHero]

Public bug reported:

Ubuntu 20.04.1 LTS

xorg:
  Instalado: 1:7.7+19ubuntu14
  Candidato: 1:7.7+19ubuntu14
  Tabela de versão:
 *** 1:7.7+19ubuntu14 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

Sometimes when I lock the screen or suspend the computer (I'm not sure
if both or just lock) and after I log in to my user again, a window
asking for the administrator password appears. This window is located in
the upper left corner of the screen and is not clickable. I try to enter
the password or cancel it but it is impossible, it is as if after the
screen lock that window would get stuck ...

Result: if I can use the computer normally, I cannot remove the window,
which occupies a significant part of the screen. Sometimes the situation
gets worse and everything starts to stall. In such cases, I can only
move the mouse, without being able to interact. Everything is stuck and
never comes back. I can only fix this problem by restarting the
computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 17:35:26 2020
DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
InstallationDate: Installed on 2020-07-24 (121 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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 freeze ubuntu

** Attachment added: "Captura de tela de 2020-11-22 17-45-42.png"
   
https://bugs.launchpad.net/bugs/1905199/+attachment/5437014/+files/Captura%20de%20tela%20de%202020-11-22%2017-45-42.png

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move the mouse, 

[Desktop-packages] [Bug 1898943] Re: dock and top bar blinking at fullscreen

[SepukkuHero]

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186

I created a new report with new details, bug video etc. I believe it is
more complete. The problem remains unresolved.

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

Title:
  dock and top bar blinking at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The dock is flashing (opening and closing) when I have smart hide mode
  enabled (Dash to Dock extension). The same phenomenon occurs when I
  use the "Hide Top Bar" extension with hidden mode ...

  The blinks occur with a certain pattern, which I believe is based on
  the values of the extensions (pressure setting etc.) ... Anyway, it is
  a problem that affects two different extensions at the same time.
  Usually the problem starts when I use Firefox's fullscreen. Sometimes
  the dock and the top bar work perfectly, but after a while they start
  to blink. You can click on the icons, but you need to reach the
  correct timing. If it blinks too fast, it becomes very difficult to
  use the dock in full screen.

  The problem happens only in some windows (which were used in
  fullscreen mode) and do not reach other windows. It is resolved with
  the closing and reopening of the program, but soon they reappear.

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

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

[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

[ALinuxUser]

@Luis

Thanks. I think you mean `--gtk-debug`, though, not 'gdk'. Also: if one
has the problem, must one *always* run the viewer in that way, and what
does running it in that way do?

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Debian:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails

[Kenneth Loafman]

Sorry, it took me a while to grok that you were using the boto3 backend.
The format for a boto3 URL is boto3+s3://bucket_name[/prefix].  It's in
the man page and usage screen.

Make that change and let me know how it went.

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

Title:
  boto3+s3 bucket fails

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  I have a duplicity job that runs on multiple hosts, and am now having 
failures on my 20.04 hosts.
  The syntax for the job (as I am currently testing to debug) is:
  duplicity --dry-run  list-current-files --name $name --s3-use-ia 
--archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 
--s3-use-multiprocessing --volsize 1024 --verbosity 8 
boto3+s3://s3.amazonaws.com/bucket.name

  Using the duplicity packages from focal/main
  duplicity=0.8.11.1612-1
  And I installed the boto packages from focal/universe
  python3-boto3=1.9.253-1
  python3-botocore=1.14.14+repack-1

  This runs into the error:
  Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir
  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
85, in __init__
  self.reset_connection()
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
96, in reset_connection
  self.s3.meta.client.head_bucket(Bucket=self.bucket_name)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 357, in _api_call
  return self._make_api_call(operation_name, kwargs)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 676, in _make_api_call
  raise error_class(parsed_response, operation_name)
   botocore.exceptions.ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I then tried the duplicity snap from the snap store, both the stable and edge 
builds, with the same issue:
  Main action: list-current
  

  duplicity 0.8.17
  Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  Main action: list-current
  

  duplicity 0.8.18.dev11
  Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I also tried to update the boto3/botocore packages by way of pip3:
  pip3 freeze | grep boto
  boto3==1.16.19
  botocore==1.19.19

  And lastly as a last ditch, I tried to pull the packages from the 
groovy/universe repo, bringing them to:
  python3-boto3  1.13.14-1
  python3-botocore   1.17.22+repack-1_all

  I have also tried in a 20.10 system as well to see if any changes
  there, but same results.

  Hoping for something I can look at to get this back working as it was
  in 18.04 since 14.04.

  For good measure, I verified in a bionic build that using 

[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

[Luis]

Hi, I was able to solve the problem using the debugging options of the
same gnome-font-viewer package. In my case, I think I started to have a
problem after installing the lxqt and xfce desktops, which I believe had
different font management daemons from gnome. After uninstalling all the
desktops and dependencies for some reason the problem did not disappear.
I finally found the solution by looking in the help file for gnome-font-
viewer, typing in the terminal:

$ gnome-font-viewer --gdk-debug =


I hope I helped, greetings!

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Debian:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1905170] Re: Impossible to create a full backup due to permission error on /home/lost+found folder

[Michael Terry]

(Any one of those should work by itself)

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

Title:
  Impossible to create a full backup due to permission error on
  /home/lost+found folder

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Error only happen since upgrade to 20.10. Everything worked on ubuntu
  20.04. Same error if I try to change location of the backup. Folder
  /home/lost+found/ is not in the configuration of deja-dup.

  Error message displayed:
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1538, in 
main
  do_backup(action)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1662, in 
do_backup
  full_backup(col_stats)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 559, in 
full_backup
  bytes_written = dummy_backup(tarblock_iter)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 224, in 
dummy_backup
  while next(tarblock_iter):
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 544, in 
__next__
  result = self.process(next(self.input_iter))  # pylint: 
disable=assignment-from-no-return
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 209, in 
get_delta_iter
  for new_path, sig_path in collated:
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 310, in 
collate2iters
  for relem1 in riter1:
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 97, in 
__next__
  return next(self.iter)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 181, in 
Iterate
  subpath, val = next(diryield_stack[-1])
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 148, in 
diryield
  s = self.Select(new_path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 210, in 
Select
  result = sf(path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 458, in 
exclude_sel_func
  elif path.append(filename).exists():
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 566, in append
  return self.__class__(self.base, self.index + (ext,))
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 539, in 
__init__
  self.setdata()
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 549, in 
setdata
  self.stat = os.lstat(self.name)
   PermissionError: [Errno 13] Permission denied: 
b'/home/lost+found/.deja-dup-ignore'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1905170/+subscriptions

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

[Desktop-packages] [Bug 1905170] Re: Impossible to create a full backup due to permission error on /home/lost+found folder

[Michael Terry]

Oh and I should have mentioned workarounds:
- give everyone execute permission on the offending folder
- install the snap version of duplicity
- install the snap (or flatpak) version of deja-dup

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

Title:
  Impossible to create a full backup due to permission error on
  /home/lost+found folder

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Error only happen since upgrade to 20.10. Everything worked on ubuntu
  20.04. Same error if I try to change location of the backup. Folder
  /home/lost+found/ is not in the configuration of deja-dup.

  Error message displayed:
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1538, in 
main
  do_backup(action)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1662, in 
do_backup
  full_backup(col_stats)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 559, in 
full_backup
  bytes_written = dummy_backup(tarblock_iter)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 224, in 
dummy_backup
  while next(tarblock_iter):
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 544, in 
__next__
  result = self.process(next(self.input_iter))  # pylint: 
disable=assignment-from-no-return
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 209, in 
get_delta_iter
  for new_path, sig_path in collated:
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 310, in 
collate2iters
  for relem1 in riter1:
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 97, in 
__next__
  return next(self.iter)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 181, in 
Iterate
  subpath, val = next(diryield_stack[-1])
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 148, in 
diryield
  s = self.Select(new_path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 210, in 
Select
  result = sf(path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 458, in 
exclude_sel_func
  elif path.append(filename).exists():
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 566, in append
  return self.__class__(self.base, self.index + (ext,))
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 539, in 
__init__
  self.setdata()
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 549, in 
setdata
  self.stat = os.lstat(self.name)
   PermissionError: [Errno 13] Permission denied: 
b'/home/lost+found/.deja-dup-ignore'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1905170/+subscriptions

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

[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

** Description changed:

  Ubuntu 20.04.1 LTS
  
  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are duly
  updated to the present date.
  
  I hoped that when entering full screen it would be possible to bring the
  dock and the top bar when placing the mouse over the respective corners.
  And in fact it is partially possible.
  
  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct timing
  to open the programs on the dock, for example. It is possible to click,
  but it is as if they were triggered several times, as if I were placing
  and removing the mouse from the corner very quickly.
+ 
+ I enter the program. Everything is OK. The problem arises when I use the
+ fullscreen. Sometimes the docks and the top bar work perfectly for a
+ while, and then they start flashing.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905184] Re: No video signal during Ubuntu splash screen and also during Logon procedure

[Agostinho Carvalho]

** Description changed:

  Hello.
  
  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).
  
  To workaround this error, I can either:
- Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in login screen and Ubuntu loads immediately.
- Problem: However, I don't want this because I'm in a multi-user scenario.
+ 
+ Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
+ Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.
+ 
  
  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.
+ 
+ 
+ Workaround 3) Although I don't have video signal during Boot Splash and Logon 
screen, I do have backlight continuously applied to the display.
+ If I wait 5 minutes or so in the logon screen the backlight will deactivate...
+ However, when I touch the keyboard or touchpad the computer will then show 
video signal and I will be able to see the logon screen perfectly.
+ 
  
  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC
  
  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC
  
  Feel free to request any extra information.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Nov 22 19:56:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS CMPC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02.00.STD
  dmi.board.asset.tag: Default string
  dmi.board.name: ik Educational Software
  dmi.board.vendor: ECS
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 30
  dmi.chassis.vendor: NULL
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: CMPC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  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

** Description changed:

  Hello.
  
  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).
  
  To workaround this error, I can either:
  
  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
  Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.
  
- 
  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and 

[Desktop-packages] [Bug 1905186] [NEW] dock and top bar flashing non-stop at fullscreen

[SepukkuHero]

Public bug reported:

Ubuntu 20.04.1 LTS

This problem affects all extensions that alter the dock and top bar.
Including the standard extension "Ubuntu dock". All extensions are duly
updated to the present date.

I hoped that when entering full screen it would be possible to bring the
dock and the top bar when placing the mouse over the respective corners.
And in fact it is partially possible.

However, both are flashing, making it impossible to use them in full
screen. They blink very fast and you need to click on the correct timing
to open the programs on the dock, for example. It is possible to click,
but it is as if they were triggered several times, as if I were placing
and removing the mouse from the corner very quickly.

I enter the program. Everything is OK. The problem arises when I use the
fullscreen. Sometimes the docks and the top bar work perfectly for a
while, and then they start flashing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 14:07:57 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-24 (120 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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


** Tags: amd64 apport-bug dock focal fullscreen gnome gnome-shell

** Attachment added: "Dock bar and top bar flashing at fullscreen"
   
https://bugs.launchpad.net/bugs/1905186/+attachment/5436953/+files/VID_20201122_142846362.mp4

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  This problem affects all extensions that alter the dock and top bar.
  Including the standard extension "Ubuntu dock". All extensions are
  duly updated to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1905185] [NEW] [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to detect card

[Romano]

Public bug reported:

good evening, I have a problem with internal microphone, sometimes it works and 
sometimes it doesn't, it happens randomly, just a restart
my pc should be Ubuntu certified

thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
 /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 18:32:04 2020
InstallationDate: Installed on 2020-11-20 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2020
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET56W(1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UJ0014IX
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UJ0014IX
dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO

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

Title:
  [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  good evening, I have a problem with internal microphone, sometimes it works 
and sometimes it doesn't, it happens randomly, just a restart
  my pc should be Ubuntu certified

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
   /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 18:32:04 2020
  InstallationDate: Installed on 2020-11-20 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET56W(1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UJ0014IX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UJ0014IX
  dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1905184] [NEW] No video signal during Ubuntu splash screen and also during Logon procedure

[Agostinho Carvalho]

Public bug reported:

Hello.

I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
I only have video in GRUB and after the logon operation takes place.
After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

To workaround this error, I can either:
Workaround 1) Enable automatic login. That way the system doesn't get stuck in 
login screen and Ubuntu loads immediately.
Problem: However, I don't want this because I'm in a multi-user scenario.

Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
When I do this I will always get video signal.
Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), and 
when I use this workaround, user session loads in Portrait mode (not Landscape) 
and there is no auto-rotation support.

Computer is this one:
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

Specs are here:
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

Feel free to request any extra information.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Nov 22 19:56:20 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 
00 [VGA controller])
InstallationDate: Installed on 2020-11-22 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ECS CMPC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02.00.STD
dmi.board.asset.tag: Default string
dmi.board.name: ik Educational Software
dmi.board.vendor: ECS
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 30
dmi.chassis.vendor: NULL
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: CMPC
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
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/1905184

Title:
  No video signal during Ubuntu splash screen and also during Logon
  procedure

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello.

  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

  To workaround this error, I can either:
  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in login screen and Ubuntu loads immediately.
  Problem: However, I don't want this because I'm in a multi-user scenario.

  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.

  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Feel free to request any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 

[Desktop-packages] [Bug 1905183] [NEW] [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a while

[Yuriy Padlyak]

Public bug reported:

sound dissapears after suspend, restored only after reboot

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yuriy  2155 F pulseaudio
 /dev/snd/pcmC0D0p:   yuriy  2155 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 19:13:54 2020
InstallationDate: Installed on 2017-10-07 (1142 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 лис 21 21:31:17 yurko-laptop systemd[1517]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
 лис 21 21:31:17 yurko-laptop dbus-daemon[1066]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.33' (uid=121 pid=1519 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
 лис 21 21:31:30 yurko-laptop systemd[1509]: pulseaudio.service: Succeeded.
 лис 21 21:31:41 yurko-laptop systemd[1509]: pulseaudio.socket: Succeeded.
Symptom_Type: Sound works for a while, then breaks
Title: [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2020
dmi.bios.release: 1.4
dmi.bios.vendor: TIMI
dmi.bios.version: XMACM500P0401
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: TM1905
dmi.board.vendor: TIMI
dmi.board.version: AX23XXAXE
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TIMI
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnTIMI:bvrXMACM500P0401:bd08/18/2020:br1.4:efr1.1:svnTIMI:pnMiLaptopPro15:pvr:rvnTIMI:rnTM1905:rvrAX23XXAXE:cvnTIMI:ct10:cvr:
dmi.product.family: Mi Laptop
dmi.product.name: Mi Laptop Pro 15
dmi.product.sku: TM1905-25887
dmi.sys.vendor: TIMI

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

Title:
  [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound dissapears after suspend, restored only after reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriy  2155 F pulseaudio
   /dev/snd/pcmC0D0p:   yuriy  2155 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 19:13:54 2020
  InstallationDate: Installed on 2017-10-07 (1142 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   лис 21 21:31:17 yurko-laptop systemd[1517]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
   лис 21 21:31:17 yurko-laptop dbus-daemon[1066]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.33' (uid=121 pid=1519 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   лис 21 21:31:30 yurko-laptop systemd[1509]: pulseaudio.service: Succeeded.
   лис 21 21:31:41 yurko-laptop systemd[1509]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: TIMI
  dmi.bios.version: XMACM500P0401
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: TM1905
  dmi.board.vendor: TIMI
  dmi.board.version: AX23XXAXE
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnTIMI:bvrXMACM500P0401:bd08/18/2020:br1.4:efr1.1:svnTIMI:pnMiLaptopPro15:pvr:rvnTIMI:rnTM1905:rvrAX23XXAXE:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: Mi Laptop Pro 15
  dmi.product.sku: TM1905-25887
  dmi.sys.vendor: TIMI

To 

[Desktop-packages] [Bug 1905175] Re: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  package upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1905170] Re: Impossible to create a full backup due to permission error on /home/lost+found folder

[Michael Terry]

This is a bug in a possible interaction between Deja Dup >= 42.1 and
Duplicity < 0.8.16.

Which means as of this writing it definitely affects 20.10, and may
affect 21.04 if Duplicity doesn't get bumped before release.

This was fixed in Duplicity by the following patch:
https://gitlab.com/duplicity/duplicity/-/commit/f6809e8a4e09b70138a0902434d8c88d3c4c8ccb

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

Title:
  Impossible to create a full backup due to permission error on
  /home/lost+found folder

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Error only happen since upgrade to 20.10. Everything worked on ubuntu
  20.04. Same error if I try to change location of the backup. Folder
  /home/lost+found/ is not in the configuration of deja-dup.

  Error message displayed:
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1538, in 
main
  do_backup(action)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1662, in 
do_backup
  full_backup(col_stats)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 559, in 
full_backup
  bytes_written = dummy_backup(tarblock_iter)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 224, in 
dummy_backup
  while next(tarblock_iter):
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 544, in 
__next__
  result = self.process(next(self.input_iter))  # pylint: 
disable=assignment-from-no-return
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 209, in 
get_delta_iter
  for new_path, sig_path in collated:
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 310, in 
collate2iters
  for relem1 in riter1:
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 97, in 
__next__
  return next(self.iter)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 181, in 
Iterate
  subpath, val = next(diryield_stack[-1])
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 148, in 
diryield
  s = self.Select(new_path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 210, in 
Select
  result = sf(path)
File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 458, in 
exclude_sel_func
  elif path.append(filename).exists():
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 566, in append
  return self.__class__(self.base, self.index + (ext,))
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 539, in 
__init__
  self.setdata()
File "/usr/lib/python3/dist-packages/duplicity/path.py", line 549, in 
setdata
  self.stat = os.lstat(self.name)
   PermissionError: [Errno 13] Permission denied: 
b'/home/lost+found/.deja-dup-ignore'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1905170/+subscriptions

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

[Desktop-packages] [Bug 1905054] Re: Firefox 83 Breaks WebGL

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox 83 Breaks WebGL

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working.
  Ubuntu 20.10 with Wayland.

  When I try to launch a webGL game:
  Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is 
not hardware-accelerated.

  Specifically Pixi says:
  Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback 
canvas2d support.

  Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build
  issue or Firefox, so I also filed upstream as well:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1678652

  I need this functionality for work, and pinning to version 82 will be
  problematic in the long-term.

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

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

[Desktop-packages] [Bug 1905175] Re: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  New

Bug description:
  package upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1905175] [NEW] package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Randy Fry]

Public bug reported:

package upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 10:07:04 2020
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2020-09-29 (53 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
 10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
 169.254.0.0/16 dev wlp8s0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: network-manager
Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
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  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  New

Bug description:
  package upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails

[Kenneth Loafman]

Thanks for the thorough analysis.


** Changed in: duplicity
   Importance: Undecided => Medium

** Changed in: duplicity
Milestone: None => 0.8.18

** Changed in: duplicity
   Status: Incomplete => In Progress

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

Title:
  boto3+s3 bucket fails

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  I have a duplicity job that runs on multiple hosts, and am now having 
failures on my 20.04 hosts.
  The syntax for the job (as I am currently testing to debug) is:
  duplicity --dry-run  list-current-files --name $name --s3-use-ia 
--archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 
--s3-use-multiprocessing --volsize 1024 --verbosity 8 
boto3+s3://s3.amazonaws.com/bucket.name

  Using the duplicity packages from focal/main
  duplicity=0.8.11.1612-1
  And I installed the boto packages from focal/universe
  python3-boto3=1.9.253-1
  python3-botocore=1.14.14+repack-1

  This runs into the error:
  Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir
  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
85, in __init__
  self.reset_connection()
File 
"/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 
96, in reset_connection
  self.s3.meta.client.head_bucket(Bucket=self.bucket_name)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 357, in _api_call
  return self._make_api_call(operation_name, kwargs)
File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", 
line 676, in _make_api_call
  raise error_class(parsed_response, operation_name)
   botocore.exceptions.ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I then tried the duplicity snap from the snap store, both the stable and edge 
builds, with the same issue:
  Main action: list-current
  

  duplicity 0.8.17
  Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  Main action: list-current
  

  duplicity 0.8.18.dev11
  Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors 
list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir 
$tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 
--verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name
  Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 
x86_64 x86_64
  /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct  8 2020, 12:12:24)
  [GCC 8.4.0]
  

  Attempt 1 failed. ClientError: An error occurred (403) when calling the 
HeadBucket operation: Forbidden

  I also tried to update the boto3/botocore packages by way of pip3:
  pip3 freeze | grep boto
  boto3==1.16.19
  botocore==1.19.19

  And lastly as a last ditch, I tried to pull the packages from the 
groovy/universe repo, bringing them to:
  python3-boto3  1.13.14-1
  python3-botocore   1.17.22+repack-1_all

  I have also tried in a 20.10 system as well to see if any changes
  there, but same results.

  Hoping for something I can look at to get this back working as it was
  in 18.04 since 14.04.

  For good measure, I verified in a bionic build that using the 

[Desktop-packages] [Bug 1905027] PulseList.txt

[Pedot]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436885/+files/PulseList.txt

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

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  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.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

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

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

[Desktop-packages] [Bug 1905027] CurrentDmesg.txt

[Pedot]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436882/+files/CurrentDmesg.txt

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

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  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.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

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

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

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

[Pedot]

apport information

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

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

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  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.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

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

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

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

[Pedot]

apport information

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

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

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  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.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

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

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

[Desktop-packages] [Bug 1905027] Re: Need to force alsa to reload after reboot to have sound

[Pedot]

apport information

** Tags added: apport-collected focal

** Description changed:

  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.
  
  I need to reload at each reboot alsa with:
  
  sudo alsa force-reload
  
  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996
  
  alsa seems to kill timidity (?)
  
  This solves it:
  systemctl disable timidity
  
  
  I didn't find an issue for this bug. Feel free to remove if needed.
  
  
  Thanks !
  
  
  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  thomas 1961 F pulseaudio
+  /dev/snd/controlC0:  thomas 1961 F pulseaudio
+  /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2017-12-29 (1058 days ago)
+ InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: alsa-driver (not installed)
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ Tags:  focal
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/27/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F2
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: H170M-HD3 DDR3-CF
+ 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: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: To be filled by O.E.M.
+ 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.
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436881/+files/AlsaInfo.txt

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

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 1905169] monitors.xml.txt

[Yuriy Padlyak]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1905169/+attachment/5436880/+files/monitors.xml.txt

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

Title:
  gnome-shell crashes when I click new notification window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  gnome-shell crashes when I click new notification window

  Including crash report as a screenshot as send button in that window does 
nothing for some reason
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-10-07 (1141 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905169] ShellJournal.txt

[Yuriy Padlyak]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1905169/+attachment/5436879/+files/ShellJournal.txt

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

Title:
  gnome-shell crashes when I click new notification window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  gnome-shell crashes when I click new notification window

  Including crash report as a screenshot as send button in that window does 
nothing for some reason
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-10-07 (1141 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1905169] Re: gnome-shell crashes when I click new notification window

[Yuriy Padlyak]

apport information

** Tags added: apport-collected groovy

** Description changed:

  
  gnome-shell crashes when I click new notification window
  
- Including crash report as a screenshot as send button in that window
- does nothing for some reason
+ Including crash report as a screenshot as send button in that window does 
nothing for some reason
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.1
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2017-10-07 (1141 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
+ Package: gnome-shell 3.38.1-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
+ RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
+ Tags:  groovy
+ Uname: Linux 5.8.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  gnome-shell crashes when I click new notification window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  gnome-shell crashes when I click new notification window

  Including crash report as a screenshot as send button in that window does 
nothing for some reason
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-10-07 (1141 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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