Error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
8
down vote

favorite
2












After update with pacman -Syuq:




# pacman -Sc



pacman: error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory




# find / -name libicuuc.so.* 2>/dev/null
/usr/lib/libicuuc.so.60.1
/usr/lib/libicuuc.so.60


Arch Linux in a Pi version 1:



# uname -an
4.9.62-1-ARCH #1 SMP Fri Nov 17 13:42:55 UTC 2017 armv6l GNU/Linux






share|improve this question






















  • Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
    – zakrapovic
    Nov 28 '17 at 15:54











  • Also missing libicui18n.so.59 probably related
    – zakrapovic
    Nov 28 '17 at 16:00










  • I actually solved my problem with pacman -Sc followed by pacman -Syuu
    – zakrapovic
    Nov 28 '17 at 16:05














up vote
8
down vote

favorite
2












After update with pacman -Syuq:




# pacman -Sc



pacman: error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory




# find / -name libicuuc.so.* 2>/dev/null
/usr/lib/libicuuc.so.60.1
/usr/lib/libicuuc.so.60


Arch Linux in a Pi version 1:



# uname -an
4.9.62-1-ARCH #1 SMP Fri Nov 17 13:42:55 UTC 2017 armv6l GNU/Linux






share|improve this question






















  • Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
    – zakrapovic
    Nov 28 '17 at 15:54











  • Also missing libicui18n.so.59 probably related
    – zakrapovic
    Nov 28 '17 at 16:00










  • I actually solved my problem with pacman -Sc followed by pacman -Syuu
    – zakrapovic
    Nov 28 '17 at 16:05












up vote
8
down vote

favorite
2









up vote
8
down vote

favorite
2






2





After update with pacman -Syuq:




# pacman -Sc



pacman: error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory




# find / -name libicuuc.so.* 2>/dev/null
/usr/lib/libicuuc.so.60.1
/usr/lib/libicuuc.so.60


Arch Linux in a Pi version 1:



# uname -an
4.9.62-1-ARCH #1 SMP Fri Nov 17 13:42:55 UTC 2017 armv6l GNU/Linux






share|improve this question














After update with pacman -Syuq:




# pacman -Sc



pacman: error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory




# find / -name libicuuc.so.* 2>/dev/null
/usr/lib/libicuuc.so.60.1
/usr/lib/libicuuc.so.60


Arch Linux in a Pi version 1:



# uname -an
4.9.62-1-ARCH #1 SMP Fri Nov 17 13:42:55 UTC 2017 armv6l GNU/Linux








share|improve this question













share|improve this question




share|improve this question








edited Dec 3 '17 at 13:33









Jeff Schaller

32.1k849109




32.1k849109










asked Nov 28 '17 at 11:19









frustratedMartian

51114




51114











  • Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
    – zakrapovic
    Nov 28 '17 at 15:54











  • Also missing libicui18n.so.59 probably related
    – zakrapovic
    Nov 28 '17 at 16:00










  • I actually solved my problem with pacman -Sc followed by pacman -Syuu
    – zakrapovic
    Nov 28 '17 at 16:05
















  • Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
    – zakrapovic
    Nov 28 '17 at 15:54











  • Also missing libicui18n.so.59 probably related
    – zakrapovic
    Nov 28 '17 at 16:00










  • I actually solved my problem with pacman -Sc followed by pacman -Syuu
    – zakrapovic
    Nov 28 '17 at 16:05















Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
– zakrapovic
Nov 28 '17 at 15:54





Same problem here, appeared today. For me libicuuc.so.59. I have to go through command line to boot and many programs do not work anymore
– zakrapovic
Nov 28 '17 at 15:54













Also missing libicui18n.so.59 probably related
– zakrapovic
Nov 28 '17 at 16:00




Also missing libicui18n.so.59 probably related
– zakrapovic
Nov 28 '17 at 16:00












I actually solved my problem with pacman -Sc followed by pacman -Syuu
– zakrapovic
Nov 28 '17 at 16:05




I actually solved my problem with pacman -Sc followed by pacman -Syuu
– zakrapovic
Nov 28 '17 at 16:05










5 Answers
5






active

oldest

votes

















up vote
17
down vote













Previously proposed solutions were not relevant or did not work for me. For some reason upgrading the icu package from 59.1-2 to 60.1-1 made linkage break and many programs (including pacman) failed with this error after. No interrupted pacman on my side.



If you still have the previous package in your cache, you can try this, which worked for me:



  1. Locate cached version of package (for example, mine was /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz).

  2. Extract it: mkdir -p ~/pkg/tmp && tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp

  3. Copy libs to your lib folder: sudo cp ~/pkg/tmp/usr/lib/libicu*.59 /usr/lib/

  4. Proceed with update: sudo pacman -Syyu

  5. You can now remove the files you just extracted.





share|improve this answer
















  • 2




    Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
    – Skatox
    Dec 11 '17 at 3:25










  • This worked for me as well. Thanks, have an upvote.
    – Vaughan Hilts
    Jan 18 at 3:01

















up vote
2
down vote













You can also use the LD_LIBRARY_PATH variable to load the icu libraries from a different location. In this way, you can avoid any copies to /usr/lib:



$ mkdir -p ~/pkg/tmp
$ tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp
$ su
# LD_LIBRARY_PATH=`pwd`/pkg/tmp pacman -U /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz





share|improve this answer




















  • It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
    – v_2e
    Feb 10 at 4:51


















up vote
1
down vote













I researched the problem and found about the /var/log/pacman.log. I read the log and found that the problem was:



...
[2017-11-28 04:34] [ALPM] upgraded libmariadbclient (10.1.28-1 -> 10.1.29-1)
[2017-11-28 04:34] [ALPM] transaction interrupted


The update was interrupted, hence the linkage problem.



I then downloaded the firmware from here. I extracted the missing library:



$ gunzip ArchLinuxARM-rpi-latest.tar.gz
$ tar -tf ArchLinuxARM-rpi-latest.tar |grep libicuuc.so.59
./usr/lib/libicuuc.so.59.1
./usr/lib/libicuuc.so.59
$ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59.1
$ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59


libicuuc.so.59 was a symlink to libicuuc.so.59.1, so I moved libicuuc.so.59.1 to /usr/lib/libicuuc.so.59.



Running pacman I got the error that libicudata.so.59 was missing. I extracted the missing library to /usr/lib and pacman was working :).



I then updated the system with pacman -Syuq and checked with ldd /usr/bin/pacman that all libraries were present. I moved the v59 libraries from /usr/lib and checked that pacman was working.



Reboot with fingers crossed... successfully!!!



pacman -Sc and go to bed with a smile :)






share|improve this answer



























    up vote
    0
    down vote













    In case you have an executable that needs that particular version of the library (as it happened in my case), there is an aur package for that specific version.






    share|improve this answer



























      up vote
      0
      down vote













      Solved the problem with pacman -Sc followed by pacman -Syyu
      Not sure why it solved the problem.






      share|improve this answer




















        Your Answer







        StackExchange.ready(function()
        var channelOptions =
        tags: "".split(" "),
        id: "106"
        ;
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function()
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled)
        StackExchange.using("snippets", function()
        createEditor();
        );

        else
        createEditor();

        );

        function createEditor()
        StackExchange.prepareEditor(
        heartbeatType: 'answer',
        convertImagesToLinks: false,
        noModals: false,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        );



        );













         

        draft saved


        draft discarded


















        StackExchange.ready(
        function ()
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407473%2ferror-while-loading-shared-libraries-libicuuc-so-59-cannot-open-shared-object%23new-answer', 'question_page');

        );

        Post as a guest






























        5 Answers
        5






        active

        oldest

        votes








        5 Answers
        5






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes








        up vote
        17
        down vote













        Previously proposed solutions were not relevant or did not work for me. For some reason upgrading the icu package from 59.1-2 to 60.1-1 made linkage break and many programs (including pacman) failed with this error after. No interrupted pacman on my side.



        If you still have the previous package in your cache, you can try this, which worked for me:



        1. Locate cached version of package (for example, mine was /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz).

        2. Extract it: mkdir -p ~/pkg/tmp && tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp

        3. Copy libs to your lib folder: sudo cp ~/pkg/tmp/usr/lib/libicu*.59 /usr/lib/

        4. Proceed with update: sudo pacman -Syyu

        5. You can now remove the files you just extracted.





        share|improve this answer
















        • 2




          Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
          – Skatox
          Dec 11 '17 at 3:25










        • This worked for me as well. Thanks, have an upvote.
          – Vaughan Hilts
          Jan 18 at 3:01














        up vote
        17
        down vote













        Previously proposed solutions were not relevant or did not work for me. For some reason upgrading the icu package from 59.1-2 to 60.1-1 made linkage break and many programs (including pacman) failed with this error after. No interrupted pacman on my side.



        If you still have the previous package in your cache, you can try this, which worked for me:



        1. Locate cached version of package (for example, mine was /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz).

        2. Extract it: mkdir -p ~/pkg/tmp && tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp

        3. Copy libs to your lib folder: sudo cp ~/pkg/tmp/usr/lib/libicu*.59 /usr/lib/

        4. Proceed with update: sudo pacman -Syyu

        5. You can now remove the files you just extracted.





        share|improve this answer
















        • 2




          Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
          – Skatox
          Dec 11 '17 at 3:25










        • This worked for me as well. Thanks, have an upvote.
          – Vaughan Hilts
          Jan 18 at 3:01












        up vote
        17
        down vote










        up vote
        17
        down vote









        Previously proposed solutions were not relevant or did not work for me. For some reason upgrading the icu package from 59.1-2 to 60.1-1 made linkage break and many programs (including pacman) failed with this error after. No interrupted pacman on my side.



        If you still have the previous package in your cache, you can try this, which worked for me:



        1. Locate cached version of package (for example, mine was /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz).

        2. Extract it: mkdir -p ~/pkg/tmp && tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp

        3. Copy libs to your lib folder: sudo cp ~/pkg/tmp/usr/lib/libicu*.59 /usr/lib/

        4. Proceed with update: sudo pacman -Syyu

        5. You can now remove the files you just extracted.





        share|improve this answer












        Previously proposed solutions were not relevant or did not work for me. For some reason upgrading the icu package from 59.1-2 to 60.1-1 made linkage break and many programs (including pacman) failed with this error after. No interrupted pacman on my side.



        If you still have the previous package in your cache, you can try this, which worked for me:



        1. Locate cached version of package (for example, mine was /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz).

        2. Extract it: mkdir -p ~/pkg/tmp && tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp

        3. Copy libs to your lib folder: sudo cp ~/pkg/tmp/usr/lib/libicu*.59 /usr/lib/

        4. Proceed with update: sudo pacman -Syyu

        5. You can now remove the files you just extracted.






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 2 '17 at 2:32









        Legogris

        1712




        1712







        • 2




          Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
          – Skatox
          Dec 11 '17 at 3:25










        • This worked for me as well. Thanks, have an upvote.
          – Vaughan Hilts
          Jan 18 at 3:01












        • 2




          Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
          – Skatox
          Dec 11 '17 at 3:25










        • This worked for me as well. Thanks, have an upvote.
          – Vaughan Hilts
          Jan 18 at 3:01







        2




        2




        Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
        – Skatox
        Dec 11 '17 at 3:25




        Thanks, this worked for me. But how should I safe remove copied libicu*.59 files? rm /usr/lib/libicu*.59 ?
        – Skatox
        Dec 11 '17 at 3:25












        This worked for me as well. Thanks, have an upvote.
        – Vaughan Hilts
        Jan 18 at 3:01




        This worked for me as well. Thanks, have an upvote.
        – Vaughan Hilts
        Jan 18 at 3:01












        up vote
        2
        down vote













        You can also use the LD_LIBRARY_PATH variable to load the icu libraries from a different location. In this way, you can avoid any copies to /usr/lib:



        $ mkdir -p ~/pkg/tmp
        $ tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp
        $ su
        # LD_LIBRARY_PATH=`pwd`/pkg/tmp pacman -U /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz





        share|improve this answer




















        • It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
          – v_2e
          Feb 10 at 4:51















        up vote
        2
        down vote













        You can also use the LD_LIBRARY_PATH variable to load the icu libraries from a different location. In this way, you can avoid any copies to /usr/lib:



        $ mkdir -p ~/pkg/tmp
        $ tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp
        $ su
        # LD_LIBRARY_PATH=`pwd`/pkg/tmp pacman -U /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz





        share|improve this answer




















        • It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
          – v_2e
          Feb 10 at 4:51













        up vote
        2
        down vote










        up vote
        2
        down vote









        You can also use the LD_LIBRARY_PATH variable to load the icu libraries from a different location. In this way, you can avoid any copies to /usr/lib:



        $ mkdir -p ~/pkg/tmp
        $ tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp
        $ su
        # LD_LIBRARY_PATH=`pwd`/pkg/tmp pacman -U /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz





        share|improve this answer












        You can also use the LD_LIBRARY_PATH variable to load the icu libraries from a different location. In this way, you can avoid any copies to /usr/lib:



        $ mkdir -p ~/pkg/tmp
        $ tar xJvf /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz -C ~/pkg/tmp
        $ su
        # LD_LIBRARY_PATH=`pwd`/pkg/tmp pacman -U /var/cache/pacman/pkg/icu-59.1-2-x86_64.pkg.tar.xz






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 12 at 22:35









        jviki

        211




        211











        • It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
          – v_2e
          Feb 10 at 4:51

















        • It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
          – v_2e
          Feb 10 at 4:51
















        It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
        – v_2e
        Feb 10 at 4:51





        It was LD_LIBRARY_PATH=`pwd`/pkg/tmp/usr/lib in my case.
        – v_2e
        Feb 10 at 4:51











        up vote
        1
        down vote













        I researched the problem and found about the /var/log/pacman.log. I read the log and found that the problem was:



        ...
        [2017-11-28 04:34] [ALPM] upgraded libmariadbclient (10.1.28-1 -> 10.1.29-1)
        [2017-11-28 04:34] [ALPM] transaction interrupted


        The update was interrupted, hence the linkage problem.



        I then downloaded the firmware from here. I extracted the missing library:



        $ gunzip ArchLinuxARM-rpi-latest.tar.gz
        $ tar -tf ArchLinuxARM-rpi-latest.tar |grep libicuuc.so.59
        ./usr/lib/libicuuc.so.59.1
        ./usr/lib/libicuuc.so.59
        $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59.1
        $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59


        libicuuc.so.59 was a symlink to libicuuc.so.59.1, so I moved libicuuc.so.59.1 to /usr/lib/libicuuc.so.59.



        Running pacman I got the error that libicudata.so.59 was missing. I extracted the missing library to /usr/lib and pacman was working :).



        I then updated the system with pacman -Syuq and checked with ldd /usr/bin/pacman that all libraries were present. I moved the v59 libraries from /usr/lib and checked that pacman was working.



        Reboot with fingers crossed... successfully!!!



        pacman -Sc and go to bed with a smile :)






        share|improve this answer
























          up vote
          1
          down vote













          I researched the problem and found about the /var/log/pacman.log. I read the log and found that the problem was:



          ...
          [2017-11-28 04:34] [ALPM] upgraded libmariadbclient (10.1.28-1 -> 10.1.29-1)
          [2017-11-28 04:34] [ALPM] transaction interrupted


          The update was interrupted, hence the linkage problem.



          I then downloaded the firmware from here. I extracted the missing library:



          $ gunzip ArchLinuxARM-rpi-latest.tar.gz
          $ tar -tf ArchLinuxARM-rpi-latest.tar |grep libicuuc.so.59
          ./usr/lib/libicuuc.so.59.1
          ./usr/lib/libicuuc.so.59
          $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59.1
          $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59


          libicuuc.so.59 was a symlink to libicuuc.so.59.1, so I moved libicuuc.so.59.1 to /usr/lib/libicuuc.so.59.



          Running pacman I got the error that libicudata.so.59 was missing. I extracted the missing library to /usr/lib and pacman was working :).



          I then updated the system with pacman -Syuq and checked with ldd /usr/bin/pacman that all libraries were present. I moved the v59 libraries from /usr/lib and checked that pacman was working.



          Reboot with fingers crossed... successfully!!!



          pacman -Sc and go to bed with a smile :)






          share|improve this answer






















            up vote
            1
            down vote










            up vote
            1
            down vote









            I researched the problem and found about the /var/log/pacman.log. I read the log and found that the problem was:



            ...
            [2017-11-28 04:34] [ALPM] upgraded libmariadbclient (10.1.28-1 -> 10.1.29-1)
            [2017-11-28 04:34] [ALPM] transaction interrupted


            The update was interrupted, hence the linkage problem.



            I then downloaded the firmware from here. I extracted the missing library:



            $ gunzip ArchLinuxARM-rpi-latest.tar.gz
            $ tar -tf ArchLinuxARM-rpi-latest.tar |grep libicuuc.so.59
            ./usr/lib/libicuuc.so.59.1
            ./usr/lib/libicuuc.so.59
            $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59.1
            $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59


            libicuuc.so.59 was a symlink to libicuuc.so.59.1, so I moved libicuuc.so.59.1 to /usr/lib/libicuuc.so.59.



            Running pacman I got the error that libicudata.so.59 was missing. I extracted the missing library to /usr/lib and pacman was working :).



            I then updated the system with pacman -Syuq and checked with ldd /usr/bin/pacman that all libraries were present. I moved the v59 libraries from /usr/lib and checked that pacman was working.



            Reboot with fingers crossed... successfully!!!



            pacman -Sc and go to bed with a smile :)






            share|improve this answer












            I researched the problem and found about the /var/log/pacman.log. I read the log and found that the problem was:



            ...
            [2017-11-28 04:34] [ALPM] upgraded libmariadbclient (10.1.28-1 -> 10.1.29-1)
            [2017-11-28 04:34] [ALPM] transaction interrupted


            The update was interrupted, hence the linkage problem.



            I then downloaded the firmware from here. I extracted the missing library:



            $ gunzip ArchLinuxARM-rpi-latest.tar.gz
            $ tar -tf ArchLinuxARM-rpi-latest.tar |grep libicuuc.so.59
            ./usr/lib/libicuuc.so.59.1
            ./usr/lib/libicuuc.so.59
            $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59.1
            $ tar -xf ArchLinuxARM-rpi-latest.tar ./usr/lib/libicuuc.so.59


            libicuuc.so.59 was a symlink to libicuuc.so.59.1, so I moved libicuuc.so.59.1 to /usr/lib/libicuuc.so.59.



            Running pacman I got the error that libicudata.so.59 was missing. I extracted the missing library to /usr/lib and pacman was working :).



            I then updated the system with pacman -Syuq and checked with ldd /usr/bin/pacman that all libraries were present. I moved the v59 libraries from /usr/lib and checked that pacman was working.



            Reboot with fingers crossed... successfully!!!



            pacman -Sc and go to bed with a smile :)







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 28 '17 at 21:09









            frustratedMartian

            51114




            51114




















                up vote
                0
                down vote













                In case you have an executable that needs that particular version of the library (as it happened in my case), there is an aur package for that specific version.






                share|improve this answer
























                  up vote
                  0
                  down vote













                  In case you have an executable that needs that particular version of the library (as it happened in my case), there is an aur package for that specific version.






                  share|improve this answer






















                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    In case you have an executable that needs that particular version of the library (as it happened in my case), there is an aur package for that specific version.






                    share|improve this answer












                    In case you have an executable that needs that particular version of the library (as it happened in my case), there is an aur package for that specific version.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Dec 6 '17 at 2:16









                    ivcha

                    1011




                    1011




















                        up vote
                        0
                        down vote













                        Solved the problem with pacman -Sc followed by pacman -Syyu
                        Not sure why it solved the problem.






                        share|improve this answer
























                          up vote
                          0
                          down vote













                          Solved the problem with pacman -Sc followed by pacman -Syyu
                          Not sure why it solved the problem.






                          share|improve this answer






















                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            Solved the problem with pacman -Sc followed by pacman -Syyu
                            Not sure why it solved the problem.






                            share|improve this answer












                            Solved the problem with pacman -Sc followed by pacman -Syyu
                            Not sure why it solved the problem.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Aug 17 at 15:05









                            asanguinetti

                            11




                            11



























                                 

                                draft saved


                                draft discarded















































                                 


                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function ()
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407473%2ferror-while-loading-shared-libraries-libicuuc-so-59-cannot-open-shared-object%23new-answer', 'question_page');

                                );

                                Post as a guest













































































                                Popular posts from this blog

                                How to check contact read email or not when send email to Individual?

                                Displaying single band from multi-band raster using QGIS

                                How many registers does an x86_64 CPU actually have?