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 246384 - editing Task's Due Date causes crash
editing Task's Due Date causes crash
Status: RESOLVED DUPLICATE of bug 245236
Product: evolution
Classification: Applications
Component: Tasks
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-07-15 15:55 UTC by Greg Hewett
Modified: 2003-07-16 19:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Greg Hewett 2003-07-15 15:55:43 UTC
Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.3
os_details: Ximian, Inc.
Synopsis: Editing Task's Due Date Causes Crash
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
When I  create several tasks using the inline editing of the available
fields everything works great.  When I double click a task, and change
the date, then click save, the evolution crashes.  I have experienced
this is several areas where there calendar wiget is used.  I will file
bugs for those as I find them.

Steps to reproduce the problem:
1.   Create a Task
2.   Double Click the Task, and edit the date
3.  Click Save

Actual Results:
Evolution Crashes

Expected Results:
Window Should Close

How often does this happen?
Frequently  (No all the time)

Additional Information:



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 1092634144 (LWP 3083)]
[New Thread 1167306032 (LWP 3132)]
[New Thread 1150520624 (LWP 3130)]
[New Thread 1142127920 (LWP 3129)]
[New Thread 1133735216 (LWP 3128)]
[New Thread 1125342512 (LWP 3126)]
[New Thread 1116949808 (LWP 3125)]
0xffffe002 in ?? ()

Thread 1 (Thread 1092634144 (LWP 3083))

  • #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 ??

Comment 1 Gerardo Marin 2003-07-16 19:20:53 UTC

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