-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Third Monitor 'Inactive' Since Update to Sway 1.4 #5008
Comments
Please try wlroots from latest master with |
Is that just an environment variable or is it in a config file somewhere? |
Yes, its just an environment variable. |
Sorry, another quick question, I know wlroots and sway have close dependency - should I also build the latest master of sway? |
It won't hurt to do that as well, but I think there haven't been any breaking changes. |
Is there a way to confirm that my computer is using the right wlroots? I built using the instructions on github but that and the environment variable don't seem to have had an effect. |
Can confirm, had to upgrade from wlroots |
As I said, I tried this and it didn't work. Is there away to confirm which version of wlroots my pc is using, incase there's somehow versions on here. |
Have you tried installing from the master branch at all? Or do you have a package manager that installed Sway for you? I'm not sure where you check the wlroots version(not on my laptop atm), but you should probably also double check that you have |
I installed from the git master with the instruction on git. And yes, the environment variable is set before sway starts and is still set if I check from within a terminal emulator inside sway. |
Seeing this from the Fedora Module repo sway:rolling. Setting WLR_DRM_NO_MODIFIERS=1 does not help (wlroots-0.10.0-5.module_f31+7694+72cbf402.x86_64). |
I had the same problem with Sway 1.4. Fixed with aur/wlroots-git (0.10.0.r18.g68820d6c-1) and export WLR_DRM_NO_MODIFIERS=1 |
10.x release != master branch. |
His version indicates that he is 18 revisions on top of 0.10.0 on commit 68820d6c… which is the current master commit. |
I had a slightly different problem, where my one external monitor over USB-C wasn't working. I can confirm my external display is working again with:
For NixOS 20.03beta users, this is what I put in to my overlay:
|
That fixes my third-monitor problem too, thanks @grahamc! |
Yes, I just installed |
Hi there, have moved to sway-git and wlroot-git from AUR and, with WLR_DRM_NO_MODIFIERS=1 all the monitors are now working! Thanks. |
|
swaywm/wlroots#1877 is basically the same thing, and swaywm/wlroots#1873 is also related. |
I'm having this problem with the currrent latest Sway 1.5-1 and wlroots 0.11.0-1 on my Asus N56VZ laptop, which has the Optimus setup. The laptop has a VGA port that works fine, and a HDMI port that gets recognized but stays inactive. Setting Any more ideas? |
Might just be a limitation of your GPU. Hard to tell without any more info though. |
ok here's more info. I am running Manjaro, originally with XFCE but installed Sway and I run it manually from the TTY after boot, with these environment variables set. # this may fix external monitor problem
WLR_DRM_NO_MODIFIERS=1
# make Firefox use native Wayland backend
MOZ_ENABLE_WAYLAND=1
# force wayland backend for bemenu
BEMENU_BACKEND=wayland
# Force Wayland backend for qt5 apps
QT_QPA_PLATFORM=wayland
QT_WAYLAND_DISABLE_WINDOWDECORATION=1
# for Java some apps
_JAVA_AWT_WM_NONREPARENTING=1
# general
XDG_SESSION_TYPE=wayland I'm using the free (nouveau) drivers. From what I've gathered from looking around onlie, the HDMI port is wired to the nvidia gpu. In Sway,
|
Please create a new issue with debug logs. |
|
Possibly due to sway exceeding intel bandwidth limits, by allocating new buffers before releasing old ones. See: swaywm/wlroots#1877, swaywm/sway#5008 and swaywm/wlroots#1873
Is |
Yes, I have two setups each with three monitors, and both of them require |
@Hubro |
@ChasNelson1990 Propably you only have an issue with thunderbolt security, check this out: |
My third monitor can no longer be used because |
Hi there,
I've been using sway for a while now and I really like it. My problem (below) seems to have coincided with the upgrade to Sway 1.4 (not sure of the best way to confirm this); I run an Arch system and have sway installed from the official repository.
In my office I connect my laptop to a dock which is connected to two monitors. Until said update I was able to hotplug the dock and have a three monitor set-up (internal laptop monitor + 2x external monitors). And then... this stopped.
I can now only get a maximum of two monitors running. When I hotplug the dock only one external monitor turns on but, if I allow my laptop to sleep, on wake both external monitors work but the internal laptop monitor stays off.
I believe this could be related to issue #4878 as
get_outputs
shows which ever monitor is off as 'inactive'.As per the advice there I have created a dmesg and sway log. Both can be found at https://gist.github.com/ChasNelson1990/02b615ec15839a77691d6a8be942c960 .
I believe the dock is plugged in and the system tries to sort monitors at around line 22400 in dmesg.log and 4700 in sway.log. Monitor DP-3 seems to load and activate fine but then the system seems to find two ports DP-4 and DP-5 at the same time. DP-4 is the third monitor (second external) that shows as inactive.
Output of
swaymsg -t get_outputs
:The text was updated successfully, but these errors were encountered: