In today’s chautauqua…

  • 0 Posts
  • 41 Comments
Joined 3 months ago
cake
Cake day: September 15th, 2025

help-circle




  • 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.



  • 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.




  • 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:

    • GPU make/model
    • Monitor model (the picture at least shows it’s an AOC)
    • Connection type (HDMI, DisplayPort, USB-C, etc.)
    • Have you tried a different connection type?
    • Have you tried a different cable of the same type?
    • Does it happen on any other monitors?
    • Are there other input ports you can try on the monitor? Do they also tear?


  • 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.


  • phaedrus@piefed.worldtoLinux@lemmy.mlBash scripting question
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    11 days ago

    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