PDA

View Full Version : Some Errors using Gnome 2.26


Crestfallen
May 14th, 2009, 15:03
Hello again =)
rc.conf

dbus_enable="YES"
polkitd_enable="YES"
gnome_enable="YES"
sshd_enable="YES"


And errors like this spamming dmesg very often :
May 14 15:49:14 Crestfallen gnome-keyring-daemon[1120]: failed to initialize a HAL context:
May 14 15:49:14 Crestfallen gnome-keyring-daemon[1120]: Scheduling hal init retry

It comes every second (

And also, 1 more issue )

Crestfallen# pkg_info | grep hal
gstreamer-plugins-hal-0.10.14,3 Gstreamer hal plugin
hal-0.5.11_23 Hardware Abstraction Layer for simplifying device access
hal-info-20080508_1 Additional FDI files to further classify HAL devices


But in /var/log/gdm logs i have such a errors:

** (gnome-power-manager:1074): WARNING **: DBUS error: Could not get owner of name 'org.freedesktop.Hal': no such name
** (gnome-power-manager:1074): DEBUG: proxy is NULL, maybe the daemon responsible for org.freedesktop.Hal is not running?

** (gnome-power-manager:1074): WARNING **: Either HAL or DBUS are not working!

** (gnome-power-manager:1074): WARNING **: DBUS error: Could not get owner of name 'org.freedesktop.Hal': no such name
** (gnome-power-manager:1074): DEBUG: proxy is NULL, maybe the daemon responsible for org.freedesktop.Hal is not running?

** (gnome-power-manager:1074): WARNING **: DBUS error: Could not get owner of name 'org.freedesktop.Hal': no such name
** (gnome-power-manager:1074): DEBUG: proxy is NULL, maybe the daemon responsible for org.freedesktop.Hal is not running?

** (gnome-power-manager:1074): WARNING **: proxy failed

** (gnome-power-manager:1074): WARNING **: proxy NULL!!


and at last, Crestfallen# cat /boot/loader.conf
beastie_disable="NO"
loader_logo="beastiebw"
snd_hda_load="YES"
nvidia_load="YES"


Sound works, XMMS playing music, mplayer too, but gnome sound settings says, than no audio device specified. How can I fix this issues?

P.s. Google wasn't helpfull that time (

Sorry my bad english

Crestfallen
May 14th, 2009, 15:04
btw, i forgot a little ))

FreeBSD Crestfallen.InNominee 7.1-RELEASE FreeBSD 7.1-RELEASE #1: Thu May 7 20:51:37 UTC 2009 Thanatos@Crestfallen.InNominee:/usr/src/sys/i386/compile/Thanatos i386

tangram
May 14th, 2009, 15:16
Hello again =)
rc.conf

dbus_enable="YES"
polkitd_enable="YES"
gnome_enable="YES"
sshd_enable="YES"



Try to enable hal in /etc/rc.conf with:

hald_enable="YES"

And have a look at the FreeBSD Gnome project page at http://www.freebsd.org//gnome/index.html.

SirDice
May 14th, 2009, 16:30
Especially have a look at the HAL FAQ that's also there. Gnome_enable should load dbus and hal.

Just by looking at the errors I'm guessing you're missing the proc filesystem. Add to /etc/fstab:

proc /proc procfs rw 0 0

Then mount /proc

LateNiteTV
May 14th, 2009, 23:09
i was actually getting dbus errors with gnome even with gnome_enable in rc.conf until i added the dbus_enable line in rc.conf. after that the errors went away. so i dont know what was going on with gnome_enable.

DrJ
May 15th, 2009, 01:04
Odd. I only use gnome_enable for hal, dbus and the rest of the lot. Sure there are other ones (like cups and apache and so forth) but as far as gnome goes, gnome_enable is it. And it works fine.

FBSDin20Steps
May 15th, 2009, 01:31
Well, if i use Gnome_enable I can't use my keyboard. Yeah i can login but after that...nope.

SirDice
May 15th, 2009, 07:16
Make sure hald is started:

# pgrep -lf hal


If not add hald_enable="YES" to rc.conf.

icer
May 15th, 2009, 10:40
gnome_enable="YES" in rc.conf will start this services:
# /usr/local/etc/rc.d/dbus start
# /usr/local/etc/rc.d/avahi-daemon.sh start
# /usr/local/etc/rc.d/avahi-dnsconfd.sh start
# /usr/local/etc/rc.d/hald start
# /usr/local/etc/rc.d/gdm start
so you don't need enable hald

FBSDin20Steps
May 15th, 2009, 18:21
Tested again with hald, dbus, gnome_enable and gdm_enable and still can't use my keyboard. I've cut and paste the pgrep -lf hal command SirDice gave me but i couldn't use my return key. The only way to change settings is to boot into single user mode.

So I start gnome from the console right now. I have hald and dbus enabled in my rc.conf and everything is working as expected.

Here is a snippet of my logfile.

May 15 17:31:06 fbsdin20steps gdm-simple-greeter[2043]: Gtk-WARNING: Failed to set text from markup due to error parsing markup: Error on line 1: Unfinished entity reference
May 15 17:31:06 fbsdin20steps gdm-simple-greeter[2043]: Gtk-WARNING: Failed to set text from markup due to error parsing markup: Error on line 1: Unfinished entity reference
May 15 17:31:06 fbsdin20steps gdm-simple-greeter[2043]: Gtk-WARNING: Failed to set text from markup due to error parsing markup: Error on line 1: Unfinished entity reference
May 15 17:31:13 fbsdin20steps gnome-keyring-daemon[2064]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
May 15 17:31:25 fbsdin20steps gnome-session[2073]: WARNING: Application 'metacity.desktop' failed to register before timeout
May 15 17:31:32 fbsdin20steps pulseaudio[2139]: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
May 15 17:31:35 fbsdin20steps kernel: WARNING: R/W mount of /media/disk-3 denied. Filesystem is not clean - run fsck
May 15 17:31:35 fbsdin20steps kernel: WARNING: /media/disk-3 was not properly dismounted
May 15 17:31:35 fbsdin20steps kernel: WARNING: /media/disk-1 was not properly dismounted
May 15 17:31:35 fbsdin20steps kernel: WARNING: /media/disk-4 was not properly dismounted
May 15 17:31:35 fbsdin20steps gnome-keyring-daemon[2066]: adding removable location: volume_uuid_A46B_BBE9 at /media/disk
May 15 17:31:37 fbsdin20steps pulseaudio[2169]: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
May 15 17:31:37 fbsdin20steps pulseaudio[2170]: pid.c: Daemon already running.
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps last message repeated 4 times
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps last message repeated 3 times
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps console-kit-daemon[1939]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:35 fbsdin20steps shutdown: reboot by root:
May 15 17:35:41 fbsdin20steps syslogd: exiting on signal 15

DrJ
May 15th, 2009, 22:12
There's a discussion about this topic on the -questions list in which you may be interested. Since I'm not affected I've not read it in detail.

Crestfallen
May 15th, 2009, 22:51
2 SirDice

After adding this to FStab, FreeBSD crashed with kernel panic and GDM refused to work before I removed it...

PhenomII
June 24th, 2010, 05:45
2 SirDice

After adding this to FStab, FreeBSD crashed with kernel panic and GDM refused to work before I removed it...
D'oh!
Did you perhaps forget:
# mkdir -p /proc?
You DID do this BEFORE you entered:
# FileSystem TABulated entries
proc /proc procfs rw 0 0
# Appears you use LINUX ABI
linproc /usr/compat/linux/proc linprocfs rw 0 0
NOTE: you will NOT need to make the directory in the /compat node,
it's made as part of the LINUX ABI install. :)
See FSTAB(5) (https://ultimateDNS.NET/man/?query=fstab) for all the important details.


HTH