** Changed in: seahorse
Importance: Unknown => High
--
seahorse crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/122620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Changed in: seahorse
Status: Unknown => Fix Released
--
seahorse crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/122620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
If the upstream bug report is correct, this bug has been fixed.
If anyone is still experiencing this issue, please feel free to reopen
the bug.
** Also affects: seahorse via
http://bugzilla.gnome.org/show_bug.cgi?id=451710
Importance: Unknown
Status: Unknown
** Changed in: seahorse
I have seen this crash too and wanted to note that one effect seems to be that
seahorse does not display my keys (own private/public pair, keys of people I
added to the keyring) anymore. It seems that it does display keys it
automatically added since the issue appeared.
I also can't encrypt in E
What looks like a related bug, it crashed network-manager applet and a
work-around was added to it :
https://bugs.launchpad.net/gnome-keyring/+bug/83326
https://bugs.launchpad.net/gnome-keyring/+bug/121228
But the real bug was/is in gnome-keyring lib :
http://bugzilla.gnome.org/show_bug.cgi?id=45
** Attachment added: "leaks as seen in valgrind"
http://launchpadlibrarian.net/8266680/valgrind.log.16960
--
seahorse crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/122620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
** Attachment added: "full backtrace as instructed in the 'Backtrace' wiki page"
http://launchpadlibrarian.net/8266599/seahorse_full_backtrace.txt
--
seahorse crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/122620
You received this bug notification because you are a member of
Starting program: /usr/bin/seahorse
[Thread debugging using libthread_db enabled]
[New Thread 47341985012128 (LWP 15111)]
** Message: init gpgme version 1.1.2
***MEMORY-WARNING***: [15111]: GSlice: g_thread_init() must be called
before all other GLib functions; memory corruption due to late
invoc
I'll try to do it tonight on my x86-64 box (as for now I'm at work on crappy
FC6)
Is there a way to make apport add information to an existing bug report rather
than creating a new one ?
--
seahorse crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/122620
You received this bug no
Thanks for your bug report. Please try to obtain a debug backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: seahorse (Ubuntu)
Importance: Undecided => Medium
Status: Confirm
I believe it is related to the bug that was just fixed in network
manager 0.6.5 with encrypted wifi
Looks like a NULL check is missing (default keyring is NULL now)
https://bugs.launchpad.net/ubuntu/+bug/121228/
** Changed in: seahorse (Ubuntu)
Status: New => Confirmed
--
seahorse cras
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8218440/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/8218441/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/8218442/ProcMaps.txt
** Attachme
12 matches
Mail list logo
