Hide Forgot
Description of problem: Usually this segfault doesn't occur (meaning: I've used this program without problems many times). I am sure it will most likely not occur when I reboot. But once this problem occurs, gedit is not the only program which reliably crashes every time (see https://bugzilla.redhat.com/show_bug.cgi?id=1003300 for a similar bug with /usr/bin/Terminal). After reliably crashing /usr/bin/Terminal, I just wanted to find some other binaries which crash in similar ways, and gedit was among those other binaries that segfaulted. $ /usr/bin/gedit Segmentation fault (core dumped) Some other programs that worked (most of the time) without problems in the past, but curretly segfault relianbly: $ /usr/bin/Terminal Segmentation fault (core dumped) $ /usr/bin/ristretto Segmentation fault (core dumped) $ /usr/bin/evince Segmentation fault (core dumped) But many other programs are not affected (otherwise I wouldn't be able to report this bug now). I'll keep the system running, so that I can perform additional tests if you let me know what might be useful. Version-Release number of selected component: gedit-3.6.2-1.fc18 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: gedit crash_function: __strcmp_sse42 executable: /usr/bin/gedit kernel: 3.10.10-100.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_sse42 at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:233 #1 _gtk_icon_cache_has_icon at gtkiconcache.c:362 #2 gtk_icon_theme_has_icon at gtkicontheme.c:1675 #3 gtk_action_group_add_actions_full at gtkactiongroup.c:1188 #4 gtk_action_group_add_actions at gtkactiongroup.c:1105 #5 create_menu_bar_and_toolbar at gedit-window.c:1541 #6 gedit_window_init at gedit-window.c:4099 #7 g_type_create_instance at gtype.c:1890 #8 g_object_constructor at gobject.c:1854 #11 gedit_app_create_window_impl at gedit-app.c:506
Created attachment 797289 [details] File: backtrace
Created attachment 797290 [details] File: cgroup
Created attachment 797291 [details] File: core_backtrace
Created attachment 797292 [details] File: dso_list
Created attachment 797293 [details] File: environ
Created attachment 797294 [details] File: exploitable
Created attachment 797295 [details] File: limits
Created attachment 797296 [details] File: maps
Created attachment 797297 [details] File: open_fds
Created attachment 797298 [details] File: proc_pid_status
Created attachment 797299 [details] File: var_log_messages
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.