Bug 1046716 - [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 ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-notification-daemon
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:599890361b17bba984aec4f3401...
: 1008014 (view as bug list)
Depends On:
Blocks: 1046991
TreeView+ depends on / blocked
 
Reported: 2013-12-26 18:02 UTC by Sergey Bostandzhyan
Modified: 2013-12-30 04:59 UTC (History)
6 users (show)

Fixed In Version: mate-notification-daemon-1.6.1-2.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1046991 (view as bug list)
Environment:
Last Closed: 2013-12-30 04:59:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.02 KB, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: core_backtrace (11.05 KB, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: dso_list (7.20 KB, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: environ (717 bytes, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: maps (36.48 KB, text/plain)
2013-12-26 18:02 UTC, Sergey Bostandzhyan
no flags Details
File: open_fds (540 bytes, text/plain)
2013-12-26 18:03 UTC, Sergey Bostandzhyan
no flags Details
File: proc_pid_status (943 bytes, text/plain)
2013-12-26 18:03 UTC, Sergey Bostandzhyan
no flags Details
File: var_log_messages (206 bytes, text/plain)
2013-12-26 18:03 UTC, Sergey Bostandzhyan
no flags Details

Description Sergey Bostandzhyan 2013-12-26 18:02:41 UTC
Description of problem:
I was simply coding some stuff in vim when a notification about the crash popped up, was not doing anything
mate/desktop specific.

Version-Release number of selected component:
mate-notification-daemon-1.6.1-1.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.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 g_return_if_fail_warning at gmessages.c:1034
 #3 g_value_get_uchar at gvaluetypes.c:732
 #4 set_notification_hints at nodoka-theme.c:1010
 #5 notify_daemon_notify_handler at daemon.c:1369
 #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 1008014

Comment 1 Sergey Bostandzhyan 2013-12-26 18:02:45 UTC
Created attachment 842023 [details]
File: backtrace

Comment 2 Sergey Bostandzhyan 2013-12-26 18:02:47 UTC
Created attachment 842024 [details]
File: cgroup

Comment 3 Sergey Bostandzhyan 2013-12-26 18:02:51 UTC
Created attachment 842025 [details]
File: core_backtrace

Comment 4 Sergey Bostandzhyan 2013-12-26 18:02:53 UTC
Created attachment 842026 [details]
File: dso_list

Comment 5 Sergey Bostandzhyan 2013-12-26 18:02:55 UTC
Created attachment 842027 [details]
File: environ

Comment 6 Sergey Bostandzhyan 2013-12-26 18:02:57 UTC
Created attachment 842028 [details]
File: limits

Comment 7 Sergey Bostandzhyan 2013-12-26 18:02:59 UTC
Created attachment 842029 [details]
File: maps

Comment 8 Sergey Bostandzhyan 2013-12-26 18:03:01 UTC
Created attachment 842030 [details]
File: open_fds

Comment 9 Sergey Bostandzhyan 2013-12-26 18:03:03 UTC
Created attachment 842031 [details]
File: proc_pid_status

Comment 10 Sergey Bostandzhyan 2013-12-26 18:03:05 UTC
Created attachment 842032 [details]
File: var_log_messages

Comment 11 Sergey Bostandzhyan 2013-12-26 23:50:18 UTC
Continues to happen randomly, had it about 3-4 times today. Can't link it to any special activities, so unfortunately still no idea on how to reproduce.

Comment 12 Wolfgang Ulbrich 2013-12-27 00:10:02 UTC
#1  0x000000369f45063f in g_log (log_domain=log_domain@entry=0x36a0039aa4 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0x369f4bc89a "%s: assertion '%s' failed") at gmessages.c:1025
        args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fff659eeb40, reg_save_area = 0x7fff659eea80}}
#2  0x000000369f450679 in g_return_if_fail_warning (log_domain=log_domain@entry=0x36a0039aa4 "GLib-GObject", pretty_function=pretty_function@entry=0x36a00432b0 <__PRETTY_FUNCTION__.12794> "g_value_get_uchar", expression=expression@entry=0x36a0042ce4 "G_VALUE_HOLDS_UCHAR (value)") at gmessages.c:1034
No locals.
#3  0x00000036a00389a7 in g_value_get_uchar (value=0x9f7960) at gvaluetypes.c:732
        __PRETTY_FUNCTION__ = "g_value_get_uchar"
#4  0x00007f6f27babcf7 in set_notification_hints (nw=0xa16050, hints=0x9f8400) at nodoka-theme.c:1010
        windata = 0xa01710
        value = <optimized out>
        __FUNCTION__ = "set_notification_hints"
#5  0x0000000000406ebe in notify_daemon_notify_handler (daemon=0x9ce8c0, app_name=<optimized out>, id=0, icon=0x9b5230 "hamster-time-tracker", summary=0x9f4c10 "Working on dSS", body=<optimized out>, actions=0x9f8f00, hints=0x9f8400, timeout=-1, context=0x9f7980) at daemon.c:1369
        priv = 0x9ce880
        nt = 0x0
        nw = 0xa16050
        data = <optimized out>
        use_pos_data = 0
        new_notification = 1
        x = 0
        y = 0
        window_xid = 0
        return_id = <optimized out>
        sender = <optimized out>
        sound_file = 0x0
        sound_enabled = <optimized out>
        i = <optimized out>
        pixbuf = <optimized out>
        gsettings = <optimized out>

Can you uninstall 'hamster-time-tracker' if you don't needed?
And report if this solve the issue.

Comment 13 Sergey Bostandzhyan 2013-12-27 00:34:13 UTC
I kind of do need it in general, but I will uninstall it tomorrow and will let you know if the crashes disappear. Thanks for the hint, I did not notice the hamster stuff in the logs!

Comment 14 rh 2013-12-27 19:16:52 UTC
hamster-time-tracker is indeed the culprit in this case as it sends notifications not conforming to the notification specification.
See:
https://github.com/mate-desktop/mate-notification-daemon/pull/26
and
https://github.com/projecthamster/hamster/pull/127

Applying either patch fixes the problem.

Comment 15 Sergey Bostandzhyan 2013-12-27 19:43:29 UTC
Tested as promised: did not run hamster today - did not experience any mate notification daemon crashes.

Comment 16 Wolfgang Ulbrich 2013-12-27 19:47:47 UTC
(In reply to rh from comment #14)
> hamster-time-tracker is indeed the culprit in this case as it sends
> notifications not conforming to the notification specification.
> See:
> https://github.com/mate-desktop/mate-notification-daemon/pull/26
> and
> https://github.com/projecthamster/hamster/pull/127
> 
> Applying either patch fixes the problem.

Thanks, i will apply the patch for mate-notification-daemon and reasign the report to hamster if it is done.

(In reply to Sergey Bostandzhyan from comment #15)
> Tested as promised: did not run hamster today - did not experience any mate
> notification daemon crashes.

cool, great that it works.

Comment 17 Wolfgang Ulbrich 2013-12-27 19:54:13 UTC
*** Bug 1008014 has been marked as a duplicate of this bug. ***

Comment 18 Fedora Update System 2013-12-27 23:34:07 UTC
mate-notification-daemon-1.6.1-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mate-notification-daemon-1.6.1-2.fc19

Comment 19 Fedora Update System 2013-12-27 23:34:15 UTC
mate-notification-daemon-1.6.1-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-notification-daemon-1.6.1-2.fc18

Comment 20 Fedora Update System 2013-12-27 23:34:23 UTC
mate-notification-daemon-1.6.1-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/mate-notification-daemon-1.6.1-2.fc20

Comment 21 Ankur Sinha (FranciscoD) 2013-12-28 00:32:21 UTC
(In reply to rh from comment #14)
> hamster-time-tracker is indeed the culprit in this case as it sends
> notifications not conforming to the notification specification.
> See:
> https://github.com/mate-desktop/mate-notification-daemon/pull/26
> and
> https://github.com/projecthamster/hamster/pull/127
> 




Thank you for the bug report and patch. I'm assigning this back to mate-notification and cloning it to file a fresh one for hamster. It isn't a good idea to share bug reports between packages. Bodhi is supposed to close this when the mate notification hits stable which might be before the hamster update does the same etc.

Warm regards,
Ankur.

Comment 22 Wolfgang Ulbrich 2013-12-28 09:37:52 UTC
(In reply to Ankur Sinha (FranciscoD) from comment #21)
> Thank you for the bug report and patch. I'm assigning this back to
> mate-notification and cloning it to file a fresh one for hamster. It isn't a
> good idea to share bug reports between packages. Bodhi is supposed to close
> this when the mate notification hits stable which might be before the
> hamster update does the same etc.
> 
> Warm regards,
> Ankur.

No, i didn't marked the check box for closing this report with the update.  ;)
But cloning is also a way to handle this.

Comment 23 Fedora Update System 2013-12-28 23:34:46 UTC
mate-notification-daemon-1.6.1-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 24 Fedora Update System 2013-12-28 23:35:07 UTC
mate-notification-daemon-1.6.1-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 25 Fedora Update System 2013-12-28 23:41:49 UTC
Package mate-notification-daemon-1.6.1-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-notification-daemon-1.6.1-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-24080/mate-notification-daemon-1.6.1-2.fc20
then log in and leave karma (feedback).

Comment 26 Fedora Update System 2013-12-30 04:59:44 UTC
mate-notification-daemon-1.6.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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