5.1-RELEASE / gnome-2.4 / too many files open

Mark Hannon markhannon at optusnet.com.au
Fri Sep 26 05:01:56 PDT 2003


Hi,

I just (more or less accidently) upgrade to Gnome-2.4 on a 5.1-RELEASE
box which was previously
running Gnome-2.2.  A check of portversion shows that all packages are
at their latests versions however
I am unable to use gnome ...

The desktop starts, I can open nautilus, but when I try to open a
sub-directory the system bogs down
and eventually I get a message saying 'too many open files'.  At this
point the system is unusable, it
is not possible to start a new command, login from another terminal etc.
Killing XFree makes things
usable again.

My xsession-errors files includes:

SESSION_MANAGER=local/tbird.home.lan:/tmp/.ICE-unix/26687
Window manager warning: Broken client! Window 0x600010 (xconsole)
changed client leader window or SM client ID
mapping method init - connect2: Connection refused

(nautilus:26724): libgnomevfs-WARNING **: module
'/usr/X11R6/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL
handle
Unable to open desktop file eek-004935fc89.desktop for panel launcher:
Error reading file
'file:///home/mark/.gnome2/panel2.d/default/launchers/eek-004935fc89.des
ktop': File not found
Unable to open desktop file greasy-00a317c073.desktop for panel
launcher: Error reading file
'file:///home/mark/.gnome2/panel2.d/default/launchers/greasy-00a317c073.
desktop': File not found
yp_next: clnt_call: RPC: Unable to send; errno = Too many open files in
system

<snip ... 27 megabytes more of the same message>

yp_next: clnt_call: RPC: Unable to send; errno = Too many open files in
system
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.
ICE default IO error handler doing an exit(), pid = 26694, errno = 0
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.

What can I try next in order to debug further?

Regards/Mark


More information about the freebsd-gnome mailing list