[Silvan]

Hello,
the nVidia driver will soon be updated to major version 550 after successful tests, I hope the upgrade will be smooth for you too.

As for the dual GPU + display support, I don’t know how to provide a out-of-the-box solution working with proprietary drivers and every situation. By the way documentation on configuring Optimus and PRIME support might be helpful. openmamba provides packages like bumblebee and envycontrol which might be helpful. I see now there is a tool called optimus-manager which maight be worth packaging.

References:

https://wiki.archlinux.org/title/PRIME

https://github.com/Askannz/optimus-manager

[Silvan]

Thanks for the test and the configuration provided. There will be a package update which will provide a default configuration with

permit persistent :sysadmin

By the way for the moment sudo commands remains the sudo tool in openmamba.

[Silvan]

Hi,
the package micro and opendoas are now available for installation in openmamba. The latter needs creating the configuration file /etc/doas.conf and maybe some testing.

[Silvan]

The nvidia driver might be missing in the latest kernel initramfs so I would suggest to try:
sudo /usr/sbini/mkinitrd -H -f /boot/initramfs-6.6.10-1mamba-x86_64.img 6.6.10-1mamba-x86_64

if network is available this shorter command might also work:
sudo dnf reinstall kernel-mamba-x86_64-6.6.10

[Silvan]

Hello,
since the installation I think you should have received at least one kernel update, so you might want to try booting with another kernel by selecting “Advanced” boot options in the Grub menu, then going down three choices should point you to the previous kernel.

Once you are able to boot openmamba without reinstalling we can further investigate the problem, but the first thing to see would be checking if dkms has built the nvidia driver for the last kernel releases. This can be checked with the following command line command:
sudo dkms status

[Silvan]

Hello Roderick,
thank you for your feedback and happy holidays!

[Silvan]

Hi,
I’ve released the package update filesystem-2.3-10mamba as an attempt to fix the problem you are reporting.
Thanks for letting me know if it works or not.

[Silvan]

Hi @ouaille_aime_scier,
I think this was a transient problem while releasing the up-to-date KDE frameworks packages. It should work now after refreshing the packages list with sudo dnf refresh or using the mambatray icon entry.
Thanks for reporting.

[Silvan]

Hello Roderick,
the issue seems to be caused by gnupg blocking due to pre-existing files in /root/.gnupg folder.
I would suggest to run the following commands from a konsole:

su
[Blocking -> Press CTRL-C and you are root]
killall -9 gpg-agent
rm -rf /root/.gnupg

Then the next su or sudo su call should regenerate a clean and correct content of the gnupg folder and fix the problem.

I hope this helps. Thanks for reporting and appreciating openmamba.
Silvan

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

[Silvan]

Hello Roderick,
you are saying that neither the su command not sudo passwd root are working correctly and that you get no prompt in response?
I currently don’t reproduce the problem, maybe I need to check if the new installation media have such problem. It might also be a problem related to network name resolution.
I will investigate more and thanks if you have some more info to provide.
Silvan

[Silvan]

Hi,
you are welcome.

About kdeconnect:
openmamba default firewall is ufw so the rules needed for kdeconnect are the ones described in the official documentation:
`
sudo ufw allow 1714:1764/udp
sudo ufw allow 1714:1764/tcp
sudo ufw reload
`
I will add these rules to ufw applications set as you suggest.

[Silvan]

Hi,
I’ve created the systray-x package for openmamba and it can be installed with:
sudo dnf install systray-x

Thank you for your post.

[Silvan]

ouaille_aime_scier wrote:

Hi Silvan,
This is what appears in the terminal :

mars 30 20:15:09 openmamba dbus-daemon[6819]: [session uid=1000 pid=6819] Successfully activated service 'org.kde.LogoutPrompt'
mars 30 20:15:09 openmamba ksmserver-logout-greeter[8068]: kde.logout_greeter: Couldn't find a theme for the Shutdown dialog ""

Hi,
this seems like a theme problem. Are you using the default theme? If so, can you try to reapply it from the Appearance > Global theme page in the settings? It is not necessary to check the box for reapplying also the dispositions so that you won’t lose your customization.

• This reply was modified 1 year ago by Silvan.
• This reply was modified 1 year ago by Silvan.
• This reply was modified 1 year ago by Silvan.

[Silvan]

Hi,
sorry, there was an error which I corrected in man-pages-fr-4.18.0-2mamba which will be available as a new update in a few hours.

[Silvan]

Hello,
I don’t reproduce the problem, I’ve also tried both X11 and Wayland sessions and searched in KDE bugs.
Can you open a terminal and run:
journalctl -f

then try to logout to reproduce the problem and see if some useful message appears on the terminal?

[Author]

Posts