“apt-get install” ends with segmentation fault

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












3














I have a following minimalistic sources.list file:



root@c:~# cat /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian/ wheezy main
root@c:~# apt-get update
Hit http://ftp.fi.debian.org wheezy Release.gpg
Hit http://ftp.fi.debian.org wheezy Release
Hit http://ftp.fi.debian.org wheezy/main i386 Packages
Hit http://ftp.fi.debian.org wheezy/main Translation-en
Reading package lists... Done
root@c:~#


Now when I try to install a package, I end up with segmentation fault. For example:



root@c:~# apt-get install tcpdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Segmentation fault
root@c:~#


In /var/log/messages there is a following entry logged:



Mar 29 05:46:25 c kernel: [ 4677.384747] apt-get[5607]: segfault at b8647e30 ip b8647e30 sp bfaaa9c8 error 14


The last (sp) number always changes, i.e if I execute apt-get install nmap three times, then following is logged:



Mar 29 05:46:59 c kernel: [ 4711.046400] apt-get[5612]: segfault at b86cbe30 ip b86cbe30 sp bfb36ea8 error 14
Mar 29 05:47:02 c kernel: [ 4714.229648] apt-get[5616]: segfault at b8609e30 ip b8609e30 sp bfcecec8 error 14
Mar 29 05:47:03 c kernel: [ 4715.505656] apt-get[5620]: segfault at b86dae30 ip b86dae30 sp bfb4b588 error 14


I have tried with different repositories and cleaned local repository of retrieved package files. What might cause segment fault when installing a package? Is my apt-get broken?










share|improve this question























  • This is most likely a hardware issue. What is the output of dpkg -C?
    – Faheem Mitha
    Mar 29 '15 at 4:34










  • @FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
    – Martin
    Mar 29 '15 at 13:19










  • Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
    – Faheem Mitha
    Mar 29 '15 at 14:30










  • Addendum: I'd start with checking your memory and hard drives.
    – Faheem Mitha
    Mar 29 '15 at 16:49










  • Does the error reproduces with aptitude: aptitude install tcpdump ?
    – nwildner
    Mar 30 '15 at 13:21















3














I have a following minimalistic sources.list file:



root@c:~# cat /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian/ wheezy main
root@c:~# apt-get update
Hit http://ftp.fi.debian.org wheezy Release.gpg
Hit http://ftp.fi.debian.org wheezy Release
Hit http://ftp.fi.debian.org wheezy/main i386 Packages
Hit http://ftp.fi.debian.org wheezy/main Translation-en
Reading package lists... Done
root@c:~#


Now when I try to install a package, I end up with segmentation fault. For example:



root@c:~# apt-get install tcpdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Segmentation fault
root@c:~#


In /var/log/messages there is a following entry logged:



Mar 29 05:46:25 c kernel: [ 4677.384747] apt-get[5607]: segfault at b8647e30 ip b8647e30 sp bfaaa9c8 error 14


The last (sp) number always changes, i.e if I execute apt-get install nmap three times, then following is logged:



Mar 29 05:46:59 c kernel: [ 4711.046400] apt-get[5612]: segfault at b86cbe30 ip b86cbe30 sp bfb36ea8 error 14
Mar 29 05:47:02 c kernel: [ 4714.229648] apt-get[5616]: segfault at b8609e30 ip b8609e30 sp bfcecec8 error 14
Mar 29 05:47:03 c kernel: [ 4715.505656] apt-get[5620]: segfault at b86dae30 ip b86dae30 sp bfb4b588 error 14


I have tried with different repositories and cleaned local repository of retrieved package files. What might cause segment fault when installing a package? Is my apt-get broken?










share|improve this question























  • This is most likely a hardware issue. What is the output of dpkg -C?
    – Faheem Mitha
    Mar 29 '15 at 4:34










  • @FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
    – Martin
    Mar 29 '15 at 13:19










  • Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
    – Faheem Mitha
    Mar 29 '15 at 14:30










  • Addendum: I'd start with checking your memory and hard drives.
    – Faheem Mitha
    Mar 29 '15 at 16:49










  • Does the error reproduces with aptitude: aptitude install tcpdump ?
    – nwildner
    Mar 30 '15 at 13:21













3












3








3







I have a following minimalistic sources.list file:



root@c:~# cat /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian/ wheezy main
root@c:~# apt-get update
Hit http://ftp.fi.debian.org wheezy Release.gpg
Hit http://ftp.fi.debian.org wheezy Release
Hit http://ftp.fi.debian.org wheezy/main i386 Packages
Hit http://ftp.fi.debian.org wheezy/main Translation-en
Reading package lists... Done
root@c:~#


Now when I try to install a package, I end up with segmentation fault. For example:



root@c:~# apt-get install tcpdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Segmentation fault
root@c:~#


In /var/log/messages there is a following entry logged:



Mar 29 05:46:25 c kernel: [ 4677.384747] apt-get[5607]: segfault at b8647e30 ip b8647e30 sp bfaaa9c8 error 14


The last (sp) number always changes, i.e if I execute apt-get install nmap three times, then following is logged:



Mar 29 05:46:59 c kernel: [ 4711.046400] apt-get[5612]: segfault at b86cbe30 ip b86cbe30 sp bfb36ea8 error 14
Mar 29 05:47:02 c kernel: [ 4714.229648] apt-get[5616]: segfault at b8609e30 ip b8609e30 sp bfcecec8 error 14
Mar 29 05:47:03 c kernel: [ 4715.505656] apt-get[5620]: segfault at b86dae30 ip b86dae30 sp bfb4b588 error 14


I have tried with different repositories and cleaned local repository of retrieved package files. What might cause segment fault when installing a package? Is my apt-get broken?










share|improve this question















I have a following minimalistic sources.list file:



root@c:~# cat /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian/ wheezy main
root@c:~# apt-get update
Hit http://ftp.fi.debian.org wheezy Release.gpg
Hit http://ftp.fi.debian.org wheezy Release
Hit http://ftp.fi.debian.org wheezy/main i386 Packages
Hit http://ftp.fi.debian.org wheezy/main Translation-en
Reading package lists... Done
root@c:~#


Now when I try to install a package, I end up with segmentation fault. For example:



root@c:~# apt-get install tcpdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Segmentation fault
root@c:~#


In /var/log/messages there is a following entry logged:



Mar 29 05:46:25 c kernel: [ 4677.384747] apt-get[5607]: segfault at b8647e30 ip b8647e30 sp bfaaa9c8 error 14


The last (sp) number always changes, i.e if I execute apt-get install nmap three times, then following is logged:



Mar 29 05:46:59 c kernel: [ 4711.046400] apt-get[5612]: segfault at b86cbe30 ip b86cbe30 sp bfb36ea8 error 14
Mar 29 05:47:02 c kernel: [ 4714.229648] apt-get[5616]: segfault at b8609e30 ip b8609e30 sp bfcecec8 error 14
Mar 29 05:47:03 c kernel: [ 4715.505656] apt-get[5620]: segfault at b86dae30 ip b86dae30 sp bfb4b588 error 14


I have tried with different repositories and cleaned local repository of retrieved package files. What might cause segment fault when installing a package? Is my apt-get broken?







debian apt






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 29 '15 at 2:56

























asked Mar 29 '15 at 2:50









Martin

4272371131




4272371131











  • This is most likely a hardware issue. What is the output of dpkg -C?
    – Faheem Mitha
    Mar 29 '15 at 4:34










  • @FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
    – Martin
    Mar 29 '15 at 13:19










  • Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
    – Faheem Mitha
    Mar 29 '15 at 14:30










  • Addendum: I'd start with checking your memory and hard drives.
    – Faheem Mitha
    Mar 29 '15 at 16:49










  • Does the error reproduces with aptitude: aptitude install tcpdump ?
    – nwildner
    Mar 30 '15 at 13:21
















  • This is most likely a hardware issue. What is the output of dpkg -C?
    – Faheem Mitha
    Mar 29 '15 at 4:34










  • @FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
    – Martin
    Mar 29 '15 at 13:19










  • Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
    – Faheem Mitha
    Mar 29 '15 at 14:30










  • Addendum: I'd start with checking your memory and hard drives.
    – Faheem Mitha
    Mar 29 '15 at 16:49










  • Does the error reproduces with aptitude: aptitude install tcpdump ?
    – nwildner
    Mar 30 '15 at 13:21















This is most likely a hardware issue. What is the output of dpkg -C?
– Faheem Mitha
Mar 29 '15 at 4:34




This is most likely a hardware issue. What is the output of dpkg -C?
– Faheem Mitha
Mar 29 '15 at 4:34












@FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
– Martin
Mar 29 '15 at 13:19




@FaheemMitha A hardware issue? Anyway, there is no output for `dpkg -C. Just an exit code 0 so I guess there are no partially installed packages in my system.
– Martin
Mar 29 '15 at 13:19












Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
– Faheem Mitha
Mar 29 '15 at 14:30




Yes, I can't think of another reason why apt would segfault on you. If you want, you could try reinstalling it. apt-get download apt (check that this is the same as the version you are using - it should be). Then dpkg -i apt...deb.
– Faheem Mitha
Mar 29 '15 at 14:30












Addendum: I'd start with checking your memory and hard drives.
– Faheem Mitha
Mar 29 '15 at 16:49




Addendum: I'd start with checking your memory and hard drives.
– Faheem Mitha
Mar 29 '15 at 16:49












Does the error reproduces with aptitude: aptitude install tcpdump ?
– nwildner
Mar 30 '15 at 13:21




Does the error reproduces with aptitude: aptitude install tcpdump ?
– nwildner
Mar 30 '15 at 13:21










3 Answers
3






active

oldest

votes


















1














Have you tried using strace to diagnose the problem?



I have a similar problem which seems to be related to the google-earth package -- something in the meta-data for the package causes apt-get (or some component of the apt system) to segfault.



I discovered this by using:



sudo strace -f apt-get update >log.strace-aptget 2>&1


Looking at the log file, I could see that, after reading the file /var/lib/apt/lists/dl.google.com_linux_earth_deb_dists_stable_Release, apt-get did a mremap() which caused a segfault. I commented out the google-earth entry in sources.list (actually, in /etc/apt/sources.list.d/google-earth.list) and now apt-get works fine. (Of course, I now cannot update google-earth, but at least apt-get is working.)



Hope this helps.






share|improve this answer


















  • 1




    Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
    – Faheem Mitha
    Apr 16 '15 at 15:41



















1














I have started experiencing the same thing in Precise. To workaround this issue I added a file /etc/apt/apt.conf.d/00bugs which contains one line:



APT::Cache-start 200000000;



The segmentation faults no longer occur. I have opened a bug report for this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436






share|improve this answer




























    0














    Run following commands: I got a fix through it.



    sudo rm /var/lib/apt/lists/lock
    sudo rm /var/cache/apt/archives/lock
    sudo rm /var/lib/dpkg/locksudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
    sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad
    sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status || sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
    sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
    sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
    sudo rm -rf /var/lib/dpkg/updates/*
    sudo rm -rf /var/lib/apt/lists
    sudo rm /var/cache/apt/*.bin
    sudo mkdir /var/lib/apt/lists
    sudo mkdir /var/lib/apt/lists/partial
    sudo apt-get upgrade





    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%2f193169%2fapt-get-install-ends-with-segmentation-fault%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      Have you tried using strace to diagnose the problem?



      I have a similar problem which seems to be related to the google-earth package -- something in the meta-data for the package causes apt-get (or some component of the apt system) to segfault.



      I discovered this by using:



      sudo strace -f apt-get update >log.strace-aptget 2>&1


      Looking at the log file, I could see that, after reading the file /var/lib/apt/lists/dl.google.com_linux_earth_deb_dists_stable_Release, apt-get did a mremap() which caused a segfault. I commented out the google-earth entry in sources.list (actually, in /etc/apt/sources.list.d/google-earth.list) and now apt-get works fine. (Of course, I now cannot update google-earth, but at least apt-get is working.)



      Hope this helps.






      share|improve this answer


















      • 1




        Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
        – Faheem Mitha
        Apr 16 '15 at 15:41
















      1














      Have you tried using strace to diagnose the problem?



      I have a similar problem which seems to be related to the google-earth package -- something in the meta-data for the package causes apt-get (or some component of the apt system) to segfault.



      I discovered this by using:



      sudo strace -f apt-get update >log.strace-aptget 2>&1


      Looking at the log file, I could see that, after reading the file /var/lib/apt/lists/dl.google.com_linux_earth_deb_dists_stable_Release, apt-get did a mremap() which caused a segfault. I commented out the google-earth entry in sources.list (actually, in /etc/apt/sources.list.d/google-earth.list) and now apt-get works fine. (Of course, I now cannot update google-earth, but at least apt-get is working.)



      Hope this helps.






      share|improve this answer


















      • 1




        Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
        – Faheem Mitha
        Apr 16 '15 at 15:41














      1












      1








      1






      Have you tried using strace to diagnose the problem?



      I have a similar problem which seems to be related to the google-earth package -- something in the meta-data for the package causes apt-get (or some component of the apt system) to segfault.



      I discovered this by using:



      sudo strace -f apt-get update >log.strace-aptget 2>&1


      Looking at the log file, I could see that, after reading the file /var/lib/apt/lists/dl.google.com_linux_earth_deb_dists_stable_Release, apt-get did a mremap() which caused a segfault. I commented out the google-earth entry in sources.list (actually, in /etc/apt/sources.list.d/google-earth.list) and now apt-get works fine. (Of course, I now cannot update google-earth, but at least apt-get is working.)



      Hope this helps.






      share|improve this answer














      Have you tried using strace to diagnose the problem?



      I have a similar problem which seems to be related to the google-earth package -- something in the meta-data for the package causes apt-get (or some component of the apt system) to segfault.



      I discovered this by using:



      sudo strace -f apt-get update >log.strace-aptget 2>&1


      Looking at the log file, I could see that, after reading the file /var/lib/apt/lists/dl.google.com_linux_earth_deb_dists_stable_Release, apt-get did a mremap() which caused a segfault. I commented out the google-earth entry in sources.list (actually, in /etc/apt/sources.list.d/google-earth.list) and now apt-get works fine. (Of course, I now cannot update google-earth, but at least apt-get is working.)



      Hope this helps.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Apr 16 '15 at 15:31









      dhag

      11.3k33045




      11.3k33045










      answered Apr 16 '15 at 15:28









      vsh

      112




      112







      • 1




        Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
        – Faheem Mitha
        Apr 16 '15 at 15:41













      • 1




        Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
        – Faheem Mitha
        Apr 16 '15 at 15:41








      1




      1




      Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
      – Faheem Mitha
      Apr 16 '15 at 15:41





      Any segfault at the software level is a bug. I hope you reported this as an apt bug. If not, please do so. People normally use the reportbug to do so.
      – Faheem Mitha
      Apr 16 '15 at 15:41














      1














      I have started experiencing the same thing in Precise. To workaround this issue I added a file /etc/apt/apt.conf.d/00bugs which contains one line:



      APT::Cache-start 200000000;



      The segmentation faults no longer occur. I have opened a bug report for this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436






      share|improve this answer

























        1














        I have started experiencing the same thing in Precise. To workaround this issue I added a file /etc/apt/apt.conf.d/00bugs which contains one line:



        APT::Cache-start 200000000;



        The segmentation faults no longer occur. I have opened a bug report for this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436






        share|improve this answer























          1












          1








          1






          I have started experiencing the same thing in Precise. To workaround this issue I added a file /etc/apt/apt.conf.d/00bugs which contains one line:



          APT::Cache-start 200000000;



          The segmentation faults no longer occur. I have opened a bug report for this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436






          share|improve this answer












          I have started experiencing the same thing in Precise. To workaround this issue I added a file /etc/apt/apt.conf.d/00bugs which contains one line:



          APT::Cache-start 200000000;



          The segmentation faults no longer occur. I have opened a bug report for this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445436







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 5 '15 at 1:09









          FreePerson

          111




          111





















              0














              Run following commands: I got a fix through it.



              sudo rm /var/lib/apt/lists/lock
              sudo rm /var/cache/apt/archives/lock
              sudo rm /var/lib/dpkg/locksudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
              sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad
              sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status || sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
              sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
              sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
              sudo rm -rf /var/lib/dpkg/updates/*
              sudo rm -rf /var/lib/apt/lists
              sudo rm /var/cache/apt/*.bin
              sudo mkdir /var/lib/apt/lists
              sudo mkdir /var/lib/apt/lists/partial
              sudo apt-get upgrade





              share|improve this answer

























                0














                Run following commands: I got a fix through it.



                sudo rm /var/lib/apt/lists/lock
                sudo rm /var/cache/apt/archives/lock
                sudo rm /var/lib/dpkg/locksudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
                sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad
                sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status || sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
                sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
                sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
                sudo rm -rf /var/lib/dpkg/updates/*
                sudo rm -rf /var/lib/apt/lists
                sudo rm /var/cache/apt/*.bin
                sudo mkdir /var/lib/apt/lists
                sudo mkdir /var/lib/apt/lists/partial
                sudo apt-get upgrade





                share|improve this answer























                  0












                  0








                  0






                  Run following commands: I got a fix through it.



                  sudo rm /var/lib/apt/lists/lock
                  sudo rm /var/cache/apt/archives/lock
                  sudo rm /var/lib/dpkg/locksudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
                  sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad
                  sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status || sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
                  sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
                  sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
                  sudo rm -rf /var/lib/dpkg/updates/*
                  sudo rm -rf /var/lib/apt/lists
                  sudo rm /var/cache/apt/*.bin
                  sudo mkdir /var/lib/apt/lists
                  sudo mkdir /var/lib/apt/lists/partial
                  sudo apt-get upgrade





                  share|improve this answer












                  Run following commands: I got a fix through it.



                  sudo rm /var/lib/apt/lists/lock
                  sudo rm /var/cache/apt/archives/lock
                  sudo rm /var/lib/dpkg/locksudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
                  sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad
                  sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status || sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
                  sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
                  sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
                  sudo rm -rf /var/lib/dpkg/updates/*
                  sudo rm -rf /var/lib/apt/lists
                  sudo rm /var/cache/apt/*.bin
                  sudo mkdir /var/lib/apt/lists
                  sudo mkdir /var/lib/apt/lists/partial
                  sudo apt-get upgrade






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 21 '18 at 5:04









                  Fahad Naeem

                  138116




                  138116



























                      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.





                      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%2funix.stackexchange.com%2fquestions%2f193169%2fapt-get-install-ends-with-segmentation-fault%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 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?