Every now and then, I get an error about plasma shell. The details are :"Executable: plasmashell PID 3108 Signal: Segmentaion fault (11) Time: ... When I try to report the bug, I can't because I can't recall what I was doing. It just happens no matter what. Has anyone else seen this? this is with KDE4 on 15.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-18 1:59 p.m., James Knott wrote:
Every now and then, I get an error about plasma shell. The details are :"Executable: plasmashell PID 3108 Signal: Segmentaion fault (11) Time: ...
When I try to report the bug, I can't because I can't recall what I was doing. It just happens no matter what.
Has anyone else seen this? this is with KDE4 on 15.1.
Do you have a coredump? Make sure to install systemd-coredump or otherwise unbreak default install so you can actually get a coredump. - Adam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@jknott.net> [08-18-19 13:11]:
On 2019-08-18 01:03 PM, Adam Majer wrote:
otherwise unbreak default install so you can actually get a coredump.
What the heck does that mean?
perhaps a language problem. maybe instead of "unbreak", deviate from the default install and install what is necessary to get a coredump. maybe coredump and company are not "default". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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 2019-08-18 7:08 p.m., James Knott wrote:
On 2019-08-18 01:03 PM, Adam Majer wrote:
otherwise unbreak default install so you can actually get a coredump.
What the heck does that mean?
Did you try to get a coredump without systemd-coredump? Also, all you need to do is look at $ cat /proc/sys/kernel/core_pattern That should be `core` or otherwise point to a core dumper program. Otherwise you will get no core file. Default system is broken because it doesn't write a sane value there but *assumes* systemd-coredump is present and when that is not, you just get nothing. - Adam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-18 01:22 PM, Adam Majer wrote:
That should be `core` or otherwise point to a core dumper program. Otherwise you will get no core file. Default system is broken because it doesn't write a sane value there but *assumes* systemd-coredump is present and when that is not, you just get nothing.
I'm sorry, but this is well beyond anything I'm familiar with. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-18 7:24 p.m., James Knott wrote:
On 2019-08-18 01:22 PM, Adam Majer wrote:
That should be `core` or otherwise point to a core dumper program. Otherwise you will get no core file. Default system is broken because it doesn't write a sane value there but *assumes* systemd-coredump is present and when that is not, you just get nothing.
I'm sorry, but this is well beyond anything I'm familiar with.
Just make sure that systemd-coredump is installed. - Adam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-18 02:22 PM, Adam Majer wrote:
I'm sorry, but this is well beyond anything I'm familiar with. Just make sure that systemd-coredump is installed.
It's installed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-18 02:24 PM, James Knott wrote:
On 2019-08-18 02:22 PM, Adam Majer wrote:
I'm sorry, but this is well beyond anything I'm familiar with. Just make sure that systemd-coredump is installed. It's installed.
Core dumped. ;-) https://www.youtube.com/watch?v=xIuUEwat6aM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/08/2019 20.24, James Knott wrote:
On 2019-08-18 02:22 PM, Adam Majer wrote:
I'm sorry, but this is well beyond anything I'm familiar with. Just make sure that systemd-coredump is installed.
It's installed.
It is normally installed, but actually dumping core is disabled. "Dump core" refers to an automatic procedure that copies all the memory used by a program to a file, so that developers can study that copy after the crash. Only once I have seen it used. The file can be huge, and bugzilla will not take it. Another useful thing is a backtrace, which needs the -debug rpms be installed of the application that crashes and all the libraries it uses. I'm not sure if this requirement is needed for coredumps. Run this command as root first: Telcontar:~ # coredumpctl No coredumps found. Telcontar:~ # If you get that result, forget it, your crashes do not produce them. If you get something like this (different names): TIME PID UID GID SIG COREFILE EXE ... Fri 2019-08-02 11:04:59 CEST 4205 1000 100 11 none /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Sat 2019-08-10 10:52:04 CEST 925 1000 100 11 missing /usr/lib64/kodi/kodi-x11 Thu 2019-08-15 18:09:16 CEST 6165 1000 100 11 none Kodi_MovistarTV Fri 2019-08-16 01:18:55 CEST 9135 1000 100 11 present /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr we can continue. For example, I can use: coredumpctl info 9143 which gives information about that process crash: ... Thu 2019-08-15 18:09:16 CEST 6165 1000 100 11 none Kodi_MovistarTV Fri 2019-08-16 01:18:55 CEST 9135 1000 100 11 present /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Isengard:~ # coredumpctl info 9135 PID: 9135 (Kodi_MovistarTV) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Fri 2019-08-16 01:18:55 CEST (3 days ago) Command Line: ./Kodi_MovistarTV_Server.pvr -d:/home/cer/Fusion Executable: /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (cer) Boot ID: a7c4b7e16b264f379b931544ca66c0ee Machine ID: af5da4da5956dc08183725bc583a0cd5 Hostname: Isengard Storage: /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000 Message: Process 9135 (Kodi_MovistarTV) of user 1000 dumped core. Isengard:~ # The next step would be this: Isengard:~ # coredumpctl dump 9135 --output somefile PID: 9135 (Kodi_MovistarTV) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Fri 2019-08-16 01:18:55 CEST (3 days ago) Command Line: ./Kodi_MovistarTV_Server.pvr -d:/home/cer/Fusion Executable: /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (cer) Boot ID: a7c4b7e16b264f379b931544ca66c0ee Machine ID: af5da4da5956dc08183725bc583a0cd5 Hostname: Isengard Storage: /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000 Message: Process 9135 (Kodi_MovistarTV) of user 1000 dumped core. Failed to decompress /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000: Protocol not supported Isengard:~ # Does not work this time, but it tells us where they are stored: /var/lib/systemd/coredump/ So, go on, do those steps and we'll see. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 19/08/2019 14.48, James Knott wrote:
On 2019-08-19 08:28 AM, Carlos E. R. wrote:
If you get that result, forget it, your crashes do not produce them.
That is what I get.
Then try what Daniel Bauer tried in thread "[opensuse] is ubuntu better than opensuse 15.1?": ]> The last thing I did was changing KDE system settings -> display -> compositor, "Ausgabemodul" from OpenGL 2.0 to 3.1. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-19 08:54 AM, Carlos E. R. wrote:
The last thing I did was changing KDE system settings -> display -> compositor, "Ausgabemodul" from OpenGL 2.0 to 3.1.
Done. BTW, what the heck is "Ausgabemodul"? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/08/2019 15.04, James Knott wrote:
On 2019-08-19 08:54 AM, Carlos E. R. wrote:
The last thing I did was changing KDE system settings -> display -> compositor, "Ausgabemodul" from OpenGL 2.0 to 3.1.
Done.
BTW, what the heck is "Ausgabemodul"?
I don't know. German, I guess. output module or so. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (4)
-
Adam Majer -
Carlos E. R. -
James Knott -
Patrick Shanahan