My IRC client is KVIrc, I install it from the system packages (5.0.0 Aria). On the X11 session of KDE it runs without issue, however KVIrc will immediately crash on startup when ran on the Plasma Wayland version. I reported the issue on the project’s Github page a while ago:
opened 08:41PM - 20 May 22 UTC
I recently noticed that KVirc will no longer start up when using a Wayland sessi… on. It works perfectly fine in X11 but if I choose Wayland it refuses to run. No detail is provided if starting up from a console, just the typical "segmentation fault" which is a fancier keyword for "it crashed". As I don't run from Git and using gdb is complex I hope others can easily reproduce this.
My OS is Manjaro and my DE is KDE, this issue happens with the Wayland session for Plasma. KVIrc is installed from the distro's system packages. Note that to test Wayland on KDE you need to install the package plasma-wayland-session in Manjaro. I haven't tried reproducing it in a VM but hopefully it works there too which should make testing easy. This is the system info from the about section, X11 session which I'm still using by default until Wayland is more stable.
```
KVIrc 5.0.0 'Aria'
Runtime Info:
System name: Linux 5.17.6-1-MANJARO
System version: #1 SMP PREEMPT Mon May 9 07:52:43 UTC 2022
Architecture: x86_64
Qt version: 5.15.3
Qt theme: breeze
Build Info:
Build date: 2021-12-03 00:27:39 UTC
Sources date: 20160102
Revision number:
CPU name: x86_64
Build command: /usr/bin/cmake
Build flags:
MANDIR=share/man
CMAKE_INSTALL_PREFIX=/usr
LIB_SUFFIX=
Threads=POSIX
Compiler name: /usr/bin/c++
Compiler flags: -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
Qt version: 5.15.2
Features: IRC, IPv6, Crypt, SSL, IfAddr, IPC, OSS, Transparency, DCCVoice, Perl, Python, Enchant, Qt5, KVS
OpenSSL version: OpenSSL 1.1.1o 3 May 2022
OpenSSL compiler flags: compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -flto=auto -Wa,--noexecstack -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -flto=auto -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -flto=auto -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG
OpenSSL built on: Tue May 3 17:34:24 2022 UTC
```
Today I set up a Manjaro VM to check on a clean install and tested further: When compiled from the Git version KVIrc no longer seems to crash on Wayland either. I assume the issue has been fixed after the version currently included in our package repository.
Who manages the KVIrc package in Manjaro? Could you consider patching it up to fix this crash please? I don’t wish to change IRC clients, and at the moment this is the only clear reason why I’m still using X11 session. Testing should be easy, issue can be reproduced both on normal install and VM with fresh config, if it starts up successfully in both Plasma X11 and Wayland it works. Thank you.
We use the package made upstream by Arch: kvirc
Why isn’t all software always the very latest version?
There are a couple of elements to this question.
Software which has just been released by the upstream project needs time to be packaged and built, so there will always be some time before it becomes available in a packaged format. If a package has patches, then more time will be needed to check whether the patches are still needed and, if so, re-written to apply against the new version. Compiling software from its source code can take a…
1 Like
Use kvirc-git
in the AUR (Arch User Repository ) for now.
1 Like