Closed Maxquig closed 1 year ago
Is the file marked as executable?
Yes, It is executable by anyone. In fact I execute it in a terminal window to fix my monitor settings. It works well. It seems that EVERY disto but Linux Mint has the same problem. I've tried 12 distros recently. On Saturday, November 5, 2022 at 12:14:26 PM CDT, Dominic Hayes - Feren OS Dev @.***> wrote:
Is the file marked as executable?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
I think I solved the problem I had. It turns out Autostart did start the script. It was a matter of timing. I added another script that merely launched kcalc. It launched just fine. So I guessed that it was launching my script before Xserver was up and running. So I added a 5 second delay (sleep 5) to the top of my script. That fixed it. I'm running Kubuntu right now, but later today I'll do the same in Feren OS. I'm confident it will work. Then I'll close this bug.
That fixed it for FEREN OS too. a 2 second delay is enough.
Package Name or Section of Feren OS where this bug resides Where does this bug happen? (e.g.: feren-themer-cinnamon) ___Autostart Login Scripts
Describe the bug A clear and concise description of what the bug is. When using HDMI-0 monitor with a HDMI cable, the default AMD Kaveri Graphic driver for my AMD A10-7700K Radeon CPU/GPU does not support corrections to overscanning and underscanning of my 1920x1080 resolution. I can execute the command: xrandr --output HDMI-0 --panning 1920x1080 --transform 1.085,0,-62,0,1.07,-21,0,0,1.02 to temporarily adjust my monitor's settings. But I want to run that command automatically at startup. So I wrote that command into a bash shell script.
Steps to Reproduce Steps to reproduce the behavior:
!/bin/bash
xrandr --output HDMI-0 --panning 1920x1080 --transform 1.085,0,-62,0,1.07,-21,0,0,1.02
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here. A quick WEB search indicates Fedora is the source of the bug, but I could find no evidence to indicate Fedora has any plans to fix it.