NetBSD Problem Report #47014

From www@NetBSD.org  Thu Sep 27 23:01:00 2012
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 9D44463E490
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 27 Sep 2012 23:01:00 +0000 (UTC)
Message-Id: <20120927230059.6EDB163B907@www.NetBSD.org>
Date: Thu, 27 Sep 2012 23:00:59 +0000 (UTC)
From: davshao@gmail.com
Reply-To: davshao@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Gnome black screen on DragonFly x86_64 but okay on NetBSD
X-Send-Pr-Version: www-1.0

>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:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 27 23:05:01 +0000 2012
>Closed-Date:    Mon Dec 07 21:44:18 +0000 2020
>Last-Modified:  Mon Dec 07 21:44:18 +0000 2020
>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:

>Release-Note:

>Audit-Trail:
From: David Shao <davshao@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/47014: Gnome black screen on DragonFly x86_64 but okay on NetBSD
Date: Fri, 28 Sep 2012 12:16:45 -0700

 Much of dbus 1.6.4nb1 functionality may be broken on DragonFly
 3.1-DEVEL x86_64.  From what I began to notice yesterday, launching
 Firefox from kde4, there is a warning box:

 "An error occurred while loading or saving configuration information
 for xulrunner. Some of your configuration settings may not work
 properly."

 with Details:

 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)
 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)
 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)
 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)

State-Changed-From-To: open->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Mon, 07 Dec 2020 21:44:18 +0000
State-Changed-Why:
stale bug report: refers to GNOME2 which has seen been removed.


>Unformatted:

Home	PR Database Search