Bug 599043
| Summary: | [abrt] notification-daemon-0.4.1-0.20090923.4.el6: raise: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Ward <cward> | ||||||
| Component: | notification-daemon | Assignee: | Florian Müllner <fmuellner> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 6.0 | CC: | jofernan, mclasen, rlat, tpelka | ||||||
| Target Milestone: | rc | Keywords: | Rebase | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:7eb4b4402326d7819280ff7e7c73c8c897f4d444 | ||||||||
| Fixed In Version: | notification-daemon-0_5_0-1_el6 | Doc Type: | Rebase: Bug Fixes and Enhancements | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-06-13 07:44:37 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: | 609244 | ||||||||
| Bug Blocks: | 662543 | ||||||||
| Attachments: |
|
||||||||
|
Description
Chris Ward
2010-06-02 15:10:49 UTC
Created attachment 419065 [details]
File: backtrace
Line 214 in stack.c is
gdk_screen_get_monitor_geometry (stack->screen, stack->monitor, &monitor);
Looks like we need to protect against stack->monitor being >= gdk_screen_get_n_monitors(stack->screen) here.
As far as reproducing this problem, I would assume the following might work: 1. move gnome-panel to external monitor 2. unplug external monitor 3. use notify-send to pop up several bubbles Do you need me to do additional testing or provide you with any additional information at this time? Just let me know. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. *** Bug 599193 has been marked as a duplicate of this bug. *** *** Bug 603656 has been marked as a duplicate of this bug. *** Created attachment 452757 [details] backtrace Package: notification-daemon-0.5.0-1.el6 Latest Crash: Mon 11 Oct 2010 06:16:50 PM Command: /usr/libexec/notification-daemon Reason: Process /usr/libexec/notification-daemon was killed by signal 11 (SIGSEGV) Segfault when running reproducer from comment 4 (no additional info on output). This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. This request has been proposed for the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Stale bug clean up; reopen if anyone else actually supports this. |