Synergy QT GUI crashes for unknown error

[Kelly Price]

Using Gentoo with Synergy 1.7.1, and just recompiled it to make sure. The QT GUI isn't working: [code]tygris@sandra ~ $ qsynergy *** WARNING *** The program 'qsynergy' uses the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=qsynergy> *** WARNING *** The program 'qsynergy' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=qsynergy&f=DNSServiceRegister> terminate called after throwing an instance of 'std::runtime_error' what(): Code: 0 Error: Unknown Aborted [/code]

[Tim Meadowcroft]

I get the same crash at startup with qsynergy 1.7.1 on gentoo (32 bit, KDE 4.14.3, QT 4.8.5). Downgrading back to 1.7.0 works fine.. I see the same WARNING messages, but the last 4 lines ("terminate called..." - "Aborted") don't show. However I do get a very similar crash under 1.7.0 if I choose the Edit-Settings menu item (ie the Settings dialog doesn;t appear, it just crashes) [code]Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::runtime_error' what(): Code: 0 Error: Unknown Aborted [/code] The Wizard and About dialogs show fine, just the Settings fails to show. And if I look at how synergys is spawned under 1.7.0 [code]/usr/bin/synergys -f --no-tray --debug WARNING --name MyMachine -c /tmp/qt_temp.k23961 --address :24800 [/code] and run the 1.7.1 synergys binary directly with that command line, that runs fine (but no UI of course).. the "-c tmpfile" is the temporary config file presumably generated by qsynergy telling syndergys how to configure itself that hasn't been deleted when qsynergy crashes. So I'd suggest it's qsynergy that's a little buggy rather than synergys itself.