Bug 1014647 - KDE session does not start
Summary: KDE session does not start
Keywords:
Status: CLOSED DUPLICATE of bug 1015048
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F20Blocker-kde
TreeView+ depends on / blocked
 
Reported: 2013-10-02 13:21 UTC by nucleo
Modified: 2013-10-03 14:24 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-03 14:24:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nucleo 2013-10-02 13:21:31 UTC
Description of problem:
KDE session does not start on last F20 nightly KDE images 20131001.09-1.

Version-Release number of selected component (if applicable):
sddm-0.2.0-0.9.20130821git50ca5b20.fc20

How reproducible:
Always.

Steps to Reproduce:
1. Start live image.
2.
3.

Actual results:
Black screen.

Additional info:
Session can be started from kdm after installing kdm and removing sddm.

Comment 1 Martin Bříza 2013-10-03 10:12:30 UTC
Hi,
did you remove SDDM and have installed KDM instead? Did you enable the kdm.service via systemctl after that?

Comment 2 nucleo 2013-10-03 10:15:02 UTC
At first I switched to 3 runlevel, then removed sddm, installed kdm, enabled kdm.service, switched to 5 runlevel and logged in kdm as liveuser.

Comment 3 Jaroslav Reznik 2013-10-03 12:31:40 UTC
Btw. black screen in latest composes could be caused by broken NetworkManager - I hit it even with KDM after Oct 02 updates. It can be just coincidence and it's different bug but fyi.

Comment 4 nucleo 2013-10-03 12:41:29 UTC
I tested latest nightly composes and Beta TC1, with kdm can login, with sddm can't.

Comment 5 Martin Bříza 2013-10-03 14:24:01 UTC
Oh, yeah, I got it wrong initially. I reported it as Bug 1015048. The solution is already attached to the report and I'm waiting for somebody to merge it into spin-kickstarts.
Even though this report is older, I'll close this one as mine has all the information needed and is reported against the correct component.
Thanks for your report!

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


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