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 1091087 - KDE defaults to failsafe
Summary: KDE defaults to failsafe
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kdebase-workspace
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Than Ngo
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2014-04-24 20:29 UTC by Robin R. Price II
Modified: 2014-06-18 09:00 UTC (History)
4 users (show)

Fixed In Version: kde-workspace-4.10.5-18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-13 09:46:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Robin R. Price II 2014-04-24 20:29:30 UTC
Description of problem:

When installing RHEL7-RC and choosing the KDE option, the initial log-in defaults to failsafe.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Installed RHEL7
2. Choose KDE as default
3. After first boot, select session and you will notice failsafe is default

Actual results:
Failsafe mode is default

Expected results:
Full KDE experience

Additional info:

I am a total KDE noob.  I have been running Gnome for years.  However, when defaulting RHEL7 to KDE, I noticed I wasn't able to configure the environment and was getting errors about KDE being in failsafe mode.

After logging out, I noticed the default is to login as Failsafe.  
I am not sure if this is by design but I feel Failsafe should be an option you switch to when troubleshooting KDE issues.  No other community spins (Fedora) I installed defaulted to KDE being in Failsafe.  Therefore I feel this needs to be corrected.


Comment 2 Vladimir Benes 2014-04-25 07:50:15 UTC
This is an easy fix and should be really fixed before GA. You can switch to full KDE experience by clicking the gearwheel and choosing KDE w/o failsave. But this should definitely be the default.

Comment 7 Vladimir Benes 2014-04-25 10:24:37 UTC
steps to reproduce:
1. install fresh system with only KDE enabled in anaconda
2. when gdm starts click test user and try gear wheel to select session

there is KDE Plasma Workspace (failsafe session) selected so it will start by default. The other one without failsave should be selected and started

Comment 14 Vladimir Benes 2014-04-29 10:47:11 UTC
I've installed RC2 and updated kde-workspace via ssh while in initial-setup. GDM started correctly with default session set to KDE Workspace for test user and login pushed me correctly to default KDE session not fail save.

Comment 15 Ludek Smid 2014-06-13 09:46:37 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.