[opensuse] How to abort swiftly the shutdown process kde plasma
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down. How can I (once the crash happens) nearly immediately block the shutdownprocess of plasma? (I am using X, not wayland). Is there a key combination or some shortcut? Must be a fast one, you have about 10 seconds from the crash to the shutdown. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 15 Jul 2019, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
Is it possible to reproduce the segfault by just dropping to run-levels 1 or 3? Roger -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 15 luglio 2019 08:59:11 CEST, Roger Price ha scritto:
On Mon, 15 Jul 2019, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
Is it possible to reproduce the segfault by just dropping to run-levels 1 or 3?
Roger Ok, this is a very ignorant question... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
By itself the segfault produces after clicking on shutdown. If I am going to runlevel 3, I would loose the konqi debug info anyway, would I? I can have a try but where would I request runlevel 3, in a terminal or would I go for it with a tty1 e.g. ? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [07-15-19 08:08]:
In data lunedì 15 luglio 2019 08:59:11 CEST, Roger Price ha scritto:
On Mon, 15 Jul 2019, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
Is it possible to reproduce the segfault by just dropping to run-levels 1 or 3?
Roger Ok, this is a very ignorant question... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
By itself the segfault produces after clicking on shutdown. If I am going to runlevel 3, I would loose the konqi debug info anyway, would I? I can have a try but where would I request runlevel 3, in a terminal or would I go for it with a tty1 e.g. ?
does the segfault produce a coredump? you can still go to runlevels or could when I last tried: init 3 or you can use the systemd cmds systemctl isolate multi-user (equates to runlevel 3/init 3) -- (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
In data lunedì 15 luglio 2019 15:13:41 CEST, Patrick Shanahan ha scritto:
* stakanov <stakanov@eclipso.eu> [07-15-19 08:08]:
In data lunedì 15 luglio 2019 08:59:11 CEST, Roger Price ha scritto:
On Mon, 15 Jul 2019, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
Is it possible to reproduce the segfault by just dropping to run-levels 1 or 3?
Roger
Ok, this is a very ignorant question... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
By itself the segfault produces after clicking on shutdown. If I am going to runlevel 3, I would loose the konqi debug info anyway, would I? I can have a try but where would I request runlevel 3, in a terminal or would I go for it with a tty1 e.g. ?
does the segfault produce a coredump?
you can still go to runlevels or could when I last tried: init 3 or you can use the systemd cmds systemctl isolate multi-user (equates to runlevel 3/init 3) This is a good question. I would guess no, journalctl does not mention the incident, thus it goes to the userspace (?), but if I "set" it to produce a core dump, no matter what, it might. IF I well understood (and that is a mouth full) you have to "set" systemd to coredump for certain programs, especially if the coredump is small in size.
It would be ideal to block the process of shutdown, because konqi is already up and running. I would have the time I think to block it, either with a key combo, or with a command. But, unfortunately, I am ignorant on what is the way to "freeze" the process in plasma. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 15 Jul 2019, stakanov wrote:
... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
According to its man page, << telinit may be used to change the SysV system runlevel. Since the concept of SysV runlevels is obsolete the runlevel requests will be transparently translated into systemd unit activation requests. >> The options are: 0 Power-off the machine. This is translated into an activation request for poweroff.target and is equivalent to systemctl poweroff. 2,3,4,5 Change the SysV runlevel. This is translated into an activation request for runlevel2.target, runlevel3.target, ... and is equivalent to systemctl isolate runlevel2.target, systemctl isolate runlevel3.target, ... 1,s,S Change into system rescue mode. This is translated into an activation request for rescue.target and is equivalent to systemctl rescue. Roger -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 15 Jul 2019, stakanov wrote:
... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
According to its man page, << telinit may be used to change the SysV system runlevel. Since the concept of SysV runlevels is obsolete the runlevel requests will be transparently translated into systemd unit activation requests. >>
The options are:
0 Power-off the machine. This is translated into an activation request for poweroff.target and is equivalent to systemctl poweroff.
2,3,4,5 Change the SysV runlevel. This is translated into an activation request for runlevel2.target, runlevel3.target, ... and is equivalent to systemctl isolate runlevel2.target, systemctl isolate runlevel3.target, ...
1,s,S Change into system rescue mode. This is translated into an activation request for rescue.target and is equivalent to systemctl rescue.
Roger O.K. I am learning quite a lot now. The ideal would be to tell systemd to stop the process right away. That way I would get an ordered bugreport from konqi, address or not, I will be able to open a bug report if applicable. I will try to read in the man pages. I would suspect that plasma simply calls
In data lunedì 15 luglio 2019 16:38:48 CEST, Roger Price ha scritto: the systemctl service in order to do as of above. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 15. Juli 2019, 14:07:55 CEST schrieb stakanov:
Ok, this is a very ignorant question... is it still possible as before to go for runlevels? I thought this was not true any more since systemd?
There is the package systemd-sysvinit , which describes itself as "Drop-in replacement of System V init tools." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 15 luglio 2019 18:18:36 CEST, Markus Koßmann ha scritto:
Am Montag, 15. Juli 2019, 14:07:55 CEST schrieb stakanov:
Ok, this is a very ignorant question... is it still possible as before to go for runlevels? I thought this was not true any more since systemd? There is the package systemd-sysvinit , which describes itself as "Drop-in replacement of System V init tools."
will check if it is already installed by default. Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/07/2019 08.49, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
How can I (once the crash happens) nearly immediately block the shutdownprocess of plasma? (I am using X, not wayland). Is there a key combination or some shortcut? Must be a fast one, you have about 10 seconds from the crash to the shutdown.
You might, instead of stopping the system, issue an "init 3" in a console as root, which would stop the entire graphical system, but the text system would continue to run, and you /might/ be able to obtain data. Or maybe better, you could log out of your session, and see if those apps still crash on the attempt. But I doubt in both cases konqui could run long enough to capture data. Other questions. Yes, runlevels continue working. Yes, orthodoxy may say that there are no runlevels any more. Forget it. For what matters to the user, they continue existing and you can do "init 3" or any other level just fine. No need to install anything extra. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 07/15/2019 01:49 AM, stakanov wrote:
I have a segfault crash of kmail / kontact quite regularly when shutting down the system. In order to find out what is wrong, I would need to let konqi finish the backtrace. But in the meanwhile the system shuts down.
How can I (once the crash happens) nearly immediately block the shutdownprocess of plasma? (I am using X, not wayland). Is there a key combination or some shortcut? Must be a fast one, you have about 10 seconds from the crash to the shutdown.
I think what you want is to set a systemd-inhibit lock on drkonqui. If I understand correctly, an inhibit lock an prevent shutdown until the inhibit-lock is released: https://www.freedesktop.org/software/systemd/man/systemd-inhibit.html Redhat also looks like it has a unit file scheme that could be adapted to inhibit shutdown until drkonqui completes: RHEL 7 systemd: How to prevent root from rebooting until a prescribed action is taken https://access.redhat.com/solutions/1580343 -- 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
participants (6)
-
Carlos E. R. -
David C. Rankin -
Markus Koßmann -
Patrick Shanahan -
Roger Price -
stakanov