Bug 1016137

Summary: [abrt] kdm-4.11.1-3.fc19: __select_nocancel: Process /usr/bin/kdm was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: glad08
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bb78cb249450449606a461427ab56de52fe0dfd9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-08 08:14:55 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:
Attachments:
Description Flags
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description glad08 2013-10-07 15:06:54 UTC 
Description of problem:
Description of problem:
kdm fails to start after reboot


Version-Release number of selected component (if applicable): Fedora 19, kdm-4.11.1-3.fc19.x86_64


How reproducible: not every time, but frequently


Steps to Reproduce:
1. Restart my computer (due to kernel updates for example)
2.
3.

Actual results: Boot screen shows logo, when I press escape I see log, where something about "reaching graphical interface target" and several lines up something about "plymouth fails to start and not running"


Expected results: logon screen


Additional info:

If I switch on some terminal (e.g. Alt-F2), and login as root and call service kdm restart then I get my graphical logon screen.

Version-Release number of selected component:
kdm-4.11.1-3.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace:      
backtrace_rating: 4
cmdline:        /usr/bin/kdm vt1
crash_function: __select_nocancel
executable:     /usr/bin/kdm
kernel:         3.11.3-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Comment 1 glad08 2013-10-07 15:07:00 UTC 
Created attachment 808878 [details]
File: cgroup
Comment 2 glad08 2013-10-07 15:07:05 UTC 
Created attachment 808880 [details]
File: core_backtrace
Comment 3 glad08 2013-10-07 15:07:14 UTC 
Created attachment 808881 [details]
File: dso_list
Comment 4 glad08 2013-10-07 15:07:21 UTC 
Created attachment 808882 [details]
File: environ
Comment 5 glad08 2013-10-07 15:07:27 UTC 
Created attachment 808883 [details]
File: limits
Comment 6 glad08 2013-10-07 15:07:33 UTC 
Created attachment 808884 [details]
File: maps
Comment 7 glad08 2013-10-07 15:07:38 UTC 
Created attachment 808885 [details]
File: open_fds
Comment 8 glad08 2013-10-07 15:07:43 UTC 
Created attachment 808886 [details]
File: proc_pid_status
Comment 9 glad08 2013-10-07 15:07:48 UTC 
Created attachment 808887 [details]
File: var_log_messages
Comment 10 Rex Dieter 2013-10-07 15:09:39 UTC 
probably a dup of bug #967521
Comment 11 glad08 2013-10-08 08:14:55 UTC 
>probably a dup of bug #967521
yes, thats it

*** This bug has been marked as a duplicate of bug 967521 ***