On 11/30/2015 04:45 PM, Rex Dieter wrote:
> In my experience, that backtrace often means a runtime conflict where
both
> qt4 and qt5 are trying to load into the same process (usually crashes
> quickly)
>
> -- Rex
Yes, you're probably right. This is what I was doing:
I'd first call, in an empty
Stephan Witt wrote:
> Am 19.11.2015 um 04:00 schrieb PhilipPirrip :
>
>> I had a similar issue a month or so ago, what helped was a clean cloning
>> of LyX source. Now even that doesn't work, and it's been like that for 2
>> or 3 weeks. It might be due to newest Qt libraries that came with Fedora
On 11/19/2015 01:27 AM, Stephan Witt wrote:
I've redirected it to developers list.
Sorry, that was sent by mistake. The report I sent here has an updated
gdb output - I installed all debug-infos. QPrinter is being mentioned
several times.
Thought we should still investigate, if it's Qt, you w
Am 19.11.2015 um 04:00 schrieb PhilipPirrip :
> I had a similar issue a month or so ago, what helped was a clean cloning of
> LyX source. Now even that doesn't work, and it's been like that for 2 or 3
> weeks. It might be due to newest Qt libraries that came with Fedora 23, not
> sure. Can you
I had a similar issue a month or so ago, what helped was a clean cloning
of LyX source. Now even that doesn't work, and it's been like that for 2
or 3 weeks. It might be due to newest Qt libraries that came with Fedora
23, not sure. Can you read anything from this backtrace?
(...after insta
