[Desktop-packages] [Bug 1895643] Autopkgtest regression report (jsunit/0.2.2-2ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted jsunit (0.2.2-2ubuntu1) for focal have 
finished running.
The following regressions have been reported in tests triggered by the package:

enigmail/2:2.1.6+ds1-1 (ppc64el, amd64, armhf, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#jsunit

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  Invalid
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 699922]

[Mkmelin+mozilla]

No that doesn't help.
I see the same thing for web notifications in Firefox, so bug 1450036 is 
related (newmailalert.js is kind of a fork of the same code)

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

Title:
  Thunderbird displays notification on wrong monitor

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

Bug description:
  Binary package hint: thunderbird

  In a multiple monitor setup, Thunderbird displays its notification in
  the bottom right of the leftmost monitor, rather than the window on
  which it is currently active.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
  Uname: Linux 2.6.35-24-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Jan  7 16:01:00 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/699922/+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 1581625] Re: /usr/lib/libreoffice/program/soffice.bin:*** Error in `/usr/lib/libreoffice/program/soffice.bin': corrupted double-linked list: ADDR ***

[Launchpad Bug Tracker]

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

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

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

Title:
  /usr/lib/libreoffice/program/soffice.bin:*** Error in
  `/usr/lib/libreoffice/program/soffice.bin': corrupted double-linked
  list: ADDR ***

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding libreoffice.  This problem was most recently seen with
  version 1:5.1.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/85626ee1bd34018dde600741e1ca536b694af9f5
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1581625/+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 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded

[Launchpad Bug Tracker]

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

** Changed in: v4l-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

Status in v4l-utils package in Ubuntu:
  Expired

Bug description:
  ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-
  keytable.rules containing the following rule:

  ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
  /etc/rc_maps.cfg -s $name"

  After upgrading to Focal, this does not get triggered at boot, nor if
  I (re)insert my receiver when the system is running. Therefore, the
  custom keytable does not get loaded.

  This is the udev events that occur when I insert the receiver:

  $ sudo udevadm monitor
  monitor will print the received events for:
  UDEV - the event which udev sends out after rule processing
  KERNEL - the kernel uevent

  KERNEL[1195.829011] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  KERNEL[1195.834989] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1195.874055] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  KERNEL[1195.875019] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  KERNEL[1195.875183] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  KERNEL[1196.134164] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  KERNEL[1196.134448] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.158923] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.174559] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.194750] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  UDEV  [1196.196268] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  UDEV  [1196.197180] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  UDEV  [1196.224577] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  UDEV  [1196.231346] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)

  Note how there's no «(rc)» displayed on any of the lines, which means
  that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
  the above events.

  I found a rule that works at https://www.mail-archive.com/linux-
  me...@vger.kernel.org/msg117165.html:

  ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
  ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg
  -s $env{.rc_sysdev}"

  Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file
  containing this rule solves the problem; now my custom keymap is
  loaded at boot, as it did before (when I was running Bionic).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec  6 18:05:06 2020
  SourcePackage: v4l-utils
  UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+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 1907317] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: tex-common (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Expired

Bug description:
  edubuntu 14.20 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-194.226-generic 4.4.236
  Uname: Linux 4.4.0-194-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.27
  Architecture: amd64
  Date: Wed Dec  9 01:36:34 2020
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2010-12-08 (3653 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32ubuntu0.1
  SourcePackage: tex-common
  Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-03-03 (646 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1907317/+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 1907798] Re: Crash during do-release-upgrade

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Crash during do-release-upgrade

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  While doing a do-release upgrade from 18.04 to 20.04, I got an error.
  The script wanted to install the Chromium snap and apparently while
  doing that, it failed.

  Original summary generated by Launchpad:

  package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18
  Uname: Linux 4.15.0-126-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: connected
   edid-base64: 
   modes: 1024x768 800x600 800x600 848x480 640x480
  Date: Fri Dec 11 11:37:46 2020
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-03 (1103 days ago)
  InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InstalledPlugins:
   
  Load-Avg-1min: 0.65
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-126-generic 
root=UUID=480b8792-a570-441d-b8c6-27b031b55c17 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago)
  dmi.bios.date: 01/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: FM2A88M Pro3+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd01/11/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MPro3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1907798/+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 1907975] Re: [snap] Al eliminar archivos no van a la papelera del sistema

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [snap] Al eliminar archivos no van a la papelera del sistema

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  --español--
  A eliminar archivos desde la interfaz de descarga, los archivos no terminan 
en la papelera del sistema. En vez de esto los archivos se ubican en 
/home//snap/chromium//.local/share/Trash/files

  --english translate--
  To delete files from the download interface, the files do not end up in the 
system trash. Instead the files are located in
  /home//snap/chromium//.local/share/Trash/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1907975/+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 1907965] Re: Orca only read desktop with numeric keypad and not read desktop with arrows. Orca read afew applications downloaded from the web and ubuntu software

[Launchpad Bug Tracker]

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

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

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

Title:
  Orca only read desktop with numeric keypad and not read desktop with
  arrows. Orca read afew applications downloaded from the web and ubuntu
  software

Status in orca package in Ubuntu:
  Expired

Bug description:
  Ubuntu 20.04.1, Orca version 3.36.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: orca 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 13 14:53:28 2020
  InstallationDate: Installed on 2020-11-15 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: orca
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1907965/+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 1915584] Re: Info documentation package does not contain Info documentation for Info package

[cheater]

For a workaround, you can do the following:

sudo wget -O /usr/share/info/info-stnd.info.gz
http://www.gnu.org/software/texinfo/manual/info-stnd/info-
stnd.info.tar.gz

note that the output file does not have the "tar" segment.

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

Title:
  Info documentation package does not contain Info documentation for
  Info package

Status in texinfo package in Ubuntu:
  New

Bug description:
  the command "info info" should show the Info documentation for the
  info program. It doesn't, instead reporting the following issue:

  "info: No menu item 'info-stnd' in node '(dir)Top'"

  
  This is because the file /usr/share/info/info-stnd.info.gz does not come 
included in the package in 18.04.

  However, it does get included in the "info" package in 20.04.

  Therefore, please backport this change from 20.04.

  A related bug is present here, first reported in 2007:

  https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/95245

  Hoping for a quick backport. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: info 6.5.0.dfsg.1-2
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 04:59:07 2021
  InstallationDate: Installed on 2018-09-24 (872 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1915584/+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 1915584] [NEW] Info documentation package does not contain Info documentation for Info package

[cheater]

Public bug reported:

the command "info info" should show the Info documentation for the info
program. It doesn't, instead reporting the following issue:

"info: No menu item 'info-stnd' in node '(dir)Top'"


This is because the file /usr/share/info/info-stnd.info.gz does not come 
included in the package in 18.04.

However, it does get included in the "info" package in 20.04.

Therefore, please backport this change from 20.04.

A related bug is present here, first reported in 2007:

https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/95245

Hoping for a quick backport. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: info 6.5.0.dfsg.1-2
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 13 04:59:07 2021
InstallationDate: Installed on 2018-09-24 (872 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: texinfo
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Info documentation package does not contain Info documentation for
  Info package

Status in texinfo package in Ubuntu:
  New

Bug description:
  the command "info info" should show the Info documentation for the
  info program. It doesn't, instead reporting the following issue:

  "info: No menu item 'info-stnd' in node '(dir)Top'"

  
  This is because the file /usr/share/info/info-stnd.info.gz does not come 
included in the package in 18.04.

  However, it does get included in the "info" package in 20.04.

  Therefore, please backport this change from 20.04.

  A related bug is present here, first reported in 2007:

  https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/95245

  Hoping for a quick backport. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: info 6.5.0.dfsg.1-2
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 04:59:07 2021
  InstallationDate: Installed on 2018-09-24 (872 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1915584/+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 1914147]

[Ryanvm]

Comment on attachment 9197123
Bug 1679933 - Call EnsureNSSInitializedChromeOrContent() during nsHttpHandler 
initialization

Low-risk fix for a longstanding issue which can cause startup freezes in
some situations. Approved for 78.8esr.

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Ryanvm]

https://hg.mozilla.org/releases/mozilla-esr78/rev/54a6f821bf52

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Bugzilla-mozilla-0]

*** Bug 1691118 has been marked as a duplicate of this bug. ***

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Catalin-sasca-z]

Tried again reproducing this issue (following some leads from Bug
1689032 as well) in order to verify this on Firefox 85.0.2 and on ESR,
but had no luck.

Tried creating dirty profiles (adding addons, cache from websites, etc),
installing and uninstalling the browser, updating it over and over from
84.0.2 to 85.0.1, and we couldn't encounter any freezes. Tests were
performed on macOS 11.2, Ubuntu 20.04 and Windows 10.

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Kershaw-6]

Comment on attachment 9197123
Bug 1679933 - Call EnsureNSSInitializedChromeOrContent() during nsHttpHandler 
initialization

### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR 
consideration**: Firefox could freeze on start up.
* **User impact if declined**: Firefox could freeze on start up.
* **Fix Landed on Version**: 86
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: The patch 
is already verified on 86.
* **String or UUID changes made by this patch**: N/A

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Kershaw-6]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #27)
> Is this worth taking on ESR78 to be safe?

OK, let's uplift this to ESR78 for safe.

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Ryanvm]

Is this worth taking on ESR78 to be safe?

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Julien Cristau]

Comment on attachment 9197123
Bug 1679933 - Call EnsureNSSInitializedChromeOrContent() during nsHttpHandler 
initialization

fixing a deadlock on startup, approved for 85.0.2

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147]

[Julien Cristau]

https://hg.mozilla.org/releases/mozilla-release/rev/f48eab99cc33

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

Title:
  [upstream] Firefox 85 hangs at startup

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Today I have received a security upgrade for kubuntu 20.04 including
  firefox 85. Unfortunately, this version of firefox appears to hang at
  start unless it is started passing an url. Namely:

  firefox

  hangs, while

  firefox lwn.net

  does not hang.

  I have quickly tried working with a clean profile and firefox 85 seems
  to start fine with that. Yet, the profile is not broken: if I
  downgrade to firefox 84 and restore my profile from a backup, then
  firefox 84 works just fine.

  So the issue seems to be that firefox 85 has issues in working with
  profiles that are totally fine with firefox 84. This breaks migration
  from firefox 84 to firefox 85.

  Issue is totally reproducible:

  downgrade to firefox 84
  restore profile from firefox 84 from backup
  work with firefox 84 (OK)
  upgrade to firefox 85
  try to work with firefox 85 (KO)

  Please consider that having to reset a profile is a form of data loss.
  In a modern browser, the profile includes extensions, passwords, data
  from web apps and more.

  Because this bug makes it impossible to apply a security update
  (firefox 85 is marked as such and shipped via the security channel),
  this bug is particularly serious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   1454 F pulseaudio
  BuildID: 20210105180113
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Feb  2 00:52:23 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-02-16 (351 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.10.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1914147/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[walkerstreet]

I just read about the correct way to report a bug or fix to the gnulib 
developers. I have emailed them as below:
Date: Sat, 13 Feb 2021 at 12:40
Subject: Suggested fix to mountlist.c: Define fuse.portal, devtmpfs and 
squashfs mounts as dummy
To: bug-gnu...@gnu.org
Cc: juli...@ubuntu.com
Hi gnulib developers,
At present many gnulib users encounter this error:
Running 'df' as user (not root) causes results in output that includes
this error message:
"df: /run/user/1000/doc: Operation not permitted"
I would like to pass on to you a suggested fix:

@@ -164,7 +164,10 @@
 #define ME_DUMMY_0(Fs_name, Fs_type)\
   (strcmp (Fs_type, "autofs") == 0  \
+   || strcmp (Fs_type, "devtmpfs") == 0 \
+   || strcmp (Fs_type, "fuse.portal") == 0  \
|| strcmp (Fs_type, "proc") == 0 \
+   || strcmp (Fs_type, "squashfs") == 0 \
|| strcmp (Fs_type, "subfs") == 0\
/* for Linux 2.6/3.x */  \
|| strcmp (Fs_type, "debugfs") == 0  \

Julian Klode, from Ubuntu, deserves credit for this suggested fix. He
published a patch that has been included in the Ubuntu Hirsute 21.04
package: coreutils 8.32-4ubuntu2. See

https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/19056232.

https://launchpadlibrarian.net/510003931/coreutils_8.32-4ubuntu1_8.32-4ubuntu2.diff.gz
I have cc'ed Julian in this email.
The patch addresses a problem that particularly affects gnulib users
with fuse.portal mounts, such as users who have installed Flatpak.
This is a significant problem for users who depend on df not returning
an error exit code in their scripts. Julian's bug report said:
"/run/user/1000/doc is a fuse.portal mount point, but statfs() return
EPERM, hence df produces an error message. Maybe statfs() is not
implemented, but it would be good to quieten this down (df even does
not allow me to ignore it, probably because it looks at statfs to find
out fs type, so my fs type ignoring doesn't work)."
This problem has also been reported on Fedora 32 here:
flatpak/xdg-desktop-portal#512
Kind regards,
Daniel

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

Title:
  df: /run/user/1000/doc: Operation not permitted

Status in coreutils package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[walkerstreet]

I formatted it as follows:
@@ -164,7 +164,10 @@
 #define ME_DUMMY_0(Fs_name, Fs_type) \
   (strcmp (Fs_type, "autofs") == 0 \
+ || strcmp (Fs_type, "devtmpfs") == 0 \
+ || strcmp (Fs_type, "fuse.portal") == 0 \
  || strcmp (Fs_type, "proc") == 0 \
+ || strcmp (Fs_type, "squashfs") == 0 \
  || strcmp (Fs_type, "subfs") == 0 \
  /* for Linux 2.6/3.x */ \
  || strcmp (Fs_type, "debugfs") == 0 \

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

Title:
  df: /run/user/1000/doc: Operation not permitted

Status in coreutils package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[walkerstreet]

Hi Julian and Kamil,
I tried to notify the gnulib upstream developers of this fix by creating a pull 
request in the github mirror (https://github.com/coreutils/gnulib/pull/11).  I 
don't know how to create a pull request in the original git repository 
(git://git.sv.gnu.org/gnulib.git).  I'm still learning.  I hope that the 
developers are able to see my pull request, even though it is in the github 
mirror, not the original repository.
All the best,
Daniel

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

Title:
  df: /run/user/1000/doc: Operation not permitted

Status in coreutils package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1915191] Re: ping utility displays wrong IPv4 address upon receiving ICMP Redirect

[Launchpad Bug Tracker]

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

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

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

Title:
  ping utility displays wrong IPv4 address upon receiving ICMP Redirect

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  * Observed behaviour *
  We ping a host, say 137.226.39.170. While doing so, the router redirects us 
to 137.226.42.42. (We verify, with Wireshark and taking a close look at RFC 
792, that our redirect packet is formatted correctly on-wire.) We see the 
following output of the ping utility:

  64 bytes from 137.226.39.170: icmp_seq=46 ttl=251 time=0.619 ms
  64 bytes from 137.226.39.170: icmp_seq=47 ttl=251 time=0.676 ms
  64 bytes from 137.226.39.170: icmp_seq=48 ttl=251 time=1.92 ms
  From 134.130.3.3 icmp_seq=47 Redirect Host(New nexthop: 42.42.226.137)
  64 bytes from 137.226.39.170: icmp_seq=49 ttl=251 time=4.79 ms

  The gateway address, as RFC 792 calls it, is displayed the wrong way
  around. Feels like an Endianness bug right from the start.

  
  * Expected behaviour *
  ping utility should display the gateway address correctly. ("New nexthop: 
137.226.42.42")

  
  * Inspection of source code; bug theory of operation *
  iputils_20190709.orig.tar.xz --> iputils-20190709/ping.c

  Bug happens in the function pr_icmph(). This gets called from one of
  three different places (lines 899, 1075, and 1101 of ping.c), and only
  in one case, the fourth parameter is set to NULL (when called from
  line 899).

  The third parameter ("info") of pr_icmph() is generally meant to be
  understood in host byte order. This can be seen in several places
  (lines 1185, 1284).

  Well, but in one place, this fact is ignored and the content of this
  third parameter, being in host byte order, gets copied into a
  structure that, by definition, is supposed to contain that piece of
  information in network byte order, which constitutes the bug.

  lines 1250 etc:
  {
  struct sockaddr_in sin = {
  .sin_family = AF_INET,
  .sin_addr =  {
  icp ? icp->un.gateway : info
  }
  };

  printf(_("(New nexthop: %s)\n"), pr_addr(, sizeof sin));
  }

  In the first alternative of the ternary operator, icp->un.gateway is
  in network byte order, and the value s_addr within struct in_addr that
  it gets copied to is also in network byte order, so everything's
  beautiful. But in the second alternative of the ternary operator, i.e.
  if icp (parameter number four of pr_icmph) happens to be NULL, as
  happens when pr_icmph() gets called from line 899, unfortunately the
  value of "info" (in host byte order) gets copied into s_addr, and bad
  things happen.

  
  * Bugfix patch *

  --- ping.c2019-07-09 22:55:49.0 +0200
  +++ ping_fixed.c  2021-02-09 20:08:18.724747594 +0100
  @@ -1251,7 +1251,7 @@
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr =  {
  - icp ? icp->un.gateway : info
  + icp ? icp->un.gateway : htonl(info)
}
};

  Simply converts the contents of info (which is in h_ost byte order) to
  n_etwork byte order, and everything's fine.

  Tried it, and this reliably fixes the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: iputils-ping 3:20190709-3
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Feb  9 19:33:57 2021
  InstallationDate: Installed on 2015-12-09 (1889 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: iputils
  UpgradeStatus: Upgraded to focal on 2020-12-28 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1915191/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Olivier Tilloy]

** Changed in: tinyjsd (Ubuntu Bionic)
   Status: New => 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/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  Invalid
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 1866059] Re: firefox-locale-* packages do not enable localization => post-install localization is not complete

[Robie Basak]

Hello Paride, or anyone else affected,

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

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

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

Title:
  firefox-locale-* packages do not enable localization => post-install
  localization is not complete

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  On 2020-03-03 I installed a Focal system from the latest ISO image and
  chose the Italian localization at install time. The localization
  setting worked as expected, but not for Firefox: its interface is
  still in English. No "Italian" option shows up in the 'Preferences ->
  Language' menu (the menu is empty).

  The firefox-locale-it package is correctly installed. I tried
  installing firefox-locale-fr and restart Firefox, but I still got no
  French option in the Language menu.

  On the other hand letting Firefox download the language pack itself
  *does* work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866059/+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 1878292] Re: firefox FTBFS on s390x

[Robie Basak]

Hello Olivier, or anyone else affected,

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

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

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

Title:
  firefox FTBFS on s390x

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Builds hang when trying to compile the third-party sqlite3 copy,
  during 7+ hours, before being killed. See e.g.
  
https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095:

  436:55.58 make[6]: *** 
[/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed
  436:55.59 make[6]: Leaving directory 
'/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src'
  436:55.59 make[5]: *** 
[/<>/firefox-76.0.1+build1/config/recurse.mk:74: 
third_party/sqlite3/src/target-objects] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+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 1895643] Please test proposed package

[Robie Basak]

Hello Timo, or anyone else affected,

Accepted thunderbird into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thunderbird/1:78.7.1+build1-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 thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  New
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 1895643] Please test proposed package

[Robie Basak]

Hello Timo, or anyone else affected,

Accepted jsunit into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/jsunit/0.2.2-2ubuntu1
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: tinyjsd (Ubuntu)
   Status: New => Invalid

** Changed in: jsunit (Ubuntu)
   Status: New => 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/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  New
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 1895643] Please test proposed package

[Robie Basak]

Hello Timo, or anyone else affected,

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

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

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

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

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

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

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

** Changed in: tinyjsd (Ubuntu Groovy)
   Status: New => Invalid

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

** Changed in: jsunit (Ubuntu Groovy)
   Status: New => Invalid

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

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  New
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Robie Basak]

Hello Timo, or anyone else affected,

Accepted thunderbird into groovy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/thunderbird/1:78.7.1+build1-0ubuntu0.20.10.4
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: thunderbird (Ubuntu Groovy)
   Status: Fix Released => Fix Committed

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

** Tags added: verification-needed-focal

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in jsunit package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in tinyjsd package in Ubuntu:
  Invalid
Status in jsunit source package in Bionic:
  New
Status in thunderbird source package in Bionic:
  Triaged
Status in tinyjsd source package in Bionic:
  New
Status in jsunit source package in Focal:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Committed
Status in tinyjsd source package in Focal:
  Fix Committed
Status in jsunit source package in Groovy:
  Invalid
Status in thunderbird source package in Groovy:
  Fix Committed
Status in tinyjsd source package in Groovy:
  Invalid

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jsunit/+bug/1895643/+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 1915570] [NEW] Login screen password entry not working

[Sebastian Horatio Stillion]

Public bug reported:

This bug is for the login package. This only affects users of the
development release and does not affect stable users. The bug in the
password entry causes either the password to be entered only for the
login to hang, or when attempting to enter the password, the computer
quickly deletes any characters entered as if backspace was being held
therefore preventing a user from being able to log in.

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


** Tags: hirsute

** Description changed:

- This bug is for
+ This bug is for the login package. This only affects users of the
+ development release and does not affect stable users. The bug in the
+ password entry causes either the password to be entered only for the
+ login to hang, or when attempting to enter the password, the computer
+ quickly deletes any characters entered as if backspace was being held
+ therefore preventing a user from being able to log in.

** Tags added: hirsute

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

Title:
  Login screen password entry not working

Status in gdm3 package in Ubuntu:
  New

Bug description:
  This bug is for the login package. This only affects users of the
  development release and does not affect stable users. The bug in the
  password entry causes either the password to be entered only for the
  login to hang, or when attempting to enter the password, the computer
  quickly deletes any characters entered as if backspace was being held
  therefore preventing a user from being able to log in.

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

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

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

[albertoiNET]

@Maton Danko pressing down on right is a secondary click. About
multitouch I don't know any multigestures touch app. I'll try to find
any app.

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

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

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

Bug description:
  Update (based on #296)
  =

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

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

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

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

  Original bug report
  ===

  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  

[Desktop-packages] [Bug 1915565] [NEW] screen fades for about 10 seconds glslideshowthen returns to normal

[WILLIAM HARRIS]

Public bug reported:

The fading happens online at . But it also happens offline in games.
Using Ubuntu 20.04
Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb 12 13:14:56 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed
 bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed
 nvidia, 390.141, 5.4.0-64-generic, x86_64: installed
 nvidia, 390.141, 5.4.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c]
InstallationDate: Installed on 2017-04-14 (1400 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch 
EXC3000-0367-44.01.00
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 820C
dmi.board.vendor: HP
dmi.board.version: 82.29
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: X0S49UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sat Oct 17 14:45:19 2020
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2.4

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  screen fades for about 10 seconds glslideshowthen returns to normal

Status in xorg package in Ubuntu:
  New

Bug description:
  The fading happens online at . But it also happens offline in 
games.
  Using Ubuntu 20.04
  Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 12 13:14:56 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed
   bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-64-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA 

[Desktop-packages] [Bug 1915562] [NEW] Libreoffice not loading installed fonts

[Danilo Alculete]

Public bug reported:

I've downloaded news fonts to be used on LibreOffice when I try to use
them, the fonts are not loading

ProblemType: Bug
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 12 22:58:17 2021
InstallationDate: Installed on 2020-10-15 (120 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Snap: libreoffice 7.0.4.2 (latest/stable)
SnapSource: ubuntu/+source/libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal snap

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

Title:
  Libreoffice not loading installed fonts

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I've downloaded news fonts to be used on LibreOffice when I try to use
  them, the fonts are not loading

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 22:58:17 2021
  InstallationDate: Installed on 2020-10-15 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Snap: libreoffice 7.0.4.2 (latest/stable)
  SnapSource: ubuntu/+source/libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915562/+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]

[Matt]

Just got this for the first time, 20.10. The cancel button reacts to
click but does not dismiss. Looks shady so I'm not going to try my
password. xkill has no effect. I see it's been nearly two years now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1895721] Re: Wayland not allowing Fractional Scaling to be set

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Wayland not allowing Fractional Scaling to be set

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

Bug description:
  Setting Fractional Scaling in the X11 Gnome Session is working fine. I
  can set the 3000x2000 screen to 150%.

  In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't
  stick, and I don't see any fractional scaling percentage options show
  up.

  (Running a slightly customized 5.9-rc5 kernel to get backlight
  working, but otherwise everything is pretty ordinary for some values
  of ordinary.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.37.91-1ubuntu1
  Uname: Linux 5.9.0-rc5-dpcdon x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 15 13:40:08 2020
  InstallationDate: Installed on 2020-08-24 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1895721/+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 1895721] Re: Wayland not allowing Fractional Scaling to be set

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Wayland not allowing Fractional Scaling to be set

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

Bug description:
  Setting Fractional Scaling in the X11 Gnome Session is working fine. I
  can set the 3000x2000 screen to 150%.

  In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't
  stick, and I don't see any fractional scaling percentage options show
  up.

  (Running a slightly customized 5.9-rc5 kernel to get backlight
  working, but otherwise everything is pretty ordinary for some values
  of ordinary.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.37.91-1ubuntu1
  Uname: Linux 5.9.0-rc5-dpcdon x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 15 13:40:08 2020
  InstallationDate: Installed on 2020-08-24 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1895721/+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 1915553] [NEW] add-apt-repository won't remove ppa if ppa has been deleted

[Dan Streetman]

Public bug reported:

If a ppa is added to the system, and then the ppa is deleted, add-apt-
repository fails to remove it, e.g.:

$ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository
ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if 
private)

the script should remove the source.list entry, which can be calculated
even if the ppa doesn't exist anymore.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  add-apt-repository won't remove ppa if ppa has been deleted

Status in software-properties package in Ubuntu:
  New

Bug description:
  If a ppa is added to the system, and then the ppa is deleted, add-apt-
  repository fails to remove it, e.g.:

  $ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository
  ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if 
private)

  the script should remove the source.list entry, which can be
  calculated even if the ppa doesn't exist anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1915553/+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 1796187] Re: [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => In Progress

-- 
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:
  In Progress
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 10883]

[Infofrommozilla]

*** Bug 1692335 has been marked as a duplicate of this bug. ***

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

Title:
  Stuck in proportional font mode

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

Bug description:
  If you start a message in HTML mode, choosing Options->Format->Plain Text Only
  switches to plain text mode but the compose window does not switch to a
  monospace font. Starting a message in plain text mode uses the correct font.

  https://bugzilla.mozilla.org/show_bug.cgi?id=216132:
  https://bugzilla.mozilla.org/show_bug.cgi?id=216132

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/10883/+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 10883]

[Infofrommozilla]

*** Bug 137884 has been marked as a duplicate of this bug. ***

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

Title:
  Stuck in proportional font mode

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

Bug description:
  If you start a message in HTML mode, choosing Options->Format->Plain Text Only
  switches to plain text mode but the compose window does not switch to a
  monospace font. Starting a message in plain text mode uses the correct font.

  https://bugzilla.mozilla.org/show_bug.cgi?id=216132:
  https://bugzilla.mozilla.org/show_bug.cgi?id=216132

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/10883/+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 1915529] Re: [SRU] Backport patches to focal

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~3v1n0/bamf/+git/bamf/+merge/398002

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

Title:
  [SRU] Backport patches to focal

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The BAMF daemon often crashes when updating/installing applications

  [Test Case]

   * As this is a racing event, it is not easy to reproduce but updating
  or installing applications can cause the crash

  [Where problems could occur]

   * The list of applications could suddenly be empty.

  [Other Info]

   * This commit in particular is fixing the racing issue
  
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0

  [ Regression potential ]

  Signals are not emitted properly causing windows / apps not being
  updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1915529/+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 1915529] Re: [SRU] Backport patches to focal

[Treviño]

** Description changed:

  [Impact]
  
-  * The BAMF daemon often crashes when updating/installing applications
+  * The BAMF daemon often crashes when updating/installing applications
  
  [Test Case]
  
-  * As this is a racing event, it is not easy to reproduce but updating
+  * As this is a racing event, it is not easy to reproduce but updating
  or installing applications can cause the crash
  
  [Where problems could occur]
  
-  * The list of applications could suddenly be empty.
+  * The list of applications could suddenly be empty.
  
  [Other Info]
-  
-  * This commit in particular is fixing the racing issue 
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0
+ 
+  * This commit in particular is fixing the racing issue
+ 
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0
+ 
+ [ Regression potential ]
+ 
+ Signals are not emitted properly causing windows / apps not being
+ updated

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

** Changed in: bamf (Ubuntu)
   Importance: Undecided => Medium

** Changed in: bamf (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  [SRU] Backport patches to focal

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The BAMF daemon often crashes when updating/installing applications

  [Test Case]

   * As this is a racing event, it is not easy to reproduce but updating
  or installing applications can cause the crash

  [Where problems could occur]

   * The list of applications could suddenly be empty.

  [Other Info]

   * This commit in particular is fixing the racing issue
  
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0

  [ Regression potential ]

  Signals are not emitted properly causing windows / apps not being
  updated

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

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

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

[Maton Danko]

@albertoiNet on that version, if you press the right bottom corner of
the touchpad does it do a primary or a secondary click? (it should do a
secondary bringing up the context menu). Also, did you tried 3/4 finger
gestures by any app? Because that also didn't work for me on another
version.

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

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

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

Bug description:
  Update (based on #296)
  =

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

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

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

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

  Original bug report
  ===

  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1915529] [NEW] [SRU] Backport patches to focal

[Corentin Noël]

Public bug reported:

[Impact]

 * The BAMF daemon often crashes when updating/installing applications

[Test Case]

 * As this is a racing event, it is not easy to reproduce but updating
or installing applications can cause the crash

[Where problems could occur]

 * The list of applications could suddenly be empty.

[Other Info]

 * This commit in particular is fixing the racing issue
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0

[ Regression potential ]

Signals are not emitted properly causing windows / apps not being
updated

** Affects: bamf (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Summary changed:

- SRU: Backport patches to focal
+ [SRU] Backport patches to focal

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

Title:
  [SRU] Backport patches to focal

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The BAMF daemon often crashes when updating/installing applications

  [Test Case]

   * As this is a racing event, it is not easy to reproduce but updating
  or installing applications can cause the crash

  [Where problems could occur]

   * The list of applications could suddenly be empty.

  [Other Info]

   * This commit in particular is fixing the racing issue
  
https://git.launchpad.net/bamf/commit/?id=312c9a29db2d4b33b96d4da71393f4a95f5e78a0

  [ Regression potential ]

  Signals are not emitted properly causing windows / apps not being
  updated

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

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

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

[albertoiNET]

Tested 5.11.0-051100rc7-generic and it works

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

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

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

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

Bug description:
  Update (based on #296)
  =

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

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

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

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

  Original bug report
  ===

  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: 

[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

[Andrej Shadura]

** Also affects: wpa (Debian)
   Importance: Undecided
   Status: New

** Changed in: wpa (Debian)
   Importance: Undecided => Wishlist

** Changed in: wpa (Debian)
   Status: New => Fix Released

** Changed in: wpa (Debian)
 Assignee: (unassigned) => Andrej Shadura (andrew.sh)

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Fix Committed
Status in wpa package in Debian:
  Fix Released

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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: Always update the initramfs when changing power profile

[Alberto Milone]

** Description changed:

- The different power profiles require loading the nvidia drivers with
- different options (or blacklisting them, in case of intel mode).
+ 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 call update-initramfs whenever we switch to a different
- profile, or things may fall out sync, resulting in a failure.
+ We need to make sure that the files in the initramfs are in sync with
+ the current user selection.
  
- The update-initramfs command takes a few seconds, therefore we also need
- to provide feedback, so that users know that they have to wait for the
- operation to complete. For this reason, prime-select will provide a
- spinner on the command line, and nvidia-settings will show a progress
- dialog.
+ 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.

** Summary changed:

- Always update the initramfs when changing power profile
+ SRU: Always update the initramfs when changing power profile

-- 
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:
  In Progress
Status in nvidia-settings source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

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 

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

[Nemanja V]

Recently I'm also experiencing this on:

Ubuntu 20.20 (Linux 5.8.0-41-generic)
AMD® A10-5750m apu with radeon(tm) hd graphics × 4

This is an older system indeed, but still...

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

Title:
  GPU lockup ring 0 stalled for more than X msec

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

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 [radeon]
do_vfs_ioctl+0xa9/0x640
? __schedule+0x2b0/0x670
ksys_ioctl+0x75/0x80
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x130
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
  ppa but that made no difference. It appears to be a bug in radeon.

  Nothing specific makes this happen, just regular usage with a
  compositing window manager. I'm not playing games or particularly
  exercising the GPU. The last two times I was just reading in web
  browser. It's also happened in the middle of the night while I was
  asleep. Sometimes I have a few days uptime, sometimes it happens in
  less than 24 hours from boot.

  This never happened before the radeon update mentioned on the first
  line.

  I'll attach two files of dmesg output. As per
  https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
  started apport for next time it happens.

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

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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/thunderbird/thunderbird.groovy

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Triaged
Status in thunderbird source package in Focal:
  Fix Committed
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1215882]

[Infofrommozilla]

*** Bug 1630283 has been marked as a duplicate of this bug. ***

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

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

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   

[Desktop-packages] [Bug 1215882]

[Infofrommozilla]

*** Bug 1630260 has been marked as a duplicate of this bug. ***

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

Title:
  Emails are silently discarded on 554 reply to STARTTLS

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

Bug description:
  It seems that emails are silently discarded when the remote SMTP
  server replies with an error on STARTTLS. Here is an example smtp log
  created with NSPR_LOG_MODULES='smtp:5,timestamp':

  2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to: 
mail.trialphaenergy.com
  2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220 
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013 
04:10:25 -0700
  2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 
14
  2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO 
[10.11.206.9]
  2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-mail.trialphaenergy.com Hello [10.11.10.19]
  2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-SIZE
  2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-PIPELINING
  2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-DSN
  2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-ENHANCEDSTATUSCODES
  2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-STARTTLS
  2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-AUTH NTLM
  2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-8BITMIME
  2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response: 
250-BINARYMIME
  2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250 
CHUNKING
  2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 
4
  2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
  2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
  2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554 
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
  2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 
19
  2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 
21
  2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
  2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0

  
  The UI, however, gives no indication of failure and closes the compose window 
after the apparent successful submission to the smtp server.

  
  If the user has not configured a Sent folder this results in data loss. Even 
if the user has configured a sent folder, he receives no indication that the 
email has not been sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikratio   2425 F pulseaudio
  BuildID: 20130803220711
  Channel: Unavailable
  Date: Fri Aug 23 13:05:30 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-30 (23 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   

[Desktop-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)

[Ika D'Amonds]

This truly feels like a significant downgrade when coming from any other
OS.

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

Title:
  Improve Save As Dialog Box (focus issues)

Status in One Hundred Papercuts:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  The save dialog box has the irritating habit of not focusing on the
  file name area once I have browsed to the location where I would like
  to save my document. This is done better in Windows.

  There are two main scenarios when saving a document where this
  behaviour annoys:

  Scanario 1 - Browsing to save location by double-clicking:  
  1. File -> Save As (to bring up the "Save" dialog box). 
  2. Double click on the folder in which you would like to save the document. 
  3. Notice that the focus is now in the folder list area, not on the file name 
area. 
  4. I now have to click in the file name area to be able to name my document. 

  In Windows, the focus is returned immediately to the file name box
  once a folder is double clicked, so the name can be typed and the
  document saved in one step.

  Scenario 2 - Browsing save location using the keyboard (find as you type):
  1. File -> Save As (to bring up the "Save" dialog box). 
  2. Click on the folder area so that folder names can be typed to find them. 
Hit enter to enter desired folder. 
  3. Within the folder, step 2 can be repeated for subfolders indefinitely. 
  4. Once the desired location has been reached, the user must use the mouse 
click in the file name area to name the file before saving. 

  In Windows, when using find as you type, although focus is retained by
  the folder area when entering a lower folder level (so that you can
  browse to another level using the keyboard if desired), jumping to the
  file name box is simply a matter of pressing tab ONCE. In Ubuntu, I
  have to reverse tab (shift-tab) around 10 times to get back to the
  file name box at the top of the screen, or use the mouse - most
  annoying.

  Solutions (copy the Windows behaviour): 
  1. If a folder is double clicked with the mouse, the focus should jump back 
to the file name box. 
  2. If a folder is entered into by pressing enter (on the keyboard), focus 
should remain in the folder area, but the file name box should only be a single 
tab away. 

  I understand that solution 2 is problematic in that tabbing would
  ordinarily jump to the next element (usually the "file type"
  dropdown), not back to the top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+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 1915481] Re: gnome crashes after running `apt upgrade`

[Walt Mankowski]

Thanks for replying so quickly. Unfortunately step 1 didn't show any
crash reports.

Step 2 doesn't show anything recent, but there were crashes on January 6
that might be relevant. They are:

gnome-control-center: 
https://errors.ubuntu.com/oops/28c05820-501b-11eb-9503-fa163e983629
gnome-shell: https://errors.ubuntu.com/oops/16d604a2-501b-11eb-8b96-fa163e6cac46

Just to be clear, is the workaround from step 3 simply "comment out line
23 from /etc/apport/crashdb.conf and reboot"? There are a lot of other
suggestion in that bug report and I wanted to doublecheck that that's
all I need to do.

As for reproducing the crash, it's probably impossible to exactly
reproduce it since it only happens when I'm running `apt upgrade` to
install new packages, and these particular new packages have already
been upgraded. The best I can do is make the change, reboot, and wait
for it to happen again with some new set of packages.

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

Title:
  gnome crashes after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+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 1915508] [NEW] reduced many features of desktop

[Aaryan Dwivedi]

Public bug reported:

removed all of my shortcuts, when i right click fewer options appear and
i cannot plug external mouse or keyboard and also i cannot multiselect
items.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 12 15:47:43 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:3184] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:398a]
InstallationDate: Installed on 2021-02-11 (0 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 174f:116a Syntek 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81D1
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=a1766085-d55f-4da8-a290-9b0a643db278 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 7XCN24WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55724 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN24WW:bd07/16/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
dmi.product.family: ideapad 330-15IGM
dmi.product.name: 81D1
dmi.product.sku: LENOVO_MT_81D1_BU_idea_FM_ideapad 330-15IGM
dmi.product.version: Lenovo ideapad 330-15IGM
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  reduced many features of desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  removed all of my shortcuts, when i right click fewer options appear
  and i cannot plug external mouse or keyboard and also i cannot
  multiselect items.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 15:47:43 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3184] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:398a]
  InstallationDate: Installed on 2021-02-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:116a Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81D1
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=a1766085-d55f-4da8-a290-9b0a643db278 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN24WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 

[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

[Nemanja V]

I'm sorry, I saw the "don't post errors for gnome-shell
3.38.2-1ubuntu1~20.10.1" message after I have already submitted my
comment.

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

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [ Impact ]

  Launching terminator crashes gnome-shell

  [ Test case ]

   - Launch terminator
   - GNOME Shell should not crash

  In any case these errors should not be reported anymore with gnome-shell 
3.38.2-1ubuntu1~20.10.1:
  - https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
  - https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605

  [ Regression potential ]

  A window could not be animated on size change.

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

[Nemanja V]

I'm experiencing this issue on gnome-shell 3.38.2-1ubuntu1~20.10.1.

Gnome crashes randomly, this time it happened while MS Teams video call
was running, and I tried to switch to Nautilus (file browser).

Extract from the syslog is attached.

** Attachment added: "Syslog extract"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897765/+attachment/5463197/+files/gnome-crash.txt

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

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [ Impact ]

  Launching terminator crashes gnome-shell

  [ Test case ]

   - Launch terminator
   - GNOME Shell should not crash

  In any case these errors should not be reported anymore with gnome-shell 
3.38.2-1ubuntu1~20.10.1:
  - https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
  - https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605

  [ Regression potential ]

  A window could not be animated on size change.

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+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 1898479] Re: Shotwell: Russian translation is invalid

[vofka]

fix released with 20.04.2

** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

** Changed in: shotwell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Shotwell: Russian translation is invalid

Status in Ubuntu Translations:
  Fix Released
Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  Shotwell 0.30.10-0ubuntu0.1 distributed in Ubuntu 20.04.1 has broken
  russian localization.

  In ru.po file all translated date templates are invalid, %е (russian
  letter "Е") is used instead of %e (english "E"). All dates in Shotwell
  are incorrectly spelled, like 'Пн %е января 2020'.

  The fix has been released upstream:
  https://gitlab.gnome.org/Teams/Translation/ru/-/issues/5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1898479/+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 1846180] Re: 1910 software-properties larger screen size

[vofka]

fix released with 20.04.2

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

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+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 1893563] Re: netplan: can't login to ap mode with psk

[Andrej Shadura]

Right, my apologies, I was too quick to be angry: I only checked the
patch proposed here but not the actual one committed — and apparently I
haven’t read the discussion to the end.

Having checked the actual package, I see it is in fact a patch from the
upstream Git.

Still, it’d be great if you could at least notify me, and it would be
much better if we could first push such changes into Debian first.

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

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1893563/+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

[Julien Olivier]

BTW: I found this bug report, but it's closed:
https://bugzilla.mozilla.org/show_bug.cgi?id=1438136

-- 
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 1915498] [NEW] Copy / paste in Firefox randomly broken

[Julien Olivier]

Public bug reported:

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.

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


** Tags: amd64 apport-bug groovy wayland-session

** Bug watch added: Mozilla Bugzilla #1438136
   https://bugzilla.mozilla.org/show_bug.cgi?id=1438136

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

[Desktop-packages] [Bug 1893563] Re: netplan: can't login to ap mode with psk

[Andrej Shadura]

I’ve just verified and in fact not only this hasn’t been submitted
upstream, but the upstream has shipped an alternative implementation of
this by Beniamino Galvani (@bengal).

I’d really appreciate if Ubuntu didn’t add non-trivial patches without
discussion with the upstream and me as the Debian maintainer for this
package.

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

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1915491] Re: Wifi adapter installed but can't be found in Settings

[Daniel van Vugt]

Next time the problem happens please try turning on wifi by pressing
Fn+PrtScr. If that doesn't fix it then please open a Terminal while the
problem is happening and run:

  rfkill > rfkill.txt

and attach the resulting text file here.


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

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

Title:
  Wifi adapter installed but can't be found in Settings

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

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+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 1915491] Re: Wifi Adpter Not found

[Daniel van Vugt]

Thanks for the bug report. I can see from your Lspci.txt that there
definitely is an Intel wifi card installed. So this looks like some kind
of GUI (or intermediate daemon) bug.

** Summary changed:

- Wifi Adpter Not found
+ Wifi adapter installed but can't be found in Settings

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

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

Title:
  Wifi adapter installed but can't be found in Settings

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

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+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 1893563] Re: netplan: can't login to ap mode with psk

[Andrej Shadura]

@seb128, @mhodson, @shemgp, has this patch been submitted to the
upstream?

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

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1915491] Re: Wifi Adpter Not found

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Wifi adapter installed but can't be found in Settings

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

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+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 1915491] [NEW] Wifi Adpter Not found

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

# Summary:
> ## Wifi Adpter Not found

## Steps to Reproduce:
- I don't know


## Expected Results:
Wifi should always be available

## Problem Description:
Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

* * *


Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 12 11:13:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Latitude E7470 [1028:06dc]
InstallationDate: Installed on 2021-01-06 (36 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Latitude E7470
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2018
dmi.bios.release: 1.20
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.20.3
dmi.board.name: 047I7V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
Wifi Adpter Not found
https://bugs.launchpad.net/bugs/1915491
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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