[Latte Dock] The end of an era (designing a Latte-Dock free alternative dr460nized setup)

[Nemisis]

@FGD

Make sure you actually have the package garuda-dr460nized-next installed first

that was missing

now both the git and the regular version of garuda system maintenance show the update

this should be mentioned in the wiki.

the Update did run perfect

Thanks

[FGD]

Not everything has been pushed yet, this is possibly why.
I added the package pre-requisite in the wiki.

[Locutus]

As I stated in my edited post 5.27 dropped while I was making that post. On another note a heads up for those that might be using sliding notifications, you may have to remove it so the 5.27 updates will be grabbed.

[glomar_response]

I do have some feedback on the migration.
So before migration Latte handles the key to open the application menu. Currently performing the migration does not unbind Latte from the key, and thus the menu does not open unless I manually restart Latte, right click the dock ~> Configure Latte ~> Uncheck the options binding to the application menu.
Only then can I hit and the application menu be opened from the Plasma Panel (after killing Latte first of course).
Is there anyway to uncheck those settings (Use to open application menu, autostart) as part of the migration?

Edit: Sorry, reverting back to get a screenshot of the Latte options as I'm sure that would help.

Edit-2: Here are the options I think need to be disabled. Autostart specifically because the migration didn't remove latte-dock automatically.

[FGD]

As part of the migration, that needs to be checked.

However the key should be (was for me) located in ~/.config/kwinrc
The section that says

[ModifierOnlyShortcuts]
Meta=org.kde.lattedock,/Latte,org.kde.LatteDock,activateLauncherMenu|

Delete it.
The section! Not the file! loll

[glomar_response]

@FGD

As part of the migration, that needs to be checked.

I just tested it with the upgrade to 5.27 and after installing garuda-dr460nized-next and garuda-system-maintenance-git, rebooting and performing the migration from the prompt. All this on a fresh install to make sure no custom settings or configs would interfere with my testing.
After the migration, hitting < super > doesn’t open application menu from the plasma top panel.

[FGD]

@glomar_response

Autostart specifically because the migration didn’t remove latte-dock automatically.

It’s not supposed to autostart on next reboots.
It depends exactly which steps you followed to perform the migration. If you did manually, then you have to remove Latte too. If you used garuda-system-maintenance-git (the kdialog prompt), it should not relaunch Latte.

[FGD]

@FGD

[ModifierOnlyShortcuts]
Meta=org.kde.lattedock,/Latte,org.kde.LatteDock,activateLauncherMenu|

@glomar_response I have edited the wiki page, too late for you but hopefully on time for others.
Tnx for bringing this up!

[SGS]

I changed it two days ago and it works for me.

Add Meta keyf or launcher (bdb8d96a) · Commits · Garuda Linux / Themes and...

[ModifierOnlyShortcuts]
Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu

[tusharhero]

When is the update coming out? I just updated but I don't see any option to migrate to latte-free dragonized version.

[dr460nf1r3]

There have been a few irritations that we still have to solve prior to triggering the update for everyone (eg. setting the wallpaper via plasma scripting turned out to be buggy at times, leaving the the default wallpaper). Rushing it doesn't seem like the right idea at this point.

[dr460nf1r3]

@glomar_response

So before migration Latte handles the key to open the application menu. Currently performing the migration does not unbind Latte from the key, and thus the menu does not open unless I manually restart Latte, right click the dock ~> Configure Latte ~> Uncheck the options binding to the application menu.

@FGD

As part of the migration, that needs to be checked.

However the key should be (was for me) located in ~/.config/kwinrc

Make sure to remove the kwin meta key binding during migration (80709e96) ·...

Gotcha, it is now removed during the migration.

@SGS

I changed it two days ago and it works for me.

This sadly does not propagate to existing installations (all of the installations are that are getting migrated).

[Hamster1962]

Manually editing the above file works for me, I did it a few days ago after a Google search.

H

[rock.flag.eagle]

I do think it would be nice to have a bit of choice for users. When they load the wizard it would be cool to pick from different color themes? The purple is a bit much for me sometimes

[SGS]

@rock.flag.eagle

I do think it would be nice to have a bit of choice for users

You can easily edit themes in system settings.
And read

Make dragonized more blue

Make dragonized more blue I would like to be able to program And what looks like nothing here has cost me some “time” of my life, because I have zero idea about KDE. Most of the time I was looking for where these pink things come from and where these colours are stored . Then I recoloured the dragonized to my taste. Now all that’s missing is a correct tutorial (if the rest I made is usable ) Would be nice if someone would be intereste…

[dr460nf1r3]

I believe we have the wallpaper issue fixed by now. I'm not longer able to set the default Plasma wallpaper via applying global theme after this:

Try setting the wallpaper via plugin (91aedcfc) · Commits · Garuda Linux /...

If someone wants to help testing, apply the global theme after updating to the latest garuda-dr460nized-next package and report whether the right wallpaper gets applied.

[ninioArtillero]

It works on my system

By the way, buttons on maximized windows disappear (since a couple of updates).

[FGD]

What is the output from terminal of the following command:

paru -Qi plasma5-applets-active-window-control plasma5-applets-window-buttons

[dr460nf1r3]

I just triggered the migration for everyone! garuda-dr460nized 3.0 is live! Thanks for everyone who contributed to making this a great version

[lum1nuss]

The Plasma panel purple glow (instead of that eye-burning white flash) looks absolutely amazing. Can confirm that the Window Buttons applet works as well. Awesome work, Garuda team! Thank you for working so hard on this - I'd get you all coffee or your preferred drink if we all knew each other irl haha

Btw with changing the panel highlight colour, where exactly can it be changed? It's not influenced by the appearance > colours menu in KDE, so it must be a value within a file somewhere? I don't want to have to completely change the entire theme in order to change that one colour I had a look through the thread again but can't seem to find anything (unless I can't read lol)