Sway Config Error

Help & Support
1

My host OS is Fedora Sway Atomic

error
error2560×213 105 KB

So every time I log into a sway session I get this error message. I just hit the X and go about my day. It doesn’t cause any issues in my workstation usability.

I added these lines to my sway local override config that lives in my home folder:
#screenshots
bindsym Print exec grim ~/Pictures/$(date +%Y-%m-%d_%H-%m-%s).png

For anyone who doesn’t know in the read only portion of my atomic system there is a sway config file. I have a local override in my home folder at ~/.config/sway/config the system will use the local user override file and probably default back to the system config file if that doesn’t work or doesn’t exist.

I added this line so that when I press the prtsc (print screen) button on my keyboard, a screenshot is saved as a .png and labeled with the date/time etc. and saved to my Pictures directory.

I came up with this solution using Gemini (a now deceased version) by giving it explicit instructions something along the lines of: Host OS Fedora Sway Atomic, I want this button to take a screen shot, label it such and such way as a .png and put it in this directory. (Though much wordier than that)

This solution works. But I get this quirky little error message when I log in and am just wondering if anyone can shed some light on that.

2 Likes
2

From what I see in the screenshot: that is not an error but a warning of of the original binding being redefined. Your custom binding works after all.

A possible way to suppress the warning might be to comment out default binding for <print screen> key so that there were no redefinition.

Good luck!

3 Likes
3

What has most likely happened is that you have included the /usr files in your custom file in your home directory.

What many of us do, is copy the file from the usr directory and then modify it. Look at the bottom of your config file and see if the /usr files are included.

I do agree though, that there should be some way to force it not to recognize a duplicate entry or as @ugnvs suggested, to disable the warning.

3 Likes