[opensuse] Update from 42.2 to 42.3 issue
System is bogged down because of PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum What the heck is this? Can barely send this email Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Den 2017-07-27 kl. 23:59, skrev Patrick Shanahan:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it? he is running kde3 and tracker is the indexing option, iirc
Isn't it the gnome semantic search project? https://wiki.gnome.org/Projects/Tracker -- /bengan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 02:59 PM, Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
Ah, jeeze... What ever happened to the list etiquette of mentioning your particulars when asking for help on the mailing list? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [07-27-17 18:29]:
On 07/27/2017 02:59 PM, Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
Ah, jeeze...
What ever happened to the list etiquette of mentioning your particulars when asking for help on the mailing list?
he did mention kde3 and when I see that, I walk right on by and do not wait on the corner :^p -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 06:28 PM, John Andersen wrote:
On 07/27/2017 02:59 PM, Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
Ah, jeeze...
What ever happened to the list etiquette of mentioning your particulars when asking for help on the mailing list?
I just did an update from 42.2 to 42.3. There is nothing "particular" about my installation that needed mentioning. I am not running kde3. I may have "something" installed that the update thought I needed "tracker" for but tracker was not installed on 42.2. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 05:59 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Hounschell <markh@compro.net> [07-28-17 09:18]:
On 07/27/2017 05:59 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
sorry, old failing memory. I saw it here (earlier post): I have been using it forever. From 7.0 through Leap 42.2. It is the only font for konsole as far as I am concerned. For Leap 42.2 it is in repositories/KDE:/KDE3/openSUSE_Leap_42.2/x86_64. Bit don't find one in repositories/KDE:/KDE3/openSUSE_Leap_42.3/x86_64. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/28/2017 09:42 AM, Patrick Shanahan wrote:
* Mark Hounschell <markh@compro.net> [07-28-17 09:18]:
On 07/27/2017 05:59 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
sorry, old failing memory. I saw it here (earlier post):
I have been using it forever. From 7.0 through Leap 42.2. It is the only font for konsole as far as I am concerned.
For Leap 42.2 it is in repositories/KDE:/KDE3/openSUSE_Leap_42.2/x86_64. Bit don't find one in repositories/KDE:/KDE3/openSUSE_Leap_42.3/x86_64.
I installed that font after the upgrade because the upgrade removed the 42.2 font package. I don't understand why the misc-console-font is not part of the DIST. It works and is a very nice font for konsole. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 28 juli 2017 15:16:36 CEST schreef Mark Hounschell:
On 07/27/2017 05:59 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum>>>> What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
Mark The 'tracker' stuff is GNOME related. Comparable to Baloo on KDE.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Hounschell composed on 2017-07-28 09:16 (UTC-0400):
Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
https://lists.opensuse.org/opensuse/2017-07/msg01035.html is why. misc-console-font is a (repeatedly rebuilt) relic of KDE3, not a part of KDE4 or Plasma5, inexplicably required AFAICT only by KDE3's Konsole. Konsole's 4 & 5 are perfectly happy running the distro's fontconfig default monospace font. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/28/2017 10:59 AM, Felix Miata wrote:
Mark Hounschell composed on 2017-07-28 09:16 (UTC-0400):
Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
https://lists.opensuse.org/opensuse/2017-07/msg01035.html is why.
misc-console-font is a (repeatedly rebuilt) relic of KDE3, not a part of KDE4 or Plasma5, inexplicably required AFAICT only by KDE3's Konsole. Konsole's 4 & 5 are perfectly happy running the distro's fontconfig default monospace font.
So because I prefer that font you assume I am running KDE3? And Konsole's 4 & 5 may be perfectly happy running the distro's fontconfig default monospace font but it's just not as good as the misc-console-font IMO. Try it and see. In any case that was another thread. This thread was about systemd-coredump and tracker being the cause. Why was tracker installed during the update? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Hounschell <markh@compro.net> [07-28-17 11:06]:
On 07/28/2017 10:59 AM, Felix Miata wrote:
Mark Hounschell composed on 2017-07-28 09:16 (UTC-0400):
Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Why would you all think so?
https://lists.opensuse.org/opensuse/2017-07/msg01035.html is why.
misc-console-font is a (repeatedly rebuilt) relic of KDE3, not a part of KDE4 or Plasma5, inexplicably required AFAICT only by KDE3's Konsole. Konsole's 4 & 5 are perfectly happy running the distro's fontconfig default monospace font.
So because I prefer that font you assume I am running KDE3? And Konsole's 4 & 5 may be perfectly happy running the distro's fontconfig default monospace font but it's just not as good as the misc-console-font IMO. Try it and see.
why on earth are you still ranting about kde3? I explained my misunderstand. there not no necessity for further discussion re; your running kde3. FULL STOP. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 05:59 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [07-27-17 17:56]:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
he is running kde3 and tracker is the indexing option, iirc
I am NOT running kde3. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 04:59 PM, Patrick Shanahan wrote:
he is running kde3 and tracker is the indexing option, iirc
Never heard of it in KDE3, after more than a decade, I would have expected to run across it. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/27/2017 05:55 PM, John Andersen wrote:
On 07/27/2017 01:29 PM, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
Looks like you were dumping core repeatedly. What is this "tracker" stuff you allude to, and how did you get rid of it?
I just removed and taboo'd the following rpms that the update installed. tracker-1.8.3-1.4.x86_64 tracker-miner-files-1.8.3-1.4.x86_64 tracker-lang-1.8.3-1.4.noarch nautilus-extension-tracker-tags-1.8.3-1.5.x86_64 gnome-documents_books-common-3.20.1-3.26.x86_64 gnome-documents-3.20.1-3.26.x86_64 gnome-documents-lang-3.20.1-3.26.noarch gnome-shell-search-provider-documents-3.20.1-3.26.x86_64 Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/07/2017 22:29, Mark Hounschell wrote:
On 07/27/2017 03:09 PM, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
Don't understand why but as soon as I got rid of all the "tracker" stuff, it went away.
Mark
You need to search for the error in the systemd logs, the easiest way is use yast systemd journal. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-27 21:09, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Some process is crashing and restarting. A core dump is being saved to disk for study by a developer. On the system log you will get a log entry stating which process crashed and perhaps why, so look in the log and find out, then impede it restarting. The system slows down because, if I recall correctly, systemd compresses the core dumps, to save some space (they can be huge). -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 07/27/2017 08:02 PM, Carlos E. R. wrote:
On 2017-07-27 21:09, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Some process is crashing and restarting. A core dump is being saved to disk for study by a developer. On the system log you will get a log entry stating which process crashed and perhaps why, so look in the log and find out, then impede it restarting.
dmesg showed nothing abnormal. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-28 15:21, Mark Hounschell wrote:
On 07/27/2017 08:02 PM, Carlos E. R. wrote:
On 2017-07-27 21:09, Mark Hounschell wrote:
6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Some process is crashing and restarting. A core dump is being saved to disk for study by a developer. On the system log you will get a log entry stating which process crashed and perhaps why, so look in the log and find out, then impede it restarting.
dmesg showed nothing abnormal.
Not dmesg. journalctl | grep coredum Example: cer@Isengard:~> journalctl | grep coredum Jan 11 04:40:38 Isengard systemd-coredump[4590]: Process 4587 (obconf) of user 1000 dumped core. Jan 11 04:40:54 Isengard systemd-coredump[4599]: Process 4596 (obconf) of user 1000 dumped core. Feb 05 04:32:26 Isengard systemd-coredump[6384]: Process 6345 (panel-15-system) of user 1000 dumped core. Then I look in detail around that timestamp and find more info, but this time I seek in syslog because I also keep it: <3.6> 2017-01-11T04:40:01.932293+01:00 Isengard systemd 1 - - Stopping User Manager for UID 0... <3.6> 2017-01-11T04:40:01.933641+01:00 Isengard systemd 4544 - - Stopped target Default. <3.6> 2017-01-11T04:40:01.934157+01:00 Isengard systemd 4544 - - Stopped target Basic System. <3.6> 2017-01-11T04:40:01.935194+01:00 Isengard systemd 4544 - - Stopped target Timers. <3.6> 2017-01-11T04:40:01.975561+01:00 Isengard systemd 4544 - - Reached target Shutdown. <3.6> 2017-01-11T04:40:01.976051+01:00 Isengard systemd 4544 - - Starting Exit the Session... <3.6> 2017-01-11T04:40:01.976427+01:00 Isengard systemd 4544 - - Stopped target Sockets. <3.6> 2017-01-11T04:40:01.976797+01:00 Isengard systemd 4544 - - Stopped target Paths. <3.6> 2017-01-11T04:40:02.000011+01:00 Isengard systemd 4544 - - Received SIGRTMIN+24 from PID 4572 (kill). <10.6> 2017-01-11T04:40:02.004232+01:00 Isengard systemd - - - pam_unix(systemd-user:session): session closed for user root <3.6> 2017-01-11T04:40:02.010475+01:00 Isengard systemd 1 - - Stopped User Manager for UID 0. <3.6> 2017-01-11T04:40:02.020141+01:00 Isengard systemd 1 - - Removed slice User Slice of root. <0.4> 2017-01-11T04:40:36.618668+01:00 Isengard kernel - - - [3028957.795445] show_signal_msg: 105 callbacks suppressed <0.6> 2017-01-11T04:40:36.618703+01:00 Isengard kernel - - - [3028957.795464] obconf[4587]: segfault at 0 ip 00007fae8eaa1486 sp 00007ffeace8d0a0 error 4 in libc-2.22.so[7fae8ea69000+19a000] <0.2> 2017-01-11T04:40:38.415747+01:00 Isengard systemd-coredump 4590 - - Process 4587 (obconf) of user 1000 dumped core. <0.6> 2017-01-11T04:40:53.054943+01:00 Isengard kernel - - - [3028974.232263] obconf[4596]: segfault at 0 ip 00007f7de6205486 sp 00007ffe51db24d0 error 4 in libc-2.22.so[7f7de61cd000+19a000] <0.2> 2017-01-11T04:40:54.843895+01:00 Isengard systemd-coredump 4599 - - Process 4596 (obconf) of user 1000 dumped core. <10.3> 2017-01-11T04:42:09.914187+01:00 Isengard gnomesu-pam-backend - - - gkr-pam: couldn't get the password from user: Critical error - immediate abort <10.3> 2017-01-11T04:42:09.916654+01:00 Isengard gnomesu-pam-backend - - - pam_unix(gnomesu-pam:auth): conversation failed <10.2> 2017-01-11T04:42:09.917253+01:00 Isengard gnomesu-pam-backend - - - pam_unix(gnomesu-pam:auth): auth could not identify password for [root] The important line would be this one: <0.6> 2017-01-11T04:40:36.618703+01:00 Isengard kernel - - - [3028957.795464] obconf[4587]: segfault at 0 ip 00007fae8eaa1486 sp 00007ffeace8d0a0 error 4 in libc-2.22.so[7fae8ea69000+19a000] A developer could find out what is wrong using the core file and that info. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 27/07/2017 21:09, Mark Hounschell wrote:
System is bogged down because of
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6237 root 20 0 118980 97324 2040 R 99.34 0.592 0:03.55 systemd-coredum 6198 root 20 0 119140 97568 2040 R 98.67 0.593 0:09.04 systemd-coredum 6217 root 20 0 118980 97508 2096 R 84.72 0.593 0:05.91 systemd-coredum 6197 root 20 0 119112 97604 2096 R 80.07 0.593 0:09.89 systemd-coredum 6238 root 20 0 119128 54760 2096 R 76.41 0.333 0:02.30 systemd-coredum 6173 root 20 0 119128 97536 2096 R 64.45 0.593 0:13.83 systemd-coredum 6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Mark
If you have intel graphics that aren't very recent then you might be having gpu hangs that trigger core dumps. See: https://bugzilla.suse.com/show_bug.cgi?id=1050256 Booting with nomodeset or removing drm-kmp-default, an update to fix this is running. Best regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Bengt Gördén -
Carlos E. R. -
Dave Plater -
David C. Rankin -
Felix Miata -
John Andersen -
Knurpht - Gertjan Lettink -
Mark Hounschell -
Patrick Shanahan