Description of problem: I have been working on VirtualBox virtual machine on a win 8 (what a shame). I've been trying to save the text file stored in VirtualBox shared folder with different encoding (using "save as"). The target encoding was utf-8, the source encoding probably cp1250. Gedit has warned me, that the file is in use (gedit was the only one application which was using this file) and then it has crashed. Version-Release number of selected component: gedit-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gedit crash_function: gtk_box_size_allocate executable: /usr/bin/gedit kernel: 3.9.9-301.fc19.x86_64 runlevel: N 5 uid: 1000 xsession_errors: abrt-applet: repeated problem in gedit-3.8.3-1.fc19, not showing the notification Truncated backtrace: Thread no. 1 (10 frames) #2 gtk_box_size_allocate at gtkbox.c:486 #7 gtk_widget_size_allocate at gtkwidget.c:5341 #8 gtk_notebook_size_allocate at gtknotebook.c:2579 #13 gtk_widget_size_allocate at gtkwidget.c:5341 #14 gtk_box_size_allocate at gtkbox.c:661 #19 gtk_widget_size_allocate at gtkwidget.c:5341 #20 gtk_paned_child_allocate at gtkpaned.c:1034 #21 gtk_paned_size_allocate at gtkpaned.c:1249 #26 gtk_widget_size_allocate at gtkwidget.c:5341 #27 gtk_paned_child_allocate at gtkpaned.c:1034
Created attachment 771728 [details] File: backtrace
Created attachment 771729 [details] File: cgroup
Created attachment 771730 [details] File: core_backtrace
Created attachment 771731 [details] File: dso_list
Created attachment 771732 [details] File: environ
Created attachment 771733 [details] File: limits
Created attachment 771734 [details] File: maps
Created attachment 771735 [details] File: open_fds
Created attachment 771736 [details] File: proc_pid_status
Created attachment 771737 [details] File: var_log_messages
Reloading file reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: gedit button.log crash_function: gtk_box_size_allocate executable: /usr/bin/gedit kernel: 3.10.5-201.fc19.x86_64 package: gedit-3.8.3-1.fc19 reason: Process /usr/bin/gedit was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000
Created attachment 811019 [details] Example file that crashes gedit when opening from file manager. It will not crash if you rename the extension to ".hex" or simply leave it out.
Had a bunch of tabs open, saved something, then the world ceased being awesome. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/gedit crash_function: gtk_box_size_allocate executable: /usr/bin/gedit kernel: 3.11.2-201.fc19.x86_64 package: gedit-3.8.3-1.fc19 reason: Process /usr/bin/gedit was killed by signal 5 (SIGTRAP) runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.