TomSchimansky / TomSchimansky/TkinterMapView
Segfault on linux using demo code
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 743
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
I've been running the exemple/map_with_customtkinter.py on linux with python 3.14 :
`
$ python map_with_customtkinter.py
Status code 403 from https://nominatim.openstreetmap.org/search: ERROR - 403 Client Error: Forbidden for url: https://nominatim.openstreetmap.org/search?q=Berlin&format=jsonv2&addressdetails=1&limit=1
Erreur de segmentation (core dumped)python map_with_customtkinter.py
`
dmesg on the 3 runs :
`
[ 46.327618] show_signal_msg: 14 callbacks suppressed
[ 46.327621] Thread-10 (load[7395]: segfault at 1 ip 00007fb6c76c23b8 sp 00007fb69fffc590 error 4 in libgcc_s-15-20251022.so.1[1d3b8,7fb6c76a5000+23000] likely on CPU 0 (core 0, socket 0)
[ 46.327629] Code: 24 a0 00 00 00 e9 58 fe ff ff 3c 04 0f 85 9f 36 fe ff bf 18 00 00 00 e9 f9 fd ff ff 66 0f 1f 44 00 00 49 8b 84 24 98 00 00 00 <80> 38 48 0f 85 2f ff ff ff 48 ba c7 c0 0f 00 00 00 0f 05 48 39 50
[ 360.426680] Thread-18 (load[10791]: segfault at 1 ip 0000000000000001 sp 00007feeeaffb138 error 14 likely on CPU 5 (core 5, socket 0)
[ 360.426690] Code: Unable to access opcode bytes at 0xffffffffffffffd7.
[ 1297.522517] Thread-20 (load[37184]: segfault at 1 ip 0000000000000001 sp 00007f209effb138 error 14 likely on CPU 13 (core 13, socket 0)
[ 1297.522526] Code: Unable to access opcode bytes at 0xffffffffffffffd7.
`
Map wasn't loading :
using scroll from mouse up and down in the mapviewer area cause the segfault in linux (sometimes directly, sometimes after few seconds)
Config :
Fedora Linux 43 (Workstation Edition)
`
$ pip list
Package Version
anyio 4.8.0
argcomplete 3.6.3
attrs 25.4.0
beautifulsoup4 4.14.2
blivet 3.12.1
branca 0.8.2
Brlapi 0.8.7
certifi 2025.11.12
cffi 2.0.0
charset-normalizer 3.4.4
click 8.3.1
cockpit 351
colorama 0.4.6
crypt_r 3.13.1
cupshelpers 1.0
customtkinter 5.2.2
darkdetect 0.8.0
dasbus 1.7
dbus_next 0.2.3
dbus-python 1.4.0
decorator 5.2.1
distro 1.9.0
dnf 4.24.0
evdev 1.9.1
fedora-third-party 0.10
file-magic 0.4.0
folium 0.20.0
future 1.0.0
geocoder 1.38.1
h11 0.16.0
httpcore 1.0.9
httpx 0.28.1
humanize 4.13.0
idna 3.11
iso639 0.1.4
Jinja2 3.1.6
jsonschema 4.23.0
jsonschema-specifications 2024.10.1
langtable 0.0.69
libcomps 0.1.23
libdnf 0.75.0
libdnf5 5.2.17.0
louis 3.33.0
lutris 0.5.19
lxml 6.0.1
MarkupSafe 3.0.3
moddb 0.12.0
nftables 0.1
numpy 2.3.5
olefile 0.47
packaging 25.0
perf 0.1
pexpect 4.9.0
pid 3.0.4
pillow 12.0.0
pip 25.3
ply 3.11
productmd 1.48
protobuf 3.19.6
ptyprocess 0.7.0
pwquality 1.4.5
PyAudio 0.2.13
pycairo 1.28.0
pycparser 2.22
pycups 2.0.4
pyenchant 3.2.2
PyGObject 3.54.5
pyinotify 0.9.6
pykickstart 3.66
pyparted 3.13.0
pyperclip 1.11.0
pypresence 4.3.0
PySocks 1.7.1
python-augeas 1.2.0
python-dateutil 2.9.0.post0
python-linux-procfs 0.7.3
python-meh 0.52
python-pam 2.0.2
pyudev 0.24.3
pyxdg 0.27
PyYAML 6.0.2
pyynl 0.0.1
RapidFuzz 3.12.2
ratelim 0.1.6
referencing 0.36.2
regex 2025.10.23
requests 2.32.5
requests-file 2.0.0
requests-ftp 0.3.1
rpds-py 0.27.0
rpm 6.0.0
selinux 3.9
sepolicy 3.9
setools 4.6.0
setuptools 78.1.1
simpleline 1.9.0
six 1.17.0
sniffio 1.3.1
sos 4.10.1
soupsieve 2.8
systemd-python 235
tkintermapview 1.29
typing_extensions 4.15.0
urllib3 2.5.0
wheel 0.45.1
xkbregistry 0.3
xyzservices 2025.11.0
youtube_dl 2025.4.7
`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with exemple/map_with_customtkinter.py on Fedora Linux 43 and Python 3.14, using mouse-wheel scrolling in the map viewer. Check the reported 403 response and the dmesg segfault details, including the load threads and libgcc_s entry. Done means the demo loads the map and repeated scrolling no longer causes a segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100