Hide Forgot
Description of problem: 1. Launch SystemLog, via Menu->Administration->SystemLog. 2. Press "?File" buttons (right side of the top bar, near "?Search" button. There are no labels). 3. Press "Filters" in the drop-down menu-list. 4. Press "Manage Filters" in the following second sub-list. 5. Press "Add". 6. Enter any name in the "Name" dialogs field-string of the dialog box, and any regular expression to the "Regular Expression" field-string. 7. Press "Apply" 8. Application crached, w/o any visual sign or warning. 9. If you launch apllication via CLI in the terminal window, there are additional messages: "Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (logview:3822): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (logview:3822): GLib-GObject-WARNING **: g_object_get_valist: object class 'GtkTextTag' has no property named 'foreground-gdk' Segmentation fault (core dumped)" " Version-Release number of selected component: gnome-system-log-3.9.90-6.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/logview crash_function: thread_memory_magazine2_free executable: /usr/bin/logview global_pid: 16446 kernel: 4.7.9-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 thread_memory_magazine2_free at gslice.c:855 #1 g_slice_free1 at gslice.c:1122 #2 gdk_color_free at deprecated/gdkcolor.c:86 #3 save_filter_foreach_func at logview-prefs.c:226 #4 g_hash_table_foreach at ghash.c:1608 #5 save_filters at logview-prefs.c:257 #6 logview_prefs_add_filter at logview-prefs.c:504 #7 on_dialog_add_edit_reponse at logview-filter-manager.c:257 #8 g_cclosure_marshal_VOID__ENUMv at gmarshal.c:1496 #9 _g_closure_invoke_va at gclosure.c:867
Created attachment 1215143 [details] File: backtrace
Created attachment 1215144 [details] File: cgroup
Created attachment 1215145 [details] File: core_backtrace
Created attachment 1215146 [details] File: dso_list
Created attachment 1215147 [details] File: environ
Created attachment 1215148 [details] File: exploitable
Created attachment 1215149 [details] File: limits
Created attachment 1215150 [details] File: maps
Created attachment 1215151 [details] File: mountinfo
Created attachment 1215152 [details] File: namespaces
Created attachment 1215153 [details] File: open_fds
Created attachment 1215154 [details] File: proc_pid_status
Created attachment 1215155 [details] File: var_log_messages
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.