Description of problem: I emptied most of $HOME because Gnome 3 wasn't working, logged in to kde and tried to start Leafpad. ABRT popped up. I tried leafpad from konsole and saw that it had a segmentation fault. I then logged out of kde, emptied /home from the terminal and logged back in to kde and saw that leafpad still had a segmentation fault. I uninstalled leafpad, reinstalled it and am still getting a segmentation fault. Version-Release number of selected component: leafpad-0.8.18.1-5.fc18 Additional info: backtrace_rating: 4 cmdline: leafpad crash_function: gtk_text_view_set_attributes_from_style executable: /usr/bin/leafpad kernel: 3.7.5-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_text_view_set_attributes_from_style at gtktextview.c:6380 #1 gtk_text_view_style_set at gtktextview.c:3980 #6 gtk_widget_set_style_internal at gtkwidget.c:7001 #7 gtk_widget_reset_rc_style at gtkwidget.c:6613 #8 reset_rc_styles_recurse at gtkwidget.c:7211 #9 gtk_scrolled_window_forall at gtkscrolledwindow.c:1085 #10 gtk_box_forall at gtkbox.c:1251 #11 gtk_rc_reset_widgets at gtkrc.c:1638 #12 _gtk_rc_context_get_default_font_name at gtkrc.c:1736 #18 g_object_notify_by_spec_internal at gobject.c:1135
Created attachment 693687 [details] File: backtrace
Created attachment 693688 [details] File: cgroup
Created attachment 693689 [details] File: core_backtrace
Created attachment 693690 [details] File: dso_list
Created attachment 693691 [details] File: environ
Created attachment 693692 [details] File: limits
Created attachment 693693 [details] File: maps
Created attachment 693694 [details] File: open_fds
Created attachment 693695 [details] File: proc_pid_status
Created attachment 693696 [details] File: var_log_messages
I have tried leafpad in several desktop environments and the segmentation fault appears to occur only in KDE. I also tried "gdb leafpad" This gives "Program received signal SIGSEGV, Segmentation fault. gtk_text_view_set_attributes_from_style (style=0x66a810, values=0x0, text_view=<optimized out>) at gtktextview.c:6380 6380 if (values->font)" The segmentation fault disappears if I change change "GTK+ Appearance to something other than oxygen-gtk in systemsettings.
I opened the my project lpr-file through popup menu item 'open with' and chose "leafpad" application. The project was created in Lazarus IDE 1.0.4. backtrace_rating: 4 Package: leafpad-0.8.18.1-5.fc18 OS Release: Fedora release 18 (Spherical Cow)
(In reply to comment #12) > I opened the my project lpr-file through popup menu item 'open with' and > chose "leafpad" application. The project was created in Lazarus IDE 1.0.4. > > backtrace_rating: 4 > Package: leafpad-0.8.18.1-5.fc18 > OS Release: Fedora release 18 (Spherical Cow) It happened twice on the same lpr-file.
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.