Bug 594544

Summary: [abrt] crash in tigervnc-1.0.1-1.fc12: Process /usr/bin/vncviewer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael Setzer II <mikes>
Component: tigervncAssignee: Adam Tkac <atkac>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: atkac, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:89880153f70e12da2998bbe9b65fd4c0976f2ec6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-18 04:34:23 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description Michael Setzer II 2010-05-20 20:59:32 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: vncviewer -passwdInput fedoragcc.dyndns.org:19
component: tigervnc
crash_function: rfb::TransImageGetter::setColourMapEntries
executable: /usr/bin/vncviewer
global_uuid: 89880153f70e12da2998bbe9b65fd4c0976f2ec6
package: tigervnc-1.0.1-1.fc12
rating: 4
reason: Process /usr/bin/vncviewer was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Michael Setzer II 2010-05-20 20:59:35 EDT
Created attachment 415546 [details]
File: backtrace
Comment 2 Michael Setzer II 2010-08-17 19:50:34 EDT
Package: tigervnc-1.0.1-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)

How to reproduce
1. vncviewer to remote machine
2. Then a dump occurred??

Use vncviewer to connect to remote machines, and have had no issues until today, when have gotten a number of these dumps.
Comment 3 Adam Tkac 2010-08-18 04:34:23 EDT

*** This bug has been marked as a duplicate of bug 624866 ***