brent I don't think this necessarily has anything to do with Budgie applets. I think that the Software Center is just complaining about the xml files which contain information about a few Budgie applets. Those warnings also appear in my terminal when I run solus-sc.

Here's my terminal output, with the Software Center working just fine:

marcus@pc ~ $ solus-sc
8 CPUs detected, restricting to 2 threads
(solus-sc:6428): As-WARNING **: 18:01:45.153: com.github.cybre.budgie-haste-applet was of type addon but had no extends
(solus-sc:6428): As-WARNING **: 18:01:45.153: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
(solus-sc:6428): As-WARNING **: 18:01:45.153: com.github.danielpinto8zz6.budgie-calendar-applet.appdata.xml was of type addon but had no extends
(solus-sc:6428): As-WARNING **: 18:01:45.160: com.github.cybre.budgie-haste-applet was of type addon but had no extends
(solus-sc:6428): As-WARNING **: 18:01:45.160: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
(solus-sc:6428): As-WARNING **: 18:01:45.160: com.github.danielpinto8zz6.budgie-calendar-applet.appdata.xml was of type addon but had no extends

Immediately of note is that I don't have that last warning about the missing icon. I'd suggest trying a different icon pack (I'm using Papirus-Dark from papirus-icon-theme in the repos) and seeing if you get results. If there's no change, then you can eliminate that from your troubleshooting.

    infinitymdm I don't think this necessarily has anything to do with Budgie applets. I think that the Software Center is just complaining about the xml files which contain information about a few Budgie applets. Those warnings also appear in my terminal when I run solus-sc.

    Me, too:

    tomscharbach@ts-plasma-portable ~ $ solus-sc
    8 CPUs detected, restricting to 2 threads
    (solus-sc:8334): As-WARNING **: 18:08:43.467: com.github.cybre.budgie-haste-applet was of type addon but had no extends
    (solus-sc:8334): As-WARNING **: 18:08:43.467: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
    (solus-sc:8334): As-WARNING **: 18:08:43.467: com.github.danielpinto8zz6.budgie-calendar-applet.appdata.xml was of type addon but had no extends
    (solus-sc:8334): As-WARNING **: 18:08:43.477: com.github.cybre.budgie-haste-applet was of type addon but had no extends
    (solus-sc:8334): As-WARNING **: 18:08:43.477: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
    (solus-sc:8334): As-WARNING **: 18:08:43.477: com.github.danielpinto8zz6.budgie-calendar-applet.appdata.xml was of type addon but had no extends
    gtk-icon-theme-error-quark: Icon 'application-x-addon' not present in theme breeze-dark (0)
    tomscharbach@ts-plasma-portable ~ $

    The Software Center works fine for me, too, or more accurately it update correctly on September 27.

    @[deleted] Ignore my question about Budgie applets. It was a question born of complete ignorance.

      infinitymdm it wasn't me who theorized about applets. my guesses were theming or corrupt desktop file
      edit: I was more of the gtk inside of plasma potential

        brent Oh, whoops. I must've misclicked the reply button and failed to catch it on a review pass. My bad!

          still a heck of a mystery.
          why do you both (infinitymdm tomscharbach ) find the gtk icon error insignificant? why is plasma referencing budgie xml metadata (for lack of a better term) at all when launching the gui from the menu?
          edit: from the terminal I mean
          the shortcut in menu can't be accessed

            That task is ancient and has absolutely nothing to do with this users current issue. The lines about applets are warnings not errors and will occur regardless of your DE. They can be ignored.

            brent why do you [...] find the gtk icon error insignificant?

            Actually, I don't find it insignificant. I thought that perhaps it could be the cause of the issue. But now that tomscharbach has shown his works with the same error (launched from terminal or Kickoff) I think we can eliminate that as a root cause.

            Now I suspect what brent theorized earlier: a misconfigured desktop file.

            Here are the contents of my desktop file at /usr/share/applications/solus-sc.desktop:

            [Desktop Entry]
            Name=Software Center
            GenericName=Software Center
            Comment=Install, Remove and Update System Software
            Exec=/usr/bin/solus-sc
            Terminal=false
            Type=Application
            StartupNotify=true
            Icon=system-software-install
            Categories=X-GNOME-Settings-Panel;PackageManager;System;Settings
            Keywords=Updates;Upgrade;Sources;Repositories;Preferences;Install;Uninstall;Program;Software;App;Store;
            Actions=view-updates;
            
            [Desktop Action view-updates]
            Name=Updates
            Exec=solus-sc --update-view

            @[deleted] if yours doesn't match that, perhaps that is our culprit.

              infinitymdm you are right, you and tom could launch SC from the menu---so these warnings are neglibile/moot. I dont have plasma for context.
              solus-sc.desktop may have a clue in it. There's a few ways one can wreck that file.

              Any modification to /usr/share/applications/solus-sc.desktop would have been caught by sudo eopkg check and reported solus-sc as Broken. Since the user has already run that command and everything is reporting as "OK" now, it clearly isn't the cause.

                Harvey Good to know. Just working within the limits of my own knowledge here. I appreciate the help expanding those limits a tad ๐Ÿ‘๏ธ

                Harvey
                interesting; did not know something like that would be check - detected.. I think noto-sans ttf was the only thing that BTE's check found. I keep thinking 'cant launch app from menu' is easy somehow๐Ÿ˜‰.

                edit: nevermind it was fleeting

                  brent ... noto-sans ttf ...

                  That shows up every time, update, no update, whatever.

                  Checking integrity of noto-sans-ttf Broken
                  Missing file: /usr/share/fonts/conf.d/66-noto-color-emoji.conf

                  I ignore it.

                  • [deleted]

                  • Edited

                  I have installed papirus-icon-set, switched to it (possibly not necessary) and tried running the Software Center from Kickoff and from the terminal.

                  It still does not run when launched from Kickoff.

                  It runs when launched from the terminal with the same output MINUS the last line so, basically, there is no complaint about the icon set anymore, not that it matters much. : )

                    [deleted] yeah, I figured that wasn't the root cause after Tom mentioned he could run just fine despite the error about the icon. Unfortunately, I'm out of troubleshooting ideas.

                      infinitymdm
                      me too.
                      sudo eopkg rdb? with a dc andrmo thrown to mop up loose ends?
                      I think removal and reinstallation of software center too insane of an idea even for me

                        brent I think removal and reinstallation of software center too insane of an idea even for me

                        Actually, I think this is a great idea. Should be as simple as sudo eopkg it --reinstall solus-sc

                          • [deleted]

                          brent You Sir! are a genius! sudo eopkg rdb coupled with dc and rmo helped! \o/