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 256202 - Task proposals crash Evolution
Task proposals crash Evolution
Status: RESOLVED DUPLICATE of bug 247667
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-03-30 05:45 UTC by topiolli
Modified: 2004-05-13 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description topiolli 2004-03-30 05:45:01 UTC
Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.3
os_details: Ximian, Inc.
Synopsis: Task proposals crash Evolution
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:

I have received a task proposal via e-mail. The mail opens nicely and
displays the attachment in-line just like I'm assuming. When I open a
new message after this, the application crashes.

Steps to reproduce the problem:
1. Open a task proposal message and scroll the in-line attachment into
the view. It is not necessary to actually do anything with the task
component, but it is necessary to view it.
2. Open another message by clicking its title in the list.
3. Crash.

How often does this happen?

I usually need two iterations to crash Evolution. That is, I need to
open two task proposals and any other messages in a sequence (or the
same proposal twice, makes no difference). Sometimes one time is enough.
Sometimes three iterations are needed. But it always happens before the
fourth try.

Additional information:

Please get it fixed soon :)


Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1092658720 (LWP 2992)]
[New Thread 1150520624 (LWP 2999)]
[New Thread 1142127920 (LWP 2998)]
[New Thread 1133735216 (LWP 2997)]
[New Thread 1125342512 (LWP 2996)]
[New Thread 1116949808 (LWP 2995)]
0xffffe002 in ?? ()

Thread 1 (Thread 1092658720 (LWP 2992))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 evolution_storage_set_view_factory_new_view
  • #3 <signal handler called>
  • #4 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_widget_get_child_visible
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_widget_has_screen
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_entry_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #9 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #14 main
  • #15 __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 2004-05-13 16:29:53 UTC

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