Red Hat Bugzilla – Full Text Bug Listing
|Summary:||[abrt] synergy-plus-1.3.4-5.fc13: raise: Process /usr/bin/synergyc was killed by signal 6 (SIGABRT)|
|Component:||synergy-plus||Assignee:||Matthias Saou <matthias>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||bugzilla, matthias, rprice, sscott, suttles, waterfoul|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-28 10:24:25 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description rucker 2010-08-19 07:26:14 EDT
abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: synergyc -n sec 192.168.1.97 component: synergy-plus crash_function: raise executable: /usr/bin/synergyc kernel: 188.8.131.52-147.2.4.fc13.x86_64 package: synergy-plus-1.3.4-5.fc13 rating: 4 reason: Process /usr/bin/synergyc was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1282172815 uid: 500
Comment 1 rucker 2010-08-19 07:26:18 EDT
Created an attachment (id=439654) File: backtrace
Comment 2 Gerhard 2010-09-16 00:29:21 EDT
Package: synergy-plus-1.3.4-5.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- It should start with a special configuration when a special condition in NetworkManagerDispatcher is fulfilled. At the first start, the crash happens. After running the script a second time, everything is fine.
Comment 3 Robin R. Price II 2010-09-22 15:02:41 EDT
Package: synergy-plus-1.3.4-5.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Launched synergy 2. 3.
Comment 4 Sullivan G. Scott, Jr. 2010-11-01 09:14:16 EDT
Package: synergy-plus-1.3.4-5.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Unknown when/how this crash happens. 2. 3.
Comment 5 Bug Zapper 2011-06-01 07:08:29 EDT
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
Comment 6 Bug Zapper 2011-06-28 10:24:25 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.