| Summary: | [abrt] notification-daemon-0.7.1-1.fc15: g_return_if_fail_warning: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||
| Component: | notification-daemon | Assignee: | David Zeuthen <davidz> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | davidz, jmccann, johannbg, mclasen | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:91b7bc506163a795cb780dcdda1c9ab3fda628c9 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-03-30 15:11:55 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Kamil Páral
2011-04-12 14:34:18 UTC
Created attachment 491496 [details]
File: backtrace
Created attachment 501206 [details]
environ
These bugs are slightly annoying. I cannot, however, figure out what precisely I am doing that is triggering them as it seems to be under different circumstances each time.
Created attachment 501207 [details]
Maps
*** Bug 677565 has been marked as a duplicate of this bug. *** Backtrace analysis found this bug to be similar to bug #709556, closing as duplicate. This bug seems to belong to component gtk3. Bugs which were found to be similar to this bug: mail-notification: bug #737601 notification-daemon: bug #677565, bug #709556 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 709556 *** |