iB::Topic::Failure to read WM protocols

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » X and Fluxbox » Failure to read WM protocols

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ [1] 2 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Failure to read WM protocols

< Next Oldest | Next Newest >

Alisdair Kelly Offline

Group: Members
Posts: 55
Joined: May 2004

Posted: Nov. 27 2004,19:48

I am having something of a problem with one of my linux boxes. The box in quesiton is a PII-450 with 128 Mb RAM. It has DSL ver 0.73 installed on the hard drive (Knoppix derivative) which has been modified with apt-get. A full version of X-86Free has been installed as well as SAMBA, CUPS, and Firefox. (And I won't tell you about doing the dirty samba with SAMBA. )

The problem is that after around 30 hours of non-use, the X-server fails. When this happens I get the following information/warnings/messages:

Failed to load groupfile
Apps file failure
BScreen::BScreen: managing screen 0 using visual 0x21,depth 16
Warning: failed to read WM protocols (repeated 6 times)
X connection to:0.0 broken
(explicit kill or server shutdown)
Xinit:connection to X server lost

So, it seems that I've screwed up the X server. Any ideas on what I need to do to fix the situation? This is a non-critical box, so I could wipe the installation and start fresh with a Sarge Network install or try one of the other "Debian" liveCD mini-distros. I would rather figure out how to fix existing installation and learn from that though.

--------------
Cheers,
Alisidair

(or you can call me Al)

cbagger01

Group: Members
Posts: 4264
Joined: Oct. 2003

Posted: Nov. 27 2004,21:04

I would not worry about the Bscreen messages or above.

The warning and below are not normal messages.

If you have a full installation of X-Windows, try looking inside your XFree86 log file. It should be stored in /var/log or somewhere inside the /var directory structure.

Alisdair Kelly Offline

Group: Members
Posts: 55
Joined: May 2004

Posted: Nov. 27 2004,22:05

The log indicates that there are multiple xdm errors (pid varies) that are caused by additional instances of xdm (pid 423).

I'll do some looking thru ps -aux and see if I can find the pid 423 and kill it.

I thought that I had a full install of X86, but apparently only have a partial.
Thanks.

--------------
Cheers,
Alisidair

(or you can call me Al)

mikshaw

Group: Members
Posts: 4856
Joined: July 2004

Posted: Nov. 28 2004,01:29

Failed to load groupfile - This means only that the groupfile listed in .fluxbox/init does not exist, but it doesn't cause a problem. Just create the file and you won't get the message.
Apps file failure - I believe this is the same as the groupfile thing.
BScreen::BScreen: managing screen 0 using visual 0x21,depth 16 - This is just information.
Warning: failed to read WM protocols (repeated 6 times) - This is a harmless Fluxbox bug...I used to get it all the time until upgrading to 0.9.10 (or maybe it was 0.9.9). It has something to do with window decorations of terms and dockapps I think.

The other messages are also normal, though the source is impossible to tell from the generic message....it could have been caused by an intentional close of X, or it could have been a crash.

--------------
http://www.tldp.org/LDP/intro-linux/html/index.html

Alisdair Kelly Offline

Group: Members
Posts: 55
Joined: May 2004

Posted: Nov. 28 2004,11:31

Thanks Mikshaw.

I took a look at active processes last night and could not find anything going on that might have been the culprit. I'll edit the
.fluxbox/init later to add the groupfile. I've printed out the docs from the fluxbox site, but haven't finished reading thru them yet.

The X connection failure is a crash of some sort. When it occurs, you have to re-start X (startx) whether operating as a usr or root. I'm just about convinced that I'd probably be smart to wipe the installation clean and re-install with a more recent version of DSL. However, the mixture of stable and testing Debian applications/services may be part of the problem.

I spotted a tag line in one of the linux newsgroups to the effect that "Screwing up" is a euphemism for "learning curve" <BEG>

--------------
Cheers,
Alisidair

(or you can call me Al)

9 replies since Nov. 27 2004,19:48

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ [1] 2 >/

Damn Small Linux Board » Damn Small Linux » X and Fluxbox » Failure to read WM protocols