Description of problem: Started up kdevelop Version-Release number of selected component: kf5-kded-5.48.0-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/kded5 crash_function: qt_message_fatal executable: /usr/bin/kded5 journald_cursor: s=138a605689274f4b9d92abb5845ae9c5;i=77ea;b=5376f8bbf21949a9a417d81ce6ed3c1c;m=2813d9643;t=573e01ee9e138;x=f33ac0787a99c46a kernel: 4.17.14-202.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1716 #3 QMessageLogger::fatal at global/qlogging.cpp:822 #4 init_platform at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:61 #5 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1302 #6 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1319 #7 QCoreApplicationPrivate::init() at kernel/qcoreapplication.cpp:849 #8 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1346 #9 QApplicationPrivate::init at kernel/qapplication.cpp:576 #10 kdemain at /usr/src/debug/kf5-kded-5.48.0-1.fc28.x86_64/src/kded.cpp:746 #12 _start
Created attachment 1477296 [details] File: backtrace
Created attachment 1477297 [details] File: cgroup
Created attachment 1477298 [details] File: core_backtrace
Created attachment 1477299 [details] File: cpuinfo
Created attachment 1477300 [details] File: dso_list
Created attachment 1477301 [details] File: environ
Created attachment 1477302 [details] File: limits
Created attachment 1477303 [details] File: maps
Created attachment 1477304 [details] File: mountinfo
Created attachment 1477305 [details] File: open_fds
Created attachment 1477306 [details] File: proc_pid_status
Created attachment 1477307 [details] File: var_log_messages
User Logs: --Aug 20 12:08:31 rose kded5[4929]: This application failed to start because it could not find or load the Qt platform plugin "wayland"
(In reply to Rex Dieter from comment #13) > User Logs: > --Aug 20 12:08:31 rose kded5[4929]: This application failed to start because > it could not find or load the Qt platform plugin "wayland" Interesting - qt5-qtwayland is indeed not installed on this system. Installing it does stop this happening. This is on a freshly installed fedora 28 system with both KDE and GNOME groups running wayland - surely the something should have pulled in the qt5-qtwayland plugin? Is this a packaging bug then?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.