reismith
August 13th, 2014, 12:50 PM
I have been experiencing a reoccurring problem starting up GIMP first under Ubuntu 12.04 and now under 14.04.1. If I attempt to execute from the icon, it simply fails to startup; no windows appear, no error messages. If I attempt a startup in the Terminal screen, I do see the startup screen, the Tip of the Day, and the tools window but get the following error message in the Terminal window:
/usr/local/lib/gimp/2.0/plug-ins/print: error while loading shared libraries: libgimpprint.so.1: cannot open shared object file: No such file or directory
(gimp:17391): LibGimpBase-WARNING **: gimp: wire_read(): error
/usr/local/lib/gimp/2.0/plug-ins/helpbrowser: error while loading shared libraries: libgtkhtml-2.so.0: cannot open shared object file: No such file or directory
(gimp:17391): LibGimpBase-WARNING **: gimp: wire_read(): error
The application fails to fully open (no edit window).
I've tried uninstalling and reinstalling but it changes nothing. When I updated to 14.04.1, I did not have GIMP installed in 12.04 and reinstalled fresh in 14.04 but got the same result. Is what seems to be missing/corrupted part of the Linux kernel? I've been updating that all along as well. No other app is exhibiting a similar issue. Any idea how I can fix this?
/usr/local/lib/gimp/2.0/plug-ins/print: error while loading shared libraries: libgimpprint.so.1: cannot open shared object file: No such file or directory
(gimp:17391): LibGimpBase-WARNING **: gimp: wire_read(): error
/usr/local/lib/gimp/2.0/plug-ins/helpbrowser: error while loading shared libraries: libgtkhtml-2.so.0: cannot open shared object file: No such file or directory
(gimp:17391): LibGimpBase-WARNING **: gimp: wire_read(): error
The application fails to fully open (no edit window).
I've tried uninstalling and reinstalling but it changes nothing. When I updated to 14.04.1, I did not have GIMP installed in 12.04 and reinstalled fresh in 14.04 but got the same result. Is what seems to be missing/corrupted part of the Linux kernel? I've been updating that all along as well. No other app is exhibiting a similar issue. Any idea how I can fix this?