Bug 905371

Summary:	kde login fails after last update
Product:	[Fedora] Fedora	Reporter:	Fabio Brugnara <fabio.brugnara>
Component:	kde-settings	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, smparrish, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-05 03:08:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Fabio Brugnara 2013-01-29 09:30:45 UTC

Description of problem:

After the last update, it became impossible to login in a KDE session.

Version-Release number of selected component (if applicable):
kde-settings 4.9.18.fc18

How reproducible:
always, to me

Steps to Reproduce:
1. wait for the kdm screen to appear
2. try to login in kde session
3.
  
Actual results:

KDE session is aborted immediately, and you are brought back to login screen

Expected results:

KDE session starts

Additional info:

After some struggling, I found a script

/etc/kde/env/fedora-kde-display-handler.sh

that is invoked during kde startup, and, according to rpm, belongs to the above mentioned package.
It contains "exit" commands that cause the whole startkde script to stop.
Everything went OK by substituting the "exit" commands in that script with "return" statements.

bye,
thank you for the good work on fedora and KDE

Fabio Brugnara

Comment 1 Fedora Update System 2013-01-29 11:43:11 UTC

libkscreen-0.0.71-2.fc17, kde-workspace-4.9.5-4.fc17, kscreen-0.0.71-3.fc17, kde-settings-4.8-24.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/FEDORA-2013-1248/kde-settings-4.8-24.fc17,kde-workspace-4.9.5-4.fc17,kscreen-0.0.71-3.fc17,libkscreen-0.0.71-2.fc17

Comment 2 Fedora Update System 2013-01-29 11:45:58 UTC

libkscreen-0.0.71-2.fc18, kde-workspace-4.9.5-4.fc18, kscreen-0.0.71-3.fc18, kde-settings-4.9-19.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-1183/kde-settings-4.9-19.fc18,kde-workspace-4.9.5-4.fc18,libkscreen-0.0.71-2.fc18,kscreen-0.0.71-3.fc18

Comment 3 Rex Dieter 2013-01-29 12:52:14 UTC

well, craptastic.  Ill fix asap

Comment 4 Rex Dieter 2013-01-29 13:05:40 UTC

I see someone else (dvratil) stepped up to take care of it... the new kde-settings builds referenced above should fix things.

And thanks for the excellent detective-work and diagnosis.

Comment 5 Fedora Update System 2013-02-01 16:50:16 UTC

Package libkscreen-0.0.71-2.fc18, kde-workspace-4.9.5-4.fc18, kscreen-0.0.71-3.fc18, kde-settings-4.9-19.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libkscreen-0.0.71-2.fc18 kde-workspace-4.9.5-4.fc18 kscreen-0.0.71-3.fc18 kde-settings-4.9-19.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-1183/kde-settings-4.9-19.fc18,kde-workspace-4.9.5-4.fc18,libkscreen-0.0.71-2.fc18,kscreen-0.0.71-3.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-02-05 03:08:34 UTC

libkscreen-0.0.71-2.fc18, kscreen-0.0.71-3.fc18, kde-settings-4.9-19.fc18, kde-workspace-4.9.5-7.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2013-02-05 17:04:51 UTC

libkscreen-0.0.71-2.fc17, kscreen-0.0.71-3.fc17, kde-settings-4.8-24.fc17, kde-workspace-4.9.5-7.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.