Mokka on VM and normal Garuda KDE Dr460nized Gaming Edition

hello Feedback :upside_down_face: :wink:,

ive donloaded the new mokka Version.

i did install it on a VM.On the VM the brightness Control didnt work and chances to Night Light Control for more blue or yellow settings.Only on the live Version.Ive installed it on the VM and after the reboot it was the Brightness Control back and really worked to lower or higher the brightness of the Display in the VM.
I have actually the in title given version and also on my HP Display i can use only Night Light warmings effect but not brightness control.Would be nice if i install on my next harddrive and took same effect to work with my Hp Display =)

Works perfectly for me on VM.
Using virt-manager with OpenGL 3D Acceleration.

It has nothing to do with the VM or OpenGL by the way.

can i show some pic i wont spoiling ? :grin:

here some pics :blush:



Also install on VM
Works well
Only one small issue with sddm login service. (message from journal)
Resolved with " usermod --expiredate= sddm "

Are you trying to have the VM use the Night Colors of your metal machine?
That is not intended.

You can independently use Night Colors from your VM vs metal machine.

If you feel the theming is causing an issue, you can do the following:

  • Apply Breeze Dark Global Theme and see if it behaves the same way
  • Install Mokka on real metal machine and see if it behaves the same way
    – 2nd option + apply Breeze Dark Global Theme and see if behaves the same way
1 Like

no i dont want try or want have night light.i want real brightness level on my metal machine.
The brightness control works on the vm.it dont work on my actually metal machine with the Garuda KDE Dr460nized version.

I will test it at next on my real machine.Thats what i was wondering hopefully it works with the brightness control =)

i will give later a feedback.Thanks

Your screenshots point to Night Color, which is not the same as Brightness.
Brightnes can be found in Power Management section of System Settings.

Works on both Dr460nized and Mokka for me.

This feature is controlled by Plasma, our themes and packages don’t use it.

1 Like

ok thats funny. it didnt seems like mine. i cant control Brightness lol.

i try to install https://iso.builds.garudalinux.org/iso/garuda/mokka/250131/garuda-mokka-linux-zen-250131.iso to my real machine but some error happening after formatting the Harddrive. sha1 and sha256 checked and green ok so download is fine because it worked on the VM.
i used dd to a 16GB USB stick.

My error is installation error primaryscript /usr/lib/calamares/modules/mount/main.py for the python-job mount.

I personally have had some “disappearing setting” issues on 2 machines with this particular setting a few weeks ago, I believe some Plasma updates cuz this. Maybe this is what you are getting on your end.

Would need to know exactly the error.

hm possible if you have on 2 machines.

i got this error in german but ive translate to my best.

Installation canceled
Faulty primary script file
Details:
Primary script file /usr/lib/calamares/modules/mount/main.py for the Python job mount threw an exception

i see this message after the installation progress have finished formating 600mb efi and btrfs 120gb.it start copy files and stopped with those aborting.

2 Likes

Ok tnx, we will look into that.

2 Likes

maz a difference between Laptop Display and a normal PC Monitor _ because i can manually lower my brightness on the monitor settings?idk

If I recall, the brightness feature is only available on monitors that support the feature. Might also take that into consideration.

1 Like

so i am on the iso from the Dr460nized Gaming version but the test iso yet :smiling_face:

i was trying to install Mokka version it didnt want work on my metal machine.
Trying with dd comand, USB ISO Writer and Ventoy.

I downloaded the Dr460nized Gaming Version and did dd in cli again and rebooted to install. Now it worked without issues.

Back to my main issue about older Garuda Dragonized Version and Tested Mokka Version on VM.Brightness control worked there for my HP Monitor so now its time to check on the new iso effect .

There some pics what i got for errors and last but not least will Brightness Control Work now :grin:


pic 1 is 250131 (mokka)
pic2 is 250202 (mokka)
pic3 (not mokka)Yesssss it works :ghost:

Yes we are working on that. Test ISOs may not work in the short term.

1 Like

want start gparted lol

Works on latest ISO. I started it form command line, how are you starting it?

You can launch KDE Partition Manager, it’s themed properly and looks nicer.

1 Like

thanks FGD,

ive started earlier on daytime cause error. ive updated and reboot and it worked . i only have those error .gparted was not installed from fresh iso i have to install it.

gparted
localuser:root being added to access control list
GParted 1.7.0
configuration --enable-libparted-dmraid
libparted 3.6

** (gpartedbin:73480): WARNING **: 22:43:25.168: Unable to connect to dbus: Fehler beim Erzeugen der Befehlszeile »dbus-launch --autolaunch=7e362c7e9c024e24b949f7ce0a80594a --binary-syntax --close-stderr«: Der Kindprozess wurde mit Status 1 beendet

(gpartedbin:73480): GLib-GObject-CRITICAL **: 01:22:05.562: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(gpartedbin:73480): GLib-GIO-CRITICAL **: 22:43:25.562: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(gpartedbin:73480): GLib-GObject-CRITICAL **: 22:43:25.562: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(gpartedbin:73480): GLib-GIO-CRITICAL **: 22:43:25.562: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(gpartedbin:73480): GLib-GIO-CRITICAL **: 22:43:25.562: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
localuser:root being removed from access control list