[Bug 1278387] Re: Private key generation does not work at all

2018-10-30 Thread Ivan
I have a same problem with version 3.30 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1278387 Title: Private key generation does not work at all To manage notifications about

[Bug 1278387] Re: Private key generation does not work at all

2015-02-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu.

[Bug 1278387] Re: Private key generation does not work at all

2014-06-06 Thread A. Eibach
3.10 is now a whopping 4 years old... https://launchpad.net/~gnome3-team/+archive/gnome3-staging Does this version work fine for you? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu.

[Bug 1278387] Re: Private key generation does not work at all

2014-02-11 Thread itzeme
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. -- You received this bug notification because you are a member of

[Bug 1278387] Re: Private key generation does not work at all

2014-02-11 Thread Sebastien Bacher
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 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1278387 Title: Private key

[Bug 1278387] Re: Private key generation does not work at all

2014-02-10 Thread Sebastien Bacher
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