Comment 33 for bug 1282542

Revision history for this message
tallien (tallien) wrote : Re: (synaptic:3405): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed

From Synaptic, when installing Bluefish after upgrading from 13.10 to 14.04:

(synaptic:5163): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed
(Reading database [...] files and directories currently installed.)
Preparing to unpack .../bluefish-data_2.2.5-1_all.deb ...
Unpacking bluefish-data (2.2.5-1) over (2.2.5-1) ...
Preparing to unpack .../bluefish_2.2.5-1_i386.deb ...
Unpacking bluefish (2.2.5-1) over (2.2.5-1) ...
Preparing to unpack .../bluefish-plugins_2.2.5-1_i386.deb ...
Unpacking bluefish-plugins (2.2.5-1) over (2.2.5-1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for mime-support (3.54ubuntu1) ...
Processing triggers for menu (2.1.46ubuntu1) ...
Setting up bluefish-data (2.2.5-1) ...
Setting up bluefish-plugins (2.2.5-1) ...
Setting up bluefish (2.2.5-1) ...
Processing triggers for menu (2.1.46ubuntu1) ...

After this, trying to run Bluefish produced the GLib-ERROR message I mentioned above. It was working fine before on 13.10.