gconf creates fork bomb using libproxy

Bug #781319 reported by Коренберг Марк
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gconf

I have maverick updated to last version.
Next I decide to update to Natty.

Upgrade process have been done with errors. I have found fork-bomb in system and what I done:
chmod a-x /usr/bin/gconftool-2

next upgrade continue, and after some amount of dpkg --configure -a the upgrade process have been done.

But when I enable execute_bits, fork bomb appear. Why?
gconf -> gio -> libgiolibproxy -> libproxy0.so -> config_gnome.so -> popen("gconf ...") -> sh -> gconf -> gio -> ...

See attached files: output of 'pstree -upal', gdb bt on process that begin that chain (it may be different process, but first items in stack are the same).

When I remove /usr/lib/libproxy/0.3.1/modules/config_gnome.so, fork bomb disappear.

What the hell ?!
problem is easily reproductible on my computer ( by recovering /usr/lib/libproxy/0.3.1/modules/config_gnome.so)

Revision history for this message
Коренберг Марк (socketpair) wrote :
description: updated
description: updated
Revision history for this message
Коренберг Марк (socketpair) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.