Libraries crash after installing experimental version of libc6
Clash Royale CLAN TAG#URR8PPP
My Debian system is not booting anymore after installing the experimental version of libc6.
I've got this message on boot:
/sbin/init: error while loading shared libraries: libsepol.so.1:
cannot open shared object file: No such file or directory
What can I do to get this resolved?
The error:
Error #2:
linux debian boot libraries glibc
edited Jan 24 at 7:03
G-Man
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
|
show 3 more comments
My Debian system is not booting anymore after installing the experimental version of libc6.
I've got this message on boot:
/sbin/init: error while loading shared libraries: libsepol.so.1:
cannot open shared object file: No such file or directory
What can I do to get this resolved?
The error:
Error #2:
linux debian boot libraries glibc
edited Jan 24 at 7:03
G-Man
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
1
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
1
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07
|
show 3 more comments
My Debian system is not booting anymore after installing the experimental version of libc6.
I've got this message on boot:
/sbin/init: error while loading shared libraries: libsepol.so.1:
cannot open shared object file: No such file or directory
What can I do to get this resolved?
The error:
Error #2:
linux debian boot libraries glibc
edited Jan 24 at 7:03
G-Man
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
My Debian system is not booting anymore after installing the experimental version of libc6.
I've got this message on boot:
/sbin/init: error while loading shared libraries: libsepol.so.1:
cannot open shared object file: No such file or directory
What can I do to get this resolved?
The error:
Error #2:
linux debian boot libraries glibc
linux debian boot libraries glibc
edited Jan 24 at 7:03
G-Man
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
edited Jan 24 at 7:03
G-Man
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
edited Jan 24 at 7:03
G-Man
13.1k93465
edited Jan 24 at 7:03
G-Man
13.1k93465
edited Jan 24 at 7:03
G-Man
13.1k93465
13.1k93465
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
asked Jan 13 '14 at 17:26
Stephan MeijerStephan Meijer
162
162
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
1
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
1
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07
|
show 3 more comments
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
1
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
1
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
1
1
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
1
1
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07
|
show 3 more comments
2 Answers
2
active
oldest
votes
You can try a chroot. boot a live USB and become root
sudo -i
Mount your old system at /mnt (change sda1 as needed)
mount /dev/sda1 /mnt
Prep the chroot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
mount -o bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/etc/resolv.conf
Enter the chroot
chroot /mnt /bin/bash
Assuming that goes well, remove the experimental repository and try running
apt-get update
apt-get -t stable install libc6-amd64 libc6-dev libc6-dbg
You may need to specify the old versions of those packages , see https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
Use apt-cache to search for the package versions
apt-cache search libc6-amd64
If all that fails, you probably need to consider backing up your data and re-installing.
edited Apr 13 '17 at 12:22
Community♦
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. trychroot /mnt
– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
add a comment |
What I did, was a fresh install. It felt like the only good solution.
I want to thank you all for your help!
Thanks!
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f109182%2flibraries-crash-after-installing-experimental-version-of-libc6%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
You can try a chroot. boot a live USB and become root
sudo -i
Mount your old system at /mnt (change sda1 as needed)
mount /dev/sda1 /mnt
Prep the chroot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
mount -o bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/etc/resolv.conf
Enter the chroot
chroot /mnt /bin/bash
Assuming that goes well, remove the experimental repository and try running
apt-get update
apt-get -t stable install libc6-amd64 libc6-dev libc6-dbg
You may need to specify the old versions of those packages , see https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
Use apt-cache to search for the package versions
apt-cache search libc6-amd64
If all that fails, you probably need to consider backing up your data and re-installing.
edited Apr 13 '17 at 12:22
Community♦
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. trychroot /mnt
– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
add a comment |
You can try a chroot. boot a live USB and become root
sudo -i
Mount your old system at /mnt (change sda1 as needed)
mount /dev/sda1 /mnt
Prep the chroot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
mount -o bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/etc/resolv.conf
Enter the chroot
chroot /mnt /bin/bash
Assuming that goes well, remove the experimental repository and try running
apt-get update
apt-get -t stable install libc6-amd64 libc6-dev libc6-dbg
You may need to specify the old versions of those packages , see https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
Use apt-cache to search for the package versions
apt-cache search libc6-amd64
If all that fails, you probably need to consider backing up your data and re-installing.
edited Apr 13 '17 at 12:22
Community♦
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. trychroot /mnt
– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
add a comment |
You can try a chroot. boot a live USB and become root
sudo -i
Mount your old system at /mnt (change sda1 as needed)
mount /dev/sda1 /mnt
Prep the chroot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
mount -o bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/etc/resolv.conf
Enter the chroot
chroot /mnt /bin/bash
Assuming that goes well, remove the experimental repository and try running
apt-get update
apt-get -t stable install libc6-amd64 libc6-dev libc6-dbg
You may need to specify the old versions of those packages , see https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
Use apt-cache to search for the package versions
apt-cache search libc6-amd64
If all that fails, you probably need to consider backing up your data and re-installing.
edited Apr 13 '17 at 12:22
Community♦
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
You can try a chroot. boot a live USB and become root
sudo -i
Mount your old system at /mnt (change sda1 as needed)
mount /dev/sda1 /mnt
Prep the chroot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /dev/pts /mnt/dev/pts
mount -o bind /sys /mnt/sys
cp /etc/resolv.conf /mnt/etc/resolv.conf
Enter the chroot
chroot /mnt /bin/bash
Assuming that goes well, remove the experimental repository and try running
apt-get update
apt-get -t stable install libc6-amd64 libc6-dev libc6-dbg
You may need to specify the old versions of those packages , see https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
Use apt-cache to search for the package versions
apt-cache search libc6-amd64
If all that fails, you probably need to consider backing up your data and re-installing.
edited Apr 13 '17 at 12:22
Community♦
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
edited Apr 13 '17 at 12:22
Community♦
1
edited Apr 13 '17 at 12:22
Community♦
1
edited Apr 13 '17 at 12:22
Community♦
1
1
answered Jan 13 '14 at 18:20
PantherPanther
846159
answered Jan 13 '14 at 18:20
PantherPanther
846159
answered Jan 13 '14 at 18:20
PantherPanther
846159
846159
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. trychroot /mnt
– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
add a comment |
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. trychroot /mnt
– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
This failed, error picture here: oi42.tinypic.com/35a4s5z.jpg
– Stephan Meijer
Jan 13 '14 at 18:43
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
See my update (there was a typo)
– Panther
Jan 13 '14 at 18:46
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Thanks, but still the same error while running "chroot /mnt /bin/bash"
– Stephan Meijer
Jan 13 '14 at 18:51
Can't be the same error, lol. try
chroot /mnt– Panther
Jan 13 '14 at 19:26
Can't be the same error, lol. try
chroot /mnt– Panther
Jan 13 '14 at 19:26
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
Looking at the second error, your best fix is to back up your data and do a fresh install. Your only other option would be to manually download, unpackage (extract) the .deb, and manually copy the files over to the proper locations in /mnt
– Panther
Jan 13 '14 at 20:47
add a comment |
What I did, was a fresh install. It felt like the only good solution.
I want to thank you all for your help!
Thanks!
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
add a comment |
What I did, was a fresh install. It felt like the only good solution.
I want to thank you all for your help!
Thanks!
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
add a comment |
What I did, was a fresh install. It felt like the only good solution.
I want to thank you all for your help!
Thanks!
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
What I did, was a fresh install. It felt like the only good solution.
I want to thank you all for your help!
Thanks!
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
answered Jan 26 '14 at 7:51
Stephan MeijerStephan Meijer
162
162
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f109182%2flibraries-crash-after-installing-experimental-version-of-libc6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
How did you install the libs? Support for experimental packages / libs is going to be very limited. You might be able to fix your problems with a chroot, but it might be easier to do a fresh install. I usually play with experimental things in a virtual machine (if at all) ;)
– Panther
Jan 13 '14 at 17:53
I followed stackoverflow.com/questions/10863613 , Add the following line to the file /etc/apt/sources.list: deb ftp.debian.org/debian experimental main Update your package database: apt-get update Install the eglibc package: apt-get -t experimental install libc6-amd64 libc6-dev libc6-dbg
– Stephan Meijer
Jan 13 '14 at 17:57
Do you know how to use a chroot ?
– Panther
Jan 13 '14 at 18:04
1
Good rule of thumb: don't upgrade libc6. Unless you need to. And you never need to.
– Faheem Mitha
Jan 13 '14 at 18:52
1
@StephanMeijer: The correct way to do that is backport it. And it looks pretty easy to backport.
– Faheem Mitha
Jan 13 '14 at 20:07