• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle

  • According to the debian wiki support is not fully guaranteed. Might just be that you ran into any of those issues:

    Wayland support is still not finished yet though. Notably, there are issues with the compositor taking down other applications with it when it crashes, changing the global theme sometimes causes a session crash, "Activities" are unimplemented, there are various papercuts with drag-and-drop functionality, and session restoration only works with XWayland windows. A full and more regularly-updated list of Plasma Wayland issues can be found here: https://community.kde.org/Plasma/Wayland_Showstoppers



  • Can you confirm that it's only the taskbar that freezes? Do any other DE components (e.g. app launcher (shortcut meta + f2 by default)) work or do they freeze/not respond as well?

    You could check various logs for errors:

    • syslog (/var/log/syslog or dmesg)
    • unit files of Plasma components (journalctl -xeu $UNITNAME; e.g. journalctl -xeu sddm.service)


  • It's a mixed bag. Personally I wouldn't use a non-standard port.

    Consider that port numbers under 1024 are Privileged Ports. You would either have to make sure that no other privileged service is running on the port you want to use for SSH when using another privileged port or you need to make sure that no unprivileged program tries to use the same port as your SSH service when using a non-privileged. Overall it adds a bit of overhead and possible headaches for barely any gain.

    Fail2ban should work with a different port without any further configuration but it might not.