Confirmed. I've just been hit by this myself (on Intrepid).
It took about half an hour to work out that it was gnome-open, because
neither top, nor htop, nor gnome-system-monitor were any use at all.
All three showed 100% total CPU usage, but none showed what was using
it: adding up the CPU totals for all processes usually came to about
10%. gnome-open, on recausing the problem and checking now, was right
at the bottom, shown using up no CPU whatsoever.
I only finally worked out that it was gnome-open using atop: using the
'c' (show command line) option showed a large number of "<gnome-open>"
lines. The brackets indicate that the process "finished during the last
interval" apparently: it was restarting itself over and over, but only
one copy was ever running at one time; hence why top and htop only
showed one.
So how did this happen? At some point, I think I set Opera to display
shell scripts with "gnome-open", in the belief that this would just
cause it to open them with Gnome's default handler (which at the time
was gedit). Apparently that must have caused gnome-open to be set as
the default file handler for scripts.
** Changed in: libgnome (Ubuntu)
Status: New => Confirmed
--
gnome-open keeps re-running itself if set as default opening application
https://bugs.launchpad.net/bugs/341389
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
