abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: synergys component: synergy-plus executable: /usr/bin/synergys kernel: 2.6.32.9-70.fc12.x86_64 package: synergy-plus-1.3.4-3.fc12 rating: 4 reason: Process /usr/bin/synergys was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 402395 [details] File: backtrace
I think this crash is related to the fact that I shut down the other (synergy-slave) machine.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
See also bug 649944
*** Bug 596808 has been marked as a duplicate of this bug. ***
*** Bug 597211 has been marked as a duplicate of this bug. ***
*** Bug 598782 has been marked as a duplicate of this bug. ***
*** Bug 602420 has been marked as a duplicate of this bug. ***
*** Bug 602969 has been marked as a duplicate of this bug. ***
*** Bug 603966 has been marked as a duplicate of this bug. ***
*** Bug 605595 has been marked as a duplicate of this bug. ***
*** Bug 605602 has been marked as a duplicate of this bug. ***
*** Bug 606358 has been marked as a duplicate of this bug. ***
*** Bug 609189 has been marked as a duplicate of this bug. ***
*** Bug 612496 has been marked as a duplicate of this bug. ***
*** Bug 615772 has been marked as a duplicate of this bug. ***
*** Bug 616132 has been marked as a duplicate of this bug. ***
*** Bug 616990 has been marked as a duplicate of this bug. ***
*** Bug 622950 has been marked as a duplicate of this bug. ***
*** Bug 721224 has been marked as a duplicate of this bug. ***
*** Bug 652219 has been marked as a duplicate of this bug. ***
*** Bug 649944 has been marked as a duplicate of this bug. ***
*** Bug 695049 has been marked as a duplicate of this bug. ***
*** Bug 654308 has been marked as a duplicate of this bug. ***
*** Bug 656416 has been marked as a duplicate of this bug. ***
*** Bug 694109 has been marked as a duplicate of this bug. ***
*** Bug 769362 has been marked as a duplicate of this bug. ***
Backtrace analysis of bugs across components suggests the actual bug is in component libX11 instead of component synergy-plus, reassigning to libX11. Bugs which were found to be similar to this bug: synergy: bug #540412, bug #540458, bug #543206, bug #543620, bug #547613, bug #550025, bug #554096, bug #554193, bug #565217, bug #582797, bug #588561, bug #589381, bug #589382, bug #593501, bug #593939, bug #623428, bug #632201, bug #765635, bug #765640, bug #769362 synergy-plus: bug #545364, bug #555251, bug #562674, bug #576723, bug #586137, bug #587141, bug #591374, bug #591375, bug #596808, bug #597211, bug #598782, bug #601441, bug #602420, bug #602969, bug #603966, bug #604241, bug #604675, bug #605595, bug #605602, bug #606358, bug #609189, bug #612372, bug #612496, bug #615772, bug #616132, bug #616990, bug #621723, bug #622950, bug #623244, bug #624685, bug #625419, bug #627825, bug #630329, bug #643064, bug #649944, bug #651755, bug #652219, bug #654308, bug #656416, bug #672915, bug #694109, bug #695049, bug #721224, bug #738828, bug #743633 This comment is automatically generated.
*** Bug 743633 has been marked as a duplicate of this bug. ***
*** Bug 765640 has been marked as a duplicate of this bug. ***
*** Bug 738828 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug is being flagged by abrt in FC17. Can we please have it reopened or have abrt fixed to not find CLOSED bugs?
And now it's being flagged in FC18. I ask again, can we please have this bug re-opened since clearly it's not been fixed yet.
Change status from "Closed" to "Assigned".
Can we also have the version field updated to FC18 since that's where I'm seeing it?
I'm afraid I have no clue what caused this; ABRT reports this occasionally at login, usually the day after it happened, so I assume it's happening either during logout, or prior to a reboot. (I start up synergy at login.) backtrace_rating: 4 Package: synergy-1.3.7-6.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.