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 582590 - evolution crashed : clicked on a new mail to view it in preview
evolution crashed : clicked on a new mail to view it in preview
Status: RESOLVED DUPLICATE of bug 540269
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-14 10:18 UTC by Akhil Laddha
Modified: 2013-09-13 01:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Akhil Laddha 2009-05-14 10:18:37 UTC
Evolution 2.27.1

akhil@lakhil-genesis:~> rpm -qa | grep bonobo
libbonoboui-2.24.1-3.3
libbonoboui-doc-2.24.1-3.3
libbonoboui-debuginfo-2.24.1-3.3
libbonoboui-lang-2.24.1-3.3
libbonobo-doc-2.24.1-3.2
libbonobo-devel-2.24.1-3.2
mingw32-libbonobo-lang-2.24.1-1.3
libbonobo-debuginfo-2.24.1-3.2
mingw32-libbonoboui-2.24.1-1.3
mingw32-libbonoboui-lang-2.24.1-1.3
libbonobo-2.24.1-3.2
libbonobo-lang-2.24.1-3.2
mingw32-libbonobo-2.24.1-1.3
libbonoboui-devel-2.24.1-3.3


Backtrace was generated from '/home/akhil/opt/gnome2/bin/evolution'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xabb70b90 (LWP 5641)]
[New Thread 0xad5bdb90 (LWP 5636)]
[New Thread 0xa82fbb90 (LWP 5628)]
[New Thread 0xa8afcb90 (LWP 5627)]
[New Thread 0xa9afeb90 (LWP 5625)]
[New Thread 0xac371b90 (LWP 5545)]
[New Thread 0xacbb5b90 (LWP 5543)]
[New Thread 0xaddbeb90 (LWP 5520)]
[New Thread 0xaedc0b90 (LWP 5519)]
[New Thread 0xae5bfb90 (LWP 5518)]
[New Thread 0xb49c6b90 (LWP 5515)]
0xffffe430 in __kernel_vsyscall ()

Thread 2 (Thread 0xabb70b90 (LWP 5641))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_89
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 em_format_is_attachment
    at em-format.c line 957
  • #6 em_format_part_as
    at em-format.c line 623
  • #7 em_format_part
    at em-format.c line 656
  • #8 efh_multipart_related
    at em-format-html.c line 1145
  • #9 em_format_part_as
    at em-format.c line 626
  • #10 em_format_part
    at em-format.c line 653
  • #11 efh_format_message
    at em-format-html.c line 2088
  • #12 efh_format_exec
    at em-format-html.c line 1274
  • #13 mail_msg_proxy
    at mail-mt.c line 520
  • #14 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #15 g_thread_create_proxy
    at gthread.c line 635
  • #16 start_thread
    from /lib/libpthread.so.0
  • #17 clone
    from /lib/libc.so.6


---- Critical and fatal warnings logged during execution ----

** camel **: camel_object_is: assertion `o != NULL' failed 
** camel **: camel_data_wrapper_get_mime_type: assertion `CAMEL_IS_DATA_WRAPPER (data_wrapper)' failed 


----------- .xsession-errors (17868 sec old) ---------------------
** (nautilus:17665): WARNING **: Unable to add monitor: Not supported
** (nautilus:17665): WARNING **: Unable to add monitor: Not supported
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
--------------------------------------------------
Comment 1 Akhil Laddha 2009-05-14 10:19:19 UTC
could be related to bug 513445 , bug 474888
Comment 2 Matthew Barnes 2009-05-14 14:17:14 UTC
Weird, the crash is happening in BonoboUI.  Is this repeatable?
Comment 3 Akhil Laddha 2009-05-15 03:28:50 UTC
i got 3 times in last 2 days. But i don't have exact steps / specific mail by which it can be reproduced.  
Comment 4 Milan Crha 2009-05-21 17:41:30 UTC
No no, this is an attachment thing,

Thread 2
  • #4 <signal handler called>
  • #5 em_format_is_attachment
    at em-format.c line 957
  • #6 em_format_part_as
    at em-format.c line 623
  • #7 em_format_part
should be message specific. Akhil, try to find some message with "multipart/related" inside it, that should be the one. Please report back and mark as duplicate of bug #540269. I would like to have data first, though.
Comment 5 Akhil Laddha 2009-06-24 07:08:55 UTC
I couldn't find message so marking this a dupe as mentioned by Milan.



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