[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Upgrade debacle........



On Sat, May 3, 2014 at 2:25 AM, Chris Bannister
<cbannister@slingshot.co.nz> wrote:
> On Fri, May 02, 2014 at 07:48:45AM +0200, Ralf Mardorf wrote:
>> On Thu, 2014-05-01 at 22:56 -0400, The Wanderer wrote:
>>> On 05/01/2014 02:37 PM, Selim T. Erdogan wrote:
>>>>
>>>> At the time, I didn't check to see if the file
>>>>   /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
>>>> existed.  I also didn't run the command
>>>>   gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
>>>> However, I checked just now and that file exists, with a non-zero size.
>>>
>>> I've seen this several times myself.
>>>
>>> My experience seems to suggest that during the course of upgrading some
>>> packages, this 'loaders.cache' file temporarily does not exist, and
>>> later in the process this command gets automatically run and the file
>>> re-created. At some point in the middle, however, something which
>>> expects the file to exist gets run, and when it doesn't find the file,
>>> that error gets printed.
>>>
>>> IOW, as long as the file exists after the apt-get or dpkg run has
>>> completed (which it always has in my experience), this appears to be a
>>> false-positive warning.
>>
>> It was an issue for the OP. It's disputable if somebody who can't solve
>> such an issue on her/his own, should use testing, instead of stable.
>
> The issue is not whether one can solve it, but whether one should have
> to. I don't even use GNOME, so shouldn't even see the
> message. It gave the impression that your system would be horribly
> broken if you didn't run the command, and yet the command doesn't even
> exist on your system!

It's the wrong impression. I've seen this message often and I no
longer bother running the query loader line - and unity and
gnome-shell still function properly.


Reply to: