pkg/47014: Gnome black screen on DragonFly x86_64 but okay on NetBSD

[davshao%gmail.com@localhost]

>Number:         47014
>Category:       pkg
>Synopsis:       Gnome black screen on DragonFly x86_64 but okay on NetBSD
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 27 23:05:01 +0000 2012
>Originator:     David Shao
>Release:        DragonFly 3.1-DEVEL  x86_64
>Organization:
>Environment:
DragonFly 3.1-DEVEL  x86_64
>Description:
On a Intel-based Shuttle SG45H7, ICH10, Radeon HD4550 graphics card, full 
meta-pkgs/gnome builds successfully both for DragonFly 3.1-DEVEL x86_64 and 
NetBSD 6.99.11 amd64.  However Gnome run using startx with .xinitrc consisting 
of the line
exec /usr/pkg/bin/gnome-session
launches into a satisfactory desktop only on NetBSD, whereas on DragonFly the 
screen simply remains black.

Launching using ssh from another machine, on NetBSD the normal output, after 
detection of the video card, reads:


GNOME_KEYRING_CONTROL=/var/tmp/keyring-Pj2jq3
GNOME_KEYRING_PID=461
GNOME_KEYRING_CONTROL=/var/tmp/keyring-Pj2jq3
GNOME_KEYRING_CONTROL=/var/tmp/keyring-Pj2jq3
GPG_AGENT_INFO=/var/tmp/keyring-Pj2jq3/gpg:0:1
SSH_AUTH_SOCK=/var/tmp/keyring-Pj2jq3/ssh
GNOME_KEYRING_CONTROL=/var/tmp/keyring-Pj2jq3
GPG_AGENT_INFO=/var/tmp/keyring-Pj2jq3/gpg:0:1
SSH_AUTH_SOCK=/var/tmp/keyring-Pj2jq3/ssh
GPG_AGENT_INFO=/var/tmp/keyring-Pj2jq3/gpg:0:1
Dac detection success
Dac detection success
Dac detection success
Dac detection success

Whereas on DragonFly one never sees the "Dac detection success" lines; instead 
getting output such as:

GConf Error: Failed to contact configuration server; the most common cause is a 
missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)
GConf Error: Failed to contact configuration server; the most common cause is a 
missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)
gnome-session[888]: WARNING: Error retrieving configuration key 
'/desktop/gnome/session/idle_delay': Failed to contact configuration server; 
the most common cause is a missing or misconfigured D-Bus session bus daemon. 
See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to 
get connection to session: Unexpected lack of content trying to read a line)
GConf Error: Failed to contact configuration server; the most common cause is a 
missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)
gnome-session[888]: WARNING: Unable to determine session: Unable to lookup 
session information for process '888'
...
gnome-session[888]: WARNING: No required applications specified
...
GConf Error: Failed to contact configuration server; the most common cause is a 
missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)
GNOME_KEYRING_CONTROL=/tmp/keyring-FY8x4q
GNOME_KEYRING_PID=896
...
GNOME_KEYRING_CONTROL=/tmp/keyring-FY8x4q
GPG_AGENT_INFO=/tmp/keyring-FY8x4q/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-FY8x4q
GPG_AGENT_INFO=/tmp/keyring-FY8x4q/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-FY8x4q/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-FY8x4q
GPG_AGENT_INFO=/tmp/keyring-FY8x4q/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-FY8x4q/ssh
GConf Error: Failed to contact configuration server; the most common cause is a 
missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Error sending data: Broken pipe)
...
** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/idle_activation_enabled': Failed to contact 
configuration server; the most common cause is a missing or misconfigured D-Bus 
session bus daemon. See http://projects.gnome.org/gconf/ for information. 
(Details -  1: Failed to get connection to session: Unexpected lack of content 
trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/lock_enabled': Failed to contact configuration server; 
the most common cause is a missing or misconfigured D-Bus session bus daemon. 
See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to 
get connection to session: Unexpected lack of content trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/desktop/gnome/lockdown/disable_lock_screen': Failed to contact configuration 
server; the most common cause is a missing or misconfigured D-Bus session bus 
daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: 
Failed to get connection to session: Unexpected lack of content trying to read 
a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/desktop/gnome/lockdown/disable_user_switching': Failed to contact 
configuration server; the most common cause is a missing or misconfigured D-Bus 
session bus daemon. See http://projects.gnome.org/gconf/ for information. 
(Details -  1: Failed to get connection to session: Unexpected lack of content 
trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/desktop/gnome/session/idle_delay': Failed to contact configuration server; 
the most common cause is a missing or misconfigured D-Bus session bus daemon. 
See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to 
get connection to session: Unexpected lack of content trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/power_management_delay': Failed to contact 
configuration server; the most common cause is a missing or misconfigured D-Bus 
session bus daemon. See http://projects.gnome.org/gconf/ for information. 
(Details -  1: Failed to get connection to session: Unexpected lack of content 
trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/lock_delay': Failed to contact configuration server; 
the most common cause is a missing or misconfigured D-Bus session bus daemon. 
See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to 
get connection to session: Unexpected lack of content trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/cycle_delay': Failed to contact configuration server; 
the most common cause is a missing or misconfigured D-Bus session bus daemon. 
See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to 
get connection to session: Unexpected lack of content trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/mode': Failed to contact configuration server; the 
most common cause is a missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)

** (gnome-screensaver:905): WARNING **: Error retrieving configuration key 
'/apps/gnome-screensaver/themes': Failed to contact configuration server; the 
most common cause is a missing or misconfigured D-Bus session bus daemon. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Unexpected lack of content trying to read a line)
...
>How-To-Repeat:
Install meta-pkgs/gnome on DragonFly
>Fix: