https://bugzilla.novell.com/show_bug.cgi?id=383336
User kmachalkova@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383336#c3
Katarina Machalkova changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kmachalkova@novell.com, gekker@novell.com,
| |samba-maintainers@SuSE.de
AssignedTo|pgajdos@novell.com |bnc-team-gnome@forge.provo.novell.com
--- Comment #3 from Katarina Machalkova 2008-04-29 02:42:31 MST ---
Bug #304632 strikes back (as it is very likely that you're using GNOME, Michael
:) )
It is Yast who was responsible for adding '127.0.0.2 hostname' line to
/etc/hosts, and for 10.3, we have fixed the installation client to add this
line to /etc/hosts unconditionally so that GNOME apps can function correctly.
But maybe now that (instead of clickable 2nd stage) everything is configured
automatically, this installation client never gets called. Anyway, this issue
should be, instead of coming up with new workarounds in Yast, finally handled
properly
To summarize: if 127.0.0.2 line is not in /etc/hosts, GNOME apps hang (bug
#304632 - 10.3 blocker). If it is there, you cannot integrate such computer
into AD domain (bug #207392, SLED10 L3 critical). So using GNOME and using AD
are mutually exclusive.
So instead of one Yast blocker bug, this should be two blockers - one for GNOME
and the other for AD integration. Reassigning to gnome-maintainers, CCing samba
team, CCing also gekker, as this influences SLED
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
