pidgin: Fatal IO error 10 (No child processes) on X server :0.0.

[Ryan Prior]

Binary package hint: pidgin

Steps to reproduce the problem:
> Launch terminal
> run the command pidgin
> Open an IM window
> Wait about a quarter second

Expected result: graphical IM window
Actual result: is the following text printed to the terminal

pidgin: Fatal IO error 10 (No child processes) on X server :0.0.

[Stuart Langridge (sil)]

Confirm this bug has also just happened to me, running released hardy. I wasn't doing anything with pidgin at all.

[Yang (yaaang)]

This just happened to me, but my pigdin instance was running for much longer (overnight). I'm running Ubuntu 8.04 64-bit and pidgin 2.4.1.

And the program just exits; it doesn't crash (which would be nice for the backtrace):

...
[New Thread 0x415a9950 (LWP 29940)]
[Thread 0x415a9950 (LWP 29940) exited]
[Thread 0x42844950 (LWP 29298) exited]
pidgin: Fatal IO error 10 (No child processes) on X server :0.0.

Program exited with code 01.
(gdb) bt
No stack.

[Sam Hathaway (sam.hathaway)]

Happens to me too. Pidgin will run for many hours, and then disappear with this error message.

Hardy x86 (main, restricted, universe, multiverse) x (hardy, hardy-updates, hardy-security, hardy-proposed)
Pidgin version: 1:2.4.3-0ubuntu1~hardy1

Using ALSA sound output (although I don't think it's related to sound).

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.