View Single Post
Old 02-13-2015, 09:16 AM   #37
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
The only one that jumps out as me as being possibly related is libxml2

libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f97029d6000)

which links directly into Qt and could cause an issue with text nodes in an xml tree.

But this is all a big guess. We do know there have been a lot of bugs fixed in libxml2. Could you try updating the Wheezy one to be the same version as used on Mint and see if that impacts anything?

If is not that one, we could simply try a process of elimination of some sort I guess, but if one binary works on one system and the exact same binary does not work on another system, it must be one of the shared libraries at fault (unless I am missing something here).
I'll give it a shot (if only for my own curiosity) but even if that shared library turns out to be the culprit, do we have real shot at fixing it or supplying a workaround (short of custom compiling Qt5 to use a newer, supplied libxml2)?
DiapDealer is offline   Reply With Quote