QGIS는 대부분 자원자들이 이끄는 프로젝트로, 헌신적인 개발자, 문서작성자, 번역가 및 지원자들의 팀이 만들고 있습니다. QGIS를 버그 없이 배포하고자 하는 팀의 노력에도 불구하고, 몇몇 버그들이 남아 있을 수도 있습니다. 여러분이 버그를 찾았거나, 또는 새 기능이 추가되길 바란다면 알려주세요!
QGIS 프로젝트의 각 부분은 문제점(기능 요청 또는 버그)를 알리고, 관리하며, 토의할 수 있는 전담 공간을 가지고 있습니다. 여러분이 문제점을 맞닥뜨린 영역에 따라, 다음 표에서 문제점을 알릴 알맞은 저장소를 찾아보세요:
버그를 발견했거나 기능을 요청할 영역 |
문제점을 알릴 곳 |
|---|---|
응용 프로그램(QGIS 데스크톱, QGIS 서버) |
|
QGIS 웹사이트 (https://qgis.org) |
|
QGIS 문서 (https://docs.qgis.org) |
|
C++ API (https://qgis.org/api) |
|
PyQGIS API (https://qgis.org/pyqgis) |
https://github.com/qgis/QGIS/issues (내용) 및 https://github.com/qgis/pyqgis/issues (서식) |
외부 플러그인 |
플러그인 설명에 설정된 작성자 저장소 |
도움 및 질문을 위한 연락처: 메일링 리스트
QGIS 응용 프로그램(QGIS 데스크톱 및 QGIS 서버) 문제점은 깃허브 에서 찾아볼 수 있습니다. 문제점을 제출하거나 문제점에 대해 코멘트를 남기고 싶다면 깃허브에 계정을 등록하고 로그인해야 합니다.
Before filing an issue, verify that you are running the currently supported versions 3.34.5 or 3.36.1 or the development version 3.37 (see also 릴리스 스케줄) 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 are 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.
If you have a crash it might be useful to include a backtrace as the bug might be not reproducible on another 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 (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.
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.
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.
시작하려면 Create a GitHub account.
그러면, 적절한 저장소를 고르세요:
https://github.com/qgis/QGIS-Documentation/issues for QGIS documentation
https://github.com/qgis/QGIS-Website/issues for the web site
보고하려는 이슈가 이미 있는지 보세요.
Click New Issue, type a title and a clear description for your issue.
When you’re finished, click Submit new issue.
참고
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.
This option is also available in the footer of the documentation.
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.
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:
https://github.com/qgis/QGIS for QGIS Desktop or QGIS Server applications
https://github.com/qgis/QGIS-Website for the web site at https://qgis.org
https://github.com/qgis/QGIS-Documentation for the documentation available at https://docs.qgis.org
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.