On Mo, 31.01.22 09:47, Raman Gupta (rocketra...@gmail.com) wrote:
> > Honestly this just sounds like systemd killing "leftover" processes within
> > the plasma-plasmashell cgroup, after the "main" process of that service has
> > exited. That's not a bug; that's standard behavior for systemd
On Sun, Jan 30, 2022 at 5:54 AM Mantas Mikulėnas wrote:
> On Sat, Jan 29, 2022 at 5:29 AM Raman Gupta wrote:
>
>> Try to set the systemd user instance's log level to 'debug'; I'm guessing
>>> it's not that systemd kills processes directly but that something triggers
>>> a 'systemctl stop' of
On Sat, Jan 29, 2022 at 5:29 AM Raman Gupta wrote:
> Try to set the systemd user instance's log level to 'debug'; I'm guessing
>> it's not that systemd kills processes directly but that something triggers
>> a 'systemctl stop' of the session .scope that they were in.
>
>
> Here are the logs at
Here are the logs at debug level when plasmashell is not running via
systemd, but instead as an independent process:
Jan 29 16:59:53 edison systemd[2551]: Got message type=signal
sender=org.freedesktop.DBus destination=n/a path=/org/freedesktop/DBus
interface=org.freedesktop.DBus
As a another test, I left plasmashell as a child process of my terminal
shell rather than starting it as a systemd user unit.
When doing it this way, plasmashell still crashed on monitor wake-up, but
my applications remained running.
Given that, it does seem like the crash of plasmashell in
>
> Try to set the systemd user instance's log level to 'debug'; I'm guessing
> it's not that systemd kills processes directly but that something triggers
> a 'systemctl stop' of the session .scope that they were in.
Here are the logs at debug level with some annotations inline:
**
Jan 28
Try to set the systemd user instance's log level to 'debug'; I'm guessing
it's not that systemd kills processes directly but that something triggers
a 'systemctl stop' of the session .scope that they were in.
Can't think of any events directly related to monitor wakeup that systemd
would react to
Does anyone have any tips for debugging this or getting more information?
Should I create an issue for this?
On Sun, Jan 23, 2022 at 3:43 PM Raman Gupta wrote:
> (A variation of this message was originally sent to fedora-users)
>
> I have a couple processes that have been consistently dying
(A variation of this message was originally sent to fedora-users)
I have a couple processes that have been consistently dying every time I
wake up my monitors after the system has been idle. One is Slack Desktop
and the other is IntelliJ IDEA.
I used an eBPF program (killsnoop.py at
