Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: hypper on 2016/01/08, 14:51:57
-
hi all,
i am currently running the following
~$ inxi -v2
System: Host: T530 Kernel: 4.1.0-towo.1-siduction-amd64 x86_64 (64 bit)
Desktop: KDE 4.14.3 Distro: siduction 13.1.0 Firestarter - kde - (201305211844
because of the ongoing transitions (gcc5, qt5, plasma 5 etc.) i waited with a du.
of course, now the du wants to change a lot:
Die folgenden Pakete werden durch eine ÄLTERE VERSION ERSETZT (Downgrade):
syslinux syslinux-common
1456 aktualisiert, 402 neu installiert, 2 durch eine ältere Version ersetzt, 74 zu entfernen und 0 nicht aktualisiert.
how can i safely perform a du now?
i am also using the kdenext repo!
thanks in advance!
cheers
mathias
-
http://forum.siduction.org/index.php?topic=5943.0
greetz
devil
-
and one can safely remove syslinux
-
thanks for the advices. everything went through without major problems, i guess.
still, there are some issues:
1) after reboot and the fsck
[***] A start job is running for udev Wait for Complete Device Initialization ( x s / 3 min)
it took at least 1 min to finish booting. is this kernel related?
2) i installed kde-standard. now i wonder, which window-manager should i use? kwin-x11 or kwin-wayland?
and a final question:
what was the reason to use apt instead of apt-get and what should i use in the future?
-
kwin-x11 for now.
For the bot delay provide the output of systemd-analyze blame
apt is the new apt-get (for most things)
greetz
devil
-
1) output of
systemd-analyze blame
1min 852 ms systemd-udev-settle.service
2) i installed kwin-x11, but it boot right away into console. i guess i miss a login-manager, too?
it needed:
sddm
kde-config-sddm
libqt5xcbqpa5
(http://forum.siduction.org/index.php?topic=5970.msg49227#msg49227)
-
systemd-analyze blame
1min 852 ms systemd-udev-settle.service
i think it is related to LVM. since i do not use LVM should i mask systemd-udev-settle.service or purge lvm2?
btw, there is no boot delay with Kernel: 4.1.0-towo.1-siduction-amd64 x86_64 (64 bit)
-
Delete lvm2 and see what that does.
greetz
devil
-
apt purge lvm2
solved the problem in my case.