Bug 1046716
Summary: | [abrt] mate-notification-daemon: g_return_if_fail_warning(): mate-notification-daemon killed by SIGTRAP | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sergey Bostandzhyan <jin> | ||||||||||||||||||||||
Component: | mate-notification-daemon | Assignee: | Dan Mashal <dan.mashal> | ||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 20 | CC: | dan.mashal, fedora, rdieter, rh, sanjay.ankur, stefano | ||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/fa35b025253f2bfc0950fce217320b15f0215e9e | ||||||||||||||||||||||||
Whiteboard: | abrt_hash:599890361b17bba984aec4f3401b90f3ea98ccd0 | ||||||||||||||||||||||||
Fixed In Version: | mate-notification-daemon-1.6.1-2.fc20 | Doc Type: | Bug Fix | ||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | |||||||||||||||||||||||||
: | 1046991 (view as bug list) | Environment: | |||||||||||||||||||||||
Last Closed: | 2013-12-30 04:59:44 UTC | Type: | --- | ||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||||||
Bug Blocks: | 1046991 | ||||||||||||||||||||||||
Attachments: |
|
Description
Sergey Bostandzhyan
2013-12-26 18:02:41 UTC
Created attachment 842023 [details]
File: backtrace
Created attachment 842024 [details]
File: cgroup
Created attachment 842025 [details]
File: core_backtrace
Created attachment 842026 [details]
File: dso_list
Created attachment 842027 [details]
File: environ
Created attachment 842028 [details]
File: limits
Created attachment 842029 [details]
File: maps
Created attachment 842030 [details]
File: open_fds
Created attachment 842031 [details]
File: proc_pid_status
Created attachment 842032 [details]
File: var_log_messages
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. #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. 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! 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. Tested as promised: did not run hamster today - did not experience any mate notification daemon crashes. (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. *** Bug 1008014 has been marked as a duplicate of this bug. *** 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 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 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 (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. (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. 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. 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. 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). 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. |