Re: vnc problem FC6 - any workaround?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David G. Miller <dave <at> davenjudy.org> writes:

> Sounds like we need the OP to clarify what kind of access he wants.  
> Does he just need a remote desktop or does he need to share the current 
> X session?  My take on both the post that started this thread and the 
> referenced bug was that they only referred to a remote session but I 
> could be wrong.
> 
> Regardless of the answer to the above, it sounds like some functionality 
> (load vnc module and have glx) has been taken away.  If this used to 
> work prior to FC6, it might be worth it to open a bug even if it gets 
> thrown back at you with a WONTFIX.  I upgraded my systems that were 
> running FC4 or FC5 to FC6 so I can't verify that it worked in prior 
> releases of FC.  I just checked on my CentOS 4.4 box (running vncserver 
> to a FC6 vnc-client) and glx isn't available in the vnc session but is 
> available from the console.  This is consistent with what I see with an 
> FC6 vncserver.

The way I use vnc is precisely to help the remote user in sorting out problems
on their machine (so I need a shared X session so both the remote user and I can
see the same desktop) and in particular problems that can only be done on the
desktop itself - such as changing menus or taskbars etc or settings in KDE. This
always used to work in FC5 and earlier.

I have already entered a BZ for this - at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214169

and also there is possibly a related bug at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214169

I don't need glx for the purpose of this kind of vnc session but once I have
disconnected from the remote machine then the user on that machine would not
have access to glx unless I rebooted without the vnc module loaded in FC6 - this
is a reversion which presumably has crept in with the automatic enabling of DRI
in FC6?  Therefore we have gained something with the new 3-d stuff but lost
somthing along the way for an important tool (vnc).

This really does need to be fixed and hopefully sooner rather than later.

Mike






-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux