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 1145144 - gnome-settings-daemon killed by SIGSEGV
Summary: gnome-settings-daemon killed by SIGSEGV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-settings-daemon
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 7.0
Assignee: Rui Matos
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 13:23 UTC by jigar
Modified: 2019-05-20 11:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 10:59:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0481 0 normal SHIPPED_LIVE gnome-settings-daemon bug fix and enhancement update 2015-03-05 15:44:00 UTC

Description jigar 2014-09-22 13:23:50 UTC 
Description of problem: gnome-settings-daemon killed by SIGSEGV . Also the customer is not able to log into root using su via GUI or CLI because it segfaults.


Version-Release number of selected component : gnome-settings-daemon-3.8.6.1-9.el7_0.1


How reproducible: Always


Steps to Reproduce:
1. Try logging into root via su
2. ABRT case is generated due to Segmentation Fault.


Actual results: gnome-settings-daemon crashes and switching to su segfaults


Expected results: gnome-settings daemon should not crash and switching to root should not segfault.


Additional info: I used the rescue disk to create another user with the UID/GID, and I can su to that user just fine. I can also su between users, and to/from the new user.
Comment 1 jigar 2014-09-22 13:25:45 UTC 
Below is the backtrace for reference for the above crash.

Core was generated by `/usr/libexec/gnome-settings-daemon'.
Program terminated with signal 11, Segmentation fault.

#0  g_cancellable_cancel (cancellable=0x726f2f0073754244) at gcancellable.c:485
485           cancellable->priv->cancelled)
(gdb) bt
#0  g_cancellable_cancel (cancellable=0x726f2f0073754244) at gcancellable.c:485
#1  0x00007f6b3014d650 in vino_vanished_cb (connection=<optimized out>, name=<optimized out>, manager=0x1946500) at gsd-remote-display-manager.c:141
#2  0x00007f6b5995daf3 in do_call (client=client@entry=0x19de990, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at gdbusnamewatching.c:216
#3  0x00007f6b5995dd25 in call_vanished_handler (client=client@entry=0x19de990, ignore_cancelled=0) at gdbusnamewatching.c:242
#4  0x00007f6b5995e008 in on_name_owner_changed (connection=<optimized out>, sender_name=0x7f6b3c10cb80 "org.freedesktop.DBus", object_path=<optimized out>, 
    interface_name=0x7f6b3c10e160 "org.freedesktop.DBus", signal_name=<optimized out>, parameters=0x7f6b3c05d430, user_data=0x19de990) at gdbusnamewatching.c:307
#5  0x00007f6b5994f1b5 in emit_signal_instance_in_idle_cb (data=0x7f6b3c00bdf0) at gdbusconnection.c:3715
#6  0x00007f6b587c2ac6 in g_main_dispatch (context=0x18e7540) at gmain.c:3058
#7  g_main_context_dispatch (context=context@entry=0x18e7540) at gmain.c:3634
#8  0x00007f6b587c2e48 in g_main_context_iterate (context=0x18e7540, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3705
#9  0x00007f6b587c325a in g_main_loop_run (loop=0x191d940) at gmain.c:3899
#10 0x00007f6b5a2310ed in gtk_main () at gtkmain.c:1156
#11 0x0000000000403847 in main (argc=1, argv=0x7fff93b59ad8) at main.c:479
Comment 3 Bastien Nocera 2014-09-25 10:19:03 UTC 
Fixed upstream (in GNOME 3.8, 3.10, 3.12 and 3.14)

commit 272fae4221bc375fefb43810179aaff85b45b3ac
Author: Bastien Nocera <hadess>
Date:   Thu Sep 25 12:14:42 2014 +0200

    remote-display: Initialise ->cancellable
    
    At least once, right?
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1145144

commit 9765a98a1063ef9bfc0a7cfee566e534384c601c
Author: Bastien Nocera <hadess>
Date:   Thu Sep 25 12:12:47 2014 +0200

    remote-display: Stop plugin when exiting
    
    Make sure that the plugin is stopped when it's disposed of.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1145144

commit ede9c19215951d6161a8d5a018149be6637662b6
Author: Bastien Nocera <hadess>
Date:   Thu Sep 25 12:11:43 2014 +0200

    remote-display: Stop watching the D-Bus name on stop
    
    So that we don't get called out when the plugin is stopped.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1145144
Comment 5 Michael Boisvert 2015-01-14 16:44:30 UTC 
Tested in gnome-settings-daemon-3.8.6.1-12.el7, no segfaults when logging into root via su. Verified.
Comment 7 errata-xmlrpc 2015-03-05 10:59:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0481.html
Note You need to log in before you can comment on or make changes to this bug.