At login I get the following errors :
[ 21.563380] systemd-logind[2908]: Failed to start unit
user@1000.service: Unknown unit: user@1000.service
[ 21.563408] systemd-logind[2908]: Failed to start user service:
Unknown unit: user@1000.service
and at logout the following ones
[ 329.910312]
On 08/31/2014 09:28 AM, Erwan David wrote:
I submitted a bug, however I could not find those messages in any log :
That's not a systemd bug...
why ?
...it's a systemd feature
/sarcasm
--
hangout: ##b0rked on irc.freenode.net
diversion: http://alienjeff.net - visit The Fringe
quote: The
On Sun, 31 Aug 2014 15:28:11 +0200
Erwan David er...@rail.eu.org wrote:
I submitted a bug, however I could not find those messages in any log :
why ?
With people considering their mistakes something that others must
fix, expect a speedy closing w/o any explanation…
If something is logged to
On 2014-08-31 15:28 +0200, Erwan David wrote:
At login I get the following errors :
[ 21.563380] systemd-logind[2908]: Failed to start unit
user@1000.service: Unknown unit: user@1000.service
[ 21.563408] systemd-logind[2908]: Failed to start user service:
Unknown unit: user@1000.service
Le 31/08/2014 15:39, B a écrit :
On Sun, 31 Aug 2014 15:28:11 +0200
Erwan David er...@rail.eu.org wrote:
I submitted a bug, however I could not find those messages in any log :
why ?
With people considering their mistakes something that others must
fix, expect a speedy closing w/o any
On Sun 31 Aug 2014 at 15:28:11 +0200, Erwan David wrote:
At login I get the following errors :
[ 21.563380] systemd-logind[2908]: Failed to start unit
user@1000.service: Unknown unit: user@1000.service
[ 21.563408] systemd-logind[2908]: Failed to start user service:
Unknown unit:
On Sun 31 Aug 2014 at 15:51:22 +0200, Erwan David wrote:
I tried journalctl systeld-logind and journalctl logind, but those where
refused foor unable to add to match
I get No journal files found for the journalctl command. I bet you do
as well.
It might be related to bug 757195 that was
Am Sonntag, 31. August 2014, 15:28:11 schrieb Erwan David:
I submitted a bug, however I could not find those messages in any log :
why ?
If something is logged to console, it should also be logged to a file,
for an admin to be able to access the messages afterward.
Use this command to find
Le 31/08/2014 16:26, Brian a écrit :
On Sun 31 Aug 2014 at 15:51:22 +0200, Erwan David wrote:
I tried journalctl systeld-logind and journalctl logind, but those where
refused foor unable to add to match
I get No journal files found for the journalctl command. I bet you do
as well.
It
On 31/08/14 16:10, Erwan David wrote:
EIther the explanation is incomplete or the badly redacted or the
examples in the man are false
I cannot see how
journalctl /usr/bin/dbus-daemon or journalctl /dev/sda fit in that
explanation
There is a third possibility: you didn't finish reading the text
Le 31/08/2014 16:12, Brian a écrit :
On Sun 31 Aug 2014 at 15:28:11 +0200, Erwan David wrote:
At login I get the following errors :
[ 21.563380] systemd-logind[2908]: Failed to start unit
user@1000.service: Unknown unit: user@1000.service
[ 21.563408] systemd-logind[2908]: Failed to
On Sun 31 Aug 2014 at 17:24:50 +0200, Erwan David wrote:
Le 31/08/2014 16:12, Brian a écrit :
I get the same thing too. It goes away when systemd-shim is purged. :)
This is related to the error messages. Not th fact that the logs of
systemd are not saved in any file, but only in dmesg
Ahoj,
Dňa Sun, 31 Aug 2014 17:09:04 +0100 Brian a...@cityscape.co.uk
napísal:
On Sun 31 Aug 2014 at 17:24:50 +0200, Erwan David wrote:
Le 31/08/2014 16:12, Brian a écrit :
I get the same thing too. It goes away when systemd-shim is
purged. :)
This is related to the error
13 matches
Mail list logo
