Console log filled with Window manager warning.

[edthome@…]

Below is the beginning of the third time of having a 12 GB console.log file. This time I was able to catch the file early enough to be able to exract enough information to say that it likely comes from starting Gnome. It does not happen every time, and so far I have not figured out what triggers it. I am sorry that I have not isolated a trigger. There will eventually be billions and billions of lines of

---

Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor. Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor.

---

I always keep things up-to-date, so I am running OS X 10.4.6 and Gnome just came up saying 2.14 (and DP 1.2.1. It is not doing it this time.

XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) 2006-04-10 13:57:04.129 X11[20557] Can't open input server /Users/leibnitz/Library/InputManagers/Smart Cras h Reports _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root [DRI] screen 0 installation complete Screen 0 added: 1152x864 @ (0,0) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! D-BUS per-session daemon address is: unix:path=/tmp/dbus-B5pf62iKdY,guid=443aaa86e2b7e1e00da6ca3f10ad6100 Window manager warning: Log level 32: could not find XKB extension. _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root SESSION_MANAGER=local/lebesgue.msunet2k.edu:/tmp/.ICE-unix/20558 esd: Esound sound daemon already running or stale UNIX socket /tmp/.esd/socket This socket already exists indicating esd is already running. Exiting... using device Built-in Audio for output:

with sample rate 44100.000000, 2 channels and 32-bit sample

using device Built-in Audio for input:

with sample rate 44100.000000, 2 channels and 32-bit sample

(gnome-panel:20602): WARNING : Failed to add file monitor for ​file:///Users/leibnitz/.gtk-bookmarks: U nsupported operation

Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor. Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor. Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor. Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor. . . .

[edthome@…]

From the submitter:

I thought I should mention that it does not happen on my home computer, so it is could be something localized with my computer. fsck shows nothing wrong with the drive, but suppose it has some bad sectors?

[edthome@…]

I am fully up-to-date on April 19th, 2006 and just this morning this same thing happened on my home computer as well. I got a 21 MB console.log file all in less than 10 minutes (perhaps far less, I'm just not sure). I had just started Gnome and all ll I had used so far were the Terminal and the Calculator. The Terminal came up from a saved state from last time, and the Calculator was called from the Applications Menu. There were 264,729 lines of that same error (according to TextWrangler) in that time. The last several were: _ Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor.

Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor.

Window manager warning: Quitting XDarwin...

Log level 16: poll(2) failed due to: Bad file descriptor.

Window manager warning: Log level 16: poll(2) failed due to: Bad file descriptor.

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.

_

...I had just logged out of Gnome a few minutes earlier to try to stop the entries. There were actually 529459 lines, but every other one was blank.

[rhwood@…]

What window manager are you using?

[edthome@…]

(In reply to comment #3)

What window manager are you using?

I use metacity, because the virtual desktops Workspace Switcher on the panel does not work with Apple's quartzwm.

I was thinking that my .xinitrc was what was suggested on the page: ​http://wiki.opendarwin.org/index.php/DarwinPorts:GNOME but now I see there is some difference. Perhaps the problem was that I was using dbus with metacity rather than with quartzwm.

I'm going to try metacity without dbus and see if the problem repeats.

Here is the tail end of the .xinitrc file, which I was using at the time: ## make sure X11 is DarwinPorts and /usr/local aware PATH=$PATH:/usr/local/bin:/opt/local/bin export PATH

## make the freedesktop menu entries work export XDG_DATA_DIRS=/opt/local/share export XDG_DATA_HOME=/opt/local/share export XDG_CONFIG_DIRS=/opt/local/etc/xdg

. /sw/bin/init.sh

## test for an existing bus daemon, just to be safe if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then

## if not found, launch a new one eval dbus-launch --sh-syntax --exit-with-session echo "D-BUS per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"

fi

## start GNOME exec /opt/local/bin/metacity & # exec /opt/local/bin/gnome-session exec dbus-launch gnome-session

[rhwood@…]

If you are using metacity, try letting gnome-session launch it. gnome-session will launch metacity as part of its own startup routine if another window manager is not running.

I think.

[edthome@…]

(In reply to comment #5)

If you are using metacity, try letting gnome-session launch it. gnome-session will launch metacity as part of its own startup routine if another window manager is not running.

On one computer this works (and on this computer I get a warning of a second wm running if I try to start metacity myself) and on another it does not.

I don't know if this is related, but when I posted this at macosxhints, someone replied that a google on "poll(2) failed due to: Bad file descriptor." led to a number of glib and glib2 errors. A google on the error together with 'Window manager warning" led to just one hit which did not really discuss it. Here is a link to one of those discussions concerning glib and glib2.

​http://comments.gmane.org/gmane.os.apple.fink.gnome/1193

[markd@…]

Is this still a problem with current versions?

[markd@…]

No response. Closing.