Hi,
I didn't turn anything off in journald.conf, it is all the default
settings. I do get every boot log just fine for example within
emergency.target, also tried with multi-user.target just for the sake of
trying. I could pastebin them somewhere or at least try to if you want
to have a look,
Am 29.04.19 um 21:32 schrieb linuxfr...@gmx.at:
> i've already did this.
>
> It started after desktop freezes here:
>
> https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12
>
>
> which were solved, but there are still systemd-coredump's
On Mon, Apr 29, 2019 at 09:32:57PM +0200, linuxfr...@gmx.at wrote:
> Hi Zbyszek,
>
>
> i've already did this.
>
> It started after desktop freezes here:
>
> https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12
>
> which were solved, but
Hi Zbyszek,
i've already did this.
It started after desktop freezes here:
https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12
which were solved, but there are still systemd-coredump's
and see comments 33 to 36 here:
On Mon, Apr 29, 2019 at 09:22:30PM +0200, linuxfr...@gmx.at wrote:
> Hi,
>
> i do not know who is the correct person / mailing list, to ask for this one.
>
> 1) screen-lock locks the screen (OK)
>
> 2) screensaver comes and screen is going to be black. (OK)
>
> 3) Everytime i unlock my
Hi,
i do not know who is the correct person / mailing list, to ask for this one.
1) screen-lock locks the screen (OK)
2) screensaver comes and screen is going to be black. (OK)
3) Everytime i unlock my locked screen (after the screensaver kicked in)
i got this:*systemd-coredump* (NOT OK)
On Mo, 29.04.19 11:06, Ellis (cont...@xogium.me) wrote:
> Hi,
> after some manual testing on my end, I can confirm two things:
>
> 1. systemd really takes care of /run as it should
> and 2. I still have no log prior to 'received sigterm from PID 1' when the
> real root is booted up.
>
> I
Hi,
after some manual testing on my end, I can confirm two things:
1. systemd really takes care of /run as it should
and 2. I still have no log prior to 'received sigterm from PID 1' when
the real root is booted up.
I intentionally messed up my kernel cmdline giving it a wrong rootfs
On Mo, 29.04.19 07:12, Ellis (cont...@xogium.me) wrote:
> Hi,
> thank you once again. I guess I will have to find how to keep this directory
> as a whole as you said. Maybe I expected systemd to realize this on its own
> somehow, and it doesn't. Should a fstab entry be enough ? I'm guessing
>
On So, 28.04.19 13:42, Ellis (cont...@xogium.me) wrote:
> Hi,
> subject pretty much says it all. I am currently working on an embeded system
> and wish to use systemd in both the rootfs and the initramfs. These are both
> built via buildroot, making a full rootfs for one and a minimal rootfs for
On Fr, 26.04.19 15:34, Richard Hughes (hughsi...@gmail.com) wrote:
> On Fri, 26 Apr 2019 at 14:47, Dan Nicholson wrote:
> > I think /etc is the only guaranteed to be writable location that's
> > generic to all ostree systems. If possible, I'd get systemd to honor
> > /etc/system-update.
>
>
11 matches
Mail list logo
