Leaderboard

  1. Nick Bolton

    Nick Bolton

    Synergy Team


    • Points

      124

    • Content count

      2377


  2. GranPaSmurf

    GranPaSmurf

    Volunteer Moderators


    • Points

      42

    • Content count

      780


  3. Kelvin Tran

    Kelvin Tran

    Volunteer Moderators


    • Points

      40

    • Content count

      600


  4. jml

    jml

    Volunteer Moderators


    • Points

      23

    • Content count

      225



Popular Content

Showing most liked content since 01/18/18 in all areas

  1. 14 points
    This has now moved to: Release Notes for Synergy 2
  2. 10 points
    Let me start with this: I've been using Synergy since day 1. Hell, I've been using it since before you developed it, as I'd developed my own almost 15 years ago and had been using it until Synergy was released. There have always been issues, but by and large, the convenience afforded by Synergy still outweighed the bugs. I've been using it since about a week after it's initial public release. That said, I feel like you guys are approaching the release of 2.x in... not a fantastic way... Synergy 1.x had it's issues and required configuration that scared off many users, but at the same time, it WORKED for those of us who used it. I dig the zero-conf in principle, but if it doesn't work, I'd much rather be stuck spending the 30 seconds to configure manually, than waiting months or years for someone to fix zero-conf. My development team (all horrible screen watchers) recently noticed, over my shoulder, that I was controlling multiple machines with one set of inputs, and sorta lost their collective minds (they're not Linux trolls... yet... so they're always blown away by the productivity enabled by Linux), so I purchased licenses for everyone. Of course 2.x worked so infrequently that they all quit using it, and now we're being told that we're in the minority (that's 25 workstations, completely homogeneous, nothing in common with each other) and that these small, but otherwise showstopping bugs won't be solved for 6-9 months? For what we paid for 2.x, I fully expect it to be at least useably stable, and/or expect that fixes be closer than nearly a year out. Same issues as everyone has been reporting. * Both Windows and Linux services seem to randomly stop working. Can see on my primary host that it simply stops sending packets to clients, or that clients simply stop responding. * Primary sharing machine hops around seemingly at random. The only time I ever touch my secondary clients is to restart Synergy. * No configuration options, no indication of what's going on in the background. Something else that hasn't really been well addressed: 1. Where is the documentation and changelogs? 2. How is 2.x communicating? 3. What is the host determination strategy? 4. What ports does it even require? Think about this from the I.T. Managers perspective. We have an application with no documentation which communicates over encrypted channels between (and unknown number of) clients. We have no idea how any of it works, but we know that it talks to the Internet, it does everything in the dark, and it randomly (every 10 minutes) stops working. No proper IT guy in his/her right mind would allow this on their clients machines, and if you think about your target demographic for a moment, you'll realise that of course there's a large chunk of it who reside in software development/high tech. Precisely where the IT folk are concerned about security. I strongly suspect that we're being told 6-9 months delivery for bug fixes because you're working on something else, but excuse my wording here, but that's bullshit. For what you're charging for 2.x these days, it is absolutely reasonable for us to expect the software to work, and to have documentation, in less than nearly a year. This whole thing feels like a $50/seat public beta for what is ultimately very nearly vaporware. Actually, "very nearly" is inaccurate as 100% of the features we've paid for, are still "coming soon", and even the basic functionality isn't working reliably yet. P.S. Tried to use contact form, but as many others have pointed out, it usually doesn't work. Didn't work for me. P.P.S. *sigh*. I just noticed that you have to approve all forum submissions.
  3. 9 points
    If you are posting about any of the following issues/concerns, please note that the response you will most likely get from the community is that these features are coming in Synergy 2.1. Without further ado... - Less reliant online mode - "Tinker-y" Settings panel - Removing and renaming a computer on the grid - A more polished uninstallation script - One-click updating process - Making the window size and elements dynamically adjustable - Tray icon for quick access to settings - Offline mode (YES!) - Better UI icons and labels - Better OS support (older versions of OS X (now named macOS), etc.) - More reliable cloud - Minor glitches and crashes (ex. with Chrome crashing on activation and Firefox not working in some instances) _________________________________________________________________________________________ The following changes will be exclusive to Synergy 2 Pro users. - Drag and drop file support - Copy and paste file support (ex. Ctrl + C a Word document and Ctrl + V on the other system) Note for this that you CAN copy and paste text and images on your clipboard. Just not entire files. - Synchronization of locked status and lock screens - Wake-on-LAN (magic packet, wake one system to wake all) - Screensaver Sync (similar to Lock Screen Sync) - Audio Sharing (share audio output between speakers of all systems) - Different computer profiles (ex. one profile for surrounding systems at work and another for the home) - Wrap around edges of computer layout - Key swapping - ex. mapping Ctrl to Cmd, etc. And as an added bonus, note that developer support (something similar to an API) will be added in Synergy 2.2 or 2.3! If what you want isn't on this list, go ahead and post it in the "Feature Ideas" forum and a Synergy team member will review your suggestion. EDIT: 2 things to note. | 1.) Please note that some of these feature suggestions have already been added in whole or in part to dot releases of Synergy 2! | 2.) Please note that as Synergy 2 is put back into beta, you will see a lot more of these features be added in a stable form before it is put back into deployment as the stable branch of Synergy.
  4. 9 points
    Why do you guys insist on making everything automatic when that's clearly a point of frustration for so many of us? I was eagerly waiting for this update since I bought Synergy 2 last December, only to realize that proxy authentication and configuration is not supported (something which I think you should mention somewhere in your page, seeing as how a lot of people rely on proxy functionality, instead of baiting unsuspecting buyers). When I contacted support about this they said the proxy support was going to be released in a few days, and they asked me if I could wait a bit instead of getting a refund. I took their advice since I genuinely thought the feature was coming. It's been more than 4 months and of course I can't get a refund now, for something which I literally haven't had a chance to even try out. Now I see that proxy support is finally released (at least for Windows).... but what is my surprise when I get the following error: [ Config ] [2018-04-26T15:08:46] debug: connected to background service [ Config ] [2018-04-26T15:08:46] debug: saying hello to background service [ Config ] [2018-04-26T15:08:48] warning: version check disabled, skipping [ Config ] [2018-04-26T15:08:48] error: Reply status code: 0 [ Config ] [2018-04-26T15:08:48] error: failed to check update: reply has error: Proxy requires authentication <<<<<---------------------------- [ Config ] [2018-04-26T15:08:48] error: Reply status code: 0 [ Config ] [2018-04-26T15:08:51] error: Reply status code: 0 And I can't even touch the configuration because you insist on making everything automatic! (even if said automation doesn't work whatsoever). More and more it starts to look as if I just threw 40 dollars down the drain. I've been trying really hard to support you and be patient as I have a few friends that recommended you and I believe that as developers we should be more supportive of each other, as opposed to some big company. But this is getting ridiculous. Why is it that you keep on insisting on crippling your power users and prevent them from actually taking advantage of your really cool (apparently) software you created? Is there any meaningful timeline that I can expect so that I can finally enjoy my purchase? or will this be one of those features that will never get implemented and I'll be left here hanging with my useless purchase? Do you guys actually care about this or not? Because so far it seems as if this is a really low priority item since you keep coming with excuses and non-working solutions instead of actually addressing the issue we care most about: being able to configure the proxy settings, which shouldn't be something terribly difficult if you just stopped trying to make everything so "seamless" and instead focus on actually making it work and THEN making it seamless. As a last hail mary... is there a way I could still get a refund for this? I'm really frustrated by now and would like to put this behind. Ideally by being able to use my Synergy 2 Pro, but if not, then at least getting my money back so I can go buy something that does work. Thanks
  5. 7 points
    The lack of being able to tweak settings or even get into any semblance of a settings page/window like version 1 had does seem to be a step backwards. I was a happy user of Synergy 1 Pro which allowed me to tweak certain settings and configuration knobs but since version 2 it seems like you have decide that Pro is no longer an option and are treating all your users as simpletons. Who is it great for that everything is managed be the "Synergy Cloud"? Certainly not the end user since we have no access to said cloud.
  6. 7 points
    One other thing I forgot to mention. A big sell for 2.x was it's ability to figure itself out over complex networks. Guess what the administrators of complex networks don't want. Rogue applications sending probes all over the place and/or sending streaming data over a 4G connected VPN when a perfectly good ethernet is connected. I haven't been able to determine 2.x's routing strategy yet, but I've found that it consistently chooses precisely the least optimal route. IE: Every single time I connect my machines (at home) to my VPN to my clients office, both machines seem to immediately communicate with each other over the VPN at least 50% of the time. They are physically no more than 5 feet of ethernet cable away from each other, and the default route for both machines is via the local gateway (which shouldn't matter as they are on the same physical switch anyway). Despite this, 2.x will, in the middle of a session, start streaming itself through the VPN, which of course introduces an additional 200ms latency and it becomes unusable. The only way I've found to prevent this, is to use DPI to find Synergy traffic and block it before it can "discover" VPN connected hosts. This solution also solves the problem where my mobile laptop which of course comes with me to the office, comes home but now every single machine in the office now wants to be a part of my Synergy group, so I'll be mousing around here at home, and then all of a sudden I completely lose my mouse, and lose my mind for about 10 minutes until my receptionist at the office phones me to report Russians are on one of my machines at the office, because she can see my cursor flying around, 1000 miles away. Seriously guys. Zero-Conf is only good in principle, if it works absolutely flawlessly. Give us both documentation and at least basic control over what constitutes a "location".
  7. 6 points
    The current Synergy 1.9 package for Ubuntu (synergy_1.9.1.stable~b327+2a0225c1_amd64.deb) unfortunately depends on libcurl3. Many other packages in Ubuntu (the most important of which, to me at least, are the curl binary itself and cmake) depend on libcurl4. libcurl4 conflicts with libcurl3 and cannot be installed simultaneously, which means I have to uninstall synergy and libcurl3. I'm pretty sure other developers will encounter the same problem. Can we get a re-spin of the package that depends on libcurl4 instead of libcurl3?
  8. 6 points
  9. 6 points
    Synergy 2: How to uninstall and reinstall
  10. 4 points
    Recently we surveyed a group of our users with a simple question: Should Synergy 2 be considered stable or beta? In November of last year, we officially released Synergy 2 as stable. We knew there were a few minor bugs but assumed we could fix them within a couple of months. Sadly, it became apparent that these bugs were not so small nor easy to fix. So with very careful consideration, we've made the decision to redeclare Synergy 2 a beta product. When will Synergy 2 be stable? We're going to leave this up to you to decide. As we make updates and enhancements, we'll continue to poll users so that you can tell us when you think it's stable. We've also decided not to ask this question until after we've re-introduced the missing features from Synergy 1, which could extend the beta period by 12-18 months. Reply to this thread if you have any questions about this decision. Update: Update 2: @Kelvin Tran also posted bout Synergy 1.
  11. 4 points
    Hi guys and gals. On OSX, is there a reason/solution that when one of my machines wakes from sleep, Synergy cannot reconnect? I need to either kill the process or remove and add the client screen! Very tedious. Worst part is I can't do otherwise than put it to sleep (MBP so I just close the lid) because Synergy prevents the laptop from activating Screensaver! So, can I do anything about this? If there is no solution I will be going back to version 1 as this is beyond annoying: it's time wasting. Thanks
  12. 4 points
    Just got this working on my end. It looks like the key is removing Synergy from "Security & Privacy > Privacy > Accessibility" before reinstalling.
  13. 4 points
    Concur. They’ve released a feature incomplete “alpha” version that doesn’t work a good chunk of the time, and above that, they have focused on features that their customers aren’t asking for (like zero comfig). Trying to say proxy support doesn’t need any comfiguration is ludicrous. Proxy setup often needs a myraid of configuration, like servernames, ports, authentication, etc. seems someone had an idea one day “Hey, let’s make it zero config” and since then it’s been damn the torpedos, full speed ahead!
  14. 4 points
    As of version 2.0.10 (on Mac) I've got nothing. It had been working irregularly. When it would quit, I would bang around blindly in the UI, and usually it would come back. This time - nothing. Often just dragging the screens apart and letting them re-connect would get it going again. But not this time. I can understand the desire to keep things like proxy settings and configuration hidden, but there is an "interface" to this thing which is completely undocumented. If you're already familiar with the old product, you probably understand that the two boxes allow you to control screen placement. If you're not, then god help you, because they are not going to explain it. But aside from that: what does the little white dot mean on the bottom of one of the screens? Why does it change sometimes when I click on it - and sometimes changes by itself? What does it mean when there is a progress bar on one of the screens? What does it mean when the screen is green vs. grey? These things are not "automatic." The user must interact with this screen to configure the software. You're clearly trying to convey some information to the user. But it's not explained anywhere. Trying to use the product is like trying to solve the riddle of a mysterious artifact left by an ancient civilization. But we don't feel anger at the ancient Babylonians, because they're dead, and we imagine they might have explained their artifact, if they could. And we didn't pay them for the artifact. But you're not dead, and we've paid you a little something. So you must understand why people are upset as years roll by and there is no communication beyond "it's supposed to be automatic." Neither on the things that are supposed to be automatic, nor on things that are clearly not automatic. I can understand that software is hard, because I do that every day. But surely, over the course of a couple of years, you can put together 20 sentences that explain what this UI does, and what the symbols on it mean?
  15. 4 points
    Whoah. That new UI! What does it do? How does it work? Who knows? Despite some frustration with things being borked and needing uninstalls/registry cleanups/cloud logins, etc (the link below is an essential reference) I did manage to get everything working. I even managed to get a connection from my weirdly networked machine that I didn't figure I'd be able to get working until there was a manual settings file. The new UX is unsettling. The windows tray / mac menubar helper doesn't have any way of showing what's going on...you have to open a different app. The Synergy App looks fine when things are working but provides no affordances for figuring out what you are supposed to try next if it's jammed. There are definitely some feature regressions (yep. already on the roadmap.). The Beta process was also long and frustrating. I'm actually back to Synergy after 6 months happy (but struggling) with a different software keyboard-mouse sharing 'ware. It was way better than the last beta I tried, and had some neat features I wouldn't mind seeing in Synergy. All of that said. Synergy 2 is BRILLIANT! WONDERFUL! Thank you so much! 1) This type of software is *so vital* to my happiness during the day. I need it so much! I know how all of the frustrate people in this forum feel, since it is probably just as vital to them. I also see how incredibly difficult just keeping keyboard/mouse sharing has become over the last decade. Remotely pwning the console is something 2018 operating systems resist very actively. You deserve more than I've paid you just for keeping the software live through so many breaking OS changes. Thank you! 2) When I figured out the trick to switch which computer was the controller, and popped my master keyboard/mouse from host to host, I was just FLOORED. Not only can my mouse swing from screen to screen and control every computer at my battlestation, but I can switch to a different machine and control all the others from there? SO HAPPY! Thank you! Somehow it feels like getting thousands of dollars of extra computer power..but for $15. This is such an impressive achievement, and fits so nicely in the control of my screen layouts. (Being able to control this switch from the tray icon, and having a command-line way of affecting control <something I can control with AutoHotKey or Keyboard Maestro?> would be very nice too?) 3) I've just spent 2 months at work with a team of 10, delivering the very smallest piece of software I can imagine. I know the whole forum is on you to hurry up with <insert pet feature>, and I can't wait either, but all software takes time, and few of us have any clue how much you folks are doing and with how few resources. Thank you! For reference, one of my other utilities that does a little tiny (technically hard) task that I have trouble living without was developed, dropped, passed to a new company, abandoned, open sourced, abandoned, redeveloped from scratch, and now is available in 2 forms: 1) old, broken, unsupported on an up-to-date OS and 2) $100. Did I mention software is hard and takes time (and money)? You guys are doing great work and at such a reasonable cost. Please keep going, because I'd ache if we lost maintenance on Synergy. Thank you! So, yeah. It was a bit of a challenge getting up to date with 2 and getting it running. I've got all sorts of peanut-gallery suggestions and demands. Sure, I'm not 100% happy and there are things I miss about the older versions. But mostly: WOW! This is great! It's an ambitious, real effort to take an essential utility and modernize it (operating systems, networks, and usage has changed a little bit since 1996, hasn't it?). I see a lot of complaints around here, so I wanted to spend a few minutes and thank you for the huge good you've accomplished. -Josh
  16. 4 points
    We plan on adding support in 2.1 which is due in about 6 months.
  17. 4 points
    This feature will be available shortly.
  18. 4 points
    Hi, I'm on Arch linux but I made mine work by killing the service (not sure about ubuntu but on arch is systemctl stop synergy, then systemctl disable synergy So it does not autostart) Then start the binary synergy-service *with sudo synergy-service. Here my thread where I solve my problem
  19. 4 points
    Had exactly the same problem on all clients, so I did powercfg /REQUESTSOVERRIDE process synergy-core.exe display system from elevated command prompt on every client machine and it took care of it.
  20. 3 points
    Hello, I was just wondering if y'all have any plans to add Android compatibility to Synergy? I have an android tablet, and also now with the introduction of Samsung DeX would like to use that with my phone as well. If you created an Android app and charged for the app individually, I'm sure you'd get a lot of hits.
  21. 3 points
    I think the "failed to create quartz event tap" is linked to privacy permissioning issues. I had this (both machines running Mac OSX Mojave) and fixed by going to System Preferences -> Security & Privacy -> Privacy and unchecking and then rechecking the box allowing Synergy to control the computer. The second I did that the connection worked and Synergy is now ticking along nicely. Good luck!
  22. 3 points
    Full disclosure guys! I had to let some people go. For the next 6 months, I'm mucking in and doing some hands-on work with Sarah. In 2019 I'll be hiring a whole new team of Software Engineers, but until then it's just us two. Read all about it: https://symless.com/blog/open-letter-synergy-team Comments welcome...
  23. 3 points
    Had the exact same issue. Sam54123 and Johnmc's suggestion worked. Here are a few images to walk you through that process should you encounter the same problem:
  24. 3 points
    I couldn't find any information at https://symless.com/synergy/release-notes which is where I always go when I see a new release. If there isn't already some information about the new release beta (v2.0.12 b), I assume it is coming soon. In case information has been released, however, could someone please link to it? I'd gladly help and test the beta, but knowing roughly what changes have been made first would be nice.
  25. 3 points
    Dude, for starters, it ain't "my" product. Secondly, just saying it doesn't work makes no sense since it does work for lots of people. If you have a particular problem, somebody could probably help you, but just complaining it doesn't work will get you nowhere.
  26. 3 points
    I just wanted to confirm, that I was having the exact same issue between two machines running Windows 10 April update 1803. Upon reading this forum post, I tested a few different scaling configurations. I found that so long as the server display that connects to the client display is scaled to 100% then it works. In the attached photo the 4K displays are connected to the server, the 3K display is a laptop acting as a client. So long as the server display with the * is set to 100% scaling, then Synergy works normally, however if it is anything more than 100% then the mouse switches to the client, the mouse cursor disappears, and it will not switch back to server while synergy services are running. Interestingly the displays without the asterisks can be set to any scaling without issue. I was running 2.0.10 before the April windows 10 update, with the 4K displays scaled to 150% and the 3K display set to 175%, I have used most of the synergy 2.0.X versions without any issue like this. The April 1803 update definitely seems to be the culprit.
  27. 3 points
    Still testing this solution (still using 1.9.1), but here's what I did to reconcile Synergy with libcurl4 on Ubuntu 18.04: Downloaded the appropriate Synergy package. Unarchived the package, then unarchived the resulting control.tar.gz, all so I can edit the control file: $ ar x synergy_1.9.1.stable_b327+2a0225c1_amd64.deb $ tar zxvf control.tar.gz $ vim control Modify the control file, removing libcurl3 with libcurl4 (>= 7.58.0) Package: synergy Version: 1.9.1.stable~b327+2a0225c1 Architecture: amd64 Maintainer: Symless <[email protected]> Installed-Size: 2591 Depends: libavahi-compat-libdnssd1 (>= 0.6.16), libc6 (>= 2.14), libcurl4 (>= 7.58.0), libgcc1 (>= 1:3.0), libqt5core5a Section: utils Priority: optional Homepage: https://symless.com/synergy Description: Keyboard and mouse sharing solution Synergy allows you to share one mouse and keyboard between multiple computers. Work seamlessly across Windows, macOS and Linux. Rolled everything back up into a new package. Note, the order of contents are specified when archiving the new deb matters. $ tar c md5sums control | gzip -c > control.tar.gz $ ar rcs synergy_1.9.1.modified.deb debian-binary control.tar.gz data.tar.xz $ sudo apt install ./synergy_1.9.1.modified.deb
  28. 3 points
    I'd like to second this, not having read down to the bottom of the thread yet... I purchased v2 at 2.0.8, which did not work between my 2 macs v10.13.3(share-server) & v.10.11.3(client). I filed a support ticket which didn't really help until v2.0.9 came out... and nothing worked. I completely uninstalled and lo and behold, v 1.9 worked fine(relatively) and I could see the logs and manage things. v.2.0.10 came out and it worked for a day! then I undocked my MBP which I share my keyboard/mouse from. I get the spinning beachball when I hover the mouse/trackpad pointer over the menubar icon, so don't know how to fix this.... I've been a happy customer for years, but I'm very upset that v.2 just doesn't work consistently.
  29. 3 points
    Just a simple one, currently left clicking the new tray icon in Windows does nothing, its just right click to disable/enable Synergy. Why not make double clicking the icon open the main Synergy config Window?
  30. 3 points
    some one should take back the strings and put synergy 1.9.x back on github to be maintained by the community... just sayin ;D
  31. 3 points
    Unfortunately, close but no cigar. I´ve tried several times since ver. 2.0 was launched and my two Mac computers, both on the same wired network, same configuration, seeing each other with ping, working flawlessly with Synergy 1.9.1, refuse to connect. I´ve installed the "server" and it remains stuck at the "second step: install synergy on another computer". I do so, but the other computer just shows a dark screen icon and nothing happens. And to add insult to injury, the "minimalist" design does not allow you to see what´s going on, aside of the sending logs feature. For the time being, I will stick with the old version...
  32. 3 points
    Even though some features are not available yet, I've found that since the launch of Synergy 2 that the Symless team has continuously worked to improve on its reliability and efficacy. My personal philosophy is that this is a small company trying to make, what I consider, a big difference and every bit of support towards them contributes to the development of those features that we're awaiting on.
  33. 3 points
    Hi All Just ran into this exact same problem under the new Bionic Bever Beta 18.04. (Running KDE as well.) I struggled for a little while as Firefox was the default application that the sign in web page was appearing in. What I discovered is that I had to go into default applications and manually set me web browser to be firefox. It was grayed out with the default option of letting the type of URL define the application. Once I switched to manually setting everything to open in firefox it was all good!!. Hopefully someone is writing instructions on how to install in the different environments
  34. 3 points
    Far too often we gripe about what is wrong and don't speak up when something good happens. Today... For the first time in a few releases... My systems connected up and worked after I had them off network and separated. The server was open and had not been used off network but had been disconnected and the client was locked but had been used off network, but I connected them both up to my LAN via ethernet and did not have to play service jockey at all. HUGE win for me. And no. I am not being snide in any way. THANK YOU!
  35. 3 points
    Scroll Lock seems to look the mouse and keyboard to the current computer its on. That solves the problem for me.
  36. 3 points
    Good news, Synergy 2.0.5 is here. https://symless.com/synergy/downloads New in v2.0.5 Remove computer from config (provides workaround for many issues) Screen status is now working much better (we're still working on making it perfect) Fixed bug where the auto-config error was always showing first on install Fixed a timing issue in the reconnect code to make it more responsive Some prep work for the connection troubleshoot tooltips (coming soon) Here are the full release notes...
  37. 3 points
    I don't know if this falls under the coming features ("Tinker-y" Settings panel) or (Making the window size and elements dynamically adjustable) but I'd really like to see better position control for multi-monitor setups. I have two adjacent monitors to my main screen, but my right one is in portrait mode. So it is taller than the other two. My second computer screen is above my 1st computer's primary display. But I can't drag my mouse directly to it. I have to go to the taller screen to the right since it has the highest point of my setup. However, I'm able to move my cursor down to my main display like normal. This was confirmed when I leveled the right portrait screen with my main screen in Window's Display Settings, and I was able to move the cursor back and forth like normal. I'd like to see an interface like windows display settings, but for synergy where the screens just like like an extra monitor and can be moved around.
  38. 3 points
    I'm sorta on the same page as @MWP13 here, though trying to be a little more diplomatic. I paid for 1.x for the same reasons. I wanted to see Synergy succeed. I paid for 2.x for the same reason, despite years of dealing with multiple bugs (many were rather obnoxious bugs, like the constant client hangups on the Linux side). I still want to see it succeed. But we're certainly well past the "hopes and dreams" stage. My experience with support since day one, has been that bugs don't typically get fixed, or if they do, there's no communication to that affect. I'm still waiting for my first bug report (this was probably from pre 1.x) to be addressed (I think it had to do with Linux client constantly disconnecting). I was told that the fix would be out in 3-6 months then as well, but it never was resolved. I get that at some point you have to just start over with a complete refactor and focus everything on that new release, but 2.x feels ... I want to say beta, but honestly it feels more pre-alpha with the complete lack of feedback from the UI, to the issues with zeroconf. That said, Nick and the team have always been pretty responsive about offering refunds. That's cool and all, but given there really aren't any other alternatives out there, I just want to see Synergy work, and from the looks of 2.x, all of the big issues are with regards to the zeroconf failing to zeroconf. I hate to invoke the argument from authority here, but I manage a fairly large development team, as well as am in charge of product development for a relatively large company. My response to the current issues with 2.x, would be to focus on the core functionality (the sharing of keyboard/mouse) before anything else. I've made recommendations before, and they've gone unanswered, but here's what I'd like to see, not in 6 months to never, but in the next few weeks as it really should be top priority (because you don't make sales on bad reviews, no matter how robust your marketing wank): 1. Start by giving us the ability to bypass the zeroconf entirely. I say this for a number of reasons. Zeroconf doesn't currently work reliably in any environment I've tested in, and sounds like I'm not alone. Even if it did, there is zero indication to the user (or the IT manager) how it's communicating with other clients. This is a massive security faux-pas and the only reason I allow it on my network is because I've got a long relationship with the software and I generally trust the developers aren't sneaky Russians after my butt-coinz. But no matter what, zeroconf has to work 100% perfectly every time, or it should not be the only method of configuration. And it should always come with technical documentation describing it's operation. There are too many possible network configurations to account for. 2.x is currently deciding that the lowest cost path between my two machines which are directly connected to each other, is through a VPN with 120ms latency. I had to perform logical host isolation on all clients to convince 2.x to stop doing this. This is nuts. I've had to firewall clients from each other, so I can run a simple application. 2. F**k it. I honestly don't care about anything else personally. 2.x seems to work great with the exception of it not working at all most of the time due to the broken zeroconf. Feature requests! Ability to disable zeroconf and manually configure connections. Task tray icon for Synergy client, with some visual indication of connected clients. That is all. Actually forget about 2. I don't care enough about it. My feature request is that zeroconf go away until it is stable, and even then have the option to disable it. @Nick Bolton, my guess is he's referring to major bugs being scheduled for a fix in "6-8 months". I've been using Synergy since the beginning, and while I'm sure this isn't true for everyone, I haven't seen a single bug I've encountered, be addressed and resolved. The default response to me has been that I can have a refund. TL;DR.
  39. 3 points
    Thanks for the perspective Steve. Issues and problems are reported and accumulate here. It doesn't mean EVERY Synergy user has the same issues. If a doctor sees patients all day that all, 100%, have the flu, that doesn't mean that the whole population, 100%, have the flu. If you skim the forum, you will see a bunch of users with problems. That's OK, they're supposed to be here. Another quick skim will turn up a lot of "thanks, that worked" messages. As always, the support team should have a support ticket for every issue raised here on the forum, even if we are able to suggest a quick fix, Support tickets help drive the direction of development. https://symless.com/contact/customer-support
  40. 3 points
    I want to open this by stating that I have no interest in pursuing legal action, and I would hope that you all feel the same. Symless has offered refunds and I'm sure they are just as upset with our dissatisfaction as we are ourselves. They have shown over time that they have nothing but good intentions. I'm including this preface because the tone of what's written below may suggest otherwise, and other users have used the word "fraud". I do not feel like Symless owes me anything other than an acknowledgement of the situation, and a public apology for the customers who feel like they have been slighted by this release. I look forward to the release of 2.1, and I plan on switching to it once available. I've been using Synergy for a long time, and the company has shown great faith with their continued support and development; although I am unhappy with this release, I ultimately am a happy customer. On to the substance: Synergy 2.0 is not feature-complete, nor is it stable. They did not market 2.0 as being feature complete, and I see now that I purchased my upgrade to Synergy 2 AFTER they had listed the upcoming features for 2.1 (source), so I only have myself to blame for purchasing the upgrade and expecting some of the features which are listed at that link. However, 2.0 was marketed as being stable, and we all see that it is anything but stable on Unix-like systems, to the point where it is almost unusable. If you need to spend 5 minutes fiddling every time you switch clients/servers, you are losing some of the productivity gained by using Synergy. It seems as if 2.0 was released as stable in an attempt to bring in revenue to keep Symless running. I have no source to warrant such a claim, so please do not believe that this is the case until we have received a response from the team. If this is the case, I would have strongly preferred transparency on this matter. Perhaps they should have continued the early access project and continued selling access to that, rather than selling the current 2.0 as stable. Others have noted that they feel as if fraud had been committed, because they were under the impression that this was a stable release. Of course, not all bugs can be found without releasing it to a larger userbase, so some bugs on a stable release are acceptable and expected. However, it seems that Symless released 2.0 knowing that a subset of beta testers believed this to not be ready for release. This can be seen by looking at the first few pages of the early access forum and it is even confirmed by the team in their message to the beta testers upon 2.0's release: It seems clear from this quote that they intend on widening their audience by prioritizing user-friendly features (which I think is a great idea for the company itself and for improvement of the product). If that is the case, then releasing 2.0 with that feature-set is understandable, as it targets the majority of their intended audience. I just wish I knew this information prior to upgrading my license. I felt very slighted when I found the above quote after realizing my dissatisfaction with the product I had purchased. This quote should have been included in all of the promotional emails for the release. I don't want a refund; I fully intend on using 2.1 upon release, and I would like my upgrade purchase to contribute toward bringing that release to realization. All I want is for Symless to acknowledge this situation on their site and in the forums. They owe such transparency to the current and potential customers. Nick and Co: I hope I am not being too disrespectful with this post; my intention with this is to bring light to the situation and get everyone on the same page. The self-support forum is filled with threads which could have been answered by the above information, and I think an official post on the situation would resolve much of the dissatisfaction.
  41. 3 points
    Symless support said the fix is in the next release. If you bought the product, open a support case so they can track the population with the error.
  42. 2 points
    Hey all, I just got synergy a couple of months ago and it has been working out great so far. I only have one minor nit pick and am not sure how many feel the same way. Problem: I have a Desktop and a MacBook and have Synergy 1.0 installed on both of them. Due to the nature of my set up, I would love to be able to use my Macbook's Keyboard while using my Desktop's Mouse. This is currently not possible due to Synergy defining a whole system being a Master, while the other being a Slave. Request: I would love to be able to separately definitely which system will have the Master Keyboard and which will have the Master Mouse. If any dev sees this, I would love to know how complex a change like this is and whether it should be something that is doable or impossible due to some fundamental limitation.
  43. 2 points
    I had a similar issue with a single Win 10 computer and a Macbook. The Macbook showed green after installing and launching, but the Windows computer was grey. There were some errors in the console (launch by pressing "~"). I tried multiple uninstall/reinstalls with no success. What worked for me was uninstalling and then deleting the registry entries on my Windows machine: Uninstall Synergy Press windows key and search "run", type "regedit" to launch Look for HKEY_CURRENT_USER > Software > Symless (or Synergy) and right click to delete. I think these were from previous versions that caused an issue. Reinstall Synergy and relaunch After reinstalling 2.0.1 it automatically connected with my Mac and showed both as green. Now to figure out how to map the windows key on my Macbook..
  44. 2 points
    I couldn't agree more! Every time I see there is a new v2 release I try it and every time it ends with disappointment. Last one was yesterday, I made a clean install (as described in this very forums and yes I even rebooted my computers) of v2.09 and even though this time I managed to see my computers on Synergy main screen (and that's all you can do there, just look at it) mouse or keyboard didn't work. Installed v1 back immediately. I think paying for v2 was one of my most disappointing purchases ever. And yes, it says it's "stable". Like a joke.
  45. 2 points
    Hi just wanted to say I have been pretty unhappy with version 2 over 1 in general but the last few updates have made massive improvements in stability and reliability for me....keep doing what you are doing, you are winning me back!
  46. 2 points
    Don't read too much into this... I think I'm in love with this post.
  47. 2 points
    We'll keep them as a sticky on the forum. Eventually, we plan on having a page on the website too.
  48. 2 points
    What will happen if my internet is down?
  49. 2 points
    Dear Synergy community, even if I'm a very satisfied Synergy User for many, many years (must be >5 years), I have never posted something in the forum. However, today I thought it is time to write this post about an issue with the French grave accent (è). On my Server computer I can easily create this character by pressing Shift + "´"-key followed by the "e"-key. However, this doesn't work on my client PC. No character will be put on the screen, when I press this combination. The "e" with the accent in the other direction (é; acute accent) works perfect on the Server and Client, but not the accent grave. Is this a known issue and how can it be fixed? My Computer configuration is the following: Server: Windows 10 Home 64 Bit Client: Windows 7 Professional, 64 Bit Keyboard: German keyboard Synergy Version: 1.8.6-stable Many thanks for your support and best regards Markus
  50. 2 points
    It takes a little work, but it is possible to use Synergy over VPN without split-tunneling. Here is what I did. 1) Register yourself a free (or paid if you don't want 30-day nags) dynamic DNS address (DDNS) from a place like dynDNS or no-ip 2) Register for the Pro version of Synergy to get that sweet, sweet SSL security. You're going to be opening some pin holes, so best to keep the connection secure while in transit 3) Select a non-default port for Synergy to use - again security precaution From you home network router: 4) Create a DHCP reservation or assign a static IP for your server system 5) Create a port forwarding rule on the router that will forward all traffic destined for the port you determined in step 3 to the IP to determined in step 4 (source should be any IP, any port) From Server system 6) Install Synergy if you haven't already done so, select server, and register your Pro key from step 2 7) On the Settings menu, enter the port number to determined in step 3, check the "Use SSL Security" box and click OK 8) Click Configure Server and then add your client screens as you normally would From home router or server system 9a) If router supports automatic dynamic DNS updates, configure your router to update the address you registered in step 1 so your home external IP is tied to your DDNS address -or- 9b) Install the DNS update client from the service used in step 1 so your home external IP is tied to your DDNS address From your client system(s) 10) Install Synergy and select Client 11) For "Server IP," enter the DDNS address you created in step 1 (don't use auto config) 12) Make sure to set the same port number from step 3 in the Settings screen 13) Watch the magic happen I think that about covers it...