Gnome 2.28 won´t start, Xorg works

I

Icher

Gnome 2.28 won´t start, Xorg works

Hi guys,

I got lot of problems with gnome.I installed FreeBSD 8.0, and Xorg from the ports. It seems to work fine. When I run:
Code: 
startx
I can see the Xterm Window, so my xorg.conf seems to be correct.

Then I installed gnome 2.28 from the ports. When I try to start gnome I get this errors:
Code: 
gdm-binary[1146]: WARNING: GdmDisplay: display lasted 2.806200 seconds
gdm-binary[1146]: WARNING: GdmDisplay: display lasted 2.806963 seconds
gdm-binary[1146]: WARNING: GdmDisplay: display lasted 2.806209 seconds
gdm-binary[1146]: WARNING: GdmDisplay: display lasted 2.805971 seconds
gdm-binary[1146]: WARNING: GdmDisplay: display lasted 2.805806 seconds
gdm-binary[1146]: WARNING: GdmDisplayFactory: maximun number of X display failures reached: check X server log for errors
The Xorg.0.log seems to have no Errors. But Xorg runs so I don't know the problem.
My rc.conf:
Code: 
...
dbus_enable="YES"
hald_enable="YES"
avahi_daemon_enable="YES"
avahi_dnsconfd_enable="YES"
gnome_enable="YES"

Can anybody please tell me what goes wrong here?
 
Have a look at the log files located in /var/log/gdm, especially the one named :0.log, which should contain the output of Xorg when gdm tries to start it. Maybe this can shed some light onto this issue.

Additionally you seem to have some superfluos settings in your /etc/rc.conf. Setting gnome_enable will enable all of dbus_enable, hald_enable, avahi_daemon_enable, avahi_dnsconfd_enable and gdm_enable. So either set gnome_enable, or the individual settings, not both.
 
Ok. I fixed the rc.conf

Here are the last lines of the output from the /var/log/gdm/:0.log
Code: 
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
        965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        Mobile Intel® GM45 Express Chipset,
        Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
(II) Loading /usr/local/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.6.1, module version = 0.1.0
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45 Express Chipset
(--) intel(0): Chipset: "Mobile Intel® GM45 Express Chipset"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xF4400000
(==) intel(0): Using EXA for acceleration
(II) intel(0): 2 display pipes available.
(II) intel(0): Output VGA using monitor section Monitor0
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "LEN", prod id 16435
(==) intel(0): Write-combining range (0xa0000,0x10000) was already clear
(II) intel(0): Resizable framebuffer: not available (1 3)
(II) intel(0): EDID vendor "LEN", prod id 16435
(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS using initial mode 1440x900
 
hm, I see nothing disturbing there. Any lines marked with (WW) or (EE) ? What does the :0-greeter.log say? Do you have procfs mounted on /proc?
 
/var/log/gdm/:0-greater.log:
Code: 
Failed to start message bus: Failed to bind socket "/var/tmp/dbus-5Lg9FYHkuM": Permission denied
EOF in dbus-launch reading address from bus daemon
Hmm this don't looks so good. But how csn I fix this?
 
Icher said:
/var/log/gdm/:0-greater.log:
Code: 
Failed to start message bus: Failed to bind socket "/var/tmp/dbus-5Lg9FYHkuM": Permission denied
EOF in dbus-launch reading address from bus daemon
Hmm this don't looks so good. But how csn I fix this?
Click to expand...
Looks like dbus is having some sort of a problem here.

Please check the following:
  • What permissions are set on your /var/tmp directory? i.e. $ ls -alL /var/tmp. Normally it should have mode 1777 (drwxrwxrwt).
  • Does the file /var/tmp/dbus-5Lg9FYHkuM exist? If so, who is the file owner?
  • How is the filesystem in which your /var/tmp resides mounted? See if # /sbin/mount lists any unusual mount options.
  • Check whether you have the "messagebus" user and group.
 
The permissions from my /var/tmp folder are set to:
-r--r-xr-x

After fixing this everything runs fine.
Thank you for your help.
 
You must log in or register to reply here.
Back
Top