[Desktop-packages] [Bug 1796187] Re: [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX

2021-02-18 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: In Progress => Fix Released

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

Title:
  [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page
  DOCX

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

Bug description:
  Trying to load the attached DOCX results in a hang.  I force-quit
  after 20 minutes.  The DOCX was created in MS Word (2013 I think), and
  is about 450 pages, thousands of footnotes, but no graphics AFAIK.

  I am using the latest package provided by snap. LibreOffice 6.1.2.1.
  Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  4 23:50:54 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-03 (488 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)

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

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


[Desktop-packages] [Bug 646157]

2021-02-18 Thread Csongor-5
I tried and can confirm the bug is still present with the below version:

Version: 7.0.4.2
Build ID: dcf040e67528d9187c66b2379df5ea4407429775
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Here is what I did:

- clicked the row label of row #8
- clicked the background color icon on the toolbar and changed it black 
- pressed Command-Z (MacOS equivalent of Ctrl-Z on Windows)

As opposed to the original bug report, the height hasn't been changed
when I changed the color to black. But changed it when I used undo.

So, the bug is still there, just in a different shape.

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

Title:
  [Upstream] Calc loses row height value when modifying a cell

Status in LibreOffice:
  Confirmed
Status in gnumeric package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

  1)
  Maverick:
  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  Natty:
  lsb_release -rd
  Description: Ubuntu natty (development branch)
  Release: 11.04

  2)
  Maverick:
  apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:3.3.1-1ubuntu3~maverick1
    Candidate: 1:3.3.1-1ubuntu3~maverick1
    Version table:
   *** 1:3.3.1-1ubuntu3~maverick1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main 
i386 Packages
  100 /var/lib/dpkg/status

  Natty:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.3.0-1ubuntu1
    Candidate: 1:3.3.0-1ubuntu1
    Version table:
   *** 1:3.3.0-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/646157/+attachment/1655284/+files
  /row-height.xls && localc -nologo row-height.xls

  Row 8 height is 0.17". Highlighted row 8, changed background color to
  black, the row height does not change.

  4) What happened instead is the the height changed to 0.40". Pressed
  Ctrl+Z to undo, the color changed back, but the row height did not.

  WORKAROUND: Use Gnumeric as this problem does not occur with it.

  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  apt-cache policy gnumeric
  gnumeric:
Installed: 1.10.8-1ubuntu1
Candidate: 1.10.8-1ubuntu1
Version table:
   *** 1.10.8-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 
Packages
  100 /var/lib/dpkg/status

  Original Report Comments: This is a regression, didn't see this happen
  on Lucid with ubuntu-proposed at least before 2010-06-03. The bug
  doesn't exist in the vanilla OpenOffice.org 3.2.1 or 3.3.0beta1 by
  Sun/Oracle.

  openoffice.org-calc 1:3.2.1-6ubuntu2
  ---
  Architecture: i386
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101214)
  Package: openoffice.org
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Tags: natty
  Uname: Linux 2.6.38-5-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 646157]

2021-02-18 Thread Qa-admin-q
Dear Christopher M. Penalver,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Calc loses row height value when modifying a cell

Status in LibreOffice:
  Confirmed
Status in gnumeric package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

  1)
  Maverick:
  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  Natty:
  lsb_release -rd
  Description: Ubuntu natty (development branch)
  Release: 11.04

  2)
  Maverick:
  apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:3.3.1-1ubuntu3~maverick1
    Candidate: 1:3.3.1-1ubuntu3~maverick1
    Version table:
   *** 1:3.3.1-1ubuntu3~maverick1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main 
i386 Packages
  100 /var/lib/dpkg/status

  Natty:
  apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.3.0-1ubuntu1
    Candidate: 1:3.3.0-1ubuntu1
    Version table:
   *** 1:3.3.0-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/646157/+attachment/1655284/+files
  /row-height.xls && localc -nologo row-height.xls

  Row 8 height is 0.17". Highlighted row 8, changed background color to
  black, the row height does not change.

  4) What happened instead is the the height changed to 0.40". Pressed
  Ctrl+Z to undo, the color changed back, but the row height did not.

  WORKAROUND: Use Gnumeric as this problem does not occur with it.

  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  apt-cache policy gnumeric
  gnumeric:
Installed: 1.10.8-1ubuntu1
Candidate: 1.10.8-1ubuntu1
Version table:
   *** 1.10.8-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 
Packages
  100 /var/lib/dpkg/status

  Original Report Comments: This is a regression, didn't see this happen
  on Lucid with ubuntu-proposed at least before 2010-06-03. The bug
  doesn't exist in the vanilla OpenOffice.org 3.2.1 or 3.3.0beta1 by
  Sun/Oracle.

  openoffice.org-calc 1:3.2.1-6ubuntu2
  ---
  Architecture: i386
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101214)
  Package: openoffice.org
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Tags: natty
  Uname: Linux 2.6.38-5-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1796187]

2021-02-18 Thread Libreoffice-commits
László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/7dd8f8aace536a8e60e87e61ee1d90d61fba15eb

tdf#120351 DOCX import: fix slow endnote import

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page
  DOCX

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

Bug description:
  Trying to load the attached DOCX results in a hang.  I force-quit
  after 20 minutes.  The DOCX was created in MS Word (2013 I think), and
  is about 450 pages, thousands of footnotes, but no graphics AFAIK.

  I am using the latest package provided by snap. LibreOffice 6.1.2.1.
  Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  4 23:50:54 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-03 (488 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)

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

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


[Desktop-packages] [Bug 1853007]

2021-02-18 Thread Gjunk1-2
One standard way to deal with this kind of thing is to open the file -
then immediately unlink the file. The file handle can continue to be
used to read / write the file.

The file is removed from the directory list (so is no longer visible).
It is  removed completely when the file handle is closed - or when app
stops running (which closes all open file handles).

May mean passing file handle around instead of  filename but that's a
trivial and automatable change.

Maybe you guys can do something similar?

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

Title:
  nsemail and nscopy files left in /tmp

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

Bug description:
  thunderbird leaves nsemail and nscopy files in /tmp:

  # ls -l /tmp/ns*
  -rw--- 1 alistair alistair   5522 Nov 18 08:42 /tmp/nscopy-1.tmp
  -rw--- 1 alistair alistair   8883 Nov 18 08:43 /tmp/nscopy-2.tmp
  -rw--- 1 alistair alistair   8311 Nov 18 08:49 /tmp/nscopy-3.tmp
  -rw--- 1 alistair alistair   3455 Nov 18 08:38 /tmp/nscopy.tmp
  -rw--- 1 alistair alistair  25790 Nov 15 09:26 /tmp/nsemail-10.eml
  -rw--- 1 alistair alistair   5840 Nov 15 09:28 /tmp/nsemail-11.eml
  -rw--- 1 alistair alistair  25442 Nov 15 09:29 /tmp/nsemail-12.eml
  -rw--- 1 alistair alistair   2838 Nov 15 09:29 /tmp/nsemail-13.eml
  -rw--- 1 alistair alistair   8556 Nov 15 10:10 /tmp/nsemail-14.eml
  -rw--- 1 alistair alistair   1659 Nov 15 10:32 /tmp/nsemail-15.eml
  -rw--- 1 alistair alistair   3240 Nov 15 10:47 /tmp/nsemail-16.eml
  -rw--- 1 alistair alistair   3260 Nov 15 10:57 /tmp/nsemail-17.eml
  -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml
  -rw--- 1 alistair alistair   4878 Nov 15 13:44 /tmp/nsemail-19.eml
  -rw--- 1 alistair alistair  21150 Nov 13 08:43 /tmp/nsemail-1.eml
  -rw--- 1 alistair alistair   2974 Nov 18 08:41 /tmp/nsemail-1.html
  -rw--- 1 alistair alistair   6328 Nov 15 13:45 /tmp/nsemail-20.eml
  -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml
  -rw--- 1 alistair alistair   2733 Nov 15 17:15 /tmp/nsemail-22.eml
  -rw--- 1 alistair alistair  53857 Nov 16 09:23 /tmp/nsemail-23.eml
  -rw--- 1 alistair alistair  89392 Nov 16 09:39 /tmp/nsemail-24.eml
  -rw--- 1 alistair alistair  80120 Nov 17 10:52 /tmp/nsemail-25.eml
  -rw--- 1 alistair alistair   6361 Nov 17 18:45 /tmp/nsemail-26.eml
  -rw--- 1 alistair alistair   3455 Nov 18 08:38 /tmp/nsemail-27.eml
  -rw--- 1 alistair alistair   5522 Nov 18 08:41 /tmp/nsemail-28.eml
  -rw--- 1 alistair alistair   8883 Nov 18 08:43 /tmp/nsemail-29.eml
  -rw--- 1 alistair alistair  29937 Nov 13 09:37 /tmp/nsemail-2.eml
  -rw--- 1 alistair alistair   5057 Nov 18 08:43 /tmp/nsemail-2.html
  -rw--- 1 alistair alistair   8311 Nov 18 08:49 /tmp/nsemail-30.eml
  -rw--- 1 alistair alistair   2015 Nov 13 09:40 /tmp/nsemail-3.eml
  -rw--- 1 alistair alistair   4949 Nov 18 08:49 /tmp/nsemail-3.html
  -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml
  -rw--- 1 alistair alistair  59817 Nov 15 08:41 /tmp/nsemail-5.eml
  -rw--- 1 alistair alistair   9751 Nov 15 08:47 /tmp/nsemail-6.eml
  -rw--- 1 alistair alistair   2967 Nov 15 08:49 /tmp/nsemail-7.eml
  -rw--- 1 alistair alistair   2983 Nov 15 08:54 /tmp/nsemail-8.eml
  -rw--- 1 alistair alistair  19780 Nov 15 09:14 /tmp/nsemail-9.eml
  -rw--- 1 alistair alistair  27900 Nov 13 08:34 /tmp/nsemail.eml
  -rw--- 1 alistair alistair   1317 Nov 18 08:38 /tmp/nsemail.html
  -rw--- 1 alistair alistair   1115 Nov 18 08:41 /tmp/nsmail-1.tmp
  -rw--- 1 alistair alistair   2424 Nov 18 08:43 /tmp/nsmail-2.tmp
  -rw--- 1 alistair alistair   2000 Nov 18 08:49 /tmp/nsmail-3.tmp
  -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2211 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  Date: Mon Nov 18 08:50:15 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  InstallationDate: Installed on 2017-08-16 (823 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 
   1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 

[Desktop-packages] [Bug 1916092] [NEW] thunderbird paste problem

2021-02-18 Thread Humphrey van Polanen Petel
Public bug reported:

copy this text (taken from a forwarded email)

--
Subject:Technisch
Date:   Thu, 1 Oct 2020 17:47:34 +1000
From:   Humphrey van Polanen Petel 
To: webcare+techni...@fvd.nl


Hallo,

Thierry vertaalde een stuk van John Laughland getiteld "Niet om vrede te
brengen, maar om oorlog te voeren. De achtergrond van het Europese
project."  Ik zou graag het origineel in het Engels lezen.  Kunt u mij
een link geven naar het origineel?  Bij voorbaat dank.

Met vriendelijk groet,
--
Humphrey van Polanen Petel
--

pastes correctly in gedit, leafpad and write
pastes incorrectly in thunderbird (in a new email)

--


Hallo,

Thierry vertaalde een stuk van John Laughland getiteld "Niet om vrede te
brengen, maar om oorlog te voeren. De achtergrond van het Europese
project."  Ik zou graag het origineel in het Engels lezen.  Kunt u mij
een link geven naar het origineel?  Bij voorbaat dank.

Met vriendelijk groet,

Humphrey van Polanen Petel
Subject:Technisch
Date:   Thu, 1 Oct 2020 17:47:34 +1000
From:   Humphrey van Polanen Petel 
To: webcare+techni...@fvd.nl
--

Note: the leading two blank lines were also part of the paste

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: thunderbird 1:68.10.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  humphrey   2243 F pulseaudio
BuildID: 20200629235513
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 19 10:41:22 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ExecutablePath: /usr/lib/thunderbird/thunderbird
ForcedLayersAccel: False
InstallationDate: Installed on 2021-01-14 (35 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.0.1 dev eno1 proto dhcp metric 100 
 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 
 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 
 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 
 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 
metric 600
MostRecentCrashID: bp-d8ee9043-ef35-483e-8c89-c1b0d0181224
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=68.10.0/20200629235513
 Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2020
dmi.bios.release: 2.48
dmi.bios.vendor: HP
dmi.bios.version: N01 Ver. 02.48
dmi.board.name: 8054
dmi.board.vendor: HP
dmi.board.version: KBC Version 05.39
dmi.chassis.type: 4
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 5.57
dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G2 SFF
dmi.product.sku: L1G76AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  thunderbird paste problem

Status in thunderbird package in Ubuntu:
  New

Bug description:
  copy this text (taken from a forwarded email)

  --
  Subject:  Technisch
  Date: Thu, 1 Oct 2020 17:47:34 +1000
  From: Humphrey van Polanen Petel 
  To:   

[Desktop-packages] [Bug 1915771] Re: Thunderbird randomly inserts string

2021-02-18 Thread Humphrey van Polanen Petel
Okay.  Good point about clipit.

I will run the system with and without clipit for some time and take it
from there.

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

Title:
  Thunderbird randomly inserts string

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  How ik happens I don't know, because I notice this only later, but
  some string gets inserted at seemingly random place.  Ctrl-Z undoes
  it.  See attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.10.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2229 F pulseaudio
   /dev/snd/pcmC0D0p:   humphrey   2229 F...m pulseaudio
  BuildID: 20200629235513
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 16 14:14:35 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-01-14 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.0.1 dev eno1 proto dhcp metric 100 
   default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 
   169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 
   192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 
   192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 
metric 600
  MostRecentCrashID: bp-d8ee9043-ef35-483e-8c89-c1b0d0181224
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=68.10.0/20200629235513
   Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 2.48
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.48
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.39
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.57
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: L1G76AV
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1767431] Re: restore type-ahead find, again

2021-02-18 Thread Rich Smith
This is really annoying, counter-intuitive behaviour. At the very least
the old behaviour should be restorable by a setting.

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

Title:
  restore type-ahead find, again

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The dropping of the type-ahead find patch in 17.10 might deeply affect
  non-technical users, as pointed out, this is possibly a bad HCI
  design. As there is a patch exists from the Arch community[1], and the
  at least some people managed to patch it in 17.10[2], might it be
  possible to add such patch back before 18.04.1 so that it won't affect
  people upgraded from 16.04?

  [1]: https://aur.archlinux.org/nautilus-typeahead.git
  [2]: https://askubuntu.com/a/1002521

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

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


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

2021-02-18 Thread Steve Langasek
** Changed in: gnome-shell (Ubuntu)
   Status: Fix Released => Fix Committed

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

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

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

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

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

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

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

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

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


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

2021-02-18 Thread Myna Mefirst
damn it. folks, i clicked on the status by mistake and changed it to released. 
I am SO SORRY. Can someone please change it back to Fix submitted?
Again, sorry.

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1916074] [NEW] Firefox has border if started with kwin compositing disabled

2021-02-18 Thread Boris Gjenero
Public bug reported:

If I start Firefox with in KDE Plasma with kwin compositing disabled,
and the Firefox title bar is disabled via Customize, the whole window
has a border. Otherwise my computer is configured to not have window
borders, and other applications don't have such a border. I don't know
how to make that border go away, besides enabling compositing. Playing
with #main-window in userChrome.css shows that the border and margin I
can set there exists inside the border which I'm trying to remove.

KWin has a hotkey for toggling compositing, found in Global Shortcuts.
Default seems to be Alt+Shift+F12. Toggling compositing doesn't seem to
change this immediately. What matters is the state of compositing when
Firefox was started.

I'm attaching a screenshot showing this border.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firefox 85.0.1+build1-0ubuntu0.20.10.1 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  bgjenero   1908 F pulseaudio
 /dev/snd/controlC0:  bgjenero   1908 F pulseaudio
 /dev/snd/controlC1:  bgjenero   1908 F pulseaudio
BuildID: 20210204182252
CasperMD5CheckResult: skip
Channel: release
CurrentDesktop: KDE
Date: Thu Feb 18 15:15:39 2021
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.44
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-99b8dfa6-8d6d-4541-919c-7d2960210213
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
 user.js
Profiles: Profile0 (Default) - LastVersion=85.0.1/20210204182252 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-99b8dfa6-8d6d-4541-919c-7d2960210213
 bp-f8fe1ebe-97ed-4eec-8e60-11f5d0210118
 bp-e9cbbf6c-3c3f-430d-83ce-a0fca0210101
 bp-f2129335-9559-437d-b537-6f4830210101
 bp-70bc911e-707f-4f53-93fe-f2ebf0210101
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to groovy on 2020-10-22 (119 days ago)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug groovy release-channel third-party-packages

** Attachment added: "Screenshot showing border."
   
https://bugs.launchpad.net/bugs/1916074/+attachment/5464856/+files/Screenshot_2021-02-18_15-18-16.png

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

Title:
  Firefox has border if started with kwin compositing disabled

Status in firefox package in Ubuntu:
  New

Bug description:
  If I start Firefox with in KDE Plasma with kwin compositing disabled,
  and the Firefox title bar is disabled via Customize, the whole window
  has a border. Otherwise my computer is configured to not have window
  borders, and other applications don't have such a border. I don't know
  how to make that border go away, besides enabling compositing. Playing
  with #main-window in userChrome.css shows that the border and margin I
  can set there exists inside the border which I'm trying to remove.

  KWin has a hotkey for toggling compositing, found in Global Shortcuts.
  Default seems to be Alt+Shift+F12. Toggling compositing doesn't seem
  to change this immediately. What matters is the state of compositing
  when Firefox was started.

  I'm attaching a screenshot showing this border.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bgjenero   1908 F pulseaudio
   /dev/snd/controlC0:  bgjenero   1908 

[Desktop-packages] [Bug 1916055] Re: XML parse error: cannot load more than 200000 XML elements

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

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

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

Title:
  XML parse error: cannot load more than 20 XML elements

Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have really big SVG file as in the https://askubuntu.com/q/1317267/66509 
question
  2. Open the file using for example Eye of MATE

  Expected result:
  * file is opened

  Actual result:
  * file is not opened, EoM shows error instead:

  Could not load image 'NOSTOC2.svg'.
  XML parse error: cannot load more than 20 XML elements

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: librsvg2-2:amd64 2.48.9-1ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Feb 18 19:49:00 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: librsvg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1916055] [NEW] XML parse error: cannot load more than 200000 XML elements

2021-02-18 Thread Norbert
Public bug reported:

Steps to reproduce:
1. Have really big SVG file as in the https://askubuntu.com/q/1317267/66509 
question
2. Open the file using for example Eye of MATE

Expected result:
* file is opened

Actual result:
* file is not opened, EoM shows error instead:

Could not load image 'NOSTOC2.svg'.
XML parse error: cannot load more than 20 XML elements

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: librsvg2-2:amd64 2.48.9-1ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Feb 18 19:49:00 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: librsvg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  XML parse error: cannot load more than 20 XML elements

Status in librsvg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have really big SVG file as in the https://askubuntu.com/q/1317267/66509 
question
  2. Open the file using for example Eye of MATE

  Expected result:
  * file is opened

  Actual result:
  * file is not opened, EoM shows error instead:

  Could not load image 'NOSTOC2.svg'.
  XML parse error: cannot load more than 20 XML elements

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: librsvg2-2:amd64 2.48.9-1ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Feb 18 19:49:00 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: librsvg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file

2021-02-18 Thread Balint Reczey
** Bug watch added: Debian Bug tracker #981407
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981407

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981407
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd spams the syslog about lack of native systemd unit file

Status in apport package in Ubuntu:
  Incomplete
Status in fam package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in ipfm package in Ubuntu:
  Incomplete
Status in n2n package in Ubuntu:
  Incomplete
Status in pfm package in Ubuntu:
  Incomplete
Status in shadowsocks package in Ubuntu:
  Incomplete
Status in sysfsutils package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete
Status in xl2tpd package in Ubuntu:
  Incomplete
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd in hirsute spams the syslog file several times per second
  about services lacking native systemd unit files.  Two things should
  happen.

  1) a systemd unit file ought to be created
  2) systemd should be slowed down with regards to these messages

  Feb 17 02:02:48 ubuntu-devel kernel: [  289.794825] 
systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  290.165351] 
systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  291.111278] 
systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:50 ubuntu-devel kernel: [  291.507164] 
systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.

  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386062] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386321] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386742] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386767] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.387281] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.388931] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.388955] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.389412] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a 
native systemd unit file. 

[Desktop-packages] [Bug 1870822] Re: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window)

2021-02-18 Thread Treviño
** Description changed:

- just what I said in the title, the gnome user interface hung for a
- minute or so, after pressing 'x' to close a terminal window...
+ [ Impact ]
  
- been having other issues with the gnome-shell, in this ubuntu beta, this
- is new.
+ The gnome user interface hung for a minute or so, after pressing 'x' to
+ close a terminal window
  
- ProblemType: Crash
- DistroRelease: Ubuntu 20.04
+ [ Test case ]
+ 
+ - Run wine on wayland (natively) 
+ - Open a window containing a dialog box
+ - Close the dialog
+ 
+ Otherwise
+ 
+ - Closing a terminal should work
+ 
+ [ Regression potential ]
+ 
+ Windows are wrongly focused on click.
+ 
+ 
+ ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:40:19 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
- Signal: 6
- SourcePackage: gnome-shell
+ Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
-  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
-  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
+  () at /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with assertion failure
  window.c:1552:meta_window_unmanage: assertion failed:
  (window->display->focus_window != window)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

  The gnome user interface hung for a minute or so, after pressing 'x'
  to close a terminal window

  [ Test case ]

  - Run wine on wayland (natively) 
  - Open a window containing a dialog box
  - Close the dialog

  Otherwise

  - Closing a terminal should work

  [ Regression potential ]

  Windows are wrongly focused on click.


  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:40:19 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1908284] Re: [snap] chromium headless crashes at startup on non-desktop system

2021-02-18 Thread Olivier Tilloy
Does deleting ~/snap/chromium/common/.cache/fontconfig work around the
problem, by any chance?

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

Title:
  [snap] chromium headless crashes at startup on non-desktop system

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 20.04 and it looks like the current stable version
  of the Chromium snap has an issue running headless:

  ```
  tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 
https://chromium.org
  [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: 
process_type gpu-process numfds 3 child_pid -1
  [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32)
  Trace/breakpoint trap (core dumped)
  ```

  ```
  tjcravey@chromium:~$ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 15:33 UTC
  channels:
latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB -
latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB -
latest/beta:  88.0.4324.41 2020-12-15 (1441) 144MB -
latest/edge:  89.0.4350.4  2020-12-11 (1434) 257MB -
  installed:  87.0.4280.88(1424) 124MB -
  ```

  I was able to revert back to snap 1421 on a different system and that
  command works fine there.

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

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


[Desktop-packages] [Bug 1915316] Re: Impossible-to-disable background auto-update randomly causes loss of data

2021-02-18 Thread Olivier Tilloy
*** This bug is a duplicate of bug 338785 ***
https://bugs.launchpad.net/bugs/338785

** This bug has been marked a duplicate of bug 338785
   [MASTER] Updates while firefox is running cause various problems until 
restart

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

Title:
  Impossible-to-disable background auto-update randomly causes loss of
  data

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox from Ubuntu 20.04 repository. Version after update is: 
85.0.1+build1-0ubuntu0.20.04.1
  I am fairly certain that before this update, I was on the latest version 
available.

  
  Problem description:

  Whenever an update is automatically installed in the background, a restart is 
required. The auto-updates occur in background at seemingly random times, and 
are, AFAIK impossible to disable (workaround seems to be to install Firefox 
from different source).
  The user always learns about the update only after it has happened already, 
and it is impossible to open new tabs. Before the restart, strange behavior 
often occurs, such as inexplicable tab crashes, pages not loading and staying 
blank, or new tabs being blank or crashing instead of showing the restart 
prompt. Sometimes, the restart prompt only appears after minutes of fighting 
with the previously described problems.

  
  This is alarming and frustrating on its own, but in the following cases this 
leads to loss of data (I have experienced all of them more than once):

  -When any content is open in private window, that the user wishes to continue 
working on. (Because private windows don't get restored after restart)
  -When a download is running which is impossible to resume, is from a 
one-time-download link, or when download is running in a private window.
  -When user is working on any work that requires opening a new window to 
finish, but progress will be lost when browser is closed.
  -When a browser with any unfinished work just crashes randomly, most often 
after following a link or submitting a form.

  
  Steps to reproduce:
  1) Install the older version of Firefox from the Ubuntu 20.04 repository (it 
is likely that this hasn't been fixed in current one either).
  2) Start to do any work filling forms, and requiring long downloads and 
opning new tabs, open few tabs in private window.
  3) Wait for it to automatically install an update in background.
  4) Wait until restart is prompted or stuff breaks randomly.
  5) Restart
  6) Your download is failed now, your unsubmitted forms are empty and your 
private windows are lost.

  
  Things that need to be fixed (in order from most severe):

  -Automatic installation of an update should never happen unprompted, while 
the user is working, and without their knowledge (unless this no longer leads 
to loss of data). With things like they are now, the absolute minimum is for 
the updates to happen at start-up, before the user is allowed to do any work.
  -User should be allowed to refuse an automatic update if it happens in a way 
that can lead to loss of data.
  User should be able to disable automatic updates.

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

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


[Desktop-packages] [Bug 1914601] Re: GUI apps do not start from the link created

2021-02-18 Thread Patrick Wu
** Changed in: wslu (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  GUI apps do not start from the link created

Status in wslu package in Ubuntu:
  Fix Committed

Bug description:
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  wslu:
Installed: 2.3.6-0ubuntu2~20.04.0
Candidate: 2.3.6-0ubuntu2~20.04.0
Version table:
   *** 2.3.6-0ubuntu2~20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.3.6-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  C:\Users\username\Desktop>wsl -l -v
NAME   STATE   VERSION
  * Ubuntu-20.04   Running 2

  $ wslusc --version
  wslu v2.3.6; wslusc v37

  $ wslusc terminator
  [info] Create shortcut terminator.lnk successful

  C:\Users\username\Desktop>terminator.lnk
  Unable to init server: Could not connect: Connection refused
  Unable to init server: Could not connect: Connection refused
  You need to run terminator in an X environment. Make sure $DISPLAY is 
properly set

  $ wslusc --gui terminator
  [info] Create shortcut terminator.lnk successful

  C:\Users\username\Desktop>terminator.lnk
  

  Looks like DISPLAY propery is not set correctly by the underlying
  script:

  $ pwd
  /usr/share/wslu
  $ export DISPLAY=SHOULD_BE_SET
  $ . wsl-integration.sh
  $ echo $DISPLAY
  SHOULD_BE_SET

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

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


[Desktop-packages] [Bug 1915498] Re: Copy / paste in Firefox randomly broken

2021-02-18 Thread Olivier Tilloy
That upstream bug sounds indeed similar to the problem you're observing,
but given that it's closed, it's unlikely to receive attention. Can you
file a new upstream bug report and share the link to it here?

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

Title:
  Copy / paste in Firefox randomly broken

Status in firefox package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1913570] Re: Firefox not opening file chooser dialog for importing certificates

2021-02-18 Thread Olivier Tilloy
It works for me here, I wonder if this might be caused by the missing
XDG portal.

Can you share the output of the following command?

apt policy xdg-desktop-portal*

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

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

Title:
  Firefox not opening file chooser dialog for importing certificates

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When installed as a snap, firefox won't open the file chooser dialog
  for importing a certificate authority. However, it is working when
  installed using apt.

  How to reproduce:
  1. Install firefox as snap
  2. Navigate to Preferences | Privacy & Security | Certificates | View 
Certificates
  3. Select Authorities
  4. Click Import ...
 -> A file selector dialog should open to import a certificate, but nothing 
happens.

  Environment:
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jan 28 11:43:55 2021
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-01-15 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 42
   model name   : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
   stepping : 7
   microcode: 0x2f
   cpu MHz  : 3701.000
   cache size   : 8192 KB
   physical id  : 6
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 6
   initial apicid   : 6
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 
cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx 
hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d 
arch_capabilities
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
   bogomips : 7402.00
   clflush size : 64
   cache_alignment  : 64
   address sizes: 43 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US
   LC_ADDRESS=de_DE.UTF-8
   LC_NAME=de_DE.UTF-8
   LC_MONETARY=de_DE.UTF-8
   LC_PAPER=de_DE.UTF-8
   LANG=en_US.UTF-8
   TERM=xterm-256color
   LC_IDENTIFICATION=de_DE.UTF-8
   LC_TELEPHONE=de_DE.UTF-8
   LC_MEASUREMENT=de_DE.UTF-8
   XDG_RUNTIME_DIR=
   LC_TIME=de_DE.UTF-8
   PATH=(custom, no user)
   LC_NUMERIC=de_DE.UTF-8
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Snap: firefox 84.0.2-1 (stable)
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1916029] [NEW] [nvidia] gnome-shell freezes randomly on login/startup

2021-02-18 Thread Ian Johnson
Public bug reported:

The symptoms here for me are exactly the same as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1912246 where after starting up my Groovy system with X11 and
proprietary NVIDIA drivers the desktop session just hangs for a minute
or so.

However I have the desktop-icons extension disabled now, so I think it's
highly unlikely that that extension is the cause of this hang. Looking
through the gnome-shell logs, I see some related things for the ubuntu-
dock extension:

Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2b3cb40 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for 
actor 0x5595d2b3cb40/dashtodockContainer which isn't a descendent of the stage!
Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2b5bfd0 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for 
actor 0x5595d2b5bfd0/dashtodockContainer which isn't a descendent of the stage!
Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2ab2100 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for 
actor 0x5595d2ab2100/dashtodockContainer which isn't a descendent of the stage!
Feb 18 06:19:59 gnome-shell[12469]: Bogus presentation time 0 travelled back in 
time, using current time.

full log at https://pastebin.ubuntu.com/p/z8jChdF4gw in addition to the
ubuntu-bug auto-collected stuff

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 18 06:28:24 2021
InstallationDate: Installed on 2019-07-05 (594 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to groovy on 2021-01-16 (33 days ago)

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

Title:
  [nvidia] gnome-shell freezes randomly on login/startup

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

Bug description:
  The symptoms here for me are exactly the same as described in
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
  desktop-icons/+bug/1912246 where after starting up my Groovy system
  with X11 and proprietary NVIDIA drivers the desktop session just hangs
  for a minute or so.

  However I have the desktop-icons extension disabled now, so I think
  it's highly unlikely that that extension is the cause of this hang.
  Looking through the gnome-shell logs, I see some related things for
  the ubuntu-dock extension:

  Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2b3cb40 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
  Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called 
for actor 0x5595d2b3cb40/dashtodockContainer which isn't a descendent of the 
stage!
  Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2b5bfd0 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
  Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called 
for actor 0x5595d2b5bfd0/dashtodockContainer which isn't a descendent of the 
stage!
  Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the 
widget [0x5595d2ab2100 
Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive 
"dashtodockContainer"] which is not in the stage.
  Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called 
for actor 0x5595d2ab2100/dashtodockContainer which isn't a descendent of the 
stage!
  Feb 18 06:19:59 gnome-shell[12469]: Bogus presentation time 0 travelled back 
in time, using current time.

  full log at 

[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file

2021-02-18 Thread Paride Legovini
Hello Rolf and thanks for this bug report. I can't reproduce the issue
you described neither on my laptop, which has been following Ubuntu
"devel" for quite some cycles now, nor in a clean LXD container running
Hirsute.

You brought freeradius as an example, but freeradius *does* ship with a
systemd unit file:

  /lib/systemd/system/freeradius.service

So this looks like a local (mis)configuration issue to me. If you still
think there's actually a bug here we need more information on how to
reproduce it from a clean environment, otherwise it's difficult to
confirm the problem or to begin working on it.

I'm marking this bug report as Incomplete for the moment.

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  systemd spams the syslog about lack of native systemd unit file

Status in apport package in Ubuntu:
  Incomplete
Status in fam package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in ipfm package in Ubuntu:
  Incomplete
Status in n2n package in Ubuntu:
  Incomplete
Status in pfm package in Ubuntu:
  Incomplete
Status in shadowsocks package in Ubuntu:
  Incomplete
Status in sysfsutils package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete
Status in xl2tpd package in Ubuntu:
  Incomplete

Bug description:
  systemd in hirsute spams the syslog file several times per second
  about services lacking native systemd unit files.  Two things should
  happen.

  1) a systemd unit file ought to be created
  2) systemd should be slowed down with regards to these messages

  Feb 17 02:02:48 ubuntu-devel kernel: [  289.794825] 
systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  290.165351] 
systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  291.111278] 
systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:50 ubuntu-devel kernel: [  291.507164] 
systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.

  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386062] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386321] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386742] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386767] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 

[Desktop-packages] [Bug 1913655] Re: Firefox Titlebar Does Not Turn To Inactive Color Until Cursor Passes Over It.

2021-02-18 Thread Olivier Tilloy
Thanks for following up Ubfan. So this appears to be fixed, I'm updating
the bug status accordingly. Feel free to re-open if the issue surfaces
again.

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

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

Title:
  Firefox Titlebar Does Not Turn To Inactive Color Until Cursor Passes
  Over It.

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal

  $ apt-cache policy firefox
  firefox:
Installed: 84.0.2+build1-0ubuntu0.20.04.1
Candidate: 84.0.2+build1-0ubuntu0.20.04.1
Version table:
   *** 84.0.2+build1-0ubuntu0.20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Ubuntu 20.04, Gnome desktop. Settings/Appearance/Standard Window Colors 
Selected. gtk issue?
  Kernel 5.4.0-64-generic #72-Ubuntu SMP Fri Jan 15 10:27:54 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux
  Nvidia gtx970, driver 460.32.03 (problem with Intel/i915 video also).

  To display the problem:
  Start with a Firefox window displaying the active color in its titlebar.
  Click on another window (like a gnome terminal).
  The color of the terminal window titlebar changes to the active color.
  The active window color of the Firefox titlebar should change to the inactive 
color,
  but does not.  However the boarder of the Firefox window does change to the 
inactive color.
  Both the terminal and Firefox window now display their titlebar with the 
active color.
  The active color on the Firefox titlebar will remain, while other windows 
become
  active and inactive, with normal titlebar color switches.
  When the cursor passes over the Firefox (wrongly active) titlebar, the
  color switches to the inactive color.
  The Firefox window is the only one I have found that displays this problem.

  
  It helps to have distinct colors and wide enough boarders to see the problem, 
  since the default is light gray/gray. To change the active color to yellow,
  and a slightly wider boarder, make a file ~/.config/gtk-3.0/gtk.css
  with the below contents (for active=yellow, inactive=gray):

  .titlebar {
  background: #00;
  color:white; 
  }
  .titlebar:backdrop  {
  background: #77;
  color:white;
  }
  decoration {
  border: 2px solid #00;
  background: #00;
  }
  decoration:backdrop {
  border: 2px solid #77;
  background: #77;
  }

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

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


[Desktop-packages] [Bug 1915771] Re: Thunderbird randomly inserts string

2021-02-18 Thread Olivier Tilloy
This very much sounds like you were triggering the paste action from clipit 
(probably using a keyboard shortcut) without realizing it.
I'm closing this bug as it's unlikely to be a problem in thunderbird, feel free 
to re-open if you think it is.

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Thunderbird randomly inserts string

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  How ik happens I don't know, because I notice this only later, but
  some string gets inserted at seemingly random place.  Ctrl-Z undoes
  it.  See attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.10.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2229 F pulseaudio
   /dev/snd/pcmC0D0p:   humphrey   2229 F...m pulseaudio
  BuildID: 20200629235513
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 16 14:14:35 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-01-14 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.0.1 dev eno1 proto dhcp metric 100 
   default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 
   169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 
   192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 
   192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 
metric 600
  MostRecentCrashID: bp-d8ee9043-ef35-483e-8c89-c1b0d0181224
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1138
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=68.10.0/20200629235513
   Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 2.48
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.48
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.39
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.57
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: L1G76AV
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2021-02-18 Thread Andrii
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Problem has NOT been fixed for my setup:

- Kernel: 5.4.0-65-generic (also tried 5.11.0-051100-generic)
- OS: Lubuntu 20.04.2 LTS
- Machine: OptiPlex 9020
- Headset: Sony WH-XB900N

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

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

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-18 Thread Łukasz Zemczak
Ok, I have accepted all the packages into -proposed pockets besides
nvidia-prime for bionic. There seems to be an old unverified nvidia-
prime/u-d-c SRU in bionic-proposed that needs to be handled first. Can
someone take a look at LP: #1904583?

Another thing: since this is a whole backport of the prime-settings, I'd
like some more aging and manual exploratory testing of this before we
proceed.

Final thing, regarding the nvidia-prime part: looking at the diff I saw this 
change bundled in it:
@@ -152,10 +154,10 @@
 # (No need to check if nvidia is available)
 self._enable_nvidia()
 elif profile == "on-demand":
-self._disable_nvidia(keep_nvidia_modules=True)
 if self._supports_runtimepm():
 self._enable_runtimepm()
 self._enable_kms()
+self._disable_nvidia(keep_nvidia_modules=True)
 else:
 # Make sure that the installed packages support PRIME
 #if not self._supports_prime():

I only noticed it after already accepting groovy. Just wanted to make
sure: is this related to the initramfs update? Was it needed? Is this
change expected?

Thank you.

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-18 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

Accepted nvidia-settings into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/460.39-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: nvidia-settings (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2021-02-18 Thread Alexei Kharchev
there is solution
Add this repository to sources.list.d
deb http://ppa.launchpad.net/nrbrtx/xorg-hotkeys/ubuntu focal main

I wrote this comment to Linux Mint forum too

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  Won't Fix
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions

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


[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-18 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


[Desktop-packages] [Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload

2021-02-18 Thread Valentin Lab
I'm on a dual screen with 4k and 2.7k (Surface pro 4) intel graphical
chipset, i7 with 4 cores.

On a 20.04, using gnome-shell over Xorg, gnome-shell proc usage jumps
from 0-3% to 40-60% usage when using indicator-multiload.

gnome-shell over Wayland will have same issue, with an added visible
mouse stuttering problem.

interestingly, I've installed unity7 (with ubuntu-unity-desktop 0.2),
and this doesn't occur on unity as dramatically: it goes from 2-4%
without indicator-multiload to 6-8%. This makes it totally usable on
unity.

indicator-multiload   0.4-0ubuntu5
gnome-shell   3.36.4-1ubuntu1~20.04.2
compiz-core   1:0.9.14.1+20.04.20200211-0ubuntu1

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

Title:
  CPU usage increases dramatically (and visible stuttering) when running
  indicator-multiload

Status in libindicator:
  Fix Committed
Status in The Ubuntu Power Consumption Project:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in indicator-multiload package in Ubuntu:
  Confirmed
Status in libindicator package in Ubuntu:
  Fix Released

Bug description:
  using 0.1-0~5~natty1 on mostly up to date natty system, when running
  the indicator-multiload with with just cpu monitor and the default
  update interval of 500 milliseconds, I see (via top) that compiz usage
  when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU.
  Reducing the update interval does seem to have an affect.

  I realize that 
  a.) top is not scientific
  b.) there could be something I'm missing here
  c.) saying "300%" (in the subject) is not scientific

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

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


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

2021-02-18 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

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

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

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

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

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

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


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

2021-02-18 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

Accepted nvidia-prime into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.10.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-settings (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-18 Thread Łukasz Zemczak
Hello Alberto, or anyone else affected,

Accepted nvidia-settings into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/460.39-0ubuntu0.20.10.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

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

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

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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


[Desktop-packages] [Bug 1914601] Re: GUI apps do not start from the link created

2021-02-18 Thread Mark Mitrushkin
Hi,

How do you test?

- Which version of WSL you are using?
- What is the output of `echo $DISPLAY` if you open a terminal from the link 
created by wslu?
- What is the content of `/etc/resolv.conf`?

I found where the issue is. On "wslu v3.2.1-1; wslusc v40", in
`/usr/share/wslu/wslusc-helper.sh` if I comment the following code, the
shortcuts start working:

#  if ( eval "$ipconfig_exec" | grep -n -m 1 "Default Gateway.*: [0-9a-z]" | 
cut -d : -f 1 ) >/dev/null; then
#set +H
#wsl2_d_tmp="$(eval "$ipconfig_exec" | grep -n -m 1 "Default Gateway.*: 
[0-9a-z]" | cut -d : -f 1)"
#wsl2_d_tmp="$(eval "$ipconfig_exec" | sed $(( wsl2_d_tmp - 4 ))','$(( 
wsl2_d_tmp + 0 ))'!d' | grep IPv4 | cut -d : -f 2 | sed -e "s|\s||g" -e 
"s|\r||g")"
#set -H
#export DISPLAY=${wsl2_d_tmp}:0.0
#  else
wsl2_d_tmp="$(grep nameserver /etc/resolv.conf | awk '{print $2}')"
export DISPLAY=${wsl2_d_tmp}:0
#  fi

This means the script is not setting DISPLAY variable properly and no
matter which X11 server you are using, it won't connect since on WSL2 it
is not in the local network. Here is what the script does without
commenting:

$ echo $DISPLAY
172.24.224.1:0  # this is what the IP should be
$ unset DISPLAY
/usr/share/wslu$ . ./wslusc-helper.sh 
$ echo $DISPLAY
192.168.0.16:0.0# this is what the scripts sets, this would work on WSL1 
where host and WSL are on the same network, but on WSL2 it won't work

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

Title:
  GUI apps do not start from the link created

Status in wslu package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  wslu:
Installed: 2.3.6-0ubuntu2~20.04.0
Candidate: 2.3.6-0ubuntu2~20.04.0
Version table:
   *** 2.3.6-0ubuntu2~20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.3.6-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  C:\Users\username\Desktop>wsl -l -v
NAME   STATE   VERSION
  * Ubuntu-20.04   Running 2

  $ wslusc --version
  wslu v2.3.6; wslusc v37

  $ wslusc terminator
  [info] Create shortcut terminator.lnk successful

  C:\Users\username\Desktop>terminator.lnk
  Unable to init server: Could not connect: Connection refused
  Unable to init server: Could not connect: Connection refused
  You need to run terminator in an X environment. Make sure $DISPLAY is 
properly set

  $ wslusc --gui terminator
  [info] Create shortcut terminator.lnk successful

  C:\Users\username\Desktop>terminator.lnk
  

  Looks like DISPLAY propery is not set correctly by the underlying
  script:

  $ pwd
  /usr/share/wslu
  $ export DISPLAY=SHOULD_BE_SET
  $ . wsl-integration.sh
  $ echo $DISPLAY
  SHOULD_BE_SET

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

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


[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-02-18 Thread Balint Reczey
@seb128 please also include the fix for n-m tests failing due to MAC
changes to let systemd 247.1-4ubuntu1 migrate.

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

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in lxd package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

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


[Desktop-packages] [Bug 1916005] Re: gnome-shell hangs window decorations and dialogs

2021-02-18 Thread whitis
disabling makes freeze duration much shorter but you lose your desktop
session every time.  DATA LOSS inevitable.

sudo perl -p -i -n -e "s/enabled=1/enabled=0/" /etc/default/apport
sudo systemctl disable apport
sudo service apport stop

If I remove apport and whoopsie, then the duration of the freeze is reduced to 
5 seconds under light load and desktop is not lost.  This uninstalls ubuntu-bug 
as well.
sudo apt-get purche apport whoopsie

The system still freezes and under load it could be much worse.   Gnome-
shell is apparently still crashing but it isn't compounded by apport
delays.

If I reinstall apport but not whoopsie, I still have the long delay.

cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P %E

If I change it to coredump, gnome-shell still crashes the whole desktop
sudo bash -c 'echo "core" >/proc/sys/kernel/core_pattern'

If I change it back and then purge apport, it changes the pattern to:
!/usr/share/apport/apport %p %s %c %d %P %E

And gnome-shell crashes somewhat gracefully, allowing you to keep your
desktop.  What happens under system load remains to be seen.

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

Title:
  gnome-shell hangs window decorations and dialogs

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Desktop hangs frequently, sometimes more than once per day and can result in 
loss of work.
  Today I found a way to easily reproduce.
  - sudo apt-get install key-mon
  - start new session with nothing but gnome-terminal running.  Unnecssary to 
reproduce, you can have dozens of programs running.
  - key-mon &
  - right click on key-mon window and open settings
  - enable meta key (may not be necessary) 
  - switch to misc tab
  - Check window decoration with nothing else checked
  - attempt to uncheck window decoration.  Fails.  Trying multiple times won't 
help and may make things worse.
  - Desktop is now frozen and will remain this way for an indeterminate time 
but may eventually come back within a minute.   If you actually had stuff 
running on your machine, chances of coming back aren't great.   Symptoms 
include:
   - psensor graph continues to update
   - cannot make terminal respond.
- cannot drag windows
- cannot focus windows

  When it came back, one of 3 gnome shell processes previously detected
  using psgrep was missing and has been replaced.  This is consistent
  with the screen being redrawn when it comes back.

  When desktop didn't come back recently, I was able to CTRL-ALT-F3 to a 
console and kill okular, freecad, gimp, key-mon, firefox, 
freecad-daily,openscad, file-roller, psensor, and gnome-terminal, in that 
order, until there was nothing left and still did not regain control of system. 
  Ctrl-Alt-Del ESC also failed (though I think I did end up causing system to 
reboot).   System pressure after killing okular and freecad was:
  ===memory
  some avg10=0.00 avg60=0.00 avg300=0.00 total=0
  full avg10=0.00 avg60=0.00 avg300=0.00 total=0
  ===cpu
  some avg10=0.01 avg60=0.02 avg300=0.00 total=9348303
  ===io
  some avg10=18.81 avg60=30.25 avg300=34.80 total=852281032
  full avg10=17.43 avg60=28.42 avg300=32.91 total=795530186

  I was able to reproduce this many times by turning window decorations
  on and off in key-mon.

  In the past, desktop freezes were frequently caused by dialog boxes
  popping up including the wait of force quit dialog.  I installed the
  extension to disable wait-or-force quit.   System still becomes
  severely non-responsive when programs like firefox eat up a lot of RAM
  and I have to use onetab firefox extension regularly.

  System information
  ==
  Linux cervantes 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic

  System:Host: cervantes Kernel: 5.4.0-65-generic x86_64 bits: 64
 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.5 LTS
  Machine:   Device: desktop Mobo: ASUSTeK model: Crosshair IV Formula v: Rev 
1.xx serial: N/A
 BIOS: American Megatrends v: 3029 date: 10/09/2012
  CPU:   6 core AMD Phenom II X6 1090T (-MCP-) cache: 3072 KB
 clock speeds: max: 3200 MHz 1: 2976 MHz 2: 1979 MHz 3: 1708 MHz
 4: 1736 MHz 5: 2420 MHz 6: 2666 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cayman PRO [Radeon HD 6950]
 Display Server: x11 (X.Org 1.20.8 ) driver: radeon
 Resolution: 3840x2160@30.00hz
 OpenGL: renderer: AMD CAYMAN (DRM 2.50.0 / 5.4.0-65-generic, LLVM 
9.0.0)
 version: 4Linux cervantes 5.4.0-65-generic #73~18.04.1-Ubuntu SMP 
Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor 

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

2021-02-18 Thread munbi
Hi Paride, where the test and logs above sufficient to validate the bug
? Can I do anything more to help looking into this issue ?

Regards, Gabriele.

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

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

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

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

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

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

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

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

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1916005] Re: gnome-shell hangs window decorations and dialogs

2021-02-18 Thread whitis
Mouse cursor works when frozen.

Actually, it looks like psensor does hang until the system starts to come back. 
 It does show a spike (of unknown amplitude) in CPU usage (tenfold) and CPU 
temperature and there is an audible increase in fan speed. Top/gnome-terminal 
also freezes.  
top -d 1 -p `pgrep gnome-shell|paste -sd,`
If I run a command in a terminal that writes the date once per second and tee's 
it to a file, the terminal output will freeze immediately when desktop freezes 
but the timestamps in the file show it still continues to write to the file on 
time.  CPU pressure was not high but CPU usage was fairly high but not on all 
cores simultaneously.
Duration of freeze on lightly loaded system was around 25 seconds.

Quickly switching to another console and running top shows apport and 
whoopsie-upload at top of CPU usage.   Turning off Settings -> Privacy -> 
Problem Reporting -> Send Error reports to canonical changes nothing.   
apport/whoopsie-upload still run and eat 100% of cpu.
+

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

Title:
  gnome-shell hangs window decorations and dialogs

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Desktop hangs frequently, sometimes more than once per day and can result in 
loss of work.
  Today I found a way to easily reproduce.
  - sudo apt-get install key-mon
  - start new session with nothing but gnome-terminal running.  Unnecssary to 
reproduce, you can have dozens of programs running.
  - key-mon &
  - right click on key-mon window and open settings
  - enable meta key (may not be necessary) 
  - switch to misc tab
  - Check window decoration with nothing else checked
  - attempt to uncheck window decoration.  Fails.  Trying multiple times won't 
help and may make things worse.
  - Desktop is now frozen and will remain this way for an indeterminate time 
but may eventually come back within a minute.   If you actually had stuff 
running on your machine, chances of coming back aren't great.   Symptoms 
include:
   - psensor graph continues to update
   - cannot make terminal respond.
- cannot drag windows
- cannot focus windows

  When it came back, one of 3 gnome shell processes previously detected
  using psgrep was missing and has been replaced.  This is consistent
  with the screen being redrawn when it comes back.

  When desktop didn't come back recently, I was able to CTRL-ALT-F3 to a 
console and kill okular, freecad, gimp, key-mon, firefox, 
freecad-daily,openscad, file-roller, psensor, and gnome-terminal, in that 
order, until there was nothing left and still did not regain control of system. 
  Ctrl-Alt-Del ESC also failed (though I think I did end up causing system to 
reboot).   System pressure after killing okular and freecad was:
  ===memory
  some avg10=0.00 avg60=0.00 avg300=0.00 total=0
  full avg10=0.00 avg60=0.00 avg300=0.00 total=0
  ===cpu
  some avg10=0.01 avg60=0.02 avg300=0.00 total=9348303
  ===io
  some avg10=18.81 avg60=30.25 avg300=34.80 total=852281032
  full avg10=17.43 avg60=28.42 avg300=32.91 total=795530186

  I was able to reproduce this many times by turning window decorations
  on and off in key-mon.

  In the past, desktop freezes were frequently caused by dialog boxes
  popping up including the wait of force quit dialog.  I installed the
  extension to disable wait-or-force quit.   System still becomes
  severely non-responsive when programs like firefox eat up a lot of RAM
  and I have to use onetab firefox extension regularly.

  System information
  ==
  Linux cervantes 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic

  System:Host: cervantes Kernel: 5.4.0-65-generic x86_64 bits: 64
 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.5 LTS
  Machine:   Device: desktop Mobo: ASUSTeK model: Crosshair IV Formula v: Rev 
1.xx serial: N/A
 BIOS: American Megatrends v: 3029 date: 10/09/2012
  CPU:   6 core AMD Phenom II X6 1090T (-MCP-) cache: 3072 KB
 clock speeds: max: 3200 MHz 1: 2976 MHz 2: 1979 MHz 3: 1708 MHz
 4: 1736 MHz 5: 2420 MHz 6: 2666 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cayman PRO [Radeon HD 6950]
 Display Server: x11 (X.Org 1.20.8 ) driver: radeon
 Resolution: 3840x2160@30.00hz
 OpenGL: renderer: AMD CAYMAN (DRM 2.50.0 / 5.4.0-65-generic, LLVM 
9.0.0)
 version: 4Linux cervantes 5.4.0-65-generic #73~18.04.1-Ubuntu SMP 
Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic
  .3 Mesa