After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 416793 - evolution-2.10 crashed with SIGSEGV in g_list_find()
evolution-2.10 crashed with SIGSEGV in g_list_find()
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-10 14:55 UTC by Sebastien Bacher
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sebastien Bacher 2007-03-10 14:55:55 UTC
The bug has been opened on https://launchpad.net/bugs/90170

"Binary package hint: evolution

Closing Evolution.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 6 17:09:59 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/evolution-2.10
Package: evolution 2.9.92-0ubuntu1
PackageArchitecture: i386
ProcCmdline: evolution-2.10 --sm-config-prefix /evolution-2.10-CBDrUl/ --sm-client-id 117f000101000117304192600000063130041 --screen 0
..."

Debug backtrace for the crash:

Thread 1 (process 15417)

  • #0 IA__g_key_file_set_string_list
    at gkeyfile.c line 1510
  • #1 folder_changed_change
    at camel-vee-folder.c line 1223
  • #2 session_thread_proxy
    at camel-session.c line 530
  • #3 IA__g_thread_pool_set_max_threads
    at gthreadpool.c line 570
  • #4 IA__g_thread_create_full
    at gthread.c line 607

Comment 1 Srinivasa Ragavan 2007-08-09 19:00:41 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-12-21 15:55:46 UTC
bug 405497 could be the same problem.