SUMMARY: Discover crashes as soon as it is launched. Here is what konsole returns when trying to start it. file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:62: TypeError: erty 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:70: TypeError: erty 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:78: TypeError: erty 'canPaste' of null invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 in adding empty sources model QStandardItemModel(0x558a4b028d80) Segmentation fault (core dumped) SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 4.12.14-lp151.28.7-default OS Type: 64-bit
Please attach the backtrace of the crash. See https://community.kde.org/Get_Involved/Bug_Reporting#Crash_reports_must_include_backtraces
I've tried adding the plasma-discover-debuginfo and the ksysguard-debuginfo and I still don't know how to make a backtrace. No 'crash window' appears after Discover crashes either, so I can't click 'report bug' either. I'm not sure where to go from here.
(In reply to adamska156 from comment #2) > I've tried adding the plasma-discover-debuginfo and the ksysguard-debuginfo > and I still don't know how to make a backtrace. No 'crash window' appears > after Discover crashes either, so I can't click 'report bug' either. I'm not > sure where to go from here. It appears that I don't have a kns-backend for Discover available in any repos either. Not sure if that's the culprit here.
I tried debugging with gdb and I run into this error. GNU gdb (GDB; openSUSE Leap 15.1) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from plasma-discover...Reading symbols from /usr/lib/debug/usr/bin/plasma-discover-5.16.1-lp151.184.1.x86_64.debug...done. done. (gdb) run Starting program: /usr/bin/plasma-discover [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 }
Ah you're on Wayland. Looks like this is the problem: qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. It seems that your Wayland session is misconfigured somehow. How did you install your KDE Software stack? I wasn't aware that Leap 15.1 had up-to-date versions. Did you install from source or using an OBS repo?
That's really interesting. I'm definitely not on Wayland, so I don't understand what the problem could be. I log in to the default "Plasma" session from SDDM. I'm using the KDE repos for opensuse 15.1 listed here https://en.opensuse.org/SDB:KDE_repositories which means I'm basically on what the opensuse team calls 'opensuse argon' just with Leap 15.1. I've never had any other issues before with this method back through opensuse 15.0. Only now after upgrading to Plasma 5.16.1 has it broken Discover. The only thing that should cause problems by using the up-to-date KDE packages is that some 3rd party packages meant for Leap 15.1 may be broken, since they'd be compiled against an older version of Qt. However Discover is maintained through those repos anyway and are perfectly compatible. Any idea how I can find out more info, so I can begin to fix this problem?
I would recommend asking the openSUSE folks. Something seems to be quite unhappy with how your OS is installed.