Description of problem: I've mistakenly configured map source with %n instead of %d as the replacement character. I guess the input should be sanitized somehow ... Version-Release number of selected component: foxtrotgps-1.1.1-6.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: foxtrotgps crash_function: __libc_message executable: /usr/bin/foxtrotgps kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 __libc_message at ../sysdeps/posix/libc_fatal.c:175 #3 __libc_fatal at ../sysdeps/posix/libc_fatal.c:186 #4 _IO_vfprintf_internal at vfprintf.c:1634 #5 ___vsprintf_chk at vsprintf_chk.c:85 #6 vsprintf at /usr/include/bits/stdio2.h:46 #7 g_vsprintf at gprintf.c:236 #8 g_sprintf at gprintf.c:116 #9 download_tile at tile_management.c:138 #10 load_tile at map_management.c:199 #11 fill_tiles_pixel at map_management.c:300
Created attachment 892944 [details] File: backtrace
Created attachment 892945 [details] File: cgroup
Created attachment 892946 [details] File: core_backtrace
Created attachment 892947 [details] File: dso_list
Created attachment 892948 [details] File: environ
Created attachment 892949 [details] File: limits
Created attachment 892950 [details] File: maps
Created attachment 892951 [details] File: open_fds
Created attachment 892952 [details] File: proc_pid_status
Created attachment 892953 [details] File: var_log_messages
Another user experienced a similar problem: (this should be duplicate) reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: foxtrotgps crash_function: __libc_message executable: /usr/bin/foxtrotgps kernel: 3.14.2-200.fc20.x86_64 package: foxtrotgps-1.1.1-6.fc20 reason: foxtrotgps killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Submitted upstreams in https://bugs.launchpad.net/foxtrotgps/+bug/1316914 and waiting for fix.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.