Bug 356271 - vncconfig is not setting parameters properly
vncconfig is not setting parameters properly
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: vnc (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-29 05:29 EDT by Joel Andres Granados
Modified: 2013-04-30 19:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-29 08:14:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joel Andres Granados 2007-10-29 05:29:32 EDT
Description of problem:
When using the vncconfig command to change a Xvnc variable, the command just
freezes.  I'm not sure if it is with all variables but it happened when setting
the SecurtyTypes to one of the two values.


Version-Release number of selected component (if applicable):
vnc-4.1.2-18.fc7
vnc-libs-4.1.2-18.fc7
vnc-server-4.1.2-18.fc7
I also tested with devel package and have the same behavior.


How reproducible:
Always

Steps to Reproduce:
1.vncserver
2.vncconfig -display # -set SecurtyTypes=None
3.
  
Actual results:
It just freezes,  does not give any output.  Additionally the value is not set.

Expected results:
For it to set the value accordingly 

Additional info:
Don't really know if its a bug or its a feature.  didn't find anything in the
man pages that stated that this could not be done.
Comment 1 Joel Andres Granados 2007-10-29 05:45:00 EDT
Think this is a false alarm.   Tested again and it seems to do what its supposed
to in f7.  I'll test in devel and see what happens.

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