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 480951 - crash in Evolution: I was browsing through a...
crash in Evolution: I was browsing through a...
Status: RESOLVED DUPLICATE of bug 340165
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-09-27 13:37 UTC by Kalle Persson
Modified: 2007-10-01 06:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Kalle Persson 2007-09-27 13:37:00 UTC 
What were you doing when the application crashed?
I was browsing through an email and clicking the attachment buttons (with arrow) of the three attachments that were jpg's. When I clicked the last one, Evolution crashed.


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

Memory status: size: 848646144 vsize: 848646144 resident: 138895360 share: 24694784 rss: 163590144 rss_rlim: 893900800
CPU usage: start_time: 1190890787 rtime: 2139 utime: 1956 stime: 183 cutime:220 cstime: 24 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 47370296165056 (LWP 7593)]
[New Thread 1141147968 (LWP 16983)]
[New Thread 1132755264 (LWP 16911)]
[New Thread 1124096320 (LWP 16908)]
[New Thread 1124362560 (LWP 16895)]
[New Thread 1115703616 (LWP 7670)]
[New Thread 1107310912 (LWP 7669)]
[New Thread 1090525504 (LWP 7643)]
[New Thread 1098918208 (LWP 7642)]
[New Thread 1082132800 (LWP 7637)]
0x00002b153f16fc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 165915

Thread 1 (Thread 47370296165056 (LWP 7593))

  • #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 g_str_hash
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #4 g_hash_table_lookup
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #5 em_cache_lookup
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #6 em_icon_stream_is_resized
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #7 em_format_html_display_new
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #8 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #13 gtk_widget_get_default_style
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #15 gdk_add_client_message_filter
    from /opt/gnome/lib64/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #17 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #19 bonobo_main
    from /opt/gnome/lib64/libbonobo-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Tobias Mueller





          2007-09-29 00:31:04 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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






Comment 2


Kalle Persson





          2007-10-01 06:44:17 UTC
        



(In reply to comment #1)
> Thanks for taking the time to report this bug.
> This particular bug has already been reported into our bug tracking system, but
> we are happy to tell you that the problem has already been fixed. It should be
> solved in the next software version. You may want to check for a software
> upgrade.
> 
> 
> *** This bug has been marked as a duplicate of 340165 ***
> 

Good to hear, thanks!