[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
I'm not sure what changed to make 19.10 heavier than 19.04, but I can
explain what you are seeing.

What you are seeing is an OpenGL-based application (Firefox or Chromium)
that is being forced to update its entire window constantly. Since it is
OpenGL-based, gnome-shell does not have the opportunity to identify just
the small area of the screen that is changing, but has to update the
entire application window at full frame rate. To do that in software
without a GPU is expected to use a lot of CPU and multiple threads,
sorry.


** Summary changed:

- gnome-shell 100% CPU usage on all cores when animated gif is displayed
+ gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just 
to update the screen

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

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

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

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

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Low

** Changed in: mesa (Ubuntu)
   Status: New => Triaged

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

Title:
  gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU
  cores just to update the screen

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+attachment/5301946/+files/lspci.txt

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
Yes, it is a virtual machine (and hence 3 CPUs!) - though it didn't show
these symptoms with Ubuntu 19.04 (noticed by laptop fans going on as
soon as I visit a page with animated gifs, i.e. showing build status and
such).

There are no gnome extensions installed.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+attachment/5301944/+files/dmesg.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/1850874

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-10-31 Thread Daniel van Vugt
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 1847570, 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.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-10-31 Thread Daniel van Vugt
Switching on connect is an intentional design choice for Ubuntu. It's
been like that for a few years although PulseAudio 13.0 in Ubuntu 19.10
has introduced extra sensitivity with respect to HDMI events...

If you would like to disable it then please just comment out this line:

  load-module module-switch-on-connect

in /etc/pulse/default.pa

So this isn't a bug, but it does seem to overlap with bug 1847570 so
please see that too.

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

** Tags added: eoan

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


[Desktop-packages] [Bug 1844799] Re: Use new snap banner format

2019-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu11

---
gnome-software (3.30.6-2ubuntu11) focal; urgency=medium

  * debian/patches/0030-snap-Use-new-banner-media.patch:
- Use new banner format (LP: #1844799)
  * 
debian/patches/0031-Use-plugin-API-to-launch-apps-from-install-notificat.patch:
  * debian/patches/0032-snap-Allow-snaps-to-be-shown-by-AppStream-ID.patch:
- Fix snaps not launchding from the after install notification
  (LP: #1816396)

 -- Robert Ancell   Fri, 01 Nov 2019
16:40:46 +1300

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

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

Title:
  Use new snap banner format

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  Snaps now have a native banner format. The old screenshot method is no longer 
supported and will result in banners no longer displaying.

  [Test Case]
  1. Open GNOME Software
  2. Check banner shown in in the new format

  [Regression Potential]
  Some small risk of breaking banner code.

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
** Attachment added: "glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+attachment/5301945/+files/glxinfo.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/1850874

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1816396] Re: Starting snap from the after-install notification fails

2019-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu11

---
gnome-software (3.30.6-2ubuntu11) focal; urgency=medium

  * debian/patches/0030-snap-Use-new-banner-media.patch:
- Use new banner format (LP: #1844799)
  * 
debian/patches/0031-Use-plugin-API-to-launch-apps-from-install-notificat.patch:
  * debian/patches/0032-snap-Allow-snaps-to-be-shown-by-AppStream-ID.patch:
- Fix snaps not launchding from the after install notification
  (LP: #1816396)

 -- Robert Ancell   Fri, 01 Nov 2019
16:40:46 +1300

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

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

Title:
  Starting snap from the after-install notification fails

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  The launch button on the notification shown after snaps are installed doesn't 
 work.

  [Test Case]
  1. Open GNOME Software
  2. Select a snap that is not installed
  3. Install that snap
  4. Switch focus to another application (i.e. so GNOME Software doesn't have 
focus)

  Expected result:
  A notification is shown saying the app is installed with a button that 
launches it.

  Observed result:
  A notification is shown but the launch button give an error like "no such 
desktop file: io.snapcraft.vlc-"

  [Regression Potential]
  TBD

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
4. Run: dmesg > dmesg.txt
   and attach the file 'dmesg.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/1850874

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
3. Run: dmesg > dmesg.txt
   and attach the file 'dmesg.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/1850874

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
Thanks. The above attachment suggests to me that this is a virtual
machine or something unusual, because:

[   34.403367] tomasz gnome-shell[1410]: Failed to initialize accelerated 
iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe 
(LLVM 9.0, 256 bits)), falling back to CPU copy path
[   34.918603] tomasz gnome-shell[1410]: glamor: 'wl_drm' not supported
[   34.918603] tomasz gnome-shell[1410]: Missing Wayland requirements for 
glamor GBM backend
[   34.918603] tomasz gnome-shell[1410]: Failed to initialize glamor, falling 
back to sw

So that's where all the CPU is going... It's Mesa trying to use all the
CPU cores to emulate a GPU in software. Probably.

Next, please:

1. Run: lspci -k > lspcik.txt
   and attach the file 'lspcik.txt'

2. Run: glxinfo > glxinfo.txt
   and attach the file 'glxinfo.txt'

3. Tell us if you have any gnome-shell extensions installed.

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850887] [NEW] Audio / Sound reverts to HDMI when power event occurs

2019-10-31 Thread RevAngel
Public bug reported:

PulseAudio reverts the sound to HDMI all the time when a HDMI related
power event occurs. That means, although I have set another USB sound
device plugged in and set as default under sound settings, when an
application like Kodi or the system shuts off the HDMI monitor and I
reactivate the monitor, the sound is set to HDMI output again and again.

That probably has to do with the fix to the reported Bug # 1711101 and
definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two
days ago.

Setting the USB device as default does not help, even when done by
PulseAudio mixer (gui) and removing HDMI output from the alternatives
option.

Expected behavior:
PulseAudio keeps the sound setting to the selected device

Actual behavior: 
PulseAudio changes to HDMI at every HDMI power event

Annoying manual workaround:
Setting the desired Audio option on the control panel after every HDMI power 
event again

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Component: pulseaudio
Version: 1:13.0-1ubuntu1

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


** Tags: audio hdmi power pulseaudio sound

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


[Desktop-packages] [Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard

2019-10-31 Thread Misaka Mikoto
Uninstalling fcitx would solve the crashing issue, while
_clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed¨
still exists when switching keyboard. This means the crash is not wholly
caused by gnome.

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

Title:
  Ubuntu 19.10 gnome-shell crashes after changing keyboard

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
Status in mutter source package in Focal:
  Fix Released

Bug description:
  Updated to Ubuntu 19.10 Eoan, changing keyboard (from zh-cn to es-es)
  crashes gnome-shell, and displays that logoff is needed, but clicking
  logoff button is useless (won't work). Reboot, log in, and a black
  screen with movable cursur will be displayed. After some time, the
  crash screen will again be displayed.

  Checked journalctl /usr/bin/gnome-shell, a lot of "gnome-shell[1907]:
  _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)'
  failed" was found.

  Use tty3 to login and deleting ~/.config/dconf/user would help logging
  in to desktop environment (gnome won't display dock, and have no
  settings of dock for some reason though), but changing keyboard still
  crashes gnome as before.

  I tried adding disco and focal apt source into sources.list, and use
  aptitude to upgrade, or downgrade gnome to other versions. Things
  won't work either (can't even login).

  After some googling, I found a possibly related PR:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/764, but this
  commit is on 3.35.1, not 3.34.

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
apport information

** Tags added: apport-collected

** Description changed:

  This started to happen with Ubuntu 19.10.
  
  When an animated gif is displayed in a browser, gnome-shell begins using
  100% CPU on all cores.
  
  To reproduce:
  
  1) open Firefox, or Chromium
  
  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif
  
- 3) gnome-shell will start using 100% CPU on all cores (as long as
- Firefox/Chromium window is in the foreground)
+ 3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.1
+ Architecture: amd64
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.10
+ GsettingsChanges:
+  
+ InstallationDate: Installed on 2019-05-12 (172 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gnome-shell 3.34.1-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
+ Tags:  eoan
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


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

2019-10-31 Thread TomaszChmielewski
apport information

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


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

2019-10-31 Thread TomaszChmielewski
apport information

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


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

2019-10-31 Thread TomaszChmielewski
apport information

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard

2019-10-31 Thread Daniel van Vugt
That crash is not related to this bug so should not be discussed here.

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

Title:
  Ubuntu 19.10 gnome-shell crashes after changing keyboard

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
Status in mutter source package in Focal:
  Fix Released

Bug description:
  Updated to Ubuntu 19.10 Eoan, changing keyboard (from zh-cn to es-es)
  crashes gnome-shell, and displays that logoff is needed, but clicking
  logoff button is useless (won't work). Reboot, log in, and a black
  screen with movable cursur will be displayed. After some time, the
  crash screen will again be displayed.

  Checked journalctl /usr/bin/gnome-shell, a lot of "gnome-shell[1907]:
  _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)'
  failed" was found.

  Use tty3 to login and deleting ~/.config/dconf/user would help logging
  in to desktop environment (gnome won't display dock, and have no
  settings of dock for some reason though), but changing keyboard still
  crashes gnome as before.

  I tried adding disco and focal apt source into sources.list, and use
  aptitude to upgrade, or downgrade gnome to other versions. Things
  won't work either (can't even login).

  After some googling, I found a possibly related PR:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/764, but this
  commit is on 3.35.1, not 3.34.

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

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


[Desktop-packages] [Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard

2019-10-31 Thread Misaka Mikoto
Hi, I tried the given method (commenting things out), and the system captured a 
crash dump of fcitx. 
https://errors.ubuntu.com/oops/7ef8bffe-fc5f-11e9-b630-fa163e102db1

Some symptom showed that this has nothing to do with fcitx (Gnome dock
and desktop is not displaying either), but I will try uninstalling fcitx
and see if things work out.

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

Title:
  Ubuntu 19.10 gnome-shell crashes after changing keyboard

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
Status in mutter source package in Focal:
  Fix Released

Bug description:
  Updated to Ubuntu 19.10 Eoan, changing keyboard (from zh-cn to es-es)
  crashes gnome-shell, and displays that logoff is needed, but clicking
  logoff button is useless (won't work). Reboot, log in, and a black
  screen with movable cursur will be displayed. After some time, the
  crash screen will again be displayed.

  Checked journalctl /usr/bin/gnome-shell, a lot of "gnome-shell[1907]:
  _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)'
  failed" was found.

  Use tty3 to login and deleting ~/.config/dconf/user would help logging
  in to desktop environment (gnome won't display dock, and have no
  settings of dock for some reason though), but changing keyboard still
  crashes gnome as before.

  I tried adding disco and focal apt source into sources.list, and use
  aptitude to upgrade, or downgrade gnome to other versions. Things
  won't work either (can't even login).

  After some googling, I found a possibly related PR:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/764, but this
  commit is on 3.35.1, not 3.34.

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

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


[Desktop-packages] [Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop

2019-10-31 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249

Thanks. It seems to be bug 1849249 so let's track it there.

** This bug has been marked a duplicate of bug 1849249
   gnome-shell crashed with SIGABRT: 
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: 
(workspace == NULL)

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

Title:
  Changing text color in Thunderbird table will crash gnome desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing text color in Thunderbird table will crash gnome desktop.

  I have reproduced this multiple times.

  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color
  5) Select the color dialog

  At this point the color pallet will open, and the desktop manager will
  then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

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


[Desktop-packages] [Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop

2019-10-31 Thread John Agosta
Hi:
I had to use step 3 and the new bug report is here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850881 

Now, there are a number of (IMHO) really weird things that also happened
in this round of reproductions:

After reproducing the crash, I had these crash files:
-rw-r-  1 jagosta whoopsie 193242154 Oct 31 21:43 
_opt_google_chrome_chrome.1000.crash
-rw-r-  1 jagosta whoopsie 0 Oct 31 21:51 
_usr_bin_gnome-shell.1000.crash

So, the gnome crash file was empty this time, but there was also a
chrome crash file, so I tried running `ubuntu-bug` on the chrome crash
file.  When I did this it stated that it failed to generate a report
because google-chrome was out of date and needed to be updated.

So, I updated `google-chrome-stable (78.0.3904.87-1) to
(78.0.3904.70-1)`, and then I tried to reproduce the bug.  This time,
the gnome window manager appeared to crash and then reset -- so I did
not lose the window manager.  But, Chrome and Thunderbird both crashed.

I was left with these crash files:
-rw-r-  1 jagosta  whoopsie  38273264 Oct 31 22:02 
_usr_bin_gnome-shell.1000.crash
-rw-r--r--  1 jagosta  whoopsie 0 Oct 31 22:02 
_usr_bin_gnome-shell.1000.upload
-rw---  1 whoopsie whoopsie37 Oct 31 22:02 
_usr_bin_gnome-shell.1000.uploaded

Bug # 1850881 was submitted for this gnome-shell crash file.

I am really curious how updating chrome is impactign the behavior of
both Thunderbird and Gnome.


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

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

Title:
  Changing text color in Thunderbird table will crash gnome desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing text color in Thunderbird table will crash gnome desktop.

  I have reproduced this multiple times.

  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color
  5) Select the color dialog

  At this point the color pallet will open, and the desktop manager will
  then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

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


[Desktop-packages] [Bug 1835669] Re: OBS-studio returns OpenGL error with NVIDIA window capture mode

2019-10-31 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  OBS-studio returns OpenGL error with NVIDIA window capture mode

Status in mutter package in Ubuntu:
  Expired

Bug description:
  The error is: error: glCopyImageSubData failed, glGetError returned
  0x502

  I can confirm OBS works fine for me with other compositors such as the
  KDE compositor and XFCE compositor.

  obs-studio 23.2.1 64 bit
  budgie-desktop 10.5
  Ubuntu 18.04.2 LTS
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-03 (66 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-54-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/+source/mutter/+bug/1835669/+subscriptions

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


[Desktop-packages] [Bug 1842161] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'.

2019-10-31 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'.

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  idk how to show you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 30 23:56:28 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Device [196e:0f00]
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  MachineType: Dell Inc. Inspiron 546
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0F896N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/12/2009:svnDellInc.:pnInspiron546:pvr:rvnDellInc.:rn0F896N:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: Inspiron 546
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  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/1842161/+subscriptions

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


desktop-packages@lists.launchpad.net

2019-10-31 Thread Ogilvierothchild
I'm still seeing this behaviour on 18.04 LTS in both chromium and
google-chrome.

To workaround the issue, visit chrome://flags/ and search for "partial".
An option called "Partial swap" should appear, with a flag called "#ui-
disable-partial-swap".  Set the associated dropdown to say "Disabled".
Then press "Restart" and let the browser restart itself.  Then visit
chrome://gpu/ and verify that the last item in the first table under
"Version Information" is "Command Line", and than "--ui-disable-partial-
swap" appears in the list of commandline options.

For me this doesn't fix 100% of the problem, but makes it much better --
when maximizing the browser window, there isn't garbage at the top of
the window.  On restoring the window, the problem (or a similar problem)
is still there, but simply mousing over it makes it go away; unlike
before, I don't need to run the mouse over sections of the window trying
to get it to repaint the whole width of the corrput area.

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

Title:
  Chromium-custom title bar corrupt after maximize&restore

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  If the window is maximized, try to restore it and the window title bar, 
address bar or toolbar will not be rendered correctly also try hovering over 
them which show the issue. 
  Also tested while extensions are disabled.

  You can see that problem in the attached screenshot.

  Version 34.0.1847.116 Ubuntu 14.04 aura (260972)
  Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2 [modified: 
usr/bin/chromium-browser]
  Uname: Linux 3.14.0-eudyptula-10313-g39aaf74-dirty x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 17:31:21 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-03-24 (24 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (19 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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


[Desktop-packages] [Bug 1850881] Re: gnome-shell crashed with SIGABRT in __GI_raise()

2019-10-31 Thread Apport retracing service
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1849249, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301919/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301921/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301925/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301926/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301927/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301929/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1850881/+attachment/5301930/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1849249
   gnome-shell crashed with SIGABRT: 
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: 
(workspace == NULL)

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  new crash report for bug https://bugs.launchpad.net/bugs/1850833

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Oct 31 22:01:57 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-05-21 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/jagosta
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (9 days ago)
  UserGroups: sudo
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-31T21:46:58.510229
  separator:

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

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


[Desktop-packages] [Bug 1815723] Re: Segmentation fault (core dumped)

2019-10-31 Thread Sundar
*** This bug is a duplicate of bug 1814949 ***
https://bugs.launchpad.net/bugs/1814949

I had the same issue. Following reset command solved the problem:-

dconf reset -f /org/gnome/control-center/

Hope it helps someone looking for the solution.

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

Title:
  Segmentation fault (core dumped)

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

Bug description:
  Segmentation fault (core dumped) after upgrading to 3.31.90

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 11:29:40 2019
  InstallationDate: Installed on 2018-02-15 (362 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2018-10-20 (116 days ago)

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

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


[Desktop-packages] [Bug 1816396] Re: Starting snap from the after-install notification fails

2019-10-31 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Disco)
   Status: Triaged => Won't Fix

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

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

** Changed in: gnome-software (Ubuntu Eoan)
   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/1816396

Title:
  Starting snap from the after-install notification fails

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  The launch button on the notification shown after snaps are installed doesn't 
 work.

  [Test Case]
  1. Open GNOME Software
  2. Select a snap that is not installed
  3. Install that snap
  4. Switch focus to another application (i.e. so GNOME Software doesn't have 
focus)

  Expected result:
  A notification is shown saying the app is installed with a button that 
launches it.

  Observed result:
  A notification is shown but the launch button give an error like "no such 
desktop file: io.snapcraft.vlc-"

  [Regression Potential]
  TBD

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

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


[Desktop-packages] [Bug 1844799] Re: Use new snap banner format

2019-10-31 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Use new snap banner format

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  Snaps now have a native banner format. The old screenshot method is no longer 
supported and will result in banners no longer displaying.

  [Test Case]
  1. Open GNOME Software
  2. Check banner shown in in the new format

  [Regression Potential]
  Some small risk of breaking banner code.

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
Wow, yes. That is unusual. Multiple threads exist in gnome-shell but
they're pretty well hidden from the main code, mostly handling
asynchronous IO etc...

Next we need to see more information about the machine. Please run this
command to send it automatically:

  apport-collect 1850874


** No longer affects: mutter (Ubuntu)

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as
  Firefox/Chromium window is in the foreground)

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

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


[Desktop-packages] [Bug 1846940]

2019-10-31 Thread Liste-o
I think that's I have de same problem with this version :

Version: 6.4.0.0.alpha1
Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787
Threads CPU : 4; OS : Linux 5.3; UI Render : par défaut; VCL: gtk3; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded

I can use LibO 6.3 because the CPU up to 100% when I use my sheet with
macro. LibO 6.4 have the same problem.

The file Xray have this problem.

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  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/df-libreoffice/+bug/1846940/+subscriptions

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


[Desktop-packages] [Bug 1846940]

2019-10-31 Thread Armin-le-grand
Seems to be special stuff with controls - sigh.
When breaking in svx\source\sdr\contact\objectcontactofpageview.cxx:290 in line

pProcessor2D->process(xPrimitiveSequence);

it can be seen that the ViewInformation2D from *this and at the processor is 
the same, while later in LazyControlCreationPrimitive2D::get2DDecomposition it 
is *different*.
This is because the processed SeqOfPrim modifies it - in 
VclProcessor2D::RenderTransformPrimitive2D. This means the ControlPrimitive 
itself contains the offset (in my local example '30' which leads to a pixel 
offset of 1.0889). Forcing this to zero silences the repaint.

Thus the question is: Who and why does someone create a
TransformPrimitive2D? There are probably good reasons, so maybe we get a
principal problem here...?

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  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/df-libreoffice/+bug/1846940/+subscriptions

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


[Desktop-packages] [Bug 1846940]

2019-10-31 Thread Armin-le-grand
In adjustControlGeometry_throw aViewTranslate is sometimes *not* zero,
but has some values. Thi seems to be the reason for the offsets - tried
to hunt down where this comes from, but hard to find - about 25 stack
levels involved...

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  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/df-libreoffice/+bug/1846940/+subscriptions

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


[Desktop-packages] [Bug 1844799] Re: Use new snap banner format

2019-10-31 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu Disco)
   Status: Triaged => Won't Fix

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

Title:
  Use new snap banner format

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  Snaps now have a native banner format. The old screenshot method is no longer 
supported and will result in banners no longer displaying.

  [Test Case]
  1. Open GNOME Software
  2. Check banner shown in in the new format

  [Regression Potential]
  Some small risk of breaking banner code.

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
In "ps -eLf":

tomasz1410  1265  1410  1   10 Oct31 ?00:33:23 /usr/bin/gnome-shell
tomasz1410  1265  1421  0   10 Oct31 ?00:00:00 /usr/bin/gnome-shell
tomasz1410  1265  1423  0   10 Oct31 ?00:00:02 /usr/bin/gnome-shell
tomasz1410  1265  1424  0   10 Oct31 ?00:00:00 /usr/bin/gnome-shell
tomasz1410  1265  1425  7   10 Oct31 ?02:33:40 /usr/bin/gnome-shell
tomasz1410  1265  1426  7   10 Oct31 ?02:32:22 /usr/bin/gnome-shell
tomasz1410  1265  1427  7   10 Oct31 ?02:32:50 /usr/bin/gnome-shell
tomasz1410  1265  1434  0   10 Oct31 ?00:00:02 /usr/bin/gnome-shell
tomasz1410  1265  1435  0   10 Oct31 ?00:00:02 /usr/bin/gnome-shell
tomasz1410  1265  1436  0   10 Oct31 ?00:00:02 /usr/bin/gnome-shell


So it's definitely using multiple threads.

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as
  Firefox/Chromium window is in the foreground)

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
** Attachment added: "gnome-shell threads"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+attachment/5301916/+files/Screenshot_20191101_115659.png

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as
  Firefox/Chromium window is in the foreground)

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

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


[Desktop-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread Daniel van Vugt
Hmm, gnome-shell is mostly single threaded so it shouldn't be able to
use "all cores". It should saturate only one core at most.

Please provide a screenshot of 'top' running in a Terminal window,
showing that gnome-shell (or anything) is using the CPU.

** Tags added: eoan performance

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

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

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as
  Firefox/Chromium window is in the foreground)

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

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


[Desktop-packages] [Bug 1850806] Re: Ubuntu Software Centre (gnome-software) search function semi-broken

2019-10-31 Thread Daniel van Vugt
** Package changed: pulseaudio (Ubuntu) => gnome-software (Ubuntu)

** Tags added: eoan

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

Title:
  Ubuntu Software Centre (gnome-software) search function semi-broken

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu version:
  Description:  Ubuntu 19.10
  Release:  19.10

  Package version:
  ubuntu-software:
Installed: 3.30.6-2ubuntu10
Candidate: 3.30.6-2ubuntu10
Version table:
   *** 3.30.6-2ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

  Expected behaviour:
  Typing in a search query returns results

  What happened instead:
  Half the time, Ubuntu Software returns "no results"

  Work-around(ish):
  Delete a letter or two out of the search query

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

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


[Desktop-packages] [Bug 1850805] Re: PulseAudio resets output device to RX 580 HDMI every reboot

2019-10-31 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

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 1847570, 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 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  PulseAudio resets output device to RX 580 HDMI every reboot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version:
  Description:  Ubuntu 19.10
  Release:  19.10

  PulseAudio version:
  pulseaudio:
Installed: 1:13.0-1ubuntu1
Candidate: 1:13.0-1ubuntu1
Version table:
   *** 1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected behavior:
  Selected output device does not change after reboot

  What happened instead:
  When Ubuntu reboots, Pulse returns the output to RX 580's HDMI/DisplayPort 
device

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

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


[Desktop-packages] [Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop

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

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

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

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

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


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

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

Title:
  Changing text color in Thunderbird table will crash gnome desktop

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Changing text color in Thunderbird table will crash gnome desktop.

  I have reproduced this multiple times.

  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color
  5) Select the color dialog

  At this point the color pallet will open, and the desktop manager will
  then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

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


[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

2019-10-31 Thread Daniel van Vugt
This kind of problem is becoming common enough that we should also check
if it's a GUI issue in gnome-control-center in how it communicates with
PulseAudio.

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

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1850782] Re: Video display very slow, framerate dropped, slowing computer

2019-10-31 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => 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/1850782

Title:
  Video display very slow, framerate dropped, slowing computer

Status in Ubuntu:
  Invalid

Bug description:
  Video display very slow, framerate dropped, slowing computer

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 12:30:40 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  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:21f9]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=d9acd6e0-ecb4-47c5-946f-efc8dd1d9780 ro nomodeset acpi=off
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  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:bvrG6ETC2WW(2.82):bd11/21/2018:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 3443CTO
  dmi.product.sku: LENOVO_MT_3443
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/+bug/1850782/+subscriptions

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


[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

2019-10-31 Thread Daniel van Vugt
gnome-shell (via gjs and mozjs) actually doesn't free memory immediately
when JavaScript objects get deleted. It defers the garbage collection
until more stress (more memory use) is put on the system.

What this means is even without any leaks it will appear to grow for
some period of time before shrinking again.

So you might have a leak here, but also it will look like it's leaking
even when it's not in the long term :(

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times after logging in gnome-shell uses 600-800kB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200kB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]

2019-10-31 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1847524 ***
https://bugs.launchpad.net/bugs/1847524

It looks like a couple of people have reported these issues already so
let's use bug 1847524.

** No longer affects: mesa (Ubuntu)

** No longer affects: mutter (Ubuntu)

** Summary changed:

- gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: 
Core 2 T6600]
+ gnome-tweak-tool window keeps flickering on cursor hovering

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

** This bug has been marked a duplicate of bug 1847524
   Black titlebar (CSD) in Tweak Tool, flickering

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering

Status in gnome-tweaks package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-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/+source/gnome-tweaks/+bug/1850103/+subscriptions

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


[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-10-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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


[Desktop-packages] [Bug 1850874] [NEW] gnome-shell 100% CPU usage on all cores when animated gif is displayed

2019-10-31 Thread TomaszChmielewski
Public bug reported:

This started to happen with Ubuntu 19.10.

When an animated gif is displayed in a browser, gnome-shell begins using
100% CPU on all cores.

To reproduce:

1) open Firefox, or Chromium

2) load an URL where an animated gif is displayed - you can also use
this direct link to https://i.stack.imgur.com/h6viz.gif

3) gnome-shell will start using 100% CPU on all cores (as long as
Firefox/Chromium window is in the foreground)

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

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

Title:
  gnome-shell 100% CPU usage on all cores when animated gif is displayed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as
  Firefox/Chromium window is in the foreground)

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

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


[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

2019-10-31 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1849930] Re: Additional L2TP VPN Breaks First VPN

2019-10-31 Thread Lonnie Lee Best
I confirm that the packages provided by Douglas Kosovic's PPA work successfully:
https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-548593238

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

Title:
  Additional L2TP VPN Breaks First VPN

Status in gnome-control-center:
  New
Status in L2TP over IPsec VPN Manager:
  New
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When I add only one L2TP VPN profile to gnome-control-center's Network
  > VPN settings, it works fine.

  However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't
  work, but it corrupts the first L2TP VPN so that it too stops working.

  Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the
  first L2TP VPN) this does NOT repair the corruption to the first L2TP
  VPN, it remains corrupted.

  Additionally, removing all VPN profiles and re-adding the first one
  back, doesn't repair the corruption. Rebooting and adding them back
  doesn't work either.

  The only thing that works, that I've found, is completely reinstalling
  Ubuntu 19.10. Please advise better workarounds than reinstalling.

  In case it matters, these additional packages were also required for
  my initial VPN setup:

  sudo apt-get install -y network-manager-l2tp network-manager-l2tp-
  gnome strongswan

  Here's what's in the syslog on a failed VPN Connection attempt:

  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5632] 
audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" 
name="L2TP VPN1" pid=3531 uid=1000 result="success"
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5702] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Started the VPN service, PID 7273
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5747] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Saw the service appear; activating connection
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.6566] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: VPN connection: (ConnectInteractive) reply received
  Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec 
failed: starter is not running
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 
IPsec [starter]...
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn 
'1942cf95-93b1-4e74-a44a-947a46bffb5a'
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan 
IPsec...
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode 
IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ SA V V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (236 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (156 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ SA V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: 
IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, 
sending keep alives
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ ID HASH ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload 
length, decryptio

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

2019-10-31 Thread Balazs Pere
The main system which I use for work is Ubuntu 18.04.3 LTS. I use gnome with 
many extensions (see above). At the beginning the memory usage of gnome-shell 
is ~177MB. (Interesting that in another machine, which is a laptop and has 
exactly the same system and almost the same hardware, gnome-shell uses ~150MB 
at the beginning) During my work (using e.g. Octave, LyX, Chrome) the memory 
usage of gnome-shell is increasing continuously, but when I restart gnome-shell 
with "Alt+F2 r ", after some time the memory usage doesn't drop to the 
original value, but ramains at a higher value, which is approx. 200-250MB. This 
value is slowly increasing. I assume that there is a memory leak somewhere in 
gnome-shell or gjs (or somewhere else), but only a portion of the leaked memory 
can be freed with "Alt+F2 r ".
I tried to watch what causes the jumps in memory usage, but coudn't figure out 
it. Sometimes e.g. locking-unlocking the screen, but sometime it seems to be 
random.

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times after logging in gnome-shell uses 600-800kB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200kB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2019-10-31 Thread Vladimir Kondratyev
After transition to snap the Chromium is not usable for me. I have a lot
of PDFs with hyperlinks and they stopped working. Is there any
workaround other then migrating to deb Chrome?

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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

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


[Desktop-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

2019-10-31 Thread Filipe Garrett
I don't know if my problem is related specifically to the Realtek AC256
codec. In any case, it seems FreeBSD folk fixed a while back the same
issue: no headphone output through some patches related to this codec on
some Dell models.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219350
https://github.com/trueos/trueos/pull/279
https://reviews.freebsd.org/D19017

** Bug watch added: bugs.freebsd.org/bugzilla/ #219350
   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219350

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  Upgra

[Desktop-packages] [Bug 1719985] Re: flatpak software is not shown in gnome-software

2019-10-31 Thread Ernst Sjöstrand
It's not showing any updates for me in 19.10, and hasn't for quite some
time.

19:59:08:0937 Gs  autogenerating unique-id for com.spotify.Client.desktop
19:59:08:0937 GsPluginFlatpak com.spotify.Client has a downloaded update 
8b984d9a880fc4a894fc3c8199347ac88062c712dbb2e50abc2ad6262bf8->d3b733de029f89e31939f8b5c27df7d203cbea6a6212468d93a42e1d08fbd3a3
19:59:08:0937 Gs  not adding duplicate 
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable as 
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable already exists
19:59:08:0938 Gs  searching appstream for 
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable
19:59:08:0938 Gs  no app with ID 
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable found in 
system appstream
19:59:08:0938 Gs  no AppStream match for {pkgname} 
app/com.spotify.Client/x86_64/stable
19:59:08:0938 GsPluginFlatpak chose GsFlatpak-system-default using ID
19:59:08:0938 Gs  installable update 1.1.10.546 [0]
19:59:08:0938 Gs  installable update 1.1.5.153 [0]
19:59:08:0938 Gs  installable update 1.1.0.237 [0]
19:59:08:0938 Gs  installable update 1.0.98.78 [0]
19:59:08:0938 Gs  installable update 1.0.96.181 [0]
19:59:08:0938 Gs  installable update 1.0.94.262 [0]
19:59:08:0938 Gs  installable update 1.0.92.390 [0]
19:59:08:0938 Gs  installable update 1.0.89.313 [0]
19:59:08:0938 GsPluginFlatpak com.spotify.Client is not installed, so ignoring 
version of 1.1.10.546
19:59:08:0938 GsPluginFlatpak skipping reading metadata
19:59:08:0939 GsPluginFlatpak chose GsFlatpak-system-default using ID
19:59:08:0939 Gs  installable update 1.1.10.546 [0]
19:59:08:0939 Gs  installable update 1.1.5.153 [0]
19:59:08:0939 Gs  installable update 1.1.0.237 [0]
19:59:08:0939 Gs  installable update 1.0.98.78 [0]
19:59:08:0939 Gs  installable update 1.0.96.181 [0]
19:59:08:0939 Gs  installable update 1.0.94.262 [0]
19:59:08:0939 Gs  installable update 1.0.92.390 [0]
19:59:08:0939 Gs  installable update 1.0.89.313 [0]
19:59:08:0939 GsPluginFlatpak com.spotify.Client is not installed, so ignoring 
version of 1.1.10.546

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

Title:
  flatpak software is not shown in gnome-software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed gnome-software-plugin-flatpak which install flatpak and a
  few other packaged.

  After a reboot I opened gnome-software and at the top of the app under
  the headerbar I saw "Sorry, something went wrong" popup.

  I couldnt find any flatpaks shown in the software center.

  Is there something else we need to-do to get flatpaks working in
  17.10?

  Subsequently I can confirm that I can install flatpaks via the command
  line though using the flathub command line webpage.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 27 20:17:46 2017
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.0-0ubuntu2
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

2019-10-31 Thread Filipe Garrett
Just to give more insight about this, I just tried a live USB with
18.04.03 and the results are similar: the sound is extremely low, but
with no distortion whatsoever.

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP76

[Desktop-packages] [Bug 428306] Re: default search engines are removed and readded (keywords wiped) with upgrade

2019-10-31 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Invalid

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

Title:
  default search engines are removed and readded (keywords wiped) with
  upgrade

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

Bug description:
  Binary package hint: firefox-3.5

  I updated Karmic, which included upgrading Firefox from 3.5.2 to
  3.5.3. I previously had the keyword 'w' set for the Wikipedia search.
  It appears that all the default search engines have been removed and
  added again to the bottom of the list of search engines, without
  keywords. This means I've had to add back keywords for default search
  engines I use, and remove all the default search engines I had
  previously removed (eg. amazon, ebay, etc).

  The same situation occurs when upgrading from firefox-3.0 to
  firefox-3.5.

  Steps to reproduce:
  0) Install both firefox-3.0 and firefox-3.5. Move away ~/.mozilla so that you 
start with a fresh profile.
  1) Run firefox-3.0. In 'Manage Search Engines', add keywords to some, and 
remove others. Close firefox-3.0.
  2) Run firefox-3.5. Check 'Manage Search Engines'.

  What should happen:
  Search engines are the same as they were with firefox-3.0

  What actually happens:
  Default search engines have keywords wiped, and previously removed search 
engines have been added again.

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

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


[Desktop-packages] [Bug 428306]

2019-10-31 Thread Standard8
It is unclear if this is still an issue or not, but seeing as there
haven't been complaints in recent years, I will assume this has either
been worked around or fixed. So for now I'll resolve it.

If this is still an issue, I'm happy to talk about options to resolve
it.

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

Title:
  default search engines are removed and readded (keywords wiped) with
  upgrade

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

Bug description:
  Binary package hint: firefox-3.5

  I updated Karmic, which included upgrading Firefox from 3.5.2 to
  3.5.3. I previously had the keyword 'w' set for the Wikipedia search.
  It appears that all the default search engines have been removed and
  added again to the bottom of the list of search engines, without
  keywords. This means I've had to add back keywords for default search
  engines I use, and remove all the default search engines I had
  previously removed (eg. amazon, ebay, etc).

  The same situation occurs when upgrading from firefox-3.0 to
  firefox-3.5.

  Steps to reproduce:
  0) Install both firefox-3.0 and firefox-3.5. Move away ~/.mozilla so that you 
start with a fresh profile.
  1) Run firefox-3.0. In 'Manage Search Engines', add keywords to some, and 
remove others. Close firefox-3.0.
  2) Run firefox-3.5. Check 'Manage Search Engines'.

  What should happen:
  Search engines are the same as they were with firefox-3.0

  What actually happens:
  Default search engines have keywords wiped, and previously removed search 
engines have been added again.

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

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


[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-10-31 Thread mark kowski
Thanks for info - I didn't know that profiles are forward-compatible
only.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
  Throttleable: 1
  UptimeTS: 98.30915265
  Vendor: Mozilla
  Version: 71.0
  useragent_locale: en-US

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

-

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

2019-10-31 Thread Gunnar Hjalmarsson
Hmm.. Since the security team plans to let the ibus packages break on
previous libglib2.0-0, I dropped the step in the test case to reproduce
the previous bug.

** Description changed:

  [Impact]
  
  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.
  
  The real fix has been made in glib2.0, and the proposed updates in the
  below PPA will allow the IBus patch to be re-enabled.
  
  https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0
  
  [Test Case]
  
-  * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
-- Upgrade the ibus packages from
-  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
-- Install some IBus input method, e.g. ibus-libpinyin
-- Install some Qt application, e.g. Kate
+  * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
+- Upgrade the glib2.0 packages from
+  {eoan,disco,bionic,xenial}-proposed
+    - Upgrade the ibus packages from
+  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
+    - Install some IBus input method, e.g. ibus-libpinyin
+    - Install some Qt application, e.g. Kate
  
- * Relogin
+ * Relogin (maybe reboot)
  
  * Add the input method to the input sources
- 
- * Open the Qt app and try to input something using the IBus IM
- 
- => Find that only latin letters get inputted
- 
- * Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed
- 
- * Relogin (maybe reboot)
  
  * Open the Qt app and try to input something using the IBus IM
  
  => Find that the transliteration works as expected
  
  [Regression Potential]
  
  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
- Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30. 
+ Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
  
  [Original description]
  
  Kubuntu Release 18.04.3 LTS
  
  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
  
  Observed behavior:
  ibus is not usable anymore in Qt applications.
  
  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:
  
  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon
  
  This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed
  that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus
  functionality in Qt applications.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress
Status in glib2.0 source package in Bionic:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress
Status in glib2.0 source package in Eoan:
  In Progress
Status in glib2.0 source package in Focal:
  Fix Committed
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the proposed updates in the
  below PPA will allow

[Desktop-packages] [Bug 1847858] Re: No num lock upon starting Unity session

2019-10-31 Thread Khurshid Alam
It got broken in LP: #1845031. So they move the "numlock-state" under
desktop-schemas, but as boolean and not as enum. So numlock-state is
never saved in u-s-d. But manually pressing the hardware key should
still work. Working on a fix.

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Khurshid Alam (khurshid-alam)

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

Title:
  No num lock upon starting Unity session

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 fully dist-upgraded

  For a couple weeks now, there is no num lock upon starting the Unity
  session, as there should be.

  Behaviour confirmed on two separate Ubuntu 19.10 Unity stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1847858/+subscriptions

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


[Desktop-packages] [Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop

2019-10-31 Thread John Agosta
** Description changed:

  Changing text color in Thunderbird table will crash gnome desktop.
  
  I have reproduced this multiple times.
  
  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color
+ 5) Select the color dialog
  
- At this point the color dialog will open, and the desktop manager will
+ At this point the color pallet will open, and the desktop manager will
  then crash
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

Title:
  Changing text color in Thunderbird table will crash gnome desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing text color in Thunderbird table will crash gnome desktop.

  I have reproduced this multiple times.

  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color
  5) Select the color dialog

  At this point the color pallet will open, and the desktop manager will
  then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

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


[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

2019-10-31 Thread Victor Douglas
Hello,

I receive the same error on Kubuntu 18.04, so I purge both duplicity 0.7
and deja-dup and install the snap version of them, as instructed by
Michael and Aaron. Nevertheless, I still get the same error when I run
"snap run duplicity". Here's the output:


$ which duplicity
/snap/bin/duplicity

$ snap list | grep duplicity
duplicity 0.8.02  11beta   
aaron-whitehouse  classic

$ snap run duplicity
Traceback (innermost last):
  File "/snap/duplicity/11/bin/duplicity", line 1711, in 
with_tempdir(main)
  File "/snap/duplicity/11/bin/duplicity", line 1699, in with_tempdir
tempdir.default().cleanup()
  File "/snap/duplicity/11/lib/python2.7/site-packages/duplicity/tempdir.py", 
line 63, in default
_defaultInstance = TemporaryDirectory(temproot=globals.temproot)
  File "/snap/duplicity/11/lib/python2.7/site-packages/duplicity/tempdir.py", 
line 135, in __init__
log.Info(_(u"Using temporary directory %s") % self.__dir)
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 16: 
ordinal not in range(128)

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-10-31 Thread Martin Dünkelmann
We always prefer a repository package over Snap.
Snap takes more storage space and forces us to run an application with 
deprecated and security breaking libraries just because a developer doesn't 
want to test his application with the newest dependencies.

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

Title:
  Please upgrade it to 68.x on Ubuntu 18.04 LTS

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Now the official upgrade way from 60 to 68 got open by mozilla.

  Plus there are security fixes and performance enhancements.
  
https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2

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

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


[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

2019-10-31 Thread Christoph
I'm still facing this problem. I just switched to 19.10 and the snap package 
has been installed. It does not work.
I tried to do the "snap connect chromium:u2f-devices" but this will not solve 
the problem.

My dmesg out put shows a lot of DENIED:

audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568 
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? 
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
 pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0


Can you please advise how to fix this? Thanks!

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]
  Installing a snap that requires the u2f-devices interface doesn't show a UI 
element to enable/disable this in GNOME Software. Initially Chromium didn't 
have this enabled by default, and thus the feature wouldn't work without going 
to the command line. It now is enabled by default.

  [Test Case]
  1. Open GNOME Software
  2. Install the Chromium snap
  3. Click "Permissions"

  Expected result:
  A switch is shown to control "Read/write access to U2F devices exposed". 
Clicking it connects/disconnects the u2f-devices interface.

  Observed result:
  No switch is shown for this interface.

  [Regression Potential]
  A string for this interface was added to GNOME Software, low risk of 
introducing a new bug.

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

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


[Desktop-packages] [Bug 1850833] [NEW] Changing text color in Thunderbird table will crash gnome desktop

2019-10-31 Thread John Agosta
Public bug reported:

Changing text color in Thunderbird table will crash gnome desktop.

I have reproduced this multiple times.

Reproduction steps:
1) Open Thunderbird
2) New mail
3) Add Table to mail
4) Format->Table->Table or Cell background Color

At this point the color dialog will open, and the desktop manager will
then crash

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 31 11:15:11 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-05-21 (162 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Changing text color in Thunderbird table will crash gnome desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing text color in Thunderbird table will crash gnome desktop.

  I have reproduced this multiple times.

  Reproduction steps:
  1) Open Thunderbird
  2) New mail
  3) Add Table to mail
  4) Format->Table->Table or Cell background Color

  At this point the color dialog will open, and the desktop manager will
  then crash

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 11:15:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-21 (162 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (8 days ago)

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

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


[Desktop-packages] [Bug 1850832] [NEW] Forced login as gnome-initial-setup user, which then crashes.

2019-10-31 Thread Emily Noneman
Public bug reported:

After updating to Ubuntu 19.10, I get automatically logged in as a
gnome-initial-setup user. Whatever it is doing then crashes (I get a
crash report). The desktop then hangs.

Work around:
1. In grub go to advanced Ubuntu options. Chose the latest kernel in recovery 
mode
2. Select root shell
3. apt-get remove gnome-initial-setup
4. reboot

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "_usr_libexec_gnome-initial-setup.136.crash"
   
https://bugs.launchpad.net/bugs/1850832/+attachment/5301862/+files/_usr_libexec_gnome-initial-setup.136.crash

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

Title:
  Forced login as gnome-initial-setup user, which then crashes.

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu 19.10, I get automatically logged in as a
  gnome-initial-setup user. Whatever it is doing then crashes (I get a
  crash report). The desktop then hangs.

  Work around:
  1. In grub go to advanced Ubuntu options. Chose the latest kernel in recovery 
mode
  2. Select root shell
  3. apt-get remove gnome-initial-setup
  4. reboot

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

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


[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save

2019-10-31 Thread Christopher Barrington-Leigh
Yes, I have now very grudgingly upgraded to 19.10 and the problem seems
to be resolved.

This problem was new at some point in 19.04 (ie did not exist at first
with 19.04) and I do not think pressuring eople to upgrade (so soon
after a release) is a good solution.

On the other hand, strangely, no one else has reported the bug.

Thanks, Olivier!

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

Title:
  print page dialog latency when trying to cancel or to save

Status in chromium-browser package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Since less than a month ago, using the print page dialog (which for me
  defaults to saving as PDF) is outlandishly slow. Once opened, if I try
  to close it (click cancel / press Esc) or to use it (click Save or
  press Enter), there is no visible response, and my system hangs for 10
  seconds.  After that though, the operation concludes successfully and
  things return to normal.

  This did not used to happen. Closing or submitting the print-to-PDF
  used to result in the pop-up window closing immediately and the
  browser regaining responsiveness.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  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-5:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-6:
   enabled: disabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM=
   modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-7:
   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///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   modes: 1920x1080
  Date: Mon Jun 17 14:03:12 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-01-24 (144 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   
  Load-Avg-1min: 3.09
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  modified.conffi

[Desktop-packages] [Bug 1850046] Re: gedit freezes when opening PHP file with long lines

2019-10-31 Thread Jaromir Obr
As for the issue with non responsive gnome shell (bug 1845302), I hope
the fix in Mutter will be delivered to Ubuntu 19.10 (where it's broken
from my point of view). And then I'm able to test it.

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

Title:
  gedit freezes when opening PHP file with long lines

Status in gedit:
  New
Status in gedit package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  * Download 
https://github.com/vrana/adminer/releases/download/v4.7.4/adminer-4.7.4.php 
(485 kB)
  * Open it in gedit

  Expected result:
  * It takes a few seconds. E.g. in Visual Studio Code editor it takes max 10 
sec

  Actual result:
  * File isn't open even in a few minutes
  * I'm only getting a dialog "Text Editor not responding" with the buttons 
"Wait" and "Force quit".
  * Unfortunately neither "Wait" or "Force Quit" is working and Gnome stops 
responding, so I have to switch to text console by Ctrl + Alt + F4 and kill the 
gedit process. But then often when I switch back to Gnome desktop, it's still 
not responding (e.g. neither clicking to any application nor keyboard is 
working) and I have to restart OS.

  Used SW:
  * Ubuntu 19.10
  * gedit 3.34.0-1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gedit 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 27 14:34:07 2019
  InstallationDate: Installed on 2015-12-29 (1397 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

2019-10-31 Thread Gunnar Hjalmarsson
** Description changed:

+ [Impact]
+ 
+ IBus was broken for Qt applications as a regression due to the fix of
+ CVE-2019-14822. As a result the IBus patch was disabled temporarily,
+ which fixed IBus from a usability POV.
+ 
+ The real fix has been made in glib2.0, and the proposed updates in the
+ below PPA will allow the IBus patch to be re-enabled.
+ 
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0
+ 
+ [Test Case]
+ 
+  * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
+- Upgrade the ibus packages from
+  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
+- Install some IBus input method, e.g. ibus-libpinyin
+- Install some Qt application, e.g. Kate
+ 
+ * Relogin
+ 
+ * Add the input method to the input sources
+ 
+ * Open the Qt app and try to input something using the IBus IM
+ 
+ => Find that only latin letters get inputted
+ 
+ * Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed
+ 
+ * Relogin (maybe reboot)
+ 
+ * Open the Qt app and try to input something using the IBus IM
+ 
+ => Find that the transliteration works as expected
+ 
+ [Regression Potential]
+ 
+ The applicable patches origin from glib upstream:
+ https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
+ Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30. 
+ 
+ [Original description]
+ 
  Kubuntu Release 18.04.3 LTS
  
  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
  
  Observed behavior:
  ibus is not usable anymore in Qt applications.
  
  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:
  
- Bus::open: Connect ibus failed! 
+ Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon
  
  This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed
  that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus
  functionality in Qt applications.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: glib2.0 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: High
   Status: Fix Committed

** Also affects: ibus (Ubuntu Focal)
   Importance: High
   Status: Fix Released

** Also affects: glib2.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** No longer affects: ibus (Ubuntu Xenial)

** No longer affects: ibus (Ubuntu Bionic)

** No longer affects: ibus (Ubuntu Disco)

** No longer affects: ibus (Ubuntu Eoan)

** Changed in: glib2.0 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Disco)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Disco)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: glib2.0 (U

[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

2019-10-31 Thread Paul White
Upstream issue #1059 was closed as being a duplicate of
https://gitlab.gnome.org/GNOME/mutter/issues/572. Updating upstream bug
task and reassigning Ubuntu task. Still a problem in Ubuntu 19.10.

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

** Changed in: gnome-shell
   Status: Fix Released => Unknown

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1059 => 
gitlab.gnome.org/GNOME/mutter/issues #572

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

** Tags added: eoan

** Project changed: gnome-shell => mutter

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850824] [NEW] nvidia-graphics-drivers-340 340.107-0ubuntu7 ADT test failure with linux 5.4.0-3.4

2019-10-31 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-340/20191030_152019_285d9@/log.gz

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-340 340.107-0ubuntu7 ADT test failure with
  linux 5.4.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-340/20191030_152019_285d9@/log.gz

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

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


[Desktop-packages] [Bug 1850827] [NEW] nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with linux 5.4.0-3.4

2019-10-31 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-430/20191030_143532_ead01@/log.gz

** Affects: nvidia-graphics-drivers-430 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with
  linux 5.4.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-430/20191030_143532_ead01@/log.gz

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

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


[Desktop-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-10-31 Thread Jean
Nope, behavior is the same between 1.10.6-2ubuntu1.1 and
1.10.6-2ubuntu1.2: broken if using split traffic between VPN and normal
connection.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Desktop-packages] [Bug 1850782] Re: Video display very slow, framerate dropped, slowing computer

2019-10-31 Thread Timo Aaltonen
don't use 'nomodeset'

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

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

Title:
  Video display very slow, framerate dropped, slowing computer

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Video display very slow, framerate dropped, slowing computer

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 12:30:40 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  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:21f9]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=d9acd6e0-ecb4-47c5-946f-efc8dd1d9780 ro nomodeset acpi=off
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  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:bvrG6ETC2WW(2.82):bd11/21/2018:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 3443CTO
  dmi.product.sku: LENOVO_MT_3443
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-10-31 Thread Till Kamppeter
Jean, does this mean that 1.10.6-2ubuntu1.1 works perfectly for you and
1.10.6-2ubuntu1.2 shows the problem you mention?

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2019-10-31 Thread Louis
> It's still the same. You can select primary monitor, but most
applications will not respect it and will run only on the left monitor.
If your primary monitor is on the right, everything works perfectly
though.

I have the same behavior with Ubuntu 18.04 LTS

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix
Status in xfwm4 package in Ubuntu:
  Invalid

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

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

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


[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-31 Thread Dariusz Gadomski
I have just run the test case from this bug description on the bionic-proposed 
version 1.10.6-2ubuntu1.2.
tcpdump does not show any leak of the VPN-specific queries. I have not observed 
other issues in my tests.

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

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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


[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]

2019-10-31 Thread tojonuko.khad...@gmail.com
exactly, that was what i was trying to explain right here. this happens
to me every single time i open the tweak tool.

https://launchpad.net/~xavierl
please click on "this bug affects me" on the top left of this page.

i was so desperate anyone would take notice of this. thanks.

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering [Intel
  Penryn: Core 2 T6600]

Status in gnome-tweaks package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-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/+source/gnome-tweaks/+bug/1850103/+subscriptions

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


[Desktop-packages] [Bug 1850805] [NEW] PulseAudio resets output device to RX 580 HDMI every reboot

2019-10-31 Thread M. Knepper
Public bug reported:

Ubuntu version:
Description:Ubuntu 19.10
Release:19.10

PulseAudio version:
pulseaudio:
  Installed: 1:13.0-1ubuntu1
  Candidate: 1:13.0-1ubuntu1
  Version table:
 *** 1:13.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

Expected behavior:
Selected output device does not change after reboot

What happened instead:
When Ubuntu reboots, Pulse returns the output to RX 580's HDMI/DisplayPort 
device

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

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

Title:
  PulseAudio resets output device to RX 580 HDMI every reboot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version:
  Description:  Ubuntu 19.10
  Release:  19.10

  PulseAudio version:
  pulseaudio:
Installed: 1:13.0-1ubuntu1
Candidate: 1:13.0-1ubuntu1
Version table:
   *** 1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected behavior:
  Selected output device does not change after reboot

  What happened instead:
  When Ubuntu reboots, Pulse returns the output to RX 580's HDMI/DisplayPort 
device

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

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


[Desktop-packages] [Bug 1850806] [NEW] Ubuntu Software Centre (gnome-software) search function semi-broken

2019-10-31 Thread M. Knepper
Public bug reported:

Ubuntu version:
Description:Ubuntu 19.10
Release:19.10

Package version:
ubuntu-software:
  Installed: 3.30.6-2ubuntu10
  Candidate: 3.30.6-2ubuntu10
  Version table:
 *** 3.30.6-2ubuntu10 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages
100 /var/lib/dpkg/status

Expected behaviour:
Typing in a search query returns results

What happened instead:
Half the time, Ubuntu Software returns "no results"

Work-around(ish):
Delete a letter or two out of the search query

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

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

Title:
  Ubuntu Software Centre (gnome-software) search function semi-broken

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version:
  Description:  Ubuntu 19.10
  Release:  19.10

  Package version:
  ubuntu-software:
Installed: 3.30.6-2ubuntu10
Candidate: 3.30.6-2ubuntu10
Version table:
   *** 3.30.6-2ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

  Expected behaviour:
  Typing in a search query returns results

  What happened instead:
  Half the time, Ubuntu Software returns "no results"

  Work-around(ish):
  Delete a letter or two out of the search query

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

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


[Desktop-packages] [Bug 1850803] [NEW] Wrong wrap length when composing emails

2019-10-31 Thread Alistair Cunningham
Public bug reported:

After upgrading to Ubuntu 19.10, Thunderbird seems to use the wrong wrap
length when composing emails. I have mail.wrap_long_lines set to true,
and mailnews.wraplength set to 72, but when composing emails, lines are
wrapped at a  shorter length. It appears to be about 55 characters.
Emails that I have sent are displayed correctly, so the problem only
happens when composing.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: thunderbird 1:68.1.2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alistair  30823 F pulseaudio
BuildID: 20191010144232
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 31 10:47:12 2019
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 dns-search integrics.com
IncompatibleExtensions:
 Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
 English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
 Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-08-16 (805 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 172.20.64.1 dev wlp58s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp58s0 scope link metric 1000 
 172.20.64.0/19 dev wlp58s0 proto kernel scope link src 172.20.71.127 metric 600
MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug eoan

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

Title:
  Wrong wrap length when composing emails

Status in thunderbird package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 19.10, Thunderbird seems to use the wrong
  wrap length when composing emails. I have mail.wrap_long_lines set to
  true, and mailnews.wraplength set to 72, but when composing emails,
  lines are wrapped at a  shorter length. It appears to be about 55
  characters. Emails that I have sent are displayed correctly, so the
  problem only happens when composing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair  30823 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:47:12 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 172.20.64.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   172.20.64.0/19 dev wlp58s0 proto kernel scope link src 172.20.71.127 metric 
600
  MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Pr

[Desktop-packages] [Bug 1322728] Re: VPN Connection Failed With 2 Factor Authentication

2019-10-31 Thread Francis
Hi,

I imported my client configuration using the option "import from a file"
(translation from "importer depuis un fichier"). My client configuration
contain that line:

static-challenge "Code unique d'authentification" 1

When I look at my connection configuration in /etc/NetworkManager
/system-connections, I don't see any reference to the static-challence
configuration. I suspect the problem come from there.

So when I try to connect, NM ask me the password, but never the
challenge PIN. I tried to enter my PIN when NM request again my
password, but it doesn't work either.

In my client logs (first try I enter my password, the second try I enter my 2FA 
PIN)
oct 31 09:09:52 u1910 NetworkManager[491]:   [1572527392.4132] audit: 
op="connection-activate" uuid="0df2fac7-29f5-4808-b15a-f49f748a8963" name="vpn" 
pid=1317 uid=1000 result="success"
oct 31 09:09:52 u1910 NetworkManager[491]:   [1572527392.4475] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
Started the VPN service, PID 2254
oct 31 09:09:52 u1910 NetworkManager[491]:   [1572527392.4768] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
Saw the service appear; activating connection
oct 31 09:10:02 u1910 NetworkManager[491]:   [1572527402.8568] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
VPN plugin: state changed: starting (3)
oct 31 09:10:02 u1910 NetworkManager[491]:   [1572527402.8574] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
VPN connection: (ConnectInteractive) reply received
oct 31 09:10:02 u1910 nm-openvpn[2271]: OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL 
(OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep  5 2019
oct 31 09:10:02 u1910 nm-openvpn[2271]: library versions: OpenSSL 1.1.1c  28 
May 2019, LZO 2.10
oct 31 09:10:03 u1910 nm-openvpn[2271]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
oct 31 09:10:03 u1910 nm-openvpn[2271]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]4.3.2.1:1192
oct 31 09:10:03 u1910 nm-openvpn[2271]: UDP link local: (not bound)
oct 31 09:10:03 u1910 nm-openvpn[2271]: UDP link remote: [AF_INET]4.3.2.1:1192
oct 31 09:10:03 u1910 nm-openvpn[2271]: NOTE: chroot will be delayed because of 
--client, --pull, or --up-delay
oct 31 09:10:03 u1910 nm-openvpn[2271]: NOTE: UID/GID downgrade will be delayed 
because of --client, --pull, or --up-delay
oct 31 09:10:03 u1910 nm-openvpn[2271]: [server] Peer Connection Initiated with 
[AF_INET]4.3.2.1:1192
oct 31 09:10:04 u1910 nm-openvpn[2271]: AUTH: Received control message: 
AUTH_FAILED
oct 31 09:10:04 u1910 nm-openvpn[2271]: SIGUSR1[soft,auth-failure] received, 
process restarting
oct 31 09:10:09 u1910 NetworkManager[491]:   [1572527409.5104] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
VPN plugin: requested secrets; state connect (4)
oct 31 09:10:21 u1910 nm-openvpn[2271]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
oct 31 09:10:21 u1910 nm-openvpn[2271]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]4.3.2.1:1192
oct 31 09:10:21 u1910 nm-openvpn[2271]: UDP link local: (not bound)
oct 31 09:10:21 u1910 nm-openvpn[2271]: UDP link remote: [AF_INET]4.3.2.1:1192
oct 31 09:10:21 u1910 PackageKit[910]: uid 1000 is trying to obtain 
org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
oct 31 09:10:21 u1910 PackageKit[910]: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
oct 31 09:10:21 u1910 nm-openvpn[2271]: [server] Peer Connection Initiated with 
[AF_INET]4.3.2.1:1192
oct 31 09:10:22 u1910 nm-openvpn[2271]: AUTH: Received control message: 
AUTH_FAILED
oct 31 09:10:22 u1910 nm-openvpn[2271]: SIGUSR1[soft,auth-failure] received, 
process restarting
oct 31 09:10:22 u1910 PackageKit[910]: refresh-cache transaction /20_aabcedec 
from uid 1000 finished with success after 1406ms
oct 31 09:10:27 u1910 NetworkManager[491]:   [1572527427.6045] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
VPN plugin: requested secrets; state connect (4)
oct 31 09:10:29 u1910 NetworkManager[491]:  [1572527429.8132] 
vpn-connection[0x55d5bb61c310,0df2fac7-29f5-4808-b15a-f49f748a8963,"vpn",0]: 
Failed to request VPN secrets #4: User canceled the secrets request.
oct 31 09:10:29 u1910 nm-openvpn[2271]: ERROR: could not read Auth 
username/password/ok/string from management interface
oct 31 09:10:29 u1910 nm-openvpn[2271]: Exiting due to fatal error

(last error is when I clicked the cancel button)


In my server logs:
Oct 31 09:10:03 srv ovpn-bureau-2fa[1409]: Error extracting challenge/response 
from password. Parse error = 'Incorrectly formatted cr string.'
Oct 31 09:10:03 srv ovpn-bureau-2fa[1409]: 1.2.3.4:51828 PLUGIN_CALL: POST 
/usr/local/lib/openvpn-auth-ldap.so/PLUGIN_AUTH_USER_PASS_VERIFY status=1

[Desktop-packages] [Bug 1850635] Re: Some applications don't redraw their windows correctly

2019-10-31 Thread Aaron A Aardvark
Having tried the "modesetting" driver for a while, I find it suffers
from severe screen tearing, which makes it practically unusable.  I
prefer the half-broken intel driver!

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

Title:
  Some applications don't redraw their windows correctly

Status in fvwm package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After updating from 19.04 to 19.10 I noted that some apps don't redraw
  their window(s) correctly.  Affected apps include (it seems) all Qt-
  based apps (including KDE and VirtualBox), as well as
  firefox/thunderbird.

  Unaffected apps include emacs, chrome, xterm.

  The symptom is that an affected app will only redraw its window when
  another X window redraws its window.  If there is no other window,
  then the app's window is not redrawn at all.

  This is best illustrated with a video, which shows the problem using
  konsole and kpat (both KDE apps) :-

  https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA

  I am using the intel graphics driver (no graphics card).

  Other info as requested below :-

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  $ apt-cache policy xserver-xorg
  xserver-xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 30 11:50:09 2019
  DistUpgraded: 2019-10-21 13:25:02,550 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
  InstallationDate: Installed on 2016-01-02 (1396 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=8af2cd02-0009-4ce5-9ec6-e6cdf44c9411 ro nopti
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (8 days ago)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   #enabled=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-01-06T17:10:43.876145
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/fvwm/+bug/1850635/+subscriptions

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


[Desktop-packages] [Bug 1725955] Re: "Printer added" notification

2019-10-31 Thread Carlos Laviola
This started happening to me after I upgraded from Ubuntu 19.04 to
19.10. Now I get a steady spam of pop-ups and the only thing in the logs
that seems related are colord messages like the one from #6:

out 31 13:08:47 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 13:13:31 maragogi colord[1784]: failed to get session [pid 4408]: No 
data available
out 31 13:32:07 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
(...)
out 31 14:00:20 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:00:38 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:01:05 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:01:37 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:01:56 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:02:14 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:02:34 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:03:02 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:03:22 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:03:40 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:04:09 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:04:31 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:04:49 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:05:05 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:05:23 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:05:53 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:06:13 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:06:32 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:07:19 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:07:38 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:08:06 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:08:24 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:08:43 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available
out 31 14:09:10 maragogi colord[1784]: failed to get session [pid 19534]: No 
data available

The referenced PIDs:

claviola  4408  0.0  0.1 991904 26724 ?Ssl  out30   0:04 
/usr/lib/gnome-settings-daemon/gsd-color
root 19534  0.0  0.0 105252 12528 ?Ss   00:00   0:03 
/usr/sbin/cupsd -l

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

Title:
  "Printer added" notification

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've recently installed Ubuntu 17.10 (Gnome shell). After a while I
  saw an OSD notification with the message "printer added", and thought
  that must be because of the new driverless printers feature in the
  kernel. I have a brother printer in the network, and I tested it and
  it worked. The thing is that the message repeats itself, approximately
  every two minutes, and it's really distracting. I saw a question about
  this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04
  -printer-added-notifications-under-gnome), and a solution, but it
  seemed like no one had filed a bug report.

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

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


[Desktop-packages] [Bug 1850646] Re: Sound output device switched on DP/MST connect

2019-10-31 Thread John
Thanks, resolution 10/10, will report issues again.

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

Title:
  Sound output device switched on DP/MST connect

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  1. Starting with sound output set to line-out with DP/MST/HDMI monitor 
connected.
  2. Disconnect monitor. Sound output remains on line-out. Music continues 
playing etc.
  3. Re-connect monitor. Music/sound stops being produced. Sound output device 
is switched to HDMI/Display Port 6 device. 

  Sound output device should remain on user-selected device unless user
  interactively changes the output device. Or add configurable option
  for "sound output device auto switching".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.3.7-050307-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 10:14:02 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-04 (329 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (7 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:59:11.363686

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

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


[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

2019-10-31 Thread Balazs Pere
Yes, MB, not kB.
Today I made a new test. I logged in (ubuntu 19.10 on virtualbox, normal ubuntu 
session) and started the gnome-system-monitor to see what is happening. The 
memory usage of gnome-shell was ~202MB at the beginning. I locked the session, 
and unlocked it. The memory usage jumped to ~225MB. A lock and unlocked again, 
the result was ~226MB. Further lock-unlock action made only small, less than 
1MB growings. After that a did nothing, left the system untouched. After an 
hour the memory usage was ~260MB.

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times after logging in gnome-shell uses 600-800kB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200kB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]

2019-10-31 Thread Xavier
Well, the same problem happens in the "Parameters" dashboard. If I get
it well, there are three breakpoints:

 * no left-menu displayed
 * a narrow left-menu displayed
 * a larger left-menu displayed

In the case of a narrow left menu, flicker happens at least in the Tweak
tool and Parameters app. See attached screenshot (flickering happens at
a much higher framerate than the gif displays it, as if width were
computed in a loop)

** Attachment added: "Peek 31-10-2019 14-01.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+attachment/5301770/+files/Peek%2031-10-2019%2014-01.gif

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering [Intel
  Penryn: Core 2 T6600]

Status in gnome-tweaks package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-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/+source/gnome-tweaks/+bug/1850103/+subscriptions

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


[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]

2019-10-31 Thread Xavier
I can confirm the bug, exact same behavior here. Upgraded from ubuntu
19.04 and same flickering effect.

 * I open the Tweak tool window
 * I try to hover one of the left menu's items -> it flickers, I can not manage 
to click on a menu item sucessfully
 * If I resize the window (I have  to make it larger so that the menu displays 
larger), then the menu works as expected and the flickering effect disappears - 
I have to do it everytime I launch the app, though.

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering [Intel
  Penryn: Core 2 T6600]

Status in gnome-tweaks package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-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/+source/gnome-tweaks/+bug/1850103/+subscriptions

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


[Desktop-packages] [Bug 1850635] Re: Some applications don't redraw their windows correctly

2019-10-31 Thread Aaron A Aardvark
Thank you for the reply.

Changing the driver in xorg.conf from "intel" to "modesetting" fixed the
problem.

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

Title:
  Some applications don't redraw their windows correctly

Status in fvwm package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After updating from 19.04 to 19.10 I noted that some apps don't redraw
  their window(s) correctly.  Affected apps include (it seems) all Qt-
  based apps (including KDE and VirtualBox), as well as
  firefox/thunderbird.

  Unaffected apps include emacs, chrome, xterm.

  The symptom is that an affected app will only redraw its window when
  another X window redraws its window.  If there is no other window,
  then the app's window is not redrawn at all.

  This is best illustrated with a video, which shows the problem using
  konsole and kpat (both KDE apps) :-

  https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA

  I am using the intel graphics driver (no graphics card).

  Other info as requested below :-

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  $ apt-cache policy xserver-xorg
  xserver-xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 30 11:50:09 2019
  DistUpgraded: 2019-10-21 13:25:02,550 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
  InstallationDate: Installed on 2016-01-02 (1396 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=8af2cd02-0009-4ce5-9ec6-e6cdf44c9411 ro nopti
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (8 days ago)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   #enabled=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-01-06T17:10:43.876145
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/fvwm/+bug/1850635/+subscriptions

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


[Desktop-packages] [Bug 1850782] [NEW] Video display very slow, framerate dropped, slowing computer

2019-10-31 Thread BjG
Public bug reported:

Video display very slow, framerate dropped, slowing computer

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 31 12:30:40 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
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:21f9]
InstallationDate: Installed on 2019-10-26 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 3443CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=d9acd6e0-ecb4-47c5-946f-efc8dd1d9780 ro nomodeset acpi=off
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G6ETC2WW (2.82 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3443CTO
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:bvrG6ETC2WW(2.82):bd11/21/2018:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X1 Carbon
dmi.product.name: 3443CTO
dmi.product.sku: LENOVO_MT_3443
dmi.product.version: ThinkPad X1 Carbon
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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 eoan 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/1850782

Title:
  Video display very slow, framerate dropped, slowing computer

Status in xorg package in Ubuntu:
  New

Bug description:
  Video display very slow, framerate dropped, slowing computer

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 12:30:40 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  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:21f9]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=d9acd6e0-ecb4-47c5-946f-efc8dd1d9780 ro nomodeset acpi=off
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  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:bvrG6ETC2WW(2.82):bd11/21/2018:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 3443CTO
  dmi.product.sku: LENOVO_MT_3443
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xor

[Desktop-packages] [Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-10-31 Thread Jaime Cruz
Snaps waste too damned much space and take forever to launch.

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

Title:
  Please upgrade it to 68.x on Ubuntu 18.04 LTS

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Now the official upgrade way from 60 to 68 got open by mozilla.

  Plus there are security fixes and performance enhancements.
  
https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2

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

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


[Desktop-packages] [Bug 801991] Re: rhythmbox crashes when adding a podcast

2019-10-31 Thread Paul White
Bug report won't expire due to bug watch
No activity on upstream bug for 7 years
No reports here for over 4 years
No response to comment #8 
Cannot reproduce crash with version 3.4.3 in Ubuntu 19.10
As 7 users were affected I'm closing this as being fixed

** Changed in: rhythmbox (Ubuntu)
   Status: Incomplete => 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/801991

Title:
  rhythmbox crashes when adding a podcast

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

Bug description:
  trying to add http://feeds.feedburner.com/linuxoutlaws-ogg
  Go to Music -> New Podcast Feed...
  Crash when I click add.
  gdb backtrace attached

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: rhythmbox 0.13.3-0ubuntu6
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic-pae 2.6.38.7
  Uname: Linux 2.6.38-10-generic-pae i686
  Architecture: i386
  Date: Sat Jun 25 18:42:44 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to natty on 2011-03-15 (101 days ago)

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

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


[Desktop-packages] [Bug 1850780] [NEW] Right click often activates the first action

2019-10-31 Thread Corentin Noël
Public bug reported:

I'm having an issue on elementary OS (based on Ubuntu 18.04) every time
that I right click, I also activate the right click menu. setting
`ui.context_menus.after_mouseup` to true in about:config seems to fix
the issue for me.

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

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

Title:
  Right click often activates the first action

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm having an issue on elementary OS (based on Ubuntu 18.04) every
  time that I right click, I also activate the right click menu. setting
  `ui.context_menus.after_mouseup` to true in about:config seems to fix
  the issue for me.

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

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


[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-10-31 Thread Till Kamppeter
Looks like that during boot time components get fired up in wrong order,
some dependency in the systemd service files is needed.

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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


[Desktop-packages] [Bug 1850778] [NEW] Audio output changes to hdmi after hibernate

2019-10-31 Thread Petter Sundlöf
Public bug reported:

This wasn't present in 19.04:

When returning from hibernate, audio devices is changed to hdmi (gp104 device), 
which is not even plugged in. When playing audio and changing volume one has to 
go into volume settings or pavucontrol to change the output/controlled device 
back to "Line out".
Disabling "module-switch-on-port-available" is not an option because that 
disable automatic switching to headphone output.

I've tried disabling the gp104 device in pavucontrol, but this has no effect, 
it keeps switching to it.
This is not specific to the nvidia driver's gp104 hdmi output though, to be 
clear, because the same thing happened when I had pulseaudio-dlna active -- it 
switched to those devices after wake, which was even worse because playing 
audio on the computer after a  wake-from-sleep kept launching my 
chromecast/other dlna devices in my apartment.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-terminal 3.34.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 31 12:04:19 2019
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2018-07-04 (483 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274

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


** Tags: amd64 apport-bug eoan

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

Title:
  Audio output changes to hdmi after hibernate

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  This wasn't present in 19.04:

  When returning from hibernate, audio devices is changed to hdmi (gp104 
device), which is not even plugged in. When playing audio and changing volume 
one has to go into volume settings or pavucontrol to change the 
output/controlled device back to "Line out".
  Disabling "module-switch-on-port-available" is not an option because that 
disable automatic switching to headphone output.

  I've tried disabling the gp104 device in pavucontrol, but this has no effect, 
it keeps switching to it.
  This is not specific to the nvidia driver's gp104 hdmi output though, to be 
clear, because the same thing happened when I had pulseaudio-dlna active -- it 
switched to those devices after wake, which was even worse because playing 
audio on the computer after a  wake-from-sleep kept launching my 
chromecast/other dlna devices in my apartment.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 12:04:19 2019
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-07-04 (483 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274

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

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


[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

2019-10-31 Thread Esokrates
Indeed, I forgot to upgrade so I missed the issue. Now that I did I see
the hiss is indeed much louder. Thanks Kai for sending this upstream
already.

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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


[Desktop-packages] [Bug 1850775] [NEW] DNS info is not loaded by dhclient

2019-10-31 Thread Pengpeng Sun
Public bug reported:

Hi Team,

Could you please help to confirm if this is an issue on Ubuntu19.10
Desktop?

1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
   supersede domain-name "vmware.com";
   supersede domain-name-servers 10.117.0.1;

2. Reboot

3. check DNS info by "systemd-resolve --status", the DNS domain and
server is not set. But /run/systemd/resolved.conf.d/isc-
dhcp-v4-ens160.conf contains the new DNS domain and server.

4. Manually run "systemctl try-reload-or-restart systemd-
resolved.service" and then DNS is set correctly, "systemd-resolve
--status" output have the new DNS domain and server.


I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

Thanks,
Pengpeng

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: cloud-init (Ubuntu) => network-manager (Ubuntu)

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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


[Desktop-packages] [Bug 1834967] Re: Windows in Activities might be partially off screen

2019-10-31 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1834967

Title:
  Windows in Activities might be partially off screen

Status in GNOME Shell:
  Fix Released
Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850753] Re: Ubuntu 19.10 cannot set background to solid color

2019-10-31 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  Ubuntu 19.10 cannot set background to solid color

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  The settings Background only allows setting to a picture, not a solid
  color.

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

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


[Desktop-packages] [Bug 1850775] [NEW] DNS info is not loaded by dhclient

2019-10-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi Team,

Could you please help to confirm if this is an issue on Ubuntu19.10
Desktop?

1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
   supersede domain-name "vmware.com";
   supersede domain-name-servers 10.117.0.1;

2. Reboot

3. check DNS info by "systemd-resolve --status", the DNS domain and
server is not set. But /run/systemd/resolved.conf.d/isc-
dhcp-v4-ens160.conf contains the new DNS domain and server.

4. Manually run "systemctl try-reload-or-restart systemd-
resolved.service" and then DNS is set correctly, "systemd-resolve
--status" output have the new DNS domain and server.


I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

Thanks,
Pengpeng

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
DNS info is not loaded by dhclient
https://bugs.launchpad.net/bugs/1850775
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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


[Desktop-packages] [Bug 1850125] Re: Can't start gnome/xorg -- says that the xsettings service is already running.

2019-10-31 Thread Nathan Schepers
Sure!

** Attachment added: "today.j"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1850125/+attachment/5301725/+files/today.j

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

Title:
  Can't start gnome/xorg -- says that the xsettings service is already
  running.

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Using `gdm` or `lightdm` and choosing gnome/xorg gives me a fatal
  error:

  Oct 24 00:40:31 AS-XPS-13-9360 gsd-xsettings[2395]: You can only run one 
xsettings manager at a time; exiting
  Oct 24 00:40:31 AS-XPS-13-9360 gsd-xsettings[2395]: Failed to start: Could 
not initialize xsettings manager.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: gsd-xsettings.service: Main 
process exited, code=exited, status=1/FAILURE
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: gsd-xsettings.service: Failed 
with result 'exit-code'.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: Failed to start GNOME XSettings.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: Dependency failed for GNOME 
XSettings.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: gsd-xsettings.target: Job 
gsd-xsettings.target/start failed with result 'dependency'.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: gsd-xsettings.service: 
Triggering OnFailure= dependencies.
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: Started GNOME Session Failed 
lockdown screen (user).
  Oct 24 00:40:31 AS-XPS-13-9360 systemd[1801]: Reached target GNOME Session 
Failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME:Unity
  Date: Mon Oct 28 11:42:03 2019
  InstallationDate: Installed on 2018-11-16 (346 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (4 days ago)

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

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


[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

2019-10-31 Thread Maciej Borzecki
** Changed in: snapd
   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/1840925

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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


[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-10-31 Thread Olivier Tilloy
I can reliably reproduce the crash in a 16.04 VM. The crash doesn't
occur on 18.04.

Note that this is a beta version of firefox, so use at your own risk
(but the crash will be investigated indeed, thanks for the report!).

Profile incompatibility when downgrading is to be expected. Profiles are
only forward-compatible.

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

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",764

  1   2   >