Xtightvnc crashes randomly with SIGSEGV (in WaitForSomething())

[Joachim Breitsprecher]

I start tightvncserver with the command line:

tightvncserver -nolisten tcp -geometry 1680x1050 -depth 16 :1

This works OK, but randomly, tightvncserver would crash, taking the whole X session with it. I noticed this seems to happen only when there is rather a lot of graphical activity (browsing web pages, searching in synaptic etc.)

ProblemType: Crash
Architecture: amd64
Date: Wed Nov 25 15:08:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xtightvnc
NonfreeKernelModules: fglrx
Package: tightvncserver 1.3.9-4
ProcCmdline:

ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SegvAnalysis:
 Segfault happened at: 0x44e6b6 <WaitForSomething+1574>: mov %edx,(%rsi,%rax,4)
 PC (0x0044e6b6) ok
 source "%edx" ok
 destination "(%rsi,%rax,4)" (0x7fff20c2d000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: tightvnc
StacktraceTop:
 WaitForSomething ()
 Dispatch ()
 ?? ()
Title: Xtightvnc crashed with SIGSEGV in WaitForSomething()
Uname: Linux 2.6.31-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:WaitForSomething ()
Dispatch ()
?? ()

[Russ Miranda (n-launchpad-samlhake-sneakemail-com)]

The tightvnc X server in tightvnc-1.3.9 has some problems with how it handles 64-bit integers that are likely to lead to SEGV. Patch http://sourceforge.net/tracker/?func=detail&aid=2570977&group_id=14067&atid=314067 is incorporated into tightvnc-1.3.10. I would recommend moving up to 1.3.10, alternatively the patch could probably be applied to 1.3.9 relatively easily.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.