Hi all, I have some mysterious things happening. Which means I'm forevera newbie I guess.
In /home/owner/.xessions I get this:
stderr is not a tty - where are you? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>same w/ KDE<<<<<<<<<<<<<<<<<<

and this: (kde & gnome):
** (gnome-volume-manager:3814): WARNING **: manager.c/1534: hal_initialize failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or
directory
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
.xsession-errors lines 1-14/317 5%
---------------------<snip>----------------
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
Initializing nautilus-open-terminal extension
Open Terminal selected
Open Terminal selected

** (nautilus:3812): WARNING **: No description found for mime type "x-special/socket" (file is ".gnome-system-monitor.root"), please tell the gnome-vfs mailing
list.
Open Terminal selected
Open Terminal selected
sys:1: GtkWarning: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
Open Terminal selected
Open Terminal selected
Open Terminal selected
.xsession-errors lines 286-318/318 (END)

Or, sometime I kill something.

Open Terminal selected
Open Terminal selected
Open Terminal selected
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
The application 'gnome-panel' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
gnome-terminal: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
.xsession-errors lines 296-329/329 (END)

Recently upgraded to kernel-2.6.7.17, but I'm not sure that had anything to do w/ this mess

Mostly I just hate to see stuff like that and not have a clue what's happening or where to start to fix it - if it needs fixing. Sendmail definately need fixing. It takes forever to finish booting because of sendmail.

Anybody out there patient enough to look this over and hazard a guess what's happening??

I be forever grateful. Thanks, lynnevan

Not very helpful, but if in doubt, I blame Gnome ;}


Cheers,
Tink

problem kinda looks like it could be hal and d-bus kernal related. maybe not I am not up to snuff anymore on kernal and hal and d-bus.

did you update kde or gnome recently?

which gnome are you using? install from source?freerock?dropline?gware?

updated kernal and problem arose may be kernel related

Well Tinkster is probably right. mrapathy, my slack upgrade from 10.1 to 10.2 was freerock, and I recently got their latest frg release. They make it so easy. And I recently upgraded the kernel from 2.4.39? to 2.6.7.17. I'd like to upgrade kde, but haven't had the patience to see if I've got all the required files yet. The 'terminal' it talks about opening is, I think, the right click terminal option, which always works - actually it shows up twice on the right click menu and one works and the other does nothing.
So maybe if I just get 'one' question answered, that'll lead to solving the others........What does it mean that "stderr is not a tty - where are you?"
I don't really know what 'stderr' is so I don't know if that's something 'hal' would tray to find or not. Is hal in charge of tty's? Actually there's a lot I don't know. What would be a good source for finding out about stderr & tty's?? Thanks in advance for any clues or ideas.

From the man page:


NAME
stdin, stdout, stderr -- standard I/O streams

SYNOPSIS
#include <stdio.h>
extern FILE *stdin;
extern FILE *stdout;
extern FILE *stderr;

DESCRIPTION
Under normal circumstances every Unix program has three streams opened for it when it starts up, one
for input, one for output, and one for printing diagnostic or error messages. These are typically
attached to the user's terminal (see tty(4)) but might instead refer to files or other devices,
depending on what the parent process chose to set up. (See also the ``Redirection'' section of sh(1).)


I seem to recall seeing somewhere that udev or hal or dbus caused an issue with one of these, but I can't seem to remember where I saw it or what it said or if itwas only on slackware, etc. etc.

Maybe it was a dream.