This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 589340 - [abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed by signal 6 (SIGABRT)
[abrt] crash in tigervnc-1.0.0-3.fc12: Process /usr/bin/vncviewer was killed ...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: tigervnc (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
abrt_hash:294cd925cfde291d205ed9cc4b5...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-05 17:51 EDT by Kai Meyer
Modified: 2013-04-30 19:46 EDT (History)
2 users (show)

See Also:
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:


Attachments (Terms of Use)
File: backtrace (6.33 KB, text/plain)
2010-05-05 17:51 EDT, Kai Meyer
no flags Details

  None (edit)
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 10.9.8.2
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
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 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.

Note You need to log in before you can comment on or make changes to this bug.