Bug#766241: gnome: dist-upgrade on 20-Oct lost gnome pixbufs and several tweak settings reset

Jim Cobley jimc at priorycomputers.com
Mon Nov 3 14:17:38 UTC 2014


Hi Michael

I did the dist-upgrade late on the 20th - about 10 hours after the 
updates for that day had been set - going from the date stamps shown 
whilst the "update" was downloading. So I would assume that this problem 
had been introduced on that day - rather than being fixed!

The only report by dist which has been happening for several days now is 
it complains about an issue with "jpeg progs" (sorry can't remember the 
exact message. Certainly don't remember seeing the message that you mention.

It is tricky deciding what package it should be filed against - I knew 
nothing (still don't know much) about the internals of Gnome.

I booted under another system and searched - I ran into a report on 
another distribution which mentioned 3 possible fixes and I was lucky it 
worked. One of the main reasons for filing the report was to ensure tat 
the fix was there on Debian for others if they had the issue. Problem 
did not recur for me and I generally do daily dist-upgrades.

Jim

On 03/11/14 13:45, Michael Biebl wrote:
> On Tue, 21 Oct 2014 18:48:14 +0100 prioryc <jimc at priorycomputers.com> wrote:
>> Source: gnome
>> Version: 3.14.1
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Dear Maintainer,
>>
>>     * What led up to the situation?
>> Performed dist-upgrade on 20-Oct
>>
>>     * What was the outcome of this action?
>> When system rebooted on 21-Oct unable to login except under basic terminal
>>     * What outcome did you expect instead?
>> To be able to use the machine
>>
>> Ran "sudo gdk-pixbuf-query-loaders --update-cache" to fix
>> Then tweak-tool and set the basic settings required which had been reset.
>>
> The gnome meta package looks like the wrong package this bug was filed
> against.
>
> This sounds like the gdk-pixbuf trigger was not run successfully.
> There have been some bugs in dpkg recently (which are now fixed) which
> made some triggers not be run due to dependency cycles [1].
>
> prioryc, have you seen such a message like this during the upgrade?
>
> Processing triggers for man-db (2.7.0.2-2) ...
> dpkg: cycle found while processing triggers:
>   chain of packages whose triggers are or may be responsible:
>    libgdk-pixbuf2.0-0:i386 -> doc-base
>   packages' pending triggers which are or may be unresolvable:
>    doc-base: /usr/share/doc-base
>    menu: /usr/share/menu
>    libgdk-pixbuf2.0-0:i386:
> /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
>    hal: /usr/share/hal/fdi
> dpkg: error processing package doc-base (--unpack):
>   triggers looping, abandoned
>
>
>
> Those bug reports started to pop up around 15t Oct and it was fixed by a
> dpkg upload on 20 Oct.
>
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434
>



More information about the pkg-gnome-maintainers mailing list