Bug 527758 - can not connect to vino VNC server (setPF: not 8, 16 OR 32 BPP)
Summary: can not connect to vino VNC server (setPF: not 8, 16 OR 32 BPP)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vino
Version: 12
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 659505
TreeView+ depends on / blocked
 
Reported: 2009-10-07 15:40 UTC by Cristian Ciupitu
Modified: 2014-06-18 09:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 659505 (view as bug list)
Environment:
Last Closed: 2010-12-04 07:32:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cristian Ciupitu 2009-10-07 15:40:44 UTC
Description of problem:
I can not connect to the vino VNC server using the TigerVNC client from Fedora 11.

Version-Release number of selected component (if applicable):
vino-2.28.0-3.fc12.x86_64 

How reproducible:
Every time

Steps to Reproduce:
1. Login to GNOME.
2. Activate the remote desktop.
3. Stop the firewall if necessarily.
3. Connect to the VNC server from another computer.
  
Actual results:
The VNC client gives this error "setPF: not 8, 16 OR 32 BPP".

Expected results:
No errors.

Additional info:
I'm using tigervnc-0.0.91-0.12.fc11.x86_64 as a client:
TigerVNC Viewer for X version 0.0.91 - built Aug 14 2009 09:54:10
Copyright (C) 2002-2005 RealVNC Ltd.
Copyright (C) 2000-2006 TightVNC Group
Copyright (C) 2004-2009 Peter Astrand for Cendio AB
See http://www.tigervnc.org for information on TigerVNC.

Wed Oct  7 18:39:52 2009
 CConn:       connected to host 192.168.122.100 port 5900
 CConnection: Server supports RFB protocol version 3.7
 CConnection: Using RFB protocol version 3.7
 main:        setPF: not 8, 16 or 32 bpp?

Comment 1 Bug Zapper 2009-11-16 13:22:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Cristian Ciupitu 2009-11-16 20:40:11 UTC
Just in case this matters, Fedora 12 (beta) was running on a KVM virtual machine under Fedora 11 (qemu-kvm-0.10.6-9.fc11.x86_64).

Comment 3 Andri Möll 2009-11-17 10:19:13 UTC
No go with Vinagre's client either.

Comment 4 Phillip Smith 2010-06-15 23:18:46 UTC
I get the same issue with Fedora 12, and Ubuntu 9.10, under a Xen HVM so it perhaps is an upstream issue?

Comment 5 Jerry Amundson 2010-09-02 04:03:38 UTC
My assumption is that the Assigned To here is either,
1. Deceased, or
2. Not interested.

Comment 6 Jerry Amundson 2010-09-02 17:36:33 UTC
Or,
3. Assigned To is busy, and has other priorities!

My apologies for the earlier remark - I have bugs with no activity for months and assumed otherwise. But I see updates by sandmann as recently as 2010-08-24 09:11:27 EDT.

I'll try to help by marking duplicates. Sorry for the noise.

Comment 7 Bug Zapper 2010-11-04 09:36:07 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2010-12-04 07:32:41 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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