This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 588020

Summary: [abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Igor Katalnikov <igor.katalnikov>
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, lst_manage, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:0a15e956f85331cdf0b169af9382fb7292dc5659
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-07 07:36:15 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Attachments:
Description Flags
File: backtrace none

Description Igor Katalnikov 2010-05-02 04:41:24 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/vncviewer
component: tigervnc
executable: /usr/bin/vncviewer
global_uuid: 0a15e956f85331cdf0b169af9382fb7292dc5659
kernel: 2.6.32.11-99.fc12.x86_64
package: tigervnc-1.0.0-3.fc12
rating: 4
reason: Process /usr/bin/vncviewer was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Start TigerVNC
2.Push Options
3.Push OK (with default settings)
Comment 1 Igor Katalnikov 2010-05-02 04:41:27 EDT
Created attachment 410770 [details]
File: backtrace
Comment 2 Emmett Culley 2010-05-02 10:27:30 EDT
Package: tigervnc-1.0.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.Start vncviewer via menu or command line
2. Select options.  Mostly you don't have to change anything
3. Close options dialog enter target address and port
4. Segfault happens when you click on OK


Comment
-----
Doesn't happen every time, but it is repeatable.
Comment 3 Adam Tkac 2010-05-07 07:36:15 EDT

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