[gdm-list] GDM D-Bus on Solaris
- From: Brian Cameron <Brian Cameron Sun COM>
- To: gdm-list gnome org
- Cc: Artem Kachitchkine <Artem Kachitchkin Sun COM>, Jim Li <Jim Li Sun COM>
- Subject: [gdm-list] GDM D-Bus on Solaris
- Date: Tue, 28 Aug 2007 19:05:28 -0500
Jon/Jim/Artem:
We know that ConsoleKit isn't working with VT properly on Solaris.
It's close to working, I think, after fixing a lot of Solaris specific
bugs that are now in ConsoleKit SVN head. But there is still one
identified bug that causes the daemon to hang. We know the bug is in
the VT code causing a kernel lockup and Riny Qian here at Sun is looking
into fixing that in the next few weeks.
So, even though I knew VT wouldn't work, I figured I could still test
the non-VT features in GDM. However, it doesn't work well and seems to
exit quickly on startup. With the --no-daemon flag, I see the following
warnings coming from the failed call to acquire_name_on_proxy.
** (gdm-binary:10475): WARNING **: Failed to acquire org.gnome.DisplayManager:
Connection ":1.16" is not allowed to own the service "org.gnome.DisplayManager"
due to security policies in the configuration file
** (gdm-binary:10475): WARNING **: Could not acquire name; bailing out
Can you give me any ideas of what configuration changes I need to make in order
that GDM will work. What are the system requirements? I notice I don't have
libpam-ck-connector installed on my machine. Is this a requirement? If so, I
better start working on that too.
Is this related to PolicyKit or how HAL? I've cc:ed Jim Li and Artem
Kachitchkine from Sun since they have worked on getting PolicyKit working on
Sun and may have some comments.
Jon:
Thanks for updating the gdm-gobject branch with my latest patch. Now aside from
the utmp code, it all builds and installs fine. What are the plans for utmp?
Could you review the following bugs? If the next bug should be fixed in 2.18,
then it would be great if you could provide a patch.
http://bugzilla.gnome.org/show_bug.cgi?id=461056
The next bug was introduced by some of the cleanup work you did in 2.19. The
problem was that you rewrote the way this code worked so it tied each
server-foo section to a display. I fixed it so it works as it did before.
However, the code still is only reading in [server-foo] sections that
are referenced in the [servers] section. Really it should read in all
[server-foo] sections so it knows what they are. Currently gdmsetup is
broken if you try to edit the [server-foo] section because of this. I
think you understand the configuration section better than I, so perhaps
you could explain how this could be fixed? I'd like to get this fixed
in 2.18 if possible.
http://bugzilla.gnome.org/show_bug.cgi?id=462613
You can refer to the SVN commit I did on 2007-08-09 to see the changes
that I made to fix the bug partially.
We should probably also start looking at the GDM head daemon bugs that
have been fixed since the fork. I'd recommend looking over the patches
in these bug reports.
#470728
#457998
#460407
#443557
#349835
#331059
#434813
#435552
#436808
#436803
#436812
#436797
#462613 (the partial fix discussed above)
- The SVN commit I did on 2007-07-11 to fix CVE-2007-3381.
Brian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]