Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Ubuntu 14.04 Synergy keeps shutting down


Recommended Posts

Bevan Simpkin
Hello, Server on Windows 10, client on Ubuntu 14.04 Works well, until switching screens after a long pause. Then, client shuts down. Swap cables, click on the synergy app, and oh, lets wake up again. Rinse and repeat. Any suggestions?
Link to post
Share on other sites
  • 2 weeks later...
Patrick Kaufmann
I seem to be experiencing a similar issue with debian and Windows 10. Every now and then it segfaults on me: [code]Program received signal SIGSEGV, Segmentation fault. 0x000000010001fffd in ?? () (gdb) bt #0 0x000000010001fffd in ?? () #1 0x000000000046b972 in XWindowsUtil::ErrorLock::internalHandler(_XDisplay*, XErrorEvent*) () #2 0x00007ffff74b545d in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #3 0x00007ffff74b23c7 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x00007ffff74b2485 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x00007ffff74b3430 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #6 0x00007ffff74aeced in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x000000000046c123 in XWindowsUtil::ErrorLock::~ErrorLock() () #8 0x000000000046ac51 in XWindowsScreenSaver::activateDPMS(bool) () #9 0x000000000046b27a in XWindowsScreenSaver::deactivate() () #10 0x0000000000459146 in XWindowsScreen::enter() () #11 0x000000000044f55b in synergy::Screen::enter(unsigned int) () #12 0x00000000004530cc in Client::enter(int, int, unsigned int, unsigned int, bool) () #13 0x0000000000455ff5 in ServerProxy::enter() () #14 0x0000000000457a9f in ServerProxy::parseMessage(unsigned char const*) () #15 0x0000000000455c15 in ServerProxy::handleData(Event const&, void*) () #16 0x000000000043eea8 in EventQueue::dispatchEvent(Event const&) () #17 0x0000000000486429 in StreamFilter::filterEvent(Event const&) () #18 0x000000000047e2ce in PacketStreamFilter::filterEvent(Event const&) () #19 0x000000000043eea8 in EventQueue::dispatchEvent(Event const&) () #20 0x00000000004424dc in EventQueue::loop() ()[/code] I'll let you know if I find out anything.
Link to post
Share on other sites
  • 4 weeks later...
Tehrasha Darkon
I get similar here, but with Win7. The linux client crashes so often, that I have left a mouse plugged into it, and leave the client GUI up on one of the workspaces at all times. The majority of the time, the linux client has not registered that the connection has been lost, and other times it reports 'server is dead'. In either case, if I toggle the STOP/START button on the GUI and I am up and running again. Probably not related, but I also cannot manage to share clipboard contents across machines more than once. I have to force stop/start the server for it to work again.... once.
Link to post
Share on other sites
Paskal Gallerneault
[quote="Tehrasha Darkon"]I get similar here, but with Win7. The linux client crashes so often, that I have left a mouse plugged into it, and leave the client GUI up on one of the workspaces at all times. The majority of the time, the linux client has not registered that the connection has been lost, and other times it reports 'server is dead'. In either case, if I toggle the STOP/START button on the GUI and I am up and running again. Probably not related, but I also cannot manage to share clipboard contents across machines more than once. I have to force stop/start the server for it to work again.... once.[/quote] I am having this exact problem with Win7 and Ubuntu 14.04 and Ubuntu 15.05 I have tried installing the server on either, no difference. The Linux client either crashes or like Tehrasha stated it reports the server as "dead" Are there any updates to this? Can we expect a new version soon or should I start using an alternative ?
Link to post
Share on other sites
Tehrasha Darkon
So far, so good. Updated both machines to v1.7.6 and have had a blissful error free 4hrs. :) Not a single crash or dead server event. Even the shared clipboard has been working correctly both ways. *fingers crossed* EDIT: Update 3 solid days without failure. Looks like whatever the issue was, is fixed.
Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...