On Sun Dec 08, 2024 at 02:07:10AM +0000, Yifei Zhan wrote:
> I'm testing out Plasma 6 on a fresh installation and I think there are a
> few workarouds and notes worth adding to the pkg readme.
>
> - Move screen locking to its own section and mention xlock as an
> alternative
> - Mention about increasing resource limits, the default login class is
> too conservative and most plasma widgets would keep crashing
> - Mention about touchscreen calibration
>
> Please help me bump the right REVISION if needed.
>
> diff --git a/meta/kde/pkg/README-plasma b/meta/kde/pkg/README-plasma
> index bb5e9fd5ce3..51775a2c534 100644
> --- a/meta/kde/pkg/README-plasma
> +++ b/meta/kde/pkg/README-plasma
> @@ -20,6 +20,26 @@ export XDG_CURRENT_DESKTOP=KDE
> export DESKTOP_SESSION=plasma
> ${LOCALBASE}/bin/startplasma-x11 > ~/.startplasma-x11.log 2>&1
>
> +Screen locking
> +==============
> +You can't unlock your session when the screensaver has locked it. I get the
> +graphical message "Something wrong happened. Run # ck-unlock-session ...".
> +So you will end up with a freezen session that you have to completely kill.
> +
> +As a workaround, you can disable the default screensaver via:
> + System Settings -> Security & Privacy -> Screen Locking
> +then uncheck lock after waking from sleep and set locking interval to never
> +
> +Alternatively, xlock(1) works well with KDE, to bind it to a shortcut:
> + System Settings -> Keyboard -> Shortcuts
> +
> +Resource limits
> +===============
> +The default resource limits are too conservative for KDE Plasma. To raise
> your
> +resource limits, increase the limits for your user's class in
> /etc/login.conf,
> +then login again to apply. KDE widgets (such as Launchers) keep crashing can
> +be a sign of insufficient resource limits.
> +
> Logging out and shutting down the computer
> ==========================================
> If your user is part of the _shutdown group and thus can execute shutdown(8),
> @@ -58,6 +78,12 @@ It is also possible to use a window manager other than
> KWin with Plasma.
>
> export KDEWM=${LOCALBASE}/bin/picom
>
> +Touch screen calibration
> +========================
> +xtsscale(1) can be used for touch screen calibration, however it will not
> +work under kwin, as a workaround, you can kill kwin first, calibrate your
> +screen, then launch kwin_x11 again.
> +
> Desktop search
> ==============
> Baloo file indexer is disabled by default on OpenBSD. To enable it go to
> @@ -89,11 +115,10 @@ ${LOCALBASE}/bin/ck-launch-session dbus-run-session \
>
> Known issues
> ============
> -- You can't unlock your session when the screensaver has locked it. I get the
> - graphical message "Something wrong happened. Run # ck-unlock-session ...".
> - So you will end up with a freezen session that you have to completely kill.
> - **It is recommended to disable KDE screen locking** for now.
> +- The default screensaver does not work, see Screen Locking section for
> + workaround.
> - The first start may take a little longer.
> +- Touchscreen configuration does not work
> - The sound mixer Kmix works only on the main channel.
>
> Not yet ported Plasma applications/plugins
>
Hi Yifei, Hi all,
I have completely forgotten this diff. I would take it up again.
Especially the part with the resource limits is important other wise new
users will see annoying crashes and stop using it. I did some test with
the limits ans this ones are surviving my use-cases.
English improvements are very welcome
Rafael
Index: Makefile
===================================================================
RCS file: /cvs/ports/meta/kde/Makefile,v
diff -u -p -r1.38 Makefile
--- Makefile 11 May 2025 05:27:01 -0000 1.38
+++ Makefile 21 May 2025 03:01:30 -0000
@@ -30,6 +30,8 @@ PKGNAME-utils = kde-utils-${MODKDE_GEAR
PKGNAME-plasma = kde-plasma-${MODKDE_PLASMA_VERSION}
PKGNAME-plasma-extras = kde-plasma-extras-${MODKDE_PLASMA_VERSION}
+REVISION-plasma = 0
+
MULTI_PACKAGES += -main \
-games \
-admin \
Index: pkg/README-plasma
===================================================================
RCS file: /cvs/ports/meta/kde/pkg/README-plasma,v
diff -u -p -r1.4 README-plasma
--- pkg/README-plasma 9 Feb 2025 09:04:15 -0000 1.4
+++ pkg/README-plasma 21 May 2025 03:01:30 -0000
@@ -45,11 +45,36 @@ proper function, it requires messagebus
consolekit2 and polkit-kde-agent, it will also allow you to suspend the
laptop from the logout dialog.
+Resource limits
+===============
+
+The "default" login-class resource limits are too conservative for KDE Plasma
+users. It is recommended to create a new login-class based on the "default"
+class for all KDE Plasma users. Here is an example for /etc/login.conf.d/kde:
+
+kde:\
+ :datasize=8192M:\
+ :openfiles-cur=2048:\
+ :openfiles-max=4096:\
+ :tc=daemon:
+
+Depending on your use-case and if KDE widgets or plasmashell heep crashing, the
+value must be set higher accordingly.
+
+You can change the login class for the user to be created with:
+
+# usermod -L kde your-user-name
+
+Touch screen calibration
+========================
+xtsscale(1) can be used for touch screen calibration, however it will not
+work under kwin, as a workaround, you can kill kwin first, calibrate your
+screen, then launch kwin_x11 again.
+
Screen compositor
=================
-The KDE compositor may not run properly by default. You can deactivate it
-under: "System Setting" -> "Display Configuration" -> "Compositor" or
-in `~/.config/kwinrc":
+You can deactivate the screen compositor under: "System Setting" -> "Display
+Configuration" -> "Compositor" or in `~/.config/kwinrc":
[Compositing]
Enabled=false
@@ -90,11 +115,11 @@ ${LOCALBASE}/bin/ck-launch-session dbus-
Known issues
============
- The first start may take a little longer.
+- Touchscreen configuration does not work
Not yet ported Plasma applications/plugins
==========================================
- aura-browser
- - kpipewire
- bluedevil
- breeze-plymouth
- discover
