Description of problem: I locked screen of my Lenovo Thinkpad T450s and was away from about 10 minutes. When I got back the screen was black and I could not get login box to appear. Eventually had to use CTRL-ALT+F2 to enter to console and use systemctl restart lightdm to restart display manager. When I logged back in to MATE it reported that mate-notification-daemon had segvaulted. No idea if this was the cause for the lockscreen problem or just an after effect of restarting lightdm. Version-Release number of selected component: mate-notification-daemon-1.22.0-1.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: g_type_check_instance_is_a executable: /usr/libexec/mate-notification-daemon journald_cursor: s=d650139227884250a4fc513a6ad7122d;i=29c5;b=d913983090b24147b748e20659546e0b;m=142c951ca4;t=58b1e6d996167;x=51e2f2937ce9e513 kernel: 5.0.19-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 20147 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:4013 #1 gdk_monitor_get_geometry at gdkmonitor.c:282 #2 notify_stack_shift_notifications at stack.c:294 #3 notify_stack_add_window at stack.c:383 #4 notify_daemon_notify_handler at daemon.c:1538 #5 ffi_call_unix64 at ../src/x86/unix64.S:76 #6 ffi_call at ../src/x86/ffi64.c:525 #7 g_cclosure_marshal_generic at gclosure.c:1496 #10 g_signal_emitv at gsignal.c:3129 #11 _notify_daemon_notifications_skeleton_handle_method_call at mnd-dbus-generated.c:1736
Created attachment 1580222 [details] File: backtrace
Created attachment 1580223 [details] File: cgroup
Created attachment 1580224 [details] File: core_backtrace
Created attachment 1580225 [details] File: cpuinfo
Created attachment 1580226 [details] File: dso_list
Created attachment 1580227 [details] File: environ
Created attachment 1580228 [details] File: exploitable
Created attachment 1580229 [details] File: limits
Created attachment 1580230 [details] File: maps
Created attachment 1580231 [details] File: mountinfo
Created attachment 1580232 [details] File: open_fds
Created attachment 1580233 [details] File: proc_pid_status
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.