That logo design though, 🔥 fire fire fire

Tori. Play music in your terminal. Built in rust and has great performance, and low trace on memory impact.

(⁠  ͝⁠°⁠  ͜ʖ͡°⁠ )

The other links, which you described as irrelevant, were only a source of insight - in that it gives an idea about how each of these people seem to be getting a unique problem or issue, but then it is all boils down to some issues with the xorg configuration files, when you dig deeper into the forum article problems that they are facing, and what the people that answer them are suggesting them do.

If the arch wiki is not helping you solve it then you can try the other options or escalate it to a maintainer, because those arch wikis are maintained by people that needs to be notified when there is inconsistencies or bugs or issues that are not solveable regarding xorg and xrandr.

If you believe there is reason to suspect it is gnome/ mutter, and that you tested with i3; it doesn’t tell us much, as i3 uses mostly a windows manager from what I know, whereas gnome/ mutter use GUI’s and thus requires its own configurations for the display. But if you still believe it is exclusively gnome’s/ mutters fault, you can raise it up to Gnome, then.

Understood, and I apologize for the impression. It seems to me that chatgpt prioritizes its own survivability, opting for the path of least resistance, instead of making more queries to the one using it, so as to allow itself to make better decisions based on information that it needs to know; and therefore, it would opt for giving cluster of information, without directly hinting at what are some of the questions that it needs to know before giving such a broad spectrum of information and directives to the users. I.e, it deems retorting a question with more questions as unhelpful and risky in conversations whereabouts such scenarios are negatively perceived. Damn you chatgpt for presenting me as the sheep, instead of sacrificing yourself for the greater good !

Some investigation:

Your issue that you are facing seems to be unique, and I could not find any specific issue related to yours, but some of the things which I looked up provided me with some insights:

https://gitlab.gnome.org/GNOME/mutter/-/issues/2029

https://bbs.archlinux.org/viewtopic.php?id=265374

https://askubuntu.com/questions/1392612/mouse-jumps-to-new-position-at-right-edge-of-screen-ubuntu-20-04

And some more:

https://bbs.archlinux.org/viewtopic.php?id=251854

And this, discussing extreme multihead solution:

https://wiki.archlinux.org/title/Extreme_Multihead

Here is an excerpt from that article above:

"When everything is on you should see the same output on each monitor. The desktop is “cloned” on to the secondary monitors. If all the monitors are not exactly the same shape or support different resolutions you may only see portions of the main desktop display.

The best tool to experiment with configuring your monitors to display as you want is xrandr. This may already be installed as part of your Xorg installation from either the xorg or xorg-apps groups".

Also check, https://wiki.archlinux.org/title/Multihead , section 2.2.2.

Conclusion:

The most likely scenario is that you had a certain configuration in your xorg files prior to making an update on the latest fresh install of archlinux, and, unfortunately, you may have to experiment and fiddle around with what is being suggested in the last two archlinux wiki articles linked there, as different setups may require a more involved and fine tuning process to achieve the expected results.

Recommendation:

I would recommend to find out what exact version that you had previously used which was perfectly working for you, and try consulting the xorg configuration files from there, and try bringing it up to a maintainer so that he provides it to you. Or, if you would and that version is still accessible to you, copy the configuration files yourself and see if that solves it.

Worst case scenario is that it still does not work, even after following the initiatives provided in the official arch wiki directives, wherein you can escalate it to a maintainer. And I would recommend to first consult the arch wiki articles mentioned above, before escalating it to a maintainer.

Options:

So here are the options:

• Copy old configuration of previous setup, and finding out what was the exact version of Arch you used previously which worked for you.

• Trying a different Arch Linux distro to see if their configuration works (as I had many problems solved that way in the past just by switching to different distros, and I can take their configs that works for me now, and use them in the future for my needs, and I never had that problem which you described, even with multi monitors).

• Configuring it manually, and experimenting with it by following the arch wikis suggestions.

• Escalating it to a maintainer.

I hope that helps !

The issue you’re describing could be related to the interaction between GNOME, Xorg, and multiple monitors. Here are a few steps you can take to troubleshoot and potentially resolve the problem:

1. Monitor Alignment:

   • Ensure that your monitors are properly aligned in the display settings. Check if there are any misalignments or overlapping regions.

2. Resolution and Refresh Rate:

   • Verify that your monitors are set to the correct resolution and refresh rate. Mismatched settings can sometimes cause graphical glitches.

3. Graphics Driver:

   • Make sure you have the latest graphics drivers installed for your GPU. Outdated or incompatible drivers can lead to graphical issues.

4. GNOME Extensions:

   • If you have GNOME extensions enabled, try disabling them to see if any of them are causing the problem. Some extensions may not be fully compatible with your system.

5. Xorg Configuration:

   • Check your Xorg configuration for any unusual settings. You can review the Xorg log files for any error messages or warnings related to the graphical issue.

6. Multiple Monitors Configuration:

   • Experiment with different configurations for multiple monitors, such as changing the primary display or adjusting the monitor arrangement.

7. Wayland vs. Xorg:

   • GNOME supports both Wayland and Xorg. You can try switching to Wayland to see if the issue persists. On the login screen, you can choose the session type.

8. Bug Reports:

   • Check if there are any known issues or bug reports related to your specific GNOME version, distribution, and graphics hardware. You might find relevant information or workarounds.

9. Testing with a Single Monitor:

   • Temporarily disconnect all but one monitor to see if the issue persists. This can help narrow down whether the problem is related to multiple monitors.

If the issue persists after trying these steps, you may want to seek assistance from the GNOME community forums.

If you find that my proposition soundly offly familiar to chatgpt, that’s because it is.

Don’t blame me though, because the details you have provided could be anything also. So in chatgpts defense, you could tackle these specific points, and see if any of them could be causing the technical issue. And that would be my advice too.

If you could provide more details, that would be helpful. XD

Nice keyboard.

Absolutely!

I started with mint. Hated it.

Ubuntu, Pop_Os. Hated it.

Fedora. Hated it.

Archlinux, okay, but not so much.

Manjaroo, hated it.

And now I settled with Garuda and Nobara. Like them.

I used Nobara for niche gaming (rarely use it now).

And Garuda Linux for dev work, and downloading and installing stuff, including proprietary packages. And I don’t have to configure all the things to make it capable of allowing me to download stuff from all the nice mirrors, such as the community arch mirror.

Nobara, on the other hand, is great at handling compatibility issues kinda out of the box. Such [Edit1: as GPU] drivers.

The reason I disliked the aforementioned distros was solely because of how much involved I had to be to configure them to integrate with my rare WiFi chip drivers, which triggered me when I banged my head at the keyboard for hours only to find out that my WiFi driver was not supported.

But Garuda and Nobara or a blessing, and a chef’s kiss.

That’s coming from a person who tried more than 20+ distros and/or their derivatives.

[Edit2:] All in all, I would recommend what the comment above suggested, as that will help you find your own path. The samurai path, the kenjutsu path, or the kendo path, the peaceful path, or the hackers path. ;)

[Edit3: sorry Debian users, but I DID try your distros, I just didn’t want to bother with them much as they had compatibility issues too !]