Version-Release number of selected component: mate-notification-daemon-1.6.0-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon kernel: 3.9.5-301.fc19.x86_64 runlevel: N 5 uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #2 dconf_shm_open at dconf-shm.c:87 #3 dconf_engine_source_user_reopen at dconf-engine-source-user.c:76 #4 dconf_engine_source_refresh at dconf-engine-source.c:57 #5 dconf_engine_acquire_sources at dconf-engine.c:201 #6 dconf_engine_get_state at dconf-engine.c:311 #7 dconf_engine_watch_fast at dconf-engine.c:762 #9 g_object_new_valist at gobject.c:1836 #11 g_settings_new at gsettings.c:869 #12 notify_daemon_init at daemon.c:364 #13 g_type_create_instance at gtype.c:1917 Potential duplicate: bug 890084
Created attachment 773295 [details] File: backtrace
Created attachment 773296 [details] File: cgroup
Created attachment 773297 [details] File: core_backtrace
Created attachment 773298 [details] File: dso_list
Created attachment 773299 [details] File: environ
Created attachment 773300 [details] File: limits
Created attachment 773301 [details] File: maps
Created attachment 773302 [details] File: open_fds
Created attachment 773303 [details] File: proc_pid_status
Created attachment 773304 [details] File: var_log_messages
*** Bug 890084 has been marked as a duplicate of this bug. ***
*** Bug 990105 has been marked as a duplicate of this bug. ***
no visible problem maybe not enough place in the notififaction area reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon kernel: 3.10.11-200.fc19.i686.PAE package: mate-notification-daemon-1.6.0-2.fc19 reason: Process /usr/libexec/mate-notification-daemon was killed by signal 5 (SIGTRAP) runlevel: N 5 type: CCpp uid: 1000
nobady was near the host when this happened. Given the timing, I suspect a suspend operation was attempted reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon kernel: 3.11.4-101.fc18.i686.PAE package: mate-notification-daemon-1.6.0-2.fc18 reason: Process /usr/libexec/mate-notification-daemon was killed by signal 5 (SIGTRAP) runlevel: N 5 type: CCpp uid: 1001
*** Bug 1044477 has been marked as a duplicate of this bug. ***
Just happened to me. It happened after caja (mate-file-manager) crashed. I got a notification of the crash, which was followed by the crash of the notification daemon.
Mate-notification-daemon followed up what happened in comment 16 by a crash of its own. abrt sent me to https://bugzilla.redhat.com/show_bug.cgi?id=1044477 but that bug was closed as a duplicate of this one.
Another user experienced a similar problem: Went through yumex and installed, Amarok, a few extra gstreamers and xine,,rebooted and... reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon kernel: 3.12.8-300.fc20.i686+PAE package: mate-notification-daemon-1.6.1-2.fc20 reason: mate-notification-daemon killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Die at log in my local acount reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: dconf_shm_open executable: /usr/libexec/mate-notification-daemon kernel: 3.14.4-200.fc20.x86_64 package: mate-notification-daemon-1.6.1-2.fc20 reason: mate-notification-daemon killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
I think this needs to be reported to the MATE developers upstream -- there are very few people actually triaging and fixing MATE on Fedora.
*** This bug has been marked as a duplicate of bug 753882 ***