Hy!
First of all, i like the new forum. Beautiful with this black theme.
My problem is using the os with three display.
I have 2 monitor and a laptop. The laptop is an Acer Aspire V5.
One of the monitor connected with HDMI and one of with VGA.
I am using this with the Intel HD graphics 520. I also have an Nvidia, but i never used it.
So
The laptop monitor is gone when i sign in.
Before i sign in, the 3 monitor works.
After a plug in and out the vga, the laptop monitor goes to work.
And before this post, the laptop monitor shut down, and when i lean to the laptop screen i saw it palely, but dont react to anything.
What should i do? Install the Nvidia and use with it? Are the Intel graphics card too weak for three display?
Thanks for the reply!
One of the main reason that I’m using Gnome now, is because Mate had a terrible support with my 2 screens at work after getting back from suspension or hibernation… With Gnome everything works…
i don’t think that wake up problems are directly caused by mate, and anyways you should try with a recent version of mate with all the latest stability updates, including those of these last weeks
It basically forgot every time that I went from hibernation how my screens were setup… so everytime that I had to take the laptop off the dock, I needed to go to settings to reconfigure. With Gnome it works every time.
I found a new bug.
It seems like mate stucked at my home display config, and the screen shuted down after the login without any monitor connected to it. The “solution” is not the best: i have to close the lid.
And also the wifi dont start with the system. The solution is to close the lid or plug in an ethernet.
SO
I am thinking about this bug. I use my laptop without monitor, and it seem like the OS cant forget the config that i used to set.
Proof: about a month ago i used my laptop with monitor and the laptop lid is always close, set it to off in Displays menu.
I think thats the main problem, that shut down my laptop screen after login.
Is there a way to remove the mate saved sessions? a cant found anything on the net
this is not a parrot bug, this is just a hardware incompatibility with debian, and again, it is not a faulth of debian but it is a faulth of your computer manufacturer which has not respected some standards (acpi is surely involved)
trust me, parrot works almost anywhere else and your problems are very hardware related and not reproducible, so you have to find a custom workaround specific for your hardware