Bug 1043675

Summary: [abrt] synergy-1.4.10-1.fc19: CServerApp::mainLoop: Process /usr/bin/synergys was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: MotherDawg <netwizurd>
Component: synergyAssignee: Christian Krause <chkr>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: chkr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5bce907f12d9957c8286b09b49e168a502bb1e71
Whiteboard: abrt_hash:2f5230219b8a3bb894f7b4738bfc96c6cdefe805
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:40:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description MotherDawg 2013-12-16 21:32:19 UTC
Description of problem:
Coming out of the Picture Folder screen saver,
Synergy,
started through a CLI tab off of MATE's Terminal 1.6.1
Crashed

All attempt to have it start at boot with a systemd service file result in Synergy

[~]# journalctl -xn
Dec 16 16:21:17 fedora.glalonde kernel: synergys[8719]: segfault at 0 ip 0000000000447761 sp 00007fff7bc95990 error 4 in synergys[400000+cc000]

Anything I can do... howler 

Version-Release number of selected component:
synergy-1.4.10-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/synergys --config /etc/synergy.conf -d ERROR -l /var/log/synergy.log
crash_function: CServerApp::mainLoop
executable:     /usr/bin/synergys
kernel:         3.11.10-200.fc19.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 CServerApp::mainLoop at /usr/src/debug/synergy-1.4.10-Source/src/lib/synergy/CServerApp.cpp:795
 #1 CApp::daemonMainLoop at /usr/src/debug/synergy-1.4.10-Source/src/lib/synergy/CApp.cpp:306
 #2 CArchDaemonUnix::daemonize at /usr/src/debug/synergy-1.4.10-Source/src/lib/arch/CArchDaemonUnix.cpp:126
 #3 CServerApp::runInner at /usr/src/debug/synergy-1.4.10-Source/src/lib/synergy/CServerApp.cpp:861
 #4 CApp::run at /usr/src/debug/synergy-1.4.10-Source/src/lib/synergy/CApp.cpp:272

Comment 1 MotherDawg 2013-12-16 21:32:23 UTC
Created attachment 837429 [details]
File: backtrace

Comment 2 MotherDawg 2013-12-16 21:32:25 UTC
Created attachment 837430 [details]
File: cgroup

Comment 3 MotherDawg 2013-12-16 21:32:26 UTC
Created attachment 837431 [details]
File: core_backtrace

Comment 4 MotherDawg 2013-12-16 21:32:28 UTC
Created attachment 837432 [details]
File: dso_list

Comment 5 MotherDawg 2013-12-16 21:32:29 UTC
Created attachment 837433 [details]
File: environ

Comment 6 MotherDawg 2013-12-16 21:32:30 UTC
Created attachment 837434 [details]
File: exploitable

Comment 7 MotherDawg 2013-12-16 21:32:32 UTC
Created attachment 837435 [details]
File: limits

Comment 8 MotherDawg 2013-12-16 21:32:33 UTC
Created attachment 837436 [details]
File: maps

Comment 9 MotherDawg 2013-12-16 21:32:36 UTC
Created attachment 837437 [details]
File: open_fds

Comment 10 MotherDawg 2013-12-16 21:32:37 UTC
Created attachment 837438 [details]
File: proc_pid_status

Comment 11 MotherDawg 2013-12-16 21:32:40 UTC
Created attachment 837439 [details]
File: var_log_messages

Comment 12 MotherDawg 2014-01-06 16:38:33 UTC
Another user experienced a similar problem:

Normal all day usage, passing from one screen to the other, it goes bonkers by itself.
I start Synergys  from the console with "synergys -f" with the following .conf:
*********************************************************************
cat /etc/synergy.conf
     1	section: screens
     2	   fedora.glal:
     3	   T430:
     4	end
     5	
     6	section: aliases
     7	   fedora.glal:
     8	      10.10.xx.xx
     9	end
    10	
    11	section: aliases
    12	   T430:
    13	      KOLW09
    14	end
    15	
    16	section: links
    17	   fedora.glal:
    18	      right = T430
    19	   T430:
    20	      left = fedora.glal
    21	end
    22	
    23	section: options
    24	screenSaverSync = false
    25	# My KVM uses Scroll Lock to switch screens, so set the
    26	# hotkey to lock the cursor to the screen to something else
    27	keystroke(f12) = lockCursorToScreen(toggle)
    28	end
*********************************************************************


I have been trying to write systemd service files for it but it's not working:

*********************************************************************
#cat /etc/systemd/system/synergys.service
     1	[Unit]
     2	Description=Synergy Server Daemon
     3	# After=network.target
     4	After=display-manager.service
     5	
     6	[Service]
     7	Type=forking
     8	ExecStart=/usr/bin/synergys --config /etc/synergy.conf -d ERROR -l /var/log/synergy.log
     9	ExecReload=/bin/kill -HUP $MAINPID
    10	KillMode=process
    11	KillMode=process
    12	Restart=always
    13	RestartSec=5
    14	User=%I
    15	
    16	[Install]
    17	WantedBy=graphical.target
*********************************************************************
#systemctl status synergys
synergys.service - Synergy Server Daemon
   Loaded: loaded (/etc/systemd/system/synergys.service; enabled)
   Active: activating (auto-restart) (Result: core-dump) since Mon 2014-01-06 10:54:53 EST; 2s ago
  Process: 20539 ExecStart=/usr/bin/synergys --config /etc/synergy.conf -d ERROR -l /var/log/synergy.log (code=exited, status=0/SUCCESS)
 Main PID: 20540 (code=dumped, signal=SEGV)
   CGroup: name=systemd:/system/synergys.service

Jan 06 10:54:53 fedora.glal systemd[1]: synergys.service: main process exited, code=dumped, status=11/SEGV
Jan 06 10:54:53 fedora.glal systemd[1]: Unit synergys.service entered failed state.
*********************************************************************
#journalctl -xn
-- Unit synergys.service has begun starting up.
Jan 06 10:59:11 fedora.glalonde systemd[1]: Started Synergy Server Daemon.
-- Subject: Unit synergys.service has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit synergys.service has finished starting up.
-- 
-- The start-up result is done.
Jan 06 10:59:11 fedora.glal kernel: synergys[21398]: segfault at 0 ip 0000000000447761 sp 00007fffacb2d410 error 4 in synergys[400000+cc
Jan 06 10:59:11 fedora.glal abrt-hook-ccpp[21401]: Not saving repeating crash in '/usr/bin/synergys'
Jan 06 10:59:11 fedora.glal systemd[1]: synergys.service: main process exited, code=dumped, status=11/SEGV
Jan 06 10:59:11 fedora.glal systemd[1]: Unit synergys.service entered failed state.
*********************************************************************

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/synergys --config /etc/synergy.conf -d ERROR -l /var/log/synergy.log
crash_function: CServerApp::mainLoop
executable:     /usr/bin/synergys
kernel:         3.12.5-200.fc19.x86_64
package:        synergy-1.4.10-1.fc19
reason:         synergys killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Fedora End Of Life 2015-01-09 20:52:50 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.

Comment 14 Fedora End Of Life 2015-02-17 19:40:35 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.