Version-Release number of selected component: mate-notification-daemon-1.5.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.6.11-3.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 _cairo_arc_in_direction at cairo-arc.c:189 #5 _cairo_default_context_arc at cairo-default-context.c:778 #6 cairo_arc_negative at cairo.c:1684 #7 draw_pie at nodoka-theme.c:485 #8 countdown_expose_cb at nodoka-theme.c:595 #9 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #14 gtk_widget_event_internal at gtkwidget.c:5017 #15 gtk_widget_send_expose at gtkwidget.c:4846 #16 gtk_main_do_event at gtkmain.c:1610 #17 _gdk_window_process_updates_recurse at gdkwindow.c:5429
Created attachment 670042 [details] File: backtrace
Created attachment 670043 [details] File: cgroup
Created attachment 670044 [details] File: core_backtrace
Created attachment 670045 [details] File: dso_list
Created attachment 670046 [details] File: environ
Created attachment 670047 [details] File: limits
Created attachment 670048 [details] File: maps
Created attachment 670049 [details] File: open_fds
Created attachment 670050 [details] File: proc_pid_status
Created attachment 670051 [details] File: smolt_data
Created attachment 670052 [details] File: var_log_messages
mate-notification-daemon-1.5.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-1181/mate-notification-daemon-1.5.1-1.fc18
mate-notification-daemon-1.5.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I am still getting this error when I attempt to connect to my bluetooth headset. The connection works, but this error still occurs.
(In reply to comment #14) > I am still getting this error when I attempt to connect to my bluetooth > headset. The connection works, but this error still occurs. Have you installed mate-bluetooth?
I didn't have mate-bluetooth installed. That package was not available when I installed the other mate packages. I just installed it, so I'll see if I get the error the next time I do something bluetoothy.
Okay cool. Let me know how that goes. I also just pushed out a bunch of updates (to updates-testing).
Any update?
recieving a call in ekiga backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.8.7-201.fc18.x86_64 package: mate-notification-daemon-1.5.1-1.fc18 reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors:
Did this issue still exits with an updated MATE desktop, we're are on 1.6.x ? I did also a fixed update for mate-notification-daemon.
Crash happens during kde-specific bug report master try to report another crash report (for kdevelop crash) reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.9.10-200.fc18.x86_64 package: mate-notification-daemon-1.6.0-2.fc18 reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors:
Created attachment 776976 [details] backtrace
mate-notification-daemon-1.6.0-2.fc18.x86_64 mate-desktop-1.6.1-8.fc18.x86_64
*** Bug 984165 has been marked as a duplicate of this bug. ***
It's hard to tell, since there is no popup, but I think it happens to me when a call comes in for ekiga. mate-notification-daemon-1.6.0-2.i686
Could you try another notification theme as the nodoka-theme to confirm if the issue occours with another theme? Use 'mate-notification-properties' to change the theme.
Rebooted my system and it showed up reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon core_backtrace: crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.9.11-200.fc18.i686 package: mate-notification-daemon-1.6.0-2.fc18 reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors:
I switched from nodoka-theme to standard-theme, and so far no recurrences. So, a bug in nodoka-theme perhaps?
I spoke too soon. It just crashed again at the same spot.
*** Bug 1005738 has been marked as a duplicate of this bug. ***
upstream informed. https://github.com/mate-desktop/mate-notification-daemon/issues/20
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Another user experienced a similar problem: ekiga got a call, and tried to open a notifier to answer the call. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.12.6-200.fc19.i686 package: mate-notification-daemon-1.6.1-2.fc19 reason: mate-notification-daemon killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Still happening in F19
Is there a way to make abrt submit a current backtrace? The backtrace from 2012 is getting rather long in the tooth.
(In reply to Stuart D Gathman from comment #35) > Is there a way to make abrt submit a current backtrace? The backtrace from > 2012 is getting rather long in the tooth. You can run the abrt commands in a terminal and submit the backtrace by hand. Go to /var/tmp/abrt/<right-folder-of-the-issue>/ Open the file 'component' for check the <right-folder-of-the-issue>. Run 'abrt-action-analyze-ccpp-local', this will install the necessary debuginfo packages and should generate the backtrace. Now check generated backtrace for missing debuginfo packages. IE, if you find a line like this the debuginfo package is missing. 0x0000003703455590 0x00000037034c1464 Yes (*) /usr/lib64/nvidia/libGL.so.1 (*): Shared library is missing debugging information yum provides /usr/lib64/nvidia/libGL.so.1 debuginfo-install <package-name> Note, in this example from rpmfusion nvidia driver there is no debuginfo package available. Than execute 'abrt-action-generate-backtrace' to generate a updated backtrace.
It occurs for me when I click on button OPEN in notification from liferea.
(In reply to Pavel Mlčoch from comment #37) > It occurs for me when I click on button OPEN in notification from liferea. You should inform upstream about your observation for helping them to fix the issue. https://github.com/mate-desktop/mate-notification-daemon/issues/20
*** Bug 1116985 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: when receiving a call in ekiga reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: _cairo_arc_in_direction executable: /usr/libexec/mate-notification-daemon kernel: 3.16.2-200.fc20.x86_64 package: mate-notification-daemon-1.8.0-2.fc20 reason: mate-notification-daemon killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
The workaround to answer a call in ekiga if you don't a notification is "View -> Video Preview" (or press the webcam button) from the main ekiga window, and click the green answer button there.
mate-notification-daemon-1.8.0-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mate-notification-daemon-1.8.0-4.fc21
mate-notification-daemon-1.8.0-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-notification-daemon-1.8.0-3.fc20
mate-notification-daemon-1.6.1-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-notification-daemon-1.6.1-3.fc19
mate-notification-daemon-1.8.0-2.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mate-notification-daemon-1.8.0-2.el7
Just tested mate-notification-daemon-1.8.0-3.fc20. Now an incoming call in ekiga generates a notification that I can answer. No more crash. Thanks.
fine that it works. Sam Tygier needs an fas account for that the karma will be count ;) samtygier.uk (unauthenticated) - 2014-10-03 16:22:36 (karma: +1 (ignored)) Fixes 890728 for me. I can now accept a call with ekiga.
Package mate-notification-daemon-1.8.0-2.el7: * should fix your issue, * was pushed to the Fedora EPEL 7 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mate-notification-daemon-1.8.0-2.el7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3108/mate-notification-daemon-1.8.0-2.el7 then log in and leave karma (feedback).
mate-notification-daemon-1.8.0-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mate-notification-daemon-1.8.0-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mate-notification-daemon-1.6.1-3.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.8.0-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.