[Bug 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI

2023-12-18 Thread wontfix
** Tags removed: bionic kinetic lunar
** Tags added: mantic noble

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

Title:
  Allow configuring Wi-Fi MAC Randomization feature from GUI

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


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

[Bug 2046847] [NEW] Ubuntu Desktop fails to login with Active Directory credentials on arm64 systems

2023-12-18 Thread Jesse M Darnley
Public bug reported:

When attempting to log in to an Ubuntu Desktop session on ARM64 systems
using Active Directory credentials. User login will fail and dump the
user back to the login prompt.

Login with local accounts work. Authentication checks succeed in logs.
The Active Directory users are added, but login still fails. This issue
has been seen on a Xilinx system and replicated using a Raspberry Pi 4.

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

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

Title:
  Ubuntu Desktop fails to login with Active Directory credentials on
  arm64 systems

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


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

[Bug 2046844] [NEW] Epiphany browser does not launch on Ubuntu 24.04: core dumped

2023-12-18 Thread Xavier Guillot
Public bug reported:

Hi, I run Ubuntu development branch 24.04 and I have a problem with
Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
this error

$ epiphany
bwrap: Creating new namespace failed: Permission denied

** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: 
Le processus fils s’est terminé avec le code 1
Trappe pour point d'arrêt et de trace (core dumped)

$ epiphany
bwrap: Creating new namespace failed: Permission denied

** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: 
Le processus fils s’est terminé avec le code 1
Trappe pour point d'arrêt et de trace (core dumped)

Thanks for your help!

** Affects: epiphany-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Epiphany browser does not launch on Ubuntu 24.04: core dumped

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


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

Re: [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Meluco
Thank you, very, very, much!

O 19:25, luns, 18 de dec. de 2023, Angelo Giacomini Ribas <
1771...@bugs.launchpad.net> escribiu:

> May the Luck be with you!
>
> On Mon, 18 Dec 2023, 14:35 Damjan Jovanovic, <1771...@bugs.launchpad.net>
> wrote:
>
> > I am personally working on this issue, you can follow my progress on
> > https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
> >
> > So far it looks like there are a number of bugs; a simplified picture
> > looks something like this:
> >
> >  seahorse: gcr_import_button_add_parsed()gnome-keyring:
> > gkr-tool-import: on_parser_parsed()
> >   ||
> >   |+---+
> >   ||
> >   vv
> >  gcr: gcr_importer_create_for_parsed()
> >   |
> >   v
> >  gcr: iface->create_for_parsed()
> >   |
> >   v
> >  gcr: _gcr_pkcs11_importer_create_for_parsed()
> >   |  ^ |
> >   v  | v
> >  gcr: list_all_slots()gcr: is_slot_importable() for
> > p11-kit-trust.so
> >  (loads PKCS#11 modules,  (prints: "token is not importable: %s:
> write
> > protected")
> >   enumerates their slots)
> >   |  ^  | ^
> >   v  |  v |  remote procedure call
> >  p11-kit-trust.so  gnome-keyring-pkcs11.so  -->
> > gnome-keyring-daemon
> >   |  ^ (disabled by blacklist)  |
> >   v  |  v
> >  trust policy module
> > gnome2-store (I kid you not)
> >   |  ^  |
> >   v  |  v
> >  read-only system CA certificates
> >  ~/.local/share/keyrings/user.keystore
> >  and blacklist
> (fails
> > to find a section)
> >
> >
> > Wish me luck...
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1771880
> >
> > Title:
> >   Seahorse unable to import pkcs12 certificates
> >
> > Status in seahorse:
> >   New
> > Status in gnome-keyring package in Ubuntu:
> >   Triaged
> > Status in seahorse package in Ubuntu:
> >   Triaged
> > Status in gnome-keyring package in Fedora:
> >   New
> > Status in seahorse package in Fedora:
> >   Unknown
> >
> > Bug description:
> >   seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
> >   18.04 LTS / GNOME 3.28.1
> >
> >   When trying to import a certificate into seahorse/gnome-keyring on
> >   Ubuntu 18.04, seahorse GUI application shows the 'import' button
> >   greyed out, while mouse hovering the "import" button shows the message
> >   "Cannot import because there are no compatible importers".
> >
> >   This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
> >   I've just tested on my wife's laptop, but happens in my Laptop with
> >   Ubuntu 18.04 LTS (Seahorse 3.20.0-5).
> >
> >   Because that problem, it's not possible to digitally sign documents
> >   with LibreOffice.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions
> >
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771880
>
> Title:
>   Seahorse unable to import pkcs12 certificates
>
> Status in seahorse:
>   New
> Status in gnome-keyring package in Ubuntu:
>   Triaged
> Status in seahorse package in Ubuntu:
>   Triaged
> Status in gnome-keyring package in Fedora:
>   New
> Status in seahorse package in Fedora:
>   Unknown
>
> Bug description:
>   seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
>   18.04 LTS / GNOME 3.28.1
>
>   When trying to import a certificate into seahorse/gnome-keyring on
>   Ubuntu 18.04, seahorse GUI application shows the 'import' button
>   greyed out, while mouse hovering the "import" button shows the message
>   "Cannot import because there are no compatible importers".
>
>   This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
>   I've just tested on my wife's laptop, but happens in my Laptop with
>   Ubuntu 18.04 LTS (Seahorse 3.20.0-5).
>
>   Because that problem, it's not possible to digitally sign documents
>   with LibreOffice.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions
>
>

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

Title:
  Seahorse unable to import pkcs12 certificates

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


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

Re: [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Angelo Giacomini Ribas
May the Luck be with you!

On Mon, 18 Dec 2023, 14:35 Damjan Jovanovic, <1771...@bugs.launchpad.net>
wrote:

> I am personally working on this issue, you can follow my progress on
> https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
>
> So far it looks like there are a number of bugs; a simplified picture
> looks something like this:
>
>  seahorse: gcr_import_button_add_parsed()gnome-keyring:
> gkr-tool-import: on_parser_parsed()
>   ||
>   |+---+
>   ||
>   vv
>  gcr: gcr_importer_create_for_parsed()
>   |
>   v
>  gcr: iface->create_for_parsed()
>   |
>   v
>  gcr: _gcr_pkcs11_importer_create_for_parsed()
>   |  ^ |
>   v  | v
>  gcr: list_all_slots()gcr: is_slot_importable() for
> p11-kit-trust.so
>  (loads PKCS#11 modules,  (prints: "token is not importable: %s: write
> protected")
>   enumerates their slots)
>   |  ^  | ^
>   v  |  v |  remote procedure call
>  p11-kit-trust.so  gnome-keyring-pkcs11.so  -->
> gnome-keyring-daemon
>   |  ^ (disabled by blacklist)  |
>   v  |  v
>  trust policy module
> gnome2-store (I kid you not)
>   |  ^  |
>   v  |  v
>  read-only system CA certificates
>  ~/.local/share/keyrings/user.keystore
>  and blacklist  (fails
> to find a section)
>
>
> Wish me luck...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771880
>
> Title:
>   Seahorse unable to import pkcs12 certificates
>
> Status in seahorse:
>   New
> Status in gnome-keyring package in Ubuntu:
>   Triaged
> Status in seahorse package in Ubuntu:
>   Triaged
> Status in gnome-keyring package in Fedora:
>   New
> Status in seahorse package in Fedora:
>   Unknown
>
> Bug description:
>   seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
>   18.04 LTS / GNOME 3.28.1
>
>   When trying to import a certificate into seahorse/gnome-keyring on
>   Ubuntu 18.04, seahorse GUI application shows the 'import' button
>   greyed out, while mouse hovering the "import" button shows the message
>   "Cannot import because there are no compatible importers".
>
>   This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
>   I've just tested on my wife's laptop, but happens in my Laptop with
>   Ubuntu 18.04 LTS (Seahorse 3.20.0-5).
>
>   Because that problem, it's not possible to digitally sign documents
>   with LibreOffice.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions
>
>

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

Title:
  Seahorse unable to import pkcs12 certificates

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


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

[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Damjan Jovanovic
I am personally working on this issue, you can follow my progress on
https://gitlab.gnome.org/GNOME/seahorse/-/issues/205

So far it looks like there are a number of bugs; a simplified picture
looks something like this:

 seahorse: gcr_import_button_add_parsed()gnome-keyring: 
gkr-tool-import: on_parser_parsed()
  ||
  |+---+
  ||
  vv
 gcr: gcr_importer_create_for_parsed()
  |
  v
 gcr: iface->create_for_parsed()
  |
  v
 gcr: _gcr_pkcs11_importer_create_for_parsed()
  |  ^ |
  v  | v
 gcr: list_all_slots()gcr: is_slot_importable() for p11-kit-trust.so
 (loads PKCS#11 modules,  (prints: "token is not importable: %s: write 
protected")
  enumerates their slots)
  |  ^  | ^
  v  |  v |  remote procedure call
 p11-kit-trust.so  gnome-keyring-pkcs11.so  --> 
gnome-keyring-daemon
  |  ^ (disabled by blacklist)  |
  v  |  v
 trust policy module
gnome2-store (I kid you not)
  |  ^  |
  v  |  v
 read-only system CA certificates   
~/.local/share/keyrings/user.keystore
 and blacklist  (fails to 
find a section)


Wish me luck...

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

Title:
  Seahorse unable to import pkcs12 certificates

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


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

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

2023-12-18 Thread Christopher Sines
I believe this issue is affecting me as well. The updater could not calculate 
the update, and asked me to use PPA-Purge. Main.log shows the following error:
2023-12-18 11:51:29,328 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
2023-12-18 11:51:29,344 DEBUG abort called
My apt.log is attached.

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5730448/+files/apt.log

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

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


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

[Bug 2046360] Autopkgtest regression report (mutter/45.2-0ubuntu2~really45.0)

2023-12-18 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mutter (45.2-0ubuntu2~really45.0) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/45.2-0ubuntu2~really45.0 (arm64)


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/mantic/update_excuses.html#mutter

[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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2046360

Title:
  Heavy stuttering in Firefox with mutter 45.1/45.2

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


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

[Bug 2046808] [NEW] Screencast app crashes after recording is stopped

2023-12-18 Thread Sergey Zolotarev
Public bug reported:

Every time I try to record a screencast via the built-in feature
triggered by Ctrl+Alft+Shift+R, it starts recording successfully but
when I click the stop button, the recording stops and nothing is saved
to ~/Videos/Screencasts. This happens with both Wayland and Xorg
sessions.

Here are the relevant journal records:

dbus-daemon[101710]: [session uid=1000 pid=101710] Activating service 
name='org.gnome.Shell.Screencast' requested by ':1.29' (uid=1000 pid=101851 
comm="/usr/bin/gnome-shell " label="unconfined")
dbus-daemon[101710]: [session uid=1000 pid=101710] Successfully activated 
service 'org.gnome.Shell.Screencast'
kernel: gjs[109549]: segfault at 8 ip 7f915005edf6 sp 7ffcd2710130 
error 4 in libgstpipewire.so[7f915004e000+14000]
kernel: Code: 50 48 8d 15 93 44 00 00 31 c0 41 b8 bc 04 00 00 48 8d 0d 3d 52 00 
00 be 05 00 00 00 e8 73 06 ff ff 58 5a 48 8b 85 00 03 00 00 <48> 8b 78 08 e8 81 
0e ff ff 48 8b 85 00 03 00 00 31 f6 c7 85 e4 02
gnome-shell[101851]: D-Bus client with active sessions vanished
gnome-shell[101851]: Error stopping screencast: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 18 19:28:49 2023
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-17 (2101 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-06-02 (563 days ago)

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


** Tags: amd64 apport-bug jammy

** Summary changed:

- Screencast app crashes recording is  stopped
+ Screencast app crashes after recording is  stopped

** Description changed:

  Every time I try to record a screencast via the built-in feature
  triggered by Ctrl+Alft+Shift+R, it starts recording successfully but
- when I click the stop button, nothing is saved to Videos/Screencasts.
+ when I click the stop button, the recording stops and nothing is saved
+ to Videos/Screencasts. This happens with both Wayland and Xorg sessions.
  
  Here are the relevant journal records:
  
  dbus-daemon[101710]: [session uid=1000 pid=101710] Activating service 
name='org.gnome.Shell.Screencast' requested by ':1.29' (uid=1000 pid=101851 
comm="/usr/bin/gnome-shell " label="unconfined")
  dbus-daemon[101710]: [session uid=1000 pid=101710] Successfully activated 
service 'org.gnome.Shell.Screencast'
  kernel: gjs[109549]: segfault at 8 ip 7f915005edf6 sp 7ffcd2710130 
error 4 in libgstpipewire.so[7f915004e000+14000]
  kernel: Code: 50 48 8d 15 93 44 00 00 31 c0 41 b8 bc 04 00 00 48 8d 0d 3d 52 
00 00 be 05 00 00 00 e8 73 06 ff ff 58 5a 48 8b 85 00 03 00 00 <48> 8b 78 08 e8 
81 0e ff ff 48 8b 85 00 03 00 00 31 f6 c7 85 e4 02
  gnome-shell[101851]: D-Bus client with active sessions vanished
  gnome-shell[101851]: Error stopping screencast: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 18 19:28:49 2023
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-17 (2101 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-06-02 (563 days ago)

** Description changed:

  Every time I try to record a screencast via the built-in feature
  triggered by Ctrl+Alft+Shift+R, it starts recording successfully but
  when I click the stop button, the recording stops and nothing is saved
- to Videos/Screencasts. This happens with both Wayland and Xorg sessions.
+ to ~/Videos/Screencasts. This happens with both Wayland and Xorg
+ sessions.
  
  Here are the relevant journal records:
  
  dbus-daemon[101710]: [session uid=1000 pid=101710] Activating service 
name='org.gnome.Shell.Screencast' requested by ':1.29' (uid=1000 pid=101851 
comm="/usr/bin/gnome-shell " label="unconfined")
  dbus-daemon[101710]: [session uid=1000 pid=101710] Successfully activated 
service 'org.gnome.Shell.Screencast'
  kernel: gjs[109549]: segfault at 8 ip 

[Bug 2046801] [NEW] Unable to launch Evolution: bwrap: Creating new namespace failed: Permission denied

2023-12-18 Thread syldeb35
Public bug reported:

~$ evolution 
bwrap: Creating new namespace failed: Permission denied

** (evolution:6289): ERROR **: 12:04:27.146: Failed to fully launch dbus-proxy: 
Le processus fils s’est terminé avec le code 1
Trappe pour point d'arrêt et de trace (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: evolution 3.50.2-1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Dec 18 12:07:13 2023
InstallationDate: Installed on 2020-08-31 (1204 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: evolution
UpgradeStatus: Upgraded to noble on 2023-12-12 (6 days ago)

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


** Tags: amd64 apport-bug noble

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

Title:
  Unable to launch Evolution: bwrap: Creating new namespace failed:
  Permission denied

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


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