Latest news will appear here soon.
Edit on GitHub

Bugs, mogelijkheden en problemen

QGIS is een grotendeels door vrijwilligers gedreven project, en is het werk van een toegewijd team van ontwikkelaars, schrijvers van documentatie, vertalers en supporters. Ondanks de inspanningen van het team om QGIS uit te geven zonder bugs, zouden er enkele bugs kunnen achterblijven. Als u een bug vindt of wilt dat nieuwe mogelijkheden worden toegevoegd, rapporteer ze dan!

Waar te melden?

Elk deel van het project QGIS heeft een toegewezen plaats waar problemen (verzoeken voor mogelijkheden of bugs) kunnen worden gerapporteerd, beheerd en besproken. Afhankelijk van het gebied waar u het probleem tegenkwam geeft de tabel hieronder de juiste opslagplaats weer om het te melden:

Plaats waar u het probleem vond of een mogelijkheid voor wilt vragenPlaats om het probleem te melden
Toepassingen (QGIS Desktop, QGIS Server)https://github.com/qgis/QGIS/issues
QGIS Website (https://qgis.org)https://github.com/qgis/QGIS-Website/issues
QGIS documentatie (https://docs.qgis.org)https://github.com/qgis/QGIS-Documentation/issues
C++ API (https://qgis.org/api)https://github.com/qgis/QGIS/issues
PyQGIS API (https://qgis.org/pyqgis)https://github.com/qgis/QGIS/issues (voor inhoud) en https://github.com/qgis/pyqgis/issues (voor opmaak)
QGIS Plugins Website (https://plugins.qgis.org)https://github.com/qgis/QGIS-Plugins-Website/issues
QGIS Hub Website (https://hub.qgis.org)https://github.com/qgis/QGIS-Hub-Website/issues
QGIS Planet Website (https://planet.qgis.org)https://github.com/qgis/QGIS-Planet-Website/issues
QGIS Changelog Website (https://changelog.qgis.org)https://github.com/kartoza/prj.app/issues
QGIS Feed Website (https://feed.qgis.org)https://github.com/qgis/qgis-feed/issues
Externe plug-insDe opslagplaats die door de auteur is ingesteld in de beschrijving van de plug-in

For help and questions, please contact the Mailing lists.

Problemen rapporteren over toepassingen van QGIS

QGIS applications (QGIS Desktop and QGIS Server) issues are available in Github. In order to submit or comment a report, you need to register and login.

Vóór het rapporteren van een probleem

Before filing an issue, verify that you are running the currently supported versions 3.44.10 or 4.0.2 or the development version 4.1 (see also Release schedule) and 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.

When you’re logged in, a New Issue button is available. Select it and follow the instructions there.

Before sending the report, please check the formatting of your report by clicking on “Preview”. Please avoid editing existing reports, if not for typos. Better add further comments in any other case.

Maken van een backtrace

Als u een crash heeft zou het handig zijn om een backtrace op te nemen omdat het probleem misschien niet te reproduceren is op een andere machine.

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, though the filename may include a dot followed by the process id on some systems.

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.

Log uitvoer op 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.

Problemen rapporteren over QGIS website of documentatie

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 valuable information, please feel free to report it.

De belangrijkste bronnen van deze documenten worden gehost en beheerd in opslagplaatsen van GitHub, dus om bugs te rapporteren of patches in te dienen, heeft u een account voor GitHub nodig om in te kunnen loggen.

To get started, first Create a GitHub account.

Kies dan de van toepassing zijnde opslagplaats :

Check if the issue you’d like to report is not already entered.

Klik op New Issue, typ een titel en een heldere beschrijving voor uw probleem.

When you’re finished, click Submit new issue.

Note

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.

Deze optie is ook beschikbaar in de voettekst van de documentatie.

Problemen met plug-ins melden

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 is provided.

Een patch indienen voor projecten van QGIS

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 Submitting Pull Requests. And more widely, you may need to read the Development Process chapter.