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 351064 - Crash from preferences window of Evolution
Crash from preferences window of Evolution
Status: RESOLVED DUPLICATE of bug 345316
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-08-12 18:03 UTC by Matthew Beals
Modified: 2007-02-28 15:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Matthew Beals 2006-08-12 18:02:57 UTC 
From:  mattb108@gmail.com
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Crash from preferences window

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: Crash from preferences window
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Crashed. <boom!>

Steps to reproduce the crash:
1. go to todo preferences, display tab
2. check "hide completed tasks"
3. close preferences
4. fiddle with tasks, notice that old tasks did not hide themselves
5. go back to preferences
6. uncheck, recheck "hide completed tasks"
7. change "hide after x days" to x=0

Expected Results:
crash.

How often does this happen?
once

Additional Information:
started up evolution again and completed tasks were hidden, tried to
reproduce bug and could not.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231288096 (LWP 5744)]
[New Thread -1260237904 (LWP 5821)]
[New Thread -1259971664 (LWP 5754)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 70314

Thread 1 (Thread -1231288096 (LWP 5744))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 e_cal_menu_target_new_select
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #6 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #7 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #8 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 e_tasks_get_tasks_menu
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #14 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 e_table_save_state
    from /usr/lib/evolution/2.6/libetable.so.0
  • #20 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 e_selection_model_selection_changed
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #26 e_selection_model_array_delete_rows
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #27 e_table_search_backspace
    from /usr/lib/evolution/2.6/libetable.so.0
  • #28 e_util_marshal_VOID__INT_INT
    from /usr/lib/evolution/2.6/libeutil.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 e_table_model_rows_deleted
    from /usr/lib/evolution/2.6/libetable.so.0
  • #34 e_table_model_row_deleted
    from /usr/lib/evolution/2.6/libetable.so.0
  • #35 e_calendar_table_process_completed_tasks
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #36 e_tasks_get_calendar_table
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #37 gconf_client_change_set_from_current
    from /usr/lib/libgconf-2.so.4
  • #38 gconf_listeners_notify
    from /usr/lib/libgconf-2.so.4
  • #39 gconf_client_change_set_from_current
    from /usr/lib/libgconf-2.so.4
  • #40 gconf_client_notify
    from /usr/lib/libgconf-2.so.4
  • #41 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #43 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #44 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #45 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #46 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-08-12 18:03 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.
Comment 1 Matthew Beals 2006-08-12 18:11:11 UTC 
I should have added (this is my bug)

Crash Description:
There was an error box, but it was unreadable as the Ubuntu bug buddy window popped up over it. I tried to move this window to see the error, but the Evolution window (including the error box) would not update properly, so it was just a blank frame or with "stutter marks" as I dragged other windows over it.
Comment 2 André Klapper 2006-08-13 12:00:59 UTC 
stacktrace looks a bit like bug 345316
Comment 3 André Klapper 2007-02-28 15:06:47 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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