Package: synergy
Version: 1.3.1-5
Followup-For: Bug #449255

On my 32bit installation of testing on a Core2Duo system, I regularly
get a crashing synergy as well. It can work for days and suddenly crash.
I can't find a trigger yet to easily reproduce it. I get this in my
dmesg:
[28463.755155] synergys[3689]: segfault at 820da44 ip b7deb9a2 sp bffd5544 
error 4 in libstdc++.so.6.0.10[b7d8e000+e3000]

I guess it's the same (or similar) problem.

Doesn't render it unusable, but it's definately very annoying.

HTH...

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages synergy depends on:
ii  libc6                         2.7-13     GNU C Library: Shared libraries
ii  libgcc1                       1:4.3.1-9  GCC support library
ii  libice6                       2:1.0.4-1  X11 Inter-Client Exchange library
ii  libsm6                        2:1.0.3-2  X11 Session Management library
ii  libstdc++6                    4.3.1-9    The GNU Standard C++ Library v3
ii  libx11-6                      2:1.1.4-2  X11 client-side library
ii  libxext6                      2:1.0.4-1  X11 miscellaneous extension librar
ii  libxinerama1                  2:1.0.3-2  X11 Xinerama extension library
ii  libxtst6                      2:1.0.3-1  X11 Testing -- Resource extension 

synergy recommends no packages.

synergy suggests no packages.

-- no debconf information

This message and attachment(s) are intended solely for use by the addressee and 
may contain information that is privileged, confidential or otherwise exempt 
from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution or copying of this communication is strictly 
prohibited.

If you have received this communication in error, please notify the sender 
immediately by telephone and with a 'reply' message.

Thank you for your co-operation.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to