Description of problem: If I start psi-plus in a wayland session (with plasma 5) it immediately segfaults. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. install ibus-wayland, kf5-kwayland, kwayland-integration, kwin-wayland, libwayland-client, libwayland-cursor, libwayland-server, mesa-libwayland-egl, plasma-workspace-wayland, qt5-qtwayland, xorg-x11-server-Xwayland (I don't know exactly what you need to be able to start a plasma5 wayland session) 2. start a plasma5 wayland session 3. start psi-plus Actual results: $ psi-plus [20171023 9:33:46] W:QObject::connect: invalid null parameter (unknown:0, unknown) zsh: segmentation fault (core dumped) psi-plus Expected results: No segfault but psi-plus should open. Additional info: $ valgrind psi-plus ==13240== Memcheck, a memory error detector ==13240== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==13240== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==13240== Command: psi-plus ==13240== [20171023 9:38:04] W:QObject::connect: invalid null parameter (unknown:0, unknown) ==13240== Invalid read of size 4 ==13240== at 0x4E47731: xcb_send_request_with_fds64 (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x4E47C78: xcb_send_request (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x4E4DDFE: xcb_intern_atom (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x68AE53: ??? (in /usr/bin/psi-plus) ==13240== by 0x68AF4B: ??? (in /usr/bin/psi-plus) ==13240== by 0x499E86: main (in /usr/bin/psi-plus) ==13240== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==13240== ==13240== ==13240== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==13240== Access not within mapped region at address 0x0 ==13240== at 0x4E47731: xcb_send_request_with_fds64 (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x4E47C78: xcb_send_request (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x4E4DDFE: xcb_intern_atom (in /usr/lib64/libxcb.so.1.1.0) ==13240== by 0x68AE53: ??? (in /usr/bin/psi-plus) ==13240== by 0x68AF4B: ??? (in /usr/bin/psi-plus) ==13240== by 0x499E86: main (in /usr/bin/psi-plus) ==13240== If you believe this happened as a result of a stack ==13240== overflow in your program's main thread (unlikely but ==13240== possible), you can try to increase the size of the ==13240== main thread stack using the --main-stacksize= flag. ==13240== The main thread stack size used in this run was 8388608. ==13240== ==13240== HEAP SUMMARY: ==13240== in use at exit: 556,493 bytes in 5,985 blocks ==13240== total heap usage: 30,649 allocs, 24,664 frees, 9,373,819 bytes allocated ==13240== ==13240== LEAK SUMMARY: ==13240== definitely lost: 0 bytes in 0 blocks ==13240== indirectly lost: 0 bytes in 0 blocks ==13240== possibly lost: 2,344 bytes in 22 blocks ==13240== still reachable: 554,149 bytes in 5,963 blocks ==13240== of which reachable via heuristic: ==13240== newarray : 1,632 bytes in 19 blocks ==13240== suppressed: 0 bytes in 0 blocks ==13240== Rerun with --leak-check=full to see details of leaked memory ==13240== ==13240== For counts of detected and suppressed errors, rerun with: -v ==13240== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) zsh: segmentation fault (core dumped) valgrind psi-plus
It's to suspect more like a bug somewhere in kf5-kwayland or wayland itself. Please tell about package versions used.
Can you provide a backtrace of the crash too?
Sorry for the delay: Package versions: - kf5-kwayland-5.38.0-1.fc26 - psi-plus-1.0-0.1.20170612git9.fc26 - ibus-1.5.16-11.fc26 - kwayland-integration-5.10.5-1.fc26 - kwin-5.10.5-1.fc26 - wayland-1.13.0-1.fc26 - mesa-17.2.2-2.fc26 - plasma-workspace-5.10.5-3.fc26 - qt5-qtwayland-5.7.1-4.fc26 - xorg-x11-server-1.19.3-4.fc26 I used abrt in order to generate a backtrace. Unfortunately he opened a new issue: https://bugzilla.redhat.com/show_bug.cgi?id=1508163 You can find the backtrace there.
*** Bug 1508163 has been marked as a duplicate of this bug. ***
Adjusting summary
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.