Bug 1224566
Summary: | Black screen follows login to F22 KDE after 24 May 2015 update. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Koppelman <koppel> | ||||
Component: | plasma-desktop | Assignee: | KDE SIG <kde-sig> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 22 | CC: | erecio, germano.massullo, jgrulich, jreznik, kde-sig, kevin, koppel, mbriza, rdieter, rnovacek, 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: | 2015-11-02 14:41:15 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: | |||||||
Attachments: |
|
Description
David Koppelman
2015-05-24 19:33:33 UTC
Can you try booting into an older kernel? What video chipset/driver are you using? (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. Created attachment 1029295 [details]
The .x-session-errors file.
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 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 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. (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 I get prompted "Enter decription key: " following that link. (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 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. Could you please provide some feedback/infos/etc. to https://bugs.kde.org/show_bug.cgi?id=353963 in order to increase bugreport relevance? 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. |