Hello everyone, Of course, not generating a core-dump allows one to honorably get out of the thermal envelope, but the system always loses time incomprehensibly from time to time. I had the opportunity to investigate a little more today and it seems to me that it was the "tracker" software that was involved. Here is an excerpt from journalctrl, theses lines being repeated a lot of time : « févr. 02 18:28:35 lin-pat org.freedesktop.Tracker1.Miner.Extract[4991]: (tracker-extract:21230): Tracker-WARNING **: Task 2, error: Unable to insert multiple values for subject `urn:uuid:7979f192-9815-e144-ad9c-bcd5c872babe' and single valued property `nie:contentCreated' (old_value: '<untransformable>', new value: '<untransformable>') févr. 02 18:28:35 lin-pat org.freedesktop.Tracker1.Miner.Extract[4991]: Sparql was: » I simply deleted this software after watching, of course, what else it could do to generate core-dump. Patrick Joke: I thought I was a victim of a virus or a web page doing "bitcoin extraction" (-: -------------------------------------------------- Le samedi 27 janvier 2018, Patrick Serru a écrit :
Hello koga, hello all,
I thank you, Koga, for this first aid solution that worked well. I have now to find which software is involved in that. For sure, it is related to the disk IO, because it happened again after a file saving. And I got a lot of IO error yesturday, running rsync in TTY1 while the disk is nearly full.
I tryed this commands, looking for the faulty programm: sudo unxz /var/ ... /coredump/core.tracker-extract.1000 ... xz sudo gdb -c /var/lib/systemd/coredump/core.tracker-extract.1000 ... ... Missing separate debuginfo for the main executable file Try: zypper install -C "debuginfo(build-id)=ae95e08ae9f ... 0f" Core was generated by `/usr/lib/tracker-extract'. Program terminated with signal SIGSYS, Bad system call. #0 0x00007f3330561d97 in ?? () [Current thread is 1 (LWP 30247)]
sudo zypper install -C "debuginfo(build-id)=ae95e08ae9f ... 0f" ... Aucun fournisseur de 'debuginfo(build-id)=ae95e08ae9f ... 0f' trouvé. ['--plus-content debug'?] ...
The core dump does not look usefull without the executable of the faulty program ! I have 6 SATA connector and when I use some of them, I have IO errors. So, it could be a system bug bug very hard to find out because it very rarely happen, and unfortunatly, I am one of the elected to experience it !
Sincerly,
Patrick ----------------------
Le vendredi 26 janvier 2018, koga@users.sourceforge.jp a écrit :
Hello Patrick,
It seems to me that it is not KDE3 issue but systemd. systemd-coredump is one of systemd function. You should set "Storage=none" in [Coredump] section on your /etc/systemd/coredump.conf if you do not want to dump cores.
See also: https://www.freedesktop.org/software/systemd/man/coredump.conf.html https://wiki.archlinux.org/index.php/Core_dump
Also you might have to investigate what process has crashed to get rid of problems. You can find core list by "coredumpctl list".
Good luck, koga
This is the reply to ... "[opensuse-kde3] BUG in KDE3 ? (Oups !)" Mr./Ms. Patrick Serru <patrik@serru.net> wrote on 2018-01-26 11:30:17.: --------------------------------------------------------------------- Message-ID: <201801252130.17457@----Apocryphe---->
Hello all,
I have a problem difficult to specify. I made a backup of my home directory yesterday. Today, after a few hours of operation, the processor started heating. This is not the first time this has happened (known solution!). A launch of ksysguard allows me to see that "systemd-coredum" uses 100% of the resources and renews itself permanently. Then, I kill X, and things calm down. When I log in as kde3 root, there is no problem. But every time I log in as a user: thermal runaway. Once restored my personal directory from yesterday, NO MORE PROBLEM.
After the last restoration of my personal directory, I went back to where I was, considering the incident as closed. All of today's work was concentrated in a repertoire. So, I copied this directory as root, out of X and with the help of rsync, and then, again thermal runaway once the kde3 user cession re-opened:!
For information, yesterday's repertoire (on which I worked) was 15.4 MB (16,164,103) and after today's work it was 50.1 MB (52,510,297). The system partition is 58.9 GB and is 87% occupied.
I am conviced that a deamond like ksysguardd is invloved, but i'm really not sure.
If you have an idea on how to find where it comes from, tell me, please.
Thank you for the attention you paid to this mail.
Patrick Serru
Edit: < NO MORE PROBLEM > in stead of < MORE PROBLEM >
-- koga@users.sourceforge.jp
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org