Arch Linux User Repository

@kihanos: would you mind to modify the PKGBUILD so that the build configuration with cmake is done in build() rather than in prepare()? Because of this:

https://bugs.archlinux.org/task/72532

I cannot cross-compile plasma-bigscreen-git on my RPI4 with distcc. Thanks.

@ArchieMeng

1. I had created a dirty PKGBUILD for that purpose. It's a runtime dependency for the configuration modules to work (KDEConnect, Wifi, Sound, Wallpaper). I just pushed onto AUR a cleaner version of the PKGBUILD: https://aur.archlinux.org/packages/plasma-settings-git/

2. I guess 2. and 3. could be avoided for Wayland sessions only provided we worked a little bit

   • Most files involved in step 2 are for UI configuration (setting an appropriate DPI, blacklisting most useless apps so that the board is not too crowded and so on). I guess they might not be strictly necessary. I don't know how to streamline Step 2 efficiently. If step 2 is not done, then step 3 should also add export PLASMA_DEFAULT_SHELL=org.kde.plasma.mycroft.bigscreen to the .bashrc.
   • Step 3 could be avoided if we patched ${pkgdir}/usr/bin/plasma-bigscreen-wayland and changed the last line startplasma-wayland --xwayland --libinput --exit-with-session=/usr/lib/libexec/startplasma-waylandsession to startplasma-wayland. The options seem to trigger the black screen, I don't know why. If we do that, then sddm should just launch Plasma-Bigscreen-Wayland. Edit: This only allows to run a Wayland session.
   • Edit: To run a X11 session: Step 3 is necessary. Step 2 partially so: you require at least to have the file ~/.config/plasmashellrc found here

3- Sure, why not :-)

@kihanos,

1. How did you solve the last dependency of 'plasma-settings'? Is it a optional dependency?

2. For the step 2 and step 3 in your post, are they required for a fresh arch environment (Which haven't install plasma before)?

3. And would you like to become co-maintainer of this package since you have done a lot for the packaging when I was absent.

@ArchieMeng

So, I finally got it to run as expected without Mycroft nor CEC support. Things are more complicated than I thought.

1- Dependencies:

    'kactivities'
    'kactivities-stats'
    'ki18n'
    'kdeconnect'
    'plasma-workspace'
    'kdeclarative'
    'plasma-framework'
    'kirigami2'
    'kcmutils'
    'knotifications'
    'kwindowsystem'
    'kwayland'
    'kwayland-integration'
    'xorg-server-xwayland'
    'plasma-wayland-session'
    'plasma-nano'
    'plasma-settings'

Note: the last dependency is Plasma-Mobile's KCM. Not yet on AUR, available at https://invent.kde.org/plasma-mobile/plasma-settings. The build procedure is straightforward. I did not untangle the dependencies of plasma-settings, but the ones of plasma-bigscreen are enough.

2- Created a dedicated user USER. Copied the content of https://invent.kde.org/plasma-bigscreen/bigscreen-debos-image-rpi4/-/tree/master/overlays/bigscreen/etc/xdg into $USER's ~/.config

3- Made this the $USER's .bash_profile

#
# ~/.bash_profile
#

export PLASMA_PLATFORM=mediacenter
export QT_FILE_SELECTORS=mediacenter

[[ -f ~/.bashrc ]] && . ~/.bashrc

4- You can now launch by loging in with $USER from sddm by running Plasma-X11 or Plasma-Wayland but not Plasma-Bigscreen-Wayland

@kihanos The plasma-meta is just a meta package which install all the plasma environment. I didn't know which plasma dependencies the plasma-bigscreen needs at first, so I just used it to build the package in advance. I will change it to the specific ones once they are clear.

For mycroft-core, I don't have the proper environment to test (GFW blocked the repo and mycroft is not taking my proxy settings). But I remember when I was first packaging this package, the mycroft-core seemed to be working. Could you recheck that? If true, then mycroft-gui is the actual one needed.

Another comment: the optional dependency mycroft-core does not seems to be enough. Installing mycroft-gui seems to be needed (as least for cmake to quit complaining)

Hi! First, sddm now launches plasma bigscreen without any problem. Second, is there a reason for the dependence to plasma-meta? This seems way more than what is listed in the git README: https://invent.kde.org/plasma/plasma-bigscreen

I get a black screen whether I start from sddm or run /usr/bin/plasma-bigscreen-wayland. What Lean0402 suggested does indeed work for me though.

When logging in from sddm, the screen is just black with my mouse cursor being visible.

From a wayland session I can use "plasmashell --replace -p org.kde.plasma.mycroft.bigscreen" though to make it work.