Ubuntu
seahorse package

Private key generation does not work at all

Bug #1278387 reported by itzeme
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

The current version of seahorse in Ubuntu 14.04 shows an option to generate a "private key". It is neither obvious what kind of key this is nor does the option work at all, leaving fields for key type empty and not offering the possibility to active the "Create" button, leaving this option completely pointless.

Additionally, when setting the key size, the value is not limeted by anything other then the size of int

See original description
itzeme (launchacc)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in seahorse (Ubuntu):
importance: Undecided → Low
Revision history for this message
itzeme (launchacc) wrote :

Yes this is a upstream issue. However the seahorse project seems barely active, so if you want to have a working version of seahorse in the next Ubuntu release, you (Ubuntu developer) will need to fix some of those bugs yourself.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Right, but in any case if we write a fix that's going to be sent upstream so we need to open a bug there

Revision history for this message
A. Eibach (andi3) wrote :

3.10 is now a whopping 4 years old...

https://launchpad.net/~gnome3-team/+archive/gnome3-staging

Does this version work fine for you?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in seahorse (Ubuntu):
status: New → Confirmed
Revision history for this message
Ivan (underwit) wrote :

I have a same problem with version 3.30

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.