I started with a 16.03 or 16.02 KDE I believe and have been rolling it along on limbo repo without issues. I notice that it seemed a bit slow to get to the login screen. The pretty animation thing would come up and when that finished my screen would turn black and sit there for a bit more time and than finally the login box. I know the liveusb boots up faster so I took a look into the logs and was discovered several things failing to load.
If you are unfamiliar with how to see your boot log you use journalctl as root user and issue the command
Code: Select all
journalctl -b
Code: Select all
journalctl -b > boot.txt
A quick look into
Code: Select all
ls -la /usr/lib64/modules-load.d/
I know I am not using zfs or xen so I am just gonna move the config files
Code: Select all
mv /usr/lib64/modules-load.d/zfs.conf zfs.conf
Code: Select all
mv /usr/lib64/modules-load.d/xen.conf xen.conf
redoing
Code: Select all
journalctl -b
Code: Select all
installer-gui.service
installer-text.service
sabayonlive.service
sabayon-mce.service
steambox.service
Code: Select all
systemctl disable installer-gui.service
systemctl disable installer-text.service
systemctl disable sabayonlive.service
systemctl disable sabayon-mce.service
systemctl disable steambox.service
redoing
Code: Select all
journalctl -b
Code: Select all
[pulseaudio] bluez5-util.c: GetManagedObjects() failed.......
So taking a look we see pulseaudio.desktop is definitely there
Code: Select all
ls -la /etc/xdg/autostart/
Code: Select all
mv /etc/xdg/autostart/pulseaudio.desktop pulseaudio.desktop
The error is now gone, but I now have a different error message with bluez and I don't know if it's my system or what, but bluez seems really unstable on my laptop. The new error is
Code: Select all
[pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Activation of org.bluez timed out
Code: Select all
systemctl enable bluetooth.service
Code: Select all
systemctl start bluetooth
Code: Select all
systemctl status bluetooth
Using journalctl I can examine the process
Code: Select all
journalctl -u bluetooth.service
-- Logs begin at Tue 2016-02-23 03:56:58 CST, end at Tue 2016-04-12 19:46:33 CDT. --
Apr 12 16:59:07 bikinibottom systemd[1]: Starting Bluetooth service...
Apr 12 16:59:07 bikinibottom bluetoothd[3306]: Bluetooth daemon 5.38
Apr 12 16:59:07 bikinibottom systemd[1]: Started Bluetooth service.
Apr 12 16:59:07 bikinibottom bluetoothd[3306]: Starting SDP server
Apr 12 16:59:07 bikinibottom bluetoothd[3306]: Bluetooth management interface 1.11 initialized
Apr 12 17:00:03 bikinibottom bluetoothd[3306]: Terminating
Apr 12 17:00:03 bikinibottom systemd[1]: Stopping Bluetooth service...
Apr 12 17:00:03 bikinibottom systemd[1]: Stopped Bluetooth service.
So my boot log looks much better and my laptop boots to the login screen faster after doing the above stuff.
Some other notes, it didn't matter which kernel I used 4.4 or 4.5, the errors were the same. I also discovered that ACPI issues can cause KDE not to shutdown properly, I know some have reported that on the forum. It's an issue all distros face. Most of the above issues are reported among all distros and several bug reports. The issues are harmless and everything here can be ignored, but it did improve my boot speed by cleaning up the boot process.
So now I wonder, am I unique to all this or is everyone plagued with this. If you could, could you please upload/pastebin your boot log for me so I can take a look at it. It doesn't have to be just the KDE installations, which ever iso you installed is fine. I would much appreciate it and maybe we can clean some of this stuff up to make installations even better for people. So get your friends and family to post their boot log.
I will worry about my bluetooth issues later, I don't use it, so I could simple disable it, but not a real solution. If you have bluetooth issues, feel free to mention so, might be an epidemic.
oh, one last thing, FEEDBACK, your ideas and thoughts on your boot experiences.