Bug 1224566 - Black screen follows login to F22 KDE after 24 May 2015 update.
Summary: Black screen follows login to F22 KDE after 24 May 2015 update.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-24 19:33 UTC by David Koppelman
Modified: 2015-11-02 15:16 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-02 14:41:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The .x-session-errors file. (83.47 KB, text/plain)
2015-05-24 20:46 UTC, David Koppelman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 353963 0 None None None Never

Description David Koppelman 2015-05-24 19:33:33 UTC
Description of problem:

Logging in to F22 KDE leads to a black screen rather than the
desktop. The black screen appears after the KDE progress screen (the
one appearing after the password is typed). Mouse right-clicks don't
work. Using Alt-SPC does pop up a search window that can be used to
start konsole (and other apps). From konsole it is possible to start
applications, and Alt-TAB can be used to switch between windows.

The problem appeared after an update on 24 May 2015 at about 10:00
CDT, the updated included kernel-4.0.4.301-fc22.


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


How reproducible:

Every time.

Steps to Reproduce:
1. Log in.
2.
3.

Actual results:

Black screen. Cursor moves but right clicks do nothing.

Expected results:

Plasma desktop appears.

Additional info:

Comment 1 Rex Dieter 2015-05-24 20:34:04 UTC
Can you try booting into an older kernel?

What video chipset/driver are you using?

Comment 2 David Koppelman 2015-05-24 20:45:20 UTC
(In reply to Rex Dieter from comment #1)
> Can you try booting into an older kernel?

I tried, but the system hung during the boot process, I don't remember exactly where.

> 
> What video chipset/driver are you using?

I'll answer below, but first let me say that the plasma desktop works when I log in as root. And even when logging in as a normal user graphics work. For example, I get the wobbly-window effect.  I just don't see the plasma desktop, I need to start everything from a shell.

I'm using the NVIDIA binary drivers, version 349.16. The GPU is Quadro K2100M.

I'm going to attach .xsession-errors, that might help.

Comment 3 David Koppelman 2015-05-24 20:46:17 UTC
Created attachment 1029295 [details]
The .x-session-errors file.

Comment 4 David Koppelman 2015-05-27 21:09:29 UTC
I don't know how useful this is, but the .x-session-errors file contains:

service is "org.kde.StatusNotifierItem-7432-1"
Registering a client interface to the KStatusNotifierWatcher
KStatusNotifierWatcher not reachable

Comment 5 Germano Massullo 2015-10-12 12:59:11 UTC
Confirming on 
plasma-desktop-5.4.1-2.fc22.1.x86_64
plasma-workspace-5.4.1-3.fc22.x86_64
and on nvidia Geforce GTX260 with nVidia propertary drivers
and on Intel i915 VGA drivers

At the bottom of xsession-errors I read

amarok(2211)/kio (Slave) KIO::Slave::kill: killing slave pid 3198 ( "http://ws.audioscrobbler.com" )
kio_http(3198)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
kio_http(3198)/kio (kioslave) KIO::SlaveBase::dispatchLoop: slave was killed, returning
kio_http(3198)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
QDBusObjectPath: invalid path ""
QDBusObjectPath: invalid path ""
1444554111366	addons.update-checker	WARN	Update manifest for {**removed**} did not contain an updates property

QXcbConnection: XCB error: 3 (BadWindow), sequence: 49198, resource id: 134217739, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 49200, resource id: 134217738, major code: 3 (GetWindowAttributes), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 49201, resource id: 134217738, major code: 14 (GetGeometry), minor code: 0
Qt: Session management error: networkIdsList argument is NULL
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1670, resource id: 136314888, major code: 18 (ChangeProperty), minor code: 0
Qt: Session management error: networkIdsList argument is NULL
Qt: Session management error: networkIdsList argument is NULL
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2778, resource id: 136314888, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 14699, resource id: 134217738, major code: 25 (SendEvent), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2965, resource id: 138412040, major code: 18 (ChangeProperty), minor code: 0
Qt: Session management error: networkIdsList argument is NULL
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3959, resource id: 136314888, major code: 18 (ChangeProperty), minor code: 0
Touchpad detached
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
Touchpad reset
Qt: Session management error: networkIdsList argument is NULL
Qt: Session management error: networkIdsList argument is NULL
Qt: Session management error: networkIdsList argument is NULL
QXcbConnection: XCB error: 3 (BadWindow), sequence: 6232, resource id: 136314888, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 6586, resource id: 138412040, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 6590, resource id: 140509192, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 16273, resource id: 134217738, major code: 25 (SendEvent), minor code: 0
Qt: Session management error: networkIdsList argument is NULL
QXcbConnection: XCB error: 3 (BadWindow), sequence: 7050, resource id: 136314888, major code: 18 (ChangeProperty), minor code: 0
Touchpad detached
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter

Comment 6 Rex Dieter 2015-10-12 15:18:25 UTC
I wouldn't assume the latest commenti is the same cause.

In particular, the logs you post seem to be after an xserver crash, where client applications are exiting due to that error condition.

Comment 7 Germano Massullo 2015-10-12 15:42:57 UTC
(In reply to Rex Dieter from comment #6)
> I wouldn't assume the latest commenti is the same cause.
> 
> In particular, the logs you post seem to be after an xserver crash, where
> client applications are exiting due to that error condition.

Full log at https://mega.nz/#F!x0IBDLpB
I haven't uploaded it here due possible presence of personal sensitive data

Comment 8 Rex Dieter 2015-10-12 16:19:02 UTC
I get prompted "Enter decription key: " following that link.

Comment 9 Germano Massullo 2015-10-12 21:16:01 UTC
(In reply to Rex Dieter from comment #8)
> I get prompted "Enter decription key: " following that link.

Ah MeGa changed the way they share the folders. Try the following URL
https://mega.nz/#F!x0IBDLpB!JH_YhWMwKE3IiN1ShRLgbQ

Comment 10 Germano Massullo 2015-10-16 12:44:51 UTC
The title is incorrect. Yesterday I experienced a similar problem while I was using KDE Plasma on a VGA with Radeon drivers. I added to the URL at comment #9, a folder named "2" containing
- dmesg;
- messages;
- xsession-errors;
- Xorg.0.log
logs.

Comment 11 Germano Massullo 2015-11-02 12:36:33 UTC
Could you please provide some feedback/infos/etc. to https://bugs.kde.org/show_bug.cgi?id=353963 in order to increase bugreport relevance?

Comment 12 David Koppelman 2015-11-02 14:41:15 UTC
I've long since applied a workaround to this bug, renaming the .local,
.config, and .kde directories and salvaging what I could from them
when replacement directories were created on a subsequent login. I've
had no problems since but I kept the renamed directories in case
someone wanted to track down the cause. Given the amount of time
that has passed, I'm going to withdraw (or close) this report.

In trying to find a solution I learned that the symptoms that I
experienced can be due to many causes. I agree that it's better to
report an issue like this to KDE, where they can sort the problem
reports by underlying causes.


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