Description of problem: Just stop effort tracking. Version-Release number of selected component: taskcoach-1.2.6-4.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/taskcoach crash_function: wxMenubarSetInvokingWindow executable: /usr/bin/python2.7 kernel: 3.8.4-202.fc18.x86_64 uid: 1000 ureports_counter: 1 var_log_messages: Mar 27 18:12:57 brainbug-nb abrt[8868]: Saved core dump of pid 5061 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-03-27-18:12:57-5061 (96985088 bytes) xsession_errors: /usr/lib64/python2.7/site-packages/revelation/ui.py:1745: GtkWarning: Inserting action group 'find' into UI manager which already has a group with this name Truncated backtrace: Thread no. 1 (10 frames) #0 wxMenubarSetInvokingWindow at src/gtk/menu.cpp:263 #1 wxMenu::GtkAppend at src/gtk/menu.cpp:1276 #2 wxMenu::DoAppend at src/gtk/menu.cpp:1306 #3 _wrap_Menu_AppendSubMenu at src/gtk/_core_wrap.cpp:44292 #4 ext_do_call at /usr/src/debug/Python-2.7.3/Python/ceval.c:4408 #5 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2779 #6 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:3330 #7 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4194 #8 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
Created attachment 717518 [details] File: backtrace
Created attachment 717519 [details] File: cgroup
Created attachment 717520 [details] File: core_backtrace
Created attachment 717521 [details] File: dso_list
Created attachment 717522 [details] File: environ
Created attachment 717523 [details] File: limits
Created attachment 717524 [details] File: maps
Created attachment 717525 [details] File: open_fds
Created attachment 717526 [details] File: proc_pid_status
Created attachment 717527 [details] File: smolt_data
Can you please be a bit more specific about the circumstances? I have created, started, stopped, re-started and re-stopped numerous efforts and everything seems to work fine.
Sorry for not being too specific. But this issue happened some time ago. Haven't experienced this problem for a while, so maybe something have changed recently. By now it's fine for me.
Thank you. I will close the bug as WORKSFORME then.