Ubuntu
tightvnc package

Xtightvnc crashed with SIGSEGV in WaitForSomething()

Bug #476845 reported by hesh
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
tightvnc (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

tightvnc crashed a lot under 9.04 when starting firefox, and I believe it depended on the content of the pages visited;
it was irritating and avoidable -- I no longer browse while using tightvnc.

Now in 9.10 I am also getting crashes just by editing files using vi, under an xterm. This is too common a task to avoid.

ProblemType: Crash
Architecture: amd64
Date: Fri Nov 6 11:31:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xtightvnc
Package: tightvncserver 1.3.9-4
ProcCmdline:

ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x44e6b6 <WaitForSomething+1574>: mov %edx,(%rsi,%rax,4)
 PC (0x0044e6b6) ok
 source "%edx" ok
 destination "(%rsi,%rax,4)" (0x7fff624b0000) 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-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
hesh (hesh-pobox) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in tightvnc (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
visibility: private → public
Revision history for this message
Russ Miranda (n-launchpad-samlhake-sneakemail-com) wrote :

I submitted a patch to the author of tightvnc over a year ago, which was incorporated into tightvnc 1.3.10. This patch corrected a number of problems with how 64-bit values were handled. I'm very surprised Ubuntu is still on 1.3.9 after a full year.

Revision history for this message
Russ Miranda (n-launchpad-samlhake-sneakemail-com) wrote :

The patch for 1.3.9 source is posted on the source forge page here: http://sourceforge.net/tracker/?func=detail&aid=2570977&group_id=14067&atid=314067

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in tightvnc (Ubuntu):
status: New → Confirmed
Revision history for this message
Gorka Navarrete (emrys) wrote :

I am having problems in Ubuntu Server 12.04. When opening more than one matlab instance, the VNC server dies and it is not recoverable. The problem seems related to this bug report.

It's been >4 years with a known problem with 1.3.9 and both a patch for the problem and a newer working version (1.3.10).

Who is in charge of maintaining the tightvnc package? This should, at least, be upgraded for 14.04!

I attach the previously mentioned patch here.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "vnc_unixsrc.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Gorka Navarrete (emrys) wrote :

There is a formal request to upgrade this package since 2011 in bug: https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/831556

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

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