http://bugzilla.novell.com/show_bug.cgi?id=546632
User ian.cheong@acm.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=546632#c9
Ian Cheong changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian.cheong@acm.org
--- Comment #9 from Ian Cheong 2009-10-24 21:19:13 MDT ---
I am completely confused by the remote desktop/administration function. I have
seen all the problems mentioned at variosu time. Happy to provide more
information but don't know what you need. Problems existed on 11.1 as well, but
have changed now that 11.2 has different mechansim for setting up graphics
devices (I thought not using xorg.conf)
My machine has two graphics devices, onboard and nvidia card, with different
resolution.
As far as I can figure there are several issues:
1. YaST/Gnome in 11.2RC1 has no "Graphics and monitor" control panel, so no way
to set up dual display mode using gui. I thought it should be set up to use
mirroring.
2. Remote Management is a bit unclear about which service/port it is using. See
attached screenshot. Remote is functioning on port 5801 with no password.
Remote desktop preferences thinks it is using port 5802, but this doesn't work.
Somehow my remote session is using a separate session rather than desktop
sharing and applications which are open on the primary desktop are unaccessible
to the remote session.
3. I'm presently presuming I have logged in using user switching and the system
has let me in with more than one session on different desktops without access
to the original desktop.
I have done nothing special to the 11.2rc1 install to try make remote
management work. (YaST2> Only running "sax2 -r -m0=nvidia" from command line
because when the system crashes, X seems to lose configuration and I get
wallpaper and a mouse pointer and no GUI. Running sax2 then rebooting fixes it.
Let me know what other information you need to debug.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.