** Changed in: seahorse
Importance: Unknown => Critical
--
seahorse crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/344696
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mail
This bug was fixed in the package seahorse - 2.26.1-0ubuntu1
---
seahorse (2.26.1-0ubuntu1) jaunty; urgency=low
* New upstream version: (LP: #360225)
- PGP UIDs display in order reported by key server, and fix
parsing of HKP PGP search UIDs. [Adam Schreiber] (LP: #351948)
** Changed in: seahorse
Status: New => Fix Released
--
seahorse crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/344696
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mail
Fixed upstream.
** Changed in: seahorse (Ubuntu)
Status: Triaged => Fix Committed
--
seahorse crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/344696
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug a
** Changed in: seahorse
Status: Unknown => New
--
seahorse crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/344696
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing l
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=576519
** Changed in: seahorse (Ubuntu)
Status: Incomplete => Triaged
** Also affects: seahorse via
http://bugzi
1. Yes, It is reproducible.
2. Steps:
2.1. Start Seahorse
2.2. Open Settings throw menu in main window
2.3. Open Sync dialog throw menu in main window
2.4. Click on button in sync window to select servers before syncing
2.5. Take crash
3. Steps:
3.1. Start Seahorse
3.2. Open Sy
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Visibil
