In today’s chautauqua…
This is the problem with assuming, there’s nothing in their notes about having a second monitor connected at the same time as the one that is tearing. This possibility didn’t even occur to me, but it’s plausible.
edit: literally a minute after I reply, OP confirms you are correct in your assumption.
although another monitor flicker when the monitor tears.
I assume that you mean “the 2nd monitor flickers under the same conditions that the 1st monitor tears”, or are you saying that you have tried 3 separate monitors, all with different behavior?
Take your time and walk through all the steps that folks have laid out for you in these comments, and try to answer each question we’re asking. There just isn’t enough detail for us to give solid answers or further suggestions.
Ohhh, very odd. I’ve been noticing a lot of inconsistencies between Lemmy and PieFed like this, and now an app is something else entirely. Seems the fediverse is not unified on markdown support!
Apologies if I came off as condescending, not my intention.
I’m not sure exactly what you’re asking about. Do you mean the directory names?
In unix, ~ expands to the user’s home directory path and / just separates each level in the path.
You might be on the right track thinking it’s the monitor, but could also be related to the GPU (assuming it’s the same PC/card that tears across different OS’s).
If different machines all tear the same way, then I’d say definitely the monitor and the manufacturer may or may not be able to give some insight.
Otherwise, I think we might need some more details about the machine’s hardware to be able to give any meaningful advice other than double-checking driver versions and firmware updates, etc.
Things that might be helpful:
I do a similar thing for code stuffs, generally always make a ~/Git and ~/Godot so I always have a spot for things.
I also delete most of the auto-created ones if I’m using a DE that does that, because I have my own organization going on with various external/network drives. Only one I have always kept is ~/Downloads.
Indeed, folks tend not to look into the docs enough to realize find is a powerful tool on its own!
I think the other answers were just adhering to the request (trying to troubleshoot the script as is), but I generally go for pragmatism despite not being what was actually requested.
It might be instance related, I’m on PieFed, so perhaps the markdown implementation is different.
Also, I realized that the parameter expansion might not be straightforward and added the GNU docs on it, but looks like you found a post about it at the same time! Glad to hear it got you sorted out.
You can do the entire thing as a one-liner using only find:
find ./ -type f \( -iname "*.jpg" -or -iname "*.png" \) -exec sh -c 'mv "$0" "$(uuidgen -r).${0##*.}"' {} \;
Test on my machine:
phaedrus@sys76 ~/D/test> ls -lh
total 0
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test1.jpg
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test1.png
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test2.jpg
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test2.png
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test3.jpg
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 test3.png
phaedrus@sys76 ~/D/test> find ./ -type f \( -iname "*.jpg" -or -iname "*.png" \) -exec sh -c 'mv "$0" "$(uuidgen -r).${0##*.}"' {} \;
phaedrus@sys76 ~/D/test> ls -lh
total 0
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 062d8954-9921-42bd-ad24-0e4ed403a5db.jpg
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 111f859f-b1fe-4488-b2bc-75585320e3a3.png
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 39b9fe4e-7a05-43c9-b30a-69e9a13aa3a9.png
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 57bda91e-49e5-43fe-8318-aeeb2e3adde7.png
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 97398eb7-54aa-488f-8fbe-0b84b5e5a50d.jpg
-rw-r--r-- 1 phaedrus users 0 Dec 6 01:08 f7a13274-e2c0-4fa7-9907-c590d1280c2e.jpg
btw, Lemmy doesn’t like language specifiers in the multi-line code blocks, so it’s difficult to read all that in its current form since there are no tabs to know how you have it formatted. Makes it virtually impossible to troubleshoot your specific script.
edit: further reading on the ever useful variable expansions (${0##*.} portion of my one-liner):
https://www.gnu.org/software/bash/manual/html_node/Shell-Parameter-Expansion.html
FinishedTFY
Believe it or not, it’s still less work than NixOS (at least for a daily-driver OS)
Incredibly simple, free, and quick thing to add for user confidence. Doesn’t sit well with me they can’t be bothered, what else does that attitude apply to in the OS?
It’s 2025, the EFF and certbot exists, but no https? Interesting.
Any who, thanks. I’ll check it out, but I’m a little bit turned off by the above.
This reminded me of my old friend DSL, had to check up on it. Didn’t realize they re-released it!
No longer at the 50MB size, but still 700MB would be great for a small OS on this odd piece of older hardware.
No differently than it’s used in Windows, plus a few more key-chords that utilize it. That’s the default in GNOME and KDE at least, and probably other DEs as well.
I’m more interested in what people do with that strange menu key sitting next to my touch-starved right-CTRL. I know it’s for pulling up the context menu, but I have literally never used it for any reason. When I’m 100% keyboard, I’m probably in a terminal and it won’t do anything any way.
Others have said it, but SyncThing all the way. Open source, been around for a decade, battle tested, no cloud, full control over everything.
I didn’t see this mentioned, but you can also tell KeePass to auto reload the database if the file gets updated elsewhere. Makes it so you can run the same KeePass database on multiple devices with live/realtime updates. I’ve used this setup instead of vaultwarden/passbolt on several IT teams to keep the important stuff separate from the normal systems. It’s not on by default usually, but right in the Basic Settings page under File Management.
I have KeePass+SyncThing on 3 laptops, 2 androids, and a home server. If I add a password to one of my androids while I’m out and about (and I have cell data), next time I sit down at my desk it’s already available. Vice versa works, too. If my home server dies, the other devices don’t care and keep syncing amongst themselves. I think I’ve had some version of this setup going since SyncThing released, I can’t imagine using anything else.
Do note that since there is no cloud or infrastructure behind it, sync conflicts do happen when a device in the network goes offline for a while. It’ll never get rid of files if there’s an error syncing, but instead create a second copy with a timestamped filename. If this happens to your password db file, KeePass can then merge the two copies together and sort things out mostly automatically. Over the many years I’ve been using this, it doesn’t happen as often when you’re the only person using any of the devices that sync. It can happen a lot when you share the setup with someone else, though.
It wasn’t at all clear that you had a 2nd monitor connected, that is also useful information. Still, not enough data to really know.
Are both monitors the same make and model? If not, then it seems likely there’s an issue with your GPU or HDMI cable, but the symptoms are different because the monitors are manufactured by different companies. If the monitors are identical to each other, then we’re back to most likely being an issue with the 1st monitor.