Porteus

Porteus User Forum
https://forum.porteus.org/

why do we have wayland on nemesis?

https://forum.porteus.org/viewtopic.php?f=137&t=9480

Page 1 of 1

why do we have wayland on nemesis?

Posted: 02 Jan 2021, 03:05
by francois
Why do we have wayland on nemesis, did it came in without us knowing it?

Code: Select all

[porteus ~]# updatedb
[porteus ~]# locate wayland
/usr/bin/es2gears_wayland
/usr/bin/wayland-scanner
/usr/include/wayland-client-core.h
/usr/include/wayland-client-protocol.h
/usr/include/wayland-client.h
/usr/include/wayland-cursor.h
/usr/include/wayland-egl-backend.h
/usr/include/wayland-egl-core.h
/usr/include/wayland-egl.h
/usr/include/wayland-server-core.h
/usr/include/wayland-server-protocol.h
/usr/include/wayland-server.h
/usr/include/wayland-util.h
/usr/include/wayland-version.h
/usr/include/gtk-3.0/gdk/gdkwayland.h
/usr/include/gtk-3.0/gdk/wayland
/usr/include/gtk-3.0/gdk/wayland/gdkwaylanddevice.h
/usr/include/gtk-3.0/gdk/wayland/gdkwaylanddisplay.h
/usr/include/gtk-3.0/gdk/wayland/gdkwaylandglcontext.h
/usr/include/gtk-3.0/gdk/wayland/gdkwaylandmonitor.h
/usr/include/gtk-3.0/gdk/wayland/gdkwaylandselection.h
/usr/include/gtk-3.0/gdk/wayland/gdkwaylandwindow.h
/usr/include/va/va_backend_wayland.h
/usr/include/va/va_wayland.h
/usr/lib/libva-wayland.so
/usr/lib/libva-wayland.so.2
/usr/lib/libva-wayland.so.2.1000.0
/usr/lib/libwayland-client.so
/usr/lib/libwayland-client.so.0
/usr/lib/libwayland-client.so.0.3.0
/usr/lib/libwayland-cursor.so
/usr/lib/libwayland-cursor.so.0
/usr/lib/libwayland-cursor.so.0.0.0
/usr/lib/libwayland-egl.so
/usr/lib/libwayland-egl.so.1
/usr/lib/libwayland-egl.so.1.0.0
/usr/lib/libwayland-server.so
/usr/lib/libwayland-server.so.0
/usr/lib/libwayland-server.so.0.1.0
/usr/lib/firefox/libmozwayland.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-wayland.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-waylandgtk.so
/usr/lib/pkgconfig/gdk-wayland-3.0.pc
/usr/lib/pkgconfig/gtk+-wayland-3.0.pc
/usr/lib/pkgconfig/libva-wayland.pc
/usr/lib/pkgconfig/wayland-client.pc
/usr/lib/pkgconfig/wayland-cursor.pc
/usr/lib/pkgconfig/wayland-egl-backend.pc
/usr/lib/pkgconfig/wayland-egl.pc
/usr/lib/pkgconfig/wayland-scanner.pc
/usr/lib/pkgconfig/wayland-server.pc
/usr/lib/xkbcommon/xkbcli-interactive-wayland
/usr/share/wayland
/usr/share/wayland-protocols
/usr/share/aclocal/wayland-scanner.m4
/usr/share/pkgconfig/wayland-protocols.pc
/usr/share/wayland/wayland-scanner.mk
/usr/share/wayland/wayland.dtd
/usr/share/wayland/wayland.xml
/usr/share/wayland-protocols/stable
/usr/share/wayland-protocols/unstable
/usr/share/wayland-protocols/stable/presentation-time
/usr/share/wayland-protocols/stable/viewporter
/usr/share/wayland-protocols/stable/xdg-shell
/usr/share/wayland-protocols/stable/presentation-time/presentation-time.xml
/usr/share/wayland-protocols/stable/viewporter/viewporter.xml
/usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml
/usr/share/wayland-protocols/unstable/fullscreen-shell
/usr/share/wayland-protocols/unstable/idle-inhibit
/usr/share/wayland-protocols/unstable/input-method
/usr/share/wayland-protocols/unstable/input-timestamps
/usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit
/usr/share/wayland-protocols/unstable/linux-dmabuf
/usr/share/wayland-protocols/unstable/linux-explicit-synchronization
/usr/share/wayland-protocols/unstable/pointer-constraints
/usr/share/wayland-protocols/unstable/pointer-gestures
/usr/share/wayland-protocols/unstable/primary-selection
/usr/share/wayland-protocols/unstable/relative-pointer
/usr/share/wayland-protocols/unstable/tablet
/usr/share/wayland-protocols/unstable/text-input
/usr/share/wayland-protocols/unstable/xdg-decoration
/usr/share/wayland-protocols/unstable/xdg-foreign
/usr/share/wayland-protocols/unstable/xdg-output
/usr/share/wayland-protocols/unstable/xdg-shell
/usr/share/wayland-protocols/unstable/xwayland-keyboard-grab
/usr/share/wayland-protocols/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml
/usr/share/wayland-protocols/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml
/usr/share/wayland-protocols/unstable/input-method/input-method-unstable-v1.xml
/usr/share/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml
/usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
/usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
/usr/share/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
/usr/share/wayland-protocols/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
/usr/share/wayland-protocols/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml
/usr/share/wayland-protocols/unstable/primary-selection/primary-selection-unstable-v1.xml
/usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml
/usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v1.xml
/usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v2.xml
/usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v1.xml
/usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v3.xml
/usr/share/wayland-protocols/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml
/usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v1.xml
/usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml
/usr/share/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml
/usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v5.xml
/usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v6.xml
/usr/share/wayland-protocols/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml
[porteus ~]#
Setting environment var:
https://wiki.archlinux.org/index.php/En ... nvironment

How to disable it? What will it do? May I disable wayland only for plank?
I would like to desable it generally or only for plank. I am not very good with setting environment variable. This thread seems to explain it:
https://www.reddit.com/r/archlinux/comm ... variables/

why do we have wayland on nemesis?

Posted: 02 Jan 2021, 04:26
by ncmprhnsbl
see here: https://archlinux.org/packages/extra/x86_64/wayland/ ... the required by column, mostly, simply because these packages have 'wayland support'
also your list is mostly headers(which are in the 05-devel module)
francois wrote: ↑
02 Jan 2021, 03:05
 How to disable it? What will it do? May I disable wayland only for plank?
it does nothing, unless you are running it, instead of xorg, which won't happen by accident..

why do we have wayland on nemesis?

Posted: 04 Jan 2021, 23:45
by francois
Is it possible that it interferes with plank?
plank without persistence or save changes

Answer is no.

I had a former installation with wayland files and plank worked fine.

why do we have wayland on nemesis?

Posted: 03 Apr 2025, 02:26
by francois
Within nemesis it seems that XDG_SESSION_TYPE is set to wayland thus the error message:

Code: Select all

plank     
Only X11 environments are supported
.
https://unix.stackexchange.com/question ... ack-to-x11

why do we have wayland on nemesis?

Posted: 03 Apr 2025, 02:46
by ncmprhnsbl
francois wrote: ↑
03 Apr 2025, 02:26
 Within nemesis it seems that XDG_SESSION_TYPE is set to wayland thus the error message:
nope (unless you happen to be running a wayland compositor, which i doubt ;) ) ... although this:

Code: Select all

echo $XDG_SESSION_TYPE
tty
does seem wrong . .. for some reason it's not being updated when X launches .. probably due to a overly simple xinitrc ..
as you allude to here: plank without persistence or save changes
maybe, try putting in xinitrc or ~/.xinitrc , before the exec <DE> line

Code: Select all

export XDG_SESSION_TYPE=x11
(and just let your plank.desktop do it's autostart)

why do we have wayland on nemesis?

Posted: 01 Jun 2025, 12:03
by francois
@ncm:

Sorry for this late reply. Your proposition did not work.

A.There is no .initrc in my guest folder.

Creating .xinitrc and inserting

Code: Select all

export XDG_SESSION_TYPE=x11
results in failure of the X environment to boot = no desktop.

The error message is:
Could not resolve keysym XF86DoNoDisturb Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost waiting for X server to shut down. Server terminated successfully Closing log file.

B. Inseting the same command into the .xsessionrc did not make any difference, a solution which worked according to:
https://askubuntu.com/questions/1340098 ... et-at-boot
Though the desktop will boot.

Thanks for your lights.

Note:
Things have changed much since the initiation of this thread. I will fork the most recent part alone.

why do we have wayland on nemesis?

Posted: 01 Jun 2025, 22:40
by ncmprhnsbl
francois wrote: ↑
01 Jun 2025, 12:03
 Creating .xinitrc and inserting
sorry, my bad. should have said: copy /etc/X11/xinit/xinitrc to ~/.xinitrc and put that export line before the exec line ..
possibly another way would be to edit ~/.bash_profile and insert the export just before startx:

Code: Select all

if [[ $(tty) = "/dev/tty1" && ! -e /tmp/.X11-unix/X0 ]]; then
   export XDG_SESSION_TYPE=x11
   exec startx 
fi
(and that whole section should probably be after the 'source .bashrc' section, too)
All times are UTC
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/