Description of problem: Trying to log into a Plasma 5 session. Version-Release number of selected component: kf5-kinit-5.3.0-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: klauncher --fd=8 crash_function: qt_message_fatal executable: /usr/libexec/kf5/klauncher kernel: 3.18.0-0.rc0.git9.4.fc22.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1411 #3 QMessageLogger::fatal at global/qlogging.cpp:639 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:346 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:155 #6 QXcbIntegrationPlugin::create at qxcbmain.cpp:50 #7 loadIntegration at kernel/qplatformintegrationfactory.cpp:56 #8 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:73 #9 init_platform at kernel/qguiapplication.cpp:1011 #10 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1166 #11 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1183
Created attachment 948514 [details] File: backtrace
Created attachment 948515 [details] File: cgroup
Created attachment 948516 [details] File: core_backtrace
Created attachment 948517 [details] File: dso_list
Created attachment 948518 [details] File: environ
Created attachment 948519 [details] File: limits
Created attachment 948520 [details] File: maps
Created attachment 948521 [details] File: open_fds
Created attachment 948522 [details] File: proc_pid_status
Created attachment 948523 [details] File: var_log_messages
This hits an assert in Qt because Qt fails to talk to X server via XCB. This happens before KLauncher does anything that could mess up XCB, so it's most probably an issue in XCB, Qt-XCB integration, or your configuration (or some rawhide breakage again :-) I'm moving this to Qt, as klauncher is almost definitely innocent in this case. Could you please start X session manually from VT, then switch to another VT and run DISPLAY=":0" startkde &> startkde.log There might be some more indication of what the problem is in what the applications print to console.
(In reply to Dan Vrátil from comment #11) > This hits an assert in Qt because Qt fails to talk to X server via XCB. This > happens before KLauncher does anything that could mess up XCB, so it's most > probably an issue in XCB, Qt-XCB integration, or your configuration (or some > rawhide breakage again :-) > > I'm moving this to Qt, as klauncher is almost definitely innocent in this > case. > > > Could you please start X session manually from VT, then switch to another VT > and run > > DISPLAY=":0" startkde &> startkde.log > > There might be some more indication of what the problem is in what the > applications print to console. I'm trying to upgrade from KDE Plasma4 to Plasma5, and I've used the latest dvratil repo for that, but still with no success. This is what the contents of the startkde.log are: ksplashqml: error while loading shared libraries: libKF5SonnetUi.so.5: cannot open shared object file: No such file or directory xset: bad font path element (#2), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... kdeinit5: Shutting down running client. Qt: Session management error: networkIdsList argument is NULL No DBUS session-bus found. Check if you have started the DBUS server. kdeinit5: Communication error with launcher. Exiting!
Could you please install kf5-sonnet-ui and try again? Maybe the missing library is causing troubles. I already updated the plasma-workspace package in the COPR to require the package, but it failed to build on Rawhide (broken deps in base repo).
After kf5-sonnet-ui install: xset: bad font path element (#2), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... Qt: Session management error: networkIdsList argument is NULL Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KCrash: Application 'kcminit_startup' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit KXMessages used on non-X11 platform! This is an application bug. KXMessages used on non-X11 platform! This is an application bug. ksmserver: error while loading shared libraries: libKF5IdleTime.so.5: cannot open shared object file: No such file or directory Qt: Session management error: networkIdsList argument is NULL KCrash: Application 'kded5' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit startkde: Shutting down... klauncher: Exiting on signal 15 klauncher: Exiting on signal 1 startkde: Running shutdown scripts... startkde: Done.
Hmm, now it's complaining about kf5-kidletime missing (please install it too, updated plasma-workspace already building in COPR). It's weird that I haven't seen this deps problem before - most people probably install kf5-*, so all deps are satisfied :-) Not sure if that will help though, ksmserver is apparently started *after* kcminit_startup crashes (probably by DrKonqi), so the key problem is that actually kcminit_startup crashes. Maybe the xset error is related?
*** Bug 1160202 has been marked as a duplicate of this bug. ***
*** Bug 1162003 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Waiting on feedback from reporter(s)... per comment #15
(In reply to Rex Dieter from comment #19) > Waiting on feedback from reporter(s)... per comment #15 I actually don't remember what happened next, but I know that everything got settled in one of the next updates. I did install kf5-* and didn't check the startup log again, since everything worked fine...
OK, lets close then