Version-Release number of selected component: libreport-gtk-2.9.7-2.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: report-gtk -- /var/spool/abrt/ccpp-2019-01-13-18:59:56.182153-7912 crash_function: pango_shape_full executable: /usr/bin/report-gtk journald_cursor: s=d36bd5fb4f9d4346be2ca5fdc217572e;i=6664;b=294dde68cc1145b7a2292949d91fe50d;m=1c4f631f2;t=57f590ff17947;x=c81df2eaee8cf552 kernel: 4.19.13-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pango_shape_full at ../pango/shape.c:191 #1 shape_run at ../pango/pango-layout.c:3242 #2 process_item at ../pango/pango-layout.c:3355 #3 process_line at ../pango/pango-layout.c:3654 #4 pango_layout_check_lines at ../pango/pango-layout.c:3982 #5 pango_layout_get_extents_internal at ../pango/pango-layout.c:2536 #6 pango_layout_get_extents at ../pango/pango-layout.c:2735 #7 gtk_text_layout_get_line_display at gtktextlayout.c:2576 #8 gtk_text_layout_real_wrap at gtktextlayout.c:1182 #9 gtk_text_btree_node_validate at gtktextbtree.c:5129
Created attachment 1520288 [details] File: backtrace
Created attachment 1520289 [details] File: cgroup
Created attachment 1520290 [details] File: core_backtrace
Created attachment 1520291 [details] File: cpuinfo
Created attachment 1520292 [details] File: dso_list
Created attachment 1520293 [details] File: environ
Created attachment 1520294 [details] File: limits
Created attachment 1520295 [details] File: maps
Created attachment 1520296 [details] File: mountinfo
Created attachment 1520297 [details] File: open_fds
Created attachment 1520298 [details] File: proc_pid_status
Created attachment 1520299 [details] File: exploitable
Are you able to reproduce this? I am thinking if this could not be issue with pango. If you are able to reproduce, can you downgrade pango and see if the issue persists?
Could you provide some screenshot or which string caused the crash? If possible, could you reproduce it with pango-view?
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days