Fatal IO error 11 (Resource temporarily unavailable) on X server

[Lars Volker]

Sometimes in the middle of playing a song, i get the following error and exaile exits:

exaile.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
exaile.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Right after that i'm back to the shell. This happens since updating to lucid (i think, am not sure).

[Johannes Sasongko (sjohannes)]

Nothing we can do from our side; this is a low-level bug somewhere in your system. I'll file this against the distro package, but I recommend asking in the Ubuntu forums because it has higher visibility.

[olek (olekasper)]

Happens for me on debian as well, using exaile 0.3.2.0.

It only happens when I'm playing albums without cover art. I also seems to only happen after a while. E.g., I can play albums without cover art for a while, then it suddenly starts crashing. No abnormal memory use or anything.

After crashing the first time, it will crash again after playing the song for a few seconds.

Might have to do with looking up covers? (I do not use the Amazon plugin, although I did at one point. -- It is not disabled.)

Typical output:

olekasper@gehenna:~$ exaile
** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
INFO : Loading Exaile 0.3.2.0...
INFO : Loading settings...
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
INFO : Loading plugins...
INFO : Attempting to connect to AudioScrobbler (http://post.audioscrobbler.com/)
INFO : Loading collection...
INFO : Logged in successfully to AudioScrobbler (http://post.audioscrobbler.com/)
INFO : Connected to AudioScrobbler
INFO : Loading devices...
INFO : Loading interface...
INFO : Loading main window...
INFO : Connecting main window events...
INFO : Loading panels...
INFO : Connecting panel events...
INFO : Done loading main window...
INFO : Playing file:///home/olekasper/music/example.mp3
exaile.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

[z06gal (z06gal)]

I get the same message using arista-gtk.

* Message: pygobject_register_sinkfunc is deprecated (GtkObject)

[Magnes (magnesus2)]

I get it only with Exaile. After update to Ubuntu 10.10 Exaile (and only Exaile) is unstable like hell. I'll probably switch to Clementine or sth but i like Exaile and will miss it.

[mp (m-p)]

Same here, in Lucid

[Facundo Batista (facundo)]

Still happening in Maverick. Moving this out of "invalid" because it was said that it also happens with Exaile on other systems.

[Facundo Batista (facundo)]

Found *one* problem (may be others). Trying to trace where the problem was, I started Exaile with a tracer:

    python -m trace --trace --trackcalls /usr/lib/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui

Several times, it crashed with the X message we know, but now previously showing:

...
  File "/usr/share/exaile/plugins/lastfmcovers/__init__.py", line 82, in find_covers
    xml = ETree.fromstring(data)
  File "<string>", line 85, in XML
SyntaxError: undefined entity &nbsp;: line 48, column 67

So, I did a try/except in that line, and shown the data which was causing problem, and returned [].

Since I did that, it stopped crashing.

The data that was creating the failure was the web page of the hotel where I'm now, saying I need to renew the internet subscription. So, I had internet (the previous urllib2.urlopen() didn't fail) but the answer was totally bogus.

Why this generated the ugly X message and didn't show the real traceback, don't know.

[snapy (sdfjsfjaei-hans)]

This bug still exists. Why is there no answer to Facundo Batista's message, that seems to fix the bug.

It isn't a low level bug a stated above, because it only happens with exaile!

[Bjorn Madsen (esprit-tordu)]

STill happening on ubuntu in xfce with version .3.2.2. I am updated to latest versions.

[Dustin Spicuzza (dustin-virtualroadside)]

Have you tried the release candidate, 3.3.0?