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

2023-06-19 Thread Mark - Syminet
Hi, thought I'd chime in here as just ran into the same issue on debian
bullseye.  Obtained an oh-so-precious "mycert.p12" file and resolved
thus:

Step 1:

a) In Firefox ESR: Settings -> Privacy and Security -> View Certificates button 
(way down at the bottom).
b) "Certificate manager" popup window, "Your Certificates",  Import button 
c) Select mycert.p12 file and it appears in Firefox.  

Step 2:

a) In LibreOffice Write: Tools -> Options -> Security, click
"Certificate" button under "Certificate Path"

This is where it got interesting - there were two selections there:

x firefox:default
o firefox:default-esr 

the top one, "firefox-default" was selected and was not working.
Clicking "firefox:default-esr" instead, restart LibreOffice Write...
fixed.

Another important note: After changing the certificate path, it prompts
"LibreOffice Write needs to restart in order to take effect.  Do this
now?" ...which I answered yes, but it did not actually restart.
Initially thinking it didn't work.  But upon manual restart, it *did*
work.

Maybe this approach is better since it takes Seahorse out of the loop.

Would also be curious to know if Jammy is fixed and/or above works?  I'm
going to upgrade one of the three debian bullseye systems I did this on
successfully, to debian bookworm right now.  If anything breaks, I'll be
sure to post that here.

Hope this helps someone out there.

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

Re: [Bug 1860824] Re: IMAP with STARTTLS on port 143 is broken

2020-07-17 Thread Mark - Syminet
Gotit - thanks! 


On Fri, 2020-07-17 at 15:36 +, Kai Kasurinen wrote:
> This bug report is being closed due to your last comment regarding this
> being fixed. For future reference you can manage the status of your own
> bugs by clicking on the current status in the yellow line and then
> choosing a new status in the revealed drop down box. You can learn more
> about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you
> again for taking the time to report this bug and helping to make Ubuntu
> better. Please submit any future bugs you may find.
> 
> ** Changed in: evolution (Ubuntu)
>Status: Incomplete => Invalid
>

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

Title:
  IMAP with STARTTLS on port 143 is broken

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

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

[Bug 1860824] Re: IMAP with STARTTLS on port 143 is broken

2020-07-17 Thread Mark - Syminet
Dug further on this and the issue is an ancient TLS version being used
on the server, so this bug can be closed.  BTW is there any way for me
to close the bug myself since I filed it?  Thnx -

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

Title:
  IMAP with STARTTLS on port 143 is broken

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

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

[Bug 1860824] [NEW] IMAP with STARTTLS on port 143 is broken

2020-01-24 Thread Mark - Syminet
Public bug reported:

Just upgraded from eoan -> fossa to test.  Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.

But in fossa, upon startup IMAP immediately fails with error message:

'The reported error was "Error performing TLS handshake: An unexpected
TLS packet was received."'

...no incoming mail and none of the folders will open.

Workaround: Switch account configuration to use TLS directly over
dedicated port 993

Then everything works as normal.  But users for whom port 993 is not an
option, no incoming mail or access to their mailfolders.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evolution 3.34.1-2build1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 15:34:28 2020
InstallationDate: Installed on 2018-10-06 (475 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  IMAP with STARTTLS on port 143 is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860824/+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-12-09 Thread Mark - Syminet
When av LTS is relkeased, is is considered according to it's promise: 6 years.  
But yet, after 3.5 years, here we are.  

Someone else said it works fine in Eoan.

...who approved this SRU?

-- 
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 1841646] Re: White text on white background for HTML e-mail

2019-11-11 Thread Mark - Syminet
Thanks, was really surprised to see this happen in an LTS release.  Any
Ubuntu devs reading this, can we get a backport?

-- 
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 1841646] Re: White text on white background for HTML e-mail

2019-11-10 Thread Mark - Syminet
Same behavior here, after unattended upgrade.  This renders Evolution
pretty much unusable with dark theme.

-- 
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/ubuntu/+source/evolution/+bug/1841646/+subscriptions

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