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 646036 - [abrt] evolution-2.32.2-1.fc14: ____strtoul_l_internal, camel_imap_folder_selected: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV
[abrt] evolution-2.32.2-1.fc14: ____strtoul_l_internal, camel_imap_folder_sel...
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imap]
Depends on:
Blocks:
 
 
Reported: 2011-03-29 05:48 UTC by Milan Crha
Modified: 2012-09-04 19:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2011-03-29 05:48:17 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=691405

abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 63733 bytes
cmdline: evolution
comment: scolled to see newly arrived emails, but search hid the new mails from
showing. kept scolling because i didn't see the search was active, evolution
then crashed
component: evolution
Attached file: coredump, 183033856 bytes
crash_function: ____strtoul_l_internal
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301317621
uid: 762

How to reproduce
-----
1. received 5 new emails
2. search (filter active, hiding new emails)
3. scoll up (even if at the top of list, to see new emails)

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 226492

Thread 5 (Thread 0x7fd647344700 (LWP 27512))

  • #0 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 136
  • #1 _L_lock_841
    from /lib64/libpthread-2.13.so
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 61
  • #3 g_static_rec_mutex_lock
    at gthread.c line 1424
  • #4 imap_sync
    at camel-imap-folder.c line 1532
  • #5 camel_folder_sync
    at camel-folder.c line 1124
  • #6 refresh_folders_exec
    at mail-send-recv.c line 911
  • #7 mail_msg_proxy
    at mail-mt.c line 469
  • #8 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #9 g_thread_create_proxy
    at gthread.c line 1897
  • #10 start_thread
    at pthread_create.c line 301
  • #11 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

Thread 1 (Thread 0x7fd627fff700 (LWP 27514))

  • #0 ____strtoul_l_internal
    at ../stdlib/strtol_l.c line 298
  • #1 camel_imap_folder_selected
    at camel-imap-folder.c line 579
  • #2 imap_command_start
    at camel-imap-command.c line 211
  • #3 camel_imap_command
    at camel-imap-command.c line 111
  • #4 imap_get_message
    at camel-imap-folder.c line 3391
  • #5 imap_sync_message
    at camel-imap-folder.c line 3535
  • #6 camel_folder_sync_message
    at camel-folder.c line 1798
  • #7 offline_downsync_sync
    at camel-offline-folder.c line 73
  • #8 session_thread_proxy
    at camel-session.c line 321
  • #9 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #10 g_thread_create_proxy
    at gthread.c line 1897
  • #11 start_thread
    at pthread_create.c line 301
  • #12 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Milan Crha





          2012-09-04 19:08:43 UTC
        



Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.