Closed Konglomneshued closed 11 months ago
If xrandr
takes 1.3 seconds to run, that's the issue you need to resolve. It indicates a problem with your system/drivers, and affects every program that queries your system for that information. It's not a wezterm bug!
Unfortunately the only issues I can find for xrandr on Google are related to extra monitors, which I have none connected.
I have installed my drivers according to my distro's guidelines and there seems to be nothing wrong with the installation. I'm not sure what else I can do.
I'd suggest trying to find kernel/driver options to disable those additional connections.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
I reached out to the EndeavourOS community and discovered I have something wrong with my OS installation, which is what's making xrandr so slow. I tested in a VM and it only takes .0x seconds, don't remember the exact amount but it's irrelevant.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
Linux X11
Which Wayland compositor or X11 Window manager(s) are you using?
i3wm with picom
WezTerm version
wezterm 20230904-133103-914f18b1
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
Wezterm appears to take about one and a half seconds to start.
Timing wezterm:
Timing xrandr it takes 1.3 seconds.
Looking at other issues they do not seem to apply to my situation: I have no external monitor, I do not have the app image installed.
I've attached the logs of WEZTERM_LOG=trace wezterm in the logs section.
To Reproduce
No response
Configuration
It happens with or without my config.
Expected Behavior
The terminal opens responsively.
Logs
Anything else?
I installed both the standard and git version from the AUR and I have the same issue.