Bug 216698 - prevent a possible crash if dbus is not available
Summary: prevent a possible crash if dbus is not available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: control-center
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ray Strode [halfline]
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-21 16:16 UTC by Matthias Clasen
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: 5.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-04 05:21:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
the patch (1.03 KB, patch)
2006-11-21 16:18 UTC, Matthias Clasen
no flags Details | Diff

Description Matthias Clasen 2006-11-21 16:16:09 UTC
This is a fix found in the upstream 2.16.2 control-center package that
prevents a possible NULL pointer dereference. It can happen in situations
where dbus is not available when gnome-session is run. Unfortunately, I 
don't have explicit reproduction information, but the patch is obviously
correct and harmless.

Comment 1 Matthias Clasen 2006-11-21 16:18:24 UTC
Created attachment 141782 [details]
the patch

Comment 2 RHEL Program Management 2006-11-21 16:41:08 UTC
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.

Comment 3 Matthias Clasen 2006-11-22 22:49:52 UTC
Fix included in control-center-2.16.0-13.el5

Comment 4 Yan Tian 2006-11-24 07:43:15 UTC
Verified attached patch had been included in control-center-2.16.0-13.el5.

Comment 5 Xiaohong Wang 2006-12-04 05:21:03 UTC
control-center-2.16.0-13.el5 has been included in RHEL5-Client-20061201.0, so
resolve this bug.


Note You need to log in before you can comment on or make changes to this bug.