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 430926 - crash in Evolution: quitaba el protector de ...
crash in Evolution: quitaba el protector de ...
Status: RESOLVED DUPLICATE of bug 430744
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-04-18 08:02 UTC by qbic
Modified: 2007-04-26 14:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description qbic 2007-04-18 08:02:33 UTC 
What were you doing when the application crashed?
quitaba el protector de pantallas


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: -1132326912 vsize: 0 resident: -1132326912 share: 0 rss: 1271730176 rss_rlim: 0
CPU usage: start_time: 1176846859 rtime: 0 utime: 4017 stime: 0 cutime:3007 cstime: 0 timeout: 1010 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232566608 (LWP 5454)]
[New Thread -1334838368 (LWP 16189)]
[New Thread -1322714208 (LWP 5486)]
[New Thread -1314321504 (LWP 5476)]
[New Thread -1284510816 (LWP 5471)]
[New Thread -1274201184 (LWP 5466)]
[New Thread -1276118112 (LWP 5464)]
[New Thread -1265783904 (LWP 5461)]
[New Thread -1257391200 (LWP 5460)]
[New Thread -1248871520 (LWP 5459)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128712

Thread 8 (Thread -1265783904 (LWP 5461))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_realloc
    from /usr/lib/libglib-2.0.so.0
  • #10 g_ptr_array_new
    from /usr/lib/libglib-2.0.so.0
  • #11 g_array_append_vals
    from /usr/lib/libglib-2.0.so.0
  • #12 g_byte_array_append
    from /usr/lib/libglib-2.0.so.0
  • #13 camel_mime_part_construct_content_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #14 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #15 camel_mime_message_new
    from /usr/lib/libcamel-1.2.so.8
  • #16 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #17 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #18 camel_data_wrapper_construct_from_stream
    from /usr/lib/libcamel-1.2.so.8
  • #19 camel_pop3_engine_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #20 camel_pop3_delete_old
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #21 camel_pop3_folder_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #22 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.8
  • #23 mail_fetch_mail
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #24 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #25 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #26 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #27 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


palfrey





          2007-04-26 14:20:20 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 430744 ***