[SOLVED]Errors? on startx

Question

I normally do my login at tty and then issue the startx command. When I hit Ctrl + Alt + F1 to see the vc/1, it has a bunch of things listed
xauth : creating new authority file /home/inxsible/.serverauth.xxxx
X.Ord X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.25-ARCH i686
Current Operating System: Linux arch 2.6.25-ARCH #1 SMP PREEMPT Sat Jun 14 18:07:19 CEST 2008 i686
Build Date: 21 June 2008 05:47:59PM
Before reporting problems, check http:wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Fri Jul 4 11:29:05 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ramdac" already built-in
Could not init font path element /usr/share/fonts/Type1, removing from list!
which: no hsetroot in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core:/opt/qt/bin)
which: no esetroot in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core:/opt/qt/bin)
which: no gnome-settings-daemon in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core:/opt/qt/bin)
which: no xfce-mcs-manager in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core:/opt/qt/bin)
which: no start_kdeinit in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core:/opt/qt/bin)
I am concerned about the last few lines. I know I haven't installed any of the gnome, kde or xfce and not even hsetroot and esetroot. Where is this info getting pulled from? Do I have to be worried and how do I get rid of it?
Also what about the font path element thing?
Also when I start conky, I see that some of the output is displayed on vc/1. I never saw that on any other distro...maybe I should check again in Debian if that happens....
Conky forked to background, pid is 2610
Conky: desktop window (c1) is root window
Conky: window type - override
Conky: drawing to created window (a00001)
Conky: drawing to double buffer
Last edited by Inxsible (2008-07-07 18:02:19)

Answer 1

ghostHack wrote:The conky output is normal, if you start a conky instance from a terminal you will see that output, its harmless.
Correct, but why use tty for it?
ghosthack wrote:
The
# Run the system-wide support stuff
. $GLOBALAUTOSTART
in your local autostart file makes openbox read the system-wide settings first (/etc/xdg/openbox/autostart.sh).  The 'errors' you see come from the following peice of code
# Set a background color
BG=""
if which hsetroot >/dev/null; then
BG=hsetroot
else
if which esetroot >/dev/null; then
BG=esetroot
else
if which xsetroot >/dev/null; then
BG=xsetroot
fi
fi
fi
test -z $BG || $BG -solid "#303030"
# D-bus
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
# Make GTK apps look and behave how they were set up in the gnome config tools
if test -x /usr/libexec/gnome-settings-daemon >/dev/null; then
/usr/libexec/gnome-settings-daemon &
elif which gnome-settings-daemon >/dev/null; then
gnome-settings-daemon &
# Make GTK apps look and behave how they were set up in the XFCE config tools
elif which xfce-mcs-manager >/dev/null; then
xfce-mcs-manager n &
fi
# Preload stuff for KDE apps
if which start_kdeinit >/dev/null; then
LD_BIND_NOW=true start_kdeinit --new-startup +kcminit_startup &
fi
It's basically looking for different ways to set the background and for any service daemons to be started.  The messages you see are just the normal output to STDERR from which/test if you want to get rid of them you coud remove the $GLOBALAUTOSTART line.
I kept the globalautostart line, because I was not sure what else was in the global and I didn't want anything to NOT start. But will try that out now
ghosthack wrote:EDIT: just spoted this line "And those errors are not the only ones, I even get some when I start pcmanfm, something about not being able to connect to hal, even though I have hal installed and running on startup under rc.xml".  HAL should be started as a system daemon in rc.conf, not in openbox's rc.xml (was that a typo? if so check what groups your user is a member of)
Whoops !! my bad. Yes that was a typo.  I did mean that I started hal in rc.conf. The rc's in both Arch and Openbox got me confused.