tightvncserver crashes with SIGSEGV when opening multiple windows at the same time

Bug #1014880 reported by George Bobeck
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tightvnc (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

source package

1.
Description: Ubuntu 10.04.4 LTS
Release: 10.04

2.
tightvncserver 1.3.9-6

tightvncserver crashes with SIGSEGV when opeing multiple windows.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: tightvncserver 1.3.9-6
ProcVersionSignature: Ubuntu 2.6.32-38.83-server 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-server x86_64
Architecture: amd64
Date: Mon Jun 18 17:15:27 2012
InstallationMedia: Ubuntu-Server 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tightvnc

Revision history for this message
George Bobeck (george-bobeck) wrote :
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
Alex Moldovan (alexmoldovan) wrote :

Here is the crash file

Revision history for this message
Chris J Arges (arges) wrote :

Can this bug be tested in Quantal and Precise as well? Thanks

Changed in tightvnc (Ubuntu):
importance: Undecided → Medium
Changed in tightvnc (Ubuntu Lucid):
status: New → Confirmed
Changed in tightvnc (Ubuntu):
status: Confirmed → New
Changed in tightvnc (Ubuntu Lucid):
importance: Undecided → Medium
Revision history for this message
penalvch (penalvch) wrote :

George Bobeck, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in tightvnc (Ubuntu):
status: New → Invalid
no longer affects: tightvnc (Ubuntu Lucid)
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.