Synergy

Issue Tracker (powered by SPIT)

Bug #1553 - Client segfault when using kde4

Status:
Invalid
Priority:
Normal
Assignee:
None
Category:
None
Target:
None
Found:
None
Created by:
Created on:
5 Feb 2008 13:27
Updated by:
None
Updated on:
20 Sep 2010 22:21
Platform:
None
Google ID:
sf-188
Redmine ID:
1585

  • Related to: Bug #306 - Disconnect after copy & paste
  • Related to: Bug #1553 - Client segfault when using kde4
  • Related to: Bug #1690 - Segfault after a while

SourceForge user: alon_levy

I'm getting a segmentation fault in synergyc. It happens after I move the mouse into the client screen, after a brief movement. According to the DEBUG2 messages it appears to be connected to clipboard copying. I used gdb to find the offending function, but without a debug version (I'm using ubuntu packages without debug symbols) I can't provide further information (I would gladly if someone wants to solve this). Here is the debug info (only the last few lines I deem relevant) and the segfault itself:

DEBUG1: CXWindowsClipboard.cpp,118: request for clipboard 250, target TARGETS (252) by 0x01e00073 (property=QTSELECTION (256))
DEBUG1: CXWindowsClipboard.cpp,135: failed, not owned at time 1396594810
DEBUG1: CXWindowsClipboard.cpp,141: failed
DEBUG1: CXWindowsClipboard.cpp,1030: clipboard: sending failure to 0x01e00073,252,0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fc0949f06f0 (LWP 14477)]
0x00007fc09381d064 in std::Rbtree_increment () from /usr/lib/libstdc++.so.6
(gdb)

The server doesn't show anything interesting.


#1

20 Feb 2008 12:05: Issue Importer wrote a comment.

SourceForge user: skarsnik-nyo

Logged In: YES
user_id=2014549
Originator: NO

I can't reproduce this bugs with kde4 from svn (using qt4.4)
The server is on a winxp box and the client (compiled from svn) is on the kde4 box.
Can you provide more information ?


#2

20 Feb 2008 13:56: Issue Importer wrote a comment.

SourceForge user: alon_levy

Logged In: YES
user_id=1354837
Originator: YES

Hi,

I can't reproduce it with the newest kde4 from ubuntu packages, so I guess you should close it (or I could do that too I guess). For the record I can only give you the versions of the current kde4 installed and synergy installed (which doesn't produce the mentioned segmentation fault) -

alon@alfajor:~$ kwin --version
Qt: 4.3.3
KDE: 4.0.1 (KDE 4.0.1)
KWin: 3.0

alon@alfajor:~$ synergyc --version
synergyc 1.3.1, protocol version 1.3
Copyright (C) 2002 Chris Schoeneman


#3

31 May 2008 21:03: Issue Importer wrote a comment.

SourceForge user: bartw

Logged In: YES
user_id=210388
Originator: NO

I'm running openSUSE 11.0 rc1 with gnome. One one particular box, synergyc crashes. Sometimes it crashes immediately, and sometimes it works for a few seconds. If it works initially, I can cause it to crash just by moving the mouse from the server to the client and back a few times. I have two other systems with identical software, and they work. Perhaps it is unique to the video driver (radeonhd) of this particular box.

Here is a stack trace:
#0 0xb7d4d4e2 in std::Rbtreeincrement () from /usr/lib/libstdc++.so.6
#1 0x0805e7c9 in CXWindowsClipboard::pushReplies (this=0x80c7c48)
at /usr/include/c++/4.3/bits/stl
tree.h:182
#2 0x080614ff in CXWindowsClipboard::addRequest (this=0x80c7c48,
owner=75497476, requestor=25165993, target=335, time=61228977,
property=535) at CXWindowsClipboard.cpp:146
#3 0x08054cb4 in CXWindowsScreen::handleSystemEvent (this=0x80b0148,
event=@0xbf9719bc) at CXWindowsScreen.cpp:1218
#4 0x08057f01 in TMethodEventJob::run (this=0x80c8140,
event=@0xbf9719bc) at ../../lib/base/TMethodEventJob.h:66
#5 0x0807f84f in CEventQueue::dispatchEvent (this=0xbf9718d8,
event=@0xbf9719bc) at CEventQueue.cpp:190
#6 0x0804d751 in mainLoop () at synergyc.cpp:398
#7 0x0804db3d in main (argc=3, argv=0xbf971b74) at synergyc.cpp:467

This is possibly the same bug:
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/148968


20 Sep 2010 22:21: Nick Bolton changed Status.

New Invalid


#4

20 Sep 2010 22:21: Nick Bolton wrote a comment.

Closing this bug report since it is more than 2 years old. If this is still a valid bug, please request that it be reopened on the mailing list.