Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.0 detected a crash. How to reproduce ----- 1. Deleting an unplayed audio podcast in Miro Attached file: backtrace cmdline: /usr/bin/python /usr/bin/miro.real component: python executable: /usr/bin/python kernel: 2.6.31.9-174.fc12.i686 package: python-2.6.2-2.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 381159 [details] File: backtrace
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? What version of Miro do you have installed? Looking at the backtrace, it looks like the problem occurred in thread #1 in gtk_tree_model_get_value (frame #6); I'm not familiar with Miro and I'm not sure if the reference to /usr/lib/xulrunner-1.9.1/libxul.so in frame #2 is accurate. Reassigning component from "python" to "Miro"
Version is Miro 2.5.4 (1e20db82). Issue happens occasionally (i.e., perhaps 5% of time). Have not tried running the program from a terminal.
Will: any ideas? Is this a xulrunner problem? Perhaps related to bug #551868?
The top/bottom of thread 1 is this: Thread 1 (Thread 2088): #0 0x0013a416 in __kernel_vsyscall () No symbol table info available. #1 0x00a19000 in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42 resultvar = <value optimized out> resultvar = <value optimized out> pid = <value optimized out> #2 0x021a9757 in ?? () from /usr/lib/xulrunner-1.9.1/libxul.so No symbol table info available. #3 <signal handler called> No symbol table info available. #4 0x00544d62 in g_sequence_iter_get_sequence () from /lib/libglib-2.0.so.0 No symbol table info available. #5 0x05de754c in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #6 0x05ee6943 in gtk_tree_model_get_value () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #7 0x010290a9 in gtk_text_view_set_border_window_size () from /usr/lib/python2.6/site-packages/gtk-2.0/gtk/_gtk.so No symbol table info available. ... I've never seen this problem before and I have no idea if it could be related to bug #551868. I'm puzzled.
Miro-3.0.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc13
Miro-3.0.2-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc12
Miro-3.0.2-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 Miro'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc12
Miro-3.0.2-1.fc13 has been pushed to the Fedora 13 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 Miro'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc13
Miro-3.0.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Miro-3.0.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.