Bug 1227346 - control center does not allow me to turn on screen sharing
Summary: control center does not allow me to turn on screen sharing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-02 13:09 UTC by udo
Modified: 2015-06-04 13:50 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-04 13:35:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description udo 2015-06-02 13:09:17 UTC
Description of problem:
control center does not allow me to turn on screen sharing without displaying further information

Version-Release number of selected component (if applicable):
control-center-3.16.2-1.fc22.x86_64

How reproducible:
Upgrade to fedora 22 from 20.


Actual results:
No working VNC connection (connection reset), control-center shows Screen sharing as off and cannot be tuned on.

Expected results:
Working VNC connection.

Additional info:

Comment 1 udo 2015-06-02 13:20:39 UTC
Found this error:

 gnome-control-center.desktop: (gnome-control-center:31491): sharing-cc-panel-WARNING **: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be enabled on this network, status is '0'

The control center screen does not show any networks.

Why can't I simply allow VNC access? My networks are secure and pathways are encrypted. Why mus the application think of its own?

How can a simple user use (cirumvent) the 'features' discussed at https://bugzilla.gnome.org/show_bug.cgi?id=727580 ?

Comment 2 udo 2015-06-02 13:27:38 UTC
Under Networks in control-center it says that NetworkManager needs to be running.
Of course we do not want NetworkMAnager on a simple hardwired connection to the firewall box.
Especially if NM does evil things to my operation network when we connect USB devices that appear as network connections without MAC address (connectgion to my Ipaq was like that).
The stubbornness and unuserfriendliness of NM in such cases, as of the developer(s) in question made me get rid of that software.
So now please allow me the freedom to turn on VNC on my own box. Please.

Comment 3 Rui Matos 2015-06-04 13:35:30 UTC
If you removed a core component of the OS (like NetworkManager) then you're certainly able to enable VNC screen sharing on your own.

I.e. removing NetworkManager is unsupported. I'd recommend you file bugs for the specific NetworkManager behavior that caused you to remove it in the first place so that you don't need to remove it in the future.

Comment 4 udo 2015-06-04 13:50:54 UTC
NM does add **nothing** in the situation I described, a simple wired connection to the firewall box. Instead it makes the connection **less** stable.
So I do not need NM.
I am not going to discuss with them again.
I will write this down as another stab at pushing users away from the nice distro that Fedora once was.
(think about systemd and the still persisting logging mess, the lack of priorities, etc)
There is no dependency between control-center and NM in the rpms. (BUG if you insist)
Therefor you cannot claim this stupid way out.
If you cannot understand that users want free choice on their own box and persist to insist on pushing a suite of stuff onto them you are not doing them any favours.

Please think of a simple way out for users that choose with their brains.


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