Hi, thanks for the reply Suraj.
> This error is caused by an incomplete status bar definition: there a > status bar applet defined in your config which lacks a "label" > subsection. I looked into my config file and found the following status bar applets: But why should a applet fail that late? I mean, it seems to work all the time except such situations. >> So I guess Sunakus ruby wmiirc is the problem? > > I don't think so :) wmiirc crashes generally do not cause wmii to > crash. It is a serious matter if the entire WM crashes, leaving you > at a virtual terminal. Well, ok :-). I am not exactly left on a virtual terminal. More I am thrown to gdm - the login screen. But I guess there is not much difference in this case. > I would recommend that you enable core dumps (ulimit -c unlimited), > run wmii, cause the crash to occur, and send a GDB backtrace to this > mailing list: > > gdb `which wmii` your_core_dump_file > bt full Thanks for the tip. If I have done it correctly I get no core file generated. To enable core dumps I executed "ulimit -c unlimited" and instead of starting "wmii" after login, I started the above gdb line. Unfortunately without success, did I do something wrong? But what I got is more log entries from "~/.wmii-hg/wmiirc.log": E, [2010-02-17T02:08:29.687682 #31728] ERROR -- : Broken pipe (Errno::EPIPE) /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:115:in `write' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:115:in `<<' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:115:in `send' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:164:in `talk' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:472:in `clunk' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:260:in `close' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/ixp/transport.rb:217:in `open' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/fs.rb:87:in `open' /home/tom/.gem/ruby/1.8/gems/rumai-3.2.0/lib/rumai/fs.rb:103:in `each_line' I have no idea if I overlooked those entries before or if they just appeared. Regards, Tom