Errores, Características y Problemas

QGIS es un proyecto impulsado en gran medida por sus voluntarios, y es el trabajo de un equipo de desarrolladores, documentos, traductores y colaboradores. A pesar de los esfuerzos del equipo para liberar QGIS sin errores, puede permanecer algunos. Si usted encuentra un error o desea que se añaden nuevas características, ¡por favor repórtelo!

Each part of the QGIS Project has a dedicated place where issues (feature requests or bugs) can be reported, managed and discussed. You’ll find issues related to:

Para preguntas, por favor contacte la Listas de correos.

Reporting issues on QGIS applications

QGIS applications (QGIS Desktop, QGIS Browser and QGIS Server) issues are available in Redmine. In order to submit or comment a report, you need an OSGeo account and login. To get started, first Create an OSGeo account. It may require some time to have your account approved.


On the OSGeo userid page you can find more information about the OSGeo id we use. For example to change your password or email address, or to reset your lost password.

Antes de notificar un problema

Before filing an issue, review the currently open issues to make sure that you aren’t creating a duplicate. If you have additional information on an issue, you can add it to the existing ticket. Third party plugins might also cause problems. If you have installed any, you should also verify that the problem is still reproducible without them. Please don’t report multiple unrelated bugs in a single bug report.

Steps to create a report

Once your account is validated and you are logged in, a New Issue tab is available in the menu bar. Select it .

Información importante necesitada cuando se abre un boleto:

  • Tracker - choose the ticket type from the drop-down list: Bug, Feature (new feature request)
  • Tema - una descripción corta del problema
  • Description - Provide a full description of the problem including steps to repeat it; if you think the bug could be related to a certain platform version or dependencies package version (GDAL, OGR, GEOS etc) include that as well. If your QGIS crashes it might be useful to include a backtrace (see below). A very important thing when reporting a bug is to boil down a minimum example that is needed to reproduce the bug. The chances of a bug being addressed in a timely manner is directly related to the speed with which the developer can reproduce the bug. If you make that hard for the developer, chances are the bug will be given up on or ignored for quite a while.
  • Prioridad - provea un estimado de la severidad del problema:
    • Baja: un problema que no afecta la utilidad de QGIS,
    • Normal: el valor predeterminado, aplicable a la mayoría de los fallos y casi todos los pedidos de características,
    • High: a bug which has a major effect on the usability of a package or a bug that makes QGIS totally unusable. In the form you will find also yes/no fields to allow you detail of the issue is causing a crash or data corruption or if it is a regression (a regression is an issue about a functionality that used to work as expected and then stopped to work in more recent QGIS release)
  • Category - Choose the aspect of the application that is most closely associated with the problem
  • Affected QGIS Version - Version of QGIS this issue affects
  • Operating System - The Operating System(s) you are using (and also their version), i.e: Windows 7, macOS 10.12.4, Ubuntu 16.04

Antes de enviar el error, por favor compruebe el formato de sus reporte haga clic en “Vista previa”. Por favor evite editar reportes existentes, si no hay errores de ortografía. Mejor añada más comentarios en cualquier otro caso.

Crear un backtrace

Si tiene un accidente que podría ser útil incluir una backtrace como el fallo podría no ser reproducible en otra máquina.

On Linux QGIS automatically tries to use gdb to connect to the crashing process to produce a backtrace. But some distributions disable the possiblity to connect debuggers to a running processes. In that case gdb only produces a rather useless message like:

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 (core dumped)

In that case you should reenable that option by setting kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf (or /etc/sysctl.conf or some other file in /etc/sysctl.d/) and run sysctl -p as root. When you reproduce the crash after that, a backtrace will be printed instead.

If you cannot reproduce the crash, there should still be a core dump in the current directory, that can be analysed after the process has already terminated. It’s called core (on some systems a dot and the process id is append to the filename).

On some distributions the creation of core dumps is also disabled. In the event that you just get Aborted instead of Aborted (core dumped) when the crash occurs. Then you need to run ulimit -c unlimited before starting QGIS. You can also include that in your .profile, so that it’s always enabled when you login.

To produce a backtrace from the core file, start gdb /path/to/the/qgis/binary core. The binary is usually /usr/bin/qgis or /usr/bin/qgis.bin on Debian with the GRASS plugin installed. In gdb you run bt which will produce the backtrace.

Registro de resultados en Windows

The nightly build in OSGeo4W (package qgis-dev) is built with debugging output, that you can view with DebugView. If the problem is not easy to reproduce the output might shed some light about where QGIS crashes.

Errores de complementos

Most of the plugins in QGIS are published in the official QGIS Plugins repository. Bugs or feature requests relative to them must be opened in their respective bug tracking system. For any plugin available in QGIS repository, you’ll find in its metadata a link to its bug tracker. Otherwise, consult the plugin documentation to find the address of the relevant bug tracking system or a developer to contact.

If no information is available, please report it to the Developer mailing-list.

For other plugins, we have no means to ensure such information are provided.

Reporting issues on QGIS web site or documentation

QGIS project provides an active web site and a rich documentation. Despite our efforts, if you find an out of date information, a wrong or unclear statement or miss a valuable information, please feel free to report it.

The main sources of these documents are hosted and managed in GitHub repositories so in order to report bugs or submit patches, you need a GitHub account and login.

Para empezar, primero Crear una cuenta GitHub.

A continuación, elija el repositorio apropiado:

Compruebe si el problema que quisiera reportar aun no esta registrado.

Haga clic en Nuevo problema, escriba un título y una descripción clara para su problema.

Cuando termine, haga clic en Enviar nuevo problema.


A Fix me link is provided at the bottom of any page of the web site to help you directly improve this page and submit pull request.

Esta opción también esta disponible en el pie de página de la Documentación.

Enviar un parche

In addition to issue report, you can help to fix issues. Fixing issues is done in GitHub through pull requests. You need to fork the repository you want to contribute to and submit pull requests at:

You can find a few guidelines that will help you to easily get your patches and pull requests into QGIS projects at Enviando Parches y Pedidos Pull. And more widely, You may need to read Acceso GIT.