abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: planner comment: Traceback happened when attempting to move duration bar with milestone selected. component: planner executable: /usr/bin/planner kernel: 2.6.37-2.fc15.i686 package: planner-0.14.4-31.fc15 reason: Process /usr/bin/planner was killed by signal 11 (SIGSEGV) release: Fedora release 15 (Rawhide) time: 1297038730 uid: 500 How to reproduce ----- 1. Create new task 2. Attempt to drag progress bar with milestone selected. 3.
Created attachment 477363 [details] File: backtrace
symbols are unfortunately missing. I can't reproduce this with a simple example. Are you able to reproduce this ?
Yes. 1. Create a new task. 2. Select Note tab and attempt to input a text. Crash should occur.
Nope, no crash for me. I'm probably failing to do this in the right way, any chance you could attach an example that fails when you try it.
Created attachment 478188 [details] Planner crash video Reproducing the crash via video
Thanks for the video. Strangely enough this doesn't crash here, but valgrind is giving me a likely candidate for this crash. Let me try and fix that, and make an update and see if it fixes your crash.
Reported during f15, so building into that. Hopefully 0.14.4-34.fc15 resolves this for you. If it doesn't then please reopen and try... export G_SLICE=always-malloc sudo yum -y install valgrind valgrind planner > /tmp/valgrind.log 2>&1 and attach that output
planner-0.14.4-34.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/planner-0.14.4-34.fc15
planner-0.14.4-34.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update planner'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/planner-0.14.4-34.fc15
planner-0.14.4-34.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.