Definitely worth reporting the bug!
The backtrace has lower informational value 
I’d say raise a Bugzilla ticket with whatever you have.
Normally, I use the “Problem Reporting” utility to report such issues. Unfortunately, that utility does not think this report is valuable. I guess I could try manually creating a ticket, but I don’t think it will get anywhere.
OK, I see SMPlayer is the Flatpak, and it can be awkward to get full backtraces there.
I’ll see if I can replicate this and shed any light. (Not today though.)
But when things got wrong discover+packagekit does not share actionable error information.
We see this situation here on a regular basis.
And right on cue… Discover Not Letting Me Install Software From The Home Screen
I can reliably reproduce the same crash, if I allow the “fallback-x11” permission for SMPlayer.
In Flatseal it looks like this:
Can you check (in Flatseal if you have it, or else in the Application Permissions in KDE Plasma System Settings) whether “fallback-x11” is enabled? If so, try disabling it.
There was a change in version 1.18 of Flatpak that changed the way this permission is represented in override files, which could have resulted in it becoming enabled without the user explicitly enabling it.
This happened to me with the Zoom Flatpak - I got pretty much the identical crash to your SMPlayer crash.
Yup, you were right. The app now launches fine.
Given what I have been told about Discover, I am willing to accept that it will lie to me about basic math too.
On the other hand, does anyone know why I have my home directory listed twice in the “File Search” menu? That just doesn’t make sense to me.
Can you remove the duplicates using the “X” icon?
Both “X” buttons for the home directories are greyed out — Only for them.
On the other hand, the “X” buttons for “Documents”, “Music”, “Pictures” and “Videos” can be clicked on.
What is in your ~/.config/baloofilerc file?
[Basic Settings]
Indexing-Enabled=false[General]
dbVersion=2
exclude filters=~,.part,.o,.la,.lo,.loT,.moc,moc_.cpp,qrc_.cpp,ui_.h,cmake_install.cmake,CMakeCache.txt,CTestTestfile.cmake,libtool,config.status,confdefs.h,autom4te,conftest,confstat,Makefile.am,.gcode,.ninja_deps,.ninja_log,build.ninja,.csproj,.m4,.rej,.gmo,.pc,.omf,.aux,.tmp,.po,.vm,.nvram,.rcore,.swp,.swap,lzo,litmain.sh,.orig,.histfile.,.xsession-errors*,.map,.so,.a,.db,.qrc,.ini,.init,.img,.vdi,.vbox*,vbox.log,.qcow2,.vmdk,.vhd,.vhdx,.sql,.sql.gz,.ytdl,.tfstate*,.class,.pyc,.pyo,.elc,.qmlc,.jsc,.fastq,.fq,.gb,.fasta,.fna,.gbff,*.faa,po,CVS,.svn,.git,_darcs,.bzr,.hg,CMakeFiles,CMakeTmp,CMakeTmpQmake,.moc,.obj,.pch,.uic,.npm,.yarn,.yarn-cache,pycache,node_modules,node_packages,nbproject,.terraform,.venv,venv,core-dumps,lost+found
exclude filters version=9
exclude folders[$e]=$HOME/,$HOME/
folders[$e]=$HOME/Documents/,$HOME/Music/,$HOME/Pictures/,$HOME/Videos/
only basic indexing=true
I would try editing this line…
exclude folders[$e]=$HOME/,$HOME/
to…
exclude folders[$e]=$HOME/
(the latter is exactly what I have in my own file).
Take a backup first for safety, but hopefully this might fix it.
Thank you
I feel so dumb now. I do recall resetting the config only to experience the same thing. I have no idea why I didn’t consider this earlier.
Cool, easy fix when you know how! But it does seem like a bug that you can get the config into this state through GUI actions.
Yeah. At least it is one less issue to deal with. I hope they will consider to remove Discover, or actually fix it.
We are not going to drop Plasma Discover. This is also absolutely the wrong place to communicate issues. If you are experiencing bugs with Discover, please file them in the appropriate bug tracker.
Same goes for other issues in the KDE Plasma Desktop stack that you encounter.
Actually I think it’s a perfectly fine topic, and agree wholeheartedly.
And your response is exactly the wrong type of response.
You see, users waste their time on using something with a bunch of quirks and bugs, and then follow all the goderator’s royal commands in submitting the “bug reports” in the “bug trackers” only to receive little, or no, communication back.
And then wait for days, months, years, as yet another “NEW RELEASE!” with 100 new shiny features that hardly anyone cares about or asked for… COMPARED to basic everyday shit that needs fixing gets ignored. All over, everywhere.
Maybe if the goderators and devs actually didn’t try to dismiss threads EXACTLY LIKE THIS ONE, which are of immense value… they’d be more successful with their software, distros, whatever.
Yeah talking to you Fedora, the distro that “Kernel Panics” after EVERY SINGLE KERNEL UPGRADE EVER, ON EVERY DEVICE I HAVE EVER INSTALLED IT ON… unless I run sudo dracut --regenerate-all before rebooting… couldn’t just have it do that itself, could ya Fedora.
Asking conceptual questions like this are very valuable and appropriate.
Or don’t you like the servants questioning the royalty?
I think you are missing the point of @ngompa’s response.
If you want to discuss the issues and have other forum members help you find solutions, this is absolutely the right place to discuss them.
If something is broken and you want it fixed, then you should report it in a bug tracker. Why? Because the people that actually fix such problems may not see them posted here on the forum. The bug tracker is how they track and resolve issues.
I don’t think anyone was saying that things shouldn’t be discussed on the forum.
Lets all remember to keep on topic and not devolve into arguing with one another.