GNOME can work well in VMWare but cannot work in real machine
Joe Marcus Clarke
marcus at freebsd.org
Tue Jun 15 22:41:56 UTC 2010
On 6/15/10 1:13 PM, Bear wrote:
> hi,
> I have done this. I created a new account named 'test' but it still have this problem...
Can you rebuild gnome-panel and gnome-session with debugging symbols,
then attach gdb while gnome-panel is "hung?" Once attached, run "bt" to
get a backtrace. That may help isolate the problem.
Joe
>
> ------------------
> Bear
> 2010-06-16
>
> -------------------------------------------------------------
> From:Joe Marcus Clarke
> Send Date:2010-06-16 00:11:32
> To:Bear
> CC:freebsd-gnome
> Subject:Re: GNOME can work well in VMWare but cannot work in real machine
>
> On 6/15/10 12:03 PM, Bear wrote:
>> hi, Yes of course I am sure that my hostname is reslovable. I used to
>> install GDM but it still has this problem. And also, I dont wanna
>> install it because I *DO NOT* need it.
>
> You might try creating a virgin account on the problem machine, and see
> if the problem follows the account. That is, a new account may not see
> any problem.
>
> Joe
>
>>
>> ------------------ Bear 2010-06-16
>>
>> -------------------------------------------------------------
>> From:Joe Marcus Clarke Send Date:2010-06-15 14:23:03 To:Lingfeng
>> Xiong CC:freebsd-gnome Subject:Re: GNOME can work well in VMWare but
>> cannot work in real machine
>>
>> On 6/14/10 9:50 PM, Lingfeng Xiong wrote:
>>> hi there, I found a strange thing. As I described, my GNOME cannot
>>> work with these error messages: gnome-session[69785]: WARNING:
>>> Unable to determine session: Unable to lookup ses sion information
>>> for process '69785' ** (gnome-panel:69812): WARNING **: Could not
>>> ask session manager if shut down i s available: Did not receive a
>>> reply. Possible causes include: the remote applic ation did not
>>> send a reply, the message bus security policy blocked the reply, t
>>> he reply timeout expired, or the network connection was broken.
>>>
>>>
>>> And gnome-panel has a very very slow responding. And also, the
>>> driver cannot be mounted without any error message. The thread
>>> about this problem with more information is here:
>>> http://forums.freebsd.org/showthread.php?t=15013
>>>
>>> I has performed a test, and found that GNOME can work well in my
>>> VMWare!! But in my real machine, no matter how many times I
>>> reinstalled my system, it cannot work. Could you help me? thx!!
>>
>> Make sure your machine's hostname is resolvable, and make sure you
>> are running gdm. Gdm will provide GNOME the ability to reboot and
>> shutdown.
>>
>> Joe
>>
>
>
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
More information about the freebsd-gnome
mailing list