https://bugs.kde.org/show_bug.cgi?id=478272
--- Comment #8 from Michał Dec <moog...@gmail.com> --- (In reply to Andreas Sturmlechner from comment #7) > I'm mostly here because you filed a packaging support question with Gentoo > specific language upstream. Alright, sorry for the rash response. I should have filed a bug in Gentoo for what I've experienced with Wayland. I'm not sure if my experience even holds true in current times, because this was a problem somewhere 3-5 years ago. My bad. The reason why I appear allergic to Wayland is that I've tried a few times, over the span of 2018-2021, to globally enable Wayland in USE and try to use it in a productive manner. I couldn't and LXQt has not supported it at the time, so I did the obvious thing and reverted my course of actions. However, over the passing months since that action, I've noticed that completely unrelated applications, mostly Gtk ones, stopped working. Upon inspection, I've noticed that they don't because they can't find Wayland libraries. When they all were rebuilt after enabling Wayland, but before disabling it, they have been dynamically linking against Wayland libraries without communicating this through USE, which tricked Portage into thinking that upon disabling Wayland globally a rebuild of all those applications is not needed. I had to painstakingly investigate all imports of all installed binaries and libraries to hunt down every package that has decided to go down with the ship in a manner of speaking, and prevent me from using them if I remove Wayland. If I can reproduce this, I will file this bug in Gentoo, because this is a problem with ebuilds not controlling if the source configure stage can pull in Wayland as a dependency if it finds Wayland exists on the system. So, this is the experience that has put me off Wayland. As for the topic of this bug report, I think what Nicolas has proposed thus far is a good solution. I'm on the "default/linux/amd64/17.1" profile and as far as I know, neither X or Wayland are implicitly enabled here, because I had to explicitly enable X in pretty much everything I want to use with a DE, which means not every package that my dependencies can pull. -- You are receiving this mail because: You are watching all bug changes.
