-
|
I recently installed Manjaro I3 and now I want to configure the system to use the second monitor Apparently the monitor detection is ok, the mouse pointer appears on the screen, but the screen itself is blank. If I use the command to open the terminal on the second monitor, the mouse cursor changes to the "text" cursor, but nothing appears on the screen. If I give a command (even without seeing what is being written), the results of the command happen in teem la. For example, if I use zenity to generate a notification popup and write this command in this "invisible terminal", the notification happens, this leads me to believe that the problem is in the terminal display, it exists but is not "rendered" . If I turn off the second monitor, the workspace that was created appears on the notebook screen, along with the terminal. I've already used xrandr to do the configuration by hand: I've already used arandr to configure the screen visually: I've already used autorandr to "automate" the settings. A curious thing is that in certain configurations I make in arandr, the second screen starts to display an image and the first screen starts to have the behavior I mentioned previously. I made the key settings in the configuration file: I've tried a lot of things, and nothing worked. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
|
Additional Information:
|
Beta Was this translation helpful? Give feedback.
-
|
From your description it's not ultimately clear in which order you are acting. You should:
Now i3 should use it and place workspaces on it, if you configured it to be an additional monitor and it's not just mirroring the first monitor. Make sure that:
I would recommend to specify both outputs (both with |
Beta Was this translation helpful? Give feedback.
-
|
I used this simplified format just to test, I really tested a lot (and learned a lot) until I found the solution, although I don't know exactly what this piece of code does to the system, it solved my problem |
Beta Was this translation helpful? Give feedback.
-
|
While I was doing more tests, my screen froze, I removed the monitor cable from the notebook, and put in a new one, it thawed the screen, after a while writing in a window, the second monitor started to show what it should. At the moment it is working, but probably when you turn it off and on it will stop working.t |
Beta Was this translation helpful? Give feedback.
-
|
as expected after removing the second monitor and putting it back in the problem returned |
Beta Was this translation helpful? Give feedback.
-
|
This won't help you in any way, but I have exactly the same situation/problem that you describe. Commenting for traction... |
Beta Was this translation helpful? Give feedback.
-
|
See my answer, I hope it helps you too |
Beta Was this translation helpful? Give feedback.
-
TL!DRChange the i3 configuration line where picom is called: Beforeexec --no-startup-id nitrogen --restore; sleep 1; picom -bAfterexec --no-startup-id nitrogen --restore; sganbialeep 1; seq 0 3 | xargs -l1 -I@ picom -b -d :0.@How did I find out how to solve the problemI finally discovered the problem! I thought: I just turn off the picom when I put another monitor on, but it has the infamous habit of locking the system when it is closed. So this "solution" was discarded. I really have no idea what I did when I ran this command, but it solved my problem. The next step was to look in the i3 file where picom was started and change it to that startup, then I tested it and finally the problem was actually resolved. I tested installing a third monitor and everything worked perfectly. @stdstijn I hope this can help you solve your problem |
Beta Was this translation helpful? Give feedback.
-
|
My picom doesn't support -d flag, I'm using edit 1: edit 2: edit 3: |
Beta Was this translation helpful? Give feedback.
TL!DR
Change the i3 configuration line where picom is called:
Before
After
How did I find out how to solve the problem
I finally discovered the problem!
I noticed that if I insisted on turning the monitor on and off at some point it would work. Well, I started eliminating everything that had to do with image display. I killed conky, took the monitor off and put it back on. It didn't solve it, I did the same with the picom and this time the monitor worked correctly. I turned the monitor off and on several times and it worked.
I thought:…