Morning all, thought I’d brave the update to Gnome 50 today. Since doing that am getting constant crashes from something called localsearch-extractor-3. The message in the notifications says html/usr/libexec/localsearch-extractor-3
Not sure what this is exactly, I have tried disabling all extension but this continue crashing.
Does this mean anything to anyone as I’m not sure what it is or what it relates to. After posting this I will try closing all open apps & see if it continues crashing.
Thanks for any assistance, maybe this will help iron out some rough edges with the Gnome 50 implementation perhaps?
Mine crashed after the upgrade but seems to have stopped after the following:
Search (Settings), disable everything
reboot
Search (Settings), re-enable (what you want).
This also showed the Search Results… no sure why Calculator, Characters or Clocks were in there
I see errors like the following in the journal, but no crashes:
apr 14 12:56:50 LT-B gnome-shell[3859]: Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Terminal without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Maybe some app configured for search (try zypper se -i search-provider ) but not yet upgraded to 50, possibly because not in the “Circle Apps”?
I’ve run that command, not sure what some of these are but I know I installed Nautilus along the way once when the Gnome Files was playing up. Not sure I know how to disable these but then I don’t seem to be getting the same crash now apart from one for a the Gnome Keyring this time.
These apps are not upgraded at 50, I don’t know if they are causing problems but consider (temporarily) disabling their search switch unless they are important to you.
Then you are using the KDE crash manager (drkonqi which crashes itself) on Gnome?
Thanks for the thoughts on that. I wasn’t sure how to disable these, but I did another dup yesterday which offered some codec looking updates I think. Mysteriously despite not doing anything these problems now seem to have gone away for now as far as I can tell & the crash reporter doesn’t report anything since yesterday. So hopefully the system has somehow fixed itself or maybe there was something in the updates yesterday that fixed. Is there a command I can use to see what was installed & show it here if it helps the maintainers / Admins or others if they should have the same issue?
If not thanks to all for the help & comments along the way.
Hi thanks for that, as I thought the later update was all Codecs from Packman, The one earlier in the day was a long list Packagekitd (+556/-11) which I guess means something to the maintenance crew. That did seem to include those search provider packages too, so not sure why they kept crashing & now seem to work. Unless there is some interplay between the things coming from packman & those search things? Although that seems unlikely I guess.