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

Re: Gnome hosed--theme crashing!

Christian Jaeger wrote:
Mumia W.. wrote:
On 08/25/2008 09:12 PM, ZephyrQ wrote:
PauL Lane wrote:
On Mon, Aug 25, 2008 at 08:38:00PM -0500, PauL Lane wrote:
Hello, have you recently upgraded libxml2? I had the same problem. Try; $ dpkg -l libxml2
If it comes back;
ii libxml2 2.6.27.dfsg-3 GNOME XML library

Try downgrading to 2.6.27.dfsg-3.
Also have a look at;

My bad, should be downgrade to 2.6.27.dfsg-2.

I downgraded, but I'm still having the same problem with the themes app in gnome (I can't change theme). I checked out the bug report, but the fix requires me to start using unstable, and I'm not comfortable enough (and don't have the time in the short term to research) with pinning to try and 'mix' my etch sources.

Anything I missed?

Perhaps this is the problem:

Yes that's probably everything the same problem, bug 496125.

ZephyrQ: Are you *really* sure that you're running the previous libxml2 now? What is dpkg -l libxml2 showing now?

Also: try to create a new user from the console ("adduser foo") and log into that one, since the default theme of Gnome does not run into the problem (at least not on Lenny).

Also, note that even if you don't manage to downgrade libxml2, you could rebuild librsvg2 instead (which is, depending on viewpoint, the real culprit here). "apt-get source librsvg; cd librsvg-*; dpkg-buildpackage -uc -us -b -r'fakeroot -u'" then install the resulting librsvg*.deb's with "dpkg -i" (well, at least those which you currently have installed, you could check with dpkg -l "librsvg*").

Also note that accordant to bug 496125, Mike Hommey, the libxml2 maintainer, has created a new libxml2 package which includes the security fix in a way which does not change the size of structs so that librsvg and other libraries which didn't allocate memory through the libxml2 api don't cause crashes anymore. I don't know if and when that version will be distributed to etch users, though. You could ask on the debian-security mailing list.


Reply to: