date:20200616

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

** Changed in: glib-networking (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Failed to load module: /usr/lib/x86_64-linux-
  gnu/gio/modules/libgiognutls.so

Status in glib-networking package in Ubuntu:
  Expired

Bug description:
  distro: xubuntu 18

  I'm trying to set up a google drive account on my pc and when I run
  the command "env XDG_CURRENT_DESKTOP=GNOME gnome-control-center" the
  following error occurs but opens the settings. When clicking on online
  accounts and trying to configure a google account, the error "TLS /
  SSL support not available; install glib-networking" occurs. I have
  glib-networking installed.

  pc:~$ env XDG_CURRENT_DESKTOP=GNOME gnome-control-center

  (gnome-control-center:13525): Clutter-WARNING **: 16:14:16.359: Whoever 
translated default:LTR did so wrongly.
  /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol 
gnutls_pkcs11_privkey_init, version GNUTLS_3_4 not defined in file 
libgnutls.so.30 with link time reference
  Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
  /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol 
gnutls_pkcs11_privkey_init, version GNUTLS_3_4 not defined in file 
libgnutls.so.30 with link time reference
  Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: glib-networking 2.55.90-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 23 08:03:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-13 (101 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: glib-networking
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1751248/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 -
1:19.1.0-1~18.04.1

---
xserver-xorg-video-ati-hwe-18.04 (1:19.1.0-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Thu, 21 May 2020 10:17:02 +0300

** Changed in: llvm-toolchain-10 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package llvm-toolchain-10 -
1:10.0.0-4ubuntu1~18.04.1

---
llvm-toolchain-10 (1:10.0.0-4ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Fri, 15 May 2020 13:05:47 +0300

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 -
19.1.0-1~18.04.1

---
xserver-xorg-video-amdgpu-hwe-18.04 (19.1.0-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Thu, 21 May 2020 10:16:59 +0300

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.8-2ubuntu2.1~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.8-2ubuntu2.1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)
  * control: Relax debhelper requirement.
  * control: Relax libepoxy-dev requirement, we don't need
EGL_MESA_query_driver on bionic.
  * rules: xdmx-tools isn't packaged, so don't try to skip it.

 -- Timo Aaltonen   Thu, 14 May 2020 22:05:06 +0300

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package libdrm - 2.4.101-2~18.04.1

---
libdrm (2.4.101-2~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.5 HWE stack update. (LP: #1876882)
  * control: Relax debhelper requirement.

 -- Timo Aaltonen   Mon, 11 May 2020 15:47:23 +0300

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

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

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

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

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.8-2ubuntu2.1~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.8-2ubuntu2.1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)
  * control: Relax debhelper requirement.
  * control: Relax libepoxy-dev requirement, we don't need
EGL_MESA_query_driver on bionic.
  * rules: xdmx-tools isn't packaged, so don't try to skip it.

 -- Timo Aaltonen   Thu, 14 May 2020 22:05:06 +0300

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3

** Also affects: simple-scan (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: simple-scan (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: simple-scan (Ubuntu Focal)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: simple-scan (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  New
Status in simple-scan source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+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 1881918] Re: Update GNOME Software to 3.36.1 in Focal

** Description changed:

- Please, consider updating the deb version of GNOME Software to 3.36.1 in
- Ubuntu 20.04. The 3.36.1 release has some important bug fixes,
- translation updates and other things.
+ [ Description ]
+ 
+ GNOME upstream have released a new stable version of gnome-software.
+ 
+ [ QA ]
+ 
+ GNOME has a micro release exception that covers this package.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ So we don't need to verify the fixes explicitly.
+ 
+ [ Regression Potential ]
+ 
+ Changes could cause issues in GNOME Software, which might make it hard
+ to install or remove software. Default store in Ubuntu is snap-store, so
+ this doesn't affect the majority of users.

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

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

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

** Changed in: gnome-software (Ubuntu Focal)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

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

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gnome-software.

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could cause issues in GNOME Software, which might make it hard
  to install or remove software. Default store in Ubuntu is snap-store,
  so this doesn't affect the majority of users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1881918/+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 1883819] Re: Update to 3.36.3

** Description changed:

+ [ Description ]
+ 
+ GNOME upstream have released a new stable version of simple-scan.
+ 
  Overview of changes in simple-scan 3.36.3
  
-   * Change the size of the paper to avoid visual glitches.
-   * Disable possibility of scanning if no device is found, to avoid 
unnecessary
- errors.
+   * Change the size of the paper to avoid visual glitches.
+   * Disable possibility of scanning if no device is found, to avoid 
unnecessary
+ errors.
  
  Overview of changes in simple-scan 3.36.2.1
  
-   * Revert the higher bit depth text scans changes - they aren't working with
- PDF saving.
+   * Revert the higher bit depth text scans changes - they aren't working with
+ PDF saving.
  
  Overview of changes in simple-scan 3.36.2
  
-   * Use higher bit depth on text scans.
-   * Fix size of first page on second scan.
-   * Don't interrupt scanning if the device is busy.
-   * Support saving files to FUSE file systems.
-   * Update known USB scanner IDs.
-   * Add initial Lexmark printers support.
-   * Add ADF duplex support for Brother DS-720.
-   * Fix setting source for Epson scanner.
+   * Use higher bit depth on text scans.
+   * Fix size of first page on second scan.
+   * Don't interrupt scanning if the device is busy.
+   * Support saving files to FUSE file systems.
+   * Update known USB scanner IDs.
+   * Add initial Lexmark printers support.
+   * Add ADF duplex support for Brother DS-720.
+   * Fix setting source for Epson scanner.
  
  Overview of changes in simple-scan 3.36.1
  
-   * Stop disabling compression to fix slow scanning
+   * Stop disabling compression to fix slow scanning
+ 
+ [ QA ]
+ 
+ GNOME has a micro release exception that covers this package.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ So we don't need to verify the fixes explicitly.
+ 
+ [ Regression Potential ]
+ 
+ Changes could break existing functionality. Issue would be confined to
+ simple-scan app.

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  New
Status in simple-scan source package in Focal:
  New

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+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 1879234] Re: Clicking Activities does nothing - screen appears to freeze

Please stop repeating the same message. And please respond only to the
above requests.

Please also be careful to not discuss the scrolling/zooming issue here.
That is bug 1883718.

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

Title:
  Clicking Activities does nothing - screen appears to freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Clicking Activities does nothing - screen appears to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879234/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson

Good. That discussion appears to be held above my head, so I'm going to
keep quiet there. All I can say is that I was able to reproduce the
issue in groovy.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883718] Re: zoom in/out problem

That's the wrong menu.

Please turn this option ON:   Always Show Universal Access Menu

and then access the menu via the Gnome Shell top bar.

Please also tap both your Ctrl keys to ensure neither is stuck.

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Thanks. Further comments on that topic are on that page.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883819] [NEW] Update to 3.36.3

Public bug reported:

Overview of changes in simple-scan 3.36.3

  * Change the size of the paper to avoid visual glitches.
  * Disable possibility of scanning if no device is found, to avoid unnecessary
errors.

Overview of changes in simple-scan 3.36.2.1

  * Revert the higher bit depth text scans changes - they aren't working with
PDF saving.

Overview of changes in simple-scan 3.36.2

  * Use higher bit depth on text scans.
  * Fix size of first page on second scan.
  * Don't interrupt scanning if the device is busy.
  * Support saving files to FUSE file systems.
  * Update known USB scanner IDs.
  * Add initial Lexmark printers support.
  * Add ADF duplex support for Brother DS-720.
  * Fix setting source for Epson scanner.

Overview of changes in simple-scan 3.36.1

  * Stop disabling compression to fix slow scanning

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Overview of changes in simple-scan 3.36.3

* Change the size of the paper to avoid visual glitches.
* Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

* Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

* Use higher bit depth on text scans.
* Fix size of first page on second scan.
* Don't interrupt scanning if the device is busy.
* Support saving files to FUSE file systems.
* Update known USB scanner IDs.
* Add initial Lexmark printers support.
* Add ADF duplex support for Brother DS-720.
* Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

* Stop disabling compression to fix slow scanning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+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 1883718] Re: zoom in/out problem

** Attachment added: "All option off but problem not resolve"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+attachment/5384596/+files/15923631113127154155332170384152.jpg

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #948
   https://gitlab.gnome.org/GNOME/mutter/-/issues/948

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883718] Re: zoom in/out problem

Please also go to: Settings > Universal Access and enable:

  Always Show Universal Access Menu

That will add a new menu to the top panel. Please look in that menu and
verify all the switches are off.

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1883718] Re: zoom in/out problem

It sounds like your keyboard Ctrl key is stuck down, which will cause
both the tabs problem and the zoom in/out problem.

Please tap the Ctrl keys on your keyboard several times in case one is
stuck. If that hasn't solved the issue then please also try briefly
unplugging the keyboard to see if your mouse then works properly in
Chrome.


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

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1879234] Re: Clicking Activities does nothing - screen appears to freeze

Okk but I've been going through this problem since I left Windows and came to 
Ubuntu Linux. My computer is not running smoothly. There are all kinds of 
problems. I can't think of anything to do. I'm very worried that you are not 
solving the problem properly.
#10 & #11 please I request you to watch the video and fix this problem because 
I have been going through this problem for a long time and I can't find any 
solution to this problem. No one can fix all the problems of system 
software.When I scroll an application after opening the computer, sometimes it 
is not working, then it is working in zoom in zoom out, for this I am not able 
to do any work well, sometimes the system automatically opens one new tab after 
another.

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

Title:
  Clicking Activities does nothing - screen appears to freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Clicking Activities does nothing - screen appears to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879234/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson

https://gitlab.gnome.org/GNOME/mutter/-/issues/948

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #948
   https://gitlab.gnome.org/GNOME/mutter/-/issues/948

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883779] Re: Hub-connected mouse doesn't work until suspend

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

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

Title:
  Hub-connected mouse doesn't work until suspend

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using a USB hub with 4 inputs, one of them is my mouse.

  The mouse doesn't react when I boot the computer into Linux, even if I
  re-plug it into the same or another slot in the hub. It works in
  Windows. It works when connected to a computer USB port.

  The mouse starts working through the hub after I suspend the computer
  then wake it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 21:57:02 2020
  DistUpgraded: 2020-04-26 18:49:17,342 DEBUG found components: {'focal': 
{'main', 'universe', 'multiverse', 'restricted'}, 'focal-updates': {'main', 
'universe', 'multiverse', 'restricted'}, 'focal-security': {'main', 'universe', 
'multiverse', 'restricted'}}
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 1.1, 5.4.0-33-generic, x86_64: installed
   88x2bu, 1.1, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2018-01-05 (893 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8acf1b56-9cb9-4afa-82c6-7f17663120be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-04-26 (51 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z97 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0801:bd04/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ97MARK2:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/linux/+bug/1883779/+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 1883718] Re: zoom in/out problem

** Attachment added: "Browse bug"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+attachment/5384595/+files/VID-20200615-WA0004.mp4

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1883718] Re: zoom in/out problem

I've been going through this problem since I left Windows and came to Ubuntu 
Linux. My computer is not running smoothly. There are all kinds of problems. I 
can't think of anything to do. I'm very worried that you are not solving the 
problem properly.
please I request you to watch the video and fix this problem because I have 
been going through this problem for a long time and I can't find any solution 
to this problem. No one can fix all the problems of system software.When I 
scroll an application after opening the computer, sometimes it is not working, 
then it is working in zoom in zoom out, for this I am not able to do any work 
well, sometimes the system automatically opens one new tab after another.

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1883092] Re: Gnome Shell freeze

Thanks for the attachments. Unfortunately I don't see any issue there.

If you mean literally the whole machine fails to boot for the next 30
minutes then it sounds like there's a hardware problem. So maybe a bug
report about the software is inappropriate. But in case that's not what
you mean, please next look for crashes which may be relevant:

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

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

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

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

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

Title:
  Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  the computer will freeze everything but mouse and fail to boot back up
  for around 30 minutes after

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 11 11:57:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2020-05-29 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 2325CJ0
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=84df2c1d-136c-448c-b0a6-8483339655b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325CJ0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2325CJ0:pvrThinkPadX230:rvnLENOVO:rn2325CJ0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325CJ0
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-shell/+bug/1883092/+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 1883718] Re: zoom in/out problem

I do not know how to make a compartment, but once you say that you
should be fixed in this way you should fix this thing that you can not
fix my Ubuntu, you can not be able to solve any problems just

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

I'm not aware of any regression. What is the bug ID for that?

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1879234] Re: Clicking Activities does nothing - screen appears to freeze

Please try moving your dock from the bottom of the screen to the left
side. Does that fix the Activities clicking problem?

Please also try hitting Windows+A on the keyboard. Does that do what you
want?

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

Title:
  Clicking Activities does nothing - screen appears to freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Clicking Activities does nothing - screen appears to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879234/+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 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors

When I last tested Nvidia multi-monitors I was unable to reproduce this
bug. So I'm not sure I can help any time soon.

Worse still, I am now unable to test any Nvidia multi-monitor issues
since my new monitors don't support (no DVI) my only Nvidia card that
runs the current Nvidia drivers :S

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

Title:
  [nvidia] Dual monitor setup with secondary monitor in portrait-right
  mode cause tiled windows to occupy 1.5 monitors

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

Bug description:
  I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted.

  I use dual screen : the main screen is on the left side (32"), the
  secondary screen (19") is at right and in portrait mode (rotated
  right). The window are improperly growed : they extend from full main
  screen to half the "witdh" of the secondary screen. Additionnally, the
  « pop-up » menus (eg. from settings) do not appear at the right place
  (see screen capture in comment). The problem disappears if I revert
  the orientation of secondary screen from « portrait turned right » to
  « landscape ». I do have gnome-shell-extension-ubuntu-dock in version
  67ubuntu20.04.5, but still got the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 11:11:25 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-19 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+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 1879234] Re: Clicking Activities does nothing - screen appears to freeze

Please be careful to only report one issue per bug. You can report many
separate bugs.

Please also remember to run the command from comment #5 and attach the
results.

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

Title:
  Clicking Activities does nothing - screen appears to freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Clicking Activities does nothing - screen appears to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879234/+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 1883813] [NEW] package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26 26.3~1.git96dd

2020-06-16 Thread Bradley Dowling

Public bug reported:

apt now unusable

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: emacs-gtk (not installed)
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 16 21:54:18 2020
ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is 
also in package emacs26 26.3~1.git96dd019-kk1+20.04
InstallationDate: Installed on 2020-06-10 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: emacs
Title: package emacs-gtk (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26 
26.3~1.git96dd019-kk1+20.04
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package emacs-gtk (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package
  emacs26 26.3~1.git96dd019-kk1+20.04

Status in emacs package in Ubuntu:
  New

Bug description:
  apt now unusable

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-gtk (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 21:54:18 2020
  ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is 
also in package emacs26 26.3~1.git96dd019-kk1+20.04
  InstallationDate: Installed on 2020-06-10 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: emacs
  Title: package emacs-gtk (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26 
26.3~1.git96dd019-kk1+20.04
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1883813/+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 1883718] Re: zoom in/out problem

Sorry I accidentally deleted one of the attachments. Please add it back
in if you can.

But it looks like the same video you provided earlier this week so
that's Chromium, not Xorg.

** Tags removed: patch

** Patch removed: "Bug 🐞"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384414/+files/VID-20200615-WA0004.mp4

** Package changed: xorg (Ubuntu) => chromium-browser (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/1883718

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+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 1883812] [NEW] package emacs-common (not installed) failed to install/upgrade: trying to overwrite '/usr/include/emacs-module.h', which is also in package emacs26-common 26.3~1

2020-06-16 Thread Bradley Dowling

Public bug reported:

An older version of emacs was among many packages from an --install-
suggests. I use a version from a PPA that supports vterm. Didn't want or
expect another version of emacs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: emacs-common (not installed)
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 16 21:54:17 2020
ErrorMessage: trying to overwrite '/usr/include/emacs-module.h', which is also 
in package emacs26-common 26.3~1.git96dd019-kk1+20.04
InstallationDate: Installed on 2020-06-10 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: emacs
Title: package emacs-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/emacs-module.h', which is also in package 
emacs26-common 26.3~1.git96dd019-kk1+20.04
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package emacs-common (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/emacs-module.h', which is also in package
  emacs26-common 26.3~1.git96dd019-kk1+20.04

Status in emacs package in Ubuntu:
  New

Bug description:
  An older version of emacs was among many packages from an --install-
  suggests. I use a version from a PPA that supports vterm. Didn't want
  or expect another version of emacs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 21:54:17 2020
  ErrorMessage: trying to overwrite '/usr/include/emacs-module.h', which is 
also in package emacs26-common 26.3~1.git96dd019-kk1+20.04
  InstallationDate: Installed on 2020-06-10 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: emacs
  Title: package emacs-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/emacs-module.h', which is also in package 
emacs26-common 26.3~1.git96dd019-kk1+20.04
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1883812/+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 873287] Re: [Upstream] Writer Picture Background No Fill does not persist saving to .doc

2020-06-16 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [Upstream] Writer Picture Background No Fill does not persist saving
  to .doc

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.4.3-3ubuntu2
Candidate: 1:3.4.3-3ubuntu2
Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status
   
  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287/+attachment/2540085/+files/problematic%20document.doc
  -O inf.doc && lowriter -nologo inf.doc

  select the picture at bottom right -> Format -> Picture -> Background
  tab -> No Fille -> OK -> Save as .doc -> Close -> Reopen and the No
  Fill persists.

  4) What happens is it does not.

  WORKAROUND: Save as .odt.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  Architecture: i386
  Date: Thu Oct 13 15:05:06 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:el:en
   LANG=el_GR.UTF-8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2020-06-16 Thread Justin Luth

OK - so I think this report is focusing on the three textboxes near the
middle of the document, where the first one is a bit left compared to
the others. The three are not lined up.left-aligned.

It appears to me that the reason is because the first one is wider than
the others - in fact it goes right to the edge of the paper. In Word the
textbox spills off the end of the page. So that would be the reason -
that LO makes the sane decision that content MUST fit on the paper.

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

Title:
  [Upstream] Rounded rectangle corners are indented importing Word .doc

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.4-0ubuntu1
    Candidate: 1:3.4.4-0ubuntu1
    Version table:
   *** 1:3.4.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

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

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611270/+files/Test%20case.doc
  -O testcase.doc && lowriter -nologo testcase.doc

  is the gray and white rounded rectangle corners look as they do in the
  Word screenshot
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611275/+files/Test%20case.jpg
  .

  4) What happens instead is the corners are indented in LO screenshot
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897235/+attachment/2611273/+files/Libreoffice.png
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Nov 28 14:49:44 2011
  ProcEnviron:
   LANGUAGE=pl_PL:pl:en_GB:en
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-10-18 (41 days ago)

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

2020-06-16 Thread Justin Luth

Fixed in LO 7.0 by commit 38e7e6f348df5d6b37d7e0051fd3b8c227db69e6
Author: Justin Luth on Tue Apr 14 17:39:36 2020 +0300

tdf#132094 doc: fix export of fill in wrap-through fly frames

This builds on commit 2f13dbac060ae6af7e25ad3eff675cc859cfb3ff
by Miklos Vajna on  Fri Jun 15 08:49:46 2012 +0100
n#325936 fix ww8 export of fly frames with transparent bg
where he wisely and cautiously says
Regression from commit ed8b5f2d -- to be safe, reverted only
for fly frames in headers.
because for some unknown reason, way back in 2002, commit
ed8b5f2debac216243930aba0873e0d75de8d0dd forced all
frames to specify a background fill. Typically of
course this is white, and so who notices?

Well, you notice if your frame is transparent, and
now the area fill hides something that it is over top of.
Like for example a transparent image, where the text wraps
through the image.

At first I was going to just try and revert everything.
Then I decided it likely was a difference between how
LO and MSO handled stacking/overlapping things.
After that, I was going to just make an exception for
eShapeType == mso_sptPictureFrame, but that only seems
necessary if there is something underneath. If the something
is just a background, that is handled anyway, so really
it would only be other shapes or (most importantly) text,
so the safest thing is testing wrap through, which there was
already a pre-defined variable to reuse
(and fix the spelling).

*** This bug has been marked as a duplicate of bug 132094 ***

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

Title:
  [Upstream] Writer Picture Background No Fill does not persist saving
  to .doc

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.4.3-3ubuntu2
Candidate: 1:3.4.3-3ubuntu2
Version table:
   *** 1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status
   
  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287/+attachment/2540085/+files/problematic%20document.doc
  -O inf.doc && lowriter -nologo inf.doc

  select the picture at bottom right -> Format -> Picture -> Background
  tab -> No Fille -> OK -> Save as .doc -> Close -> Reopen and the No
  Fill persists.

  4) What happens is it does not.

  WORKAROUND: Save as .odt.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  Architecture: i386
  Date: Thu Oct 13 15:05:06 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:el:en
   LANG=el_GR.UTF-8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2020-06-16 Thread Jan-Marek Glogowski

This is the typical chicken-egg problem: LO's SVG rasterizer / icons
broken => default to PNG. Everybody uses PNG (and some complain about
blocky icons in HiDPI) => nobody fixes the LO's SVG rasterizer / icons.
Some more background info is in bug 133877 comment 11.

And OTOH people can manually select an SVG icon set, so the pressure to
fix this isn't really high.

While the SVG icons easily look better when scaled, the PNG icons
definitely look better in 100% / non-scaled in Linux.

And it also doesn't help that gtk3 always scales the rasterized icons,
so you get the worse 100% SVG icons scaled to HiDPI.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1876882] Update Released

2020-06-16 Thread Chris Halse Rogers

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

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones

2020-06-16 Thread Hui Wang

For the issue of the default input device, we are working on it.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/295

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

Title:
  Dell Inspirion 5391: headphones work only if I manually switch source
  port every time and no different volume levels for speaker and
  headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu
  18.04, and it doesn't have such problems. But I have manually
  installed Xubuntu 20.04 LTS (firstly because I need full disk
  encryption with LUKS). And I have two problems the with sound system:

  1) If I plug headphones, there is no sound. Sound becomes only if I
  manually switch source port to "Headset Mono microphone" from
  "Headphones stereo microphone" in pavucontrol or with the command:

  pacmd set-source-port 4  "[In] Headset"

  or with ALSA:

  amixer set 'Input Source' 'Headset Mic'

  I have a workaround with /etc/acpi/events, but it is not seamless (I
  have an one second delay when I plug the headphones).

  2) There is no separate volume levels for speaker and headphone in
  pulseaudio.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tenikeev   3385 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jun  1 23:13:38 2020
  InstallationDate: Installed on 2020-05-28 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 07DM2C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5391
  dmi.product.sku: 096E
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881659/+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 1807600] Re: auctex preview doesn't work

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

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

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

Title:
  auctex preview doesn't work

Status in auctex package in Ubuntu:
  Confirmed

Bug description:
  Auctex is a package which allows in particular to preview formulas when 
typing Latex under Emacs.
  Under Ubuntu 18.04 LTS this is provided by package auctex. 
  But the previews don't appear.

  I have checked on auctex site that this is a known problem of the version of 
auctec used 
  in Ubuntu, version 11.91-1ubuntu1.

  So i have removed  the auctex package and installed instead the auctex package
  provided by elpa directly in my home. This one is based on a more recent 
version 12.1
  of auctex. Now previews work OK which confirms that the solution of the bug 
is to
  upgrade auctex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/auctex/+bug/1807600/+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 1883798] [NEW] package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is differe

2020-06-16 Thread spyam

Public bug reported:

not install file !!! packettracer

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjpeg-turbo8 2.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
 libjpeg-turbo8:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun 17 03:37:01 2020
DpkgTerminalLog:
 Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
 Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) 
...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
InstallationDate: Installed on 2020-06-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which 
is different from other instances of package libjpeg-turbo8:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libjpeg-
  turbo8/changelog.Debian.gz', which is different from other instances
  of package libjpeg-turbo8:amd64

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  not install file !!! packettracer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   libjpeg-turbo8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 03:37:01 2020
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
   Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over 
(2.0.3-0ubuntu1) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', 
which is different from other instances of package libjpeg-turbo8:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1853331] Re: nm-applet assertion failure manipulatng widgets

2020-06-16 Thread Raphael Mankin

I start from xfce4 with other odd apps added.

On Tue, 2020-06-16 at 19:16 +, Sebastien Bacher wrote:
> Thank you for your bug report. Is that still an issue? Which desktop
> environment do you use? (nm-applet isn't used by GNOME)
> 
> ** Changed in: network-manager-applet (Ubuntu)
>Importance: Undecided => Low
> 
> ** Changed in: network-manager-applet (Ubuntu)
>Status: Confirmed => Incomplete
>

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

Title:
  nm-applet assertion failure manipulatng widgets

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  nm-applet is logging a continuous stream of:

  
  Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent

  System updated on 19 Nov 2019

   lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Wed Nov 20 15:48:21 2019
  InstallationDate: Installed on 2018-11-06 (379 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 
   default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 
   192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 
192.168.178.24 metric 100 
   192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.14  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+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 1883744] Re: Numlock out of sync

2020-06-16 Thread tim

Need to correct 2 errors in my post:
 The vino-server version is 3.22.0
 The vino-server is stared up from the Startup applications deal after you log 
in not systemd.

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

Title:
  Numlock out of sync

Status in vino package in Ubuntu:
  New

Bug description:
  Using Remmina for vnc on Linux Mint 19.3 MATE (Based on Ubuntu 18.04)
  accessing several machines with vino-server (v 1.4.6) running also on
  Linux Mint 19.3 MATE. All machines boot up with Numlock on and vino-
  server running. However in order to use the numeric key pad for
  numbers on the remote machine I have to toggle the Numlock key on the
  Remmina machine. Then the numbers work on the remote machine but the
  local machine they are off. The symbols /, *, -, and . work fine.

  Any idea how to fix this? Vino-server is started by systemd at boot. I
  don't know what mechanism toggles the Numlock on at boot but could
  there be a timing problem?

  Is there a fixed setting in vino I can tell it what state to assume
  the Numlock is when vino-server is started?

  By the way when I use Remmina to access windows machines that are
  running UltraVNC the Numlock is synced correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1883744/+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 256373] Re: rhythmbox tag editing issue (back button in file property menu becomes inactive)

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

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

Title:
  rhythmbox tag editing issue (back button in file property menu becomes
  inactive)

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  Hello all,

  A strange behaviour of rhythmbox (version 0.11.5, german translation)
  occured on my laptop:

  I select a few music files to edit their properties. Right-clicking on one 
file brings up a menu from which I select 'properties'. Using the 'back' and 
'next' buttons I adjust artist, title, album etc.
  So far things are working fine.

  When I reach the end of the list of prior selected music files sometimes 
(rather seldom) the 'back' button turns to grey and becomes inactive. Strangely 
enough the 'next' button is still active even thought there is no next file in 
the selection.
  While the 'back'-button in the properties menu is 'out of order' I have the 
close that menu and manually choose another music file from the selection. This 
occures to be rather strange to me. There could be something going on with the 
GUI of the file property menu.

  If you need any further description or system output from my laptop
  please let me know. I am running Ubuntu 8.04 on an IBM T40 laptop.

  Kind regards, Tobias

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/256373/+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 1846785] Re: Crashes instantly on launch with Pentium J5005 Processor

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

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

Title:
  Crashes instantly on launch with Pentium J5005 Processor

Status in djview4 package in Ubuntu:
  Invalid
Status in djvulibre package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Invalid
Status in djvulibre source package in Bionic:
  Fix Released

Bug description:
  * Impact
  djvulibre segfaults on older i386 CPU

  * Test case
  try to open a djvu file in evince on an atom based machine

  * Regression potential
  check that djvu files are open fine on newer machines

  -

  [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.

  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

  and fixed in commit 8407dd, on the 7th of October 2018.

  From git tags, it is included in 3.5.27.1-11 (probably version xxx
  -10, though I cannot see this tag in git history)

  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)

  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.

  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.

  I suggest upgrading the version available for Bionic LTS as part of
  the development hardware stack long term support to 3.5.27.1-11.

  Yours sincerly,

  Milvi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djview4/+bug/1846785/+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 256373] Re: rhythmbox tag editing issue (back button in file property menu becomes inactive)

2020-06-16 Thread crvi

I think this is fixed in 3.4.3

Refer https://bugzilla.gnome.org/show_bug.cgi?id=789632

** Bug watch added: bugzilla.gnome.org/ #789632
   https://bugzilla.gnome.org/show_bug.cgi?id=789632

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

Title:
  rhythmbox tag editing issue (back button in file property menu becomes
  inactive)

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  Hello all,

  A strange behaviour of rhythmbox (version 0.11.5, german translation)
  occured on my laptop:

  I select a few music files to edit their properties. Right-clicking on one 
file brings up a menu from which I select 'properties'. Using the 'back' and 
'next' buttons I adjust artist, title, album etc.
  So far things are working fine.

  When I reach the end of the list of prior selected music files sometimes 
(rather seldom) the 'back' button turns to grey and becomes inactive. Strangely 
enough the 'next' button is still active even thought there is no next file in 
the selection.
  While the 'back'-button in the properties menu is 'out of order' I have the 
close that menu and manually choose another music file from the selection. This 
occures to be rather strange to me. There could be something going on with the 
GUI of the file property menu.

  If you need any further description or system output from my laptop
  please let me know. I am running Ubuntu 8.04 on an IBM T40 laptop.

  Kind regards, Tobias

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/256373/+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 1882258] Re: XRDP to Ubuntu 19.10 request many popup dialog for creating a colorprofile

2020-06-16 Thread AdlerHorst

> Could you describe what you are trying to do exactly to trigger those
errors? How did you configure xrdp? what server and client softwares do
you use?

Server-PC (ubuntu 19.10)
1.) apt get install xrdp
2.) Restart system

Client-PC (ubuntu 20.04)
3.) Install Remmina
4.) RDP to Server-PC
5.) RDP open but I got many color profile error

Server-PC
6.) researched Internet
7.) found solution from my post one
8.) got problems with grapphical login if an application request root access
9.) researched Internet (a long time)
10.) found solution #2 
11.) every thing works as expected.

I didn't changed xrdp or Remmina configuration

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

Title:
  XRDP to Ubuntu 19.10 request many popup dialog for creating a
  colorprofile

Status in policykit-1-gnome package in Ubuntu:
  Incomplete

Bug description:
  While searching abougt a solution I found this Blogpost which was able to 
help me in this case:
  https://c-nergy.be/blog/?p=12073

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1882258/+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 1876716] Re: Error transferring track: "could not open resource for writing" when copying tracks to library

2020-06-16 Thread crvi

1. Error transferring track: "could not open resource for writing"

This error is displayed if the imported ( copy mode ) song is already
available in Rhythmbox Music Library. So, if you import ( copy mode )
the same song more than once, this message will be displayed. The import
is aborted as a safety measure to avoid unintentionally overwriting your
files in the Music Library ( which might have better metadata tag /
album art than the copy source ). The error message displayed in the
dialog could be better and the UI dialog could offer a choice to "skip /
skip all / overwrite / overwrite all / cancel" to the user. You can open
a new issue on this at

https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/new

providing all necessary info.

2. The "error" mentioned in the initial bug description ( Import 4974
listed tracks ) is what I think is a hidden issue. I would guess that
there are duplicate songs / tracks in your iTunes library, which
Rhythmbox import code detects and fails. Try repeating the steps in the
initial bug description ( start from empty Rhythmbox Library ). Capture
the "rhythmbox.log" and attach it here.

Hint: Look for "Could not open resource for writing" string in the
rhythmbox.log. The song listed in the line above this error message is
the duplicate file which causes the import to fail.

3. The "crash" mentioned in the initial bug description is a different
bug tracked in:

https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1768

You can update it with your findings.

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1768
   https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1768

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

Title:
  Error transferring track: "could not open resource for writing" when
  copying tracks to library

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I tried adding my old iTunes music folder into my (empty) Rhythmbox
  library having the option 'Copy files that are outside the music
  library' checked. After clicking 'Import 4974 listed tracks'.

  Expected behaviour: 
  all files should've been copied to my Rhythmbox media folder.

  What happened instead: 
  the copy process got interupted with the following error: 

  Error transferring track: "could not open resource for writing"
  Only a few tracks where copied, I was able to press the button a few more 
times to copy a few more tracks, but then Rhythmbox crashed/closed and I had to 
restart it.

  
  I also tried it with just a few tracks. That worked, but the same error 
message came up when trying to copy tracks that were added to the library 
before.

  
  ---

  Description:  Zorin OS 15.2
  Release:  15

  rhythmbox:
Installed: 3.4.2-4ubuntu1
Candidate: 3.4.2-4ubuntu1
Version table:
   *** 3.4.2-4ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1876716/+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 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones

2020-06-16 Thread tim474

Yes. Headphones work with this version of Pulseaudio. Thank you. But
there is still a problem with volume level. If I plug and unplug
headphones, Speaker volume level drops to level of headphones, then I
can't separate set up volume level for headphones and speaker. But there
is no this problem with OEM version of Ubuntu.

And another problem. If I plug headphones with mic, set external mic as
input device (in pavucontrol), unplug and plug again, the default source
device is still internal mic. I want to set up automatic switching to
external mic if I plug it. As in previous case, there is not such
problem in OEM ubuntu.

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

Title:
Dell Inspirion 5391: headphones work only if I manually switch source
port every time and no different volume levels for speaker and
headphones

Status in pulseaudio package in Ubuntu:
New

Bug description:
I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu
18.04, and it doesn't have such problems. But I have manually
installed Xubuntu 20.04 LTS (firstly because I need full disk
encryption with LUKS). And I have two problems the with sound system:

1) If I plug headphones, there is no sound. Sound becomes only if I
manually switch source port to "Headset Mono microphone" from
"Headphones stereo microphone" in pavucontrol or with the command:

pacmd set-source-port 4 "[In] Headset"

or with ALSA:

amixer set 'Input Source' 'Headset Mic'

I have a workaround with /etc/acpi/events, but it is not seamless (I
have an one second delay when I plug the headphones).

2) There is no separate volume levels for speaker and headphone in
pulseaudio.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tenikeev 3385 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon Jun 1 23:13:38 2020
InstallationDate: Installed on 2020-05-28 (4 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 07DM2C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5391
dmi.product.sku: 096E
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881659/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-16 Thread Wesley Batista Santos

The comment #65 was what worked for me.

https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1840725/comments/65


My OS installation is Kubuntu 18.04.

Additional and more detailed info about my laptop:

```
$ uname -a
Linux ioku 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux


$ sudo dmidecode -t system
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.

Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20QDCTO1WW
Version: ThinkPad X1 Carbon 7th
Serial Number: PF1E44X3
UUID: 06E257CC-238A-11B2-A85C-ECF7951B56CA
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
Family: ThinkPad X1 Carbon 7th

Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options

Handle 0x0037, DMI type 15, 31 bytes
System Event Log
Area Length: 1586 bytes
Header Start Offset: 0x
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0062
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None


$ arecord -l
 List of CAPTURE Hardware Devices 
card 0: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 6: DMIC32 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 7: DMIC16 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

```

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1883783] Re: LibreOffice Help not available

2020-06-16 Thread Paul White

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

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

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1869561
   Libreoffice Help does not work

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

Title:
  LibreOffice Help not available

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When trying to get help in LibreOffice Writer it is unavailable.  See
  attachment for exact dialog.  I have uninstalled and reinstalled the
  package libreoffice-help-en-us and it doesn't change anything.  If I
  run /usr/lib/libreoffice/program/soffice.bin --writer on the command
  line no errors are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-help-en-us 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun 16 14:19:30 2020
  InstallationDate: Installed on 2020-04-23 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883783/+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 1883783] [NEW] LibreOffice Help not available

2020-06-16 Thread Scott Dunbar

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

Public bug reported:

When trying to get help in LibreOffice Writer it is unavailable.  See
attachment for exact dialog.  I have uninstalled and reinstalled the
package libreoffice-help-en-us and it doesn't change anything.  If I run
/usr/lib/libreoffice/program/soffice.bin --writer on the command line no
errors are shown.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-help-en-us 1:6.4.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Tue Jun 16 14:19:30 2020
InstallationDate: Installed on 2020-04-23 (53 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Dialog box error message"
   
https://bugs.launchpad.net/bugs/1883783/+attachment/5384528/+files/Screenshot%20from%202020-06-16%2014-26-26.png

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

Title:
  LibreOffice Help not available

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When trying to get help in LibreOffice Writer it is unavailable.  See
  attachment for exact dialog.  I have uninstalled and reinstalled the
  package libreoffice-help-en-us and it doesn't change anything.  If I
  run /usr/lib/libreoffice/program/soffice.bin --writer on the command
  line no errors are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-help-en-us 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun 16 14:19:30 2020
  InstallationDate: Installed on 2020-04-23 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883783/+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 1883781] [NEW] [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound

2020-06-16 Thread Rim

Public bug reported:

I have continuous noise / constant "shooting" instead of the audio and
video. I guess it appeared after the latest Ubuntu update. I cannot
watch any video, hear any sound in any program, only glitches,
shattering noise, and video freezing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  airim  1808 F pulseaudio
 /dev/snd/controlC0:  airim  1808 F pulseaudio
 /dev/snd/pcmC1D0p:   airim  1808 F...m pulseaudio
 /dev/snd/timer:  airim  1808 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 23:09:41 2020
InstallationDate: Installed on 2020-01-08 (160 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog: июн 16 23:06:40 airim dbus-daemon[1055]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=124 pid=1242 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, 
dropouts or crackling sound
UpgradeStatus: Upgraded to focal on 2020-04-25 (52 days ago)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ULTRA
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ULTRA
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have continuous noise / constant "shooting" instead of the audio and
  video. I guess it appeared after the latest Ubuntu update. I cannot
  watch any video, hear any sound in any program, only glitches,
  shattering noise, and video freezing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  airim  1808 F pulseaudio
   /dev/snd/controlC0:  airim  1808 F pulseaudio
   /dev/snd/pcmC1D0p:   airim  1808 F...m pulseaudio
   /dev/snd/timer:  airim  1808 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 23:09:41 2020
  InstallationDate: Installed on 2020-01-08 (160 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog: июн 16 23:06:40 airim dbus-daemon[1055]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=124 pid=1242 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] 
Underruns, dropouts or crackling sound
  UpgradeStatus: Upgraded to focal on 2020-04-25 (52 days ago)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technol

[Desktop-packages] [Bug 1883779] [NEW] Hub-connected mouse doesn't work until suspend

2020-06-16 Thread Wojciech Kaliciński

Public bug reported:

I'm using a USB hub with 4 inputs, one of them is my mouse.

The mouse doesn't react when I boot the computer into Linux, even if I
re-plug it into the same or another slot in the hub. It works in
Windows. It works when connected to a computer USB port.

The mouse starts working through the hub after I suspend the computer
then wake it up.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 21:57:02 2020
DistUpgraded: 2020-04-26 18:49:17,342 DEBUG found components: {'focal': 
{'main', 'universe', 'multiverse', 'restricted'}, 'focal-updates': {'main', 
'universe', 'multiverse', 'restricted'}, 'focal-security': {'main', 'universe', 
'multiverse', 'restricted'}}
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 88x2bu, 1.1, 5.4.0-33-generic, x86_64: installed
 88x2bu, 1.1, 5.4.0-37-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] 
[1462:3362]
InstallationDate: Installed on 2018-01-05 (893 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8acf1b56-9cb9-4afa-82c6-7f17663120be ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-04-26 (51 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z97 MARK 2
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr0801:bd04/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ97MARK2:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Hub-connected mouse doesn't work until suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using a USB hub with 4 inputs, one of them is my mouse.

  The mouse doesn't react when I boot the computer into Linux, even if I
  re-plug it into the same or another slot in the hub. It works in
  Windows. It works when connected to a computer USB port.

  The mouse starts working through the hub after I suspend the computer
  then wake it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate res

[Desktop-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301

Right, the debouncer doesn't seem ideal. I'm not convinced either by
upstream reply that forcing shutdown on another press is by design, imho
we should try to convince them that it is wrong

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately on Dell Vostro 5301

Status in OEM Priority Project:
  Incomplete
Status in gnome-session package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878351/+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 1876716] Re: Error transferring track: "could not open resource for writing" when copying tracks to library

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

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

Title:
  Error transferring track: "could not open resource for writing" when
  copying tracks to library

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I tried adding my old iTunes music folder into my (empty) Rhythmbox
  library having the option 'Copy files that are outside the music
  library' checked. After clicking 'Import 4974 listed tracks'.

  Expected behaviour: 
  all files should've been copied to my Rhythmbox media folder.

  What happened instead: 
  the copy process got interupted with the following error: 

  Error transferring track: "could not open resource for writing"
  Only a few tracks where copied, I was able to press the button a few more 
times to copy a few more tracks, but then Rhythmbox crashed/closed and I had to 
restart it.

  
  I also tried it with just a few tracks. That worked, but the same error 
message came up when trying to copy tracks that were added to the library 
before.

  
  ---

  Description:  Zorin OS 15.2
  Release:  15

  rhythmbox:
Installed: 3.4.2-4ubuntu1
Candidate: 3.4.2-4ubuntu1
Version table:
   *** 3.4.2-4ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1876716/+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 1853331] Re: nm-applet assertion failure manipulatng widgets

Thank you for your bug report. Is that still an issue? Which desktop
environment do you use? (nm-applet isn't used by GNOME)

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  nm-applet assertion failure manipulatng widgets

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  nm-applet is logging a continuous stream of:

  
  Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
  Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a 
parent

  System updated on 19 Nov 2019

   lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Wed Nov 20 15:48:21 2019
  InstallationDate: Installed on 2018-11-06 (379 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 
   default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 
   192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 
192.168.178.24 metric 100 
   192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.14  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+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 1849977] Re: account not recognized in ubuntu software

Could you also add the 'journalctl -b 0' log after getting the issue?

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

Title:
  account not recognized in ubuntu software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  it says wrong e-mail address or password when I try to log in ubuntu
  software

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1849977/+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 1849977] Re: account not recognized in ubuntu software

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

  apport-collect 1849977

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

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

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

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

Title:
  account not recognized in ubuntu software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  it says wrong e-mail address or password when I try to log in ubuntu
  software

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1849977/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

Hello Claire, or anyone else affected,

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

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

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

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

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

** Changed in: wpa (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Committed
Status in wpa source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT),
 also called fast roaming) if it either supports SME or the
 NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites,
 wpa_supplicant currently doesn't take into account whether or not either
 of those conditions are met. This can cause association failures, e.g.,
 when an AP supports both WPA-EAP and FT-EAP but the driver doesn't
 support FT (wpa_supplicant will decide to do FT-EAP since it is unaware
 the driver doesn't support it).

   * This is known to affect users at least users with popular chip-sets,
 such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15
 laptops).

   * The upload fixes the bug by allowing an FT suite to be selected only
 when the driver also supports FT.

  [Test Case]

   * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R
 and connecting to an AP supporting WPA-EAP and FT-EAP

  [Regression Potential]

   * a driver not advertising correctly its support for SME or the
 NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from
 using FT but would still be able to connect to APs

  [Other Info]

   * Upstream fix: 
https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490
   * Initial report: https://bugs.archlinux.org/task/63397
  ---

  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.l

[Desktop-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

Hello Thomas, or anyone else affected,

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

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

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

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

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

** Changed in: wpa (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  dbus errors, frequent roaming and unstable connectivity

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

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those 
warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

Hello Laurent, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa ships an invalid network-manager configuration that triggers warnings

  * Test case
  $ journalctl | grep no-mac-addr-change
  should not have errors listed

  * Regression potential
  the change removes configurations which are not needed (since they set the 
value to the same one as the default) and in the wrong section, it shouldn't 
have any visible impact

  

  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Hello Ken, or anyone else affected,

Accepted gnome-terminal into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
terminal/3.36.2-1ubuntu1~20.04 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: gnome-terminal (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Fix Committed
Status in vte2.91 source package in Focal:
  Fix Committed
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1883015/+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 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Hello Ken, or anyone else affected,

Accepted vte2.91 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vte2.91/0.60.3-0ubuntu1~20.04 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: vte2.91 (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Fix Committed
Status in vte2.91 source package in Focal:
  Fix Committed
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1883015/+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 1883535] Re: SRU the current 40.7 stable update

Hello Sebastien, or anyone else affected,

Accepted deja-dup into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/deja-dup/40.7-0ubuntu1
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: deja-dup (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  SRU the current 40.7 stable update

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current stable update, including some fixes and translation updates
  https://gitlab.gnome.org/World/deja-dup/-/releases/40.7

  The update also fixes bug #1883254 where a restore on a new
  installation hangs with no feedback

  * Test case

  Check that local and remote backups and restore are working. Also
  specifically it fixes the bug mentioned before which can be tested
  with those steps

  'On a fresh install, open Deja Dup, click the restore button, and
  notice that the progress bar never finishes.'

  
  * Regression potential

  The patch is pretty small, but technically does affect both restore
  and backup paths so best to test those for locale and remote locations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1883535/+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 1815289] Re: Please add Provides: gnome-www-browser

This bug was fixed in the package chromium-browser -
81.0.4044.129-0ubuntu0.19.10.1

---
chromium-browser (81.0.4044.129-0ubuntu0.19.10.1) eoan; urgency=medium

  * New upstream release: 81.0.4044.129
  * debian/control: add x-www-browser and gnome-www-browser to the Provides
section (LP: #1815289)
  * debian/chromium-browser.postinst: install /usr/bin/chromium-browser as an
alternative for x-www-browser and gnome-www-browser (LP: #1870640)

 -- Olivier Tilloy   Thu, 30 Apr 2020
16:34:30 +0200

** Changed in: chromium-browser (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  Please add Provides: gnome-www-browser

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Low. Some Debian packages depend on gnome-www-browser, and chromium-
  browser should be marked as providing it (similarly, it should provide
  x-www-browser).

  For instance, cinnamon-desktop-environment depends on gnome-www-
  browser and it doesn't have the chromium-browser name in the
  alternates (it has Debian's chromium name instead).

  
  [Test case]

  The output of `apt-cache showpkg gnome-www-browser` after the "Reverse 
Provides:" line should contain a chromium-browser entry.
  Similarly for `apt-cache showpkg x-www-browser`.

  
  [Regression potential]

  This is adding a couple of "provides" entries to the control file.
  Regressions could happen if other packages depending on or
  recommending gnome-www-browser (or x-www-browser) were implicitly
  relying on the fact that chromium-browser wasn't a candidate, but that
  sounds unlikely, and in any case something that should be fixed in
  thoses packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1815289/+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 1846785] Update Released

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

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

Title:
  Crashes instantly on launch with Pentium J5005 Processor

Status in djview4 package in Ubuntu:
  Invalid
Status in djvulibre package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Invalid
Status in djvulibre source package in Bionic:
  Fix Released

Bug description:
  * Impact
  djvulibre segfaults on older i386 CPU

  * Test case
  try to open a djvu file in evince on an atom based machine

  * Regression potential
  check that djvu files are open fine on newer machines

  -

  [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.

  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

  and fixed in commit 8407dd, on the 7th of October 2018.

  From git tags, it is included in 3.5.27.1-11 (probably version xxx
  -10, though I cannot see this tag in git history)

  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)

  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.

  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.

  I suggest upgrading the version available for Bionic LTS as part of
  the development hardware stack long term support to 3.5.27.1-11.

  Yours sincerly,

  Milvi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djview4/+bug/1846785/+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 1870640] Re: Does not register as x-www-browser alternative

This bug was fixed in the package chromium-browser -
81.0.4044.129-0ubuntu0.19.10.1

---
chromium-browser (81.0.4044.129-0ubuntu0.19.10.1) eoan; urgency=medium

  * New upstream release: 81.0.4044.129
  * debian/control: add x-www-browser and gnome-www-browser to the Provides
section (LP: #1815289)
  * debian/chromium-browser.postinst: install /usr/bin/chromium-browser as an
alternative for x-www-browser and gnome-www-browser (LP: #1870640)

 -- Olivier Tilloy   Thu, 30 Apr 2020
16:34:30 +0200

** Changed in: chromium-browser (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  Does not register as x-www-browser alternative

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Low. When installing chromium-browser in eoan/focal (which is a
  transitional package that installs the chromium snap), update-
  alternatives cannot be used to set it as x-www-browser or gnome-www-
  browser. This is a regression compared to the version of chromium-
  browser in bionic.

  
  [Test case]

  # update-alternatives --set x-www-browser /usr/bin/chromium-browser
  update-alternatives: error: alternative /usr/bin/chromium-browser for 
x-www-browser not registered; not setting

  
  [Regression potential]

  This is fixing a regression by adding back a code snippet that was in
  the package in bionic and previous releases. If the snippet has
  incorrect syntax, it could possibly prevent installation of the
  package. If the package installs fine, it's unlikely that anything
  could have regressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1846785] Re: Crashes instantly on launch with Pentium J5005 Processor

This bug was fixed in the package djvulibre - 3.5.27.1-8ubuntu0.2

---
djvulibre (3.5.27.1-8ubuntu0.2) bionic; urgency=medium

  * debian/patches/git_cpu_fix.patch:
- don't segfault when trying to open document on an atom based config
  (lp: #1846785)

 -- Sebastien Bacher   Wed, 20 May 2020 23:32:10
+0200

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

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

Title:
  Crashes instantly on launch with Pentium J5005 Processor

Status in djview4 package in Ubuntu:
  Invalid
Status in djvulibre package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Invalid
Status in djvulibre source package in Bionic:
  Fix Released

Bug description:
  * Impact
  djvulibre segfaults on older i386 CPU

  * Test case
  try to open a djvu file in evince on an atom based machine

  * Regression potential
  check that djvu files are open fine on newer machines

  -

  [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.

  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

  and fixed in commit 8407dd, on the 7th of October 2018.

  From git tags, it is included in 3.5.27.1-11 (probably version xxx
  -10, though I cannot see this tag in git history)

  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)

  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.

  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.

  I suggest upgrading the version available for Bionic LTS as part of
  the development hardware stack long term support to 3.5.27.1-11.

  Yours sincerly,

  Milvi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djview4/+bug/1846785/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

This bug was fixed in the package accountsservice -
0.6.55-0ubuntu12~20.04.1

---
accountsservice (0.6.55-0ubuntu12~20.04.1) focal; urgency=medium

  * Backport from groovy to focal.

accountsservice (0.6.55-0ubuntu12) groovy; urgency=medium

  * Cherry-pick from unstable.
  * Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)

 -- Iain Lane   Tue, 05 May 2020 17:05:26 +0100

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

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+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 1870847] Update Released

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

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

Title:
  App grid has too many page dots on right

Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1870847/+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 1870847] Re: App grid has too many page dots on right

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
68ubuntu1~20.04.1

---
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1) focal; urgency=medium

  * No contents change upload to focal
  * debian: Update control and gbp branch references to focal

gnome-shell-extension-ubuntu-dock (68ubuntu1) groovy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream stable release

  [ Michele Gaio ]
  * Get dash max size from the container and drop the
bindcontraint machinery (LP: #1870847)
  * Remove padding the dock ends in panel mode (LP: #1873321)

  [ Philip Langdale ]
  * locations: Handle emblemed mount icons

  [ ibaios ]
  * Added Basque localization.

 -- Marco Trevisan (Treviño)   Thu, 07 May 2020
23:06:01 +0200

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

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

Title:
  App grid has too many page dots on right

Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1870847/+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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
68ubuntu1~20.04.1

---
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1) focal; urgency=medium

  * No contents change upload to focal
  * debian: Update control and gbp branch references to focal

gnome-shell-extension-ubuntu-dock (68ubuntu1) groovy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream stable release

  [ Michele Gaio ]
  * Get dash max size from the container and drop the
bindcontraint machinery (LP: #1870847)
  * Remove padding the dock ends in panel mode (LP: #1873321)

  [ Philip Langdale ]
  * locations: Handle emblemed mount icons

  [ ibaios ]
  * Added Basque localization.

 -- Marco Trevisan (Treviño)   Thu, 07 May 2020
23:06:01 +0200

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

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Released
Status in yaru-theme source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1883744] [NEW] Numlock out of sync

2020-06-16 Thread tim

Public bug reported:

Using Remmina for vnc on Linux Mint 19.3 MATE (Based on Ubuntu 18.04)
accessing several machines with vino-server (v 1.4.6) running also on
Linux Mint 19.3 MATE. All machines boot up with Numlock on and vino-
server running. However in order to use the numeric key pad for numbers
on the remote machine I have to toggle the Numlock key on the Remmina
machine. Then the numbers work on the remote machine but the local
machine they are off. The symbols /, *, -, and . work fine.

Any idea how to fix this? Vino-server is started by systemd at boot. I
don't know what mechanism toggles the Numlock on at boot but could there
be a timing problem?

Is there a fixed setting in vino I can tell it what state to assume the
Numlock is when vino-server is started?

By the way when I use Remmina to access windows machines that are
running UltraVNC the Numlock is synced correctly.

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

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

Title:
  Numlock out of sync

Status in vino package in Ubuntu:
  New

Bug description:
  Using Remmina for vnc on Linux Mint 19.3 MATE (Based on Ubuntu 18.04)
  accessing several machines with vino-server (v 1.4.6) running also on
  Linux Mint 19.3 MATE. All machines boot up with Numlock on and vino-
  server running. However in order to use the numeric key pad for
  numbers on the remote machine I have to toggle the Numlock key on the
  Remmina machine. Then the numbers work on the remote machine but the
  local machine they are off. The symbols /, *, -, and . work fine.

  Any idea how to fix this? Vino-server is started by systemd at boot. I
  don't know what mechanism toggles the Numlock on at boot but could
  there be a timing problem?

  Is there a fixed setting in vino I can tell it what state to assume
  the Numlock is when vino-server is started?

  By the way when I use Remmina to access windows machines that are
  running UltraVNC the Numlock is synced correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1883744/+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 1883718] Re: zoom in/out problem

2020-06-16 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+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 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files

2020-06-16 Thread teo1978

No I can't.

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

Title:
  Left panel flickers like crazy during several seconds after deleting a
  bunch of files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have no idea if there are some requirements to trigger this issue,
  so I don't know whether you'll be able to reproduce it by just
  following my steps.

  Anyway, I can reproduce it 100% of the times:

  1. Open some folder in Nautilus
  2. Select a few files. Make sure you select quite a few
  3. Delete them by pressing the DEL key

  Expected:
  Nothing, a part from the files being deleted and disappearing from the 
displayed folder contents.

  Observed:
  During a few seconds after you hit Delete (I guess the time it takes to move 
the files to Trash and do some associated action, which by the way I don't know 
what it is that can take so long when deleting just a handful of files), the 
items in the list of shortcuts in the left panel (see screenshot) start 
flickering frantically, like crazy. It's pathetic.

  It looks like the item called "Networks", just below "Trash",
  disappears and reappears several times very quickly, causing all the
  items below it to move down and up, hence the flickering.

  Obviously it makes no sense.

  Note: there's nothing wrong to be appreciated in my screenshot, it
  just indicates where the flickering happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 19:24:36 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1797 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+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 1869981] Re: Printer notification every day at midnight

2020-06-16 Thread Till Kamppeter

I have already found a solution for this and applied it upstream
(1.27.5, already in Grrovy).

The problem is that near midnight, for the log rotate cups-browsed is
stopped and restarted. Stopping cups-browsed makes the cups-browsed-
generated print queues getting removed and when re-starting cups-browsed
afterwards they are generated again. This causes the notifications.

My approach is to let cups-browsed not remove the queues on shut-down,
on re-start cups-browsed connects to these queues again (as I have
designed cups-browsed to cope with crashes) and so no queue-creation
happens.

Zdenek Dohnal from Red Hat suggests modifying gnome-settings-daemon to
identify queues coming from cups-browsed and not notifying then. See

https://github.com/OpenPrinting/cups-filters/issues/241

Marking as fixed as my approach has made it into Groovy already.

** Bug watch added: github.com/OpenPrinting/cups-filters/issues #241
   https://github.com/OpenPrinting/cups-filters/issues/241

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

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  Printer notification every day at midnight

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869981/+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 1883705] Re: SRU the current 2.5.25 stable update

2020-06-16 Thread Bug Watch Updater

** Changed in: libgphoto2 (Debian)
   Status: Unknown => New

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

Title:
  SRU the current 2.5.25 stable update

Status in libgphoto2 package in Ubuntu:
  Fix Committed
Status in libgphoto2 package in Debian:
  New

Bug description:
  * Impact

  That's a stable update including bugfixes and support for newer
  cameras

  The list of changes is available there:
  https://sourceforge.net/projects/gphoto/files/libgphoto/2.5.25/

  * Test case

  Connect a camera and check that the desktop correctly see it and
  prompt for an action. Check that the content can be browsed from
  nautilus and the photos imported from shotwell (unmount the device
  from nautilus first if needed)

  * Regression potential

  Nothing specific to check, the fixes are mostly for hardware that was
  not working and the change devices specific

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1883705/+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 1869981] Re: Printer notification every day at midnight

IRC discussion extract

 seb128 see /etc/logrotate.d/cups-daemon postrotate "invoke-rc.d 
--quiet cups restart > /dev/null"; and cups-browsed.service has Requires: 
cups.service so it will restart, too
usually it's so the daemon closes the old logfile and opens the new one, but a 
full restart does seem excessive

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+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 1883718] Re: zoom in/out problem

I've been going through this problem since I left Windows and came to Ubuntu 
Linux. My computer is not running smoothly. There are all kinds of problems. I 
can't think of anything to do. I'm very worried that you are not solving the 
problem properly.
#2 & #3 please I request you to watch the video and fix this problem because I 
have been going through this problem for a long time and I can't find any 
solution to this problem. No one can fix all the problems of system 
software.When I scroll an application after opening the computer, sometimes it 
is not working, then it is working in zoom in zoom out, for this I am not able 
to do any work well, sometimes the system automatically opens one new tab after 
another.

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+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 1883718] Re: zoom in/out problem

** Attachment added: "Bug 🐞 2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384418/+files/VID-20200615-WA0005.mp4

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+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 1883718] Re: zoom in/out problem

** Attachment added: "Bug 🐞"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384414/+files/VID-20200615-WA0004.mp4

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

(closing the chromium part since it's not an issue with that component)

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svn

[Desktop-packages] [Bug 1883718] [NEW] zoom in/out problem

Public bug reported:

zoom in/out problem ,mouse scroll not work ,i seen all type of
application same problem like chromium,fireffox,files all software same
kind of problem ,please solve it .also send a video .

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 19:58:59 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23
dmi.board.asset.tag: Default string
dmi.board.name: A320M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: A320M-S2H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
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 resolution 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/1883718

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., L

[Desktop-packages] [Bug 1869981] Re: Printer notification every day at midnight

Till, could you have a look to that? It has been mentioned on bug
#1882462 as well, from the log there

'Jun 12 00:00:01 hero systemd[1]: Starting Rotate log files...
Jun 12 00:00:01 hero systemd[1]: Starting Daily man-db regeneration...
Jun 12 00:00:01 hero systemd[1]: Stopping Make remote CUPS printers available 
locally...
Jun 12 00:00:01 hero systemd[1]: cups-browsed.service: Succeeded.
Jun 12 00:00:01 hero systemd[1]: Stopped Make remote CUPS printers available 
locally.
Jun 12 00:00:01 hero systemd[1]: Stopping CUPS Scheduler...
Jun 12 00:00:01 hero systemd[1]: cups.service: Succeeded.
Jun 12 00:00:01 hero systemd[1]: Stopped CUPS Scheduler.
Jun 12 00:00:01 hero systemd[1]: cups.path: Succeeded.
...
'

Could you try to see why cups services restart there? Does it has to do
with the log rotation?

** Changed in: cups (Ubuntu)
   Importance: Undecided => Low

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

Hey Ian, thanks for the updating the report. I don't have the answers to
all your question and I'm unsure we have someone in desktop who is
expert with fontconfig or fonts to reply to e.g the first one

I can reply to at least one though!

> * Can someone explain exactly what things the `dpkg-reconfigure
fontcache` command calls to build the cache? is it sufficient to just
call fc-cache from the fontconfig package or do we need to be doing
something else too?

$ cat /var/lib/dpkg/info/fontconfig.postinst 
...
  # Force regeneration of all fontconfig cache files.
  mkdir -p /var/cache/fontconfig
  printf "Regenerating fonts cache... "
  fc-cache -s -f -v 1>/var/log/fontconfig.log 2>&1 || (printf "failed.\nSee 
/var/log/fontconfig.log for more information.\n"; exit 1)
  printf "done.\n"


that's what the fontconfig package is doing

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.C

[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2020-06-16 Thread Philippe

#6 Chris quote:
4. Go to "System" -> "Administration" -> "Users and Groups".
5. Change password from "Asked on logon" to "Not asked on logon".
6. Lock your machine.
7. Press "Switch User".
8. Observe no password is required to unlock as the current user.

I confirm this issue on Ubuntu Mate 20.04.0 in a virtual machine. I can
reproduce it each times.

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in Ubuntu MATE:
  Confirmed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-session-manager package in Ubuntu:
  Confirmed

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson

@Daniel: The regression caused by the mutter MR I mentioned in comment
#21 is bad for ibus-hangul users (Korean input). Any chance you can take
a look at it?

Besides fixing that ibus-hangul issue, doing so would make it possible
to stop setting GTK_IM_MODULE=ibus on GNOME desktops, which is something
I believe would be desirable for other reasons but this bug.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

2020-06-16 Thread Ian Johnson

Unfortunately we do not have a clear solution to this yet, so I have
unassigned myself from the snapd task and we need more help before we
can continue on this. Although, we have a few options as I detail here:
https://github.com/snapcore/snapd/pull/8856#issuecomment-644784642

I'm not sure what the best solution is, but definitely this will need
some guidance from the desktop team or others more knowledgable about
fonts about how to proceed here. Some questions I have include:

* Can someone explain the difference between fonts-noto-color-emoji and 
fonts-kiloji to try and understand why one shows up and the other doesn't with 
our current fontcache mechanism in snapd? 
* Can someone explain exactly what things the `dpkg-reconfigure fontcache` 
command calls to build the cache? is it sufficient to just call fc-cache from 
the fontconfig package or do we need to be doing something else too?
* Would it be possible for the fontcache to be run from inside confinement? 
I.e. what set of directories from the host would the fontcache binary from the 
fontconfig package need to see in order to build a fontcache?
* If we had to ship fontconfig in the base snaps, is it possible for us to just 
ship the fontconfig binary like we do today in the snapd snap, or do we really 
need the full package in order to have full compatibility with all fonts in 
Ubuntu?

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64

[Desktop-packages] [Bug 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Tagging rls-gg-notfixing after having it discussed in our meeting, while
it's a bug and should be fixed it only has one report and it's mostly a
cosmectic problem so we don't believe it deserves special tracking

Do you have a special ibus configuration?

Could you try if it happens with a new user account on the same machine?

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

@Dean, thanks for the log. Did you see the issue directly on boot? Did
you note the time where you saw it (would be useful to match the log
activity)

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

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+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 1883092] Re: Gnome Shell freeze

2020-06-16 Thread robert harper

** Attachment added: "settings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883092/+attachment/5384390/+files/settings.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/1883092

Title:
  Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  the computer will freeze everything but mouse and fail to boot back up
  for around 30 minutes after

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 11 11:57:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2020-05-29 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 2325CJ0
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=84df2c1d-136c-448c-b0a6-8483339655b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325CJ0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2325CJ0:pvrThinkPadX230:rvnLENOVO:rn2325CJ0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325CJ0
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-shell/+bug/1883092/+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 1883092] Re: Gnome Shell freeze

2020-06-16 Thread robert harper

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883092/+attachment/5384389/+files/journal.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/1883092

Title:
  Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  the computer will freeze everything but mouse and fail to boot back up
  for around 30 minutes after

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 11 11:57:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2020-05-29 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 2325CJ0
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=84df2c1d-136c-448c-b0a6-8483339655b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325CJ0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2325CJ0:pvrThinkPadX230:rvnLENOVO:rn2325CJ0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325CJ0
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-shell/+bug/1883092/+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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

2020-06-16 Thread Ian Johnson

** Changed in: snapd (Ubuntu)
 Assignee: Ian Johnson (anonymouse67) => (unassigned)

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:r

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

** Changed in: rtkit (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

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