Description of problem: The calculator started in basic mode. I entered 64*1024. The * shows up as an actual multiply sign, which is okay. I selected the x1024 part. I pressed control insert in order to copy it. I pressed shift insert, intending to do that three times, but on the first press it crashed. Version-Release number of selected component: gnome-calculator-3.24.0-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: gnome-calculator crash_function: _gtk_text_btree_get_chars_changed_stamp executable: /usr/bin/gnome-calculator journald_cursor: s=2540e810cff54343929fb6623da48dc5;i=926;b=65e5f417262b408785deec84334a49cd;m=92d7fe0e;t=5690ae8ee3200;x=c92f724cbc06cb14 kernel: 4.11.8-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_text_btree_get_chars_changed_stamp at gtktextbtree.c:544 #1 gtk_text_iter_make_surreal at gtktextiter.c:174 #2 gtk_text_iter_get_offset at gtktextiter.c:600 #3 insert_text_cb at a11y/gtktextviewaccessible.c:1778 #8 gtk_text_buffer_emit_insert at gtktextbuffer.c:936 #9 insert_text_range at gtktextbuffer.c:1088 #10 insert_range_untagged at gtktextbuffer.c:1270 #11 insert_range_not_inside_self at gtktextbuffer.c:1335 #12 gtk_text_buffer_real_insert_range at gtktextbuffer.c:1412 #13 paste_from_buffer at gtktextbuffer.c:3609 Potential duplicate: bug 1220468
Created attachment 1417400 [details] File: backtrace
Created attachment 1417401 [details] File: cgroup
Created attachment 1417402 [details] File: core_backtrace
Created attachment 1417403 [details] File: cpuinfo
Created attachment 1417404 [details] File: dso_list
Created attachment 1417405 [details] File: environ
Created attachment 1417406 [details] File: exploitable
Created attachment 1417407 [details] File: limits
Created attachment 1417408 [details] File: maps
Created attachment 1417409 [details] File: open_fds
Created attachment 1417410 [details] File: proc_pid_status
Created attachment 1417411 [details] File: var_log_messages
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.