Hi Jonathan,
1. As Matthias suggested, after you send a kill signal, you can go back
to the gdb prompt and type bt to see the backtrace.
2. You QGIS 2.18 is not starting with a specific project, right? (The
one with style by category).
The project file is readable (hum... if XML is readable!).
Hi Jonathan,
The most interesting part in GDB becomes visible as soon as you type
"bt" after a crash (I think the same if you kill it but no guarantee).
Thanks
Matthias
On 03/23/2017 06:11 PM, Jonathan Webb wrote:
> Hi Jorge,
>
> I uninstalled all my plugins & that project won't even open now.
Hi Jorge,
I uninstalled all my plugins & that project won't even open now.
GDB report is:
$ gdb -ex=r --args /usr/bin/qgis.bin
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
In response to Richard Duivenvoorde's reply
Thanks - I have QGIS on a different W7 machine, no other Linux ones. I
I packaged it with QConsolidate & it worked OK on the W7 machine, with
much panning and rapid mousewheel zooming
I'm trying rebuilding the project from the start & so far it
On 22-03-17 19:05, Jonathan Webb wrote:
> Hello,
> Linux Mint 17.2
> Eventually managed to reinstall QGIS, upgrading from 2.16 to 2.18.
> Was working OKfor about a day (apart from missing geoprocessing/geometry
> & analysis tools now mostly resolved), then started crashing out instantly.
>
> I
Hello,
Linux Mint 17.2
Eventually managed to reinstall QGIS, upgrading from 2.16 to 2.18.
Was working OKfor about a day (apart from missing geoprocessing/geometry
& analysis tools now mostly resolved), then started crashing out instantly.
I think I've tracked it down to applying a categorised
