No one will ever know without logs. Otherwise we can add 100 posts to this thread and likely never answer whereas one posted log may be all we need. Please help us help you.
I’ll make a VM to replicate. I saw Cinnamon and plasma? And xfce-terminal all mentioned. Which one? I want to see what you see.
Please post your inxi -Fza --no-host
inxi -Fza --no-host
System:
Kernel: 5.17.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=31e8dffb-a868-40a9-b378-9dd5a4726523 rw quiet loglevel=3
nowatchdog
Desktop: KDE Plasma v: 5.24.4 tk: Qt v: 5.15.3 wm: kwin_wayland vt: 3 dm:
1: LightDM v: 1.30.0 note: stopped 2: SDDM Distro: EndeavourOS
base: Arch Linux
Machine:
Type: Desktop System: Dell product: OptiPlex 3060 v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: Dell model: 0NV0M7 v: A02 serial: <superuser required> UEFI: Dell
v: 1.17.0 date: 12/10/2021
CPU:
Info: model: Intel Core i5-8500T bits: 64 type: MCP arch: Coffee Lake
family: 6 model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xEC
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
desc: 1x9 MiB
Speed (MHz): avg: 900 min/max: 800/2100 scaling: driver: intel_pstate
governor: powersave cores: 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900
bogomips: 25211
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Dell
driver: i915 v: kernel ports: active: HDMI-A-1
empty: DP-1, DP-2, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:3e92
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: kwin_wayland driver: X: loaded: intel
unloaded: fbdev,modesetting,vesa gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 res: 2560x1440 size: N/A modes: N/A
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
v: 4.6 Mesa 22.0.0 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Device-2: XMOS iFi (by AMR) HD USB Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-4:3 chip-ID: 20b1:3008
class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.17.1-arch1-1 running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.49 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Dell driver: r8168 v: 8.049.02-NAPI modules: r8169 pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0
port: 4060 bus-ID: 00:17.0 chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 704.24 GiB used: 121.12 GiB (17.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT500MX500SSD1
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: <filter> rev: 023 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung
model: SSD PM871b M.2 2280 256GB size: 238.47 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 3D0Q scheme: GPT
Partition:
ID-1: / raw-size: 238.17 GiB size: 233.38 GiB (97.99%)
used: 121.08 GiB (51.9%) fs: ext4 dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 33.7 MiB (11.3%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 27.8 C pch: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 199 Uptime: 3h 24m wakeups: 0 Memory: 15.45 GiB
used: 2.24 GiB (14.5%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 Packages: pacman: 1460 lib: 432 Shell: Bash v: 5.1.16
running-in: konsole inxi: 3.3.14
I’ll start a vm and see if I can recreate it in plasma wayland.
EOS + plasma-wayland-session. Everything works as expected here too @manuel they must have some other config issue.
as far as i understand @endbob (nice username b.t.w. 
) is using xfce4-terminal under plasma?
And have set it to be used for eos-yad services?
Can confirm - when making xfce4-terminal the default application - the update button in welcome app no longer works when I click on it.
Interesting.
Welcome is based on yad which has some known problems with wayland protocols.
So setting konsole as the default terminal with KDE / wayland is the recommended setting.
Also, in file /etc/eos-script-lib-yad.conf there’s a setting EOS_YAD_TERMINAL that should be set to "konsole".
looks like xfce4-terminal is getting lost under qt and wayland … do not know how to appear properly
It’s not just QT/Plasma; on my other eos installation Gnome Wayland has the same issue.
Also both were working fine until April 1st.
so the issue could be … xfce4-terminal running under wayland. also it was not an issue before it could be it now…
you could try downgrading it to version before…
sudo downgrade xfce4-terminal
As it is indeed also working with xfce4-terminal under xfce4 and also on other xorg based WM/DE
Felt sure that was going to work, but…it didn’t 
Is there anyway of downgrading eos-welcome?
Thanks for everyone’s efforts, btw 
How did you “downgrade” xfce4-terminal? You should be able to downgrade welcome as well in the same manner.
Are you also using xfce4-terminal on your Gnome install?
I just followed the instructions in the post above by @joekamprad
Unfortunately it won’t let me downgrade eos-welcome in the same manner (it complains about No results found).
Yes, Gnome also appears to be using xfce4-terminal.
we do not archive packages …
In addition, I think downgrading welcome would help nothing.
indeed … i suggest downgrading xfce4-terminal only… as it was updated on 1. April…
I did, and it didn’t make any difference.
For now, until it’s fixed, your best work around is updating the old fashion way and not using the welcome app, or changing your default terminal back to konsole and stop using xfce4-terminal.
Yeah, I’ve pretty much accepted I’ll need to use Pacman in Wayland for the time being.
Incidentally, my default terminal in Plasma has always been konsole, and still is now. I don’t know why eos-terminal uses xfce4-terminal instead. Maybe it’s because I installed xfce later on and it seems to have taken over that function.
Anyway, thanks again for your efforts.
I can’t reply on that or how it would work. But I had zero issue when konsole was the default terminal and xfce-terminal installed. I could not recreate that bug.
