abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: ekiga comment: ekiga crashes when started from automatically. I guess this is because of a race condition between nm getting the network up and ekiga connecting. Usually it is fine to start ekiga before wireless is up, but sometimes ekiga crashes on startup. component: ekiga executable: /usr/bin/ekiga kernel: 2.6.32.9-70.fc12.x86_64 package: ekiga-3.2.6-1.fc12 rating: 4 reason: Process /usr/bin/ekiga was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Put ekiga in your autostart 2. Log in a few times 3. ekiga starts before wireless is up and sometimes it crashes
Created attachment 401546 [details] File: backtrace
*** Bug 595132 has been marked as a duplicate of this bug. ***
ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12
ekiga-3.2.7-1.fc12, opal-3.6.8-1.fc12, ptlib-2.6.7-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 ekiga opal ptlib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12
ekiga-3.2.7-1.fc12, opal-3.6.8-1.fc12, ptlib-2.6.7-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.