Bug 547370 - [abrt] crash detected in tigervnc-1.0.0-3.fc12
Summary: [abrt] crash detected in tigervnc-1.0.0-3.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 522369
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:fb43d0e0e5fdede621aa6e35fdd...
: 544493 546469 566001 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-14 14:10 UTC by Nils Philippsen
Modified: 2013-04-30 23:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-03 07:42:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (3.25 KB, text/plain)
2009-12-14 14:10 UTC, Nils Philippsen 		no flags Details
View All

Description Nils Philippsen 2009-12-14 14:10:45 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
With a remote machine that has a running GNOME desktop, remote desktop sharing enabled:

1. "vncviewer -via <remotemachine> :0"
2. Reduce color depth: F8 -> Options -> In "Encoding and Color Level" uncheck "Auto select", then check "Medium" or "Low", click on "OK"
3. Crashes


Attached file: backtrace
cmdline: vncviewer -via wombat  0
component: tigervnc
executable: /usr/bin/vncviewer
kernel: 2.6.31.6-166.fc12.x86_64
package: tigervnc-1.0.0-3.fc12
rating: 4
reason: Process was terminated by signal 6
Comment 1 Nils Philippsen 2009-12-14 14:10:47 UTC 
Created attachment 378217 [details]
File: backtrace
Comment 3 Adam Tkac 2009-12-21 16:59:47 UTC 
*** Bug 546469 has been marked as a duplicate of this bug. ***
Comment 4 Karel Klíč 2010-02-24 16:53:41 UTC 
*** Bug 566001 has been marked as a duplicate of this bug. ***
Comment 5 Jan Görig 2010-03-02 14:49:52 UTC 
*** Bug 544493 has been marked as a duplicate of this bug. ***
Comment 6 Jan Görig 2010-03-03 07:42:47 UTC 

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