Bug 115901 - xdmcp Enable=true not set in /etc/opt/gnome/gdm.conf by YaST2 for VNC remote administration
Summary: xdmcp Enable=true not set in /etc/opt/gnome/gdm.conf by YaST2 for VNC remote ...
Status: RESOLVED FIXED
: 334 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: PowerPC All
: P5 - None : Minor
Target Milestone: ---
Assignee: Arvin Schnell
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-08 15:57 UTC by Leah Cunningham
Modified: 2005-09-21 11:36 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
displaymanager (2.24 KB, text/plain)
2005-09-08 22:44 UTC, Leah Cunningham 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leah Cunningham 2005-09-08 15:57:31 UTC 
I have installed the GNOME default system.  I did make one change to the
gdm.conf file by hand to adjust autologin to not happen after installation.

When enabling remote administration in YaST2, I would expect for the [xdmcp]
section in gdm.conf to have Enable set to true, as this is how it has worked in
the past (iirc).  However, I had to enable it manually.  Maybe this is because
the file is not modified if you have already touched it, or maybe it is by
design...  Perhaps if it is by design, a warning message should be displayed though.
Comment 1 Michael Gross 2005-09-08 16:23:20 UTC 
I assigned it. But please try if this works with RC1 nontheless.
Comment 2 Stanislav Brabec 2005-09-08 18:40:32 UTC 
SuSEconfig (module gdm) should update settings from
/etc/sysconfig/displaymanager to gdm.conf, whenever one of sysconfig values is
changed.

If /etc/sysconfig/displaymanager has xdmcp disabled, it is a problem of YaST. If
it is emabled there but disabled in gdm, it is a problem of gdm.
Comment 3 Leah Cunningham 2005-09-08 22:43:13 UTC 
Looks like DISPLAYMANAGER_REMOTE_ACCESS is set to "yes".  I'll check in RC1 as
soon as I can, may be next week though.
Comment 4 Leah Cunningham 2005-09-08 22:44:57 UTC 
Created attachment 49284 [details]
displaymanager
Comment 5 Stanislav Brabec 2005-09-09 08:19:39 UTC 
Confirming problem.

This is a problem in the file Remote.ycp.

To propagate change in displaymanager sysconfig file to gdm, SuSEconfig gdm
module has tu be run, but is isn't.

Fix should be trivial oneliner. Nice to have in 10.0.
Comment 6 Arvin Schnell 2005-09-09 10:10:38 UTC 
Yes, a oneliner.
Comment 7 Martin Vidner 2005-09-21 11:36:57 UTC 
*** Bug 334 has been marked as a duplicate of this bug. ***