ASUS-X551CA tracker-miner-f: Could not remove files in volumes: GDBus.Error.TimedOut: Failed to activate> ASUS-X551CA dbus-daemon: Failed to activate service '1': timed out (service_start_>
ASUS-X551CA systemd: Started Application launched by gnome-session-binary. ASUS-X551CA geoclue: Service not used for 60 seconds. ASUS-X551CA PackageKit: refresh-cache transaction /54_dadccebd from uid 1000 finished with success after 5530ms ASUS-X551CA kernel: snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 ASUS-X551CA kernel: snd_hda_codec_realtek hdaudioC0D0: inputs: ASUS-X551CA kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 ASUS-X551CA kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC270: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker ASUS-X551CA systemd: Reached target Local Encrypted Volumes. ASUS-X551CA systemd: Started Forward Password Requests to Plymouth Directory Watch. ASUS-X551CA systemd: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. ASUS-X551CA systemd: Started Show Plymouth Boot Screen. ASUS-X551CA systemd: Starting Show Plymouth Boot Screen. ASUS-X551CA systemd: Started udev Kernel Device Manager. ASUS-X551CA systemd: Finished Flush Journal to Persistent Storage. ASUS-X551CA systemd-journald: Time spent on flushing to /var/log/journal/566f5db5a1c44e7e82177afc4065ba38 is 106.109ms for 974 entri> ASUS-X551CA systemd: Starting udev Kernel Device Manager.
There are 3 sections (pasted below) where there seems to be an inordinate amount of time going, but i'm not clear what these services actually do and why they might be taking a long time: I have tried journalctl -b -o short-monotonic to see what the system is spending time doing while it boots. I've tried making the edits mentioned here: – 28 Oct 16 └─system.slice i think this is indicating an issue with device driver for my ASUS X551CA intel backlight - after Googling, there seems to be a lot of issues with this causing slow boots (especially on Ubuntu). └─system-systemd\x2dbacklight.slice 50.657s The command systemd-analyze critical-path gives: It still takes Zorin 16 Beta an age to boot. I've reformatted the SSD and a) installed a fresh Win10 Pro b) installed a fresh Zorin 16 Beta (created separate /, /home and swap partitions). I'm not too sure what you mean by "Windows partition failed"? Win10 boots okay and Zorin 16 Beta boots okay (eventually).
0 kommentar(er)
