[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's solution (root rights granted in Xwrapper) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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
** Description changed:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
- The real fix has been made in glib2.0, and the proposed updates in the
- below PPA will allow the IBus patch to be re-enabled.
-
- https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0
+ The real fix has been made in glib2.0, and the updates in -proposed will
+ allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
-- Upgrade the glib2.0 packages from
- {eoan,disco,bionic,xenial}-proposed
+ - Upgrade the glib2.0 packages from
+ {eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed
that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus
functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of 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 1798840] Re: Night Light is not functioning
Night light stopped working for me from Disco to Eoan upgrade. -- 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/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] Re: Unnecessary Delays Recovering from Screen Lock
** 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Description changed: You can turn "Sreen Lock" off using gnome-control-center > Privacy > - Screen Lock : Off. + Screen Lock : Off: - However, this is bad terminology because you screen will still go into - the exact same "Screen Lock" state upon an inactivity timeout, but the - only difference is that you don't have to enter your password to regain - access to the desktop. + https://gitlab.gnome.org/GNOME/gnome-control- + center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png + + **Side-note:** this is bad terminology because your screen will still go + into the exact same state that "Screen Lock: On" accomplishes (upon an + inactivity timeout), but the only difference is that you won't have to + enter your password to regain access to the desktop. I would have named + this "Require Password Authentication After Inactivity Timeout" (to me + wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a - couple of behaviors. + couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press - enter. I want to be able to accomplish this also by moving my mouse. + the "enter" key. I want to be able to accomplish this also by moving my + mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. + Also, there should be separate setting for "blank screen x time", and + "monitor power off after x time". + + My ideal settings would to make the screen go black after 5 minutes of + inactively and to turn my monitors completely off after 15 minutes of + inactively, and I'd like to control whether each of these requires + password authentication or not. On the 5 minute one, I personally would + note require a password, but I would require a password after monitor + going off. However, on either of these, I expect the desktop to be fully + functional immediately after coming out of these states. At the very + least please remove these unnecessary delays. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 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 + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Screen Lock Recovery has Unnecessary Delays + Unnecessary Delays Recovering from Screen Lock -- 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Importance: Unknown Status: Unknown -- 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] [NEW] Screen Lock Recovery has Unnecessary Delays
Public bug reported: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off. However, this is bad terminology because you screen will still go into the exact same "Screen Lock" state upon an inactivity timeout, but the only difference is that you don't have to enter your password to regain access to the desktop. While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of behaviors. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press enter. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 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: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1851067 Title: Screen Lock Recovery has Unnecessary Delays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850995] Re: gnome-shell: freeze and high CPU usage
I tried to start a session with "ubuntu wayland" on the VM and the problem is not there, the problem is only on the xorg session. I can't start "ubuntu wayland" on the host desktop with the NVIDIA GPU, of course I enable "nvidia-drm.modeset = 1", but that's another problem. -- 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/1850995 Title: gnome-shell: freeze and high CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850995/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I am also facing this issue in Ubuntu 19.10 Eoan Ermine -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu Bionic) Status: New => Confirmed -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Confirmed -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843984] Re: iubuntu dash truncate the name of all application searched - no way to see the complete name
*** This bug is a duplicate of bug 968213 *** https://bugs.launchpad.net/bugs/968213 hank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 968213, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: dash (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 968213 Too many icons in Gnome Shell Activities Overview require ellipses -- 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/1843984 Title: iubuntu dash truncate the name of all application searched - no way to see the complete name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847516] Re: Alt+Shift does not change layout
** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1847516 Title: Alt+Shift does not change layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1847516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843984] [NEW] iubuntu dash truncate the name of all application searched - no way to see the complete name
You have been subscribed to a public bug:
I installed avidemux, which installed two packages with the same initial part
of their names: avidemux2.7_jobs_qt5 and avidemux2.7_qt5.
By clicking SUPER, the Dash will appear. If I search for "avidemux" the two
elements appear but because of the name truncated, I can't differentiate them,
either are showed with the name "avidemux 2.7 (".
Right-clicking on one of these there is the "details" option but it bring me to
the "ubuntu software" application that does not recognize the application
saying "application not found".
I think that the choose to truncate the application name in the Dash is simply
a design bug.
This is very annoying: there is enough space to see the compllete name, instead
of truncate it to the preview image size...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dash 0.5.8-2.10
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 10:42:12 2019
InstallationDate: Installed on 2019-09-07 (6 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
iubuntu dash truncate the name of all application searched - no way to see the
complete name
https://bugs.launchpad.net/bugs/1843984
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to gnome-shell in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847516] [NEW] Alt+Shift does not change layout
You have been subscribed to a public bug: Ubuntu 19.10 Daily 09.10.2019 and older After settings in gnome tweaks I expect changing of keyboard layout, but it still super+space. Also , shortcut's "Set shortcut' ignores Alt+Shift. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Alt+Shift does not change layout https://bugs.launchpad.net/bugs/1847516 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832426] Re: "Program" is not responding when debugging in gdb
I am also affected in Ubuntu 19.10 -- 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/1832426 Title: "Program" is not responding when debugging in gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851041] [NEW] Occasionally, the keyboard cannot be input
Public bug reported: 有时键盘无法输入文字，功能键正常，约几十秒后恢复正常，期间无法打开输入法设置 Sometimes the keyboard cannot input text and the function key is normal. It will return to normal after several tens of seconds. During this period, the input method setting cannot be opened ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus-libpinyin 1.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Sat Nov 2 22:00:06 2019 InstallationDate: Installed on 2019-10-18 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ibus-libpinyin UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.default.apport: 2019-10-18T23:13:49.837467 mtime.conffile..etc.logrotate.d.apport: 2019-10-29T22:06:09.766287 ** Affects: ibus-libpinyin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1851041/+attachment/5302279/+files/syslog -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1851041 Title: Occasionally, the keyboard cannot be input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1851041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725315] Re: evolution crashes with SIGSEGV in g_hash_table_lookup_node() when "evolution-indicator" package is installed
I reported the bug including a proposed fix on evolution-indicator: https://bugs.launchpad.net/evolution-indicator/+bug/1851036 -- 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/1725315 Title: evolution crashes with SIGSEGV in g_hash_table_lookup_node() when "evolution-indicator" package is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1725315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
