Broken libc6 makes system unbootable when I install packages via apt-get












0















I tried to install Skype on my amd64 Debian 7, after believing the page that told me to upgrade libc6 and allow the x86 architecture. When I started downloading such packages and upgrading libc6 my system broke and at boot I kept getting this message:
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion map >l_init_called' failed!
(Which happens to be the same one when I type /lib/libc.so.6 on the terminal)



I used a rescue disk, erased all the x86 packages and deleted the x86 architecture but if I install something from apt-get, the system breaks again and the OS wont boot until the ld.so.cache file is deleted.



If ldd --version is run on the terminal the output is: ldd (Debian EGLIBC 2.13-38+deb7u6) 2.13



What should I do in order to be able to install packages again via apt-get without having to rescue the system each time afterwards?










share|improve this question














bumped to the homepage by Community 42 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • My advice would be to do a total reinstll as you broke part of your toolchain

    – eyoung100
    Jan 1 '15 at 18:14











  • Can't I just reinstall what I need?

    – Marcox
    Feb 4 '15 at 21:33
















0















I tried to install Skype on my amd64 Debian 7, after believing the page that told me to upgrade libc6 and allow the x86 architecture. When I started downloading such packages and upgrading libc6 my system broke and at boot I kept getting this message:
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion map >l_init_called' failed!
(Which happens to be the same one when I type /lib/libc.so.6 on the terminal)



I used a rescue disk, erased all the x86 packages and deleted the x86 architecture but if I install something from apt-get, the system breaks again and the OS wont boot until the ld.so.cache file is deleted.



If ldd --version is run on the terminal the output is: ldd (Debian EGLIBC 2.13-38+deb7u6) 2.13



What should I do in order to be able to install packages again via apt-get without having to rescue the system each time afterwards?










share|improve this question














bumped to the homepage by Community 42 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • My advice would be to do a total reinstll as you broke part of your toolchain

    – eyoung100
    Jan 1 '15 at 18:14











  • Can't I just reinstall what I need?

    – Marcox
    Feb 4 '15 at 21:33














0












0








0








I tried to install Skype on my amd64 Debian 7, after believing the page that told me to upgrade libc6 and allow the x86 architecture. When I started downloading such packages and upgrading libc6 my system broke and at boot I kept getting this message:
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion map >l_init_called' failed!
(Which happens to be the same one when I type /lib/libc.so.6 on the terminal)



I used a rescue disk, erased all the x86 packages and deleted the x86 architecture but if I install something from apt-get, the system breaks again and the OS wont boot until the ld.so.cache file is deleted.



If ldd --version is run on the terminal the output is: ldd (Debian EGLIBC 2.13-38+deb7u6) 2.13



What should I do in order to be able to install packages again via apt-get without having to rescue the system each time afterwards?










share|improve this question














I tried to install Skype on my amd64 Debian 7, after believing the page that told me to upgrade libc6 and allow the x86 architecture. When I started downloading such packages and upgrading libc6 my system broke and at boot I kept getting this message:
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion map >l_init_called' failed!
(Which happens to be the same one when I type /lib/libc.so.6 on the terminal)



I used a rescue disk, erased all the x86 packages and deleted the x86 architecture but if I install something from apt-get, the system breaks again and the OS wont boot until the ld.so.cache file is deleted.



If ldd --version is run on the terminal the output is: ldd (Debian EGLIBC 2.13-38+deb7u6) 2.13



What should I do in order to be able to install packages again via apt-get without having to rescue the system each time afterwards?







debian apt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 1 '15 at 18:07









MarcoxMarcox

13




13





bumped to the homepage by Community 42 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 42 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • My advice would be to do a total reinstll as you broke part of your toolchain

    – eyoung100
    Jan 1 '15 at 18:14











  • Can't I just reinstall what I need?

    – Marcox
    Feb 4 '15 at 21:33



















  • My advice would be to do a total reinstll as you broke part of your toolchain

    – eyoung100
    Jan 1 '15 at 18:14











  • Can't I just reinstall what I need?

    – Marcox
    Feb 4 '15 at 21:33

















My advice would be to do a total reinstll as you broke part of your toolchain

– eyoung100
Jan 1 '15 at 18:14





My advice would be to do a total reinstll as you broke part of your toolchain

– eyoung100
Jan 1 '15 at 18:14













Can't I just reinstall what I need?

– Marcox
Feb 4 '15 at 21:33





Can't I just reinstall what I need?

– Marcox
Feb 4 '15 at 21:33










1 Answer
1






active

oldest

votes


















0














On Debian 7 amd64 [Wheezy] I manually installed TFTP using dpkg. By mistake I installed libc6-udep version 2.19 besides having libc6 2.13 [stable for wheezy] installed.



After that I encountered same problems; apt-get broke system with exact same message.



With the Synaptic package mgr I removed libc6-udep 2.19 which solved the error for me.






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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f176949%2fbroken-libc6-makes-system-unbootable-when-i-install-packages-via-apt-get%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    On Debian 7 amd64 [Wheezy] I manually installed TFTP using dpkg. By mistake I installed libc6-udep version 2.19 besides having libc6 2.13 [stable for wheezy] installed.



    After that I encountered same problems; apt-get broke system with exact same message.



    With the Synaptic package mgr I removed libc6-udep 2.19 which solved the error for me.






    share|improve this answer






























      0














      On Debian 7 amd64 [Wheezy] I manually installed TFTP using dpkg. By mistake I installed libc6-udep version 2.19 besides having libc6 2.13 [stable for wheezy] installed.



      After that I encountered same problems; apt-get broke system with exact same message.



      With the Synaptic package mgr I removed libc6-udep 2.19 which solved the error for me.






      share|improve this answer




























        0












        0








        0







        On Debian 7 amd64 [Wheezy] I manually installed TFTP using dpkg. By mistake I installed libc6-udep version 2.19 besides having libc6 2.13 [stable for wheezy] installed.



        After that I encountered same problems; apt-get broke system with exact same message.



        With the Synaptic package mgr I removed libc6-udep 2.19 which solved the error for me.






        share|improve this answer















        On Debian 7 amd64 [Wheezy] I manually installed TFTP using dpkg. By mistake I installed libc6-udep version 2.19 besides having libc6 2.13 [stable for wheezy] installed.



        After that I encountered same problems; apt-get broke system with exact same message.



        With the Synaptic package mgr I removed libc6-udep 2.19 which solved the error for me.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 6 '15 at 13:49









        Jakuje

        16.5k53256




        16.5k53256










        answered Dec 6 '15 at 12:35









        ManiMani

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f176949%2fbroken-libc6-makes-system-unbootable-when-i-install-packages-via-apt-get%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

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt