Bug 589340

Summary: [abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Kai Meyer <kai>
Component: tigervncAssignee: Adam Tkac <atkac>
Status: CLOSED CURRENTRELEASE 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:294cd925cfde291d205ed9cc4b5b05d29bb0852a
Fixed In Version: tigervnc-1.0.1-1.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-07 07:40:16 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 Kai Meyer 2010-05-05 17:51:03 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: vncviewer
comment: Just regular use. I use vnc rather heavily. This was really really bad a few versions back, but it's not entirely gone.
component: tigervnc
executable: /usr/bin/vncviewer
global_uuid: 294cd925cfde291d205ed9cc4b5b05d29bb0852a
package: tigervnc-1.0.0-3.fc12
rating: 4
reason: Process /usr/bin/vncviewer was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
1. Open a connection using defaults
2. Change Color Level from Full to Low
3. Watch it crash (sometimes)
Comment 1 Kai Meyer 2010-05-05 17:51:05 EDT
Created attachment 411744 [details]
File: backtrace
Comment 2 Adam Tkac 2010-05-07 07:40:16 EDT
This issue should be fixed in the latest tigervnc-1.0.1-1.fc12. If it is still present, please reopen this issue.