gnome-panel problems

[jilingshu]

hi all,
I dont know if this is a new problem but I searched this forum and found nothing.
I fresh installed my FreeBSD 8.0-RELEASE and upgrade it to p2. Then I installed these ports:
bash
xorg-minimal
gnome2-lite
wqy (Chinese fonts)
ibus-pinyin (Chinese IME)
nvidia-driver
nvidia-xsetting

When I typed in startx, some problems appeared.

First, the desktop appeared as normal, but the gnome-panel wont appear. I must wait for a long time. And when I added or deleted some ports/packages with icon on menu, the gnome-panel will lost responding. I have to wait for another long time for its recover.
I switched to tty1 and got these information:


[bear@bear ~]$ startx
xauth: creating new authority file /home/bear/.serverauth.5668


X.Org X Server 1.7.5
Release Date: 2010-02-16
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 8.0-RELEASE-p2 amd64
Current Operating System: FreeBSD bear.whitebear.lan 8.0-RELEASE-p2 FreeBSD 8.0-
RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 root@amd64-builder.daemonology.n
et:/usr/obj/usr/src/sys/GENERIC amd64
Build Date: 24 May 2010 09:06:50AM

Current version of pixman: 0.16.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon May 24 16:41:35 2010
(==) Using config file: "/etc/X11/xorg.conf"
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
gnome-session[5689]: WARNING: Unable to determine session: Unable to lookup sess
ion information for process '5689'
GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l
GNOME_KEYRING_PID=5707
May 24 16:41:37 bear gnome-keyring-daemon[5707]: couldn't allocate secure memory
to keep passwords and or keys from being written to the disk
GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l
SSH_AUTH_SOCK=/var/tmp/keyring-hXBL8l/ssh
GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l
SSH_AUTH_SOCK=/var/tmp/keyring-hXBL8l/ssh
窗口管理器警告：无法读取保存的会� �文件 /home/bear/.config/met
acity/sessions/102b991067f3508b1112746904977822500000056890013.ms ：打开文件
“/home/bear/.config/metacity/sessions/102b991067f3508b111274690497782250000005
6890013.ms”失败：No such file or directory
May 24 16:41:39 bear pulseaudio[5734]: pid.c: Daemon already running.

** (gnome-panel:5719): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.

** (gnome-panel:5719): WARNING **: Error deleting '/home/bear/.gnome2/panel2.d/d
efault/launchers/evolution.desktop': 移除文件出错：No such file or direct
ory


(gnome-appearance-properties:5789): Pango-WARNING **: failed to choose a font, e
xpect ugly output. engine-type='PangoRenderFc', script='common'
May 24 16:44:24 bear firefox-bin: gethostby*.getanswer: asked for "twitter.com I
N AAAA", got type "A"
May 24 16:44:24 bear firefox-bin: gethostby*.getanswer: asked for "www.facebook.
com IN AAAA", got type "A"

** (gnome-volume-control:5831): WARNING **: Bad setup, install the freedesktop s
ound theme

(gnome-volume-control:5831): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: ass
ertion `GTK_IS_TREE_MODEL (tree_model)' failed

** (gnome-volume-control:5858): WARNING **: Bad setup, install the freedesktop s
ound theme

(gnome-volume-control:5858): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: ass
ertion `GTK_IS_TREE_MODEL (tree_model)' failed
** (gnome-screensaver-preferences:5866): DEBUG: Found best visual for GL: 0x21

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (polkit-gnome-authorization:5869): WARNING **: Cannot get PolKitCaller object
for target (pid=5869): org.freedesktop.PolicyKit: Cannot look up start time for
pid 5869

** (gnome-panel:5719): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

(nautilus:5728): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTA
INER (container)' failed

** (gnome-panel:6264): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.
May 24 16:52:26 bear firefox-bin: gethostby*.getanswer: asked for "www.youtube.c
om IN AAAA", got type "A"
May 24 16:52:27 bear firefox-bin: gethostby*.getanswer: asked for "sites.google.
com IN AAAA", got type "A"

** (gnome-panel:6264): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.
May 24 16:57:04 bear firefox-bin: gethostby*.getanswer: asked for "sites.google.
com IN AAAA", got type "A"

** (gnome-panel:6264): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.
May 24 17:01:10 bear firefox-bin: gethostby*.getanswer: asked for "sites.google.
com IN AAAA", got type "A"

INER (container)' failed

** (gnome-panel:6264): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.
May 24 16:52:26 bear firefox-bin: gethostby*.getanswer: asked for "www.youtube.c
om IN AAAA", got type "A"
May 24 16:52:27 bear firefox-bin: gethostby*.getanswer: asked for "sites.google.
com IN AAAA", got type "A"

** (gnome-panel:6264): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.
May 24 16:57:04 bear firefox-bin: gethostby*.getanswer: asked for "sites.google.
com IN AAAA", got type "A"


And I also found gnome-panel.core in my home directory.

Could you give me some advice on this? thx!!

[zeiz]

Do you have in /etc/fstab :
proc /proc procfs rw 0 0
Actually here (http://www.freebsd.org/gnome/) is a lot, especially FAQ and HAL FAQ.

[jilingshu]

Do you have in /etc/fstab :
proc /proc procfs rw 0 0
Actually here (http://www.freebsd.org/gnome/) is a lot, especially FAQ and HAL FAQ.

hi,
thanks for ur answer, but ... er... it still cannot work since i added the proc into fstab.
The warnning still there so I dont think this way is correct.
What can I do now? thx!

P.S.:Its rather strange... All themes and icons in GNOME become corrupted today. Most icons can shown correctly and theme become X11-default. I tried to change theme in Menu - Apperance but it tooks no effect except Title Bar.

[SirDice]

Hal and dbus aren't running.

Also review the Gnome and HAL FAQ.

http://www.freebsd.org/gnome/docs/faq2.html#q20

[jilingshu]

Hal and dbus aren't running.

Also review the Gnome and HAL FAQ.

http://www.freebsd.org/gnome/docs/faq2.html#q20

hi,
thanks for ur answer. I have added these lines into rc.conf

hald_enable="YES"
dbus_enable="YES"
gnome_enable="YES"

And I ran ps in gnome-terminal, I got this:

[bear@bear /usr/home/bear]$ ps
PID TT STAT TIME COMMAND
1455 v0 I 0:00.01 -bash (bash)
1651 v0 I+ 0:00.00 /bin/sh /usr/local/bin/startx
1669 v0 I+ 0:00.00 xinit /home/bear/.xinitrc -- /usr/local/bin/X :0 -aut
1672 v0 I 0:00.44 gnome-session
1675 v0 I 0:00.00 dbus-launch --exit-with-session gnome-session
1681 v0 S 0:01.58 gnome-panel
1687 v0 S 0:01.63 nautilus
1694 v0 S 0:00.23 gnome-volume-control-applet
1695 v0 I 0:00.60 ibus-daemon --xim
1698 v0 I 0:00.02 /usr/local/libexec/ibus-gconf
1699 v0 S 0:00.84 python /usr/local/share/ibus/ui/gtk/main.py
1701 v0 S 0:00.05 /usr/local/libexec/ibus-x11 --kill-daemon
1708 v0 I 0:00.16 python /usr/local/share/ibus-pinyin/engine/main.py --
1933 v0 S 0:00.78 metacity
1934 v0 I 0:00.02 libgtop-server (libgtop_server2)
1948 v0 I 0:01.73 gnome-terminal
22346 v0 I 0:00.01 /bin/sh /usr/local/bin/firefox3
22369 v0 I 0:00.00 /bin/sh /usr/local/lib/firefox3/run-mozilla.sh /usr/l
22389 v0 I 0:09.21 /usr/local/lib/firefox3/firefox-bin
1950 0 Is 0:00.01 bash
39794 1 Ss 0:00.01 bash
42020 1 R+ 0:00.00 ps
[bear@bear /usr/home/bear]$

I can see dbus-daemon running.
Could you help me? thx!

[SirDice]

ibus != dbus

[zeiz]

I recalled that when I tried xorg-minimal I also got some problems.
Then I figured out that it's not big difference in MB between xorg and xorg-minimal
after that I've been installing just full xorg.
I would try install of full xorg-7.5

PS. proc line in /etc/fstab is a must for Gnome.
Even if it didn't solve your current problem this way is correct ;)

[jilingshu]

ibus != dbus

hi,
thx for ur reminding. But in fact, I know dbus != ibus ;)
ibus is only a Chinese IME I installed. You can see both ibus-daemon and dbus-daemon in ps output :)

[jilingshu]

I recalled that when I tried xorg-minimal I also got some problems.
Then I figured out that it's not big difference in MB between xorg and xorg-minimal
after that I've been installing just full xorg.
I would try install of full xorg-7.5

PS. proc line in /etc/fstab is a must for Gnome.
Even if it didn't solve your current problem this way is correct ;)

hi,
thx for ur answer. I have installed xorg without deinstalling xorg-minimal. But the problem still there... Need I reinstall xorg-minimal or gnome2-lite or even the whole FreeBSD? It would took me a whole day building xorg and gnome2-lite...

[zeiz]

xorg and xorg-minimal are metapackages; I didn't mean to deinstall all packages belonging to xorg-minimal, only metapackage itself and replace it with xorg metapackage (that would install a number of additional packages). I'm sure you know that.
You don't need to build everything from ports (compile from source).
There are all latest packages (xorg-7.5, gnome2-2.30) on FreeBSD ftp server.
I'm on 8-STABLE and my latest update gave me 8.1-PRERELEASE.
There is also latest snapshot of 8-STABLE there: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/ choose your ARCH.
Install the snapshot and then just run:
# pkg_add -r xorg
# pkg_add -r gnome2-lite

It'd take you an hour altogether.
If you want to stay with 8.0-RELEASE (despite 8.1 is around the corner) set your environment to 8-STABLE branch (if you use bash it may have different syntax - google):
# setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/ARCH/packages-8-stable/Latest/
and enjoy latest packages :)

[jilingshu]

xorg and xorg-minimal are metapackages; I didn't mean to deinstall all packages belonging to xorg-minimal, only metapackage itself and replace it with xorg metapackage (that would install a number of additional packages). I'm sure you know that.
You don't need to build everything from ports (compile from source).
There are all latest packages (xorg-7.5, gnome2-2.30) on FreeBSD ftp server.
I'm on 8-STABLE and my latest update gave me 8.1-PRERELEASE.
There is also latest snapshot of 8-STABLE there: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/ choose your ARCH.
Install the snapshot and then just run:
# pkg_add -r xorg
# pkg_add -r gnome2-lite

It'd take you an hour altogether.
If you want to stay with 8.0-RELEASE (despite 8.1 is around the corner) set your environment to 8-STABLE branch (if you use bash it may have different syntax - google):
# setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/ARCH/packages-8-stable/Latest/
and enjoy latest packages :)

hi,
Your answer is very useful but... Er... My problem still stay unsolved...
I still got these errors below.

gnome-session[1489]: WARNING: Unable to determine session: Unable to lookup sess
ion information for process '1489'
(nautilus:1508): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `f
ormat != NULL' failed
(gnome-appearance-properties:1644): Gtk-WARNING **: Theme directory 48x48/mimety
pes of theme Snow-Apple has no size field
** (gnome-panel:1502): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.


And it took a very long time to start GNOME.

[jilingshu]

I have gotten a new log which would be more clear and understood.

[bear@bear ~]$ startx
xauth: creating new authority file /home/bear/.serverauth.2423


X.Org X Server 1.7.5
Release Date: 2010-02-16
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 8.0-RELEASE-p2 amd64
Current Operating System: FreeBSD bear.whitebear.lan 8.0-RELEASE-p2 FreeBSD 8.0-
RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 root@amd64-builder.daemonology.n
et:/usr/obj/usr/src/sys/GENERIC amd64
Build Date: 24 May 2010 09:06:50AM

Current version of pixman: 0.16.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed May 26 13:04:15 2010
(==) Using config file: "/etc/X11/xorg.conf"
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
gnome-session[2444]: WARNING: Unable to determine session: Unable to lookup sess
ion information for process '2444'
GNOME_KEYRING_CONTROL=/var/tmp/keyring-N1UEEJ
GNOME_KEYRING_PID=2455
May 26 13:04:16 bear gnome-keyring-daemon[2455]: couldn't allocate secure memory
to keep passwords and or keys from being written to the disk
GNOME_KEYRING_CONTROL=/var/tmp/keyring-N1UEEJ
SSH_AUTH_SOCK=/var/tmp/keyring-N1UEEJ/ssh
GNOME_KEYRING_CONTROL=/var/tmp/keyring-N1UEEJ
SSH_AUTH_SOCK=/var/tmp/keyring-N1UEEJ/ssh

(gnome-settings-daemon:2458): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name:
assertion `format != NULL' failed
窗口管理器警告：无法读取保存的会� �文件 /home/bear/.config/met
acity/sessions/1028e710ff202a8070127485025648697600000024440015.m s：打开文
�“/home/bear/.config/metacity/sessions/1028e710ff202a8070127485025648697600000
024440015.ms”失败：No such file or directory
May 26 13:04:17 bear pulseaudio[2483]: pid.c: Daemon already running.

(polkit-gnome-authentication-agent-1:2482): polkit-gnome-1-WARNING **: Unable to
determine the session we are in: Remote Exception invoking org.freedesktop.Cons
oleKit.Manager.GetSessionForUnixProcess() on /org/freedesktop/ConsoleKit/Manager
at name org.freedesktop.ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralE
rror: Unable to lookup session information for process '2482' org.freedesktop.Co
nsoleKit.Manager.GeneralError Unable%20to%20lookup%20session%20information%20for
%20process%20%272482%27

(gnome-settings-daemon:2458): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name:
assertion `format != NULL' failed

(nautilus:2468): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `f
ormat != NULL' failed

** (gnome-panel:2466): WARNING **: Could not ask session manager if shut down is
available: Did not receive a reply. Possible causes include: the remote applica
tion did not send a reply, the message bus security policy blocked the reply, th
e reply timeout expired, or the network connection was broken.

[DutchDaemon]

@jilingshu: use the proper posting tags (http://forums.freebsd.org/showthread.php?t=8816). System output belongs in [code] tags, not [quote] tags.

[jilingshu]

@jilingshu: use the proper posting tags (http://forums.freebsd.org/showthread.php?t=8816). System output belongs in [code] tags, not [quote] tags.

Er... I am very sorry that I will take care of this.:P

[jilingshu]

hi all,
I have reinstalled my FreeBSD and installed the xorg and gnome2-lite packages from pkg_add -r. But the problem still there!!!!
What shall I do??
thx!

[zeiz]

I would try to troubleshoot one by one:
1. Install FreeBSD without localizations.
2. Check general behavior and check dmesg output: is everything fine?
3. Install Xorg only without anything else.
4. Does Xorg work fine with twm?
5. If not - configure X. If yes
6. Install Gnome and configure it looking also here: http://www.freebsd.org/gnome/ (FAQ and HAL FAQ too).
7. Does problem appear again? If not
8. Install everything else and watch when problems appear (if any).
9. If yes. Troubleshoot Gnome (standalone topic).
10. Google for similar issues (in general :))

[fender0107401]

cd your home and delete related gnome config file and install gdm

[jilingshu]

cd your home and delete related gnome config file and install gdm

I tried to delete all files which related to gnome in my home directory. But I dont wanna install gdm. I dont need it.

[jilingshu]

I would try to troubleshoot one by one:
1. Install FreeBSD without localizations.
2. Check general behavior and check dmesg output: is everything fine?
3. Install Xorg only without anything else.
4. Does Xorg work fine with twm?
5. If not - configure X. If yes
6. Install Gnome and configure it looking also here: http://www.freebsd.org/gnome/ (FAQ and HAL FAQ too).
7. Does problem appear again? If not
8. Install everything else and watch when problems appear (if any).
9. If yes. Troubleshoot Gnome (standalone topic).
10. Google for similar issues (in general :))

hi,
I have reinstalled my system and installed xorg and twm. I added hald_enable="YES" and dbus_enable="YES" into my rc.conf and tried to type in "startx". There is no problem. No error messages in console.
I think the problem is in gnome.
;)

BTW:I googled for so many times and there is no answer for this question yet...

[zeiz]

Right today I reinstalled my 9-current amd64 to get Chromium browser working.
I installed X from packages found only 2 packages (out of >200) out of date.
Then I installed Chromium and got it working with flash (installed all the linux stuff) and then found only 1 outdated package.
Then I installed gnome2-lite from packages and found 8 outdated packages.
Then I installed gimp and inkscape updated ports and portupgrade 2 more packages.
Everything is just fine, never better.
You really have something special, sorry if I cannot help.

[jilingshu]

Right today I reinstalled my 9-current amd64 to get Chromium browser working.
I installed X from packages found only 2 packages (out of >200) out of date.
Then I installed Chromium and got it working with flash (installed all the linux stuff) and then found only 1 outdated package.
Then I installed gnome2-lite from packages and found 8 outdated packages.
Then I installed gimp and inkscape updated ports and portupgrade 2 more packages.
Everything is just fine, never better.
You really have something special, sorry if I cannot help.

hi,
thx for ur answer.
I have installed GNOME today from port. But so strange, the problem appeared. twm can work well but GNOME cannot.

gnome-session[2444]: WARNING: Unable to determine session: Unable to lookup sess
ion information for process '2444'


gnome-panel still have a very slow responding while menus got changed.

[zeiz]

I meaningfully counted outdated packages: there are just about 10 of them to update at this time and I believe none - is critical.
Compiling of Gnome takes a day or more, why don't you try packages? It would take an hour.
A compiler also may have bugs (and ones specific to your hardware). Even if some packages' default configs are not good enough for you
you could try the defaults first and then recompile only those packages. It would take an hour or 2.

[jilingshu]

I meaningfully counted outdated packages: there are just about 10 of them to update at this time and I believe none - is critical.
Compiling of Gnome takes a day or more, why don't you try packages? It would take an hour.
A compiler also may have bugs (and ones specific to your hardware). Even if some packages' default configs are not good enough for you
you could try the defaults first and then recompile only those packages. It would take an hour or 2.

hi,
I have tried packages. I am using FreeBSD 8.0-RELEASE. I installed GNOME via pkg_add -r gnome2-lite, and this error still there...
BTW: It seems that 8.0-RELEASE will install GNOME-2.28 automatically.

[zeiz]

One more puzzle...:)
On ftp they have 2.26.3 for both: gnome2 and gnome2-lite.
What is the output of
echo $PACKAGESITE?

[jilingshu]

One more puzzle...:)
On ftp they have 2.26.3 for both: gnome2 and gnome2-lite.
What is the output of
echo $PACKAGESITE?

it outputs nothing ;)

Maybe from pkg I installed 2.26? I forgot it... At least it is not 2.30. Yes, I believe it is not 2.30.
BTW: I use Taiwan mirror.

[zeiz]

Of course it's not 2.30 if you are on 8.0-RELEASE. 8.1 - is around the corner, maybe try 8-STABLE? The latest snapshot is in ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/

Well, what is the output of this command:
$PACKAGESITE?

To get 2.30 when on RELEASE(for csh):
setenv PACKAGESITE ftp://ftp.jp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/Latest/
This works till first reboot then must be set again.

I noticed a kind of mess on TW mirrors: main one has gnome2-2.22, another is empty (ftp.tw6)
You'd rather check "manually" what is present on a mirror before install.
Also Japanese servers are good even from here and must be very fast for you.

[jilingshu]

Of course it's not 2.30 if you are on 8.0-RELEASE. 8.1 - is around the corner, maybe try 8-STABLE? The latest snapshot is in ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/

Well, what is the output of this command:
$PACKAGESITE?

To get 2.30 when on RELEASE(for csh):
setenv PACKAGESITE ftp://ftp.jp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/Latest/
This works till first reboot then must be set again.

I noticed a kind of mess on TW mirrors: main one has gnome2-2.22, another is empty (ftp.tw6)
You'd rather check "manually" what is present on a mirror before install.
Also Japanese servers are good even from here and must be very fast for you.

er... Could u tell me how to upgrade my FreeBSD to 8.1-PRERELEASE? I wanna try it.

[zeiz]

The easy way is to download the 8-stable snapshot as I mentioned above. Choose dvd1.iso, it has live file system that could be very useful.
Install it as usual and you'll get access to newest packages. Install them and see if you problem gone. This all may take 1-1.5 hours.
Start with this. Then you supposed to learn how to rebuild base (world) and kernel. It's not as difficult as one could imagine. Read handbook, there is a howto on this forum and some threads. Just search the forum. Post questions if still something isn't clear.
http://forums.freebsd.org/showpost.php?p=58220&postcount=21
There is another way to upgrade 8.0 to 8.1. It's freebsd-upgrade. I tried it too but found it more troublesome and time consuming than just rebuild world and kernel. But you may like it. It explained very well in handbook and also in a number of threads here. Search for "freebsd-upgrade"

[jilingshu]

The easy way is to download the 8-stable snapshot as I mentioned above. Choose dvd1.iso, it has live file system that could be very useful.
Install it as usual and you'll get access to newest packages. Install them and see if you problem gone. This all may take 1-1.5 hours.
Start with this. Then you supposed to learn how to rebuild base (world) and kernel. It's not as difficult as one could imagine. Read handbook, there is a howto on this forum and some threads. Just search the forum. Post questions if still something isn't clear.
http://forums.freebsd.org/showpost.php?p=58220&postcount=21
There is another way to upgrade 8.0 to 8.1. It's freebsd-upgrade. I tried it too but found it more troublesome and time consuming than just rebuild world and kernel. But you may like it. It explained very well in handbook and also in a number of threads here. Search for "freebsd-upgrade"

I AM GETTING MAD!!!!
I reinstalled my system and then upgraded it to FreeBSD 8.1-BETA1 instantly via freebsd-upgrade. Then I found that it would download packages form 8.0-STABLE automatically. I type in
pkg_add -r xorg gnome2-lite
It downloaded and installed packages from ftp.freebsd.org automacially. Then I went out.
When I return, I added

gnome_enable="YES"

into /etc/rc.conf, and

proc /proc procfs rw 0 0

into /etc/fstab. Then I reboot my computer. When I loggin, I type in
startx
Then the nightmare RETURNED AGAIN!!!!
OMG!!!
What shall I do??

[jilingshu]

Ahhhhhhhhhhhh,
I think I found the source of the problem!!!! This is a strange problem. I have looked up into /proc, and I found every process has a pid-named folder except gnome-session. I run ps and got gnome-session's PID 2110. Then I run

ls /proc

and found no folder named 2110. Then I looked gnome-panel and other process's PID and found they all have a folder in /proc. So strange... Could you help me? thx!

[zeiz]

OK. Please post your output of uname -a
Also we have no idea what hardware do you have.
Please attach (as text file attachment - don't post) full output of dmesg
Please post again (or better attach as text file) the error messages you are receiving now.
Please post here your /etc/rc.conf
Last question so far: this time did you install xorg before gnome2-lite?

In meantime: the line gnome_enable="YES" enables dbus, hald , avahi , and gdm . All at once.
Since you installed gnome2-lite you don't have gdm installed and you probably don't need avahi so edit this part of /etc/rc.conf like this:
#gnome_enable="YES"
dbus_enable="YES"
hald_enable="YES"
Next. I hope you don't run startx as root so you have created ~/.xinitrc (where ~/ represents your regular user's home directory) with the line exec gnome-session If not just create the file.
Next: Did you edit /etc/hosts ? If not edit it as described in Gnome FAQ #20 (http://www.freebsd.org/gnome/docs/faq2.html#q20)

After all done please attach the output of ps aux

[jilingshu]

OK. Please post your output of uname -a
Also we have no idea what hardware do you have.
Please attach (as text file attachment - don't post) full output of dmesg
Please post again (or better attach as text file) the error messages you are receiving now.
Please post here your /etc/rc.conf
Last question so far: this time did you install xorg before gnome2-lite?

In meantime: the line gnome_enable="YES" enables dbus, hald , avahi , and gdm . All at once.
Since you installed gnome2-lite you don't have gdm installed and you probably don't need avahi so edit this part of /etc/rc.conf like this:
#gnome_enable="YES"
dbus_enable="YES"
hald_enable="YES"
Next. I hope you don't run startx as root so you have created ~/.xinitrc (where ~/ represents your regular user's home directory) with the line exec gnome-session If not just create the file.
Next: Did you edit /etc/hosts ? If not edit it as described in Gnome FAQ #20 (http://www.freebsd.org/gnome/docs/faq2.html#q20)

After all done please attach the output of ps aux

hi,
I have attached all files you need and some more.
Of course, I installed gnome2-lite after xorg everytime.
And I never run X as root. I run it as a regular user everytime.
I never edited /etc/hosts.

If you need other information, please tell me, I will give them to you.
Thx for ur help!

[zeiz]

Sorry, no clue. Everything looks ~same as here but the errors.
Actually I discovered some error in my install too but they don't affect Gnome performance.
There is a file /var/log/messages maybe something is there?
You've sent errors from 8.0-release. Are new errors (under 8.1-beta) the same as it was under 8.0-release?
You have plenty of room on HDDs. What if you try installing gdm ?

As to /etc/hosts please edit it as recommended though I don't think it's the root of the problem.

[jilingshu]

Sorry, no clue. Everything looks ~same as here but the errors.
Actually I discovered some error in my install too but they don't affect Gnome performance.
There is a file /var/log/messages maybe something is there?
You've sent errors from 8.0-release. Are new errors (under 8.1-beta) the same as it was under 8.0-release?
You have plenty of room on HDDs. What if you try installing gdm ?

As to /etc/hosts please edit it as recommended though I don't think it's the root of the problem.

hi,
I have attached /var/log/message. These problems are as seem as it be in 8.0-RELEASE. Maybe even in 7.0-RELEASE? I remembered about two years ago, it was I installed FreeBSD first time in my life. I installed xorg and gnome2 from packages and there also so many errors in tty1 while I start it. But I cannot remember what errors they are. And I must say I installed 7.0 in an old computer, not the one I now using.
I will try gdm later. Shall I post a mail to mailing list of GNOME in FreeBSD to report this?

[jilingshu]

So strange!
After I installed gdm, the /proc shown the folder which named by gnome-session pid and there is no lang gap between gnome-panel appearing.
Because there is no output in any ttys so I dont know if there still any errors.
I will do something to find what happened while I installing gdm.

[jilingshu]

hi,
I have tried gdm. Now if I add gdm_enable="YES" into /etc/rc.conf, everything works well, there is a folder in /proc named by gnome-session pid. But I removed the line and typed in startx, the error would appeared again. I think only gdm can execute gnome-session correctly.

[jilingshu]

hi,
I have tried to run gnome-session as root. Nothing unusual except all ntfs volumes are mounted. The problem still there.

[zeiz]

At the end of your /var/log/messages there are messages similar to this:
https://bugzilla.redhat.com/show_bug.cgi?id=495986
It's about Fedora but it's more about Gnome. Maybe indeed write to gnome@FreeBSD.org?
There are a team there: http://www.freebsd.org/gnome/contact.html
Who knows: may be you discovered a bug?
In my "messages" I see this:
avahi-daemon[967]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
gnome-session[1222]: WARNING: Could not launch application 'at-spi-registryd-wrapper.desktop': Unable to start application:
Failed to execute child process "${exec_prefix}/libexec/at-spi-registryd" (No such file or directory)
gnome-session[1222]: WARNING: Could not launch application 'gnome-power-manager.desktop': Unable to start application:
Failed to execute child process "gnome-power-manager" (No such file or directory)
gnome-keyring-daemon[1255]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
gnome-session[1222]: WARNING: Application 'metacity.desktop' failed to register before timeout
But they feels harmless so I just don't care.
Some applications while run as root may install important files in /root instead of user directory.
Also all "gurus" say that it's very bad practice :)
There is even a thread here about running X as root.

[jilingshu]

At the end of your /var/log/messages there are messages similar to this:
https://bugzilla.redhat.com/show_bug.cgi?id=495986
It's about Fedora but it's more about Gnome. Maybe indeed write to gnome@FreeBSD.org?
There are a team there: http://www.freebsd.org/gnome/contact.html
Who knows: may be you discovered a bug?
In my "messages" I see this:
avahi-daemon[967]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
gnome-session[1222]: WARNING: Could not launch application 'at-spi-registryd-wrapper.desktop': Unable to start application:
Failed to execute child process "${exec_prefix}/libexec/at-spi-registryd" (No such file or directory)
gnome-session[1222]: WARNING: Could not launch application 'gnome-power-manager.desktop': Unable to start application:
Failed to execute child process "gnome-power-manager" (No such file or directory)
gnome-keyring-daemon[1255]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
gnome-session[1222]: WARNING: Application 'metacity.desktop' failed to register before timeout
But they feels harmless so I just don't care.
Some applications while run as root may install important files in /root instead of user directory.
Also all "gurus" say that it's very bad practice :)
There is even a thread here about running X as root.

Emmm... I remembered the error message

gnome-keyring-daemon[1255]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk

has already exsited in FreeBSD 7.0-RELEASE.
Now I will send email to gnome@freebsd.org. I hope this problem can get solved.
Thank you for your help!:)

[chrisstankevitz]

I have the same problem The problem is not:

- misconfigured /etc/hosts
- dbus not running
- hald not running
- /proc not mounted

The problem is deeper than this. The problem is related to the components not being able to communicate with gnome-session. Please tell me when you find the solution.

Thank you,

Chris

[chrisstankevitz]

The might be related to this entry in /var/log/messages:

Jul 1 04:00:23 myhost kernel: pid 1551 (polkit-gnome-authen), uid 92: exited on signal 4 (core dumped)

Chris

[zeiz]

Ironically I just recently also got similar problem :)
Exactly with gnome-panel: Gnome shows already icons on Desktop but it takes a minute or more for gnome-panel to appear.
I installed Xfce then Gnome then KDE on 9-CURRENT. After switching to KDM gnome-panel "went astray" as above.
I returned to GDM and problem was gone. I decided to investigate the problem later, switched again to KDM and worked with KDE where I did a couple of updates. Unfortunately I don't remember what Gnome-related updates I did at the same time. But when I next time started Gnome from KDM the problem was gone. So I don't know what exactly fixed it. Maybe even switching to GDM (enabling it after fresh Gnome install) at least once is already enough. But may be some updates fixed it.
In general I noticed that with GDM enabled Gnome (2.30) starts faster than if use startx.
So the problem may be somehow connected to GDM.

[jilingshu]

Ironically I just recently also got similar problem :)
Exactly with gnome-panel: Gnome shows already icons on Desktop but it takes a minute or more for gnome-panel to appear.
I installed Xfce then Gnome then KDE on 9-CURRENT. After switching to KDM gnome-panel "went astray" as above.
I returned to GDM and problem was gone. I decided to investigate the problem later, switched again to KDM and worked with KDE where I did a couple of updates. Unfortunately I don't remember what Gnome-related updates I did at the same time. But when I next time started Gnome from KDM the problem was gone. So I don't know what exactly fixed it. Maybe even switching to GDM (enabling it after fresh Gnome install) at least once is already enough. But may be some updates fixed it.
In general I noticed that with GDM enabled Gnome (2.30) starts faster than if use startx.
So the problem may be somehow connected to GDM.

loool
this problem is always there since at least 7.0-RELEASE. I believe this is a problem related to dbus policy because when I login as root, no errors shown. I have already post a mail into gnome@freebsd.org and hope the problem can be solved.;)

[zeiz]

For me it was first time, it's connected with kdm/gdm and finally it's gone.
I guess it appeared just to confirm your PR :)
Seriously please post if they'll reply.

[kenorb]

In my "messages" I see this:
avahi-daemon[967]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
gnome-session[1222]: WARNING: Could not launch application 'at-spi-registryd-wrapper.desktop': Unable to start application:
Failed to execute child process "${exec_prefix}/libexec/at-spi-registryd" (No such file or directory)
gnome-session[1222]: WARNING: Could not launch application 'gnome-power-manager.desktop': Unable to start application:
Failed to execute child process "gnome-power-manager" (No such file or directory)
gnome-keyring-daemon[1255]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
gnome-session[1222]: WARNING: Application 'metacity.desktop' failed to register before timeout
But they feels harmless so I just don't care.
Some applications while run as root may install important files in /root instead of user directory.
Also all "gurus" say that it's very bad practice :)
There is even a thread here about running X as root.

See: http://forums.freebsd.org/showthread.php?t=3542

[arli]

i have same problem, solve by "exec ck-launch-session gnome-session":

echo "exec ck-launch-session gnome-session">~/.xinitrc
startx


and say hello with chinese too... :e

[arli]

detail:

1, mount /proc by procfs
2, make sure
/usr/local/etc/rc.d/dbus
/usr/local/etc/rc.d/hald
is started.

3,exec by ck-launch-session, see above
4,and don't forget put 127.0.0.1 hostname to /etc/hosts, for example:
# cat /etc/hosts

::1 localhost absd-nb absd-nb.f13
127.0.0.1 localhost absd-nb absd-nb.f13

5,try at new user(without ~/.gconfd ~/.gnome2 ...etc)

and here is my PolicyKit.conf for you (don't forage change the username):
# cat /usr/local/etc/PolicyKit/PolicyKit.conf

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
<match user="root">
<return result="yes"/>
</match>
<define_admin_auth group="wheel" />
<match user="arli">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.mount-fixed">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.eject">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.unmount-others">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.power-management.reboot">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.power-management.shutdown">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.power-management.hibernate">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.power-management.suspend">
<return result="yes" />
</match>
</match>
</config>


ps: thank you for DutchDaemon ;)