abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: xiphos component: xiphos executable: /usr/bin/xiphos kernel: 2.6.31.6-134.fc12.x86_64 package: xiphos-3.1.1-1.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 376162 [details] File: backtrace
Can you please tell us what you were doing when this crash occur?
(In reply to comment #2) > Can you please tell us what you were doing when this crash occur? I was simply launching the application. I deleted the files in my .xiphos folder and the problem resolved temporarily, but that is the second time I have had to do that.
Can you please save your .xiphos folder for further analysis if this crash occur again, thanks.
Created attachment 379467 [details] My .xiphos folder. This is my .xiphos folder with the same crash reoccuring.
xiphos-3.1.3-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/xiphos-3.1.3-1.fc12
xiphos-3.1.3-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/xiphos-3.1.3-1.fc11
xiphos-3.1.3-1.fc11 has been pushed to the Fedora 11 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 xiphos'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xiphos-3.1.3-1.fc11
xiphos-3.1.3-1.fc12 has been pushed to the Fedora 12 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 xiphos'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xiphos-3.1.3-1.fc12
xiphos-3.1.3-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
xiphos-3.1.3-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.