johan
Member
Posts: 23
Likes: 17
|
Post by johan on Sept 22, 2021 10:27:31 GMT
Hi fans, I am very happy with Bodhi on my T430 desktop. However, I've noticed something strange. It works fine with the built in laptop screen, but when I put the T430 in my dock which is connected to a monitor, Bodhi seems to struggle with the screen or format and only the wallpaper appears without being able to use Bodhi. I use a multiboot system and the strange thing is the other distro's (Linux Mint, Ubuntu mate) work fine.
What could be wrong here? Kind regards, Johan from the Netherlands
|
|
|
|
Post by thewaiter on Sept 22, 2021 11:29:03 GMT
Hello and welcome
Try to play with Monitor settings a.k.a arandr. You can find it in menu or simply press ALT ESC and start typing "arandr" (without quotes). There is a possibility for multi screens. If OK, save to Moksha Startup.
Good luck
Stefan
|
|
enigma9o7
Crew Member
Posts: 1,436 
Likes: 1,338
|
Post by enigma9o7 on Sept 22, 2021 13:52:24 GMT
Hi fans,
I am very happy with Bodhi on my T430 desktop. However, I've noticed something strange. It works fine with the built in laptop screen, but when I put the T430 in my dock which is connected to a monitor, Bodhi seems to struggle with the screen or format and only the wallpaper appears without being able to use Bodhi.
I use a multiboot system and the strange thing is the other distro's (Linux Mint, Ubuntu mate) work fine.
What could be wrong here?
Kind regards,
Johan from the Netherlands
To me this sounds normal and perhaps you're unfamiliar with having a second monitor, other than you say it behaves different on other distro. Can you describe what's different Mint/mate? Do they not put the wallpaper? Maybe their desktops put a copy of the shelves onto other monitors? Or what is it they are doing different than Bodhi that you want?
The fact the wallpaper is on it means its enabled and working, and if you havent rearranged it I believe its oriented to the right of your main screen. Can you drag apps to it? Do you see your mouse pointer move when you move your mouse onto it?
With "Monitor Settings" under applications/preferences you can rearrange the relative positions of your two screens, or plop them on top of each other for mirror type mode...
|
|
johan
Member
Posts: 23
Likes: 17
|
Post by johan on Sept 23, 2021 13:09:16 GMT
Thank you Stefan and Enigma,
Changing settings in arandr definately helped. Both on my Medion Tv/monitor as well as on the built-in laptop screen I now have the wallpaper and the menu bar.
One strange thing, this happens only on the built-in T430 screen. At startup a error message appears.
/home/j/.e/e/applications/startup/startupcommands is onverwachts opgehouden met draaien.
But for the rest, it works fine. I am very happy with Bodhi Linux.
regards.
|
|
enigma9o7
Crew Member
Posts: 1,436
Likes: 1,338
|
Post by enigma9o7 on Sept 23, 2021 14:28:34 GMT
I bet I know what that is.
If you added arandr commands to startup (saveto moksha) then it tries to execute them on startup. If your TV isn't on at the time, it gets an error. This happens to me too, and how I resolved it in my ~/.e/e/applications/startup/startupcommands was by wrapping it in an if fail, then do something else, so that moksha doesn't see the failure.
if ! xrandr --output VGA-0 --off --output LVDS-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal --output HDMI-0 --mode 1920x1080 --pos 0x0 --rotate normal ; then
echo "Cannot enable HDMI when nothings turned on, dumb thing, but cant let moksha see the error when it fails"
fi
|
|
johan
Member
Posts: 23
Likes: 17
|
Post by johan on Sept 23, 2021 15:11:37 GMT
Thanks again. So you replaced the text of the error message by a witty text made by yourself. This for me (level user+) is too much to edit the startupcommands file. I think you need to do that with nano. Too complicated for me I know I would completely screw up the file. What I do is to simply live with this error which can be clicked away easily fortunately.
I assume booting time will not be affected. I have not noticed any delay.
|
|
enigma9o7
Crew Member
Posts: 1,436
Likes: 1,338
|
Post by enigma9o7 on Sept 23, 2021 15:13:08 GMT
Thanks again. So you replaced the text of the error message by a witty text made by yourself. This for me (level user+) is too much to edit the startupcommands file. I think you need to do that with nano. Too complicated for me I know I would completely screw up the file. What I do is to simply live with this error which can be clicked away easily fortunately. No problem Johan.
Paste your ~/.e/e/applications/startup/startupcommands here. It is a text file and access requires no special permission. You could attach the file here, or open it with text editor (leafpad if using GUI) and paste its contents here. I'll wrap the error handling around it for you, and you can then replace yours.
If you're not sure how to open it, paste this command into prompt:
leafpad ~/.e/e/applications/startup/startupcommands &exit
What I will do is add "if !" before your xrandr line and "; then" after it. The "if !" part means, if (whatever comes next) fails.
On the next line I'll put something useless like "echo hello" , thats what will happens if the xrandr command fails, but its running in background so you wont see it anyway, so no more error message popup from Moksha, cuz moksha wont see the failure, it'll see that the echo command was successful instead.
Then on the next line I'll close the if statement with "fi".
|
|
johan
Member
Posts: 23
Likes: 17
|
Post by johan on Sept 23, 2021 15:30:52 GMT
Thanks, I could not attach this file in this reply, therefore I have included the startupcommands file in the original text of this thread.
|
|
enigma9o7
Crew Member
Posts: 1,436
Likes: 1,338
|
Post by enigma9o7 on Sept 23, 2021 16:19:58 GMT
BEFORE: xrandr --output LVDS-1 --mode 1366x768 --pos 0x0 --rotate normal --output VGA-1 --primary --mode 1360x768 --pos 1366x0 --rotate normal --output HDMI-1 --off --output DP-1 --off --output HDMI-2 --off --output HDMI-3 --off --output DP-2 --off --output DP-3 --offAFTER: if ! xrandr --output LVDS-1 --mode 1366x768 --pos 0x0 --rotate normal --output VGA-1 --primary --mode 1360x768 --pos 1366x0 --rotate normal --output HDMI-1 --off --output DP-1 --off --output HDMI-2 --off --output HDMI-3 --off --output DP-2 --off --output DP-3 --off; then
echo
fistartupcommands (280 B) |
|
johan
Member
Posts: 23
Likes: 17
|
Post by johan on Sept 23, 2021 16:32:24 GMT
Wow! That is the solution. No more error messages. I think I have thanked you at least six times before, but I am willing to thank you for the seventh time.
|
|
|
|
Post by thewaiter on Sept 23, 2021 16:48:19 GMT
Great support Enigma9o7
Thanx
|
|
johan
Member
Posts: 23
Likes: 17
|
Post by johan on May 19, 2023 15:08:41 GMT
For your info: I did the same (same monitor, different computer Lenovo X250 also dual boot with dock) and after the changes I made to the screen, the usual error message /home/j/.e/e/applications/startup/startupcommands is onverwachts opgehouden met draaien did not pop up. Maybe this has been solved in the latest release?
|
|
