Bug 245391 - VNC Server fails with depth of 24 pixels
Summary: VNC Server fails with depth of 24 pixels
Keywords:
Status: CLOSED DUPLICATE of bug 242277
Alias: None
Product: Fedora
Classification: Fedora
Component: vnc
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-22 19:52 UTC by Liam Dennehy
Modified: 2013-04-30 23:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-07-02 15:56:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
VNC Log output (831 bytes, text/plain)
2007-06-22 19:52 UTC, Liam Dennehy 		no flags Details
View All

Description Liam Dennehy 2007-06-22 19:52:33 UTC 
Description of problem:
creating a new VNC desktop with a depth of 8, 15 or 24 bits per pixel fails,
only 16 works.

Version-Release number of selected component (if applicable):
Xvnc 4.1.2

How reproducible:
Every time

Steps to Reproduce:
1. Launch a desktop with (e.g.)
vncserver :1 -geometry 1280x800 -depth 8
2.
3.
  
Actual results:
Silent failure, only log file reveals problem (and not being able to attach)

Expected results:
VNC desktop should be created

Additional info:
VNC desktop works jus fine for 16bpp
Comment 1 Liam Dennehy 2007-06-22 19:52:34 UTC 
Created attachment 157642 [details]
VNC Log output
Comment 2 Liam Dennehy 2007-06-22 19:58:43 UTC 
Hmmm, 8 is working now... 15 and 24 still fail.
Comment 3 Adam Tkac 2007-06-28 12:16:31 UTC 
What says rpm -q vnc-server? Looks like dupe of bug #242277 for me.
vnc-server-4.1.2-18.fc7 could support depths 8, 16 and 24 without any problem.
15bpp depth isn't supported now because I think this depth isn't used. If you
need it I could add 15bpp support.

Regards, Adam
Comment 4 Adam Tkac 2007-07-02 15:56:21 UTC 

*** This bug has been marked as a duplicate of 242277 ***
Comment 5 Liam Dennehy 2007-07-02 20:59:46 UTC 
Thanks for the attention, I will monitor the original bug.
Note You need to log in before you can comment on or make changes to this bug.