[Silvan]

This may be partially redundant with what already written in previous reply:
discovery is a strict requirement of the KDE Plasma desktop environment as it is provided by openmamba so it is by design a requirement of the desktop-base-kde meta package. kwin-x11 is a weak requirement of desktop-base-kde and it is removed because it was installed by desktop-base-kde itself which you are removing, so dnf considers it a leaf which is no longer required. Supported openmamba Plasma desktop users are not expected to remove neither desktop-base-kde nor discover.

By wanting to uninstall discovery you are customizing your desktop installation in a way which is not supported by openmamba, so you will also get desktop-base-kde and, e.g., mambatray tools removed. You can do it but then you have to manage the desktop requirements on your own. You can of course just reinstall kwin-x11 after the removal of desktop-base-kde for your needs. You can also make and maintain your own desktop-base-mycustomkde metapackage if you want and know how to do it.

• This reply was modified 2 weeks, 1 day ago by Silvan.

[Silvan]

By uninstalling discover also desktop-base-kde has been uninstalled. desktop-base-kde is openmamba metapackage which ensures that all requirements for KDE Plasma are installed as expected for openmamba desktop users.

If you remove this metapackage then you need to fulfill the KDE requirements and any required change upon upstream Plasma updates on your own.

Specifically, the missing or broken features you have noticed may depend on plugins that have been moved into the new kwin-x11 package which has not been installed automatically for you because desktop-base-kde has been removed in your previous installation.

[Silvan]

einar.hjortdal wrote:

I believe the update from the 23 june broke plasma-desktop or kwin. I do not have the ability to switch virtual desktops any longer, the virtual desktop widget pager is gone from the panel and windows overlap but cannot be moved. Typical shortcuts to change window sizes do not work.

By not being able to switch virtual desktops you suggest that your plasma desktop is running and you should be able to run programs. If that’s the case you may open a konsole and troubleshoot the problem by yourself by inspecting logs or run the openmamba “system report” and send it via the website if you are expecting suuport from whom is writing.

With the latest upgrades KDE Plasma has been updated to 6.4.0 release and proved to work on some test environments. The kwin package has been split upstream into kwin (wayland) and kwin-x11, by the way both are installed if you have performed a full system upgrade because the desktop-base-kde package will require the new kwin-x11 package as a soft dependency. Provided that all packages have been upgraded the system logs may reveal if there is some plasma component which is reporting errors or crashing.

• This reply was modified 2 weeks, 2 days ago by Silvan.

[Silvan]

Ok. Release 470.256.02-5mamba supposingly fixed it.

[Silvan]

Hi,
does access to any virtual console work by pressing CTRL-ALT-F2..F8? This would allow retrieving log information from the console to identify the cause of the issue.
If not, the only way to get useful information would be to start the kernel with the “debug” menu choice (or removing “quiet splash” from Grub command line).
Did you by any chance install the “nvidia” proprietary driver?

[Silvan]

In order to check for any low level error returned by the authentication layer you may want to login into a tty console after you got the password rejected, then run:

sudo os-makereport

this will create a report file that you can send for us to inspect.

Or if you have the required console skills you can check for any relevant error (maybe reported by PAM) in the user and system journal with sudo journalctl -b or journalctl -b.

[Silvan]

Hi,

the password might not be accepted in the graphical section due to a wrong keyboard layout setting if it contains some special characters, have you checked for this?
Then you don’t have the problem any longer after recreating the user? Maybe you changed the password too?
The “Send a report” page seems to work but you need to be logged in the site.

[Silvan]

Many thanks for adding openmamba-KDE6 to your WSL howto project and for sharing in this forum!

[Silvan]

Good. User can just be added to the sysadmin group to give root permissions with sudo, adding to this group is also recommended for polkit policies.

[Silvan]

Hello,
the command to add a user in openmamba is  useradd. See also man useradd.

You need to install KDE Plasma 6 because you used rootfs-base for the installation`? The command is:

sudo dnf install desktop-base-kde

If you need the graphical login manager also sudo dnf install sddm may be needed.

[Silvan]

einar.hjortdal wrote:

Silvan wrote:

A contributor might want to start learning and creating packages for openmamba in his local environment and if you express that you have this interest the discussion might evolve into discussing the technical details on how to do this.

I would like that. And if necessary, I may host my own user rpm repository, with packages built according to openmamba standards.

Good,
the most straightforward and interesting way to start is by creating and using a Docker buildvm image which provides you locally with the webbuild interface, which is what is used to create and update openmamba packages. I’ve checked that it currently works correctly by cloning the openmamba-docker-buildvm repository:

git clone https://src.openmamba.org/openmamba/openmamba-docker-buildvm

and follow the instructions in the project page.

We can discuss about any doubts or problems before or after you have setup the Docker buildvm container.

[Silvan]

einar.hjortdal wrote:

Silvan wrote:

Contributing by making packages which openmamba users might install would require by the way some sort of user identification for legal reasons. If there is interest for this we can go into more detail.

I am surprised by this. Is this a requirement of the openmamba project, or is it an actual european/local issue? I value my online anonymity

There is currently no policy about accepting contributors in openmamba. I’m responsible of openmamba servers and consequently about the risks of accepting people to do things for which I might become at least part of a chain of responsibilities. openmamba is in fact a single maintainer driven distribution which makes it different from a community driven distribution, maybe I should make this more clear so that users may better target their interest, questions and comments accordignly.

A packager might well remain under a pseudonym for the public but I need to accept only trusted people (by me) for binary packages submissions on openmamba repositories. Because you cited Arch Linux, you may have already read their policy for maintainer where candidates need to be presented by two sponsoring maintainers and voted for admission. Contributing to AUR is far less strict because people are only expected to send the PKGBUILD file (plus any patches and other related files), a text file which can be easily audited. The same may be applied to .spec files but openmamba distributes binary packages so things are different in terms of letting anybody to upload packages.

A contributor might want to start learning and creating packages for openmamba in his local environment and if you express that you have this interest the discussion might evolve into discussing the technical details on how to do this. This might be a step allowing to evaluate the quality of the produced packages followed by giving the authorization to send contributions to the openmamba hosted repositories.

• This reply was modified 4 months, 1 week ago by Silvan.

[Silvan]

As of today and for the last years there have been no users contributing so there are currently no contributions although a repository called devel-contrib exists for this.

So, if you are looking for contributions you will find nothing, if instead you want to propose yourself as a contributor, i.e. making packages that will be hosted in the openmamba devel-contrib repository and eventually be imported to the base repository, I may work to refresh and provide the tools and interfaces for contributors to make rpm packages according to openmamba standards. Contributing by making packages which openmamba users might install would require by the way some sort of user identification for legal reasons. If there is interest for this we can go into more detail.

The two /etc/yum.repos.d and /etc/yum/repos.d folders exist and are both supported because some external software  may provide their repository expecting to use the first path, while other tools like dnf (and openmamba) use the second path. One folder should be a symlink to the other but I have given this change a low priority because replacing folders with symlinks has always been a pain with rpm.

[Silvan]

Nothing was specifically patched. Generally speaking the only relevant update might be the kernel update but if you update daily it was not in today updates.

I find it more likely that by running cpupower-gui you fixed its behaviour at startup, because in the old report there was this in the logs:

cpupower-gui[5372]: Applying configuration...
systemd[5330]: cpupower-gui-user.service: Main process exited, code=exited, status=255/EXCEPTION
systemd[5330]: cpupower-gui-user.service: Failed with result 'exit-code'.
systemd[5330]: Failed to start cpupower-gui-user.service.

These considerations are based on and limited by the information I have.

[Silvan]

You may want to try to remove the cpupower-gui package which is currently the only guess about CPU frequency improperly set.
For further investigations from this side you may also want to send two reports: one after boot when the system is slow and another after a sleep/resume cycle.

[Author]

Posts