Unable to install KDE Plasma from Obarun repos since Arch Linux kwin split

eric

perrazo on my own nor my old hardware (13+ years) coping with package compilation

That's the difference between AUR and obcommunity. The obcommunity repo build the package for you and provide the resulting binary directly on the obcommunity repo. You just have to provide the script, the rest is made automatically.
See https://git.obarun.org/pkg/prototype-pkg

perrazo

eric Many thanks for the information. Unfortunately, my packaging skills are still lacking, even with the hardware compiling problem out the table thanks to the Obarun Git infrastructure. I do not foresee myself producing a packable script in the near future, as I find the information provided too difficult for me to understand and produce an actionable result. So I am stuck here.

Hopefully somebody more knowledgeable may pitch in some time soon. I will leave the KDE Plasma installation with Obarun intent on stand-by while I keep on reading the Obarun documentation and assess other Obarun DE flavours working alternatives in the meantime.
Many thanks to you all for your help so far!

Wat-now

perrazo Hi, I think it the x11 plasma should work not. I was having trouble getting it to compile with the documentation so I just removed the doc handler and it compiled. I have never been able to get wayland plasma to work for some reason.

perrazo

Wat-now Hi and many thanks for you reply. I am trying to use the current kwin version (6.4.5-2) from the obcommunity repo and is not working for me. I may be wrong, but I believe this kwin package you have recently compiled is the new kwin-wayland (the wayland part is ommited from the Arch Linux naming structure) after the Arch Linux package split and there is nothing on the obcommunity repo equivalent to the newly created package kwin-x11 on the Arch Linux extra repo. How are you getting your Plasma x11 session to work if the Plasma Wayland session is not working on Obarun Linux and the current kwin package present on obcommunity repo only provides a Wayland session now? Many thanks for your help and efforts packaging packages for Oburun Linux.

Wat-now

perrazo Hi, glad to help, no problem. It seems to be working for me but you need to enable your boot-user tree. Plasma is known not to work without a $XDG_RUNTIME_DIR set, which is set by activating the boot-user tree by $sudo 66 enable boot-user@youruser

Edit: IF you use startx then you need to edit: # 66 configure -e youreditor boot-user@youruser -edit last line to DESKTOP_CMDLINE=!startplasma-x11

perrazo

Wat-now many thanks for the hints. Unfortunately, I already have the boot-user tree enabled and current kwin packages offers me a Plasma x11 session without any window management nor desktop effects. Not using startx these days. Any other suggestion to troubleshoot my KDE Plasma x11 session?

Wat-now

perrazo How are you trying to start plasma? with what Display Manager?

perrazo

Wat-now I am using SDDM. The Plasma x11 exists as a session option, but every time I choose it, the session launches without effects or window management. Within that particular session, I have searched with btop for kwin and it is not present. For the sake of testing, I have tried KDE/Openbox and I have no issues with it whatsoever. Therefore, I believe the cause of the problem for me is kwin itself.

Wat-now

perrazo try getting some logs: Kwin debgging Hopefully ~/.xsession-errors file is created once you export QT_LOGGING_RULES="kwin_*.debug=true" in env.

perrazo

Wat-now Will the new qt6-base version hitting the obcommunity and extra repos not affecting the current kwin package? Shall I wait to get any logs until the new kwin version is compiled?

Wat-now

perrazo Good catch! Update to version 6.4.5-3 when it hits the obcommunity repo.

perrazo

Wat-now Hi again. I have updated my system to the new kwin version 6.4.5-3. Set the kwin debugging scenario by appending export QT_LOGGING_RULES="kwin.debug=true" in ~/.bash_profile and QT_LOGGING_RULES="kwin.debug=true" in /etc/environment. Sadly, no ~/.xsession-errors file is produced. Could this be as there is no kwin errors at logging to begin with? Should the ~/.xsession-errors file be created in any case?

Wat-now

perrazo try switching to a different tty, logging in then:

export QT_LOGGING_RULES="kwin_*.debug=true" startplasma-x11 > ~/startplasma-x11.log 2>&1

perrazo

Wat-now What I have tried is to boot up the system to SDDM (tty3) then switched to tty12 to run the commands. Since nothing has happened graphically, I have switched back to SDDM to log in to Plasma X11. Nothing has been logged to startplasma-x11.log in any case. Not sure I am doing what you intend me to do.

Wat-now

perrazo I have another way to catch logs. Temporarily change your DM from SDDM to ly. Sudo pacman -S ly ly-66serv
Then switch to TTY12 or any available, log in, then:

sudo 66 disable -S sddm
sudo 66 enable -S ly@tty7 or ly@tty#aprefered TTY# to switch to

after that check ~/ly-session.log to see if there is any output from the failed launch of kwin.

perrazo

Wat-now Hi again. I have tried disabling SDDM and enabling ly (also had to install the ly@-66serv package to enable the tty service). Sadly, ly starts in a loop indicating a "thread panic index out of bounds" on tty7. Any clue of what I am doing wrong this time? No ~/ly-session.log has been generated so far. Many thanks for your help and patience so far.

Wat-now

perrazo try ly again, I have rebuilt it. to version 1.1.2-3. Edit: you were right, uninstall ly-66serv and only install ly@66serv. This should enable to start it

perrazo

Wat-now After updating ly to the new version, boot loop is now gone. However, no DE can be launched. Ly indicates "file not found" for Plasma-X11, LXDE, xinitrc and Openbox (I have tried other WM and DE, just in case). Plasma-Wayland option shows a "logout" and the shell option successfully logs me in. Any clue on how to fix "file not found" error?

Wat-now

perrazo Yes, I have been getting that file not found error when my boot-user@myuser module is not started or not functioning right for some reason. So you must go to a different TTY login, then run % sudo 66 enable -S boot-user@youruser then you should be able to login using ly.

Edit: I may need to file a bug report, I thought I only needed this workaround because I am using the dev. version of 66..

perrazo

Wat-now Sorry to report that running sudo 66 enable -S boot-user@youruser in my case has not fixed the file not found error. Apparently, my boot-user module is running fine. I have tried with DM=ly commented in and out before reconfiguring my boot-user module. Also, with ly@tty7 and ly@tty3. At the moment, no tty for ly. System boot fine and reach ly greeting screen. But every combination so far is giving me such error. Side news, I have now an empty system generated ly-session.log. Any other suggestions?

Wat-now

perrazo Do you have consolekit running?

%sudo 66 status boot-user@orb
Name                   : boot-user@orb
Version                : 0.8.0
In tree                : session
Status                 : enabled, up
Type                   : module
Description            : Configure a nested supervision tree for orb user
Part of                : None
Notify                 : 0
Max death              : 5
Earlier                : 0
Source                 : /usr/share/66/service/boot-user/boot-user@
Live                   : /run/66/scandir/0/boot-user@orb
Dependencies           : consolekit-log dbus-log scandir@orb scandir@orb:setenv@orb scandir@orb:svscan@orb-log dbus consolekit scandir@orb:svscan@orb
Required by            : None
Contents               : boot-user@orb:mount-run@orb
Optional dependencies  : None
Start script           : 
                         None
Stop script            : 
                         None
Environment source     : /etc/66/conf/boot-user@orb/0.8.0
Environment file       : environment variables from: /etc/66/conf/boot-user@orb/0.8.0/.boot-user@orb
                         ## Uncomment it to use a display manager.
                         ## Can be any display manager as long as the
                         ## corresponding frontend file exist on your system
                         ## e.g sddm,lightdm,...
                         ## It also prepare the .xsession file.
                         #DISPLAY_MANAGER=sddm
                         ## Uncomment it to use a console tracker.
                         ## Can be any console tracker as long as the
                         ## corresponding frontend file exist on your system
                         ## e.g consolekit,seatd,turnstile,...
                         #CONSOLE_TRACKER=consolekit
                         ## Create and mount the XDG_RUNTIME directory
                         ## at /run/user/orb [yes|no]
                         XDG_RUNTIME=!yes
                         ## Command to use in your .xinitrc
                         ## to launch your desktop e.g.: openbox-session.
                         ## If commented the .xinitrc file is not configured.
                         DESKTOP_CMDLINE=!jwm

                         environment variables from: /etc/66/conf/boot-user@orb/0.8.0/boot-user@orb
                         ## Uncomment it to use a display manager.
                         ## Can be any display manager as long as the
                         ## corresponding frontend file exist on your system
                         ## e.g sddm,lightdm,...
                         ## It also prepare the .xsession file.
                         #DISPLAY_MANAGER=sddm
                         ## Uncomment it to use a console tracker.
                         ## Can be any console tracker as long as the
                         ## corresponding frontend file exist on your system
                         ## e.g consolekit,seatd,turnstile,...
                         #CONSOLE_TRACKER=consolekit
                         ## Create and mount the XDG_RUNTIME directory
                         ## at /run/user/orb [yes|no]
                         XDG_RUNTIME=!yes
                         ## Command to use in your .xinitrc
                         ## to launch your desktop e.g.: openbox-session.
                         ## If commented the .xinitrc file is not configured.
                         DESKTOP_CMDLINE=!jwm

Environment ImportFile : None
StdIn                  : None
StdOut                 : None
StdErr                 : None
Logger name            : None
Logger file            : None

This is how my output looks when I run sudo 66 status boot-user@myuser
any differences with yours? also the session part of %sudo 66 status

In tree: session
\
├─consolekit-log (pid=1078, state=Enabled, type=classic, tree=session)
├─scandir@orb:setenv@orb (pid=up, state=Enabled, type=oneshot, tree=session)
├─scandir@orb:svscan@orb-log (pid=1080, state=Enabled, type=classic, tree=session)
├─scandir@orb (pid=up, state=Enabled, type=module, tree=session)
├─boot-user@orb:mount-run@orb (pid=up, state=Enabled, type=oneshot, tree=session)
├─consolekit (pid=1157, state=Enabled, type=classic, tree=session)
├─scandir@orb:svscan@orb (pid=1108, state=Enabled, type=classic, tree=session)
└─boot-user@orb (pid=up, state=Enabled, type=module, tree=session)