Bug 373948 - blank screen after login
Summary: blank screen after login
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.8.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-12-20 10:30 UTC by Hagai Hadad
Modified: 2016-12-22 17:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hagai Hadad 2016-12-20 10:30:53 UTC
Application: kwin_x11 (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.13-300.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
1. I installed fedora 25 last week.
2. I installed Nvidia driver 375.20
3. I used Gnome Classic for the rest of the week - no problem (there is a login problem with gnome-shell - known problem).
4. decided to give kde a try
5. installed kde plasma
 1. su -
 2. dnf group install kde-desktop-environment
 3. reboot
 4. choose "plasma" on login screen
 5. login - blank screen
 6. logout (pkill -kill -u <my user name>)
 7. login again - crash report

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc27189d940 (LWP 4136))]

Thread 2 (Thread 0x7fc263fff700 (LWP 4141)):
#0  0x00007fc280cb90d1 in ppoll () from /lib64/libc.so.6
#1  0x00007fc281abb9c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5
#2  0x00007fc281abced6 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#3  0x00007fc281a7073a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#4  0x00007fc2818cd5f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x00007fc2835dd739 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5
#6  0x00007fc2818d19da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#7  0x00007fc283ae16ca in start_thread () from /lib64/libpthread.so.0
#8  0x00007fc280cc4f6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc27189d940 (LWP 4136)):
[KCrash Handler]
#6  0x00007fc280bf292f in raise () from /lib64/libc.so.6
#7  0x00007fc280bf452a in abort () from /lib64/libc.so.6
#8  0x00007fc2818bcbb1 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#9  0x00007fc281a96fd5 in QObjectPrivate::QObjectPrivate(int) () from /lib64/libQt5Core.so.5
#10 0x00007fc2884ef414 in QQmlEnginePrivate::QQmlEnginePrivate(QQmlEngine*) () from /lib64/libQt5Qml.so.5
#11 0x00007fc2884f29a2 in QQmlEngine::QQmlEngine(QObject*) () from /lib64/libQt5Qml.so.5
#12 0x00007fc289d2e103 in KWin::Scripting::Scripting(QObject*) () from /lib64/libkwin.so.5
#13 0x00007fc289d2e221 in KWin::Scripting::create(QObject*) () from /lib64/libkwin.so.5
#14 0x00007fc289c14ff5 in KWin::Workspace::init() () from /lib64/libkwin.so.5
#15 0x00007fc289c15bf3 in KWin::Workspace::Workspace(QString const&) () from /lib64/libkwin.so.5
#16 0x00007fc289c6a023 in KWin::Application::createWorkspace() () from /lib64/libkwin.so.5
#17 0x00007fc28a04ddce in QtPrivate::QFunctorSlotObject<KWin::ApplicationX11::performStartup()::{lambda()#2}::operator()() const::{lambda()#1}, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libkdeinit5_kwin_x11.so
#18 0x00007fc281a98ae6 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#19 0x00007fc28a04e12f in QtPrivate::QFunctorSlotObject<KWin::ApplicationX11::performStartup()::{lambda()#2}, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libkdeinit5_kwin_x11.so
#20 0x00007fc281a98ae6 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#21 0x00007fc2827e481b in KSelectionOwner::Private::claimSucceeded() () from /lib64/libKF5WindowSystem.so.5
#22 0x00007fc281a9982b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#23 0x00007fc2822b1ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#24 0x00007fc2822b9671 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#25 0x00007fc281a717aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#26 0x00007fc281abed3b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#27 0x00007fc281abd078 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#28 0x00007fc26ac8e79d in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5XcbQpa.so.5
#29 0x00007fc281a7073a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#30 0x00007fc281a7823c in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#31 0x00007fc28a0500b6 in kdemain () from /lib64/libkdeinit5_kwin_x11.so
#32 0x00007fc280bdd401 in __libc_start_main () from /lib64/libc.so.6
#33 0x000056372620ccca in _start ()

Reported using DrKonqi
Comment 1 Martin Flöser 2016-12-20 16:18:36 UTC
You have broken graphics drivers. Due to that QML aborts. This is probably also the reason for GNOME Shell to not start. Please contact your distribution's support channel for fixing the drivers.
Comment 2 Hagai Hadad 2016-12-22 17:20:55 UTC
I disagree on both analysis (driver and gnome-shell)

I have another nvidia card which is GTX580 (my current card is GTX960)
Here is the test I made:
I removed my GTX960 and installed GTX580
login to kde - works !!!
logout, shutdown, replace cards back to original.
login again to KDE - works !!!

So I'm writing to you now from firefox on kde plasma, fc 25 - with a card which previously was not able to load kde.

My guess - once the first login occurred (with the GTX580), "something" was set in place.

About the gnome-shell issue - the problem is re-login. you can login for the first time. but you can't re-login if you logout. Had it been a driver issue, most probably the first login would have failed.