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 246690 - Crashed opening contact.
Crashed opening contact.
Status: RESOLVED DUPLICATE of bug 245236
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-07-21 22:29 UTC by fdjsouthey
Modified: 2003-07-23 22:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description fdjsouthey 2003-07-21 22:29:07 UTC
Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.3
os_details: Ximian, Inc.
Synopsis: Crashed opening contact.
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:

Ok.  A bit confusing.

I was editing a contact with a large "note" or "details" field (can't
remember what it's called).  I greatly shortened the note and then
Save/Closed the contact and Evolution crashed.  

Then, Bug Buddy appeared, asked to download updated information,
appeared to download correctly, but then crashed before reaching the
next window (i.e. Bug Buddy crashed).   This triggered a second Bug
Buddy so, since I'm always game for a potentially futile scenarios, I
tried to process that bug.  It was filed correctly.

So, I ran Evolution again and double-clicked the bad contact (which
appeared to have saved the changes to the note) and Evolution crashed
again, and this is the resulting Bug Buddy report.

Let's recap for the people who weren't paying attention:

- Evolution Contacts crashed triggering Bug Buddy #1.
- Bug Buddy #1 crashed triggering Bug Buddy #2.
- Bug Buddy #2 completed successfully.
- Evolution was opened again and Contacts crashed triggering Bug Buddy
#3.
- This is Bug Buddy #3's report.

Let me know if you want to see the bug report from Bug Buddy #2 (can't
get mail right now because Evolution is in crash limbo).


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 16384 (LWP 26933)]
[New Thread 32769 (LWP 26936)]
[New Thread 16386 (LWP 26937)]
[New Thread 32771 (LWP 26938)]
[New Thread 49156 (LWP 26939)]
[New Thread 65541 (LWP 26940)]
0x4010e844 in waitpid ()
   from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 26933))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 evolution_storage_set_view_factory_new_view
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_widget_get_child_visible
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_widget_has_screen
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_entry_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #10 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #16 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 fdjsouthey 2003-07-21 22:45:40 UTC
Launched Evolution again right after filing, check some mail and then
tried to reopen the contact in question.  There was no problem reading
it, and also changing the text in the 'preview version', but opening
the contact as a dialog, adding a blank line, and clicking Save
crashed it again.

I will attach the second stack trace (although it looks similar based
on my cursory inspection).

I have reproduced this a third time now by deleting a line and saving.

This might be the return of a crash I saw a long time ago that was
related to the same contact and the editing of a large note.  That was
bug 215550 , closed because I was unable to reproduce it.

Let me know if you want any files.

Note also that I'm using Redhat 9, so there could, just possibly, be 
a pthreads issue (although the crash from long ago was RH 7.1).

Here's the URL for the Gnome Bugzilla entry for the Bug Buddy crash,
in case you are interested:

http://bugzilla.gnome.org/show_bug.cgi?id=118028
Comment 2 fdjsouthey 2003-07-21 23:04:49 UTC
*** bug 246691 has been marked as a duplicate of this bug. ***
Comment 3 fdjsouthey 2003-07-21 23:06:55 UTC
Actually, I seem to crash when editing even just the email address
field.  I have reproduced this several times now with different addresses.

Changes are saved.  Dialog seems to close and then the crash occurs
(perhaps when updating the contact list view).

See dupe for yet another stack trace.
Comment 4 Gerardo Marin 2003-07-23 22:07:25 UTC

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