Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to remove Wayland
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
InvisibleRasta
Tux's lil' helper
Tux's lil' helper


Joined: 30 Mar 2011
Posts: 111

PostPosted: Wed Nov 07, 2018 9:17 pm    Post subject: How to remove Wayland Reply with quote

hello guys i have installed KDE but for some reason wayland got pulled in and i do not really want it. I tried to remove it and these are the outputs. Not really sur eon how to deal with it without breaking up my kde install. Keep in mind i want to keep Plasma. just remove Wayland

emerge -cav dev-libs/wayland
Code:
Calculating dependencies... done!
  dev-libs/wayland-1.16.0 pulled in by:
    dev-libs/wayland-protocols-1.16 requires dev-libs/wayland
    dev-qt/qtwayland-5.11.1 requires >=dev-libs/wayland-1.6.0
    kde-frameworks/kwayland-5.50.0 requires >=dev-libs/wayland-1.13.0
    kde-plasma/kscreenlocker-5.13.5 requires dev-libs/wayland
    kde-plasma/kwin-5.13.5 requires >=dev-libs/wayland-1.2
    media-libs/mesa-18.2.4 requires >=dev-libs/wayland-1.15.0:0/0=[abi_x86_32(-),abi_x86_64(-)], >=dev-libs/wayland-1.15.0:=[abi_x86_32(-),abi_x86_64(-)]

>>> No packages selected for removal by depclean
Packages installed:   962
Packages in world:    84
Packages in system:   43
Required packages:    962
Number removed:       0


emerge -cav dev-libs/wayland dev-libs/wayland-protocols dev-qt/qtwayland kde-frameworks/kwayland kde-plasma/kscreenlocker kde-plasma/kwin media-libs/mesa

Code:

Calculating dependencies... done!
  dev-libs/wayland-1.16.0 pulled in by:
    dev-libs/wayland-protocols-1.16 requires dev-libs/wayland
    dev-qt/qtwayland-5.11.1 requires >=dev-libs/wayland-1.6.0
    kde-frameworks/kwayland-5.50.0 requires >=dev-libs/wayland-1.13.0
    kde-plasma/kscreenlocker-5.13.5 requires dev-libs/wayland
    kde-plasma/kwin-5.13.5 requires >=dev-libs/wayland-1.2
    media-libs/mesa-18.2.4 requires >=dev-libs/wayland-1.15.0:=[abi_x86_32(-),abi_x86_64(-)], >=dev-libs/wayland-1.15.0:0/0=[abi_x86_32(-),abi_x86_64(-)]

  dev-libs/wayland-protocols-1.16 pulled in by:
    media-libs/mesa-18.2.4 requires >=dev-libs/wayland-protocols-1.8

  dev-qt/qtwayland-5.11.1 pulled in by:
    kde-frameworks/kwayland-5.50.0 requires >=dev-qt/qtwayland-5.9.4:5[egl(+)]

  kde-frameworks/kwayland-5.50.0 pulled in by:
    kde-plasma/drkonqi-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/kscreenlocker-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/kwayland-integration-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/kwin-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/libkscreen-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/plasma-integration-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/plasma-workspace-5.13.5-r1 requires >=kde-frameworks/kwayland-5.46.0:5
    kde-plasma/powerdevil-5.13.5 requires >=kde-frameworks/kwayland-5.46.0:5

  kde-plasma/kscreenlocker-5.13.5 pulled in by:
    kde-plasma/kwin-5.13.5 requires >=kde-plasma/kscreenlocker-5.13.5:5
    kde-plasma/plasma-meta-5.13.5 requires >=kde-plasma/kscreenlocker-5.13.5:5
    kde-plasma/plasma-workspace-5.13.5-r1 requires >=kde-plasma/kscreenlocker-5.13.5:5

  kde-plasma/kwin-5.13.5 pulled in by:
    kde-plasma/plasma-desktop-5.13.5-r3 requires >=kde-plasma/kwin-5.13.5:5
    kde-plasma/plasma-meta-5.13.5 requires >=kde-plasma/kwin-5.13.5:5
    kde-plasma/plasma-workspace-5.13.5-r1 requires >=kde-plasma/kwin-5.13.5:5

  media-libs/mesa-18.2.4 pulled in by:
    app-emulation/wine-staging-3.18 requires >=media-libs/mesa-13[osmesa,abi_x86_32(-),abi_x86_64(-)]
    dev-qt/qtgui-5.11.1 requires media-libs/mesa[egl]
    dev-qt/qtwayland-5.11.1 requires media-libs/mesa[egl]
    kde-frameworks/kwayland-5.50.0 requires media-libs/mesa[egl]
    kde-plasma/kinfocenter-5.13.5 requires media-libs/mesa
    kde-plasma/kwin-5.13.5 requires media-libs/mesa[egl,gbm,wayland]
    media-libs/gst-plugins-base-1.14.1 requires >=media-libs/mesa-9.0[egl,abi_x86_64(-)]
    media-libs/libepoxy-1.5.3 requires media-libs/mesa[egl,abi_x86_64(-)]
    virtual/opencl-0-r5 requires >=media-libs/mesa-9.1.6[opencl,abi_x86_32(-),abi_x86_64(-)]
    virtual/opengl-7.0-r2 requires >=media-libs/mesa-9.1.6[abi_x86_32(-),abi_x86_64(-)]
    x11-apps/mesa-progs-8.3.0 requires media-libs/mesa
    x11-base/xorg-server-1.20.3 requires >=media-libs/mesa-18[egl,gbm], >=media-libs/mesa-18
    x11-libs/cairo-1.14.12 requires >=media-libs/mesa-9.1.6[egl,abi_x86_64(-)]

Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 6876
Location: almost Mile High in the USA

PostPosted: Wed Nov 07, 2018 10:00 pm    Post subject: Reply with quote

At least according to portage, kscreenlocker and kwin have hard dependencies on dev-libs/wayland. Unfortunately I'm not a KDE user so I don't know what this means, but it seems like you cannot remove dev-libs/wayland.

There's also the question whether it's actually using wayland, it is linking it in but may not be actually using it? I don't know...
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed watching?


Last edited by eccerr0r on Wed Nov 07, 2018 10:01 pm; edited 1 time in total
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Wed Nov 07, 2018 10:00 pm    Post subject: Reply with quote

There is no way around dev-libs/wayland. kwin hard-depends on it, and even while you are in an X session, kscreenlocker is using parts of its wayland protocol code for secure session locking.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
InvisibleRasta
Tux's lil' helper
Tux's lil' helper


Joined: 30 Mar 2011
Posts: 111

PostPosted: Wed Nov 07, 2018 10:08 pm    Post subject: Reply with quote

i see, so basically ther eis no way to have kde withou twayland.. are they porting kde to wayland a little at a time?
i tried logging in as plasma wayland in sddm and the system just frooze..
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Wed Nov 07, 2018 10:27 pm    Post subject: Reply with quote

InvisibleRasta wrote:
are they porting kde to wayland a little at a time?

that's... how it usually works :)

Plasma Wayland works fine for what it currently is (with several known errata), but to answer why it did not work for you is impossible without knowing GPU driver and type of session manager.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Thu Nov 08, 2018 3:18 am    Post subject: Reply with quote

asturm wrote:
InvisibleRasta wrote:
are they porting kde to wayland a little at a time?

that's... how it usually works :)


While I just need not to miss the moment to dump KDE, when it becomes too much Wayland :)
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Thu Nov 08, 2018 3:26 am    Post subject: Reply with quote

wayland or not, it would actually be nice to remove kscreenlocker, but, alas ....
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 521
Location: Germany

PostPosted: Thu Nov 08, 2018 8:23 am    Post subject: Reply with quote

dmpogo wrote:
wayland or not, it would actually be nice to remove kscreenlocker, but, alas ....


Well, one can become "minimalist" and use stuff line awesome or ratpoison. Then no questions about kscreenlocker come up :wink:
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Thu Nov 08, 2018 10:31 am    Post subject: Reply with quote

dmpogo wrote:
While I just need not to miss the moment to dump KDE, when it becomes too much Wayland :)

Do you have a rational explanation for the Wayland hate?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Thu Nov 08, 2018 7:37 pm    Post subject: Reply with quote

asturm wrote:
dmpogo wrote:
While I just need not to miss the moment to dump KDE, when it becomes too much Wayland :)

Do you have a rational explanation for the Wayland hate?


It is not hate, it just seems boring and not forward thinking. In a way pedestrian. In contrast to X11, which was mind-boggling great and forward thinking conceptually, especially back in early 90-s when I first encountered it, when my colleagues were sitting in windows 3.1 :) So just aesthetical attachment to old friend.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Thu Nov 08, 2018 7:41 pm    Post subject: Reply with quote

v_andal wrote:
dmpogo wrote:
wayland or not, it would actually be nice to remove kscreenlocker, but, alas ....


Well, one can become "minimalist" and use stuff line awesome or ratpoison. Then no questions about kscreenlocker come up :wink:


Well, I still have my old fvwm2rc scripts around, I'll be pretty OK with them as well :) (and in terms of window managers, we have lost since old days some capabilities I loved, such as virtual space. Present day workspaces, including KDE ones, are a sad joke ). But of course I meant narrowly, staying with KDE ....
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Thu Nov 08, 2018 8:04 pm    Post subject: Reply with quote

dmpogo wrote:
It is not hate, it just seems boring and not forward thinking. In a way pedestrian.

Could you elaborate? The X developers working on wayland protocol clearly think different. Sure, a new way to paint your desktop on the screen does not seem that revolutionary when there already is a thing that does 'the same', meanwhile X has several dead ends that are being worked around for years (or simply have no solution, like screens with vastly different DPI).
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
1clue
Advocate
Advocate


Joined: 05 Feb 2006
Posts: 2404

PostPosted: Thu Nov 08, 2018 8:47 pm    Post subject: Reply with quote

dmpogo wrote:
Well, I still have my old fvwm2rc scripts around, I'll be pretty OK with them as well :) (and in terms of window managers, we have lost since old days some capabilities I loved, such as virtual space. Present day workspaces, including KDE ones, are a sad joke ). But of course I meant narrowly, staying with KDE ....


Would you mind sharing? I had fvwm back when it was fvwm2, and XFree86 was still the norm. I've lost my configs I had, and the published files don't seem to work well with me. I'd like to get back on it, if I could find an adequate starting point.
_________________
You can't fix yourself by breaking someone else.


Last edited by 1clue on Fri Nov 09, 2018 1:22 am; edited 1 time in total
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Fri Nov 09, 2018 12:31 am    Post subject: Reply with quote

asturm wrote:
dmpogo wrote:
It is not hate, it just seems boring and not forward thinking. In a way pedestrian.

Could you elaborate? The X developers working on wayland protocol clearly think different. Sure, a new way to paint your desktop on the screen does not seem that revolutionary when there already is a thing that does 'the same', meanwhile X has several dead ends that are being worked around for years (or simply have no solution, like screens with vastly different DPI).


I am interested in network transparency, which essentially means that the server attached to display hardware should render, no the clients. I still cannot shake off the feeling I had coming to England in 1992 and having on my desktop graphical windows (sure graphics was simple then) opened from Berkeley, Paris (where I did some calculations), not to mention couple local Cambridge machines at the same time.
Back to top
View user's profile Send private message
AJM
Tux's lil' helper
Tux's lil' helper


Joined: 25 Sep 2002
Posts: 83
Location: Aberdeen, Scotland

PostPosted: Fri Nov 09, 2018 11:44 pm    Post subject: Reply with quote

I know exactly what you mean, dmpogo, and I think you're right. I don't know if you've read about the Arcan display server, but reading about that gave me a very different feeling than reading about Wayland.

Reading about Arcan (there are lots of well written in-depth blog posts about the design and implementation) makes something "click" in my mind - I can see it as really solving problems that the Wayland authors are aware of but decided are too difficult to solve properly, or just side issues of little importance.

Then again, I'm really very happy with X11 and WindowMaker for now, just as I was nearly 20 years ago!
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Sat Nov 10, 2018 1:40 pm    Post subject: Reply with quote

Thanks, but no thanks to a display server depending on lua.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
dspahn
Guru
Guru


Joined: 22 Jun 2006
Posts: 351

PostPosted: Sun Nov 11, 2018 3:22 am    Post subject: Just curious.... Reply with quote

Is there some reason why choosing Plasma (The choice without wayland) doesn't work? Wayland has never worked with my card- X just bombs, but when I simply use the Plasma x-session setting, it works.... So is there some advantage to not having Wayland as an unused option?
_________________
---

Since there is no admin beer, I stick to root beer.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2475
Location: Canada

PostPosted: Sun Nov 11, 2018 8:31 pm    Post subject: Reply with quote

AJM wrote:
I know exactly what you mean, dmpogo, and I think you're right. I don't know if you've read about the Arcan display server, but reading about that gave me a very different feeling than reading about Wayland.

Reading about Arcan (there are lots of well written in-depth blog posts about the design and implementation) makes something "click" in my mind - I can see it as really solving problems that the Wayland authors are aware of but decided are too difficult to solve properly, or just side issues of little importance.

Then again, I'm really very happy with X11 and WindowMaker for now, just as I was nearly 20 years ago!


Thanks for point to Arcan, I'll read about it more !

I maybe wrong here, or misunderstanding something, but if I am to add some rationality, I feel that wayland is what is said to be 'one the wrong side of history'. I think that the central role of personal computing in a sense of desktops/laptops running all-local software is coming to an end. I think there will be mobile platforms, and 'cloud' services where data processing/storage will be doneover "there" while locally you have run a displaying hardware (doesn't it remind of X-terminal?). So at the end I think rendering should be done where display is, in a way optimized to display hardware, not where clients are. And wayland paradigm is a dead end here. This setup was always somewhat the case in research computing, that's where X was born explicitly having in mind networked computers. But it is becoming quite everywhere now. Say my daughter is a lawyer - when she works from home, she is using some proprietary software on her firms server (via VPN), they are not even allowed to have clients files on personal laptops. She has lots of pain of displaying graphiscs generated remotely. How does wayland will help here ? I'm not saying X is the best ever written implementation, but it had a right model of what should be done.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum