I started changing up my desktop experience as can be seen here:
I reset all the configs in Garuda Assistant and after I rebooted most of the changes I made were reconfigured.
Upon seeing this, I thought it was no problem. I could just do the same configuration steps again and be right back to where I was in 15 minutes.
I encountered a bug with Latte Dock that seems to apply on both the dr460ized configuration and the Garuda configuration.
When I try to move a dock/panel to display other than "primary display" it spits out giant blurry patches and then the panel/dock in question disappears, not moving to the second display.
I also got a crash after attempting to do it a second time, although the crash reporter says the info it has is not likely to be useful:
The message it spits out is "Executable: latte-dock PID: 42262 Signal: Segmentation fault (11) Time: 2/26/21 9:55:04PM EST"
Just to confirm I also booted up the latest Dr460ized live iso(02/25/20 image) and I was also unable to move panels/docks to the other display.
Please let me know what I can provide to help, such as the output of commands or any other additional details.
Perhaps it is a bug with Lattedock itself, or it could be something wrong with the new configurations.
P.S. Apologies for all the images. I know the server space is precious and I hope they don't take up too much space.
Edit: tried using an alternative lattedock layout and encountered the same problem. This could be due to something seemingly unrelated, such as those evil Nvidia Drivers.
Woke up this morning and did a system update. It did have an update for latte dock, but upon reboot the inability to move panels to displays other than "Primary Screen" persists.
I also tried switchig to the linux-lts kernel, but that also yielded no dice.
Unfortunately, my current understanding of lattedock only allows very rudimentary debugging as I described above.
I need to find some way to view a log.
My current theory is it could be some sort of issue with configuration.qml. I don't really have a good idea, latte dock also seems a little more sluggish recently.
Alright, I did exactly as you said. I renamed the latte folder latte.old and renamed the lattedockrc file lattedockrc.old
After doing so, I reset latte dock.
However, the issue still seemed to persist. I was unable to move panels/docks to other displays.
I did one experiment that may be telling
I ran sudo pacman -Rdd latte-dock-git && sudo pacman -S latte-dock
While the package off the main Arch repository was kind of borked with Garuda configurations in many ways, I was able to move docks/panels to my other display.
Unfortunately, I don't think the solution is to uninstall latte-dock-git and just use latte-dock, given the multiple issues.
But, this is telling. It seems that the problem is with latte-dock-git itself.
I don't know if anyone else is having this issue or I am seeing it in isolation.
Perhaps, if it is isolated, it could be due to my monitors being different resolutions(1920 x 1080 vs 1920 x 1200)
Here is a temporary fix: sudo downgrade latte-dock
I personally downgraded to r4985.ea214c52
I'm not sure exactly when the cut off is before it stops working. I could test it later, but I am just glad to have things up and running temporarily.
It may take a few days to have this problem solved in the git repository
With kde updates issues, first clear cache and second reset config (keeping backup).
Creating a clean new latte-dock/panel is a matter of seconds.
You may also use configSaver applet to keep backup of all local/user plasma settings.
Any tips ? should I change the init command for latte-dock to the one with --cc args?
I had 2 latte things, One was a panel at the top right and the other in the bottom middle. I deleted the top right one and substituted it by a KDE panel and the top side is not getting the compositing error anymore one where the latte dock resides
I'll try to change the latte command to init it on kde to see if using the --cc args will change anything