I've run into a rare, intermittant crashing problem with Gajim recently. Gajim would crash, rarely and seemingly at random on *receipt* of a message, reporting a generic python crash in desktop notifications. I think I'm homing in on the problem, running it in a terminal with -v offered little except:

GLib-ERROR **: Creating pipes for GWakeup: Too many open files

After some google-fu, I began watching Gajim with:

watch -n 0.5 "ls /proc/<gajim pid>/fd | wc -l"

and the error message looks to be spot on. Every time I receive a message Gajim will open 4 files and never close them. This is not the case when sending a message. So, if I receive too many messages (woe is me), it will open too many files and it will crash. I'm not sure when this started, maybe the previous update or the one before, I rarely have Gajim on more than a few hours at a time, so I haven't run into this crash more than a handful of times.

I don't think it's particular to my setup, I'm not using any strange plugins, just a box-standard Gajim installation interacting with a box-standard Prosody server.

Let me know if I can debug it more usefully (and tell me how).

Cheers,
AR

I've narrowed this down further, the increase in open files does not happen after receiving any old message, but "urn:xmpp:carbons:2" messages when clients other than gajim are messaging, using the same account and gajim is getting copies of those messages.