Bug 1049636 - [abrt] mate-notification-daemon: g_return_if_fail_warning(): mate-notification-daemon killed by SIGTRAP
Summary: [abrt] mate-notification-daemon: g_return_if_fail_warning(): mate-notificatio...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-notification-daemon
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:54a565f6a5edeade565e96893f8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-07 22:05 UTC by Christopher Chavez
Modified: 2014-02-15 14:26 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-15 14:26:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.65 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: cgroup (159 bytes, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: core_backtrace (9.74 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: dso_list (7.84 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: environ (2.71 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: limits (1.29 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: maps (27.42 KB, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: open_fds (519 bytes, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: proc_pid_status (792 bytes, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details
File: var_log_messages (220 bytes, text/plain)
2014-01-07 22:05 UTC, Christopher Chavez
no flags Details

Description Christopher Chavez 2014-01-07 22:05:30 UTC
Version-Release number of selected component:
mate-notification-daemon-1.6.1-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/mate-notification-daemon
crash_function: g_return_if_fail_warning
executable:     /usr/libexec/mate-notification-daemon
kernel:         3.12.6-300.fc20.i686+PAE
runlevel:       N 3
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 g_return_if_fail_warning at gmessages.c:1034
 #3 matewnck_window_is_on_workspace at window.c:2396
 #4 fullscreen_window_exists at daemon.c:1168
 #5 notify_daemon_notify_handler at daemon.c:1564
 #6 dbus_glib_marshal_notification_daemon_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER at notificationdaemon-dbus-glue.h:102
 #7 invoke_object_method at dbus-gobject.c:1899
 #8 object_registration_message at dbus-gobject.c:2161
 #9 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #16 gtk_main at gtkmain.c:1257

Potential duplicate: bug 908513

Comment 1 Christopher Chavez 2014-01-07 22:05:37 UTC
Created attachment 846848 [details]
File: backtrace

Comment 2 Christopher Chavez 2014-01-07 22:05:38 UTC
Created attachment 846849 [details]
File: cgroup

Comment 3 Christopher Chavez 2014-01-07 22:05:39 UTC
Created attachment 846850 [details]
File: core_backtrace

Comment 4 Christopher Chavez 2014-01-07 22:05:42 UTC
Created attachment 846851 [details]
File: dso_list

Comment 5 Christopher Chavez 2014-01-07 22:05:44 UTC
Created attachment 846852 [details]
File: environ

Comment 6 Christopher Chavez 2014-01-07 22:05:45 UTC
Created attachment 846853 [details]
File: limits

Comment 7 Christopher Chavez 2014-01-07 22:05:47 UTC
Created attachment 846854 [details]
File: maps

Comment 8 Christopher Chavez 2014-01-07 22:05:49 UTC
Created attachment 846855 [details]
File: open_fds

Comment 9 Christopher Chavez 2014-01-07 22:05:50 UTC
Created attachment 846856 [details]
File: proc_pid_status

Comment 10 Christopher Chavez 2014-01-07 22:05:51 UTC
Created attachment 846857 [details]
File: var_log_messages

Comment 11 Wolfgang Ulbrich 2014-01-12 10:52:49 UTC
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?


Note You need to log in before you can comment on or make changes to this bug.