[Qgis-user] Qgis 3.2.0 crashes at DigitizingTools plugin activation.

[Nyall Dawson]

On Thu, 19 Jul 2018 at 12:03, Fernando M. Roxo da Motta <petro at roxo.org> wrote:
>
>
>
>   Hi all,
>
>
>   I have just updated my machine to the Xubuntu 18.04 LTS:
>
> $ lsb_release -a
> LSB Version:
> core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
> Distributor ID: Ubuntu Description:    Ubuntu 18.04 LTS
> Release:        18.04
> Codename:       bionic
>
>   The machine is a Asus Republic of Gamers:
> $ uname -a
> Linux cabore 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
>   Upon installing Qgis it was offered the Qgis 3.2.0:
>
> $ dpkg -l qgis
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Nome           Versão       Arquitectura Descrição
> +++-==============-============-============-=================================
> ii  qgis           1:3.2.0+28bi amd64        Geographic Information
> System (GI
>
>   Until the upgrade I was using the last inception Qgis 2.18 in the
> Qgis stable repository:
>
> $ cat /etc/apt/sources.list.d/qgis-stable.list
> #
> #  http://www.qgis.org/en/site/forusers/alldownloads.html#ubuntu
> #
> deb http://qgis.org/debian bionic main
> # deb-src http://qgis.org/debian trusty main
> # nightly binaries.
> # deb http://qgis.org/debian-nightly xenial main
>
>   I am still finding my way on this new version.
>
>   I have installed the DigitizingTools plugin from the oficial
> repository.   On start os Qgis the issues the mesage:
>
>  WARNING    Plugin DigitizingTools : The plugin will be disabled
> because it crashed QGIS during last startup. Please report an issue and
> re-enable the plugin when the problem has been solved.
>
>   If I try to activate it in the Plugin Manager I got this message at
> the terminal:
>
> QGIS died on signal 11Could not attach to process.  If your uid matches
> the uid of the target process, check the setting
> of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user.
> For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation
> not permitted. No thread selected
> No stack.
> gdb returned 0
> Aborted
>
>   Is there any procedure I should use to help detect what the problem
> is?

It's a bug in that plugin -- you'll need to file it with the plugin's
author and try to get their attention.

Nyall