Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Jan 26 13:14:22 Sailfish systemd[1]: jolla-devicelock-encsfa.service: Start operation timed out. Terminating.
- Jan 26 13:14:22 Sailfish wait-session-to-start[1299]: In wait loop (89) - state: activating
- Jan 26 13:14:22 Sailfish systemd[1]: Failed to start Nemo device lock daemon.
- Jan 26 13:14:22 Sailfish systemd[1]: jolla-devicelock-encsfa.service: Unit entered failed state.
- Jan 26 13:14:22 Sailfish systemd[1]: jolla-devicelock-encsfa.service: Failed with result 'timeout'.
- Jan 26 13:14:23 Sailfish systemd[1]: jolla-devicelock-encsfa.service: Service hold-off time over, scheduling restart.
- Jan 26 13:14:23 Sailfish systemd[1]: sys-fs-pstore.mount: Cannot add dependency job, ignoring: Unit sys-fs-pstore.mount failed to load: Invalid argument. See system logs and 'systemctl status sys-fs
- -pstore.mount' for details.
- Jan 26 13:14:23 Sailfish systemd[1]: Stopped Nemo device lock daemon.
- Jan 26 13:14:23 Sailfish systemd[1]: Starting Nemo device lock daemon...
- Jan 26 13:14:23 Sailfish wait-session-to-start[1299]: In wait loop (90) - state: activating
- Jan 26 13:14:24 Sailfish systemd[1324]: booster-qt5.service: Start operation timed out. Terminating.
- Jan 26 13:14:24 Sailfish systemd[1324]: Failed to start Application launch booster for Qt5.
- Jan 26 13:14:24 Sailfish systemd[1324]: Dependency failed for Signal booster-qt5 that boot is over.
- Jan 26 13:14:24 Sailfish systemd[1324]: booster-qt5-signal.service: Job booster-qt5-signal.service/start failed with result 'dependency'.
- Jan 26 13:14:24 Sailfish systemd[1324]: booster-qt5.service: Unit entered failed state.
- Jan 26 13:14:24 Sailfish systemd[1324]: booster-qt5.service: Failed with result 'timeout'.
- Jan 26 13:14:24 Sailfish wait-session-to-start[1299]: In wait loop (91) - state: activating
- Jan 26 13:14:25 Sailfish mce[1081]: mce-sensorfw.c: sfw_plugin_load_cb(): plugin(alssensor): error reply: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the re
- mote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Jan 26 13:14:25 Sailfish mce[1081]: mce-sensorfw.c: sfw_plugin_load_cb(): plugin(orientationsensor): error reply: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include
- : the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Jan 26 13:14:25 Sailfish mce[1081]: mce-sensorfw.c: sfw_session_start_cb(): session(proximitysensor): error reply: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes includ
- e: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Jan 26 13:14:25 Sailfish kernel: s3c2410_wdt: s3c2410wdt_keepalive: wtcnt=0x0000fef5, wtdat=0000fef5, wtcon=00009d39
- Jan 26 13:14:25 Sailfish kernel: s3c2410_wdt: s3c2410wdt_keepalive: wtcnt=0x0000fef5, wtdat=0000fef5, wtcon=00009d39
- Jan 26 13:14:25 Sailfish kernel: s2m-rtc s2m-rtc: s2m_rtc_read_time: 2018-01-26 11:14:26(0x01)AM
- Jan 26 13:14:25 Sailfish kernel: s3c2410_wdt: s3c2410wdt_keepalive: wtcnt=0x0000fef5, wtdat=0000fef5, wtcon=00009d39
- Jan 26 13:14:26 Sailfish wait-session-to-start[1299]: In wait loop (92) - state: activating
- Jan 26 13:14:26 Sailfish systemd[1324]: booster-qt5.service: Service hold-off time over, scheduling restart.
- Jan 26 13:14:26 Sailfish systemd[1324]: Stopped Application launch booster for Qt5.
- Jan 26 13:14:26 Sailfish systemd[1324]: Starting Application launch booster for Qt5...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement