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 407874 - crash in Evolution: I've opened another inst...
crash in Evolution: I've opened another inst...
Status: RESOLVED DUPLICATE of bug 334966
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-02-14 14:31 UTC by djurikam
Modified: 2007-02-14 16:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description djurikam 2007-02-14 14:31:41 UTC
What were you doing when the application crashed?
I've opened another instace of evolution


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

Memory status: size: 551301120 vsize: 551301120 resident: 11509760 share: 21512192 rss: 33021952 rss_rlim: 894858240
CPU usage: start_time: 1171466975 rtime: 185 utime: 159 stime: 26 cutime:26 cstime: 5 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 47772805741776 (LWP 5069)]
[New Thread 1141147968 (LWP 5191)]
[New Thread 1132755264 (LWP 5189)]
[New Thread 1132489024 (LWP 5188)]
[New Thread 1124096320 (LWP 5172)]
[New Thread 1115703616 (LWP 5112)]
[New Thread 1107310912 (LWP 5111)]
[New Thread 1098918208 (LWP 5089)]
[New Thread 1090525504 (LWP 5088)]
[New Thread 1082132800 (LWP 5086)]
(no debugging symbols found)
0x00002b72f6a82c5f in waitpid () from /lib64/libpthread.so.0

Thread 10 (Thread 1082132800 (LWP 5086))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 e_msgport_wait
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib64/libpthread.so.0
  • #4 clone
    from /lib64/libc.so.6
  • #5 ??

Thread 9 (Thread 1090525504 (LWP 5088))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 camel_read
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #2 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #3 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #4 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #5 camel_stub_marshal_decode_uint32
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #6 camel_stub_send
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #7 start_thread
    from /lib64/libpthread.so.0
  • #8 clone
    from /lib64/libc.so.6
  • #9 ??

Thread 8 (Thread 1098918208 (LWP 5089))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 camel_read
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #2 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #3 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #4 camel_stub_marshal_flush
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #5 camel_stub_marshal_decode_uint32
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #6 camel_stub_marshal_new
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #7 camel_stub_send
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #8 camel_exchange_folder_construct
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #9 exchange_path_to_physical
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #10 camel_store_get_folder
    from /opt/gnome/lib64/libcamel-provider-1.2.so.8
  • #11 mail_tool_uri_to_folder
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #12 mail_receive_uri
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #13 mail_enable_stop
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #14 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #15 start_thread
    from /lib64/libpthread.so.0
  • #16 clone
    from /lib64/libc.so.6
  • #17 ??

Thread 7 (Thread 1107310912 (LWP 5111))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 e_msgport_wait
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib64/libpthread.so.0
  • #4 clone
    from /lib64/libc.so.6
  • #5 ??

Thread 6 (Thread 1115703616 (LWP 5112))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 e_msgport_wait
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib64/libpthread.so.0
  • #4 clone
    from /lib64/libc.so.6
  • #5 ??

Thread 5 (Thread 1124096320 (LWP 5172))

  • #0 __select_nocancel
    from /lib64/libc.so.6
  • #1 e_msgport_wait
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib64/libpthread.so.0
  • #4 clone
    from /lib64/libc.so.6
  • #5 ??

Thread 4 (Thread 1132489024 (LWP 5188))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_106
    from /lib64/libpthread.so.0

Comment 1 palfrey 2007-02-14 16:40:11 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 334966 ***