[SOLVED] segfault-problems

pan64 · 05-12-2018, 11:59 AM

libc.so is more or less the soul of the system (next to the kernel itself). You added a lot of apt repositories, installed a huge amount of whatever which may or may not rely on the same libc.so (=compiled on/for a [slightly] different system). Now when they try to run they try to use the only available libc.so and reclaim it is not compatible (=segfaults).
To analyze this you may need to check what other libs were in use and probably you will find the real reason (=the one [or probably more?] which are incompatible with the actual system).

ondoho · 05-12-2018, 12:03 PM

you still have that omnous "debian xenial" in there.
also, after each change to the sources you have to run

Code:

apt update
apt upgrade

again (*).
not sure what would happen if libc needed to be downgraded or changed to a different version.
not sure if that would happen automatically with an 'apt upgrade'. worth a try though.

(*) these are the command line versions, but you can achieve the same with a software management tool, e.g. synaptic or the infamous pere ubu software center...

_roman_ · 05-12-2018, 12:25 PM

Quote:

What I don´t understand is why I keep getting those libc-2.23.so-related segfaults in spite of the fact that I re-installed libc-2.23.so. So this lib should be O.K now....

The issue is about how the other packages were compiled with. A big drawback of binary distros.

So reinstalling a now incompatible libc will not solve anything.

--

usually revert to a well known working state, if that is even possible with a binary distro

or submit a bug report and wait until they upload a fixed package / update the repository with a working one.

--

and some software just randomly segfaults, especially opera webbrowser here

--

for a binary distro it is always advised to have his own home partition. + check double when you do a reinstall, to not mix up partitions.

pan64 · 05-13-2018, 12:31 AM

Quote:

Originally Posted by _roman_

So reinstalling a now incompatible libc will not solve anything.

You are right, just one comment: usually libc is ok, the others are incompatible with it. Replacing libc is not recommended and [can be] dangerous.

Rosika · 05-13-2018, 10:11 AM

Hi all,

tnx for the feedback.

@ pan64:

Quote:

Now when they try to run they try to use the only available libc.so and reclaim it is not compatible (=segfaults).
To analyze this you may need to check what other libs were in use and probably you will find the real reason (=the one [or probably more?] which are incompatible with the actual system).

O.K., now I understand what´s going on here. Yet analyzing and checking what other libs were in use seems difficult for me to do.

Quote:

Replacing libc is not recommended and [can be] dangerous.

What I did was

Code:

sudo apt-get --reinstall install libc6

and thus reinstalled what was already there. I hope that´s O.K.

@ ondoho:
The one thing I can do now is take out

Code:

http://download.virtualbox.org/virtualbox/debian xenial contrib

Then no "debian xenial" should be left over.

@ _roman_:

Quote:

and some software just randomly segfaults, especially opera webbrowser here

Yeah, that´s the difficult part. It´s not easy, or better: impossible, to reproduce that error that way.

Anyhow, yesterday I didn´t get any segfaults, which was quite a surprise and which I was was very glad about.

The only message in this respect I got today (so far) was

Code:

May 13 13:54:53 rosika-Lenovo-H520e kernel: [ 1466.661692] Web Content[6325]: segfault at 0 ip 00007fceb90a5f07 sp 00007ffd4a964c90 error 6 in libmozsandbox.so[7fceb9098000+1f000]

But that has other reasons. There are problems running the new firefox-version (60.0) within firejail.
See also
https://firejail.wordpress.com/support/ and
https://github.com/netblue30/firejail/issues/1940

pan64 · 05-13-2018, 10:31 AM

Quote:

Originally Posted by Rosika

What I did was

Code:

sudo apt-get --reinstall install libc6

and thus reinstalled what was already there. I hope that´s O.K.

Yes, that is ok.

Removing a line from sources.list will not solve anything. It was there and based on that some changes were applied (= packages installed). Theoretically you need to revert those changes, but I think noone really knows how to do that (what packages should be removed, replaced ...)

And especially Oracle suggested that line, therefore I think that is not a problem at all. (and what about codezen and all the other files in sources.list.d?)

Rosika · 05-13-2018, 10:48 AM

Hi,

Quote:

Removing a line from sources.list will not solve anything

Well, what I did was taking out sources from "applications and updates" (GUI-based, under "settings").
After that a "sudo apt-get update" was neccessary of course).
So, as already said, these are my current seetings:

Code:

- von Canonical unterstützte freie und quelloffene Software (main)
- Von der Ubuntu-Gemeinschaft betreute freie und quelloffene Software (universe)
- Proprietäre Gerätetreiber (restricted)
- Rechtlich eingeschränkte Software
(I believe those were the defaults after installation)

plus: (further programmes)

- http://download.virtualbox.org/virtualbox/debian xenial contrib
- http://ppa.launchpad.net/wireshark-dev/stable/ubuntu xenial main

The combined output of /etc/apt/sources.list and /etc/apt/sources.list.d results in:

Code:

# deb cdrom:[Lubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1)]/ xenial main multiverse restricted universe

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://de.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://de.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://de.archive.ubuntu.com/ubuntu/ xenial universe
deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates universe
# deb-src http://de.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://de.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://de.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu xenial partner
# deb-src http://archive.canonical.com/ubuntu xenial partner

deb http://de.archive.ubuntu.com/ubuntu/ xenial-security main restricted
# deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://de.archive.ubuntu.com/ubuntu/ xenial-security universe
# deb-src http://security.ubuntu.com/ubuntu xenial-security universe
deb http://de.archive.ubuntu.com/ubuntu/ xenial-security multiverse
# deb-src http://security.ubuntu.com/ubuntu xenial-security multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu xenial main universe
# deb-src http://de.archive.ubuntu.com/ubuntu xenial main universe

# deb http://codezen.org/debian xenial main
# deb-src http://codezen.org/debian xenial main
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
# deb-src http://download.virtualbox.org/virtualbox/debian xenial contrib
insgesamt 88
-rw-r--r-- 1 root root 144 Mai 12 14:19 arkose-devel-ubuntu-stable-xenial.list
-rw-r--r-- 1 root root 144 Mai 12 14:19 arkose-devel-ubuntu-stable-xenial.list.save
-rw-r--r-- 1 root root 136 Mai 12 14:19 atareao-ubuntu-atareao-xenial.list
-rw-r--r-- 1 root root 136 Mai 12 14:19 atareao-ubuntu-atareao-xenial.list.save
-rw-r--r-- 1 root root 158 Mai 12 14:19 format-junkie-team-ubuntu-release-xenial.list
-rw-r--r-- 1 root root 158 Mai 12 14:19 format-junkie-team-ubuntu-release-xenial.list.save
-rw-r--r-- 1 root root 174 Mai 12 14:19 maarten-baert-ubuntu-simplescreenrecorder-xenial.list
-rw-r--r-- 1 root root 174 Mai 12 14:19 maarten-baert-ubuntu-simplescreenrecorder-xenial.list.save
-rw-r--r-- 1 root root 191 Mai 12 14:19 midori-ubuntu-ppa-xenial.list
-rw-r--r-- 1 root root 191 Mai 12 14:19 midori-ubuntu-ppa-xenial.list.save
-rw-r--r-- 1 root root 136 Mai 12 14:19 nemh-ubuntu-systemback-xenial.list
-rw-r--r-- 1 root root 136 Mai 12 14:19 nemh-ubuntu-systemback-xenial.list.save
-rw-r--r-- 1 root root   0 Aug  7  2016 nvbn-rm-ubuntu-ppa-xenial.list
-rw-r--r-- 1 root root   0 Aug  7  2016 nvbn-rm-ubuntu-ppa-xenial.list.save
-rw-r--r-- 1 root root 134 Mai 12 14:19 teejee2008-ubuntu-ppa-xenial.list
-rw-r--r-- 1 root root 134 Mai 12 14:19 teejee2008-ubuntu-ppa-xenial.list.save
-rw-r--r-- 1 root root 152 Mai 12 14:19 ubuntu-x-swat-ubuntu-x-updates-xenial.list
-rw-r--r-- 1 root root 152 Mai 12 14:19 ubuntu-x-swat-ubuntu-x-updates-xenial.list.save
-rw-r--r-- 1 root root   0 Aug 10  2016 vincent-c-ubuntu-nevernote-xenial.list
-rw-r--r-- 1 root root   0 Aug 10  2016 vincent-c-ubuntu-nevernote-xenial.list.save
-rw-r--r-- 1 root root   0 Nov  8  2016 wallch-ubuntu-wallch-4_0-xenial.list
-rw-r--r-- 1 root root   0 Nov  8  2016 wallch-ubuntu-wallch-4_0-xenial.list.save
-rw-r--r-- 1 root root   0 Nov  8  2016 wallch-ubuntu-wallch-daily-xenial.list
-rw-r--r-- 1 root root   0 Nov  8  2016 wallch-ubuntu-wallch-daily-xenial.list.save
-rw-r--r-- 1 root root 136 Mai 12 14:19 webkit-team-ubuntu-ppa-xenial.list
-rw-r--r-- 1 root root 134 Mai 12 14:19 webkit-team-ubuntu-ppa-xenial.list.save
-rw-r--r-- 1 root root 144 Mai 12 14:19 wireshark-dev-ubuntu-stable-xenial.list
-rw-r--r-- 1 root root 144 Mai 12 14:19 wireshark-dev-ubuntu-stable-xenial.list.save
-rw-r--r-- 1 root root 134 Mai 12 14:19 zerkalica-ubuntu-main-xenial.list
-rw-r--r-- 1 root root 134 Mai 12 14:19 zerkalica-ubuntu-main-xenial.list.save

codezen is commented out now.

pan64 · 05-13-2018, 10:56 AM

I think you still do not fully understand how it works.
sources.list and the files in sources.list.d contains locations to repositories. Nothing more. Editing/modifying those files has no any effect on the system.
apt-get update will process this list and downloads the content of the repositories (obviously some index files and similar will be created too). Your system has still not been changed, just now it knows the content of the specified repositories.
apt-get install will install packages - including its dependencies - therefore it will modify the system. Also apt-get upgrade and apt-get remove may change the system.

hydrurga · 05-13-2018, 10:58 AM

Merely addressing the previous post by Rosika, just a note that if you install inxi and then run:

Code:

inxi -r

then it gives you a nice listing of all the active repositories.

Rosika · 05-13-2018, 11:12 AM

Hi,

@ pan64:

Tnx for the clarification.
apt-get update, apt-get install, apt-get upgrade and apt-get remove are known to me.
What I wasn´t sure of was the effect they take on sources.list and the files in sources.list.d.

@ hydrurga:

Fine.
inxi-r gives me the following output:

Code:

inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://de.archive.ubuntu.com/ubuntu/ xenial main restricted
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
           deb http://de.archive.ubuntu.com/ubuntu/ xenial universe
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates universe
           deb http://de.archive.ubuntu.com/ubuntu/ xenial multiverse
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-security main restricted
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-security universe
           deb http://de.archive.ubuntu.com/ubuntu/ xenial-security multiverse
           deb http://download.virtualbox.org/virtualbox/debian xenial contrib
           Active apt sources in file: /etc/apt/sources.list.d/wireshark-dev-ubuntu-stable-xenial.list
           deb http://ppa.launchpad.net/wireshark-dev/stable/ubuntu xenial main

hazel · 05-13-2018, 11:44 AM

Apt-get commands have no effect at all on the sources lists in /etc/apt. They read the lists to find out where to go for software, but they can't modify them. You can only do that by hand-editing them.

That goes for all the configuration files in the /etc tree. They tell the programs how to work but it's up to you how you maintain them. Default versions are installed along with the programs they serve. If you modify these, for example by adding extra apt repositories, then you are responsible for any problems that causes.

hydrurga · 05-13-2018, 12:05 PM

Quote:

Originally Posted by hazel

Apt-get commands have no effect at all on the sources lists in /etc/apt. They read the lists to find out where to go for software, but they can't modify them. You can only do that by hand-editing them.

That goes for all the configuration files in the /etc tree. They tell the programs how to work but it's up to you how you maintain them. Default versions are installed along with the programs they serve. If you modify these, for example by adding extra apt repositories, then you are responsible for any problems that causes.

Agreed, Hazel, but the sources lists do not need to be hand-edited in many cases. Some programs, such as Mint's Software Sources, provide a GUI which manipulates the sources lists. The add-apt-repository script also does so.

hazel · 05-13-2018, 12:20 PM

Quote:

Originally Posted by hydrurga

Agreed, Hazel, but the sources lists do not need to be hand-edited in many cases. Some programs, such as Mint's Software Sources, provide a GUI which manipulates the sources lists. The add-apt-repository script also does so.

I wasn't aware of that, but now that I have read your description, I think it's a very bad idea. Graphical configuration tools are fine for helping to reconfigure the user interface, but basic system configuration files should not be modified except by people who know what they are doing. This whole thread is an illustration of that. Having to do it in a text editor makes you aware of the seriousness of your action. It's like the difference between handing over actual money for what you buy and just presenting a plastic card. Just my

ondoho · 05-14-2018, 01:17 AM

Rosika:
just to clarify what others have been trying to explain:
you had the "bad" soources in your lists (how you added them, via gui or commandline, doesn't matter).
after an update, you did an upgrade (*), which will upgrade all installed softwares to the newest versions provided by those sources.
so from that moment on, your system might be poisoned already.
personally, i think that is what you're experiencing.
it is really really difficult to undo that.

(*) https://www.startpage.com/do/dsearch...te+and+upgrade

Rosika · 05-14-2018, 06:49 AM

Hi all,

tnx for the clarification.
I think I´m aware of the issues now.
Alas it seems there´s not a lot to be done now.

@ ondoho:

Quote:

it is really really difficult to undo that

I see.
Well, as I said: worst case scenario for me is to reinstall the whole system. But I thhink I defer that as long as possible in order to avoid having to re-install all programmes. That would be a bit of a hassle due to the fact that I´ve got just a web-stick as sole internet-connection....
In the meantime I´ll keep an eye on error-messages in syslog and look how things develop.

Thanks again to all of you for your help.