abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: pioneers component: pioneers crash_function: raise executable: /usr/bin/pioneers global_uuid: 5667c5a68c9f0f3edaa421192f789814a8b03fe2 kernel: 2.6.32.11-99.fc12.i686.PAE package: pioneers-0.12.2-4.fc12 rating: 4 reason: Process /usr/bin/pioneers was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start local server pioneers 2. launch gtk client
Created attachment 415758 [details] File: backtrace
*** Bug 615821 has been marked as a duplicate of this bug. ***
I think I have a fix for this problem. It's somewhat of a workaround. Changes the user tries to make outside of a session are discarded, thus avoiding the tripped assertion that causes the crash. It would be preferable to simply not allow the profile to work outside of a session, but that requires much more invasive changes (like turning off the menu entry and the key combo) which I was loathe to get into. I'll try to get this into a build shortly for F-12, F-13, F-14, and devel. ---- diff -uNr pioneers-0.12.2-orig/client/gtk/name.c pioneers-0.12.2/client/gtk/name.c --- pioneers-0.12.2-orig/client/gtk/name.c 2008-05-01 15:05:57.000000000 -0400 +++ pioneers-0.12.2/client/gtk/name.c 2010-08-01 17:29:58.284181851 -0400 @@ -47,7 +47,7 @@ gpointer user_data) { DialogData *dialog = user_data; - if (response_id == GTK_RESPONSE_OK) { + if ((response_id == GTK_RESPONSE_OK) && (callback_mode != MODE_INIT)) { const gchar *new_name = gtk_entry_get_text(GTK_ENTRY(dialog->name_entry)); const gchar *new_style = dialog->current_style;
pioneers-0.12.3-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/pioneers-0.12.3-2.fc13
pioneers-0.12.2-5.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pioneers-0.12.2-5.fc12
pioneers-0.12.3-2.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/pioneers-0.12.3-2.fc14
pioneers-0.12.2-5.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 pioneers'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pioneers-0.12.2-5.fc12
pioneers-0.12.3-2.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 pioneers'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pioneers-0.12.3-2.fc13
pioneers-0.12.3-2.fc14 has been pushed to the Fedora 14 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 pioneers'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pioneers-0.12.3-2.fc14
Reporter and others: Please use the above instructions (comment 7 for F12, comment 8 for F13) to test this update, and give your feedback at the URL provided. If you have a Fedora account, please login to provide your feedback so you get credit for the contribution. Thanks!
In Fedora 13, following the instructions from Comment 8 I'm no longer able to reproduce the bug. I'll try to get a Fedora 12 box to test it. FAS: casep Thanks!
pioneers-0.12.2-5.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
pioneers-0.12.3-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
pioneers-0.12.3-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.