SUMMARY: GNOME startup issues

[Lingfeng Xiong]

Hi,
According your reply, can i assume that you mean gdm is a required
module for gnome to work well?
But i must say i dont think so. Gdm may really can solve this issue
but it is not the source of this.
1. I installed gnome without gdm in linux, and it worked well, no problem.
2. If this issue is caused by a normal user have no right to shutdown,
gnome-session at least should reply a 'refuse' message instead of
response nothing.
3. Gnome-panel is talking with gnome-session, not gdm.
4. If i double click on a non-freebsd partition, nothing would appear.
10min later, it may told me something no responding. I know this is a
problem related to hal, but dont you think it is also a problem
related to dbus? The default policy deny this message too. If i did
this in linux, a error box(no right,because i run gnome-session
without ck-launch-session) would appear immediatly.

On 7/12/10, Joe Marcus Clarke <marcus at freebsd.org> wrote:
> On 7/11/10 3:58 AM, Bear wrote:
>> hi,
>> Thanks for your reply. But I dont think GDM is required. When I use Linux
>> such as Debian, I can run GNOME without any problems, include this error
>> message, without GDM. GDM should not be a required module.
>> And also, I believe this message told us the slow responding of
>> gnome-panel. If I run startx as root, this error message would gone. So I
>> believe this is caused by a security policy(possibly dbus).
>> I hope my analysis is useful :)
>
> Root works because root is, of course, authorized to shutdown the
> system.  When you're a non-root user, additional authorization needs to
> be done.
>
> Joe
>
>>
>> ------------------				
>> Bear
>> 2010-07-11
>>
>> -------------------------------------------------------------
>> From:Joe Marcus Clarke
>> Send Date:2010-07-11 14:22:58
>> To:Bear
>> CC:FreeBSD GNOME Users
>> Subject:Re: SUMMARY: GNOME startup issues
>>
>> On 7/10/10 10:20 PM, Bear wrote:
>>> hi,
>>> Thanks for your working on these issues! Cant you recreate the issue? I
>>> can say something about the issue which related to gnome-panel. I always
>>> met this issue. My environment is listed below:
>>> Hardware:
>>> CPU: Intel Q8300
>>> Video: GeForce GTS 250 512MB
>>> RAM: Kingstone 2GB DDR2 800
>>> Motherboard: GA-EP45-UD3 rev 1.0 (Chipset: Intel P45)
>>>
>>> Software:
>>> FreeBSD 8.0-RELEASE
>>> Xorg
>>> gnome2-lite
>>>
>>> I installed my OS and then modify my PASKAGESITE to 8-stable. Then I
>>> typed in
>>> pkg_add -r xorg gnome2-lite
>>>
>>> And then I add dbus_enable="YES" and hald_enable="YES" into /etc/rc.conf.
>>> I also add the line into /etc/fstab to make it mount /proc automatically.
>>> I am sure that they both okay to ping localhost and my computer name.
>>> Then I reboot my computer and then modified ~/.xinitrc to add the line
>>> below:
>>> exec ck-launch-session gnome-session
>>>
>>> At last, I ran startx. Then the issue appeared. gnome-panel took long
>>> time to appear and in tty0, I got error messages like:
>>>
>>> ** (gnome-panel:69812): WARNING **: Could not ask session manager if shut
>>> down is available: Did not receive a reply. Possible causes include: the
>>> remote application did not send a reply, the message bus security policy
>>> blocked the reply, the reply timeout expired, or the network connection
>>> was broken.
>>
>> This is exactly what I see when I use startx, and it is expected.
>> Gnome-panel is trying to talk to GDM during this time.  Since GDM is not
>> running, you get this failure.  If you want to get rid of this, you'll
>> need to start GNOME with GDM.
>>
>> Joe
>>
>
>
> --
> Joe Marcus Clarke
> FreeBSD GNOME Team	::	gnome at FreeBSD.org
> FreeNode / #freebsd-gnome
> http://www.FreeBSD.org/gnome
>

-- 
Sent from my mobile device