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 391410 - crash in Evolution: Waking up from being awa...
crash in Evolution: Waking up from being awa...
Status: RESOLVED DUPLICATE of bug 352284
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: 2006-12-31 21:00 UTC by jlpearce
Modified: 2007-01-02 18:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jlpearce 2006-12-31 21:00:27 UTC 
What were you doing when the application crashed?
Waking up from being away from the computer, suspended.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: -203304960 vsize: -203304960 resident: -1793978368 share: 13967360 rss: -1780011008 rss_rlim: -1772896256
CPU usage: start_time: 1167578972 rtime: 4605 utime: 3595 stime: 1010 cutime:597 cstime: 84 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47764323204304 (LWP 12632)]
[New Thread 1115703616 (LWP 12775)]
[New Thread 1115969856 (LWP 12676)]
[New Thread 1090525504 (LWP 12675)]
[New Thread 1082132800 (LWP 12674)]
[New Thread 1107310912 (LWP 12672)]
[New Thread 1098918208 (LWP 12640)]
(no debugging symbols found)
0x00002b70fe51c1f6 in poll () from /lib64/libc.so.6

+ Trace 98354

Thread 7 (Thread 1098918208 (LWP 12640))

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






Comment 1


palfrey





          2007-01-02 18:50:20 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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