Oh. I see I need to ask OpenSuse to fix or get a newer OpenSuse version.
Thank you
Markus
"ZbigniewJędrzejewski-Szmek" wrote in message
news:[email protected]...
On Thu, Jan 01, 2015 at 01:13:30PM -0500, Dave Reisner wrote:
On Thu, Jan 01, 2015 at 07:05:04PM +0100, Zbigniew Ję
OK I logged it as https://bugs.freedesktop.org/show_bug.cgi?id=87943 . I
can't seem to get a core dump file.
Markus
"ZbigniewJędrzejewski-Szmek" wrote in message
news:[email protected]...
On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote:
Hi,
How can I find o
On Thu, Jan 01, 2015 at 01:13:30PM -0500, Dave Reisner wrote:
> On Thu, Jan 01, 2015 at 07:05:04PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote:
> > > Hi,
> > >
> > > How can I find out why systemd core dumps and requires system
> >
On Thu, Jan 01, 2015 at 07:05:04PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote:
> > Hi,
> >
> > How can I find out why systemd core dumps and requires system
> > reboot :-( ?
> >
> > I just did
> >
> > # systemctl status sockd-1.5.
On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote:
> Hi,
>
> How can I find out why systemd core dumps and requires system
> reboot :-( ?
>
> I just did
>
> # systemctl status sockd-1.5.0
> Failed to issue method call: Did not receive a reply. Possible
> causes include: the remote
Hi,
How can I find out why systemd core dumps and requires system reboot
:-( ?
I just did
# systemctl status sockd-1.5.0
Failed to issue method call: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the
