noise617
That's because the package name is gdk-pixbuf, not pixbug 🙂

Anyway, two important things to note about this:

  1. As this is a cache file, which can be edited by our new gdk-pixbuf usysconf trigger (e.g. when you install the webp loader) it's not unusual for eopkg check to report it as "Broken", which simply means that it's not in the state it was in during the package installation. I do wonder however whether we should handle this a bit better now.
  2. For the future: Standard procedure after you encounter a genuinely broken package shouldn't be to remove it, but instead to re-install it (using sudo eopkg it --reinstall <package-name>). Otherwise you might remove something vital to the system.

    Well my gdk-pixbuf is reported as broken now after todays update. I have trie reinstalling, but it is still broke..So Whats the solution??

      Silversurfer Well my gdk-pixbuf is reported as broken now after todays update. I have trie reinstalling, but it is still broke..So Whats the solution??

      Try sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

      I had the same issue:

      tomscharbach@ts-plasma-portable ~ $ sudo eopkg check
      ...
      Checking integrity of gdk-pixbuf Broken
      Corrupted file: /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
      ...

      As was the case with your installation, sudo eopkg it --reinstall gdk-pixbuf did not resolve the issue.

      However, the General Troubleshooting command sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall resolved the issue:

      tomscharbach@ts-plasma-portable ~ $ sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
      Total size of package(s): 477.00 KB
      Downloading 1 / 1
      Package gdk-pixbuf found in repository Solus
      gdk-pixbuf-2.42.9-47-1-x86_64.eopkg [cached]
      Installing 1 / 1
      gdk-pixbuf-2.42.9-47-1-x86_64.eopkg [cached]
      Installing gdk-pixbuf, version 2.42.9, release 47
      Extracting the files of gdk-pixbuf
      Installed gdk-pixbuf
      [✓] Syncing filesystems success
      [✓] Updating dynamic library cache success
      [✓] Updating manpages database success

      The command sudo eopkg check no longer reports gdk-pixbuf as "Broken":

      tomscharbach@ts-plasma-portable ~ $ sudo eopkg check
      ...
      Checking integrity of gdk-pixbuf OK
      ...

      I have no idea why the one worked and the other didn't. No guarantee that what worked for me will work for you, but it is worth a try.

        Ah the broken gdk-pixbuf package is due to the pre-compiled loaders.cache file getting overridden by the new usysconf trigger for gdk-pixbuf. I'll remove the pre-compiled loaders.cache file and let usysconf handle it exclusively. It is nothing to worry about in the mean while.

          I've tried sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall and it succesfully re-installed three packages:

          dropbox  gdk-pixbuf  noto-sans-ttf

          However, sudo eopkg check still indicates:

          Checking integrity of gdk-pixbuf                                     Broken
Corrupted file: /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache

            noise617 I don't either. I'm seeing dual messages about this broken pix package in this thread: has nothing to do with your problem/has everything to do with your problem. But I am tired and not seeing all the nuances in this conversation.
            edit/droopy eyed typo

              noise617 You can safely ignore this issue for now. Will disappear with the next update. As Joey and I explained above that's just a consequence of the automatic way in which we handle the gdk-pixbuf loader cache now. Starting with the next update, the loaders.cache will be completely dynamically generated on the user system and therefore no longer tracked (and complained about) by eopkg check.

                  4 days later