much more stable, does regard the GNOME standard, doesn't have ads, IS a
democracy, plus the devs don't customize the UI to death).
where is ad in ubuntu?
On a laptop of a friend where Jaunty was installed she was prompted to
upgrade to Lucid. I was surprised to hear that. A dist upgrade
the problem is that theses voices are only the minority.
The most ubuntu users, don't test Beta1 ,2 or follow every bugreport.
they will install the new LTS when its available and after the installation the
will be surprised/ annoyed / happy
maybe they will google for it, or they will stick to
@Pyramid Technologies #607
i stand 100% behind your post. the problem is not the decision itself, but the
way how it was
- discussed
- communicated
- implemented
And i think this is a very important question for the whole community:
Should ubuntu ignore the community (lp,brainstorm, etc ..) to
added
http://bugzilla.gnome.org/show_bug.cgi?id=587638
upstream link.
** Bug watch added: GNOME Bug Tracker #587638
http://bugzilla.gnome.org/show_bug.cgi?id=587638
** Also affects: seahorse via
http://bugzilla.gnome.org/show_bug.cgi?id=587638
Importance: Unknown
Status:
** Attachment added: Screenshot-seahorse.png
http://launchpadlibrarian.net/25888067/Screenshot-seahorse.png
--
seahorse can not change trust level
https://bugs.launchpad.net/bugs/365540
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: seahorse
It is not possible to change the trust of the key i signed.
The gui always displays : Trust: Marginal and the dropdown box is disabled. (as
you can see in the screenshot)
the gpg command displayes 2 trust levels:
1. trust:marginal
2. [ full ]
sry forgotten about
$ apt-cache policy seahorse
seahorse:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
*** 2.26.1-0ubuntu1 0
500 http://at.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
sry forgotten about:
$ apt-cache policy
Public bug reported:
Binary package hint: seahorse
The old seahorse in jaunty displayed the correct Key ID for the inner
certificate
The seahorse version in jaunty (all updates) just displays something not
useable.
The certficate is valid because the firefox addon FireGPG CAN handle this.
** Attachment added: Screenshot-Passwords and Encryption Keys.png
http://launchpadlibrarian.net/25865792/Screenshot-Passwords%20and%20Encryption%20Keys.png
--
seahorse does not correctly handel keys with subkeys
https://bugs.launchpad.net/bugs/365315
You received this bug notification
ok:
the KeyID is 2FCC2BB4 this key is in the security tab of my mailaccount @
evolution.
i write a testmail to myself from the account with the KeyID 2FC ..
I check Security PGP Sign
send:
it asks me to unlock the cached passphrase for Key with ID 2FCC2BB4
It sends the message without any
an additional problem is: when i send a email with the content testmail to a
friend (his public key is known)
and want to encrypt that, evolutionis encrypting the mail with MY key.
When i display the sourcecode of the sent mail i just get a long
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.9
11 matches
Mail list logo
