Often when I run eog, it opens a window, then hangs when trying to actually show an image. I also get several "atk-bridge-WARNING **: failure: no device event controller found."
stracing the hung process shows it waiting for a futex(...) call.
I see from Jeremy's debugging above that he has atk (assistive technologies) enabled, or mono enables it by default.
Since I disabled atk, I no longer get the atk-bridge messages, and eog no longer lock up when I start it.
(Sometimes, gimp would lock up for me on startup too, so have to see if this fixes it).
If you have atk enabled (System -> Preferences -> Assistive Technologies), you can disable in on a per-terminal shell basis by unsetting the GTK_MODULES environment variable.
Perhaps this is the same cause of f-spot's problem.
Often when I run eog, it opens a window, then hangs when trying to actually show an image. I also get several "atk-bridge-WARNING **: failure: no device event controller found."
stracing the hung process shows it waiting for a futex(...) call.
I see from Jeremy's debugging above that he has atk (assistive technologies) enabled, or mono enables it by default.
Since I disabled atk, I no longer get the atk-bridge messages, and eog no longer lock up when I start it.
(Sometimes, gimp would lock up for me on startup too, so have to see if this fixes it).
If you have atk enabled (System -> Preferences -> Assistive Technologies), you can disable in on a per-terminal shell basis by unsetting the GTK_MODULES environment variable.
Perhaps this is the same cause of f-spot's problem.