Version-Release number of selected component: mate-notification-daemon-1.19.1-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon journald_cursor: s=7f84b6cc5be344bda01f6d9bf32ec356;i=10851bc7;b=03ebfcde5a804f329b9e4b9ffce4daa1;m=85633115c2;t=564088f406d08;x=5ee1fc1994226dd kernel: 4.14.14-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 6675 Truncated backtrace: Thread no. 1 (10 frames) #3 dconf_shm_open at dconf-shm.c:63 #4 dconf_engine_source_user_reopen at dconf-engine-source-user.c:76 #5 dconf_engine_source_refresh at dconf-engine-source.c:57 #6 dconf_engine_acquire_sources at dconf-engine.c:203 #7 dconf_engine_get_state at dconf-engine.c:314 #8 dconf_engine_watch_fast at dconf-engine.c:857 #9 g_object_new_internal at gobject.c:1837 #10 g_object_new_valist at gobject.c:2120 #12 notify_daemon_init at daemon.c:392 #13 g_type_create_instance at gtype.c:1866 Potential duplicate: bug 1165182
Created attachment 1389768 [details] File: backtrace
Created attachment 1389769 [details] File: cgroup
Created attachment 1389770 [details] File: core_backtrace
Created attachment 1389771 [details] File: cpuinfo
Created attachment 1389772 [details] File: dso_list
Created attachment 1389773 [details] File: environ
Created attachment 1389774 [details] File: limits
Created attachment 1389775 [details] File: maps
Created attachment 1389776 [details] File: mountinfo
Created attachment 1389777 [details] File: open_fds
Created attachment 1389778 [details] File: proc_pid_status
Similar problem has been detected: logging in X2Go reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon journald_cursor: s=9a474aa2f6124ef291f8a7910c7caff1;i=f0760f1;b=6ecbb92662c74928aaa33397e2281f5d;m=1098ad6feb9;t=5654b44c586fb;x=784c6112117c3b43 kernel: 4.14.14-300.fc27.x86_64 package: mate-notification-daemon-1.19.1-1.fc27 reason: mate-notification-daemon killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 6675
Similar problem has been detected: just tried logging in with X2Go reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon journald_cursor: s=664a140e89af4d069da14f8f40522c15;i=3531d;b=e297e718a24f4008bb309ce42ae47d53;m=699334fd01;t=5637b62cacf1a;x=2b30b6a10631c5d0 kernel: 4.14.13-300.fc27.x86_64 package: mate-notification-daemon-1.19.1-1.fc27 reason: mate-notification-daemon killed by SIGTRAP rootdir: / runlevel: 1 3 type: CCpp uid: 1000
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.