ldd started to show me “not a dynamic executable”












2














I am a bit confused because I don't understand why it happens:

The last changes on the system that I remember were




  • installed g++5 for the old porject (removed already)

  • apt autoclean


  • removed ldconfig cache (guess this is the reason)


Now I can't launch some of the applications. Ldd tells me that it's “not a dynamic executable”



igor@Linbox:/lib/i386-linux-gnu$ ldd libssl.so.1.0.0 
is not a dynamic executable

igor@Linbox:/lib/i386-linux-gnu$ ldd libselinux.so.1
is not a dynamic executable

igor@Linbox:/bin$ ldd dd
linux-vdso.so.1 => (0x00007fff0b380000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb618c76000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb619269000)

igor@Linbox:/lib/x86_64-linux-gnu$ ldd libc.so.6
/lib64/ld-linux-x86-64.so.2 (0x00007fcb44373000)
linux-vdso.so.1 => (0x00007ffed8f33000)


Version: Linux Linbox 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



Also I checked that it is still present:



// for running x32 applications on x64 system
sudo dpkg --add-architecture i386
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


Since removed ld.so.cache I did sudo ldconfig. There is new cache in /etc/ld.so.cache



Do I miss some library?



Added file checks:



file /lib/i386-linux-gnu/libssl.so.1.0.0
/lib/i386-linux-gnu/libssl.so.1.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=c1e3854cb8b86f1006dc391d23f102ea1184cf25, stripped
file /lib/i386-linux-gnu/libselinux.so.1
/lib/i386-linux-gnu/libselinux.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=396cda857e41036061599a59c9f5fe62d7b50c4d, stripped
dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0
libssl1.0.0:i386: /lib/i386-linux-gnu/libssl.so.1.0.0
dpkg -S /lib/i386-linux-gnu/libselinux.so.1
libselinux1:i386: /lib/i386-linux-gnu/libselinux.so.1


Checked libx32 from comments:



igor@Linbox:/lib/i386-linux-gnu$ ls -l /libx32/ld*
-rwxr-xr-x 1 root root 155092 Jan 12 2018 /libx32/ld-2.26.so
lrwxrwxrwx 1 root root 10 Jan 12 2018 /libx32/ld-linux-x32.so.2 -> ld-2.26.so









share|improve this question




















  • 1




    You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
    – N0rbert
    Dec 2 '18 at 13:32






  • 1




    I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
    – steeldriver
    Dec 2 '18 at 14:56










  • ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
    – IgorZ
    Dec 2 '18 at 21:23






  • 1




    Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
    – ubfan1
    Dec 2 '18 at 22:39
















2














I am a bit confused because I don't understand why it happens:

The last changes on the system that I remember were




  • installed g++5 for the old porject (removed already)

  • apt autoclean


  • removed ldconfig cache (guess this is the reason)


Now I can't launch some of the applications. Ldd tells me that it's “not a dynamic executable”



igor@Linbox:/lib/i386-linux-gnu$ ldd libssl.so.1.0.0 
is not a dynamic executable

igor@Linbox:/lib/i386-linux-gnu$ ldd libselinux.so.1
is not a dynamic executable

igor@Linbox:/bin$ ldd dd
linux-vdso.so.1 => (0x00007fff0b380000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb618c76000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb619269000)

igor@Linbox:/lib/x86_64-linux-gnu$ ldd libc.so.6
/lib64/ld-linux-x86-64.so.2 (0x00007fcb44373000)
linux-vdso.so.1 => (0x00007ffed8f33000)


Version: Linux Linbox 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



Also I checked that it is still present:



// for running x32 applications on x64 system
sudo dpkg --add-architecture i386
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


Since removed ld.so.cache I did sudo ldconfig. There is new cache in /etc/ld.so.cache



Do I miss some library?



Added file checks:



file /lib/i386-linux-gnu/libssl.so.1.0.0
/lib/i386-linux-gnu/libssl.so.1.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=c1e3854cb8b86f1006dc391d23f102ea1184cf25, stripped
file /lib/i386-linux-gnu/libselinux.so.1
/lib/i386-linux-gnu/libselinux.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=396cda857e41036061599a59c9f5fe62d7b50c4d, stripped
dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0
libssl1.0.0:i386: /lib/i386-linux-gnu/libssl.so.1.0.0
dpkg -S /lib/i386-linux-gnu/libselinux.so.1
libselinux1:i386: /lib/i386-linux-gnu/libselinux.so.1


Checked libx32 from comments:



igor@Linbox:/lib/i386-linux-gnu$ ls -l /libx32/ld*
-rwxr-xr-x 1 root root 155092 Jan 12 2018 /libx32/ld-2.26.so
lrwxrwxrwx 1 root root 10 Jan 12 2018 /libx32/ld-linux-x32.so.2 -> ld-2.26.so









share|improve this question




















  • 1




    You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
    – N0rbert
    Dec 2 '18 at 13:32






  • 1




    I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
    – steeldriver
    Dec 2 '18 at 14:56










  • ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
    – IgorZ
    Dec 2 '18 at 21:23






  • 1




    Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
    – ubfan1
    Dec 2 '18 at 22:39














2












2








2







I am a bit confused because I don't understand why it happens:

The last changes on the system that I remember were




  • installed g++5 for the old porject (removed already)

  • apt autoclean


  • removed ldconfig cache (guess this is the reason)


Now I can't launch some of the applications. Ldd tells me that it's “not a dynamic executable”



igor@Linbox:/lib/i386-linux-gnu$ ldd libssl.so.1.0.0 
is not a dynamic executable

igor@Linbox:/lib/i386-linux-gnu$ ldd libselinux.so.1
is not a dynamic executable

igor@Linbox:/bin$ ldd dd
linux-vdso.so.1 => (0x00007fff0b380000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb618c76000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb619269000)

igor@Linbox:/lib/x86_64-linux-gnu$ ldd libc.so.6
/lib64/ld-linux-x86-64.so.2 (0x00007fcb44373000)
linux-vdso.so.1 => (0x00007ffed8f33000)


Version: Linux Linbox 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



Also I checked that it is still present:



// for running x32 applications on x64 system
sudo dpkg --add-architecture i386
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


Since removed ld.so.cache I did sudo ldconfig. There is new cache in /etc/ld.so.cache



Do I miss some library?



Added file checks:



file /lib/i386-linux-gnu/libssl.so.1.0.0
/lib/i386-linux-gnu/libssl.so.1.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=c1e3854cb8b86f1006dc391d23f102ea1184cf25, stripped
file /lib/i386-linux-gnu/libselinux.so.1
/lib/i386-linux-gnu/libselinux.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=396cda857e41036061599a59c9f5fe62d7b50c4d, stripped
dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0
libssl1.0.0:i386: /lib/i386-linux-gnu/libssl.so.1.0.0
dpkg -S /lib/i386-linux-gnu/libselinux.so.1
libselinux1:i386: /lib/i386-linux-gnu/libselinux.so.1


Checked libx32 from comments:



igor@Linbox:/lib/i386-linux-gnu$ ls -l /libx32/ld*
-rwxr-xr-x 1 root root 155092 Jan 12 2018 /libx32/ld-2.26.so
lrwxrwxrwx 1 root root 10 Jan 12 2018 /libx32/ld-linux-x32.so.2 -> ld-2.26.so









share|improve this question















I am a bit confused because I don't understand why it happens:

The last changes on the system that I remember were




  • installed g++5 for the old porject (removed already)

  • apt autoclean


  • removed ldconfig cache (guess this is the reason)


Now I can't launch some of the applications. Ldd tells me that it's “not a dynamic executable”



igor@Linbox:/lib/i386-linux-gnu$ ldd libssl.so.1.0.0 
is not a dynamic executable

igor@Linbox:/lib/i386-linux-gnu$ ldd libselinux.so.1
is not a dynamic executable

igor@Linbox:/bin$ ldd dd
linux-vdso.so.1 => (0x00007fff0b380000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb618c76000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb619269000)

igor@Linbox:/lib/x86_64-linux-gnu$ ldd libc.so.6
/lib64/ld-linux-x86-64.so.2 (0x00007fcb44373000)
linux-vdso.so.1 => (0x00007ffed8f33000)


Version: Linux Linbox 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



Also I checked that it is still present:



// for running x32 applications on x64 system
sudo dpkg --add-architecture i386
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


Since removed ld.so.cache I did sudo ldconfig. There is new cache in /etc/ld.so.cache



Do I miss some library?



Added file checks:



file /lib/i386-linux-gnu/libssl.so.1.0.0
/lib/i386-linux-gnu/libssl.so.1.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=c1e3854cb8b86f1006dc391d23f102ea1184cf25, stripped
file /lib/i386-linux-gnu/libselinux.so.1
/lib/i386-linux-gnu/libselinux.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=396cda857e41036061599a59c9f5fe62d7b50c4d, stripped
dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0
libssl1.0.0:i386: /lib/i386-linux-gnu/libssl.so.1.0.0
dpkg -S /lib/i386-linux-gnu/libselinux.so.1
libselinux1:i386: /lib/i386-linux-gnu/libselinux.so.1


Checked libx32 from comments:



igor@Linbox:/lib/i386-linux-gnu$ ls -l /libx32/ld*
-rwxr-xr-x 1 root root 155092 Jan 12 2018 /libx32/ld-2.26.so
lrwxrwxrwx 1 root root 10 Jan 12 2018 /libx32/ld-linux-x32.so.2 -> ld-2.26.so






libraries executable






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 2 '18 at 21:27

























asked Dec 2 '18 at 13:29









IgorZ

1114




1114








  • 1




    You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
    – N0rbert
    Dec 2 '18 at 13:32






  • 1




    I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
    – steeldriver
    Dec 2 '18 at 14:56










  • ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
    – IgorZ
    Dec 2 '18 at 21:23






  • 1




    Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
    – ubfan1
    Dec 2 '18 at 22:39














  • 1




    You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
    – N0rbert
    Dec 2 '18 at 13:32






  • 1




    I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
    – steeldriver
    Dec 2 '18 at 14:56










  • ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
    – IgorZ
    Dec 2 '18 at 21:23






  • 1




    Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
    – ubfan1
    Dec 2 '18 at 22:39








1




1




You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
– N0rbert
Dec 2 '18 at 13:32




You can check filetype with file /lib/i386-linux-gnu/libssl.so.1.0.0 and file /lib/i386-linux-gnu/libselinux.so.1. Also check their package names with dpkg -S /lib/i386-linux-gnu/libssl.so.1.0.0 and dpkg -S /lib/i386-linux-gnu/libselinux.so.1. Please add all this output to the question.
– N0rbert
Dec 2 '18 at 13:32




1




1




I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
– steeldriver
Dec 2 '18 at 14:56




I wonder if ld-linux-x32.so is missing or broken? what is the output of ls -l /libx32/ld*?
– steeldriver
Dec 2 '18 at 14:56












ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
– IgorZ
Dec 2 '18 at 21:23




ls -l /libx32/ld* --> -rwxr-xr-x 1 root root /libx32/ld-2.26.so, lrwxrwxrwx 1 root root /libx32/ld-linux-x32.so.2 --> ld-2.26.so; ldd ld-2.26.so -> is not a dynamic executable;
– IgorZ
Dec 2 '18 at 21:23




1




1




Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
– ubfan1
Dec 2 '18 at 22:39




Your 4.13 kernel (16.04.4) reached EOL Aug 2018. Try upgrading your HWE stack to the next release.
– ubfan1
Dec 2 '18 at 22:39










2 Answers
2






active

oldest

votes


















1














Bug 1616609, ldd reports incorrectly "not a dynamic executable" when the executable's loader is not present , is probably the cause of the problem (as steeldriver suggested). Reinstall the libc6-x32 package to get it back. Do consider adding yourself to the bug, maybe it'll be fixed one day -- a patch is even suggested.






share|improve this answer





















  • I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
    – IgorZ
    Dec 2 '18 at 21:24



















0














I've solved the problem (thx to ubfan1) by updating kernel from 4.13.0-46-generic up to 4.15.0-39-generic:



$ uname -a
Linux Linbox 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

/lib/i386-linux-gnu$ ldd libselinux.so.1
linux-gate.so.1 (0xf7fca000)
libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf7ee6000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7ee1000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7d05000)
/lib/ld-linux.so.2 (0xf7fcc000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ce6000)





share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1097900%2fldd-started-to-show-me-not-a-dynamic-executable%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Bug 1616609, ldd reports incorrectly "not a dynamic executable" when the executable's loader is not present , is probably the cause of the problem (as steeldriver suggested). Reinstall the libc6-x32 package to get it back. Do consider adding yourself to the bug, maybe it'll be fixed one day -- a patch is even suggested.






    share|improve this answer





















    • I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
      – IgorZ
      Dec 2 '18 at 21:24
















    1














    Bug 1616609, ldd reports incorrectly "not a dynamic executable" when the executable's loader is not present , is probably the cause of the problem (as steeldriver suggested). Reinstall the libc6-x32 package to get it back. Do consider adding yourself to the bug, maybe it'll be fixed one day -- a patch is even suggested.






    share|improve this answer





















    • I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
      – IgorZ
      Dec 2 '18 at 21:24














    1












    1








    1






    Bug 1616609, ldd reports incorrectly "not a dynamic executable" when the executable's loader is not present , is probably the cause of the problem (as steeldriver suggested). Reinstall the libc6-x32 package to get it back. Do consider adding yourself to the bug, maybe it'll be fixed one day -- a patch is even suggested.






    share|improve this answer












    Bug 1616609, ldd reports incorrectly "not a dynamic executable" when the executable's loader is not present , is probably the cause of the problem (as steeldriver suggested). Reinstall the libc6-x32 package to get it back. Do consider adding yourself to the bug, maybe it'll be fixed one day -- a patch is even suggested.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 2 '18 at 16:12









    ubfan1

    9,23641527




    9,23641527












    • I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
      – IgorZ
      Dec 2 '18 at 21:24


















    • I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
      – IgorZ
      Dec 2 '18 at 21:24
















    I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
    – IgorZ
    Dec 2 '18 at 21:24




    I did sudo apt remove libc6-x32 and then sudo apt install libc6-x32; Still the same.
    – IgorZ
    Dec 2 '18 at 21:24













    0














    I've solved the problem (thx to ubfan1) by updating kernel from 4.13.0-46-generic up to 4.15.0-39-generic:



    $ uname -a
    Linux Linbox 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

    $ lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 18.04.1 LTS
    Release: 18.04
    Codename: bionic

    /lib/i386-linux-gnu$ ldd libselinux.so.1
    linux-gate.so.1 (0xf7fca000)
    libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf7ee6000)
    libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7ee1000)
    libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7d05000)
    /lib/ld-linux.so.2 (0xf7fcc000)
    libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ce6000)





    share|improve this answer


























      0














      I've solved the problem (thx to ubfan1) by updating kernel from 4.13.0-46-generic up to 4.15.0-39-generic:



      $ uname -a
      Linux Linbox 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

      $ lsb_release -a
      No LSB modules are available.
      Distributor ID: Ubuntu
      Description: Ubuntu 18.04.1 LTS
      Release: 18.04
      Codename: bionic

      /lib/i386-linux-gnu$ ldd libselinux.so.1
      linux-gate.so.1 (0xf7fca000)
      libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf7ee6000)
      libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7ee1000)
      libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7d05000)
      /lib/ld-linux.so.2 (0xf7fcc000)
      libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ce6000)





      share|improve this answer
























        0












        0








        0






        I've solved the problem (thx to ubfan1) by updating kernel from 4.13.0-46-generic up to 4.15.0-39-generic:



        $ uname -a
        Linux Linbox 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

        $ lsb_release -a
        No LSB modules are available.
        Distributor ID: Ubuntu
        Description: Ubuntu 18.04.1 LTS
        Release: 18.04
        Codename: bionic

        /lib/i386-linux-gnu$ ldd libselinux.so.1
        linux-gate.so.1 (0xf7fca000)
        libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf7ee6000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7ee1000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7d05000)
        /lib/ld-linux.so.2 (0xf7fcc000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ce6000)





        share|improve this answer












        I've solved the problem (thx to ubfan1) by updating kernel from 4.13.0-46-generic up to 4.15.0-39-generic:



        $ uname -a
        Linux Linbox 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

        $ lsb_release -a
        No LSB modules are available.
        Distributor ID: Ubuntu
        Description: Ubuntu 18.04.1 LTS
        Release: 18.04
        Codename: bionic

        /lib/i386-linux-gnu$ ldd libselinux.so.1
        linux-gate.so.1 (0xf7fca000)
        libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf7ee6000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7ee1000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7d05000)
        /lib/ld-linux.so.2 (0xf7fcc000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ce6000)






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 3 '18 at 12:55









        IgorZ

        1114




        1114






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1097900%2fldd-started-to-show-me-not-a-dynamic-executable%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to change which sound is reproduced for terminal bell?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Can I use Tabulator js library in my java Spring + Thymeleaf project?