[Bug 1849426] Re: Daily Limit Exceeded error for Google calendar

2019-11-22 Thread Florian Dorn
same here

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

Title:
  Daily Limit Exceeded error for Google calendar

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-11-22 Thread Balazs Pere
I'm trying to catch that function(s) which leaks the memory, but
unfortunately I am not an expert. Can anyone help me what to do? I
copied /usr/bin/gnome-shell to /usr/bin/gnome-shell.bin and made a
script in /usr/bin/gnome-shell:

#!/bin/sh
if [ $USER = gstest ] ; then exec valgrind --tool=massif --num-callers=500 
--massif-out-file=/tmp/massif.out.%p 
--log-file=/tmp/gnome-shell.valgrind.log.%p $0.bin $* ; fi
exec $0.bin $*

after that I logged in as gstest and watched the valgrind output with
massif-visualizer. But I don't know how to control the frequency of
writing out the massif.out.pid file? This file was wrote out couple
minutes after logging in, but after that nothing was written out for
hours. It would be better to see continuously what is happening when I
e.g. push Super+A.

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

Title:
  Memory usage grows when locking/unlocking the screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-11-22 Thread Timo Aaltonen
Hello Sebastien, or anyone else affected,

Accepted gnome-software into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.6-2ubuntu10.19.10.0 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-eoan

** Tags added: verification-needed-bionic

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

Title:
  Starting snap from the after-install notification fails

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844799] Re: Use new snap banner format

2019-11-22 Thread Timo Aaltonen
Hello Robert, or anyone else affected,

Accepted gnome-software into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.6-2ubuntu10.19.10.0 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-eoan

** Tags added: verification-needed-bionic

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

Title:
  Use new snap banner format

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1816396] Please test proposed package

2019-11-22 Thread Timo Aaltonen
Hello Sebastien, or anyone else affected,

Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.13 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Starting snap from the after-install notification fails

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1806697] Re: Status of interface connections not properly updated in the UI

2019-11-22 Thread Timo Aaltonen
Hello Efthimios, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.5-0ubuntu0.16.04.13 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Status of interface connections not properly updated in the UI

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844799] Please test proposed package

2019-11-22 Thread Timo Aaltonen
Hello Robert, or anyone else affected,

Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.13 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed-xenial

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

Title:
  Use new snap banner format

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844799] Please test proposed package

2019-11-22 Thread Timo Aaltonen
Hello Robert, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.5-0ubuntu0.16.04.13 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Use new snap banner format

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-11-22 Thread Timo Aaltonen
Hello Adam, or anyone else affected,

Accepted glib2.0 into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.60.4-0ubuntu0.19.04.2 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-disco

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

Title:
  IBus no longer works in Qt applications after upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1840955] Re: Evolution crashes on automatic mail check

2019-11-22 Thread Petr Fischer
The application crashes the same way on my Ubuntu 19.10 (I have one
Exchange account and one iCloud account - it's seems that app is
crashing after auto-receive new mail from both accounts).

Evolution is crashing also when I want to view new items from some
subscribed feeds.

Console error:
“evolution” terminated by signal SIGSEGV (Address boundary error)

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

Title:
  Evolution crashes on automatic mail check

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1840955] Re: Evolution crashes on automatic mail check

2019-11-22 Thread Petr Fischer
Note: I also have some "search folders", which is connected to both
email accounts.

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

Title:
  Evolution crashes on automatic mail check

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1845396] Re: [SRU] Update epiphany-broswer to 3.28.6 in Bionic

2019-11-22 Thread Timo Aaltonen
Hello Amr, or anyone else affected,

Accepted epiphany-browser into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/epiphany-
browser/3.28.6-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: epiphany-browser (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [SRU] Update epiphany-broswer to 3.28.6 in Bionic

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853584] [NEW] [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"

2019-11-22 Thread hugh chao
Public bug reported:

Summary:Not able to adjust Audio input UI volume, it's gray

Steps to reproduce:
1. Plug 3 ring earphone with mic to appropriate jack

Expected result:
System can be recording audio from external mic

Actual result:
Not able to adjust Audio input UI volume, it's gray, and no volume detected in 
UI, but I can recording the input audio by checkbox

Failure rate:100%

Note.
1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

** Affects: gnome-control-center
 Importance: Unknown
 Status: Unknown

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


** Tags: oem-priority

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #324
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/324

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/324
   Importance: Unknown
   Status: Unknown

** Tags added: oem-priority

** Summary changed:

- Not able to adjust Audio input UI volume after connecting headset in  "input 
tab"
+ [18.04]Not able to adjust Audio input UI volume after connecting headset in  
"input tab"

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

Title:
  [18.04]Not able to adjust Audio input UI volume after connecting
  headset in  "input tab"

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"

2019-11-22 Thread hugh chao
1. Still can reproduce this issue in 18.04.3
2. can not reproduce this issue in 19.04 and 19.10

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

Title:
  [18.04]Not able to adjust Audio input UI volume after connecting
  headset in  "input tab"

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-11-22 Thread Timo Aaltonen
Hello Adam, or anyone else affected,

Accepted glib2.0 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu4.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-xenial

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

Title:
  IBus no longer works in Qt applications after upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1845396] Autopkgtest regression report (epiphany-browser/3.28.6-0ubuntu1)

2019-11-22 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted epiphany-browser (3.28.6-0ubuntu1) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

libomxil-bellagio/0.9.3-4 (ppc64el)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#epiphany-browser

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

Thank you!

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

Title:
  [SRU] Update epiphany-broswer to 3.28.6 in Bionic

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-22 Thread hugh chao
** Summary changed:

- [18.04]Not able to adjust Audio input UI volume after connecting headset in  
"input tab"
+ [18.04]Not able to adjust Audio input UI volume after connecting headset

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

Title:
  [18.04]Not able to adjust Audio input UI volume after connecting
  headset

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-11-22 Thread Balazs Pere
Here is a similar issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1886
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886

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

Title:
  Memory usage grows when locking/unlocking the screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-22 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  [18.04]Not able to adjust Audio input UI volume after connecting
  headset

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1840955] Re: Evolution crashes on automatic mail check

2019-11-22 Thread Petr Fischer
Next findings: it looks like evolution is crashing on auto-received
email only when I am logged in gnome session with wayland, in normal X11
gnome session, no crashes yet.

Can @willismonroe test this?

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

Title:
  Evolution crashes on automatic mail check

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844853] Autopkgtest regression report (glib2.0/2.48.2-0ubuntu4.5)

2019-11-22 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted glib2.0 (2.48.2-0ubuntu4.5) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.28.2-1ubuntu1~16.04.3 (s390x)
dbus-test-runner/15.04.0+15.10.20151002-0ubuntu1 (arm64)
libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10 (i386)
libglib-object-introspection-perl/0.040-2 (armhf)
network-manager/1.2.6-0ubuntu0.16.04.3 (ppc64el)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#glib2.0

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

Thank you!

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

Title:
  IBus no longer works in Qt applications after upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1841646] Re: White text on white background for HTML e-mail

2019-11-22 Thread Pietro
I also have this problem in ubuntu 18.04, will I receive an update?

Thank you

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

Title:
  White text on white background for HTML e-mail

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778332] Re: Apparmor Permission Denied (apparmor="DENIED")

2019-11-22 Thread Jamie Strandboge
Clement, your issue is different than Charles'. More information is
required from you to triage your issue.

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

Title:
  Apparmor Permission Denied (apparmor="DENIED")

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778332] Re: Apparmor Permission Denied (apparmor="DENIED")

2019-11-22 Thread Jamie Strandboge
Nov 11 09:47:56  kernel: audit: type=1400
audit(1573487276.018:797080): apparmor="DENIED" operation="open"
profile="snap.gnome-system-monitor.gnome-system-monitor"
name="/run/systemd/sessions/c1" pi d=8733 comm="gnome-system-mo"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

I'm able to reproduce this on 19.10 under X11 (but not Wayland) in the
default install. I'll update snap for this denial. That fix should be in
snapd 2.43.

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

Title:
  Apparmor Permission Denied (apparmor="DENIED")

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853641] Re: Dragging a diff file from the Desktop to the Trash causes the file to be simply moved next to the trash instead of inside the trash.

2019-11-22 Thread Seija Kijin
** Patch added: "This is the file I attempted to trash"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853641/+attachment/5307151/+files/change.diff

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

Title:
  Dragging a diff file from the Desktop to the Trash causes the file to
  be simply moved next to the trash instead of inside the trash.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853641] [NEW] Dragging a diff file from the Desktop to the Trash causes the file to be simply moved next to the trash instead of inside the trash.

2019-11-22 Thread Seija Kijin
Public bug reported:

When I attempted to move a .diff file on the Desktop to the trash by
dragging the file over the Trash, Nautilus placed the file next to the
trash, instead of inside the trash. I tried again, and then I received
an error stating "change.diff cold not be placed in the trash. Do you
want to delete it immediately?" even though the file is less than 1
Kilobyte.

Steps to reproduce:
1. Run git diff to output a .diff file to the Desktop with sudo
2. Drag the file into the trash
3. Notice how the file gets put next to the trash and nautilus is unable to 
trash the file.

Expected Results:
Nautilus trashes the file

Actual Results:
Nautilus alerts the user it cannot trash the file.

Description:Ubuntu 19.10
Release:19.10

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

I only have the default plug-ins installed for nautilus.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1: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: Fri Nov 22 13:07:13 2019
GsettingsChanges:
 
InstallationDate: Installed on 2019-11-20 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Image of the screen when I saw the error later after it 
happened."
   
https://bugs.launchpad.net/bugs/1853641/+attachment/5307148/+files/Screenshot%20from%202019-11-22%2013-16-36.png

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

Title:
  Dragging a diff file from the Desktop to the Trash causes the file to
  be simply moved next to the trash instead of inside the trash.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844853] Autopkgtest regression report (glib2.0/2.60.4-0ubuntu0.19.04.2)

2019-11-22 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted glib2.0 (2.60.4-0ubuntu0.19.04.2) for 
disco have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.10-0ubuntu27.3 (i386, amd64)
awesome/4.3-4 (armhf)
graphviz/unknown (armhf)
vlc/unknown (armhf)
systemd/240-6ubuntu5.7 (i386, amd64)
umockdev/0.12.1-2 (amd64)
udisks2/2.8.2-1 (arm64)
gtk+3.0/3.24.8-1ubuntu1 (armhf)
glib2.0/2.60.4-0ubuntu0.19.04.2 (i386)
sbd/1.3.1-4 (i386)
firefox/70.0.1+build1-0ubuntu0.19.04.1 (armhf)
lazarus/unknown (armhf)
dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (ppc64el)
gvfs/1.40.1-1ubuntu0.1 (ppc64el)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#glib2.0

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

Thank you!

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

Title:
  IBus no longer works in Qt applications after upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal

2019-11-22 Thread Olivier Tilloy
Follow-up patch that updates the vendored crates in the source tarball
accordingly.

** Patch added: "cssparser-update-vendored-crates.patch"
   
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307180/+files/cssparser-update-vendored-crates.patch

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

Title:
  librsvg 2.44.15 FTBFS in focal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal

2019-11-22 Thread Olivier Tilloy
Build log with the above two patches applied, unit tests fail.

** Attachment added: 
"buildlog_ubuntu-focal-amd64.librsvg_2.44.15-1ubuntu1_ppa8_BUILDING.txt.gz"
   
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307181/+files/buildlog_ubuntu-focal-amd64.librsvg_2.44.15-1ubuntu1_ppa8_BUILDING.txt.gz

** Changed in: librsvg (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Changed in: librsvg (Ubuntu)
   Importance: Undecided => High

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

Title:
  librsvg 2.44.15 FTBFS in focal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853657] [NEW] librsvg 2.44.15 FTBFS in focal

2019-11-22 Thread Olivier Tilloy
Public bug reported:

focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and
librsvg 2.44.15 fails to build from source with this version. It built
fine with rustc 1.37 (although there was a unit test failure on ppc64el,
which prevented it from leaving focal-proposed, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942022).

The upstream commit that addresses this is 
https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8.
I backported it and added another patch to update the vendored crates in the 
source tarball accordingly, and the build succeeds again, but unit tests 
consistently fail, on all architectures.

The upstream commit message says « Although you should rather be using
the 2.46 branch of librsvg as 2.44 is EOL », so we should probably
update librsvg in debian to 2.46 indeed.

** Affects: librsvg (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged

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

Title:
  librsvg 2.44.15 FTBFS in focal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal

2019-11-22 Thread Olivier Tilloy
Patch for the upstream commit
(https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8).

** Patch added: "upstream-de26c4d8.patch"
   
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307179/+files/upstream-de26c4d8.patch

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

Title:
  librsvg 2.44.15 FTBFS in focal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal

2019-11-22 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  librsvg 2.44.15 FTBFS in focal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-11-22 Thread Matt Austin
** Attachment added: "tearing-2.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-11-22 Thread Matt Austin
** Attachment added: "tearing-1.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1075923] Re: nautilus hangs copying large directories from a samba share

2019-11-22 Thread Ryan C. Underwood
Still a problem on Eoan.

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

Title:
  nautilus hangs copying large directories from a samba share

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs