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 1049965 - [abrt] gdm-3.8.1.1-3.fc19: act_user_is_loaded: Process /usr/libexec/gdm-session-worker was killed by signal 11 (SIGSEGV)
Summary: [abrt] gdm-3.8.1.1-3.fc19: act_user_is_loaded: Process /usr/libexec/gdm-sessi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.0
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL: http://faf-report.itos.redhat.com/rep...
Whiteboard: abrt_hash:73336bc98ca97b65299d63dd53d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-08 14:33 UTC by Michal Toman
Modified: 2015-03-23 00:42 UTC (History)
3 users (show)

Fixed In Version: gdm-3.8.4-14.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 965370
Environment:
Last Closed: 2014-06-13 09:53:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Toman 2014-01-08 14:33:38 UTC
+++ This bug was initially created as a clone of Bug #965370 +++

Version-Release number of selected component:
gdm-3.8.1.1-3.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        'gdm-session-worker [pam/gdm-password]'
crash_function: act_user_is_loaded
executable:     /usr/libexec/gdm-session-worker
kernel:         3.9.2-301.fc19.x86_64
runlevel:       N 5
uid:            0
var_log_messages: May 20 18:00:07 vinesh-teotia abrt[7166]: Saved core dump of pid 7163 (/usr/libexec/gdm-session-worker) to /var/tmp/abrt/ccpp-2013-05-20-18:00:06-7163 (18575360 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 act_user_is_loaded at act-user.c:1463
 #1 gdm_session_settings_load at gdm-session-settings.c:321
 #2 attempt_to_load_user_settings at gdm-session-worker.c:618
 #3 gdm_session_worker_update_username at gdm-session-worker.c:659
 #4 gdm_session_worker_process_pam_message at gdm-session-worker.c:756
 #5 gdm_session_worker_pam_new_messages_handler at gdm-session-worker.c:849
 #6 pam_vprompt at pam_vprompt.c:83
 #7 pam_prompt at pam_vprompt.c:111
 #8 _unix_read_password at support.c:825
 #9 pam_sm_authenticate at pam_unix_auth.c:160

--- Additional comment from vineshteotia on 20130521T03:52:28 ---

Created attachment 750829 [details]
File: backtrace

--- Additional comment from vineshteotia on 20130521T03:52:33 ---

Created attachment 750830 [details]
File: cgroup

--- Additional comment from vineshteotia on 20130521T03:52:36 ---

Created attachment 750831 [details]
File: core_backtrace

--- Additional comment from vineshteotia on 20130521T03:52:41 ---

Created attachment 750832 [details]
File: dso_list

--- Additional comment from vineshteotia on 20130521T03:52:45 ---

Created attachment 750833 [details]
File: environ

--- Additional comment from vineshteotia on 20130521T03:52:50 ---

Created attachment 750834 [details]
File: limits

--- Additional comment from vineshteotia on 20130521T03:52:54 ---

Created attachment 750835 [details]
File: maps

--- Additional comment from vineshteotia on 20130521T03:53:02 ---

Created attachment 750836 [details]
File: open_fds

--- Additional comment from vineshteotia on 20130521T03:53:06 ---

Created attachment 750837 [details]
File: proc_pid_status

--- Additional comment from jay.finger on 20131008T15:50:07 ---

I was just mucking around with dropbox from inside chrome, 

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        'gdm-session-worker [pam/gdm-password]'
crash_function: act_user_is_loaded
executable:     /usr/libexec/gdm-session-worker
kernel:         3.11.3-201.fc19.x86_64
package:        gdm-3.8.4-2.fc19
reason:         Process /usr/libexec/gdm-session-worker was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            0

--- Additional comment from mclasen on 20140108T00:43:08 ---

Looks like gdm_session_worker_update_username passes any non-NULL username down to gdm_session_settings_load, which in turn calls act_user_manager_get_user with that name. 

But act_user_manager_get_user rejects the empty string as invalid argument, and returns NULL. Things go downhill from there.

Comment 1 Michal Toman 2014-01-08 14:33:42 UTC
The same problem has been detected in Red Hat Enterprise Linux 7. The following packages are affected:

gdm-3.8.4-7.el7.x86_64
gdm-3.8.4-9.el7.x86_64

Comment 3 Ray Strode [halfline] 2014-01-08 20:02:46 UTC
probably fixed by:

https://git.gnome.org/browse/gdm/commit/?id=29def8761bbac04cf84c7f83722bed447d5d03c6

Comment 5 Ludek Smid 2014-06-13 09:53:23 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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