[SOLVED] Segmentation faults during upgrade from 13.1 to 13.37

dimm0k · 05-01-2011, 06:24 PM

Just finished the upgrade from 13.1 to 13.37 using the script mentioned in the docs to "upgradepkg --install-new" through all of the directories except kdei. When I initiated the script, I redirected the output as follows:

upgrade.sh > install.log

Doing so outputted some messages to the console about segmentation faults, but after checking the install.log I did not find any problems. The outputted messages were similar throughout and were as follows:

Code:

install/doinst.sh: line 25: 1521 Segmentation fault  usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 25: 2243 Segmentation fault  usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 8: 7211 Segmentation fault  /usr/bin/update-mime-database /usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 8: 7917 Segmentation fault  /usr/bin/update-mime-database /usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 4: 32335 Segmentation fault  /usr/bin/update-mime-database ./usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 4: 32577 Segmentation fault  /usr/bin/update-mime-database ./usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 8: 9589 Segmentation fault  /usr/bin/update-mime-database ./usr/share/mime >/dev/null 2>&1
install/doinst.sh: line 8: 9829 Segmentation fault  /usr/bin/update-mime-database ./usr/share/mime >/dev/null 2>&1

Is this anything to worry about?

dive · 05-01-2011, 07:15 PM

I wouldn't check if it still segfaults when you run it manually. It could be a sign of a corrupt package or binary.

Try grabbing a fresh shared-mime-info package from a mirror and see if it fixes it.

That app isn't system critical but you do want the mime database updated from time to time. Normally it runs at boot in rc.M

dimm0k · 05-01-2011, 07:49 PM

Thank you for the fast response! Perhaps the upgrade process attempted to use the mime package from 13.1 before it was upgraded to 13.37. Re-running that command as listed in the messages produced no errors this time around.