Comment 130 for bug 36581

> Can people try 0.0.19
Updated. Now testing.

I noticed that the /usr/libexec/gam_server process is *not* killed
upon exit from my (KDE) graphical session. In other words, logging
in/out repeatidly ends up using the very same process through
different graphical sessions. Shouldn't _all_ user processes started
with a graphical session be killed upon exit ?

I will compile glib with
 --disable-mem-pools --enable-gc-friendly
in the next few days with KDE-3.3.2.

> Hummm ... If you recompile stuff by yourself, this may raise
problems
> that others using the pristine distro will not get.
Beside the fact that "pristine" distro users _are_ getting it, this
is _good_ as you noticed because non-standard build may help
find/troubleshoot more bugs.

And since you mention the word "pristine", let me tell you that if
Redhat/Fedora's implementation of KDE were indeed pristine and not so
crippled (i.e downgraded menus/apps/configs resulting in a poor man's
common denominator with Gnome, inheriting in the process some of its
_bad_ user-interface-guidelines like the infamous
double-click-by-default), you would have more users running your
distro. Many KDE users have gone away from Redhat at the time
Bluecurve and the bright "unified-desktop" idea came out. Since I
always compile KDE from sources, it does not affect me that much but
I am a somewhat rare case of KDE enthusiast on Fedora.

Last nut not least, did you consider using the C++ STL to replace
glib in gamin ?

Cheers,

Philippe