how do i capture an error message?

Drone4four · 07-05-2006, 08:53 PM

EDIT: Scroll down to post #4 for the fluxbox error

I messed fluxbox up. I had version 0.9.13 and saw in Pat V's /slackware-current/xap version 1.0RC. I downloaded it and mistakenly entered the command:

Code:

installpkg fluxboxRC.tgz

That was wrong and I didn't realize this at the time. Now when I startx, x.org returns with a lengthy message explaining it can't use some shared library. To capture the exact error message, I tried:

Code:

startx > fluxboxMessage.txt

However when I try to open that file, I see a blank document. So, uh, what's the correct command to capture the error message? Once I've collectedthe entire message, then I can finish troubleshooting fluxbox.

leonscape · 07-05-2006, 08:55 PM

Theres already a log for X its usually in /var/log/ or one of its sub-directories.

Drone4four · 07-05-2006, 09:07 PM

Quote:

Originally Posted by leonscape

Theres already a log for X its usually in /var/log/ or one of its sub-directories.

The fluxbox error includes mention of "libstdc++.so.6". My /var/log/Xorg.0.log does not mention that library. I'd post my entire Xorg log file, but it's too long for a single post, apparently. So is there any other way of recording the 10 or 20 lines I need?

gilead · 07-05-2006, 09:23 PM

If you want to divert standard output and standard error to the one destination, the following will do it:

Code:

startx &> fluxboxMessage.txt

This is the same as

Code:

startx > fluxboxMessage.txt 2>&1

Drone4four · 07-05-2006, 09:51 PM

Quote:

Originally Posted by gilead

If you want to divert standard output and standard error to the one destination, the following will do it:

Code:

startx &> fluxboxMessage.txt

This is the same as

Code:

startx > fluxboxMessage.txt 2>&1

Thanks gilead. Here is the error message when I try to load fluxbox:

Code:

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/314:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.4.31 i686 [ELF] 
Current Operating System: Linux 314 2.4.31 #6 Sun Jun 5 19:04:47 PDT 2005 i686
Build Date: 02 May 2006
	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: Wed Jul  5 22:47:49 2006
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
Warning: Failed to open file(/usr/X11R6/share/fluxbox/nls/en_US/fluxbox.cat)
for translation, using default messages.
/usr/X11R6/bin/fluxbox: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

waiting for X server to shut down

What is this message trying to say?

edit:why exactly won't the topic to this thread not change according to the new title I just gave it?

edit:sp

gilead · 07-05-2006, 10:00 PM

I hope it's as simple as not having the libstdc++.so.6 library installed. I'm running slackware -current and /usr/lib/libstdc++.so.6 was installed from the gcc-g++-3.4.6-i486-1 package. You might also have to run ldconfig after installing the package.

kevkim55 · 07-05-2006, 10:08 PM

Like gilead said, it's either not having libstdc++.so.6 or having a different verion of libstdc++.so

libstdc++.so should be found under /usr/lib. See if you got one.

Drone4four · 07-05-2006, 10:23 PM

Thanks kevkim55 and gilead for your quick replies. It turns out that installing from -current gcc-g++ allows fluxbox to now start perfectly. That means libstdc++.so.6 was just out of date.

I'd like to change the topic of this thread by including "solved" but it won't let me. Why is that?

gilead · 07-05-2006, 10:44 PM

I'm glad it's working properly now

As far as changing the thread topic goes, I think that only the moderators can do that. Modifying the post subject as you already have done looks to be the best way.