date:20200212

Actually I have seen this a couple of times in the past week or so. I'll
reconfirm if and when it happens again.

** Tags added: focal

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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

[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-02-12 Thread ABIX - Adam Jurkiewicz

One comment. This situation does NOT happen, when I use Atom to edit.
It is happening only with Xed Editor.

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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

[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-02-12 Thread ABIX - Adam Jurkiewicz

I can confirm. My system is:

adasiek@mint-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:Linux Mint 19.3 Tricia
Release:19.3
Codename:   tricia
adasiek@mint-desktop:~$ uname -a
Linux mint-desktop 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I have quite good machine:
processor   : 7
vendor_id   : GenuineIntel
cpu family  : 6
model   : 94
model name  : Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz
stepping: 3
microcode   : 0xd6
cpu MHz : 1191.362
cache size  : 6144 KB
physical id : 0
siblings: 8
core id : 3
cpu cores   : 4

and ibus daemon is running randomly about 100% cpu. Keeping htop opened
in terminal helps.

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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

[Desktop-packages] [Bug 1855469] Re: gnome-shell lags on wayland

This bug is closed for now because the information requested in comment
#2 was not provided.

I'd like to note though, that if you find 'swapoff -a' helps then that's
an indication your system was experiencing a memory leak. For some
reason Ubuntu is better able to deal with those situations when swapping
is disabled. But it doesn't mean the kernel's swapping behaviour is the
main issue...

If you would like to continue discussing this bug then please:

 (a) Provide the information requested in comment #2; and

 (b) Reproduce the lag situation again and while it is happening run:

 ps auxw --sort -rss > allprocesses.txt

 and then attach the file 'allproceses.txt' here.

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

Title:
  gnome-shell lags on wayland

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  see https://discourse.ubuntu.com/t/boosting-the-real-time-performance-
  of-gnome-shell-3-34-in-ubuntu-19-10/13095/24

  I’m using ubuntu on wayland for a while (Unity and Gnome since Unity 
abandon). But with ubuntu 19.10 upgrade, Gnome was so slow and laggy that I had 
thought to downgrade or a new laptop. I switched back to Xorg and now 
everything is as smoth as usual.
  I have an intel card, don’t know if it can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  6 18:54:15 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-05-23 (1658 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (33 days ago)

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

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

[Desktop-packages] [Bug 1855534] Re: UI irresponsive Object Clutter.Actor , has been already deallocated

Since you are using Debian and not Ubuntu please go here instead:

https://www.debian.org/Bugs/Reporting

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

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

Title:
  UI irresponsive Object Clutter.Actor , has been already deallocated

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  We are using GNOME Shell 3.30.2 and the UI become irresponsible until
  a reboot several times a week with the following continuously logs in
  journalctl.

  If it can help, it is used as a kiosk with chromium started fullscreen and an 
hdmi/usb touchscreen
  ( 
https://www.amazon.fr/gp/product/B07MRL2FWT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
 )
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:15   id=7[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:15id=6[slave  
keyboard (3)

  Is there:
  - a way to fix it?
  - a workaround (disabling something) to avoid it

  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname gnome-shell[563]: 
../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with 
id '101431'
  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for 
context 0x55cdae05c280 ==
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0   7fffba689f60 b 
  resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #1   7fffba68a030 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #2   7fffba68a0e0 b 
  resource:///org/gnome/shell/ui/tweener.js:112 (7fae046d9040 @ 37)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #3   7fffba68a1a0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (7fae046db9d0 @ 54)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #4   7fffba68a2f0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:342 (7fae046dba60 @ 1742)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #5   7fffba68a3a0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:355 (7fae046dbaf0 @ 100)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #6   7fffba68a430 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:370 (7fae046dbb80 @ 10)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #7   7fffba68a4b0 I 
  resource:///org/gnome/gjs/modules/signals.js:128 (7fae046c18b0 @ 386)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #8   7fffba68a560 b 
  resource:///org/gnome/shell/ui/tweener.js:244 (7fae046d99d0 @ 159)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #9   7fffba68a630 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #10   7fffba68a6d0 
b   resource:///org/gnome/shell/ui/tweener.js:219 (7fae046d9940 @ 15)
  déc. 06 20:10:35 myhostname gnome-shell[563]: 
../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with 
id '101431'
  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for 
context 0x55cdae05c280 ==
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0   7fffba689f60 b 
  resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #1   7fffba68a030 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #2   7fffba68a0e0 b 
  resource:///org/gnome/shell/ui/tweener.js:112 (7fae046d9040 @ 37)
  déc. 06 20:10:35 myhostname

[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

2020-02-12 Thread Bug Watch Updater

** Changed in: gcc
   Status: New => Confirmed

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

(In reply to Jakub Jelinek from comment #8)
> On the #c7 testcase, this started with
> r8-6072-ga3a821c903c9fa2288712d31da2038d0297babcb (so I wonder why this
> isn't a 8/9/10 Regression).

I'm not sure Kelvin's patch is to blame.  I think it's just exposing a
latent issue.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

2020-02-12 Thread Jakub-gcc

On the #c7 testcase, this started with
r8-6072-ga3a821c903c9fa2288712d31da2038d0297babcb (so I wonder why this
isn't a 8/9/10 Regression).

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

2020-02-12 Thread Matthias Klose

the file from icu 65.1 is built using

g++ -v -Wdate-time -g -O3 -fstack-protector-strong -Wformat -Werror
=format-security -W -Wall -pedantic -Wpointer-arith -Wwrite-strings
-Wno-long-long -std=c++11 -c -o genmbcs.o genmbcs.ii

no specific patches applied for the trunk. The compiler defaults to PIE,
and the usual hardening defaults:

/usr/lib/gcc/powerpc64le-linux-gnu/10/cc1plus -fpreprocessed genmbcs.ii
-msecure-plt -quiet -dumpbase genmbcs.ii -mcpu=power8 -auxbase-strip
genmbcs.o -g -O3 -Wdate-time -Wformat=1 -Werror=format-security -Wextra
-Wall -Wpedantic -Wpointer-arith -Wwrite-strings -Wno-long-long
-std=c++11 -version -fstack-protector-strong -fasynchronous-unwind-
tables -fstack-protector-strong -Wformat-security -fstack-clash-
protection

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

Confirmed.  With the options in Comment 4, I'm able to recreate the
hang/infinite loop.  I'll have a look.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

So we are in an infinite loop in process_address() calling
process_address_1().  I've hacked in some code to ICE if we loop for too
long and I'm currently using creduce to minimize the test case.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

I cannot recreate this with trunk or GCC 9 from today.  DO you have
extra patches applied or ???

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

Here's the minimal test case using options -O3 -mcpu=power8 -fstack-
protector-strong:

void bar();
char b;
void
foo (void)
{
  char a;
  int d = b;
  char *e = 
  while (d)
*e++ = --d;
  bar ();
}

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1378982] Re: A strange screeching sound is heard randomly

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

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

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

Title:
  A strange screeching sound is heard randomly

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  Hello

  I use Ubuntu 14.04 64 bits and Rhythmbox 3.0.2.

  When I listen to music file whether they are mp3, ogg or any other
  format, the application make a strange noise during playback, it's a
  noise which looks like reading a music CD with computer data track. It
  happens randomly on several tracks, it can happen on one track and if
  read again not and vice-versa. I have tested the same music files on
  VLC and SMPLAYER and did not get the same issues.

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

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

[Desktop-packages] [Bug 948322] Re: Rhythmbox sync to library deleted all my music files

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

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

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

Title:
  Rhythmbox sync to library deleted all my music files

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  I use an external usb drive to store my music, I added the music
  folder on my external usb as the library in preferences. Now when I
  did this it did not look like it was adding anything to the library so
  I clicked import folder and imported the music folder from the
  external usb drive. This imported all my files however they did not
  show up in library under music, showed all my files under devices
  which is not what I wanted as it was having to rescan the library
  every time I started the program. Then I clicked the sync to library
  button which deleted all my files without so much as asking me. Ubuntu
  12.04 beta 1 and rhythmbox 2.95.

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

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

[Desktop-packages] [Bug 1855534] Re: UI irresponsive Object Clutter.Actor , has been already deallocated

[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/1855534

Title:
  UI irresponsive Object Clutter.Actor , has been already deallocated

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  We are using GNOME Shell 3.30.2 and the UI become irresponsible until
  a reboot several times a week with the following continuously logs in
  journalctl.

  If it can help, it is used as a kiosk with chromium started fullscreen and an 
hdmi/usb touchscreen
  ( 
https://www.amazon.fr/gp/product/B07MRL2FWT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
 )
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:15   id=7[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:15id=6[slave  
keyboard (3)

  Is there:
  - a way to fix it?
  - a workaround (disabling something) to avoid it

  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname gnome-shell[563]: 
../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with 
id '101431'
  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for 
context 0x55cdae05c280 ==
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0   7fffba689f60 b 
  resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #1   7fffba68a030 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #2   7fffba68a0e0 b 
  resource:///org/gnome/shell/ui/tweener.js:112 (7fae046d9040 @ 37)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #3   7fffba68a1a0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (7fae046db9d0 @ 54)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #4   7fffba68a2f0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:342 (7fae046dba60 @ 1742)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #5   7fffba68a3a0 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:355 (7fae046dbaf0 @ 100)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #6   7fffba68a430 b 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:370 (7fae046dbb80 @ 10)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #7   7fffba68a4b0 I 
  resource:///org/gnome/gjs/modules/signals.js:128 (7fae046c18b0 @ 386)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #8   7fffba68a560 b 
  resource:///org/gnome/shell/ui/tweener.js:244 (7fae046d99d0 @ 159)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #9   7fffba68a630 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #10   7fffba68a6d0 
b   resource:///org/gnome/shell/ui/tweener.js:219 (7fae046d9940 @ 15)
  déc. 06 20:10:35 myhostname gnome-shell[563]: 
../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with 
id '101431'
  déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor 
(0x55cdb066c440), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for 
context 0x55cdae05c280 ==
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0   7fffba689f60 b 
  resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #1   7fffba68a030 b 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #2   7fffba68a0e0 b 
  resource:///org/gnome/shell/ui/tweener.js:112 (7fae046d9040 @ 37)
  déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]:

[Desktop-packages] [Bug 1855469] Re: gnome-shell lags on wayland

[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/1855469

Title:
  gnome-shell lags on wayland

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  see https://discourse.ubuntu.com/t/boosting-the-real-time-performance-
  of-gnome-shell-3-34-in-ubuntu-19-10/13095/24

  I’m using ubuntu on wayland for a while (Unity and Gnome since Unity 
abandon). But with ubuntu 19.10 upgrade, Gnome was so slow and laggy that I had 
thought to downgrade or a new laptop. I switched back to Xorg and now 
everything is as smoth as usual.
  I have an intel card, don’t know if it can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  6 18:54:15 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-05-23 (1658 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (33 days ago)

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

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

[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)

Maybe not. Today I did see the bug, or something like it, occur in Gnome
Shell 3.35.

** Tags removed: fixed-in-3.35 fixed-upstream

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-12 Thread Nivedita Singhvi

Additional observations.

MAAS is being used to deploy the system and configure
the bond interface and settings.

MAAS allows you to specify which is the primary interface, with
the other being the backup, for the active-backup bonding mode.
However, it does not appear to be working -it's not passing along 
a primary primitive, for instance, in the netplan yaml or otherwise 
resulting in this being honored (still need to confirm).

MAAS allows you to enter a mac address for the bond interface,
but if not supplied, by default it will use the mac address of
the "primary" interface, as configured.

MAAS then populates the /etc/netplan/50-cloud-init.yaml, including
a macaddr= line with the default.

netplan then passes that along to systemd-networkd.

The bonding kernel, however, will use as the active interface
whichever interface is first attached to the bond (i.e., which
completes getting attached to the bond interface first) in the
absence of a primary= directive.

The bonding kernel will, however, use the mac addr supplied
as an override.

So let's say the active interface was configured in MAAS to be
f0, and it's mac is used to be the mac address of the bond,
but f1 (the second port of the NIC) actually gets attached
first to the bond and is used as the active interface by the
bond.

We have a situation where f0 = backup, f1 = active, and bond0
is using the mac of f0. While this should work, there is a
potential for problems depending on the circumstances.

It's likely this has nothing to do with our current issue, but
here for completeness. Will see if we can test/confirm.

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

BTW, show-seconds also causes CPU spikes and frame stutters, so best to
avoid that for now.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/2085

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

> I installed appimagelauncher [1] some time ago and if I disable the
daemon and reboot then it seems the memory leak is no more.

Yes, please verify that. It's hard to imagine how that's relevant to
gnome-shell's memory usage, but one theory is that it is periodically
triggering code execution in gnome-shell that a default system would not
experience. This could happen via dbus interfaces, or by repeatedly
changing the set of installed apps. That would still be a gnome-shell
bug, but not a common one...

> I did already have show seconds set, I have now tried without and it
doesn't seem to make a difference

Can you please check that again, without show-seconds? That was my
strongest suspicion of why the leak continues on a desktop that's not
being used.

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2020-02-12 Thread Peter

I have the same issue but have not investigated further as yet.
I have recently upgraded however the issue was there before. I'm leaning toward 
a hardware issue.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

** Tags added: focal

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

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

** No longer affects: linux (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

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

Title:
  Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

Status in xorg-server package in Ubuntu:
  New

Bug description:
  If I run a thermal transition test script (30 seconds stress-ng, 30
  seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
  crashes, usually in the first couple of runs and almost 100% of the
  time by run 6.

  This appears to be hardware-linked, but not due to a specific piece of
  bad hardware: I have swapped literally every piece of hardware in the
  system.

  It shows up (while running the script at the end):
  - On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
  - On both an AMD Ryzen 5 3600 and 3600X CPU.
  - With one or two sticks of RAM. I've tested both sticks individually, in 
more than one mainboard slot.
  - Regardless of whether the mainboard is in/attached to a case.
  - Regardless of whether there is an m.2 SSD installed or I'm running off a 
live Kubuntu 19.10 USB stick with no hard disk attached.
  - Regardless of which of two mice I use (an old Logitech one, or a GTX 133 
Gaming mouse).
  - Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
  - Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia 
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
  - Regardless of whether I'm using KDE or XFCE.
  - Regardless of whether I'm using the default KDE DM or switch to GDM3 and 
set WaylandEnable=false.
  - Regardless of whether I use the default 5.3.0-29-generic kernel or 
5.4.17-050417-generic.
  - Regardless of whether I go directly into the graphical environment or start 
in runlevel 3 and then manually run startx.
  - Regardless of whether it's on the rising or falling edge of the 
stress-script's temperature changes.
  - Regardless of bios version on the X570 mainboard (the one it shipped with, 
or the newest one released in January 2020).
  - Regardless of whether XMP is on or off in the bios.
  - Regardless of whether I use the default or set global c-state to "control = 
disabled" in the bios.
  - Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
  - Regardless of whether or not speakers are plugged in.
  - Regardless of whether I'm using a USB port that is directly on the 
motherboard or is on the front of the case.
  - Regardless of which monitor it is attached to.

  It doesn't show up:
  - On an old i7-4771 machine I have, also running Kubuntu 19.10, while running 
the test script.
  - When I use a mouse remotely with ssh -Y [ip of the machine I am reporting 
this from] xeyes, while running the test script.
  - When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle, 
including under saturated network load, while running the test script.
  - During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, 
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
  - When the system is entirely idle aside from mouse movement.
  - When I start in runlevel 3 and run the same test script, using the mouse 
with gpm.
  - Running the same test script without mouse movement: this was stable 
overnight, then crashed within a couple of minutes of moving the mouse.

  It shows up with load other than the stress-ng+sleep script too, but
  much less reliably - I'm writing this bug report on the relevant
  machine, with firefox open. Crashes occur at least once a week under
  these conditions, but not frequently.

  Crashes occur with sensor-reported CPU temperatures of 32 to 41
  degrees Celsius. Nothing is overheating, and the system is stable at
  much higher temperatures under sustained stress tests.

  The symptoms of the crash: the display stops updating and the system
  does not respond to any further input, including via the network or
  magic sysrq key. There is nothing related to it in syslog or
  journalctl, including when I'm running journalctl -f at the time of
  the crash.

  The test script:
  #!/bin/bash
  for x in {1..1}
  do
  echo "Run $x at `date`"
  stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
  sleep 30
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.17-050417-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Feb  7 00:02:22 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:1e84] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology

[Desktop-packages] [Bug 1862792] Re: gnome-shell always crash after boot

Thanks, but unfortunately none of those are usable, for a variety of
reasons. Obviously we should ignore the crashes in google-chrome-stable
and cups-browsed here since this bug report is about gnome-shell
crashing. But the gnome-shell crashes are not usable for reasons like:

---

Invalid core dump: BFD: warning: /tmp/apport_core_getbxb5s is truncated:
expected core file size >= 1186811904, found: 249229312

---

You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:

usb-modeswitch

---

Please keep collecting crash reports as one of them should eventually be
useful. Please also try uninstalling these:

'dash-to-pa...@jderose9.github.com',
'sensory-percept...@harlemsquirrel.github.io',
'alternate-...@gnome-shell-extensions.gcampax.github.com',
'openweather-extens...@jenslody.de'

We need extensions to be uninstalled because we find a large number of
bugs are caused by extensions. And just disabling a buggy extension is
not enough to stop it from interfering.

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

Title:
  gnome-shell always crash after boot

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-shell always crash after boot with an UnreportableReason. This is in a 
Wayland session. 
  There are no stability issues after boot. 

  I get this information in the terminal after the command ubuntu-bug

  p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
  p-i@pi-asus-b450f-gaming:~$ 
[8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
  [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!

  ERROR:gl goes from 1 to 19.

  In Settings the Display is named Microstep 27"
  The problem might be hardware related:
  Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
  GPU: AMD Navi 10 Radeon RX 5700

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 11 16:43:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-08 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2)
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  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/1862792/+subscriptions

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  New
Status in hoel package in Ubuntu:
  New
Status in jabberd2 package in Ubuntu:
  New
Status in kannel package in Ubuntu:
  New
Status in libgda5 package in Ubuntu:
  New
Status in libodb-mysql package in Ubuntu:
  New
Status in lyricue package in Ubuntu:
  New
Status in motion package in Ubuntu:
  New
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  New
Status in mysqltcl package in Ubuntu:
  New
Status in opendnssec package in Ubuntu:
  New
Status in opensmtpd-extras package in Ubuntu:
  New
Status in orthanc-mysql package in Ubuntu:
  New
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  New
Status in gnokii package in Ubuntu:
  New
Status in hoel package in Ubuntu:
  New
Status in jabberd2 package in Ubuntu:
  New
Status in kannel package in Ubuntu:
  New
Status in libgda5 package in Ubuntu:
  New
Status in libodb-mysql package in Ubuntu:
  New
Status in lyricue package in Ubuntu:
  New
Status in motion package in Ubuntu:
  New
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  New
Status in mysqltcl package in Ubuntu:
  New
Status in opendnssec package in Ubuntu:
  New
Status in opensmtpd-extras package in Ubuntu:
  New
Status in orthanc-mysql package in Ubuntu:
  New
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

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

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

[Desktop-packages] [Bug 1724098]

Bug fixed by the new menu design in 3.35/3.36.

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Changed in: argus-clients (Ubuntu)
   Status: New => In Progress

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

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

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

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  New
Status in gerbera package in Ubuntu:
  New
Status in gnokii package in Ubuntu:
  New
Status in hoel package in Ubuntu:
  New
Status in jabberd2 package in Ubuntu:
  New
Status in kannel package in Ubuntu:
  New
Status in libgda5 package in Ubuntu:
  New
Status in libodb-mysql package in Ubuntu:
  New
Status in lyricue package in Ubuntu:
  New
Status in motion package in Ubuntu:
  New
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  New
Status in mysqltcl package in Ubuntu:
  New
Status in opendnssec package in Ubuntu:
  New
Status in opensmtpd-extras package in Ubuntu:
  New
Status in orthanc-mysql package in Ubuntu:
  New
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

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

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

[Desktop-packages] [Bug 1863026] [NEW] Remove my_bool typedef workaround

Public bug reported:

During the previous development cycle, when mysql 8 was introduced, too
many reverse deps failed due to the my_bool removal. It was then decided
to put that back in to let the reverse dependencies build again.

Now we should try to drop it one more time, and instead fix the reverse
dependencies. Either by updating them, if upstream fixed it, or
reintroducing only this my_bool typedef in the reverse dependency
itself, instead of in mysql as it's now.

This bug will track these tasks:
- remove my_bool workaround from Ubuntu's mysql 8 package
- fix the build of the reverse dependencies, each one a task of this bug.

PPA with test builds:
https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-removal

** Affects: argus-clients (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: libodb-mysql (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: mysql-8.0 (Ubuntu)
 Importance: High
 Assignee: Andreas Hasenack (ahasenack)
 Status: In Progress

** Affects: mysql-ocaml (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: opensmtpd-extras (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: orthanc-mysql (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: pike8.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Affects: voms-mysql-plugin (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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


** Tags: server-next

** Description changed:

  During the previous development cycle, when mysql 8 was introduced, too
  many reverse deps failed due to the my_bool removal. It was then decided
  to put that back in to let the reverse dependencies build again.
  
  Now we should try to drop it one more time, and instead fix the reverse
  dependencies. Either by updating them, if upstream fixed it, or
  reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.
  
  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.
+ 
+ PPA with test builds:
+ https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-removal

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

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

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

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

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

** Also affects: argus-clients (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mysql-ocaml (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Also

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

I think this may not be a gnome-shell issue at all.  I installed 
appimagelauncher [1] some time ago and if I disable the daemon and reboot then 
it seems the memory leak is no more.  At least I think that is the case, I need 
to do some more testing but thought I should report back immediately so that 
no-one wastes any more time on it.
I will follow up when I have reached a firm conclusion.

[1] https://github.com/TheAssassin/AppImageLauncher

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1316399] Re: Podcast episodes deleted if "played" while waiting for download

2020-02-12 Thread Paul White

Thanks for that confirmation.
I couldn't reproduce it either so closing.

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

Title:
  Podcast episodes deleted if "played" while waiting for download

Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:

  1) Find a podcast that (a) has at least three episodes in it and (b) has
 episodes that are sufficiently long that you can perform step (5)
 below while waiting for one to download.  (I encountered this bug on
 , which is the podcast for
 the U.S.A. radio show "Wait Wait Don't Tell Me" by NPR).
  2) Subscribe to the podcast (i.e. select "Podcasts" under "Library",
 click "Add", enter the URL in the search box, click "Search", click
 "Subscribe", and click "Close".).
  3) Rhythmbox will download only the most recent episode.  Wait for that
 download to complete.
  4) Select at two of the older (not yet downloaded) episodes with
 ctrl-click.  Then right-click on the selected episodes and choose
 "download episode" from the context menu.  Rhythmbox will start
 downloading one episode and mark the other as "waiting".
  5) Before that download completes, double-click on the "waiting" episode.

  Results:
  1) The double-clicked episode immediately starts playing, but it still
 displays its status as "waiting".  The existing download is not
 interrupted.
  2) When the existing download completes, the double-clicked episode
 continues to play but also starts "downloading", apparently from the
 beginning.
  3) When the double-clicked episode finishes downloading, it abruptly
 stops playing and then disappears from the episode list.  After this,
 the episode is no longer visible anywhere in Rhythmbox.  This
 persists even after a restart.

  Expected result: Not sure what I would expect, but episodes most
  certainly should not be getting deleted. ;)

  The attached 'rbx.log' contains the output of 'rhythmbox -d' when
  performing the performing the procedure described above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May  5 23:57:48 2014
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to trusty on 2014-04-15 (20 days ago)

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

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

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

2020-02-12 Thread Bruce Copeland

Sergey, I think you might be onto something. I use a yubikey and have
PAM configured to detect the yubikey automatically for sudo. So it could
be a timing issue as you suggest, or maybe GNOME is making inappropriate
assumptions about whether authentication requires actual user input.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-12 Thread Jonathan Hartley

For others with similar problems, I'm keeping my findings up to date
here: https://www.tartley.com/dina-as-otf

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  gnome-font-viewer does not list any of the installed bitmap fonts.

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

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

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

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

2020-02-12 Thread Sergey Zolotorev

Just want to add five cents: I am not active user of Ubuntu right now
but I faced with the same issue in many other versions of GNOME in other
distributions (currently I suffer from this issue in Arch Linux). I
suspect that it caused by custom PAM modules which add to authorization
process some delays (in my case this module is pam_yubico which waits
for user action) but I still do not have a chance to check it.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

2020-02-12 Thread Luke Barone-Adesi

The problem does not show up on "Ubuntu on Wayland" (as judged by 20
minutes of moving the mouse while running the stress-ng script in the
first post).

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

Title:
  Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  If I run a thermal transition test script (30 seconds stress-ng, 30
  seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
  crashes, usually in the first couple of runs and almost 100% of the
  time by run 6.

  This appears to be hardware-linked, but not due to a specific piece of
  bad hardware: I have swapped literally every piece of hardware in the
  system.

  It shows up (while running the script at the end):
  - On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
  - On both an AMD Ryzen 5 3600 and 3600X CPU.
  - With one or two sticks of RAM. I've tested both sticks individually, in 
more than one mainboard slot.
  - Regardless of whether the mainboard is in/attached to a case.
  - Regardless of whether there is an m.2 SSD installed or I'm running off a 
live Kubuntu 19.10 USB stick with no hard disk attached.
  - Regardless of which of two mice I use (an old Logitech one, or a GTX 133 
Gaming mouse).
  - Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
  - Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia 
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
  - Regardless of whether I'm using KDE or XFCE.
  - Regardless of whether I'm using the default KDE DM or switch to GDM3 and 
set WaylandEnable=false.
  - Regardless of whether I use the default 5.3.0-29-generic kernel or 
5.4.17-050417-generic.
  - Regardless of whether I go directly into the graphical environment or start 
in runlevel 3 and then manually run startx.
  - Regardless of whether it's on the rising or falling edge of the 
stress-script's temperature changes.
  - Regardless of bios version on the X570 mainboard (the one it shipped with, 
or the newest one released in January 2020).
  - Regardless of whether XMP is on or off in the bios.
  - Regardless of whether I use the default or set global c-state to "control = 
disabled" in the bios.
  - Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
  - Regardless of whether or not speakers are plugged in.
  - Regardless of whether I'm using a USB port that is directly on the 
motherboard or is on the front of the case.
  - Regardless of which monitor it is attached to.

  It doesn't show up:
  - On an old i7-4771 machine I have, also running Kubuntu 19.10, while running 
the test script.
  - When I use a mouse remotely with ssh -Y [ip of the machine I am reporting 
this from] xeyes, while running the test script.
  - When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle, 
including under saturated network load, while running the test script.
  - During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, 
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
  - When the system is entirely idle aside from mouse movement.
  - When I start in runlevel 3 and run the same test script, using the mouse 
with gpm.
  - Running the same test script without mouse movement: this was stable 
overnight, then crashed within a couple of minutes of moving the mouse.

  It shows up with load other than the stress-ng+sleep script too, but
  much less reliably - I'm writing this bug report on the relevant
  machine, with firefox open. Crashes occur at least once a week under
  these conditions, but not frequently.

  Crashes occur with sensor-reported CPU temperatures of 32 to 41
  degrees Celsius. Nothing is overheating, and the system is stable at
  much higher temperatures under sustained stress tests.

  The symptoms of the crash: the display stops updating and the system
  does not respond to any further input, including via the network or
  magic sysrq key. There is nothing related to it in syslog or
  journalctl, including when I'm running journalctl -f at the time of
  the crash.

  The test script:
  #!/bin/bash
  for x in {1..1}
  do
  echo "Run $x at `date`"
  stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
  sleep 30
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.17-050417-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Feb  7 00:02:22 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA

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

2020-02-12 Thread Bruce Copeland

This morning, I managed to trigger this bug again. I installed a new
component from the Activities/Search view. The component installed
without requiring any authentication, but 30 minutes later, the
offending authentication dialog image appeared on the screen.

I believe there are probably two different bugs here:

1. In the ubuntu software install, there is probably a thread
synchronization defect that allows software to install without
authentication.

2. Separately gnome shell appears to paint widgets even though there is
apparently no logic/process attached to the widget.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1862855] Re: "file does not exist" for existing files

2020-02-12 Thread Moses Moore

It's the snap: 
 Name: libreoffice
 Version: 6.4.0.3
 Rev: 170
 Tracking: stable
 Publisher: canonical

I don't know how to report a bug for snap packages published by
Canonical.  If this is working as intended then... :shrug:  broke the
Rule Of Least Surprise but that was probably as intended.

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

Title:
  "file does not exist" for existing files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice reports files are missing when trying to open them from anywhere 
but $HOME/Documents/
  May be related to Ubuntu moving libreoffice to be a snap package.

  How to reproduce:
  $ echo "anything at all" >/tmp/testfile.txt
  $ libreoffice /tmp/testfile.txt

  Expected:
  LibreOffice Writer starts, or I'm prompted for whether I wanted to use 
--writer or --calc

  Seen:
  error message "/tmp/testfile.txt does not exist"

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 11 18:14:58 2020
  InstallationDate: Installed on 2018-10-30 (469 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to eoan on 2019-11-14 (89 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709

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

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

[Desktop-packages] [Bug 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap

2020-02-12 Thread Mantas Kriaučiūnas

Current situation about this issue is described and fixed in bug
#1863001

** Changed in: baltix
   Status: New => Triaged

** Changed in: baltix
   Status: Triaged => In Progress

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

Title:
  Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap

Status in xkeyboard-config package in Ubuntu:
  New
Status in Baltix:
  In Progress

Bug description:
  Binary package hint: xkeyboard-config

  Main lithuanian layout has no EURO symbol.

  Main lithuanian layout should have EURO symbol on key "e" (alt gr +
  e), like other layouts "Lithuanian US", "Lithuanian IBM", "Lihuanian
  Standard"  has it on key "e". Windows OS it is also on key "e".

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

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

[Desktop-packages] [Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.

2020-02-12 Thread S Jaker

A viable work around seems to be increasing shared memory via the
sysctl.conf file and opening a small (?KB) image before opening a larger
(?MB) image. This does cause a noticable system lag when the mouse
cursor passes over the rendered image window.

add the following line:

kernel.shmmax = 1073741824

then execute:

sudo sysctl -p

...

This solution does NOT always work if a small image has not first been
opened. Looking through the source code, it appears the cairo routines
find exhausted shared memory pool and return a NULL ptr. Why opening a
small image first seems to help? I have no idea.

Version 3.18.1 on 16.04 LTS does not have this issue.

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

Title:
  eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619:
  _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  I opened an image.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: 
_cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 16:22:00 2019
  ExecutablePath: /usr/bin/eog
  ExecutableTimestamp: 1523677004
  InstallationDate: Installed on 2017-03-13 (874 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg
  ProcCwd: /home/mircea
  Signal: 6
  SourcePackage: eog
  StacktraceTop:
   __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", 
file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", 
line=line@entry=619, function=function@entry=0x7fac8c0cead0 
"_cairo_xlib_shm_pool_create") at assert.c:92
   __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", 
file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, 
function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: 
_cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1862855] Re: "file does not exist" for existing files

2020-02-12 Thread Heather Ellsworth

Thanks for the report! First off, what version of libreoffice are you
using? Your system info says "Package: libreoffice (not installed)".
What version is in the libreoffice -> Help -> About libreoffice ?

If you're using the deb that is provided in the 19.10 update archives,
then that should be 6.3.4-0ubuntu0.19.10.1, and running libreoffice
/tmp/testfile.txt should open writer.

If you're using the snap, then that is 6.4.0.3 and the snap does not
have access to /tmp. Because it's an isolated app package, the snap has
access to $HOME and /snap/libreoffice/current.

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

Title:
  "file does not exist" for existing files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice reports files are missing when trying to open them from anywhere 
but $HOME/Documents/
  May be related to Ubuntu moving libreoffice to be a snap package.

  How to reproduce:
  $ echo "anything at all" >/tmp/testfile.txt
  $ libreoffice /tmp/testfile.txt

  Expected:
  LibreOffice Writer starts, or I'm prompted for whether I wanted to use 
--writer or --calc

  Seen:
  error message "/tmp/testfile.txt does not exist"

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 11 18:14:58 2020
  InstallationDate: Installed on 2018-10-30 (469 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to eoan on 2019-11-14 (89 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709

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

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

[Desktop-packages] [Bug 1316399] Re: Podcast episodes deleted if "played" while waiting for download

2020-02-12 Thread crvi

not reproducible in version 3.4.4

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

Title:
  Podcast episodes deleted if "played" while waiting for download

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  To reproduce:

  1) Find a podcast that (a) has at least three episodes in it and (b) has
 episodes that are sufficiently long that you can perform step (5)
 below while waiting for one to download.  (I encountered this bug on
 , which is the podcast for
 the U.S.A. radio show "Wait Wait Don't Tell Me" by NPR).
  2) Subscribe to the podcast (i.e. select "Podcasts" under "Library",
 click "Add", enter the URL in the search box, click "Search", click
 "Subscribe", and click "Close".).
  3) Rhythmbox will download only the most recent episode.  Wait for that
 download to complete.
  4) Select at two of the older (not yet downloaded) episodes with
 ctrl-click.  Then right-click on the selected episodes and choose
 "download episode" from the context menu.  Rhythmbox will start
 downloading one episode and mark the other as "waiting".
  5) Before that download completes, double-click on the "waiting" episode.

  Results:
  1) The double-clicked episode immediately starts playing, but it still
 displays its status as "waiting".  The existing download is not
 interrupted.
  2) When the existing download completes, the double-clicked episode
 continues to play but also starts "downloading", apparently from the
 beginning.
  3) When the double-clicked episode finishes downloading, it abruptly
 stops playing and then disappears from the episode list.  After this,
 the episode is no longer visible anywhere in Rhythmbox.  This
 persists even after a restart.

  Expected result: Not sure what I would expect, but episodes most
  certainly should not be getting deleted. ;)

  The attached 'rbx.log' contains the output of 'rhythmbox -d' when
  performing the performing the procedure described above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May  5 23:57:48 2014
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to trusty on 2014-04-15 (20 days ago)

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

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

[Desktop-packages] [Bug 1862926] Re: Request for update: SANE 1.0.29

2020-02-12 Thread Till Kamppeter

Also reported to Debian as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=951213

** Bug watch added: Debian Bug tracker #951213
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951213

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

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  New

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
 + adds an escl backend (theoretically supporting all AirPrint devices with 
a scan unit
 + adds support for 23 new scanner models via existing backends
 + significantly changes genesys and pixma backends
 + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and 
xerox_mfp backends
 + fixes all compiler warnings on Debian 10 (#120)
 + fixes portability issues for uClibc-ng and MacOS builds
 + adds support to record and replay USB I/O traffic
 + adds timestamps to debug logs

  debdiff attached.

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

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

[Desktop-packages] [Bug 1862969] [NEW] On SystemReboot wifi failed to connect on tplink wifi adapter

2020-02-12 Thread FeaturizSudhakar

Public bug reported:

I'm using Ubuntu 19.10 64bit for my PC. For network/wifi I'm using TP-
Link wifi adapter.

My network works only when I do a fresh start (That is completely shutdown and 
start).
But network connection fails to connect to my wifi on REBOOT(on system software 
updates , etc..).

After reboot:
1. I can see my mobile device(wifi service providing) name in the list at WIFI 
SETTINGS -> VISIBLE NETWORKS.
2. BUT IT FAILS TO CONNECT. It tries many times and finally says , CANT CONNECT.

I searched GOOGLE, UBUNTU FORMS, but I failed to find the solution.


As per now solution:
After reboot , I have to shutdown pc again and do a boot. To make wifi connect.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  On SystemReboot wifi failed to connect on tplink wifi adapter

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 19.10 64bit for my PC. For network/wifi I'm using TP-
  Link wifi adapter.

  My network works only when I do a fresh start (That is completely shutdown 
and start).
  But network connection fails to connect to my wifi on REBOOT(on system 
software updates , etc..).

  After reboot:
  1. I can see my mobile device(wifi service providing) name in the list at 
WIFI SETTINGS -> VISIBLE NETWORKS.
  2. BUT IT FAILS TO CONNECT. It tries many times and finally says , CANT 
CONNECT.

  I searched GOOGLE, UBUNTU FORMS, but I failed to find the solution.

  
  As per now solution:
  After reboot , I have to shutdown pc again and do a boot. To make wifi 
connect.

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

2020-02-12 Thread Ppaalanen

I tested with a Dell D3100 dock and two monitors connected to the dock
via HDMI in addition to laptop built-in screen. I did this on Ubuntu
19.10 with the libmutter fix from eoan-proposed (libmutter-5-0 package
version 3.34.3-1ubuntu1~19.10.1).

I tried unplugging and hotplugging each HDMI cable individually and
together. I tried hotplugging and unplugging the dock itself (USB). I
tried booting with the dock connected, and booting with the dock
disconnected then hotplugged.

With all three monitors on, I left one glxgears running on one
DisplayLink output and the laptop screen each, and a terminal printing
the fps on the other DL output for 10 minutes. Then I changed the
refresh rate of one DL output to 50 Hz and the other DL output to 75 Hz,
confirmed from the monitors themselves to actually run with those
refresh rates, and left things running for a couple of minutes more.
(Everything defaulted to 60 Hz before.)

I was unable to reproduce any kind of freeze.

However, I did notice that with three monitors, gnome-control-center
Display settings is crash-happy if any monitor was disabled. But that is
off-topic here, because even that did not cause anything to freeze.

I did also observe the "outdated content" issue I referred to in my
earlier comment here. That should be fixed in EVDI kernel module once
DisplayLink releases an update.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-12 Thread Eric Desrochers

This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35


A test package (including the above fix) is available on my PPA:
sudo add-apt-repository ppa:slashd/lp1794478
sudo apt-get update

Please let me know the outcome.

- Eric

** Bug watch added: Red Hat Bugzilla #1575944
   https://bugzilla.redhat.com/show_bug.cgi?id=1575944

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions

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

[Desktop-packages] [Bug 1862959] Re: remmina crashed with SIGSEGV

2020-02-12 Thread Apport retracing service

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

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 #1859485, 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/1862959/+attachment/5327659/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1859485
   remmina crashed with SIGSEGV

** 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 remmina in Ubuntu.
https://bugs.launchpad.net/bugs/1862959

Title:
  remmina crashed with SIGSEGV

Status in remmina package in Ubuntu:
  New

Bug description:
  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.3.10+dfsg-1ubuntu2
  Uname: Linux 5.5.3-050503-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 11 15:18:00 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-12-02 (436 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: remmina
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f5e60c6da80:mov(%rax),%edx
   PC (0x7f5e60c6da80) ok
   source "(%rax)" (0x7f5e3c346854) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: remmina crashed with SIGSEGV
  UpgradeStatus: Upgraded to focal on 2018-12-02 (436 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

** Attachment added: "glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327670/+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/1862910

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327669/+files/lspcik.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/1862910

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

1. Screenshot attached. I have been using two screens but to simplify
things I have confirmed that only having one makes no difference, so I
am sticking to that whilst testing.

2. I did already have show seconds set, I have now tried without and it
doesn't seem to make a difference

3. I thought I had disabled all extensions, though I am not entirely
sure of the official method of doing that. If I go to
https://extensions.gnome.org/local/ I see only Desktop Icons, Ubuntu App
Indicators and Ubuntu Dock and they are all disabled, but as you can see
from the screenshot I don't see exactly the same as I see if I logon
using Gnome. For instance the Dock is not autohiding. So I don't know
what is going on there. Logging on using Gnome does not stop the leak
though.

I see I have a larger selection of logon options than I see in a clean
install, I have Gnome, Gnome Classic, Gnome on Xorg, Ubuntu, Ubuntu on
Wayland, and Unity. I tried them all a few days ago and they all
exhibited the leak except Gnome Classic and Unity, though I have done a
lot of cleaning up trying to fix the problem since then so if it would
be useful I can repeat that test.

** Attachment added: "Desktop screenshot"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327658/+files/Screenshot%20from%202020-02-12%2014-02-37.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/1862910

Title:
gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
On one of my machines which has been upgraded over several years and
is now running 19.10 just one of the configured users appears to be
seeing a dramatic memory leak in gnome-shell, even when nothing is
happening on the UI. Immediately after logging on, using the Ubuntu
selection from the logon screen, gnome shell shows as using about
134MB. From there it climbs at about 300MB per hour and after a few
hours the machine grinds to a crawl, not surprisingly. This happens
even if the user logs on and then the machine is left completely
alone. Logout and back in frees all the memory.
A test user I have configured sees no such problem.
I have uninstalled all extensions apart from the system ones, disabled
all the system ones and reset all the gnome settings using dconf reset
-f /org/gnome/ to no avail. Also I have removed
~/.local/share/gnome-shell and allowed it to recreate it.
Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
I can't see anything obvious in the log.
It must be something in my settings that is triggering it as the other
user does not see it, but I have run out of ideas on what to try.

[Desktop-packages] [Bug 1861882] Re: Shift key cancels accented IME input with fcitx

2020-02-12 Thread T.D. Stoneheart

** Description changed:

  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1
  
  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.
  
  Expected result:
- * Nothing happens, or the typed character should not change, to the very 
least.
+ * Nothing happens, or the typed character should not change, at the very 
least.
  
  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).
  
  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, version 79.
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.

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

Title:
  Shift key cancels accented IME input with fcitx

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1

  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.

  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.

  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).

  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, version 79.
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.

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

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

[Desktop-packages] [Bug 1862945] [NEW] Change desktop - select color no longer possible

2020-02-12 Thread corrado venturini

Public bug reported:

Open control center - settings - set background - select a solid color
is not possible also if stated in the help.

Change the desktop and lock screen backgrounds
You can change the image used for your backgrounds or set it to be a solid 
color.

corrado@corrado-x5-ff-0104:~$ inxi -Fxx
System:Host: corrado-x5-ff-0104 Kernel: 5.4.0-12-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 
   Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 Distro: Ubuntu 20.04 
LTS (Focal Fossa) 
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
   date: 05/11/2017 
CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 
   L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
   Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 803 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 chip ID: 8086:5912 
   Display: x11 server: X.Org 1.20.7 driver: i915 compositor: 
gnome-shell resolution: 1920x1080~60Hz 
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 
4.6 Mesa 19.3.3 compat-v: 3.0 
   direct render: Yes 
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
   bus ID: 00:1f.3 chip ID: 8086:a170 
   Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-10:5 
   chip ID: 046d:0990 
   Sound Server: ALSA v: k5.4.0-12-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
   chip ID: 8086:15b8 
   IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
Drives:Local Storage: total: 2.05 TiB used: 12.48 GiB (0.6%) 
   ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB speed: 31.6 Gb/s lanes: 4 
   serial: 50026B72823D1475 
   ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
speed: 6.0 Gb/s serial: 37PYNGAFS 
   ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB speed: 3.0 Gb/s 
   serial: JP2940J80Z3D3V 
Partition: ID-1: / size: 31.25 GiB used: 12.48 GiB (39.9%) fs: ext4 dev: 
/dev/nvme0n1p5 
   ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 27.0 C mobo: 29.5 C 
   Fan Speeds (RPM): fan-1: 0 fan-2: 2343 fan-3: 0 fan-4: 2268 fan-5: 0 
fan-6: 0 
   Voltages: 12v: N/A 5v: N/A 3.3v: 3.49 vbat: 3.15 
Info:  Processes: 219 Uptime: 24m Memory: 7.49 GiB used: 1.24 GiB (16.6%) 
Init: systemd v: 244 runlevel: 5 
   Compilers: gcc: 9.2.1 alt: 9 Shell: bash v: 5.0.11 running in: 
gnome-terminal inxi: 3.0.37 
corrado@corrado-x5-ff-0104:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.35.90-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 12 14:30:09 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-01-04 (39 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Change desktop - select color no longer possible

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

Bug description:
  Open control center - settings - set background - select a solid color
  is not possible also if stated in the help.

  Change the desktop and lock screen backgrounds
  You can change the image used for your backgrounds or set it to be a solid 
color.

  corrado@corrado-x5-ff-0104:~$ inxi -Fxx
  System:Host: corrado-x5-ff-0104 Kernel: 5.4.0-12-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 
 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 Distro: Ubuntu 
20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4:

Re: [Desktop-packages] [Bug 1862792] Re: gnome-shell always crash after boot

2020-02-12 Thread Per-Inge

This is the result:

Error reports sent from this system
Occurred Received Problem Type Program
2020-02-11 19:02 2020-02-11 18:02 UTC Crash gnome-shell
2020-02-11 06:02 2020-02-11 05:02 UTC Crash gnome-shell
2020-02-10 11:02 2020-02-10 11:02 UTC Crash gnome-shell
2020-02-09 12:02 2020-02-09 12:02 UTC Crash gnome-shell
2020-02-08 09:02 2020-02-08 08:02 UTC Crash gnome-shell
2020-02-03 17:02 2020-02-03 16:02 UTC Crash /usr/lib/xorg/Xorg
2020-02-03 07:02 2020-02-03 07:02 UTC Crash /usr/lib/xorg/Xorg
2020-01-24 15:01 2020-01-24 14:01 UTC Crash google-chrome-stable
2020-01-17 21:01 2020-01-17 20:01 UTC Crash gnome-shell
2020-01-13 18:01 2020-01-13 17:01 UTC Crash cups-browsed
2019-12-30 21:12 2019-12-30 20:12 UTC Crash google-chrome-stable
2019-12-27 19:12 2019-12-27 18:12 UTC Crash google-chrome-stable
2019-12-27 12:12 2019-12-27 13:12 UTC Crash cups-browsed

These are the links:
https://errors.ubuntu.com/oops/31013d32-4cfd-11ea-a96b-fa163e983629
https://errors.ubuntu.com/oops/8269e776-4c91-11ea-a07a-fa163e6cac46
https://errors.ubuntu.com/oops/e4e4e6ec-4bfa-11ea-a95c-fa163e983629
https://errors.ubuntu.com/oops/5f9cd9b2-4b3b-11ea-a957-fa163e983629
https://errors.ubuntu.com/oops/650b32dc-4a4e-11ea-a953-fa163e983629
https://errors.ubuntu.com/oops/234b0822-46a3-11ea-aa47-fa163e6cac46
https://errors.ubuntu.com/oops/b2bebda8-4655-11ea-b902-fa163e102db1
https://errors.ubuntu.com/oops/65f83450-3eb8-11ea-a7c8-fa163ee63de6
https://errors.ubuntu.com/oops/a46d4394-3966-11ea-b219-fa163e983629
https://errors.ubuntu.com/oops/cb2e2fc2-3626-11ea-b89d-fa163e102db1
https://errors.ubuntu.com/oops/e2494484-2b44-11ea-a75f-fa163ee63de6
https://errors.ubuntu.com/oops/b45882ec-28d8-11ea-b84d-fa163e102db1
https://errors.ubuntu.com/oops/70a7627c-28b0-11ea-b1c1-fa163e983629

Den ons 12 feb. 2020 kl 03:20 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:

> It sounds like the main issue is that Xwayland has crashed first:
>
> [   31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to
> xwayland lost
>
> Please follow the steps in comment #2 to help us diagnose the problem
> further.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1862792
>
> Title:
>   gnome-shell always crash after boot
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   gnome-shell always crash after boot with an UnreportableReason. This is
> in a Wayland session.
>   There are no stability issues after boot.
>
>   I get this information in the terminal after the command ubuntu-bug
>
>   p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
>   p-i@pi-asus-b450f-gaming:~$
> [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID
> data: manufacturer id
>   [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)]
> InitializeSandbox() called with multiple threads in process gpu-process.
>
> [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)]
> GetVSyncParametersIfAvailable() failed for 1 times!
>
>   ERROR:gl goes from 1 to 19.
>
>   In Settings the Display is named Microstep 27"
>   The problem might be hardware related:
>   Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
>   GPU: AMD Navi 10 Radeon RX 5700
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.34.3-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
>   Uname: Linux 5.4.0-12-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu16
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 11 16:43:08 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-02-08 (3 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200207.2)
>   RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
>   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/1862792/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell always crash after boot

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-shell always crash after boot with an UnreportableReason. This is in a 
Wayland session. 
  There are no stability issues after boot. 

  I get this information in the terminal after the command ubuntu-bug

  p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
  p-i@pi-asus-b450f-gaming:~$ 
[8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
  [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)]

[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

2020-02-12 Thread Silvan Geissmann

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

Same here on Linux CH-W-7269416 5.3.0-28-generic #30~18.04.1-Ubuntu SMP
Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux


Device 04:5D:4B:99:46:9C (public)
Name: WH-1000XM2
Alias: WH-1000XM2
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
UUID: Vendor specific   (96cc203e-5068-46ad-b32d-e316f5e069ba)
UUID: Vendor specific   (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
Modalias: usb:v054Cp0C67d0105

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

I would also like to know more about your GPU/driver configuration, in
case the problem is unique to a particular driver.

Please run:

  lspci -k > lspcik.txt

and attach the resulting file here.

Please also run:

  sudo apt install mesa-utils
  glxinfo > glxinfo.txt

and attach the resulting file here.

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory

I would like to understand if there's something about your system
triggering these leaks that most of us don't encounter.

Please:

1. Take a screenshot of your whole Ubuntu desktop (all monitors) that is
experiencing the problem and attach it here.

2. Try setting this to false:

   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'

   and run the leak test again.

3. Try disabling ALL Ubuntu extensions, or just try a raw GNOME session
which should be the same:

   sudo apt install gnome-session

   and choose GNOME on the login screen.


   

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow

2020-02-12 Thread Pablo Copissa

Looks like gio is part of glib, not gvfs, so changed the package accordingly. 
Also made clear in the title that gio vs mount is part of the issue.

** Package changed: gvfs (Ubuntu) => glib2.0 (Ubuntu)

** Summary changed:

- Browsing smb share is painfully slow
+ Browsing smb share is painfully slow when mounted via "gio" (compared with 
"mount")

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.

  Hope this helps

  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)

  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).

  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

  $ gio mount smb://nas.example.com/share2

  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path

  $ time ls

  ... 528 subdirs approximately ...

  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s

  $ time ls | wc
  5281631   10893

  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s

  Factor is about 50.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1862264/+subscriptions

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

[Desktop-packages] [Bug 1264115] Re: Gedit hangs while searching in large file

2020-02-12 Thread Ge

the same with Ubuntu v. 16.04 ->
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1862924

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

Title:
  Gedit hangs while searching in large file

Status in gedit:
  Confirmed
Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  When I did a search in Gedit with a large text file (about 101 KB), the 
editor hangs and used high CPU load. 
  When I shut down the application, a dialog box appears: The Window 
"history.log (/var/log/apt) - gedit" is not respondig. This dialog box is 
attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 25 14:24:16 2013
  InstallationDate: Installed on 2013-12-20 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2020-02-12 Thread Till Kamppeter

I have started to address remedy 3: bug 1862926.

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

Title:
  package python3 3.6.5-3 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in HPLIP:
  Invalid
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hello, error came up while updating. Paketmanager has canceled the
  update completely. Not yet analyzed for errors with console ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 00:01:23 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago)

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

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow

2020-02-12 Thread Pablo Copissa

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

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

Title:
  Browsing smb share is painfully slow

Status in gvfs package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.

  Hope this helps

  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)

  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).

  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

  $ gio mount smb://nas.example.com/share2

  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path

  $ time ls

  ... 528 subdirs approximately ...

  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s

  $ time ls | wc
  5281631   10893

  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s

  Factor is about 50.

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

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

[Desktop-packages] [Bug 1862924] Re: Gedit hangs while searching in large file Edit @ ubuntu 16.04

2020-02-12 Thread Ge

80k json-file attached...

** Attachment added: "_nodes.json"
   
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1862924/+attachment/5327643/+files/_nodes.json

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

Title:
  Gedit hangs while searching in large file Edit @ ubuntu 16.04

Status in gedit package in Ubuntu:
  New

Bug description:
  the same B after 7 (!) years
  REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115

  {
  $ uname -a
  Linux LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  }

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

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

[Desktop-packages] [Bug 1862926] [NEW] Request for update: SANE 1.0.29

2020-02-12 Thread Till Kamppeter

Public bug reported:

In Focal we are still a bit old-fashioned regarding scanning. We are
still at the ancient SANE 1.0.27! That is really INSANE.

Current version is 1.0.29 and it contains a very important new feature
which will make hundreds (thousands?) of new scanners work with Ubuntu.
This new feature is Apple AirScan support as a client. I have introduced
a lot of nice printing stuff to support AirPrint, making lots of
printers (practically all modern network printers) working, and all the
multi-function devices under these (printer and scanner in one) do
AirScan, so all these scanner will work with SANE 1.0.29 (if yours does
not, it is a bug in SANE, please report).

The AirScan support is provided by the new "escl" backend. supporting
the eSCL protocol AirPrint is based on. The protocol uses HTTP and XML,
so this works out-of-the-box if your printer is connected to the
network, if it is connected via USB it work via IPP-over-USB using the
ippusbxd package.

Changes list from upstream:

- Backends
+ adds an escl backend (theoretically supporting all AirPrint devices with a
scan unit
+ adds support for 23 new scanner models via existing backends
+ significantly changes genesys and pixma backends
+ fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and
xerox_mfp backends
+ fixes all compiler warnings on Debian 10 (#120)
+ fixes portability issues for uClibc-ng and MacOS builds
+ adds support to record and replay USB I/O traffic
+ adds timestamps to debug logs

debdiff attached.

** Affects: sane-backends (Ubuntu)
Importance: High
Status: New

** Patch added: "sane-backends_1.0.27-3.2ubuntu4_1.0.29-0ubuntu1.debdiff"

https://bugs.launchpad.net/bugs/1862926/+attachment/5327642/+files/sane-backends_1.0.27-3.2ubuntu4_1.0.29-0ubuntu1.debdiff

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

Title:
Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
New

Bug description:
In Focal we are still a bit old-fashioned regarding scanning. We are
still at the ancient SANE 1.0.27! That is really INSANE.

Current version is 1.0.29 and it contains a very important new feature
which will make hundreds (thousands?) of new scanners work with
Ubuntu. This new feature is Apple AirScan support as a client. I have
introduced a lot of nice printing stuff to support AirPrint, making
lots of printers (practically all modern network printers) working,
and all the multi-function devices under these (printer and scanner in
one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
yours does not, it is a bug in SANE, please report).

The AirScan support is provided by the new "escl" backend. supporting
the eSCL protocol AirPrint is based on. The protocol uses HTTP and
XML, so this works out-of-the-box if your printer is connected to the
network, if it is connected via USB it work via IPP-over-USB using the
ippusbxd package.

Changes list from upstream:

- Backends
+ adds an escl backend (theoretically supporting all AirPrint devices with
a scan unit
+ adds support for 23 new scanner models via existing backends
+ significantly changes genesys and pixma backends
+ fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and
xerox_mfp backends
+ fixes all compiler warnings on Debian 10 (#120)
+ fixes portability issues for uClibc-ng and MacOS builds
+ adds support to record and replay USB I/O traffic
+ adds timestamps to debug logs

debdiff attached.

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

[Desktop-packages] [Bug 1862264] [NEW] Browsing smb share is painfully slow

You have been subscribed to a public bug:

Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
TEST #1:
To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
$ sudo mount -t cifs -o username=pablo //myserver.example.com/share ~/mnt/share
$ cd ~/mnt/share/some/dir
$ time ls
... approx 320 files ...
real0m1,080s
user0m0,008s
sys 0m0,005s
$ sudo umount ~/mnt/share

TEST #2
Now we do the same via gio mount:
$ gio mount smb://myserver.example.com/share
cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
$ time ls
... same 320 files ...
real0m28,999s
user0m0,013s
sys 0m0,032s

Enumeration of files is about 29 times slower when mounted via gio mount
than via mount -t cifs.

TEST #3
Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
$ time ls | wc
   321 3239804

real0m0,546s
user0m0,006s
sys 0m0,004s

Note that this is almost TWICE AS FAST than the "fast" mount of test #1
and about 53 times faster than "slow" test #2 !

The expectation is that Tests 1 and 2 should have similar timings, not
differing by a factor of 30 or so. More disturbing, there is no good
reason why tests 2 and 3 differ by an even bigger factor of 53: They use
the same underlying infrastructure which test 3 proves is adequately
fast. And yet, we get this slow down in test 2.

As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
The same timing difference is of course visible in any file manager.

Hope this helps

PS: several old/ancient bug reports exist for a similar issue and I
deliberately copied the title from one of them (#259771)

PS2: may or may not be relevant: The remote server is a VM running
Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
stock SSTP).

PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

$ gio mount smb://nas.example.com/share2

$ cd /run/user/1000/gvfs/smb-
share\:server\=nas.example.com\,share\=share2/another/path

$ time ls

... 528 subdirs approximately ...

real0m45,075s
user0m0,013s
sys 0m0,058s

$ time ls | wc
5281631   10893

real0m0,911s
user0m0,003s
sys 0m0,005s

Factor is about 50.

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


** Tags: bot-comment
-- 
Browsing smb share is painfully slow
https://bugs.launchpad.net/bugs/1862264
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gvfs 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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

2020-02-12 Thread AJenbo

This issue is present in 20.04. I'm mainly seeing it in CodeLite
(probably because that is where I spend all my time), but one
interesting thing is that it also affects VMs (Ubuntu 18.04) running in
Boxes with shared copy paste.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1862924] [NEW] Gedit hangs while searching in large file Edit @ ubuntu 16.04

2020-02-12 Thread Ge

Public bug reported:

the same B after 7 (!) years
REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115

{
$ uname -a
Linux LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
}

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

** Description changed:

  the same B after 7 (!) years
+ REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115

** Description changed:

  the same B after 7 (!) years
  REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115
+ 
+ {{{
+ $ uname -a
+ Linux i1-LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+ }}}

** Description changed:

  the same B after 7 (!) years
  REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115
  
- {{{
+ {
  $ uname -a
  Linux i1-LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
- }}}
+ }

** Description changed:

  the same B after 7 (!) years
  REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115
  
  {
  $ uname -a
- Linux i1-LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+ Linux LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  }

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

Title:
  Gedit hangs while searching in large file Edit @ ubuntu 16.04

Status in gedit package in Ubuntu:
  New

Bug description:
  the same B after 7 (!) years
  REF: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264115

  {
  $ uname -a
  Linux LIFEBOOK-E756 4.15.0-76-generic #86~16.04.1-Ubuntu SMP Mon Jan 20 
11:02:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  }

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

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

[Desktop-packages] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie

2020-02-12 Thread Rolf Leggewie

closing task for trusty

** Changed in: evolution-data-server (Ubuntu Trusty)
   Status: Triaged => Invalid

** Changed in: binutils (Ubuntu Trusty)
   Status: Confirmed => Invalid

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

Title:
  ld:i386 crashes with -static -fPIE -pie

Status in GLibC:
  Incomplete
Status in binutils package in Ubuntu:
  Confirmed
Status in eglibc package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in binutils source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Invalid
Status in xorg-server source package in Trusty:
  Fix Released
Status in eglibc package in Debian:
  Fix Released

Bug description:
  Making a simple file conftest.c with the following contents:

  int main() { return 0; }

  And then compiling it on i386 with gcc -fPIE -pie -static conftest.c
  returns:

  *** Error in `/usr/bin/ld': corrupted double-linked list: 0x08dddb38
  ***

  This breaks compilation xorg-server on i386. I believe that -static
  -fPIE -pie is probably invalid, and it fails on amd64 too.

  $ gcc -fPIE -pie -static conftest.c 
  /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: relocation 
R_X86_64_32 against `__TMC_END__' can not be used when making a shared object; 
recompile with -fPIC
  /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: error adding symbols: Bad value
  collect2: error: ld returned 1 exit status

  But autoconf hangs on the corrupted double-linked list, which times
  out the xorg-server build.

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

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

[Desktop-packages] [Bug 1862753] Re: Backport GPU hotplug RandR fix

2020-02-12 Thread Ppaalanen

Let's keep them separate. Bug 1853357 is a Wayland-related bug with many
other issues mixed in. This here is a Xorg patch.

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

Title:
  Backport GPU hotplug RandR fix

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  In order for the first DisplayLink device hotplug after reboot to be
  correctly acted on in GNOME, the following fix should be backported to
  all Xorg-server downstream branches that already apply the patch
  "xf86: autobind GPUs to the screen" (upstream
  078277e4d92f05a90c4715d61b89b9d9d38d68ea):

  https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326

  The related upstream bug report fixed by this is
  https://gitlab.freedesktop.org/xorg/xserver/issues/909

  I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on
  the 1.20.4 upstream release.

  Upstream will not backport this patch into the stable 1.20 branch,
  because that branch does not carry "xf86: autobind GPUs to the
  screen".

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

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

[Desktop-packages] [Bug 1862753] Re: Backport GPU hotplug RandR fix

2020-02-12 Thread Timo Aaltonen

it was said to be unrelated to that bug, so keep them separate?

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

Title:
  Backport GPU hotplug RandR fix

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  In order for the first DisplayLink device hotplug after reboot to be
  correctly acted on in GNOME, the following fix should be backported to
  all Xorg-server downstream branches that already apply the patch
  "xf86: autobind GPUs to the screen" (upstream
  078277e4d92f05a90c4715d61b89b9d9d38d68ea):

  https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326

  The related upstream bug report fixed by this is
  https://gitlab.freedesktop.org/xorg/xserver/issues/909

  I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on
  the 1.20.4 upstream release.

  Upstream will not backport this patch into the stable 1.20 branch,
  because that branch does not carry "xf86: autobind GPUs to the
  screen".

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

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

[Desktop-packages] [Bug 1862135] Re: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders

2020-02-12 Thread Efthimios Chaskaris

Fixed in 80.0.3987.100

** Changed in: chromium-browser (Ubuntu)
   Status: New => 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/1862135

Title:
  [snap] Chromium 80 window border artifacts while using chromium's
  title bar and borders

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  FIX: It can be fixed by switching to system title bar and borders and
  back to chromium's.

  I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-02-12 Thread Olivier Tilloy

>From another report on the snapcraft forum, another custom scheme: urn

(https://forum.snapcraft.io/t/chromium-user-open-error-supplied-url-
scheme-is-not-allowed/15429)

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

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

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10

Reported bug #1862910

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  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/1856516/+subscriptions

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

[Desktop-packages] [Bug 1862910] [NEW] gnome-shell leaking memory

Public bug reported:

On one of my machines which has been upgraded over several years and
is now running 19.10 just one of the configured users appears to be
seeing a dramatic memory leak in gnome-shell, even when nothing is
happening on the UI. Immediately after logging on, using the Ubuntu
selection from the logon screen, gnome shell shows as using about
134MB. From there it climbs at about 300MB per hour and after a few
hours the machine grinds to a crawl, not surprisingly. This happens
even if the user logs on and then the machine is left completely
alone. Logout and back in frees all the memory.
A test user I have configured sees no such problem.
I have uninstalled all extensions apart from the system ones, disabled
all the system ones and reset all the gnome settings using dconf reset
-f /org/gnome/ to no avail. Also I have removed
~/.local/share/gnome-shell and allowed it to recreate it.
Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
I can't see anything obvious in the log.
It must be something in my settings that is triggering it as the other
user does not see it, but I have run out of ideas on what to try.

See also bug #1856516

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 12 08:54:21 2020
DisplayManager: gdm3
InstallationDate: Installed on 2014-10-21 (1939 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 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/1862910

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1664438] Re: updating device name in system settings doesn't update /etc/hosts

2020-02-12 Thread Mantas Kriaučiūnas

** 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 unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1664438

Title:
  updating device name in system settings doesn't update /etc/hosts

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

Bug description:
  probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
  and older releases, like 18.04 and 16.04.

  Changed the hostname of a system recently by opening the system
  settings tool, into details, and typing a new device name.

  Noticed afterwards that running sudo commands in the terminal resulted
  in an 'unable to resolve hostname' message, although the commands ran
  successfully.

  Checked and it looked like changing the name updates /etc/hostname as
  expected, but it didn't update /etc/hosts for me - it still had:

  127.0.0.1 localhost
  127.0.1.1 (old hostname)

  Replacing the old hostname with the new one removed the message from
  the terminal when running sudo commands.

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

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

[Desktop-packages] [Bug 1664438] Re: updating device name in system settings doesn't update /etc/hosts

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

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

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

Title:
  updating device name in system settings doesn't update /etc/hosts

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

Bug description:
  probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
  and older releases, like 18.04 and 16.04.

  Changed the hostname of a system recently by opening the system
  settings tool, into details, and typing a new device name.

  Noticed afterwards that running sudo commands in the terminal resulted
  in an 'unable to resolve hostname' message, although the commands ran
  successfully.

  Checked and it looked like changing the name updates /etc/hostname as
  expected, but it didn't update /etc/hosts for me - it still had:

  127.0.0.1 localhost
  127.0.1.1 (old hostname)

  Replacing the old hostname with the new one removed the message from
  the terminal when running sudo commands.

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

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

[Desktop-packages] [Bug 1664438] Re: updating device name in system settings doesn't update /etc/hosts

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

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

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

Title:
  updating device name in system settings doesn't update /etc/hosts

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

Bug description:
  probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
  and older releases, like 18.04 and 16.04.

  Changed the hostname of a system recently by opening the system
  settings tool, into details, and typing a new device name.

  Noticed afterwards that running sudo commands in the terminal resulted
  in an 'unable to resolve hostname' message, although the commands ran
  successfully.

  Checked and it looked like changing the name updates /etc/hostname as
  expected, but it didn't update /etc/hosts for me - it still had:

  127.0.0.1 localhost
  127.0.1.1 (old hostname)

  Replacing the old hostname with the new one removed the message from
  the terminal when running sudo commands.

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

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

[Desktop-packages] [Bug 1664438] Re: updating device name in system settings doesn't update /etc/hosts

2020-02-12 Thread Mantas Kriaučiūnas

** Tags added: eoan

** Description changed:

- probably a "paper cut" issue here. On 16.04.
+ probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
+ and older releases, like 18.04 and 16.04.

Changed the hostname of a system recently by opening the system settings
tool, into details, and typing a new device name.

Noticed afterwards that running sudo commands in the terminal resulted
in an 'unable to resolve hostname' message, although the commands ran
successfully.

Checked and it looked like changing the name updates /etc/hostname as
expected, but it didn't update /etc/hosts for me - it still had:

127.0.0.1 localhost
127.0.1.1 (old hostname)

Replacing the old hostname with the new one removed the message from the
terminal when running sudo commands.

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

Title:
updating device name in system settings doesn't update /etc/hosts

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

Bug description:
probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
and older releases, like 18.04 and 16.04.

Changed the hostname of a system recently by opening the system
settings tool, into details, and typing a new device name.

Noticed afterwards that running sudo commands in the terminal resulted
in an 'unable to resolve hostname' message, although the commands ran
successfully.

Checked and it looked like changing the name updates /etc/hostname as
expected, but it didn't update /etc/hosts for me - it still had:

127.0.0.1 localhost
127.0.1.1 (old hostname)

Replacing the old hostname with the new one removed the message from
the terminal when running sudo commands.

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

[Desktop-packages] [Bug 1862895] Re: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM