Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 586169 - [abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 552024
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f6ce2acc95aac4350484be3fe97...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-27 01:34 UTC by Matt Gagne
Modified: 2013-04-30 23:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-27 10:45:39 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (105.55 KB, text/plain)
2010-04-27 01:34 UTC, Matt Gagne 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Matt Gagne 2010-04-27 01:34:08 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/vncviewer
comment: The reproduce steps are what I did. Hoewver, it crashes EVERYTIME I open it, click options, then OK - even if NO changes are made.
component: tigervnc
executable: /usr/bin/vncviewer
global_uuid: f6ce2acc95aac4350484be3fe97098575bb99a64
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. Simply opened it
2. Clicked options, made changes
3. Clicked "OK"
4. Crashed!
Comment 1 Matt Gagne 2010-04-27 01:34:16 UTC 
Created attachment 409330 [details]
File: backtrace
Comment 2 Adam Tkac 2010-04-27 10:45:39 UTC 

*** This bug has been marked as a duplicate of bug 552024 ***
Note You need to log in before you can comment on or make changes to this bug.