RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 699681 - [abrt] notification-daemon-0.5.0-1.el6: g_type_check_instance_cast: Process /usr/libexec/notification-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] notification-daemon-0.5.0-1.el6: g_type_check_instance_cast: Process /...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: notification-daemon
Version: 6.1
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:50e33e6100d574260267f2c011f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 11:04 UTC by Radek Lat
Modified: 2017-12-06 12:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:34:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
File: backtrace (26.34 KB, text/plain)
2011-04-26 11:04 UTC, Radek Lat 		no flags Details
backtrace 2 (24.56 KB, text/plain)
2014-09-03 15:02 UTC, Jiri Koten 		no flags Details
View All

Description Radek Lat 2011-04-26 11:04:33 UTC 
abrt version: 1.1.16
architecture: x86_64
Attached file: backtrace, 26977 bytes
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
Attached file: coredump, 3796992 bytes
crash_function: g_type_check_instance_cast
executable: /usr/libexec/notification-daemon
kernel: 2.6.32-131.0.5.el6.x86_64
package: notification-daemon-0.5.0-1.el6
rating: 4
reason: Process /usr/libexec/notification-daemon was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.1 Beta (Santiago)
Attached file: sosreport.tar.xz, 540644 bytes
time: 1303812137
uid: 501

comment
-----
This is also easily reproducible with docking station. It is enough to take workstation from it and then after few seconds put it back again.

I am not sure, if screen configuration makes any difference so just in case, I used main screen on the bottom and external on the top.

How to reproduce
-----
1. Obtain dualhead setup
2. Connect external monitor, make sure it is recognised by system
3. Disconnect monitor
3. Immediately after that, before system recognizes disconnected monitor, run in terminal:
     $ notify-send -t 20000 "Test message"
4. Wait until system recognizes disconnected monitor, then connect it back
5. After few moments crash appears
Comment 1 Radek Lat 2011-04-26 11:04:35 UTC 
Created attachment 494871 [details]
File: backtrace
Comment 3 RHEL Program Management 2011-04-26 11:38:04 UTC 
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.
Comment 4 David Jaša 2011-06-08 13:03:31 UTC 
Package: notification-daemon-0.5.0-1.el6
Architecture: x86_64
OS Release: Red Hat Enterprise Linux Workstation release 6.1 (Santiago)


How to reproduce
-----
1. during NM-related events (network disconnected)
2.
3.
Comment 5 Jiri Koten 2014-09-03 15:02:08 UTC 
Created attachment 934131 [details]
backtrace 2

Still an issue in rhel 6.6


notification-daemon-0.5.0-1.el6
glib2-2.28.8-2.el6
gtk2-2.24.23-6.el6
Comment 6 Jan Kurik 2017-12-06 12:34:26 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.