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 252405 - crash while dragging to make a selection
crash while dragging to make a selection
Status: RESOLVED DUPLICATE of bug 240627
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-12-21 00:00 UTC by Edward J. Huff
Modified: 2003-12-23 19:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Edward J. Huff 2003-12-21 00:00:44 UTC 
Package: Evolution
Priority: Normal
Version: 1.2.2
Synopsis: crash while dragging to make a selection
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:

In main evolution window, selected a vfolder, selected a message,
clicked on text of message and dragged to right.
Selection was made as usual.  But mouse moved up a tiny amount, and
selection changed to previous line.
Then evolution mail crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:
crash segfault

Expected Results:
no crash, selection made...

How often does this happen?  I think this is the first time, but I did
get
another crash in email that might have been the same thing.


Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1091467264 (LWP 11076)]
[New Thread 1150528304 (LWP 13523)]
[New Thread 1142135600 (LWP 11205)]
[New Thread 1133742896 (LWP 11134)]
[New Thread 1125350192 (LWP 11130)]
[New Thread 1116957488 (LWP 11127)]
[New Thread 1102838576 (LWP 11126)]
0xffffe002 in ?? ()

+ Trace 42805

Thread 1 (Thread 1091467264 (LWP 11076))

  • #0 ??
  • #1 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #2 message_browser_get_type
  • #3 <signal handler called>
  • #4 ??
  • #5 html_image_factory_unregister
    from /usr/lib/libgtkhtml-1.1.so.3
  • #6 html_image_get_actual_height
    from /usr/lib/libgtkhtml-1.1.so.3
  • #7 html_object_destroy
    from /usr/lib/libgtkhtml-1.1.so.3
  • #8 html_checkbox_new
    from /usr/lib/libgtkhtml-1.1.so.3
  • #9 html_cluealigned_new
    from /usr/lib/libgtkhtml-1.1.so.3
  • #10 html_object_destroy
    from /usr/lib/libgtkhtml-1.1.so.3
  • #11 html_checkbox_new
    from /usr/lib/libgtkhtml-1.1.so.3
  • #12 html_object_destroy
    from /usr/lib/libgtkhtml-1.1.so.3
  • #13 html_selection_current_time
    from /usr/lib/libgtkhtml-1.1.so.3
  • #14 html_engine_activate_selection
    from /usr/lib/libgtkhtml-1.1.so.3
  • #15 html_engine_update_selection_active_state
    from /usr/lib/libgtkhtml-1.1.so.3
  • #16 gtk_html_get_url_object_relative
    from /usr/lib/libgtkhtml-1.1.so.3
  • #17 gtk_marshal_BOOL__POINTER
    from /usr/lib/libgtk-1.2.so.0
  • #18 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #19 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #20 gtk_widget_event
    from /usr/lib/libgtk-1.2.so.0
  • #21 gtk_propagate_event
    from /usr/lib/libgtk-1.2.so.0
  • #22 gtk_main_do_event
    from /usr/lib/libgtk-1.2.so.0
  • #23 gdk_wm_protocols_filter
    from /usr/lib/libgdk-1.2.so.0
  • #24 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #25 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #26 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #29 main
  • #30 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 


Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Gerardo Marin 2003-12-23 19:46:34 UTC 
This is fixed a long ago. Please upgrade

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