synergyc crashes when opening a new gnome-terminal tab

Bug #88906 reported by Jonathan Sambrook
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: synergy

I get the following output running with the -f option (the first instance shows the crash before the server is connected, the second instance after):

$ synergyc -f servername
INFO: synergyc.cpp,716: Synergy client 1.3.1 on Linux 2.6.20-rc7 #1 PREEMPT Wed Jan 31 15:59:40 GMT 2007 i686
DEBUG: CXWindowsScreen.cpp,840: XOpenDisplay(":0.0")
DEBUG: CXWindowsScreenSaver.cpp,339: xscreensaver window: 0x00000000
DEBUG: CXWindowsScreen.cpp,110: screen shape: 0,0 1920x1200
DEBUG: CXWindowsScreen.cpp,111: window is 0x04200004
DEBUG: CScreen.cpp,38: opened display
NOTE: synergyc.cpp,330: started client
synergyc: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
Aborted

$ synergyc -f servername
INFO: synergyc.cpp,716: Synergy client 1.3.1 on Linux 2.6.20-rc7 #1 PREEMPT Wed Jan 31 15:59:40 GMT 2007 i686
DEBUG: CXWindowsScreen.cpp,840: XOpenDisplay(":0.0")
DEBUG: CXWindowsScreenSaver.cpp,339: xscreensaver window: 0x00000000
DEBUG: CXWindowsScreen.cpp,110: screen shape: 0,0 1920x1200
DEBUG: CXWindowsScreen.cpp,111: window is 0x04200004
DEBUG: CScreen.cpp,38: opened display
NOTE: synergyc.cpp,330: started client
DEBUG: CXWindowsClipboard.cpp,313: open clipboard 0
DEBUG: CXWindowsClipboard.cpp,266: empty clipboard 0
DEBUG: CXWindowsClipboard.cpp,289: grabbed clipboard 0
DEBUG: CXWindowsClipboard.cpp,348: close clipboard 0
DEBUG: CXWindowsClipboard.cpp,313: open clipboard 1
DEBUG: CXWindowsClipboard.cpp,266: empty clipboard 1
DEBUG: CXWindowsClipboard.cpp,289: grabbed clipboard 1
DEBUG: CXWindowsClipboard.cpp,348: close clipboard 1
NOTE: synergyc.cpp,247: connected to server
synergyc: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
Aborted

Problem occurs under different WMs (Beryl and Metacity). All packages up-to-date with Feisty repo. Anything else I can tell you?

description: updated
Revision history for this message
Jamey Sharp (sharpone) wrote :

Can you supply a backtrace for this problem?

Revision history for this message
Christer Edwards (christer.edwards) wrote :

I have had trouble with synergyc / synergys crashing when not mapped correctly. Have you tried setting your .synergy.conf mapped to IP addresses vs hostnames or visa versa? this has solved synergy problems for me in the past.

Please let us know the outcome of further testing.

Revision history for this message
kenden (kenden) wrote :

I cannot reproduce this on Hardy beta, with compiz on or off.
Do you still have the problem (you mentioned you were on Feisty. Have you tried on Gutsy/Hardy)?
Can you supply a backtrace for this issue?

Changed in synergy:
status: New → Incomplete
Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in synergy:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.